Terminal, base station, transmission method, reception method, and integrated circuit

Abstract

The terminal includes: a control circuit that controls an uplink transmission timing using one of a first offset and a second offset shorter than the first offset, based on information related to a control signal for scheduling; and a transmission circuit that performs uplink transmission based on the control of the uplink transmission timing.

Description

Technical Field

[0001] This disclosure relates to terminals, base stations, transmission methods, and reception methods. Background Technology

[0002] Regarding 5G standardization, 3GPP (3rd Generation Partnership Project) has discussed New Radio access technology (NR) and released the NR Release 15 (Rel.15) specification.

[0003] Existing technical documents

[0004] Non-patent literature

[0005] Non-patent literature 1: 3GPP, TR 38.821, V16.0.0 “Solutions for NR to support non-terrestrial networks (NTN) (Release 16)”, 2019-12

[0006] Non-patent literature 2: 3GPP, TS 38.321, V16.2.0 "Medium Access Control (MAC) protocol specification (Release 15)", 2020-09 Summary of the Invention

[0007] However, there is still room for research into appropriate timing control corresponding to the propagation delay between the terminal and the base station.

[0008] The non-limiting embodiments of this disclosure help to provide terminals, base stations, transmitting methods, and receiving methods capable of implementing appropriate timing control corresponding to the propagation delay between the terminal and the base station.

[0009] One embodiment of the terminal disclosed herein includes: a control circuit that controls uplink transmission timing using one of a first offset and a second offset shorter than the first offset, based on information related to a control signal used for scheduling; and a transmission circuit that performs uplink transmission based on the control of the uplink transmission timing.

[0010] It should be noted that these general or specific methods can be implemented by systems, devices, methods, integrated circuits, computer programs or recording media, or by any combination of systems, devices, methods, integrated circuits, computer programs and recording media.

[0011] According to one embodiment of this disclosure, appropriate timing control corresponding to the propagation delay between the terminal and the base station can be achieved.

[0012] Further advantages and effects of one aspect of this disclosure will be illustrated by the description and accompanying drawings. The aforementioned advantages and / or effects are provided by the various embodiments and the features described in the description and drawings, but it is not necessary for all of these features to be provided in order to obtain one or more of the same features. Attached Figure Description

[0013] Figure 1 This is a diagram illustrating an example of a four-step random access process.

[0014] Figure 2 This diagram illustrates an example of timing adjustments based on the terminal's location information and the satellite's orbital information.

[0015] Figure 3 This is a diagram illustrating an example of transmission time slot timing.

[0016] Figure 4 This is a block diagram representing a structural example of a part of a terminal.

[0017] Figure 5 This is a block diagram representing a structural example of a part of a base station.

[0018] Figure 6 This is a block diagram illustrating an example of the structure of the terminal in Implementation Method 1.

[0019] Figure 7 This is a block diagram illustrating an example of the structure of a base station according to Implementation Method 1.

[0020] Figure 8 This is a diagram illustrating an example of a sequence diagram related to timing control in Implementation 1.

[0021] Figure 9 This diagram illustrates an example of timing adjustment that uses the cell's inherent TA (Timing Advance) offset and location-based timing adjustment values.

[0022] Figure 10 This diagram illustrates an example of timing adjustments using each TA, including TA command 2.

[0023] Figure 11 This indicates that K was used. adj,UE A diagram illustrating an example of timed adjustments to information.

[0024] Figure 12 This is a diagram showing an example of a sequence diagram related to timing control in Implementation 2.

[0025] Figure 13 This is a diagram illustrating an example of a flowchart related to timing control in Implementation Method 3.

[0026] Figure 14 This is a diagram illustrating the exemplary architecture of a 3GPP NR system.

[0027] Figure 15 This is a schematic diagram illustrating the functional separation between NG-RAN (Next Generation-Radio Access Network) and 5GC (5th Generation Core).

[0028] Figure 16 This is a sequence diagram of the setting / resetting process for an RRC (Radio Resource Control) connection.

[0029] Figure 17 This is a schematic diagram illustrating the application scenarios of high-capacity high-speed communication (eMBB), massive machine-type communications (mMTC), and ultra-reliable and low-latency communications (URLLC).

[0030] Figure 18 This is a block diagram representing an exemplary 5G system architecture for non-roaming scenarios. Detailed Implementation

[0031] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings.

[0032] [Expansion to networks beyond the terrestrial plane (NTN: Non-Terrestrial Network)]

[0033] Version 15 (Rel. 15) of New Radio access technology (NR) has been standardized as a radio access technology for terrestrial networks. On the other hand, NR has explored the extension of communications using satellites and / or high-altitude platform stations (HAPS) to non-terrestrial networks (NTN) (e.g., Non-Patent Document 1). In an NTN environment, for example, terminals and base stations communicate wirelessly via satellite. Hereinafter, the wireless link between the terminal and the satellite is sometimes referred to as a "service link," and the wireless link between the satellite and the base station is sometimes referred to as a "feeder link."

[0034] In an NTN environment, the satellite coverage area (e.g., more than one cell) for a ground terminal or aircraft terminal is formed by beams from the satellite. Furthermore, the round-trip time of radio wave propagation between the terminal and the satellite depends on the satellite's altitude (e.g., up to approximately 36,000 km) and / or the angle measured from the terminal, i.e., the positional relationship between the satellite and the terminal. Additionally, when the base station is configured at a terrestrial gateway (GW), the round-trip time of radio wave propagation between the base station and the terminal is further increased by the round-trip time of radio wave propagation between the satellite and the terrestrial GW.

[0035] For example, Non-Patent Document 1 describes that in an NTN, the maximum round-trip time (RTT) for radio wave propagation between a base station and a terminal can be approximately 540 ms. Furthermore, Non-Patent Document 1 also describes a maximum delay difference of approximately 10 ms that can occur depending on the location of the terminal within the beam (cell). This maximum delay difference, for example, represents the difference between the round-trip time between the terminal furthest from the satellite and that satellite within the beam (cell), and the round-trip time between the terminal closest to the satellite and that satellite.

[0036] [Random Access Procedure]

[0037] In 5G NR, terminals use random access channels for initial access and data transmission requests. For example, the random access process is implemented through four-step random access (also known as "4-step RACH (Random Access Channel)" or "4-step CBRA (Contention Based Random Access)").

[0038] Figure 1This is a diagram illustrating an example of a four-step random access procedure. In four-step random access, for example, as... Figure 1 As shown, in the first step of transmission (MSG1), the terminal (UE: User Equipment) sends the PRACH (Physical Random Access Channel) preamble signal to the base station (gNB). The MSG1 transmission in the terminal is performed within the transmission timing (slot timing or RACH opportunity) notified to each cell by the base station. Furthermore, the transmission of the PRACH signal (e.g., the preamble signal) is sometimes simply referred to as "PRACH transmission" or "transmitting PRACH". Similarly, the reception of the PRACH signal is sometimes referred to as "PRACH reception" or "receiving PRACH". Furthermore, the transmission and reception of signals on other channels are sometimes similarly simply described.

[0039] The base station receives and decodes MSG1. In the second step of transmission (MSG2), it notifies the terminal of the RA response (Random Access response) for the PRACH preamble signal and the uplink transmission timing scheduling information of MSG3.

[0040] The terminal receives and decodes MSG2. In the third step (MSG3), it uses the scheduling information indicated by MSG2 to notify the base station of terminal-related information (e.g., terminal ID) and other information used to establish a connection. For example, MSG3 is notified in the PUSCH (Physical Uplink Shared Channel). The information notified by MSG3 can also be referred to as "RRC (Radio Resource Control) Connection Request Information".

[0041] The base station receives and decodes MSG3, and in the fourth step (MSG4), it sends a notification of the connection establishment response, etc.

[0042] [Timed Adjustment]

[0043] In 5G NR, the timing of terminal transmission is controlled by concentrating signals from different terminals within a cell to the base station within a certain time period. For example, a certain time period refers to the CP (Cyclic Prefix) of OFDM (Orthogonal Frequency Division Multiplexing) signals or DFT-S-OFDM (Discrete Fourier Transform-Spread-OFDM) signals.

[0044] During random access, the transmission of MSG1 in the terminal is performed during the transmission timing (RACH opportunity) notified to each cell by the base station. Here, the terminal determines the transmission timing based on the reception timing of the synchronization signal, referred to as the "SSB (Synchronization Signal) / PBCH (Physical Broadcast Channel) Block," transmitted from the base station in the downlink. Therefore, corresponding to the propagation delay between the base station and the terminal, the reception timing in the base station will deviate from the reception timing envisioned by the base station. Here, the reception timing envisioned by the base station is, for example, the reception timing determined based on the transmission timing (RACH opportunity) notified to each cell by the base station.

[0045] Therefore, in MSG2, the base station sends information to the terminal for timing correction (adjustment). This timing correction (adjustment) information is sometimes referred to as a "TA (Timing Advancement) command" (e.g., Non-Patent Document 2). Based on the TA command contained in MSG2, the terminal corrects the transmission timing after MSG3. Furthermore, when a timing deviation is detected in the transmission and reception of signals after MSG3, the base station sends a TA command to the terminal.

[0046] In NTN, because communication between base stations and terminals is long-distance, the propagation delay between base stations and terminals is greater compared to terrestrial cellular systems, and the difference in propagation delay between terminals is also larger. For example, the difference in propagation delay between terminals is equivalent to the difference between the propagation delay between a base station A and a terminal a, and the difference between base station A and a terminal b (different from terminal a).

[0047] Therefore, the reception timing of PRACH messages sent from different terminals varies significantly at the base station, complicating reception at the base station. Furthermore, the TA commands specified in Rel. 15 sometimes fail to correct propagation delays generated in NTN environments. Additionally, expanding the range of TA command values ​​to correct large propagation delays increases the amount of information (e.g., the number of bits) required to notify the TA command.

[0048] Therefore, for example, the following was studied: the terminal estimates the distance between itself and the satellite based on its location information obtained through GNSS (Global Navigation Satellite System) and the satellite's location information obtained based on the satellite's orbital information (satellite ephemeris), calculates the propagation delay, and the terminal autonomously adjusts the timing.

[0049] Figure 2 This diagram illustrates an example of timing adjustments based on the terminal's location information (UE location information) and the satellite's orbital information (satellite ephemeris).

[0050] exist Figure 2 The example illustrates the transmit time slots of the downlink (DL) and receive time slots of the uplink (UL) of the base station (gNB), and the receive time slots of the DL and transmit time slots of the UL of the terminal (UE). Furthermore, Figure 2 The horizontal axis represents the time axis.

[0051] Figure 2 The propagation delay from the timing of transmitting a signal at the base station to the timing of receiving that signal at the terminal is shown, represented by the propagation delay of the feeder link (feeder link delay) and the propagation delay of the service link (service link delay). Additionally, in Figure 2 The diagram illustrates how the terminal uses the TA (Transmission Timing) determined based on the terminal's location information and the satellite's orbital information to adjust the signal transmission timing. Figure 2 The TA in the example is equivalent to twice the propagation latency of the service link.

[0052] However, in terminal timing adjustments based on the distance between the satellite and the terminal, while the latency between the terminal and the satellite (i.e., the service link) is corrected, the latency between the base station configured at the ground-based GW (gateway) and the satellite (i.e., the feeder link) is not corrected. Furthermore, in environments where the satellite and terminal are in non-line-of-sight (NLOS) conditions, the propagation delay calculated using location information may sometimes differ from the actual propagation delay generated in non-line-of-sight environments, which includes reflections and / or diffraction.

[0053] In addition, in 5G NR, Rel.15 specifies the timing of the transmission slots.

[0054] Figure 3This is a diagram illustrating an example of transmission time slot timing. In Figure 3 The text shows examples of transmission slot timing in terrestrial cells as specified in Rel.15, and examples of transmission slot timing for NTN studies.

[0055] exist Figure 3 The example illustrates the transmit time slots of the DL (Deep Path) and the receive time slots of the UL (Upper Path) for a base station (gNB), and the receive time slots of the DL and the transmit time slots of the UL for a terminal (UE). Furthermore, Figure 3 The horizontal axis represents the time axis.

[0056] exist Figure 3 In Rel.15, the timing of the transmission time slots is specified as follows: in the nth time slot, a signal containing DCI (Downlink Control Information) is transmitted from the base station to the terminal, and in the n+K2th time slot, a PUSCH signal is transmitted from the terminal to the base station.

[0057] like Figure 3 As shown, the following case was studied in NTN: for the Rel.15 transmission slot timing specification, an offset K was set to correct for the propagation delay longer than that of terrestrial cells. offset,cell (sometimes abbreviated as "K") offset For example, according to the community broadcast K offset .

[0058] On the other hand, because the round-trip propagation delay (RTT) between the terminal and the satellite varies depending on the location of the terminal within the cell, even with an offset set to correct for a longer propagation delay than that of terrestrial cells, some terminals may still be unable to send data or may wait for a long time to send data.

[0059] Furthermore, research considering both timing control and transmission time slot control using TA is insufficient.

[0060] Therefore, in one non-limiting embodiment of this disclosure, for example for an environment where the propagation delay between the terminal and the base station is increased, such as an NTN environment, both timing control of the TA and control of the transmission time slot are considered to achieve appropriate timing control corresponding to the propagation delay between the terminal and the base station.

[0061] (Implementation Method 1)

[0062] [Overview of Communication Systems]

[0063] One embodiment of the communication system disclosed herein includes a terminal 100 (equivalent to a transmitting device) and a base station 200 (equivalent to a receiving device).

[0064] Figure 4This is a block diagram representing a structural example of a portion of terminal 100. Figure 4 In the terminal 100 shown, the control unit 109 controls the transmission timing based on first information and second information. The first information relates to signal transmission timing control performed in units of signal transmission, and the second information relates to transmission timing control performed in units smaller than the transmission units. The wireless transmission unit 105 transmits signals based on the transmission timing control by the control unit 109.

[0065] Figure 5 This is a block diagram representing a structural example of a portion of base station 200. Figure 5 In the base station 200 shown, the control unit 209 controls the reception timing based on first information related to the control of the reception timing of the signal in the signal receiving unit and second information related to the control of the transmission timing in a unit smaller than the receiving unit. The wireless receiving unit 202 receives the signal based on the control unit 209's control of the reception timing.

[0066] [Terminal Structure]

[0067] Next, an example of the structure of terminal 100 will be described.

[0068] Figure 6 This is a block diagram illustrating an example of the structure of the terminal 100 according to Embodiment 1. The terminal 100 includes a PRACH generation unit 101, a data generation unit 102, a location information acquisition unit 103, a timing adjustment unit 104, a wireless transmission unit 105, an antenna 106, a wireless receiving unit 107, and a demodulation / decoding unit 108. The PRACH generation unit 101, data generation unit 102, location information acquisition unit 103, timing adjustment unit 104, and demodulation / decoding unit 108 may be included in the control unit 109.

[0069] The PRACH generation unit 101 determines the PRACH transmission resources from candidate PRACH transmission resources available in the cell of the base station 200, for example. For instance, the PRACH generation unit 101 sets the time / frequency resources and preamble number for PRACH transmission based on information about the time / frequency resources and preamble number group available for PRACH transmission. This information about the time / frequency resources and preamble number group available for PRACH transmission is, for example, notified by the base station 200.

[0070] The data generation unit 102 generates an uplink transmission data stream and generates a data signal that is transmitted using the time / frequency resources allocated by the base station 200 for data signal transmission and the MCS (Modulation and Coding Scheme).

[0071] The location information acquisition unit 103 uses GNSS functions such as GPS (Global Positioning System) to acquire the location information (latitude, longitude, altitude, etc.) of the terminal 100 and the location information of the satellite being communicated with. The location information acquisition unit 103 calculates the distance between the terminal 100 and the satellite and outputs the calculated distance information to the timing adjustment unit 104. For example, the satellite's location information can also be obtained in advance by acquiring orbital information and / or time information known as "satellite ephemeris".

[0072] The timing adjustment unit 104 adjusts the reception timing of the received signal and the transmission timing of the transmitted signal. For example, the timing adjustment unit 104 adjusts the transmission timing based on information notified or broadcast by the base station 200 and / or information calculated by the timing adjustment unit 104.

[0073] For example, the timing adjustment unit 104 calculates the propagation delay time between the satellite and the terminal 100 based on the distance information output from the location information acquisition unit 103 and the radio wave propagation speed. Then, the timing adjustment unit 104 adjusts the transmission timing based on one or more of the following: the reception timing of the signal transmitted from the base station 200, the calculated propagation delay time, a cell-wide timing adjustment value broadcast by the base station 200, and a timing adjustment value (e.g., TA value) of the terminal 100 notified by the base station 200. The timing adjustment can also vary depending on the channel and / or the transmitted signal. For example, the timing adjustment can also vary depending on PRACH, PUSCH, PUCCH (Physical Uplink Control Channel), and SRS (Sounding Reference Signal). Furthermore, examples of timing adjustments will be described below.

[0074] The wireless transmitter 105 performs D / A (Digital / Analog) conversion, up-conversion, and other transmission processing on the signal output from the PRACH generator 101 and the data signal output from the data generator 102. During the transmission timing adjusted by the timing adjustment unit 104, the wireless transmitter 105 transmits the wireless signal obtained through the transmission processing from the antenna 106 to the base station 200.

[0075] During the reception timing adjusted by the timing adjustment unit 104, the wireless receiving unit 107 receives the signal from the base station 200 via the antenna 106. The received signal may be, for example, a downlink signal from a PDCCH (Physical Downlink Control Channel) or PDSCH (Physical Downlink Shared Channel). Additionally, the received signal may contain data and / or control information. The wireless receiving unit 107 performs down-conversion and A / D (Analog / Digital) conversion on the received signal and outputs the processed signal to the demodulation / decoding unit 108.

[0076] The demodulation / decoding unit 108 performs demodulation and decoding processing on the signal output from the wireless receiving unit 107. For example, the demodulation / decoding unit 108 demodulates and decodes the PRACH response data signal. For example, if the information obtained from demodulation and decoding includes information related to transmission timing and reception timing, the demodulation / decoding unit 108 outputs information to the timing adjustment unit 104.

[0077] [Base station structure]

[0078] Figure 7 This is a block diagram illustrating an example of the structure of the base station 200 according to Embodiment 1. The base station 200 includes an antenna 201, a wireless receiver 202, a data receiver / processor 203, a PRACH detector 204, a timing control information generator 205, a data generator 206, a data transmitter / processor 207, and a wireless transmitter 208. The data receiver / processor 203, PRACH detector 204, timing control information generator 205, data generator 206, and data transmitter / processor 207 may be included in the control unit 209.

[0079] The wireless receiver 202 performs down-conversion and A / D conversion on the data signal and PRACH signal received from the terminal 100 via the antenna 201, and outputs the processed signal to the data receiving and processing unit 203 and the PRACH detection unit 204.

[0080] The data receiving and processing unit 203 performs demodulation / decoding processing on received data signals other than PRACH. Furthermore, the data receiving and processing unit 203 can perform channel estimation and timing estimation based on the received data signals. The data receiving and processing unit 203 outputs information related to the estimated timing to the timing control information generation unit 205.

[0081] The PRACH detection unit 204 performs correlation processing between the received PRACH preamble signal and the copy signal of the preamble signal, thereby detecting the PRACH preamble signal and estimating the transmission timing and reception timing. The copy signal of the preamble signal is a signal generated using a sequence number corresponding to the set preamble number and a cyclic shift amount.

[0082] Furthermore, the correlation processing in the PRACH detection unit 204 can be either a time-domain calculation of the delay distribution or a frequency-domain correlation processing (division processing) followed by an IFFT (Inverse Fast Fourier Transform) calculation of the delay distribution. The calculated delay distribution can be used to estimate the transmission timing and / or reception timing.

[0083] For example, the PRACH detection unit 204 outputs information related to the estimated transmission timing and / or reception timing to the timing control information generation unit 205. For example, the PRACH detection unit 204 calculates the difference between the reference timing of the base station 200 and the arrival timing of the received signal, and outputs the calculation result to the timing control information generation unit 205.

[0084] The timing control information generation unit 205 generates a TA command for the terminal 100 based on information output from the PRACH detection unit 204 and the data receiving and processing unit 203 (e.g., timing estimation results). The TA command can be of multiple types. Additionally, the timing control information generation unit 205 generates a cell-wide timing adjustment value. For example, it generates a cell-wide timing adjustment value based on at least one of the cell size formed by the satellite beam, the feeder link length, and the feeder link delay.

[0085] The data generation unit 206 generates downlink data signals such as user data, synchronization signals, system information (broadcast information), dedicated control information (e.g., RRC control information), and MAC (Medium Access Control) control information to be sent to the terminal 100. The data generation unit 206 outputs the generated downlink data signals to the data transmission processing unit 207.

[0086] The data transmission processing unit 207 encodes and modulates the downlink data signal output from the data generation unit 206 and the information output from the timing control information generation unit 205, and outputs the modulated signal to the wireless transmission unit 208.

[0087] The wireless transmitter 208 performs transmission processing such as D / A conversion, up-conversion, and amplification on the signal output from the data transmission processing unit 207, and transmits the wireless signal obtained through the transmission processing from the antenna 201.

[0088] [Example of timed adjustment]

[0089] Next, the timing adjustment in Embodiment 1 will be explained. Terminal 100 uses one or more timing adjustment values ​​to perform timing adjustment.

[0090] This example demonstrates two timing adjustments: a relatively fine-grained timing adjustment and a relatively coarse-grained timing adjustment.

[0091] In relatively fine-grained timing adjustments, terminal 100 performs transmission timing adjustments on a sample-by-sample basis. For example, the transmission timing is adjusted to ensure that base station 200 receives data within the CP length of PUSCH OFDM symbols or PRACH symbols. In relatively coarse-grained timing adjustments, terminal 100 performs transmission timing adjustments on a time slot and / or OFDM symbol-by-segment basis. For example, the transmission timing is adjusted to ensure that base station 200 receives data within a predetermined time slot or OFDM symbol range.

[0092] As timing adjustment values ​​for finer granular adjustments, the following values ​​can be listed as examples.

[0093] • Timing adjustment value calculated by the terminal based on location information

[0094] • Timing adjustment value calculated by the terminal using the first path tracking

[0095] • Timing adjustment value based on TA command 1 sent from the base station (Fine TA command)

[0096] In addition, the following values ​​can be listed as examples of timing adjustment values ​​for coarse granularity adjustment.

[0097] • Cell-specific timing adjustment values ​​(cell-specific TA offset) broadcast by the base station.

[0098] • Terminal-specific timing adjustment value (K) notified by the base station adj,UE )

[0099] • Based on the timing adjustment value of TA command 2 sent from the base station (coarse TA command)

[0100] Furthermore, in Implementation 2, the timing adjustment value calculated by the terminal using the first path tracking is explained among the timing adjustment values ​​described above.

[0101] Next, an example of timing control using the timing adjustment values ​​described above will be explained.

[0102] Figure 8 This is a diagram illustrating an example of a sequence diagram related to timing control in Embodiment 1. Figure 8The diagram shows examples of signals transmitted and received between terminal 100 (UE) and base station 200 (gNB) (or, channels used for transmitting and receiving signals), and timing adjustment values ​​used for signal transmission by the UE. The following section... Figure 8 Steps 101 (S101) to S109 will be explained.

[0103] <S101>

[0104] The base station (gNB) transmits SSB and SIB (System Information Block). SSB and SIB can be transmitted periodically. The SSB contains signals for synchronization and basic cell-specific control information (e.g., Master Information Block). The SIB contains cell-specific information for terminal access to the base station. Additionally, the SIB may contain information indicating satellite positions (e.g., satellite ephemeris). The SIB also contains the cell-specific TA offset and the time slot offset (K) indicating the time slot location for data allocation. offset,cell ).

[0105] <S102>

[0106] The terminal receives the SSB and SIB and sends a PRACH for initial access. Here, the terminal adjusts the timing of the PRACH transmission. For example, the terminal uses the cell-inherent TA offset value broadcast by the base station and a timing adjustment value calculated by the terminal based on location information to perform timing adjustment. The timing adjustment value based on location information is sometimes described as "TA based on GNSS / ephemeris" or "GNSS / ephemeris based TA".

[0107] Here, an example of calculating timing adjustment values ​​based on location information is explained. The terminal acquires the location information of a terminal using GNSS functions, etc. The terminal calculates the distance between the satellite and the terminal based on the stored or notified satellite location information and the terminal's own location information. Then, the terminal divides the calculated distance by the speed of radio wave propagation (e.g., 3 × 10⁻⁶). 8 [m / s]) is used to calculate the one-way propagation delay time. Twice the calculated propagation delay time corresponds to the round-trip time (RTT). The calculated round-trip propagation delay time is a timing adjustment value based on location information. Alternatively, the timing adjustment value based on location information can also be the calculated round-trip propagation delay time plus the processing delay time of the terminal and / or base station.

[0108] The TA value is obtained by adding the timing adjustment value based on location information to the cell's inherent TA offset value broadcast by the base station.

[0109] For example, the terminal uses equations (1), (2), and (3) to determine the value TA used for timing adjustment. final Furthermore, TA is determined by equation (1). final TA is determined by equation (2) NTN_offset and TA determined by equation (3) coarse For example, it can be in units of ns (nano second).

[0110] [Mathematical Expression 1]

[0111] TA final =(N TA +N TAoffset )×T c +TA NTN_offset (1)

[0112] TA NTN_offset =TA location +TA coarse (2)

[0113] TA coarse =(M offset,cell +M coarse )×10 6 / 2 μ (3)

[0114] The first term on the right-hand side of equation (1) above is the same as that in Rel.15NR. Furthermore, as stated in Section 4.1 of TS38.211V15.8.0, Tc = 0.509 ns, N TA It is a correction value based on the TA command sent from the base station. For example, in the case of PRACH transmission, N TA The value is zero. N TAoffset It is the offset value used for timing adjustments between different base stations. The TA value calculated by equation (1) is TA. final For example, the T described in section 4.3.1 of TS38.211V15.8.0 TA Synonymous, it is the same as the first term of equation (1) in the Rel.15NR specification plus the modification term TA for NTN represented by equation (2). NTN_offset The resulting value. Because the Rel.15NR specification can be reused, the extension to NTN can be achieved with fewer changes.

[0115] TA locationThis represents the round-trip propagation delay calculated based on location information. For example, TA location It can be represented by ns.

[0116] 10 of equation (3) 6 / 2 μ The term represents the time slot length as follows, that is, the time slot length in the case of the parameter μ representing the subcarrier spacing, and its unit can be, for example, ns. For example, for subcarrier spacings of 15kHz, 30kHz, 60kHz, 120kHz, and 240kHz, the parameter μ representing the subcarrier spacing is determined to be μ = 0, 1, 2, 3, and 4, respectively.

[0117] M offset,cell This is the cell-inherent TA offset. The cell-inherent TA offset, for example, represents the number of shifted time slots. When transmitting PRACH data using the offset described later, M... coarse Set to zero. Furthermore, instead of the number of time slots, these offsets can also represent the time offset (e.g., in milliseconds). Additionally, in the case of an offset representing time, this offset may not be correlated with 10, which represents the time slot length. 6 / 2 μ Multiplying terms together can also involve multiplying or dividing them by other coefficients.

[0118] The terminal advances the timing by the aforementioned TA value (TA) compared to the downlink reference reception timing of the SSB, etc. final In the timing sequence formed by the above signal, an uplink signal is sent.

[0119] Figure 9 This diagram illustrates an example of timing adjustment that uses the cell's inherent TA offset value and a timing adjustment value based on location information.

[0120] exist Figure 9 The example illustrates the transmit time slots of the DL (Deep Path) and the receive time slots of the UL (Upper Path) for a base station (gNB), and the receive time slots of the DL and the transmit time slots of the UL for a terminal (UE). Furthermore, Figure 9 The horizontal axis represents the time axis.

[0121] exist Figure 9 The image shows an example of an uplink signal transmitted in a transmission timing that is advanced by a TA value compared to the downlink reference receive timing. Figure 9 The TA value is represented by the sum of the cell's inherent offset value and the timing adjustment value based on location information.

[0122] in addition, Figure 9The “DL-UL timing difference due to feeder link delay” refers to the DL-UL timing difference caused by feeder link delay without using the cell’s inherent offset value.

[0123] By using the cell's inherent TA offset value, the base station can, for example, shorten the DL-UL timing difference caused by feeder link delay.

[0124] Due to the round-trip propagation delay in satellite communication, a DL-UL timing difference of hundreds of milliseconds (ms) can occur. In some base station implementations, managing this DL-UL timing difference can be challenging. As mentioned above, by using the cell-inherent TA offset, the DL-UL timing difference can be controlled to a manageable level (e.g., within 10 ms). Here, in the case of non-geostationary satellites such as LEO (Low Earth Orbit satellites), the propagation delay of the feeder link varies depending on the position of the non-geostationary satellite over time. Therefore, the minimum delay amount of the feeder link can be corrected. As long as the correction is sufficient to allow the base station to easily manage the DL-UL timing difference, by informing the terminal of coarse-grained values ​​such as time slot units and OFDM symbol units, the increase in notification overhead can be suppressed, which is suitable for long-latency satellite communication environments such as NTN environments.

[0125] <S103>

[0126] The base station receives the PRACH and detects the difference between the base station's reference timing and the PRACH reception timing. The base station determines the TA command 1 (for timing correction corresponding to the detected difference) to perform the correction. Figure 8 The system sends a PDSCH containing the determined TA command 1 (the detailed TA command in S103), and then sends a PDSCH containing the TA command 1. TA command 1 can be, for example, the same TA command as Rel.15NR. Additionally, the response sent to the terminal in S103 containing TA command 1 can also be called a "RACH response (RAR)".

[0127] The CP length of PRACH is set to be longer than the CP length of PUSCH. Therefore, even if PRACH is received within its CP length, the timing of receiving PUSCH sent by the terminal after PRACH at the base station may sometimes still exceed the CP length. In this step, the base station sends TA command 1 and controls the timing of the terminal's transmission to be within the CP length of PUSCH.

[0128] <S104>

[0129] The terminal transmits PUSCH within the time / frequency resources specified by the RAR. The time resources are offset from K, which is notified by the base station using SIB. offset,cell The terminal transmits in the time slot corresponding to the time slot numbered after the time slot number, during the timing that enables the base station to receive in that time slot. At this time, the terminal adjusts the timing according to the timing of the PRACH transmission and further according to the notified TA command 1. For example, the value of TA command 1 is used as N in equation (1). TA And the decision TA final Perform timed adjustments and send PUSCH.

[0130] In addition, the terminal can send timing information to the base station ( Figure 8 The TA value report. For example, the terminal can notify the TA value determined by using formula (1). final It can also notify the base station of a value that it does not know, namely TA. NTN_offset Or TA location In all cases, the notification is rounded to a coarse-grained value, such as a time slot length unit or an OFDM symbol length unit. For example, rounding or flooring operations can be used to convert it to a coarse-grained value. In the base station, this notification is used to control the allocation of time slots for PUSCH and / or HARQ-ACK (Hybrid Automatic Repeat request-Acknowledgement), so it can be a coarse-grained notification, such as a time slot unit. Using coarse-grained notifications reduces notification overhead. Alternatively, the terminal can notify location information obtained via GNSS instead of TA. location You can also notify them. location Both location information and location information. Alternatively, the location information can be specified in a way that minimizes the calculation error of the propagation delay, such as providing location information with a granularity of approximately 1 km, or location information with latitude and longitude values ​​limited to decimal places. Furthermore, information used for control purposes, such as handover, can be reused within the location information.

[0131] <S105>

[0132] The base station uses the PDSCH to transmit information for contention resolution in random access and / or RRC configuration information, etc. For example, the base station sends information including TA command 2 ( Figure 8The TA command 2 is a MACCE (Control Element) for the coarse TA command. TA command 2 is, for example, a timing adjustment command with granularity at the time slot unit level. The base station sets TA command 2 based on the TA value notified by the terminal in S104.

[0133] For example, the larger the TA value notified by the terminal to the base station, the longer the propagation delay. Therefore, the base station can set the TA command 2 notified to the terminal to a smaller value. In this case, the time slots allocated by the DCI for PUSCH and / or HARQ-ACK become time slots with later timing, i.e., time slots with larger time slot numbers. The terminal can then send PUSCH or HARQ-ACK after sufficient transmission preparation time from receiving the DCI or PDSCH.

[0134] On the other hand, the smaller the TA value notified by the terminal, the shorter the propagation delay. Therefore, TA command 2 can be set to a larger value. In this case, the time slot for PUSCH and / or HARQ-ACK is the time slot with an earlier timing, i.e., the time slot with a smaller time slot number. With a relatively short propagation delay, even if the timing is adjusted to an earlier value due to TA command 2, the terminal can still send PUSCH or HARQ-ACK after sufficient preparation time from receiving DCI or PDSCH. For example, K can be set to accommodate the propagation delay generated in the terminal located at the location farthest from the satellite within the cell. offset,cell In this case, the TA command 2 sent to the terminal located furthest from the satellite can be set to zero. Alternatively, the TA command 2 value can be set to a higher value for terminals located closer to the satellite. This control allows for lower latency transmission to terminals closer to the satellite.

[0135] In addition, in S104, when the terminal notifies the location information, the base station can estimate the TA value of the terminal based on the notified location information and set the TA command 2 in the same way as described above.

[0136] Additionally, TA command 2 can be sent within the RRC configuration information.

[0137] <S106>

[0138] In subsequent timing adjustments for PUSCH and HARQ-ACK transmissions, the terminal uses the TA value determined as follows (TA of equation (1)). final In this decision, by M of equation (2) coarse The TA value is set to be determined by the value notified by TA command 2.

[0139] Figure 10This diagram illustrates an example of timing adjustments using various TAs, including TA command 2.

[0140] exist Figure 10 The example illustrates the transmit time slots of the DL (Deep Path) and the receive time slots of the UL (Upper Path) for a base station (gNB), and the receive time slots of the DL and the transmit time slots of the UL for a terminal (UE). Furthermore, Figure 10 The horizontal axis represents the time axis.

[0141] Figure 10 The “coarse TA” refers to the TA notified by TA command 2. Figure 10 The "detailed TA" refers to the TA notified by TA command 1. It could be... Figure 10 The "TA based on GNSS / ephemeris" and "inherent TA offset of the cell" are respectively with Figure 9 The "TA based on GNSS / ephemeris" and "inherent TA offset of the cell" shown are the same.

[0142] in addition, Figure 10 The "cell-specific timing" refers to the timing of base station PUSCH reception in cases where transmissions such as msg3 are not performed using TA command 2. For example, considering the round-trip propagation delay of the terminal farthest from the satellite within a cell, a timing is set so that even the farthest terminal can transmit. On the other hand, because the timing is tailored to the farthest terminal, it introduces additional delays for terminals closer to the satellite. Figure 10 As shown, by using the coarse TA notified by TA command 2, the transmission and reception timing of PUSCH can be advanced compared to the inherent timing of the cell.

[0143] Here, the granularity of TA command 2 can also be used to adjust M in equation (2). coarse The conversion can be performed. For example, if the granularity is OFDM symbol units, it can also be converted to OFDM symbol unit values ​​by dividing the value notified by TA command 2 (the value of the slot unit) by the number of OFDM symbols per slot, i.e., 14.

[0144] <S107, S108>

[0145] If the satellite and / or terminal have moved more than a threshold distance, the terminal recalculates the propagation delay based on the GNSS position information and the position information from the satellite ephemeris, and adjusts the TA in equation (1). location Update and send uplink data. Additionally, TA... location The update is not limited to situations where the satellite and / or terminal have moved above a threshold; for example, it could also be performed at a predetermined interval. Alternatively, it could be performed both when the satellite and / or terminal have moved above a threshold and when TA is executed. locationThe updates are also executed on a predetermined schedule. location Update.

[0146] TA location The frequency and period of TA updates, as well as the threshold for movement distance, can also be notified by the base station. Alternatively, instead of the movement distance threshold, the change in TA value accompanying movement can be notified. Furthermore, a predetermined value can be used as the TA. location The frequency and cycle of updates, and the threshold for the moving distance.

[0147] Furthermore, if the round-trip propagation delay changes by a predetermined value or more (e.g., equivalent to more than half a time slot), the terminal can, as in S104, notify the base station of the corrected timing value and / or location information. If the round-trip propagation delay does not change by a predetermined value or more, the terminal can send user data without notifying the corrected timing value and / or location information. Here, for example, when notifying the terminal's location information, even if the propagation delay changes due to satellite movement, for a stationary terminal or a terminal whose movement is less than a threshold, the base station can still grasp the change in TA based on the previously notified terminal's location information. Therefore, frequent notifications of the terminal's location information can be avoided, thereby reducing the overhead of location information notification.

[0148] <S109>

[0149] If the round-trip propagation delay of the terminal changes by more than a specified value (e.g., more than 1 time slot), the base station sends TA command 2 to change the allocated time slots of the terminal's PUSCH and / or HARQ-ACK.

[0150] As illustrated in the sequence diagram above, the terminal performs both fine-grained and coarse-grained timing adjustments. Additionally, the terminal performs different timing adjustments based on the channel and / or the transmitted signal.

[0151] Furthermore, the information notified to the terminal by the base station in the above sequence diagram is one example, and this disclosure is not limited thereto. For example, instead of the TA command, the information notified by the TA command 2 in the above S105 and S109 can also be provided by the offset value (K) for the allocated time slot. adj,UE Notification. Offset value (K) adj,UE For example, it is a timing adjustment value specific to the terminal.

[0152] In the offset value (K) adj,UE In the event of notification, M in equation (3) can be... coarse Set to zero. Additionally, the offset value (K) adj,UE In the event of a notification, the terminal interprets the allocated time slot of PUSCH as "n+K2+K". offset,cell-K adj,UE Here, n is the time slot in which the DCI allocating the PUSCH is sent, and K2 is the value notified by the DCI. For example, K2 sets the time required from receiving the DCI to preparing to send the PUSCH, and / or the time until the next uplink time slot available for transmission. Offset value (K adj,UE It can also take negative values.

[0153] Figure 11 This indicates that K was used. adj,UE A diagram illustrating an example of timed adjustments to information.

[0154] exist Figure 11 The example illustrates the transmit time slots of the DL (Deep Path) and the receive time slots of the UL (Upper Path) for a base station (gNB), and the receive time slots of the DL and the transmit time slots of the UL for a terminal (UE). Furthermore, Figure 11 The horizontal axis represents the time axis.

[0155] exist Figure 11 In this process, the terminal determines the allocation slot of PUSCH to be shifted by K from the slot that serves as the "cell's inherent timing". adj,UE The time slot after the offset value.

[0156] In addition, Figure 11 In the middle, although the use of K is shown adj,UE This is an example of using the offset value to determine the allocation slot for PUSCH, but this disclosure is not limited to this. For example, K can be applied. adj,UE The offset value is used to determine the transmission slot for HARQ-ACK and / or SRS. When the offset value is applied to HARQ-ACK transmission, n can be the PDSCH slot to which HARQ-ACK is intended. Conversely, when the offset value is applied to SRS transmission, n can be the DCI slot indicating SRS transmission. Because instead of the TA command, the notification indicates that from K... offset,cell The offset information is calculated, thus reducing the amount of information required for notification. The granularity of the notification offset can be in time slot units or OFDM symbol units. By setting it to OFDM symbol units, finer timing control can be achieved. Alternatively, K can be omitted for certain channels and / or signals. adj,UE The offset value can also be different for certain channels and / or signals.

[0157] In this embodiment 1, in addition to fine-grained timing control, coarse-grained timing control is also performed. This helps to suppress the increase in notification overhead and enables terminal transmission timing control suitable for satellite communication environments with long propagation times and large differences in propagation delays between terminals.

[0158] (Implementation Method 2)

[0159] In this second embodiment, based on the first embodiment, a timing adjustment based on path tracking is further performed.

[0160] [Terminal Structure]

[0161] The structure of the terminal in this embodiment 2 can be the same as that of the terminal 100 shown in embodiment 1. However, the processing in the timing adjustment unit 104 of the terminal 100 shown in embodiment 1 is added.

[0162] The timing adjustment unit 104 tracks the reception timing of the SSB, PDCCH, or PDSCH received by the wireless receiver 107 and calculates a timing adjustment value corresponding to the change in reception timing. If multiple paths (e.g., delayed waves) are detected, the timing of the first path can be set as the reception timing for tracking. Next, the timing adjustment unit 104 performs timing adjustment using one or more timing adjustment values, including the calculated path-tracking-based timing adjustment value and the timing adjustment value shown in Embodiment 1.

[0163] [Example of timed adjustment]

[0164] Next, the timing adjustment in this embodiment 2 will be explained.

[0165] For example, the terminal uses equations (4) and (5) to determine the value TA used for timing adjustment. final Furthermore, TA is determined by equation (4). final For example, it can be measured in nanoseconds (ns).

[0166] [Mathematical Expression 2]

[0167] TA final =(N TA +N TAoffset )×T c +TA NTN_offset (4)

[0168] TA NTN_offset =TA location +TA path +TA coarse (5)

[0169] Furthermore, explanations regarding the parameters in equations (4) and (5) that are the same as those in equations (1), (2), and (3) are omitted. Although equation (4) is the same as equation (1), the second term on the right-hand side is represented by equation (5). On the right-hand side of equation (5), compared to the parameters on the right-hand side of equation (2), a new parameter TA is added. path TA path It is a value that is adjusted periodically based on path tracing.

[0170] The terminal can distinguish between instances that perform location-based timing adjustment and instances that perform both location-based and path-tracking-based timing adjustment based on the terminal's uplink transmission channel and / or transmission timing. For example, in instances performing location-based timing adjustment (in other words, instances that do not utilize path tracking for timing adjustment), the TA... path The value can be set to zero. Alternatively, control information from the base station can be used to instruct the terminal which of the two instances to use. Or, rules can be predefined, and the terminal can distinguish which instance to use based on those rules.

[0171] For example, the following shows an example of applying two instances.

[0172] An example of performing location-based timing adjustments, i.e., not performing path-tracking-based timing adjustments, is the following example.

[0173] ·PRACH sent

[0174] • SRS transmission

[0175] • The initial transmission after waking from a DRX (Discontinuous Reception) sleep interval (long sleep and / or short sleep)

[0176] • The initial transmission after the TA timer expires

[0177] • Sending in idle or inactive state

[0178] In addition, examples of timing adjustments based on location information and timing adjustments based on path tracking are as follows.

[0179] • RRC connected (RRC_CONNECTED) status

[0180] • Subsequent transmissions after the second wake-up from hibernation

[0181] Next, an example of timing control using the timing adjustment values ​​described above will be explained.

[0182] Figure 12 This is a diagram illustrating an example of a sequence diagram related to timing control in Embodiment 2. Figure 12 In, with Figure 8 Similarly, examples are shown of signals transmitted and received between terminal 100 (UE) and base station 200 (gNB) (or, channels used for transmitting and receiving signals), and of timing adjustment values ​​used by the UE when transmitting signals. Furthermore, in Figure 12In China, sometimes with Figure 8 The same processing is indicated by the same reference numerals in the accompanying drawings, and the description is omitted.

[0183] <S201>

[0184] The base station (gNB) transmits SSB and SIB. SSB and SIB can be transmitted periodically. The SSB contains signals for synchronization and basic cell-specific control information. The SIB contains cell-specific information for terminal access to the base station. Additionally, the SIB may contain information indicating satellite positions (e.g., satellite ephemeris). The SIB also contains the cell-specific TA offset.

[0185] <S204 and S205>

[0186] The terminal sends (PRACH) Figure 12 In step S102), the timing adjustment value TA based on location information is calculated. location During the process, the SSB receive timing (first path timing) is stored. Then, the terminal receives the SSB, PDCCH, or PDSCH at certain intervals and monitors changes in the first path timing. When the change reaches a certain level, the terminal changes (updates) the transmit timing. The amount of timing change for the path is set as Δ. path In this case, the terminal decides to be TA. path =2×Δ path In equations (4) and (5), the terminal uses TA respectively. path The timing adjustment value determines TA final Use the determined TA final Perform timed adjustments and send PUSCH.

[0187] Additionally, the terminal can update the timing if the change in the path's received timing reaches or exceeds a threshold. The interval for updating the TA value, and / or the threshold for determining whether to update the TA value, can be specified by the base station or predetermined.

[0188] Similar to implementation method 1, the terminal notifies the base station of timing information (e.g., at least one of TA value and location information). Figure 12 (TA value report). For example, the terminal can notify the TA. location With TA path The sum. Alternatively, similar to implementation 1, the value can be rounded to a coarse-grained value such as a slot length unit or an OFDM symbol length unit before notification.

[0189] When there is no data to be communicated, the terminal will go into sleep mode. The sleep mode can be performed in the same manner as Rel.15NR described in TS38.821. Furthermore, the terminal's sleep mode is not limited to sleep mode in the absence of communication data; for example, it can also be replaced by sleep mode activated by the CPU (Central Processing Unit).

[0190] <S206>

[0191] The terminal obtains its location information during its initial transmission after waking up (e.g., a PUSCH transmission). If the satellite's location has changed, the terminal uses the updated satellite location information. Next, the terminal performs a TA (Targeting Acquisition) test. location The system performs updates, timed adjustments, and PUSCH transmission. Additionally, the terminal will send TA here. path Set (reset or clear) to zero.

[0192] <S207>

[0193] After a terminal wakes up from sleep mode, since the position of the satellite or the terminal may have changed, it can also notify the base station of timing information (e.g., TA value). Furthermore, whether to notify the base station of timing information can be specified by the base station based on the type of satellite (geostationary satellite, non-geostationary satellite, etc.) (using SIB for notification), or it can be set for each terminal based on its movement speed and / or category, and notification can be sent to each terminal individually.

[0194] <S208 and S209>

[0195] Similar to S204 and S205, the terminal uses path tracking to track the TA. path Update. Additionally, the terminal may not need to perform an update here. location Update.

[0196] As illustrated in the sequence diagram above, the terminal performs both fine-grained and coarse-grained timing adjustments. Additionally, the terminal performs different timing adjustments based on the channel and / or the transmitted signal. Furthermore, the terminal utilizes path tracking to determine the timing adjustment (TA). path and using TA path The timed adjustment value is adjusted periodically.

[0197] Furthermore, although examples are shown such that the terminal sleeps in S206 and wakes up in S207, this disclosure is not limited to these examples. For instance, the same applies to recovering from an idle or inactive state, or from a state where the TA timer has expired. The TA timer can also be the time alignment timer described in TS38.321V15.8.0.

[0198] Furthermore, in the sequence diagram above, similar to Embodiment 1, K can be used. offset,cell K adj,UE TA command 2 (coarse TA), K can also be omitted. offset,cell K adj,UE The TA command 2 (coarse TA) can also be used, or a specified value can be used. The base station can explicitly notify the user of the disabling, or it can notify the user of the specified value.

[0199] In this second embodiment, in addition to fine-grained timing control, coarse-grained timing control is also performed. This suppresses the increase in notification overhead and enables terminal transmission timing control suitable for satellite communication environments with prolonged propagation times and large differences in propagation delays between terminals. Furthermore, in this second embodiment, by using path-tracking-based timing adjustment values ​​in the timing control, appropriate terminal transmission timing control can be achieved.

[0200] When timing adjustments are based on terminal and satellite location information (e.g., GNSS / ephemeris location information), errors will occur relative to the actual propagation path in non-line-of-sight environments (e.g., environments where reflected or diffracted waves arrive without a direct wave). Although this error can be corrected using TA commands sent from the base station, whenever the terminal or satellite position changes, if timing adjustments based on GNSS / ephemeris location information are performed again, errors will recur, requiring correction using TA commands once more.

[0201] Therefore, by performing path tracking-based corrections instead of frequent timing adjustments based on GNSS / ephemeris position information, timing control accuracy can be maintained, and frequent TA commands from the base station can be avoided. Furthermore, timing accuracy can be improved and overhead reduced. Additionally, in cases of prolonged periods without signal reception, such as during sleep periods, or the initial transmission after a partial functional shutdown, the likelihood of failure to perform path tracking is high; therefore, implementing timing adjustments based on GNSS / ephemeris position information can maintain a certain level of timing accuracy.

[0202] (Implementation Method 3)

[0203] The structure of the terminal and base station in this embodiment can be the same as that of the terminal 100 and base station 200 shown in Embodiment 1. However, the timing adjustment-related operations of the terminal 100 and base station 200 shown in Embodiment 1 are different from those in this embodiment.

[0204] In this embodiment, in addition to TA, timing adjustment is also performed using "Koffset", which specifies the timing of the transmission time slot.

[0205] For example, in Figure 4 In the terminal 100 shown, the control unit 109 uses a first offset (e.g., K) based on information related to control signals (e.g., DCI or PDCCH) used for scheduling. offset,cell ) and a second offset shorter than the first offset (e.g., K) offset,UE One of the following controls the uplink transmission timing (e.g., transmission slot timing). The wireless transmission unit 105 performs uplink transmission based on the control of the uplink transmission timing.

[0206] Additionally, for example in Figure 5 In the base station 200 shown, the control unit 209 uses a first offset (e.g., K) based on information related to control signals (e.g., DCI or PDCCH) used for scheduling. offset,cell ) and a second offset shorter than the first offset (e.g., K) offset,UE One of the following is used to control the uplink reception timing (e.g., receive time slot timing). The wireless receiver 202 performs uplink reception based on the control of the uplink reception timing.

[0207] For example, a cell-specific value, "K", can be set. offset,cell ", or a UE-specific value, i.e., "K" offset,UE "As Koffset. For example, terminal-specific K." offset,UE Compared to the inherent K of the community offset,cell short.

[0208] For example, SIB can be used to transfer the cell's inherent K offset,cell The notification is sent to terminal 100. Terminal 100 can, for example, use the cell's inherent K... offset,cell The decision will be made until the terminal is notified of the dedicated K. offset,UE The following are the transmission slots sent up to this point (e.g., Koffset = K). offset,cellThis transmission can be, for example, a PUSCH or PUCCH transmission for MSG3 during initial access, or an ACK / NACK (e.g., also known as "HARQ-feedback") transmission for PDSCH used for MSG4. Additionally, terminal 100 can, for example, transmit a terminal-specific K... offset,UE Then, use K offset,UE To determine the transmission slot of PUSCH or PUCCH (e.g., Koffset = K offset,UE ).

[0209] Alternatively, for example, the terminal-specific K can be transmitted via at least one of the following: terminal-specific RRC messages, MAC CE, and DCI. offset,UE Notify terminal 100. Additionally, relative to K... offset,cell The relative value (or difference) of K relative to the last notification offset,UE The relative value (or difference) of the value can also be used as the terminal-specific K. offset,UE The relevant information is then communicated to terminal 100.

[0210] Alternatively, similar to implementation method 1, as at least one of the satellite and the terminal moves, the terminal-specific K can be appropriately adjusted. offset,UE Update accordingly. For example, in the case of a GEO (Geostationary Earth Orbit) satellite, because the satellite is stationary, it can move along with the terminal 100, providing dedicated K-band communication to the terminal. offset,UE Perform an update. In this case, the terminal-specific K... offset,UE Since the update frequency is relatively low, it is appropriate to use RRC messages for notification. On the other hand, for example in the case of LEO, it is possible to send K-series messages to the terminal along with the high-speed movement of the satellite. offset,UE Perform an update. In this case, the terminal-specific K... offset,UE Since the update frequency is relatively high, MAC CE or DCI, which can notify and respond in a shorter time than RRC messages, can be used to send terminal-specific K... offset,UE The relative value (e.g., difference) is notified to terminal 100. For example, by notifying the terminal's dedicated K. offset,UE The relative value of Koffset can reduce the amount of notification information and notify Koffset more quickly.

[0211] Additionally, when using DCI to notify the terminal's dedicated K... offset,UE In this case, in addition to DCI for terminal-specific use, group-wide DCI (e.g., DCI format 2_0, etc.) can also be used.

[0212] Here, during terminal-specific notifications, due to errors in receiving the notification information or errors in the ACK / NACK signals for the notification information, communication between base station 200 and terminal 100 regarding K... offset,UE The identification of values ​​may be inconsistent. For example, when used as K... offset,UE In the case of notification information about relative values ​​(or differences), for the previous value where there may be identification discrepancies between base station 200 and terminal 100, the difference relative to that value will be notified to terminal 100. Therefore, it is difficult to make the identification between base station 200 and terminal 100 consistent again.

[0213] Therefore, in this embodiment, the terminal 100 and the base station 200, for example, use the cell-specific K based on information related to the DCI (or PDCCH) used for scheduling. offset,cell and terminal-specific K offset,UE One of them is used to control the timing of uplink signal transmission and reception. For example, in cases where scheduling is performed by a specific method or a specific DCI, even in terminal-specific K... offset,UE When notified to terminal 100, terminal 100 and base station 200 will also use the cell's inherent K. offset,cell Instead of using terminal-specific K offset,UE .

[0214] An example of timing control using the above-described transmission time slot timing (or timing adjustment value) will be explained.

[0215] Figure 13 This is an example of a flowchart illustrating the control related to the transmission slot timing of uplink signals (e.g., PUSCH or PUCCH) in the terminal 100 of this embodiment. Hereinafter, [further details will be provided]. Figure 13 Steps 301 (S301) to S305 will be explained.

[0216] <S301>

[0217] Terminal 100, for example, receives the cell's inherent K offset,cell The inherent K of the community offset,cell For example, it can be included in SIB.

[0218] <S302>

[0219] Terminal 100, for example, determines whether it has received the terminal-specific K. offset,UE For example, it could be in Figure 8 In the timing of receiving PDSCH (msg4) (processing in S105) or receiving PDSCH (S109) as shown, the base station 200 transmits the terminal-specific K... offset,UEThe terminal 100 is notified. Additionally, for example, during initial access transmission and reception, or in cases of small cell size (where the cell size is below the threshold), sometimes the terminal-specific K is not set (in other words, notified) by the base station 200. offset,UE Regarding scheduling data (e.g., the case of DCI for receiving uplink or downlink data allocation).

[0220] <S303>

[0221] Upon receiving the terminal-specific K offset,UE In the case of (S302: "Yes"), terminal 100 determines, for example, whether the transmission of PUSCH or PUCCH has been scheduled by a specific method or a specific DCI. Examples of specific methods and specific DCIs will be described below.

[0222] <S304, S305>

[0223] Without receiving the terminal-specific K offset,UE In the case of (S302: "No"), or in the case where the transmission of PUSCH or PUCCH has been scheduled by a specific method or a specific DCI (S303: "Yes"), terminal 100, for example based on the cell's inherent K offset,cell This determines the transmission time slot.

[0224] On the other hand, upon receiving the terminal-specific K offset,UE (S302: "Yes"), but if the transmission of PUSCH or PUCCH is not scheduled by a specific method and a specific DCI (S303: "No"), terminal 100, for example, based on terminal-specific K offset,UE This determines the transmission time slot.

[0225] As illustrated in the flowchart above, even when receiving the terminal-specific K... offset,UE In the case of scheduling by a specific method or a specific DCI, terminal 100 will still be based on the cell's inherent K. offset,cell This determines the transmission time slot.

[0226] Next, methods 1 through 5 will be explained as specific methods and specific examples of DCI.

[0227] <Method 1>

[0228] In method 1, the offset Koffset used to determine the transmission time slot is determined, for example, based on the DCI format. For instance, if the DCI format used for scheduling is DCI format 0_0 or DCI format 1_0, terminal 100 uses the cell-specific Koffset. offset,cellIn other words, in method 1, a specific DCI is, for example, DCI format 0_0 and DCI format 1_0.

[0229] Furthermore, specific DCI formats such as DCI format 0_0 and DCI format 1_0 can be, for example, DCI formats that do not support MIMO (Multiple-Input Multiple-Output), DCI formats with limitations on resource allocation notifications such as notifications of consecutive resource blocks, DCI formats used for scheduling of cell-wide PDSCH, or DCI formats with a small number of bits (e.g., fewer than the threshold). Such DCI formats may be used for transmissions with fewer bits or low overhead transmissions.

[0230] On the other hand, DCI formats such as DCI format 0_1, DCI format 0_2, DCI format 1_1, or DCI format 1_2, which are different from the specific DCI mentioned above, can provide more flexible and less restrictive scheduling information. For example, they can be DCI formats used for high-speed data communication or high-reliability low-latency data communication.

[0231] For example, in the case of scheduling by DCI format 0_0 or DCI format 1_0, terminal 100 is based on the cell's inherent K offset,cell The transmission time slot is determined based on the DCI format 0_1, DCI format 0_2, DCI format 1_1, or DCI format 1_2. On the other hand, for example, in the case of scheduling by DCI format 0_1, DCI format 0_2, DCI format 1_1, or DCI format 1_2, terminal 100 uses terminal-specific K... offset,UE This determines the transmission time slot.

[0232] For example, regarding PUSCH, terminal 100 can use slot n+K2+K. offset,cell The transmission slot of PUSCH, scheduled by DCI format 0_0, is determined and determined via slot n+K2+K. offset,UE This determines the transmission slot of the PUSCH, scheduled by either DCI format 0_1 ​​or DCI format 0_2. Here, slot n is the slot number notified by DCI.

[0233] Alternatively, for example, regarding PDSCH, terminal 100 can use slot n'+K1+K offset,cell The transmission slot for HARQ feedback (or ACK / NACK) of PDSCH scheduled by DCI format 1_0 is determined, and is determined by slot n'+K1+K. offset,UE This determines the transmission slot for the HARQ feedback (or ACK / NACK) of the PDSCH scheduled by DCI format 1_1 or DCI format 1_2. Here, slot n' is the slot number where the PDSCH was transmitted.

[0234] The decision of this transmission time slot, for example, even if a terminal-specific K is generated between base station 200 and terminal 100, is made possible by this decision. offset,UE Even with a deviation in the value recognition, terminal 100 can still rely on the cell's inherent K. offset,cell This allows communication to continue.

[0235] Alternatively, for example, if no PUSCH or HARQ feedback (e.g., PUCCH) is detected from terminal 100 within a certain period, base station 200 determines that an identification deviation has occurred between base station 200 and terminal 100, and base station 200 determines this based on DCI format 0_0 or DCI format 1_0 (in other words, the cell's inherent K). offset,cell And communicate with terminal 100.

[0236] For example, base station 200 could use DCI format 0_0 or DCI format 1_0 communication to transmit the terminal-specific K offset,UE The value is then communicated to terminal 100 again, thereby enabling base station 200 and terminal 100 to communicate regarding K. offset,UE The values ​​are consistent. For example, when K is notified using an RRC message. offset,UE In this case, terminal 100 and base station 200 can also reset the accumulated value of differential information previously notified by MACCE or DCI. This enables communication between base station 200 and terminal 100 regarding K. offset,UE The values ​​are consistent.

[0237] For example, using DCI format 0_0 or 1_0 based on cell-specific K offset,cell The communication is sufficient to notify K, which is used to make the identification between terminal 100 and base station 200 consistent. offset,UE Furthermore, in identifying instances where no deviation has occurred (e.g., typical instances), terminal 100 can, for example, use DCI formats 0_1, 0_2, 1_1, 1_2, etc., which allow for more flexible scheduling, to perform terminal-specific K-series scheduling with lower latency. offset,UE Sending.

[0238] <Method 2>

[0239] In method 2, the offset Koffset used to determine the transmission slot is determined, for example, based on the category of the search space (SS) used for scheduling (e.g., DCI transmission). For example, if the search space used for DCI transmission for scheduling is a common search space shared by multiple terminals, terminal 100 uses the cell-specific Koffset. offset,cellIn other words, in method 2, a specific method is, for example, sending a DCI (or PDCCH) containing scheduling information in a general search space.

[0240] For example, when scheduled by DCI (or PDCCH) transmitted in the general search space, terminal 100 is based on the cell-specific K. offset,cell The transmission time slot is determined based on the terminal's specific K. On the other hand, for example, when scheduled by a DCI (or PDCCH) transmitted in the UE-specific search space, terminal 100 uses the UE-specific K... offset,UE This determines the transmission time slot.

[0241] For example, regarding PUSCH, terminal 100 can use slot n+K2+K. offset,cell The transmission slot of the PUSCH, scheduled by the DCI sent in the general search space, is determined and determined by slot n+K2+K. offset,UE The transmission slot for the PUSCH, scheduled by the DCI sent in the terminal-dedicated search space, is determined. Here, slot n is the slot number that notifies the DCI.

[0242] Alternatively, for example, regarding PDSCH, terminal 100 can use slot n'+K1+K offset,cell The transmission slot for the HARQ feedback (or ACK / NACK) of the PDSCH scheduled by the DCI sent in the general search space is determined, and is determined by slot n'+K1+K. offset,UE This determines the transmission slot for the HARQ feedback (or ACK / NACK) of the PDSCH scheduled by the DCI sent in the terminal-dedicated search space. Here, slot n' is the slot number where the PDSCH was transmitted.

[0243] The decision of this transmission time slot, for example, even if a terminal-specific K is generated between base station 200 and terminal 100, is made possible by this decision. offset,UE Even with a deviation in the value recognition, terminal 100 can still rely on the cell's inherent K. offset,cell And thus communication continues. Here, in normal communication, the DCI used for scheduling for terminal 100 can, for example, be notified to terminal 100 in a terminal-specific search space with a greater number of candidate CCEs (Control Channel Element) or blind decoding attempts (e.g., more candidate resources for mapping DCIs). In contrast, in the case of generating terminal-specific K... offset,UEIn the case of identification deviation of the value, the DCI used for scheduling is notified to the terminal 100 in a general search space with fewer candidate CCEs or fewer blind decoding times (e.g., fewer candidate resources for mapping DCI). Thus, in normal communication, the range of candidate resources that can be used to notify scheduling information is not narrowed, and scheduling limitations can be eliminated as much as possible.

[0244] Alternatively, for example, if no PUSCH or HARQ feedback (e.g., PUCCH) is detected from terminal 100 within a certain period, base station 200 determines that an identification deviation has occurred between base station 200 and terminal 100, and uses the universal search space (in other words, the cell's inherent K) to perform the search. offset,cell The base station 200 sends a DCI signal, thereby communicating with the terminal 100. For example, the base station 200 could use communication via a universal search space to send a terminal-specific K... offset,UE The value is then communicated to terminal 100 again, so that base station 200 and terminal 100 communicate with each other regarding K. offset,UE The values ​​are consistent.

[0245] <Method 3>

[0246] In method 3, the offset Koffset used to determine the transmission time slot is determined, for example, based on the control channel transmission resources (e.g., CORESET: Control Resource Set) used for scheduling (e.g., DCI transmission). For example, if the CORESET used for DCI transmission for scheduling is a specific CORESET, terminal 100 uses the cell-specific Koffset. offset,cell In other words, in method 3, a specific method, for example, is to send a DCI (or PDCCH) containing scheduling information in a specific CORESET.

[0247] As an example, a specific CORESET can be CORESET0. For instance, the resources of CORESET0 can be resources broadcast by the SIB and shared by multiple terminals within the cell. For example, a CORESET different from CORESET0 can be a resource configured for terminal-specific use. Furthermore, the number of a specific CORESET is not limited to 0. Additionally, the number of specific CORESETs is not limited to one.

[0248] For example, when scheduled by a DCI (or PDCCH) sent in CORESET0, terminal 100 is based on the cell-specific K. offset,cellThe transmission time slot is determined by this. On the other hand, for example, when scheduled by a DCI (or PDCCH) transmitted in a different CORESET than CORESET0, terminal 100 determines the transmission time slot based on terminal-specific K. offset,UE This determines the transmission time slot.

[0249] For example, regarding PUSCH, terminal 100 can use slot n+K2+K. offset,cell The transmission slot of the PUSCH, scheduled by the DCI sent in CORESET0, is determined and determined via slot n+K2+K. offset,UE The transmission slot for the PUSCH scheduled by the DCI, which is transmitted in a different CORESET than CORESET0, is determined. Here, slot n is the slot number that notifies the DCI.

[0250] Alternatively, for example, regarding PDSCH, terminal 100 can use slot n'+K1+K offset,cell The transmission slot for the HARQ feedback (or ACK / NACK) of the PDSCH scheduled by the DCI sent in CORESET0 is determined, and transmitted via slot n'+K1+K. offset,UE This determines the transmission slot for the HARQ feedback (or ACK / NACK) of the PDSCH scheduled by the DCI sent in a different CORESET than CORESET0. Here, slot n' is the slot number where the PDSCH was sent.

[0251] The decision of this transmission time slot, for example, even if a terminal-specific K is generated between base station 200 and terminal 100, is made possible by this decision. offset,UE Even with a deviation in the value recognition, terminal 100 can still rely on the cell's inherent K. offset,cell And thus communication continues. Here, normally, the DCI used for scheduling for terminal 100 can be notified to terminal 100, for example, in a terminal-specific CORESET (here, a CORESET different from CORESET0) that allows for more flexible resource configuration. In contrast, in the case of generating a terminal-specific K... offset,UE In the event of a discrepancy in the value of the DCI used for scheduling, the DCI used for scheduling is notified to terminal 100 in CORESET0 (e.g., a CORESET common to multiple terminals). As a result, the range of resources available for notification of scheduling information in normal times is not reduced, and thus the impact on notification of scheduling information in normal times can be reduced.

[0252] Alternatively, for example, if no PUSCH or HARQ feedback (e.g., PUCCH) is detected from terminal 100 within a certain period, base station 200 determines that an identification deviation has occurred between base station 200 and terminal 100, and uses CORESET0 (in other words, the cell's inherent K) offset,cell The base station 200 sends a DCI signal to the terminal 100, thereby communicating with the terminal 100. For example, the base station 200 could use CORESET0 communication to send the terminal-specific K... offset,UE The value is then communicated to terminal 100 again, so that base station 200 and terminal 100 communicate with each other regarding K. offset,UE The values ​​are consistent.

[0253] <Method 4>

[0254] In method 4, the offset Koffset used to determine the transmission time slot is determined, for example, based on the scheduling method. For instance, when the scheduling method used for scheduling (DCI, or PDCCH) is SPS (Semi-persistent scheduling), terminal 100 uses the cell-specific Koffset. offset,cell In other words, in method 4, the specific scheduling method is, for example, SPS.

[0255] For example, terminal 100 could use slot n'+K1+K offset,cell The transmission slot for HARQ feedback (or ACK / NACK) of PDSCH scheduled by SPS is determined, and this is done via slot n'+K1+K. offset,UE This determines the transmission slot for HARQ feedback (or ACK / NACK) of PDSCH scheduled by a method different from SPS. Here, slot n' is the slot number where the PDSCH was transmitted.

[0256] The decision of this transmission time slot, for example, even if a terminal-specific K is generated between base station 200 and terminal 100, is made possible by this decision. offset,UE Even with a deviation in the value recognition, terminal 100 can still rely on the cell's inherent K. offset,cell This allows communication to continue.

[0257] For example, terminal-specific K offset,UE The more frequently updates are made in conjunction with the movement of LEO satellites, the higher the overhead becomes. Here, SPS can reduce PDCCH overhead for periodic services or small data transmissions. Therefore, according to method 4, the terminal-specific K is replaced... offset,UE The inherent K of the community offset,cell Used for HARQ feedback for PDSCH scheduled by SPS, thus eliminating the need for frequent terminal-specific K...offset,UE Updating can reduce costs.

[0258] <Method 5>

[0259] In method 5, the offset Koffset used to determine the transmission slot is determined, for example, based on the HARQ process (retransmission process) allocated to the PUSCH or PDSCH. For example, terminal 100 selects the cell-specific Koffset based on the HARQ process number notified by the DCI used for scheduling. offset,cell and terminal-specific K offset,UE One of them. In method 5, for example, a specific method is to send data by assigning a specific HARQ process to PUSCH or PUCCH.

[0260] As an example, a specific HARQ process is set as HARQ process number 0. This specific HARQ process could also be a HARQ process assigned by the SPS as described in method 3 (e.g., including HARQ process number 0). Furthermore, the HARQ process number can be notified to terminal 100, for example, by DCI. For instance, in the case of HARQ process number 0, terminal 100 selects the cell-specific K... offset,cell .

[0261] For example, when assigned HARQ process number 0, terminal 100 uses the cell's inherent K... offset,cell The time slot for transmission is determined. On the other hand, for example, if a HARQ process number different from HARQ process number 0 is assigned, terminal 100 uses a terminal-specific K... offset,UE The time slot for transmission is determined.

[0262] For example, regarding PUSCH, terminal 100 can use slot n+K2+K. offset,cell It was determined that the PUSCH, which was assigned HARQ process number 0, would send its transmission slot via slot n+K2+K. offset,UE This determines the transmission slot for the PUSCH that has been assigned a HARQ process number different from HARQ process number 0. Here, slot n is the slot number that notified the DCI.

[0263] Alternatively, for example, regarding PDSCH, terminal 100 can use slot n'+K1+K offset,cell Determine the transmission slot for the HARQ feedback (or ACK / NACK) of the PDSCH assigned HARQ process number 0, and slot n'+K1+K offset,UEThis determines the transmission slot for the HARQ feedback (or ACK / NACK) of the PDSCH that has been assigned a HARQ process number different from HARQ process number 0. Here, slot n' is the slot number where the PDSCH was transmitted.

[0264] The decision of this transmission time slot, for example, even if a terminal-specific K is generated between base station 200 and terminal 100, is made possible by this decision. offset,UE Even with a deviation in the value recognition, terminal 100 can still rely on the cell's inherent K. offset,cell This allows communication to continue. For example, base station 200 could use HARQ process number 0 to schedule and allow communication with terminal 100 to continue.

[0265] Alternatively, for example, base station 200 could use HARQ process number 0 (in other words, the cell's inherent K) offset,cell The communication will use the terminal's dedicated K offset,UE The value is then communicated to terminal 100 again, ensuring that the identification between base station 200 and terminal 100 is consistent.

[0266] The above describes methods 1 through 5. Furthermore, at least two methods from methods 1 through 5 can be combined. As an example, terminal 100 can also use the cell-specific K based on a combination of the DCI format used for scheduling transmission (method 1) and the search space. offset,cell and terminal-specific K offset,UE One of them. For example, it could also be that, in the case of using a general search space and being scheduled by DCI format 0_0 or 1_0, terminal 100 uses the cell-specific K. offset,cell In other cases, terminal 100 uses terminal-specific K offset,UE The same applies to other combinations of methods 1 through 5.

[0267] Additionally, base station 200 can also notify the use of the cell's inherent K in the DCI used for data scheduling. offset,cell With terminal-specific K offset,UE Which one?

[0268] Thus, according to this embodiment, terminal 100 uses the cell-specific K based on information related to the DCI used for scheduling (e.g., a specific DCI or a specific method). offset,cell and terminal-specific K offset,UE One of them controls the uplink transmission timing. Therefore, for example, when the identification of the terminal-specific transmission time slot timing differs between terminal 100 and base station 200, even in the terminal-specific K... offset,UE Even after being notified to terminal 100, it is still possible to use the cell's inherent K...offset,cell The transmission time slot timing allows communication between terminal 100 and base station 200 to continue. Therefore, according to this embodiment, appropriate timing control corresponding to the propagation delay between terminal 100 and base station 200 can be achieved. Furthermore, if based on information related to the PDCCH used for scheduling (e.g., a specific PDCCH or a specific method), the cell-specific K... offset,cell and terminal-specific K offset,UE One of the methods, controlling the uplink transmission timing, can also achieve the same effect.

[0269] Additionally, DCI formats such as DCI format 0_0 and DCI format 1_0, whose DCI content does not change based on the settings of individual terminals, are sometimes referred to as "Fallback DCI". Alternatively, in the case of fallback DCI scheduling, the cell's inherent K can be used. offset,cell In all other cases, use the terminal-specific K. offset,UE .

[0270] (Implementation Method 4)

[0271] The structure of the terminal and base station in this embodiment can be the same as that of the terminal 100 and base station 200 shown in Embodiment 1. However, the timing adjustment operations of the terminal 100 and base station 200 shown in Embodiment 1 are different from those in this embodiment. For example, the terminal 100 and base station 200 can perform timing adjustment using "Koffset", which specifies the timing of the transmission time slot, just like in Embodiment 3.

[0272] Additionally, in this embodiment, for example, for data transmission, a HARQ process with HARQ feedback enabled or a HARQ process with HARQ feedback disabled is used.

[0273] Information related to enabling or disabling HARQ feedback, for example, can be communicated to the terminal 100 by the base station 200 as information specific to the HARQ process.

[0274] Terminal 100 sends HARQ feedback (e.g., ACK / NACK) for PDSCH (or transport block) of HARQ process with HARQ feedback enabled, and does not send HARQ feedback for PDSCH (or transport block) of HARQ process with HARQ feedback disabled.

[0275] The following describes Koffset notification method 1 and notification method 2 in this embodiment.

[0276] <Koffset Notification Method 1>

[0277] In notification method 1, for example, for notifying Koffset (e.g., K... offset,UE K offset,adj The PDSCH of terminal 100 (or the coarse TA) allocates a HARQ process with HARQ feedback enabled. For example, terminal 100 can use a retransmission process with HARQ feedback enabled to receive information related to Koffset. In other words, terminal 100 will not use a retransmission process with HARQ feedback disabled to receive information related to Koffset.

[0278] Additionally, terminal 100 may reflect the received Koffset value at a predetermined time interval, for example. For instance, if the Koffset is notified by the MAC CE, terminal 100 may reflect the Koffset three time slots (or X time slots) after the HARQ-ACK transmission time for the PDSCH containing the MAC CE. Alternatively, if the Koffset is notified by RRC signaling, terminal 100 may reflect the Koffset 10ms after the PDSCH reception time slot.

[0279] For example, in response to the notification of Koffset, base station 200 receives the HARQ feedback signal sent from terminal 100, thereby inferring whether terminal 100 has correctly received the MAC CE. Therefore, the possibility of inconsistencies in the identification of the Koffset value between base station 200 and terminal 100 can be reduced.

[0280] Furthermore, since the timing of the response to the received Koffset is uniquely defined in the terminal 100, the identification of the Koffset can be made consistent between the base station 200 and the terminal 100 if the terminal 100 correctly receives the Koffset.

[0281] <Koffset Notification Method 2>

[0282] In notification method 2, for example, it could be used to notify Koffset (e.g., K... offset,UE K offset,adj The PDSCH (or coarse TA) allocates either a HARQ process with HARQ feedback enabled or a HARQ process with HARQ feedback disabled. For example, terminal 100 can use either a retransmission process with HARQ feedback enabled or a retransmission process with HARQ feedback disabled to receive information related to Koffset.

[0283] For example, when using a HARQ process with HARQ feedback disabled, base station 200 can also reduce the probability of transmission timing discrepancies between base station 200 and terminal 100 due to errors in Koffset notification by using low MCS or transmitting with a low target error rate (BLER: Block Error Rate) such as repetition transmission.

[0284] In addition, in notification method 2, similar to notification method 1, terminal 100 may, for example, reflect the received Koffset value at a predetermined time interval. For example, when Koffset is notified by MAC CE, terminal 100 may reflect Koffset 3 time slots later (or X time slots later) from the time interval of HARQ-ACK transmission for PDSCH containing MAC CE.

[0285] On the other hand, when using a HARQ process with HARQ feedback disabled, no HARQ-ACK is sent. In this case, although terminal 100 does not actually send anything, it can reflect the Koffset 3 times (or X times) after the timing from which the HARQ-ACK is supposed to be sent (e.g., referred to as the "virtual HARQ-ACK timing").

[0286] Additionally, the timing of HARQ-ACK transmission can be determined, for example, based on the value of K1 (the offset from the PDSCH slot) notified by DCI during PDSCH scheduling. For instance, when using a HARQ process with HARQ feedback disabled, although terminal 100 does not actually send HARQ-ACK, the virtual HARQ-ACK timing can still be determined based on the notified value of K1.

[0287] Furthermore, when HARQ feedback is disabled, a K1 value is not needed in the first place. Therefore, the K1 value may not be notified by DCI, may be used for other purposes, or may be considered an invalid field. In these cases, one of the values ​​configured as candidate K1 values ​​(e.g., minimum or maximum) can be used to determine the virtual HARQ-ACK timing. Alternatively, the K1 value used when HARQ feedback is disabled can be configured, or a default value for the K1 value can be specified in the specification.

[0288] According to notification method 2, for example, whether HARQ feedback is enabled or disabled, the timing of Koffset response is specified in a way that can be uniquely determined. Therefore, if terminal 100 correctly receives the Koffset value, the identification of Koffset can be consistent between base station 200 and terminal 100.

[0289] The above explains Koffset's notification method 1 and notification method 2.

[0290] Furthermore, in embodiments 3 and 4, the adjustment value K described in embodiment 1 or embodiment 2 may also be used, for example. adj,UE Through K offset,cell -K adj,UE Calculate the terminal-specific K offset,UE Alternatively, a coarser TA value (e.g., coarse TA) can be used, through K. offset,cell -TA coarse Calculate the terminal-specific K offset,UE K adj,UE Alternatively, a coarser TA value may be communicated to terminal 100 via at least one of an RRC message, MAC CE, or DCI.

[0291] Additionally, for example, in cases where the Koffset is notified by a group common DCI containing information for multiple terminals within a single DCI such as DCI format 2_x, terminal 100 may also reflect the Koffset 3 time slots (or X time slots) after the time slot from which the DCI is received. Terminal 100, for example, aims to minimize the Koffset... offset,UE The generation of identification bias can also occur when receiving data containing K. offset,UE In the case of DCI related information, a HARA-ACK signal is sent to base station 200.

[0292] Additionally, for example, even in terminal-specific K... offset,UE If terminal 100 has already been notified, the cell's inherent K can also be used. offset,cell HARQ feedback is used for PDSCH scheduling by the DCI using the RA-RNTI (Random Access-Radio Network Temporary Identifier). That is, it can also be determined whether to use the cell-specific K based on the RNTI used for scheduling. offset,cell Or should we use the terminal-specific K? offset,UE For example, the cell-inherent K can also be used in the HARQ feedback for PDSCH scheduled by DCI with the following RNTI. offset,cell This RNTI is an RNTI other than the terminal's inherent ID, namely C-RNTI.

[0293] Additionally, for example, even in terminal-specific K... offset,UEIf terminal 100 has already been notified, the cell-specific K can also be used for the PUSCH used for UL grant scheduling of Msg3. offset,cell The aforementioned UL license for Msg3 was notified by the RACH response (MSG2).

[0294] Additionally, for example, the inherent K of the community offset,cell It can be the Koffset value inherent to the satellite beam, or the Koffset value inherent to the SSB beam as specified in 3GPP.

[0295] In addition, the community's inherent K offset,cell It can also be the Koffset value notified via SIB. Additionally, there is a terminal-specific K... offset,UE The Koffset value can be notified via an RRC reconfiguration message sent to each terminal, or it can be notified via MAC CE or DCI.

[0296] Additionally, for example, the offset value (e.g., K) used to determine the transmission slot for PUSCH or PUCCH (HARQ feedback) offset,cell +K1、K offset,cell +K2, or K offset,UE +K1、K offset,UE If +K2 (multiplied by the slot length for time conversion) is less than the TA value (the TA value after time conversion) set for terminal 100, it means that the transmission slot of PUSCH or PUCCH is earlier than the reception slot of DCI or PDSCH. In this case, terminal 100 may not transmit PUSCH or PUCCH. Alternatively, in this case, terminal 100 may, for example, initiate a radio link failure procedure (RLF) or a beam failure procedure (Beam Failure or Beam Recovery). Additionally, RACH may be transmitted for resynchronization.

[0297] Additionally, HARQ feedback can also be referred to as "HARQ-ACK" or "ACK / NACK".

[0298] The above describes various embodiments of this disclosure.

[0299] Furthermore, although the NTN environment (e.g., a satellite communication environment) has been described as an example in the above embodiments, this disclosure is not limited thereto. This disclosure can also be applied to other communication environments (e.g., LTE and / or NR terrestrial cellular environments).

[0300] Furthermore, while examples of GNSS (i.e., location detection using satellite signals) such as GPS have been described in the above embodiments, location detection based on terrestrial cellular base stations, location detection using WiFi and / or Bluetooth (registered trademark) signals, location detection using accelerometers, or a combination thereof can also be performed. Additionally, in addition to latitude and longitude, altitude information may also be included in the location information. Alternatively, values ​​in a separately defined coordinate system may be used. Altitude information may also be obtained from barometric pressure sensors, etc.

[0301] In the above embodiments, although examples are shown of the terminal notifying the base station of at least one of the TA value and location information, the timing of the notification (notification triggering) may differ from the above embodiments. For example, instead of the change in TA value or location, the notification may be triggered based on other indicators such as the change in channel quality. For example, RSRP (Reference Signal Received Power), RSRQ (Reference Signal Received Quality), SINR (Signal to Interference plus Noise Ratio) may be used as channel quality indicators. The threshold for the indicator or change may also be set (Configure) by the base station.

[0302] In addition, the base station can also indicate which information, such as TA value or location information, should be notified.

[0303] Cellular inherent TA offset and K offset,cell Notification can be made by differentiating the notification from the value notified by cell parameters (e.g., a value equivalent to the RTT near the cell center). By performing differential notification, the amount of notification information can be reduced.

[0304] In the above embodiments, the TA command 1, which is controlled at a fine granularity, can utilize the TA command of Rel15 NR without changing the granularity and range. By utilizing it without changing the granularity and range, the amount of changes required in the implementation of the terminal and the base station can be reduced. Alternatively, the base station can use SIB or the like to notify the granularity and range of the TA command 2. Therefore, the TA command 2 can be notified with an appropriate number of bits (e.g., a minimum number of bits) based on factors such as cell size and satellite altitude, thereby reducing notification overhead. Furthermore, regarding K... offset K adj,UE The granularity and range are the same as those described above.

[0305] TA command 1 can be represented by a relative value to TA command 1 sent in the previous transmission timing, or by a control value relative to the TA value sent in the previous transmission timing. In this case, the value obtained by accumulating the values ​​of the received TA command 1 is used as N in equation (1). TA Alternatively, TA command 2 can also be represented by a relative value to TA command 2 sent in the previous transmission timing, or by a control value relative to the TA value sent in the previous transmission timing. In this case, the value obtained by accumulating the values ​​of the received TA command 2 is used as M in equation (2). coarse .

[0306] Cell-specific TA offset and / or K offset,cell It can also be the value for each beam associated with the SSB. In this case, the amount of information in the notification can be reduced by differentiating the value from the value notified at the cell level.

[0307] Signals and / or information broadcast by the base station can be transmitted using SSB and / or SIB, or using methods that can be received by multiple terminals, such as a group-wide DCI format (DCI format 2_x, etc.). Additionally, when multiple terminals use the same timing adjustment value by simultaneously notifying them of TA command 1 and / or TA command 2, TA command 1 and / or TA command 2 can also be transmitted using a group-wide DCI format (DCI format 2_x, etc.).

[0308] Furthermore, in the above embodiments, although two timing adjustment values ​​with different granularities and ranges are used, they can be set to the same granularity and range, or one of the granularity and range can be different. Alternatively, three or more timing adjustment values ​​with different granularities and ranges can be used.

[0309] The timing adjustments based on GNSS / ephemeris location information and path tracking in the above-described embodiments are not implemented according to commands from the base station, but are implemented autonomously by the terminal. The base station detects the reception timing of the received signal from the terminal. If the reception timing changes significantly within the average window during detection, the detection accuracy of the reception timing may deteriorate. Therefore, the terminal can also specify the minimum interval and / or minimum timing change range for the timing adjustments implemented autonomously by the terminal, and set the changes to be within a specified range. In addition, information related to the minimum interval and / or minimum change range can also be notified to the terminal by the base station.

[0310] Alternatively, in the above embodiments, the terminal may use an instruction from the base station as a trigger to perform timing adjustments based on GNSS / ephemeris location information and timing adjustments based on path tracking.

[0311] Additionally, a cell can be an area defined by the received power of SSB and / or CSI-RS transmitted by a base station (or satellite), or it can be an area defined by geographical location. Furthermore, the cell in the above-described embodiment can also be replaced with a beam defined by an SSB.

[0312] Satellite ephemeris information, related to the satellite's position, can be broadcast using system information or pre-stored by the terminal (or base station). Alternatively, the terminal (or base station) can update the satellite ephemeris information when communication is possible. Furthermore, the terminal (or base station) can also use other information to determine the satellite's position.

[0313] Furthermore, while examples of utilizing location information have been described in the above embodiments, for terminals without GNSS functionality and / or terminals unable to obtain satellite location-related information, timing control based on cell-wide timing control information broadcast by the base station can be used instead of location-based timing control. In this case, the base station may also transmit timing control information with a propagation delay equivalent to that near the cell center.

[0314] When a PUSCH allocation is made using a configured grant (i.e., when a PUSCH allocation is not made using DCI), the PUSCH transmission time slot timing will not be adjusted for the DCI receive timing. Therefore, the terminal can also send PUSCH without using TA command 2.

[0315] The uses of the cell's inherent TA offset, TA command 1, TA command 2, and TA value notifications from the terminal are not limited to the uses described above.

[0316] In systems using multiple cells, component carriers, or transceiver points, where there are multiple TA groups (TAGs), primary TA control can be performed by TA group. Additionally, parameters such as the cell-specific TA offset can be made common. Furthermore, the Koffset can be set by TA group. Alternatively, because the delay difference between component carriers (or cells) is less than the time slot length, the Koffset set for the PCell or SpCell can be used in other component carriers or cells (SCells). This reduces the amount of notification information.

[0317] Although the timing adjustment value based on location information is recorded as a fine-grained timing adjustment value, the accuracy of the location information can also be considered to determine the coarser-grained timing adjustment value.

[0318] The base station can be referred to as "gNodeB" or "gNB". Additionally, the terminal can be referred to as "UE".

[0319] A time slot can also be replaced with a time slot, micro-time slot, frame, subframe, etc.

[0320] In addition, expressions such as "...part" in the above embodiments can be replaced with other expressions such as "...circuitry", "...device", "...unit" or "...module".

[0321] Furthermore, in the above embodiments, although the speed of radio wave propagation is recorded as approximately 3 × 10⁻⁶, 8 [m / s], but not limited to this; for example, 2.99792××10 can also be used. 8 Values ​​like [m / s]. The accuracy of radio wave propagation speed can also depend on the installation.

[0322] (Control signal)

[0323] In this disclosure, the downlink control signal (or downlink control information) associated with an embodiment of this disclosure may be, for example, a signal (or information) transmitted in the Physical Downlink Control Channel (PDCCH) at the physical layer, or a signal (or information) transmitted in a higher-layer Medium Access Control Element (MAC CE) or Radio Resource Control (RRC). Furthermore, the signal (or information) is not limited to being notified by a downlink control signal; it may be predefined in a specification (or standard) or pre-configured in the base station and terminal.

[0324] In this disclosure, the uplink control signal (or uplink control information) associated with an embodiment of this disclosure may be, for example, a signal (or information) transmitted in the physical layer PUCCH, or a signal (or information) transmitted in the higher layer MAC CE or RRC. Furthermore, the signal (or information) is not limited to being notified by an uplink control signal; it may be predefined in a specification (or standard) or pre-set in the base station and terminal. Additionally, the uplink control signal may, for example, be replaced with uplink control information (UCI), first-stage sidelink control information (SCI), or second-stage SCI.

[0325] (Base station)

[0326] In one embodiment of this disclosure, the base station can also be a Transmission Reception Point (TRP), cluster head, access point, Remote Radio Head (RRH), eNodeB (eNB), gNodeB (gNB), Base Station (BS), Base Transceiver Station (BTS), host, gateway, etc. Additionally, in sidelink communication, a terminal can replace the base station. Furthermore, a relay device for communication between a high-level relay node and the terminal can replace the base station. Finally, roadside equipment can replace the base station.

[0327] (Uplink / Downlink / Sidelink)

[0328] An embodiment of this disclosure can be applied to any link in the uplink, downlink, and sidelink. For example, an embodiment of this disclosure can also be applied to the Physical Uplink Shared Channel (PUSCH), Physical Uplink Control Channel (PUCCH), Physical Random Access Channel (PRACH) of the uplink, the Physical Downlink Shared Channel (PDSCH), PDCCH, Physical Broadcast Channel (PBCH) of the downlink, or the Physical Sidelink Shared Channel (PSSCH), Physical Sidelink Control Channel (PSCCH), and Physical Sidelink Broadcast Channel (PSBCH) of the sidelink.

[0329] Furthermore, PDCCH, PDSCH, PUSCH, and PUCCH are examples of downlink control channel, downlink data channel, uplink data channel, and uplink control channel, respectively. Additionally, PSCCH and PSSCH are examples of sidelink control channel and sidelink data channel, respectively. Furthermore, PBCH and PSBCH are examples of broadcast channels, and PRACH is an example of a random access channel.

[0330] (Data Channel / Control Channel)

[0331] One embodiment of this disclosure can be applied to any channel in the data channel and the control channel. For example, the channel in one embodiment of this disclosure can also be replaced with one of the following channels: PDSCH, PUSCH, PSSCH of the data channel, or PDCCH, PUCCH, PBCH, PSCCH, PSBCH of the control channel.

[0332] (Reference signal)

[0333] In one embodiment of this disclosure, the reference signal is, for example, a signal known to both the base station and the mobile station, and is sometimes referred to as a "Reference Signal (RS)" or "pilot signal". The reference signal can be any of the following: demodulation reference signal (DMRS), channel state information-reference signal (CSI-RS), tracking reference signal (TRS), phase tracking reference signal (PTRS), cell-specific reference signal (CRS), or sounding reference signal (SRS).

[0334] (Time interval)

[0335] In one embodiment of this disclosure, the unit of time resource is not limited to one or a combination of time slots and symbols. For example, it can be a frame, superframe, subframe, time slot, time slot subslot, minislot, or symbol, Orthogonal Frequency Division Multiplexing (OFDM) symbol, Single Carrier-Frequency Division Multiplexing (SC-FDMA) symbol, or other time resource units. Furthermore, the number of symbols contained in one time slot is not limited to the number of symbols exemplified in the above embodiments, and can also be other numbers of symbols.

[0336] (frequency band)

[0337] One embodiment of this disclosure can be applied to either a licensed band or an unlicensed band.

[0338] (communication)

[0339] One embodiment of this disclosure can be applied to any communication in base station-terminal communication (Uu link communication), terminal-to-terminal communication (sidelink communication), and vehicle-to-everything (V2X) wireless communication technology. For example, the channel in one embodiment of this disclosure can be replaced with one of the following channels: PSCCH, PSSCH, Physical Sidelink Feedback Channel (PSFCH), PSBCH, PDCCH, PUCCH, PDSCH, PUSCH, and PBCH.

[0340] Furthermore, one embodiment of this disclosure can be applied to any network, including terrestrial networks and non-terrestrial networks (NTNs) that use satellites or High Altitude Pseudo Satellites (HAPS). Additionally, one embodiment of this disclosure can also be applied to terrestrial networks with transmission delays greater than the symbol length or time slot length, such as networks with large cell sizes and ultra-wideband transmission networks.

[0341] (Antenna Port)

[0342] In one embodiment of this disclosure, an antenna port refers to a logical antenna (antenna group) composed of one or more physical antennas. For example, an antenna port may not necessarily refer to a single physical antenna; sometimes it refers to an array antenna composed of multiple antennas. For instance, instead of specifying how many physical antennas constitute an antenna port, it may be defined as the smallest unit that the terminal can transmit a reference signal. Additionally, an antenna port is sometimes also defined as the smallest unit multiplied by a precoding vector.

[0343] <5G NR System Architecture and Protocol Stack>

[0344] To realize the next version of fifth-generation mobile phone technology (also known simply as "5G"), which includes the development of a new radio access technology (NR) operating in the frequency range up to 100 GHz, 3GPP is continuing its work. The first version of the 5G standard was completed at the end of 2017, thus enabling the transition to the trial production of terminals (e.g., smartphones) according to the 5G NR standard and commercial deployment.

[0345] For example, the overall system architecture envisions a gNB-RAN (Next Generation Radio Access Network). The gNB provides the UE (User Equipment) side termination for the NG radio access protocols (SDAP (Service Data Adaptation Protocol) / PDCP (Packet Data Convergence Protocol) / RLC (Radio Link Control) / MAC (Medium Access Control) / PHY (Physical Layer)) and control plane (RRC). gNBs are interconnected via the Xn interface. Additionally, gNBs are connected to the NGC (Next Generation Core) via the Next Generation (NG) interface, and more specifically, to the AMF (Access and Mobility Management Function) (e.g., a specific core entity implementing the AMF) via the NG-C interface, and to the UPF (User Plane Function) (e.g., a specific core entity implementing the UPF) via the NG-U interface. Figure 14 This refers to the NG-RAN architecture (e.g., refer to 3GPP TS 38.300v15.6.0, section 4).

[0346] The user plane protocol stack for NR (e.g., see 3GPP TS 38.300, section 4.4.1) comprises the PDCP (Packet Data Convergence Protocol, see TS 38.300, section 6.4) sublayer, RLC (Radio Link Control, see TS 38.300, section 6.3) sublayer, and MAC (Media Access Control, see TS 38.300, section 6.2) sublayer, which terminates on the network side in the gNB. Additionally, a new Access Stratum (AS) sublayer (SDAP: Service Data Adaptation Protocol) has been incorporated into PDCP (e.g., see 3GPP TS 38.300, section 6.5). Furthermore, a control plane protocol stack is defined for NR (e.g., see TS 38.300, section 4.4.2). A summary of Layer 2 functionality is described in Section 6 of TS 38.300. The functions of the PDCP sublayer, RLC sublayer, and MAC sublayer are listed in Sections 6.4, 6.3, and 6.2 of TS 38.300, respectively. The functions of the RRC layer are listed in Section 7 of TS 38.300.

[0347] For example, the media access control layer handles the multiplexing of logical channels, scheduling of processing involving various parameter sets, and various functions associated with scheduling.

[0348] For example, the Physical Layer (PHY) is responsible for encoding, PHY HARQ (Physical Layer Hybrid Automatic Repeat Request) processing, modulation, multi-antenna processing, and mapping signals to appropriate physical time-frequency resources. Additionally, the Physical Layer handles the mapping of physical channels to transport channels. The Physical Layer provides services to the MAC Layer in the form of transport channels. A physical channel corresponds to a set of time-frequency resources used to transmit a specific transport channel; each transport channel is mapped to a corresponding physical channel. For example, in physical channels, uplink physical channels include PRACH (Physical Random Access Channel), PUSCH (Physical Uplink Shared Channel), and PUCCH (Physical Uplink Control Channel), while downlink physical channels include PDSCH (Physical Downlink Shared Channel), PDCCH (Physical Downlink Control Channel), and PBCH (Physical Broadcast Channel).

[0349] In NR use cases / extended scenarios, enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), and massive machine-type communications (mMTC) may have multiple necessary conditions in terms of data rate, latency, and coverage. For example, eMBB is expected to support peak data rates approximately three times that of IMT-Advanced (20Gbps in downlink and 10Gbps in uplink) and effective (user-experienced) data rates. On the other hand, in the case of URLLC, more stringent necessary conditions are proposed for ultra-low latency (0.5ms latency in both UL and DL) and high reliability (within 1ms, 1-10-5). Finally, in mMTC, high connection density (1,000,000 devices / km in urban environments) is preferably required. 2 ), wide coverage in harsh environments and extremely long battery life (15 years) for inexpensive devices.

[0350] Therefore, a set of OFDM (Orthogonal Frequency Division Multiplexing) parameters suitable for one use case (e.g., subcarrier spacing (SCS), OFDM symbol length, cyclic prefix (CP) length, number of symbols per scheduling interval) may be ineffective for other use cases. For example, in low-latency services, it is preferable to have shorter symbol lengths (and thus larger subcarrier spacings) and / or fewer symbols per scheduling interval (also known as "TTI"). Moreover, in extended scenarios with large channel delay spreads, it is preferable to have longer CP lengths than in scenarios with shorter delay spreads. The subcarrier spacing can also be optimized depending on the situation to maintain the same CP overhead. NR supports more than one subcarrier spacing value. Correspondingly, subcarrier spacings of 15kHz, 30kHz, 60kHz, etc., are currently considered. The symbol length Tu and subcarrier spacing Δf are directly related according to the formula Δf = 1 / Tu. Similar to the LTE (Long Term Evolution) system, the term "resource element" can be used to represent the smallest resource unit consisting of a subcarrier with a length corresponding to one OFDM / SC-FDMA (Single-Carrier Frequency Division Multiple Access) symbol.

[0351] In the new 5G-NR wireless system, resource grids for subcarriers and OFDM symbols are defined in both the uplink and downlink for each parameter set and each carrier. Each element of the resource grid is called a "resource element," which is determined based on the frequency index in the frequency domain and the symbol position in the time domain (refer to 3GPP TS 38.211v15.6.0).

[0352] <Functional Separation between NG-RAN and 5GC in 5G NR>

[0353] Figure 15 This indicates the functional separation between NG-RAN and 5GC. The logical node of NG-RAN is either gNB or ng-eNB. 5GC has logical nodes AMF, UPF, and SMF (Session Management Function).

[0354] For example, gNB and ng-eNB host the following main functions:

[0355] - Functions such as Radio Bearer Control, Radio Admission Control, Connection Mobility Control, and Radio Resource Management (RRM) that dynamically allocates (schedules) resources to the UE in both the uplink and downlink links;

[0356] - Data IP (Internet Protocol) header compression, encryption, and integrity protection;

[0357] - Selection of AMF when attaching a UE in situations where the route to the AMF cannot be determined based on the information provided by the UE;

[0358] - Routing to user plane data towards UPF;

[0359] - Routing of control plane information toward AMF;

[0360] - Setting and canceling connections;

[0361] - Scheduling and sending paging messages;

[0362] - The scheduling and transmission of system broadcast information (originating from AMF or Operation, Admission, and Maintenance functions (OAM));

[0363] - Setting up measurements and measurement reports for mobility and scheduling;

[0364] - Packet markings for transmission class in the uplink;

[0365] -Session management;

[0366] -Support for network slicing;

[0367] - QoS (Quality of Service) flow management and mapping to data radio bearers;

[0368] Support for UEs in RRC_INACTIVE (RRC inactive) state;

[0369] - NAS (Non-Access Stratum) message distribution function;

[0370] - Sharing of wireless access networks;

[0371] - Dual connectivity;

[0372] - Close collaboration between NR and E-UTRA (Evolved Universal Terrestrial Radio Access).

[0373] The Access and Mobility Management Function (AMF) administers the following main functions:

[0374] - Function to terminate Non-Access Stratum (NAS) signaling;

[0375] -Security of NAS signaling;

[0376] - Security controls at the access layer (AS);

[0377] - Core Network (CN) inter-node signaling for mobility between 3GPP access networks;

[0378] - The possibility of a UE reaching idle mode (including control and execution of paging retransmission);

[0379] -Management of the registered area;

[0380] - Support for intra-system mobility and inter-system mobility;

[0381] -Access authentication;

[0382] - Access licenses that include roaming permission checks;

[0383] - Mobility management controls (subscription and policies);

[0384] -Support for network slicing;

[0385] - Selection of Session Management Function (SMF).

[0386] In addition, the User Face Function (UPF) hosts the following main functions:

[0387] - Anchor points for intra-RAT (Radio Access Technology) mobility / inter-RAT (where applicable) mobility;

[0388] - External PDU (Protocol Data Unit) session points used for interconnection with data networks;

[0389] - Packet routing and forwarding;

[0390] - Enforcement of policy rules in group checks and user-facing aspects;

[0391] - Reports on business usage;

[0392] - Uplink classifier used to support routing of service flows toward the data network;

[0393] - Branching points used to support multi-homed PDU sessions;

[0394] - For user plane QoS processing (e.g., packet filtering, gating, UL / DL rate enforcement);

[0395] - Uplink service verification (SDF (Service Data Flow) mapping to QoS flow);

[0396] - Downlink packet buffering and downlink data notification triggering functions.

[0397] Finally, the Session Management Function (SMF) administers the following main functions:

[0398] -Session management;

[0399] - The allocation and management of UE IP addresses;

[0400] -Selection and control of UPF;

[0401] - A function for setting traffic steering in the User Plane Function (UPF) to direct traffic to the appropriate destination;

[0402] - Enforcing policies and QoS in the control section;

[0403] - Notification of downlink data.

[0404] <The process of setting up and resetting RRC connection>

[0405] Figure 16 This refers to several interactions between the UE, gNB, and AMF (5GC entity) when the UE in the NAS part transitions from RRC_IDLE (RRC idle) to RRC_CONNECTED (RRC connected) (refer to TS 38.300v15.6.0).

[0406] RRC is a higher-level signaling (protocol) used for UE and gNB configuration. Through this transition, the AMF prepares UE context data (which includes, for example, PDU session context, security keys, UE radio capabilities, and UE security capabilities) and sends it to the gNB along with an initial context setting request. Next, the gNB and UE activate AS security together. The gNB sends a SecurityModeCommand message to the UE, and the UE responds with a SecurityModeComplete message, thereby activating AS security. Then, the gNB sends an RRCReconfiguration message to the UE, and receives an RRCReconfigurationComplete message from the UE for this message, thus performing the reconfiguration of Signaling RadioBearer 2 (SRB2) and Data Radio Bearer (DRB). For signaling-only connections, since SRB2 and DRB are not configured, the steps related to RRC reconfiguration can be omitted. Finally, the gNB notifies the AMF that the configuration process is complete using the Initial Context Setup Reply.

[0407] Therefore, this disclosure provides an entity (e.g., AMF, SMF, etc.) for a fifth-generation core network (5GC), comprising: a control circuit that, upon operation, establishes a Next Generation (NG) connection with a gNodeB; and a transmission unit that, upon operation, transmits an initial context setting message to the gNodeB via the NG connection to configure the signaling radio bearer between the gNodeB and the User Equipment (UE). Specifically, the gNodeB transmits Radio Resource Control (RRC) signaling containing an Information Element (IE) to the UE via the signaling radio bearer. The UE then performs uplink transmission or downlink reception based on the resource allocation settings.

[0408] <Application Scenarios of IMT after 2020>

[0409] Figure 17This section outlines several use cases for 5G NR. Within the 3rd Generation Partnership Project New Radio (3GPP NR), three use cases supporting a wide variety of services and applications, conceived through IMT-2020, have been studied. Planning for the first phase of specifications for enhanced mobile broadband (eMBB) has been completed. Current and future work, in addition to gradually expanding eMBB support, includes standardization for ultra-reliable and low-latency communications (URLLC) and massive machine-type communications (mMTC). Figure 17 Several examples illustrating conceptual application scenarios for IMT after 2020 (e.g., referring to ITU-R M.2083). Figure 2 ).

[0410] URLLC use cases have strict requirements related to performance aspects such as throughput, latency, and availability. URLLC is conceived as a key technology for enabling wireless control of future industrial production or manufacturing processes, remote medical surgery, automation of power transmission and distribution in smart grids, and traffic safety applications. Ultra-high reliability of URLLC is supported by defining technologies that meet the requirements set by TR38.913. In NR URLLC version 15, a crucial requirement is a target user plane latency of 0.5ms in the UL (uplink) and 0.5ms in the DL (downlink). For a single packet transmission, the overall requirement for URLLC is a block error rate (BLER) of 1E-5 for a 32-byte packet size with a user plane latency of 1ms.

[0411] Considering the physical layer, numerous methods are available to improve reliability. Current possibilities for reliability enhancement include defining alternative CQI (Channel Quality Indicator) tables for URLLC, a more compact DCI (Downlink Control Information) format, and PDCCH iteration. However, as NR (a crucial prerequisite for NR URLLC) becomes more stable and is further developed, this scope can be expanded to achieve ultra-high reliability. Specific use cases for NR URLLC in version 15 include augmented reality / virtual reality (AR / VR), e-health, e-safety, and other critical applications.

[0412] Furthermore, technical enhancements targeting NR URLLC aim to improve latency and reliability. Latency enhancements include configurable parameter sets, non-slot-based scheduling utilizing flexible mapping, unlicensed (already licensed) uplinks, slot-level repetition in the data channel, and pre-emption in the downlink. Pre-emption refers to stopping transmissions with allocated resources and using those resources for later-requested transmissions that require lower latency / higher priority. Therefore, a permitted transmission is replaced by a subsequent transmission. Pre-emption can be applied regardless of the specific service type. For example, a transmission in service type A (URLLC) can be replaced by a transmission in service type B (eMBB, etc.). Reliability enhancements include a dedicated CQI / MCS (Modulation and Coding Scheme) table for a target BLER of 1E-5.

[0413] The use cases for mMTC (massive machine-type communications) are characterized by a large number of connected devices that transmit relatively small amounts of data that are not easily affected by latency. These devices require low cost and very long battery life. From NR's perspective, utilizing very narrow bandwidth is a solution to save UE power and extend its battery life.

[0414] As mentioned above, the potential for improved reliability in NR is further expanded. It is one of the essential conditions for all situations; for example, high or ultra-high reliability is a crucial requirement related to URLLC and mMTC. From both wireless and network perspectives, reliability can be improved through several mechanisms. Generally, there are two to three important areas that could potentially contribute to improved reliability. These areas include compact control channel information, data / control channel iteration, and diversity related to the frequency, time, and / or spatial domains. These areas can be used universally to improve reliability, independent of specific communication scenarios.

[0415] Regarding NR URLLC, further use cases with more stringent requirements are envisioned, such as factory automation, transportation, and power transmission. Stricter requirements refer to high reliability (reaching level 10⁻⁶), high availability, a packet size of 256 bytes, and time synchronization of approximately several microseconds (μs) (capable of corresponding to use cases, with values ​​set to 1 μs or several microseconds depending on the frequency range and short latency of approximately 0.5ms to 1ms (e.g., 0.5ms latency in the target user plane)).

[0416] Furthermore, from a physical layer perspective, there are several technical enhancements to NR URLLC. These enhancements include strengthening the PDCCH (Physical Downlink Control Channel) associated with compact DCI, PDCCH repetition, and increased PDCCH monitoring. Additionally, enhancements to UCI (Uplink Control Information) are related to enhanced HARQ (Hybrid Automatic Repeat Request) and CSI feedback. Furthermore, there may be enhancements to PUSCH and retransmission / repetition related to micro-slot-level frequency hopping. The term "micro-slot" refers to a transmission time interval (TTI) containing fewer symbols than a time slot (a time slot has 14 symbols).

[0417] <QoS Control>

[0418] 5G's QoS (Quality of Service) model is based on QoS flows, supporting both QoS flows that require guaranteed bit rate (GBR) and QoS flows that do not require guaranteed bit rate (non-GBR QoS flows). Therefore, at the NAS level, QoS flows represent the finest granular QoS classification within a PDU session. QoS flows are determined within a PDU session based on the QoS Flow ID (QFI) transmitted via the encapsulation header through the NG-U interface.

[0419] For each UE, 5GC establishes one or more PDU sessions. For each UE, in conjunction with the PDU session, NG-RAN, for example, refers to the previous text. Figure 16 As explained, at least one Data Radio Bearer (DRB) is established. Additionally, DRBs can be subsequently configured for QoS flows added to this PDU session (when to configure this depends on the NG-RAN). The NG-RAN maps packets belonging to various PDU sessions to various DRBs. NAS-level packet filters in the UE and 5GC are used to associate UL and DL packets with QoS flows, while AS-level mapping rules in the UE and NG-RAN associate UL and DL QoS flows with DRBs.

[0420] Figure 18 This refers to the non-roaming reference architecture of 5G NR (refer to TS 23.501v16.1.0, section 4.23). Application Function (AF) (e.g., hosting...) Figure 17 The external application server for the illustrated 5G service interacts with the 3GPP core network to provide services. For example, it may access a Network Exposure Function (NEF) to support applications that impact service routing, or it may interact with a policy framework (see Policy Control Function (PCF)) for policy control (e.g., QoS control). Based on operator deployment, operators deem trusted application functions capable of directly interacting with associated network functions. Application functions not permitted by the operator to directly access network functions interact with associated network functions via the NEF, using an open framework accessible to the outside world.

[0421] Figure 18It also indicates further functional units of the 5G architecture, namely, the Network Slice Selection Function (NSSF), the Network Repository Function (NRF), Unified Data Management (UDM), the Authentication Server Function (AUSF), the Access and Mobility Management Function (AMF), the Session Management Function (SMF), and the Data Network (DN: Data Network, such as services provided by operators, internet access, or services provided by third parties). All or part of the core network's functions and application services can also be deployed and operate in a cloud computing environment.

[0422] Therefore, the present invention provides an application server (e.g., an AF in a 5G architecture) comprising: a transmitting unit that, in order to establish a PDU session containing a radio bearer between a g node B and a UE corresponding to QoS requirements, sends at least one of the following functions (e.g., NEF, AMF, SMF, PCF, UPF, etc.) to the 5GC during operation: a request containing QoS requirements for at least one of URLLC service, eMMB service, and mMTC service; and a control circuit that, during operation, performs services using the established PDU session.

[0423] This invention can be implemented in software, hardware, or software in cooperation with hardware. The functional blocks used in the above embodiments are implemented partially or wholly as LSIs (Large Scale Integration), and the processes described in the above embodiments can also be controlled partially or wholly by a single LSI or a combination of LSIs. An LSI can be composed of individual chips, or it can be composed of a single chip containing some or all of the functional blocks. An LSI can also include data input and output. Depending on the degree of integration, an LSI can also be called an "IC (Integrated Circuit)," a "System LSI," a "Super LSI," or an "Ultra LSI."

[0424] The method of integrating LSIs is not limited to LSIs; it can also be implemented using dedicated circuits, general-purpose processors, or special-purpose processors. Alternatively, LSIs can be used to fabricate programmable FPGAs (Field Programmable Gate Arrays), or reconfigurable processors that allow for reconfiguration of the connections or settings of the circuit blocks within the LSI. This disclosure can also be implemented for digital or analog processing.

[0425] Furthermore, if advancements in semiconductor technology or the emergence of other derivative technologies lead to integrated circuit technologies that can replace LSIs, these technologies could also be used to integrate functional blocks. There are also possibilities for applications such as biotechnology.

[0426] This invention can be implemented in all kinds of devices, apparatuses, and systems with communication capabilities (collectively referred to as "communication devices"). A communication device may also include a wireless transceiver and processing / control circuitry. The wireless transceiver may also include a receiving unit and a transmitting unit, or perform the functions of these units. The wireless transceiver (transmitting unit, receiving unit) may also include an RF (Radio Frequency) module and one or more antennas. The RF module may also include an amplifier, an RF modulator / demodulator, or similar devices. Non-limiting examples of communication devices include: telephones (mobile phones, smartphones, etc.), tablet computers, personal computers (PCs) (laptops, desktops, laptops, etc.), cameras (digital cameras, digital camcorders, etc.), digital players (digital audio / video players, etc.), wearable devices (wearable cameras, smartwatches, tracking devices, etc.), game consoles, e-book readers, remote health / telemedicine (remote healthcare / medical prescription) devices, vehicles or transportation vehicles with communication capabilities (cars, airplanes, ships, etc.), and combinations of the various devices described above.

[0427] Communication devices are not limited to portable or movable devices, but also include all kinds of devices, equipment, and systems that cannot be carried or fixed, such as smart home devices (home appliances, lighting equipment, smart meters or meters, control panels, etc.), vending machines, and all other "things" that can exist on the IoT (Internet of Things) network.

[0428] In addition to data communication via cellular systems, wireless LAN (Local Area Network) systems, and communication satellite systems, communication also includes data communication via a combination of these systems.

[0429] In addition, the communication device also includes devices such as controllers or sensors that are connected or linked to a communication device performing the communication functions described in this disclosure. For example, it includes a controller or sensor that generates control signals or data signals used by the communication device to perform the communication functions of the communication device.

[0430] In addition, the communication device includes infrastructure equipment that communicates with or controls the various devices described above (not limited to these), such as base stations, access points, and all other devices, equipment, and systems.

[0431] One embodiment of the terminal disclosed herein includes: a control circuit that controls uplink transmission timing using one of a first offset and a second offset shorter than the first offset, based on information related to a control signal used for scheduling; and a transmission circuit that performs uplink transmission based on the control of the uplink transmission timing.

[0432] In one embodiment of this disclosure, the information indicates the format of the control signal, and when the format is DCI format 0_0 or DCI format 1_0, the control circuit uses the first offset.

[0433] In one embodiment of this disclosure, the information represents a search space for sending the control signal, and in the case that the search space is a search space common to multiple terminals, the control circuit uses the first offset.

[0434] In one embodiment of this disclosure, the information represents a resource for transmitting the control signal, and in the case that the resource is a resource common to multiple terminals, the control circuit uses the first offset.

[0435] In one embodiment of this disclosure, the information indicates that, using a scheduling method with the control signal, in the case of a semi-continuous scheduling method, the control circuit uses the first offset.

[0436] In one embodiment of this disclosure, the information represents a retransmission process number notified by the control signal, and the control circuit selects one of the first offset and the second offset based on the retransmission process number.

[0437] In one embodiment of this disclosure, when the retransmission process number is 0, the control circuit selects the first offset.

[0438] In one embodiment of this disclosure, a receiving circuitry is included to receive information related to the second offset using a retransmission process with retransmission control enabled.

[0439] In one embodiment of this disclosure, a receiving circuitry is included to receive information related to the second offset using a retransmission process with retransmission control disabled.

[0440] A base station according to one embodiment of this disclosure includes: a control circuit that controls uplink reception timing using one of a first offset and a second offset shorter than the first offset, based on information related to control signals for scheduling; and a reception circuit that performs uplink reception based on the control of the uplink reception timing.

[0441] In one embodiment of the transmission method of this disclosure, the terminal controls the uplink transmission timing based on information related to the control signal used for scheduling, using either a first offset or a second offset shorter than the first offset, and performs uplink transmission based on the control of the uplink transmission timing.

[0442] In one embodiment of the receiving method of this disclosure, the base station controls the uplink receiving timing based on information related to control signals used for scheduling, using one of a first offset and a second offset shorter than the first offset, and performs uplink receiving based on the control of the uplink receiving timing.

[0443] The entire contents of the specification, drawings and abstract of the specification contained in Japanese Patent Application No. 2020-177279, filed on October 22, 2020, are incorporated herein by reference.

[0444] Industrial applicability

[0445] One aspect of this disclosure is useful for wireless communication systems.

[0446] Explanation of reference numerals in the attached figures

[0447] 100 terminals

[0448] 101 PRACH Production Department

[0449] Data Generation Departments 102 and 206

[0450] 103 Location Information Acquisition Department

[0451] 104 Timing Adjustment Department

[0452] Wireless Transmission Units 105 and 208

[0453] 106, 201 antennas

[0454] 107, 202 Wireless Receiving Unit

[0455] 108 Demodulation / Decoding Section

[0456] 109, 209 Control Department

[0457] 200 base stations

[0458] 203 Data Receiving and Processing Department

[0459] 204 PRACH Inspection Department

[0460] 205 Timing Control Information Generation Unit

[0461] 207 Data Transmission Processing Department

Claims

1. A terminal, characterized in that, include: The control circuit controls the uplink transmission timing using one of a first offset and a second offset, based on information related to the control signal, which is a control signal used for scheduling. as well as The transmitter performs uplink transmission based on the aforementioned uplink transmission timing. The first offset is a cell-inherent offset, and the second offset is an offset based on the cell-inherent offset and the terminal-specific offset. The information related to the control signals is the Radio Network Temporary Identifier (RNTI) for downlink control information. A second offset is used in the C-RNTI, which is the first RNTI, and a first offset is used in the second RNTI, which is different from the C-RNTI.

2. The terminal as described in claim 1, wherein, The first offset is used for uplink transmissions scheduled by the uplink license of the random access response.

3. The terminal as described in claim 1, wherein, The information related to the control signals is the Radio Network Temporary Identifier (RNTI), which is a downlink control information related to downlink data transmission. The uplink transmission timing is the transmission timing of a response signal, which is a response signal for the downlink data transmission.

4. A base station, characterized in that, include: The control circuit controls the uplink transmission timing using one of a first offset and a second offset, based on information related to the control signal, which is a control signal used for scheduling. as well as The receiver, based on the aforementioned uplink transmission timing, receives the uplink transmission. The first offset is a cell-inherent offset, and the second offset is an offset based on the cell-inherent offset and the terminal-specific offset. The information related to the control signals is the Radio Network Temporary Identifier (RNTI) for downlink control information. A second offset is used in the C-RNTI, which is the first RNTI, and a first offset is used in the second RNTI, which is different from the C-RNTI.

5. The base station as described in claim 4, wherein, The first offset is used for uplink transmissions scheduled by the uplink license of the random access response.

6. The base station as described in claim 4, wherein, The information related to the control signals is the Radio Network Temporary Identifier (RNTI), which is a downlink control information related to downlink data transmission. The uplink transmission timing is the transmission timing of a response signal, which is a response signal for the downlink data transmission.

7. A method for transmitting data, characterized in that, Includes the following steps: Based on information related to the control signal, the uplink transmission timing is controlled using one of a first offset and a second offset, wherein the control signal is a scheduling control signal; and Based on the aforementioned uplink transmission timing, uplink transmission is performed. The first offset is a cell-inherent offset, and the second offset is an offset based on the cell-inherent offset and the terminal-specific offset. The information related to the control signals is the Radio Network Temporary Identifier (RNTI) for downlink control information. A second offset is used in the C-RNTI, which is the first RNTI, and a first offset is used in the second RNTI, which is different from the C-RNTI.

8. The sending method as described in claim 7, wherein, The first offset is used for uplink transmissions scheduled by the uplink license of the random access response.

9. The sending method as described in claim 7, wherein, The information related to the control signals is the Radio Network Temporary Identifier (RNTI), which is a downlink control information related to downlink data transmission. The uplink transmission timing is the transmission timing of a response signal, which is a response signal for the downlink data transmission.

10. A receiving method, characterized in that, Includes the following steps: Based on information related to the control signal, the uplink transmission timing is controlled using one of a first offset and a second offset, wherein the control signal is a scheduling control signal; and Based on the aforementioned uplink transmission timing, receive the uplink transmission. The first offset is a cell-inherent offset, and the second offset is an offset based on the cell-inherent offset and the terminal-specific offset. The information related to the control signals is the Radio Network Temporary Identifier (RNTI) for downlink control information. A second offset is used in the C-RNTI, which is the first RNTI, and a first offset is used in the second RNTI, which is different from the C-RNTI.

11. The receiving method as described in claim 10, wherein, The first offset is used for uplink transmissions scheduled by the uplink license of the random access response.

12. The receiving method as described in claim 10, wherein, The information related to the control signals is the Radio Network Temporary Identifier (RNTI), which is a downlink control information related to downlink data transmission. The uplink transmission timing is the transmission timing of a response signal, which is a response signal for the downlink data transmission.

13. An integrated circuit, characterized in that, include: The control circuit controls the uplink transmission timing using one of a first offset and a second offset, based on information related to the control signal, which is a control signal used for scheduling. as well as The transmitting circuit controls the uplink transmission based on the uplink transmission timing. The first offset is a cell-inherent offset, and the second offset is an offset based on the cell-inherent offset and the terminal-specific offset. The information related to the control signals is the Radio Network Temporary Identifier (RNTI) for downlink control information. A second offset is used in the C-RNTI, which is the first RNTI, and a first offset is used in the second RNTI, which is different from the C-RNTI.

14. An integrated circuit, characterized in that, include: The control circuit, based on information related to the control signal, controls the uplink transmission timing using either a first offset or a second offset, wherein the control signal is a scheduling control signal; and The receiving circuit controls the following reception, which is based on the timing of the uplink transmission and the reception of the uplink transmission. The first offset is a cell-inherent offset, and the second offset is an offset based on the cell-inherent offset and the terminal-specific offset. The information related to the control signals is the Radio Network Temporary Identifier (RNTI) for downlink control information. A second offset is used in the C-RNTI, which is the first RNTI, and a first offset is used in the second RNTI, which is different from the C-RNTI.

Images