Terminal and communication method

Abstract

A terminal is provided with: a reception unit that receives, from a base station constituting an NTN (non-terrestrial network), a TA command and a parameter relating to a TA (timing advance) common to all users in the base station; and a control unit that calculates a common TA on the basis of the parameter, and performs uplink synchronization on the basis of the TA command, the calculated common TA, a device-specific TA, and an offset amount, and when GNSS (Global Navigation Satellite System) information cannot be used, the control unit calculates the device-specific TA on the basis of position information, and performs uplink synchronization on the basis of the device-specific TA and the offset amount. The location information is obtained based on positioning dependent on RAT (Radio Access Technology).

Description

Technical Field

[0001] This invention relates to terminals and communication methods in wireless communication systems. Background Technology

[0002] In NR (New Radio) (also known as "5G"), which is the successor system to LTE (Long Term Evolution), technologies are being researched to meet the requirements of high-capacity systems, high-speed data transmission, low latency, simultaneous connection of multiple terminals, low cost, and power saving (e.g., Non-Patent Literature 1).

[0003] In addition, NTN (Non-Terrestrial Network) is currently under research. NTN uses non-terrestrial networks such as satellites to provide services to areas that are mainly inaccessible to terrestrial 5G networks due to cost constraints (e.g., Non-Patent Literature 2 and Non-Patent Literature 3).

[0004] Existing technical documents

[0005] Non-patent literature

[0006] Non-patent literature 1: 3GPP TS 38.300 V17.6.0 (2023-09)

[0007] Non-patent literature 2: 3GPP TR 38.821 V16.2.0 (2023-03)

[0008] Non-Patent Document 3: Konishi, “A Study on Downlink Frequency Sharing in HAPS Mobile Communication Systems”, General Conference of the China Electronics and Information Communication Society, B-17-1, 2020

[0009] Non-patent literature 4: 3GPP TS 38.211 V17.6.0 (2023-09) Summary of the Invention

[0010] The problem that the invention aims to solve

[0011] In NTN, the propagation delay is greater than in terrestrial networks (TN) due to the large distance between the base station and the terminal in the sky. Furthermore, communication in NTN is performed via feeder links and service links, resulting in a significantly larger timing advance (TA) compared to conventional terrestrial networks. This necessitates uplink synchronization that accounts for this propagation delay.

[0012] The present invention was made in view of the above-mentioned problems, and its purpose is to perform uplink synchronization in NTN (Non-Terrestrial Network) systems.

[0013] Methods for solving problems

[0014] According to the disclosed technology, a terminal is provided, comprising: a receiving unit that receives parameters and TA commands related to the common TA (Timing Advance) of all users in the base station constituting an NTN (Non-Terrestrial Network); and a control unit that calculates the common TA based on the parameters, and performs uplink synchronization based on the TA commands, the calculated common TA, the device-specific TA, and an offset. When GNSS (Global Navigation Satellite System) information cannot be used, the control unit calculates the device-specific TA based on location information obtained based on RAT (Radio Access Technology).

[0015] Invention Effects

[0016] According to publicly available technology, uplink synchronization can be performed in NTN (Non-Terrestrial Network) systems. Attached Figure Description

[0017] Figure 1 This is a diagram showing an example (1) of NTN.

[0018] Figure 2 The diagram shows an example (2) of NTN.

[0019] Figure 3 This is a diagram showing example (3) of NTN.

[0020] Figure 4 The diagram shows an example (4) of NTN.

[0021] Figure 5 This is a diagram used to illustrate an example of timing advance in NTN.

[0022] Figure 6 This is a timing diagram illustrating an example of UL synchronization in NTN.

[0023] Figure 7 This is a diagram used to illustrate example (1) of the common TA in NTN.

[0024] Figure 8 This is a diagram used to illustrate example (2) of the common TA in NTN.

[0025] Figure 9 This is a diagram used to illustrate an example of the inherent TA of a UE in NTN.

[0026] Figure 10 This is a flowchart illustrating an action example (1) in an embodiment of the present invention.

[0027] Figure 11 This is a flowchart illustrating the action example (2) in the embodiments of the present invention.

[0028] Figure 12 This is a diagram illustrating an example of the functional structure of a base station 10 in an embodiment of the present invention.

[0029] Figure 13 This is a diagram illustrating an example of the functional structure of terminal 20 in an embodiment of the present invention.

[0030] Figure 14 This is a diagram illustrating an example of the hardware structure of a base station 10 or terminal 20 in an embodiment of the present invention.

[0031] Figure 15 This is a diagram illustrating an example of the structure of a vehicle 2001 according to an embodiment of the present invention. Detailed Implementation

[0032] Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings. Furthermore, the embodiments described below are merely examples, and the application of the present invention is not limited to the embodiments described below.

[0033] In the operation of the wireless communication system according to embodiments of the present invention, existing technologies are appropriately used. These existing technologies include, for example, existing LTE, but are not limited to, existing LTE. Furthermore, unless otherwise stated, the term "LTE" as used in this specification has a broad meaning that includes LTE-Advanced and subsequent methods (e.g., NR).

[0034] Furthermore, in the embodiments of the present invention described below, the terms SS (Synchronization signal), PSS (Primary SS), SSS (Secondary SS), PBCH (Physical broadcast channel), PRACH (Physical random access channel), PDCCH (Physical Downlink Control Channel), PDSCH (Physical Downlink Shared Channel), PUCCH (Physical Uplink Control Channel), and PUSCH (Physical Uplink Shared Channel) used in conventional LTE are used. These are for ease of description, and the same signals, functions, etc., can also be referred to by other names. Additionally, the above terms in NR correspond to NR-SS, NR-PSS, NR-SS S, NR-PBCH, NR-PRACH, NR-PDCCH, NR-PDSCH, NR-PUCCH, and NR-PUSCH, respectively. However, even signals used for NR are not necessarily explicitly labeled as "NR-".

[0035] In addition, in embodiments of the present invention, the duplex mode can be TDD (Time Division Duplex), FDD (Frequency Division Duplex), or other modes (e.g., Flexible Duplex).

[0036] Furthermore, in embodiments of the present invention, the "configure" wireless parameters can be pre-configured predetermined values, or wireless parameters notified from the base station 10 or the terminal 20.

[0037] Figure 1This is a diagram illustrating example (1) of NTN. NTN (Non-Terrestrial Network) refers to a network that uses non-terrestrial devices such as satellites to provide services to areas that are primarily inaccessible to terrestrial 5G networks due to cost constraints. Furthermore, NTN enables the provision of more reliable services. For example, NTN is envisioned for applications in IoT (Internet of Things), ships, buses, trains, and critical communications. In addition, NTN offers scalability based on efficient multicast or broadcast.

[0038] As an example of NTN, such as Figure 1 As shown, satellite 10A can retransmit signals sent from ground base station 10B and can provide services to areas without ground base stations, such as mountainous areas.

[0039] Furthermore, terrestrial 5G networks can also have the structure described below. A terrestrial 5G network includes one or more base stations 10 and terminals 20. Base station 10 is a communication device that provides one or more cells and wirelessly communicates with terminals 20. The physical resources of the wireless signal are defined in the time and frequency domains. The time domain can be defined by the number of OFDM (Orthogonal Frequency Division Multiplexing) symbols, and the frequency domain can be defined by the number of subcarriers or resource blocks. Base station 10 sends synchronization signals and system information to terminal 20. Synchronization signals are, for example, NR-PSS and NR-SSS. System information is transmitted, for example, via NR-PBCH, also known as broadcast information.

[0040] Base station 10 sends control signals or data to terminal 20 via DL (Downlink) and receives control signals or data from terminal 20 via UL (Uplink). Both base station 10 and terminal 20 are capable of beamforming for signal transmission and reception. Furthermore, both base station 10 and terminal 20 can apply MIMO (Multiple Input Multiple Output) based communication to DL or UL. Additionally, base station 10 and terminal 20 can also communicate via CA (Carrier Aggregation) based SCell (Secondary Cell) and PCell (Primary Cell).

[0041] Terminal 20 is a communication device with wireless communication capabilities, such as a smartphone, mobile phone, tablet computer, wearable terminal, or M2M (Machine-to-Machine) communication module. Terminal 20 receives control signals or data from base station 10 via DL and sends control signals or data to base station 10 via UL, thereby utilizing various communication services provided by the wireless communication system.

[0042] Figure 2 This is a diagram illustrating example (2) of an NTN. The area of ​​each cell or beam in an NTN is very large compared to that of a terrestrial network (TN). Figure 2 An example of an NTN constructed via satellite retransmission is shown. The connection between satellite 10A and NTN gateway 10B is called the feeder link, and the connection between satellite 10A and UE20 is called the service link.

[0043] like Figure 2 As shown, the differential delay between the near-side UE20A and the far-side UE20B is, for example, 10.3 ms in the case of GEO (Geosynchronous orbit) and 3.2 ms in the case of LEO (Low Earth Orbit). Additionally, the beam size in the NTN is, for example, 3500 km in the case of GEO and 1000 km in the case of LEO.

[0044] Figure 3 This is a diagram illustrating example (3) of NTN. For example... Figure 3 As shown, NTN is achieved by satellites in space or spacecraft in the air. For example, a GEO satellite can be a satellite in a geostationary orbit at an altitude of 35,786 km. For example, a LEO satellite can be a satellite at an altitude of 500-2000 km and orbiting with a period of 88-127 minutes. For example, a HAPS (High Altitude Platform Station) can be a spacecraft at an altitude of 8-50 km that hovers in orbit.

[0045] like Figure 3 As shown, GEO satellites, LEO satellites, and HAPS spacecraft can connect to the ground station gNB via a gateway. Furthermore, the service area can be expanded in the order of HAPS, LEO, and GEO.

[0046] For example, NTN can extend the coverage of 5G networks to non-service areas or service areas. Additionally, NTN can improve the continuity, availability, and reliability of services in ships, buses, trains, or other critical communications. Furthermore, NTN can be notified by sending dedicated parameters to terminal 20; these dedicated parameters could be, for example, parameters related to the determination of Timing Advance (TA) based on satellite or aircraft information.

[0047] Figure 4 The diagram shows an example (4) of NTN. Figure 4 This illustrates an example of an NTN network architecture conceived as a transparent payload. Figure 4 As shown, the CN (Core Network) 10D, gNB10C, and gateway 10B are connected. Gateway 10B is connected to satellite 10A via a feeder link. Satellite 10A is connected to terminal 20A or VSAT (Very Small Aperture Terminal) 20B via a service link. NR Uu is established between gNB10C and terminal 20A or VSAT 20B.

[0048] Furthermore, the network architecture of NTN can be either FDD or TDD. Additionally, the terrestrial cells can be fixed or mobile. Furthermore, terminal 20 can also have GNSS (Global Navigation Satellite System) support capabilities. For example, in FR1, a power level 3 handheld device can also be envisioned. Moreover, at least in FR2, a VSAT device can also be envisioned.

[0049] Furthermore, the NTN network architecture can also envision regenerative payloads. For example, gNB functionality could be carried on satellites or spacecraft. Alternatively, gNB-DU could be carried on satellites or spacecraft, while gNB-CU could be configured as a ground station.

[0050] Figure 5 This is a diagram used to illustrate an example of timing advance in NTN. For example... Figure 5As shown, the TA in the NTN includes a common TA corresponding to the distance from satellite / HAPS10A to the reference point (RP) in the feeder link, and a UE-specific TA corresponding to the distance from satellite / HAPS10A to UE20 in the serving link. The TA of the serving link is the UE-specific TA, which varies depending on the location of UE20. Additionally, the feeder link includes a user-transparent delay corresponding to the distance from the reference point to gNB / gateway 10B.

[0051] The reference point used for UL synchronization can be determined through network implementation. For example, the reference point can be any location on a satellite, gNB, GW, or feeder link. In a gNB or GW, for ease of implementation, the time domains of DL and UL can be consistent. In a satellite, to reduce UE load, UE actions related to common TA can be omitted.

[0052] In NTN, TA can be, for example, through T. TA =(N TA +N TA,UE-specific +N TA,common +N TA,offset )×T C To calculate (refer to non-patent literature 4).

[0053] N TA In the case of PRACH, the value is 0, which is notified via TA commands based on MAC-CE (Medium Access Control-ControlElement). TA It can be a closed-loop TA.

[0054] N TA,UE-specific It is the TA inherent to the UE. N TA,UE-specific This could be a value estimated by the UE within its own device to compensate for service link delays in advance. TA,UE-specific It is calculated based on the UE's location and the celestial positions of the serving satellites.

[0055] N TA,common It is a shared TA controlled by the network. N will also be referred to below. TA,common This is called the common TA. For example, in the case where the reference point is a satellite, the supported value is 0. N TA,offset It can be a fixed value specified in the specification for TA calculation.

[0056] Figure 6 This is a timing diagram illustrating an example of UL synchronization in NTN. Figure 6This is an example of establishing synchronization between gNB10 and UE20 during Phase 1 of the initial access and RACH (random access) procedures and Phase 2 of the RRC_CONNECTED state.

[0057] The following describes the actions in Phase 1. In step S101, gNB10 sends the SSB to UE20. UE20 performs DL time-frequency synchronization to detect the MIB. In the next step S102, gNB10 sends CORESET#0 to UE20. Based on CORESET#0, UE20 detects the SIB and obtains the PRACH resources, parameters related to the public TA, satellite positions, and epoch time contained in the SIB.

[0058] In the next step S103, based on the common TA obtained from the SIB and the self-estimated UE-specific TA, a RACH preamble as Msg1 or MsgA is sent to gNB10. In the next step S104, gNB10 sends a RAR containing a TA command as Msg2 or MsgB to UE20. UE20 performs UL synchronization using the common TA, the UE-specific TA, and the TA command contained in the RAR.

[0059] The following describes the actions in Phase 2. In step S201, the MAC-CE containing the TA command is sent to UE20. UE20 performs UL synchronization using the common TA, the UE-specific TA, and the TA command contained in the MAC-CE. In step S202, the UE receives or uses dedicated signaling via SIB to update the common TA parameters, satellite and celestial positions, and epoch time.

[0060] Figure 7 This is a diagram used to illustrate example (1) of the common TA in NTN. For example... Figure 7 As shown, the required TA corresponding to the time from UL transmission time to DL reference time becomes the τ corresponding to the time from UE to satellite contained in the UE's inherent TA. s,UL The τ contained in the public TA corresponds to the time from the satellite to the reference point. c,UL The public TA contains τ corresponding to the time from the reference point to the satellite. c,DL and the τ corresponding to the time from the satellite to the UE contained in the UE's inherent TA. s,DL sum.

[0061] Figure 8This is a diagram used to illustrate the common TA in NTN (2). The common TA is calculated based on the NTN's inherent SIB and the common TA parameters based on individual signaling. The common TA parameters can be the common TA, the common TA drift rate (1st-order derivative), or the common TA drift rate variation (2nd-order derivative).

[0062] The satellite's motion changes over time. The values ​​of the notified parameters are based on the reference time assigned by the epoch time. The UE can estimate the common TA for a given period based on the notified parameters. The notified parameters are received or updated within a valid period. For example, such as... Figure 8 As shown, Taylor expansion can also be used to estimate the TA over time as it progresses from the maximum elevation angle to the minimum elevation angle.

[0063] N TA,common By using a one-way propagation delay common (t) is derived from the UE implementation. Delay common (t) is the value obtained by dividing the distance between the satellite and the reference point for UL time synchronization by the speed of light. TA,common Not Delay common (t) is twice that of N. This is because the DL propagation delay and UL propagation delay become different values ​​depending on the satellite's motion. For UL transmission, the UE implementation determines which t value (e.g., UE transmission timing, satellite transmission timing, etc.) is used for N. TA,common The calculation.

[0064] The calculation formula based on Taylor sets is as follows.

[0065] .

[0066] In addition, TA common / 2 is Delay common (t) epoch The zeroth derivative coefficient of . TA commonDrift / 2 is Delay common (t) epoch The first-order differential coefficient of TA. commonDriftVariation / 2 is Delay common (t) epoch The second derivative coefficients of ). The network's response to TA. common Send a signaling notification. TA commonDrift TA commonDriftVariationFor example, it can be signaled based on the NTN type as an option.

[0067] Figure 9 This diagram illustrates an example of the UE-inherent TA in an NTN. The delay of bidirectional transmission between the satellite and the UE varies for each UE. Figure 9 As shown, the UE's inherent TA is calculated based on the location of its own GNSS-based device and the celestial position of the serving satellite. Parameters related to the celestial position of the serving satellite are communicated via the NTN's inherent SIB and dedicated signaling. Detailed methods for calculating the UE's inherent TA can also be implemented on the UE itself.

[0068] like Figure 9 As shown in A1, A2, and A3, the satellite's motion changes over time. The values ​​of the notified parameters are the values ​​at the reference time assigned by the epoch time. The UE can estimate its inherent TA for a given period based on the notified parameters. The notified parameters are received or updated within a valid period. Parameters related to the celestial position of the serving satellite are notified through format 1 of the satellite position and velocity state vector, or format 2 of the orbital parameters in the celestial position format. Format 1 and format 2 are equivalent and can be transformed from one to the other using Kepler's equations.

[0069] In this NTN, it is assumed that GNSS information is always available in each UE, and synchronization is performed based on this GNSS information. As mentioned above, the UE's inherent TA is derived from the UE's location and the celestial positions of the satellites. Therefore, if the UE cannot utilize GNSS information, it is not allowed to perform UL transmission.

[0070] However, in reality, GNSS information may not be available; it is assumed that GNSS information is at least temporarily unavailable. Therefore, the actions of the UE and / or the network in cases where GNSS information cannot be utilized can be specified.

[0071] Figure 10 This is a flowchart illustrating an action example (1) in an embodiment of the present invention. In step S101, the UE determines whether the GNSS information is unavailable. If it is unavailable (S101 is "Yes"), the process proceeds to step S102; if it is not unavailable (S101 is "No"), the process proceeds to step S103.

[0072] In step S102, the UE determines its location information using a predetermined method. Conversely, in step S103, the UE uses GNSSS information as its location information.

[0073] In step S104, the UE calculates its inherent TA based on its location information. In step S105, the UE uses its inherent TA to perform UL synchronization and UL transmission.

[0074] Figure 11 This is a flowchart illustrating an action example (2) in an embodiment of the present invention. In step S201, the base station and / or UE determines whether GNSS information is unavailable. If it is unavailable (S201 is "Yes"), the process proceeds to step S202; if it is not unavailable (S202 is "No"), the process ends. In step S202, the base station and / or UE performs predetermined actions related to TA calculation.

[0075] For example, when GNSS information is unavailable, actions 1) to 11) as shown below can also be performed.

[0076] Action 1) Use past GNSS information.

[0077] Operation 2) Use the location information predicted by the UE.

[0078] Action 3) Import more dynamic notifications.

[0079] Action 4) Notification sending prohibited.

[0080] Action 5) Notify the UE of location information determined based on location using RAT (Radio Access Technology) from the gNB or LMF.

[0081] Action 6) Calculate the location on the UE side based on the RAT-dependent positioning.

[0082] Action 7) The gNB notifies the UE of the location of the beam associated with the UE.

[0083] Action 8) Import notification of larger values.

[0084] Action 9) Report to gNB that GNSS is temporarily unavailable.

[0085] Action 10) Notify UEs that GNSS is temporarily unavailable, whether or not it is permitted.

[0086] Action 11) is a combination of Action 1) and Action 10).

[0087] Actions 1) through 11) above can be applied to any of the modes or states of RRC_IDLE, RRC_INACTIVE, or RRC_CONNECTED. Furthermore, actions 1) through 11) above can be applied to actions during initial access and / or handover.

[0088] The following explanation uses past GNSS information for action 1). Action 1) can also be performed using... Figure 10 or Figure 11 The flowchart shown is used to execute the procedure.

[0089] For example, the UE can continue to use the preceding GNSS information. The UE can continue using the preceding GNSS information as described in 1) or 2) below, or it can terminate the operation.

[0090] 1) The UE can start a timer or counter when GNSS information becomes unavailable. The period from start to end of a timer or the period from start to reach a predetermined value of a counter can be defined and set. For example, this period can be set using the parameter GNSS-ValidityDuration::=ENUMERATED{s10, s20, s30, s40, s50, s60, min5, min10, min15, min20, min25, min30, min50, min90, min120, infinity}. Additionally, s10 refers to 10 minutes, min5 refers to 5 minutes, and so on. The values ​​applied to this period can be determined based on conditions specified by the UE speed, SCS, satellite type, etc., or based on corresponding parameters.

[0091] The UE can use the preceding GNSS information to calculate its inherent TA and perform communication until a timer expires or a counter reaches a predetermined value. After the timer expires or the counter reaches the predetermined value, but before the GNSS information becomes available, the UE may not perform communication. That is, in the RRC_CONNECTED state, the RRC connection can be released, and in the RRC_IDLE state, transmissions for the RRC connection may not be performed.

[0092] Alternatively, the timer or counter can be initialized and stopped at the point when the GNSS information becomes available, before the timer expires or the counter reaches a predetermined value.

[0093] 2) The UE can use the preceding GNSS information to calculate its inherent TA and perform communication until it receives notification from base station 10 or gNB. After receiving this notification, and before the GNSS information becomes available, the UE may choose not to perform communication. That is, in the RRC_CONNECTED state, the RRC connection can be released, and in the RRC_IDLE state, transmissions for the RRC connection can be omitted.

[0094] For this notification, a DCI format or field for prohibiting transmission can also be defined. This DCI format or field can be UE-specific signaling or group common signaling accompanying a specific RNTI. The UE can also apply a UL-related transmission prohibition after a period T has elapsed since receiving the DCI format or field. Period T can be the processing time between DL allocation and PUCCH, or the processing time between UL authorization and PUSCH, and can be defined for UL revocation or for this notification. Furthermore, the signaling used for this notification is not limited to a DCI format or field; for example, it can also be MAC-CE. If a predetermined value is notified in the TAC of the MAC-CE or DCI, the UE can determine that it has received the transmission prohibition notification.

[0095] Through the aforementioned action 1), even when GNSS information is unavailable, the UE can determine its location information and calculate its inherent TA within a predetermined period.

[0096] The following explains action 2) using the location information predicted by the UE. Action 2) can also be performed via... Figure 10 or Figure 11 The flowchart shown is used to execute the procedure.

[0097] The UE may have the ability to predict its own location information and may also report this ability to the base station 10 or gNB. When GNSS information is available, the UE may periodically or non-periodically report the predicted location information and / or GNSS information to the base station 10 or gNB. When GNSS information is unavailable, the UE may periodically or non-periodically report the predicted location information to the base station 10 or gNB.

[0098] The above report can be triggered or activated by base station 10 or gNB (e.g., receiving notification), or it can be triggered or activated after a period T (e.g., Xms, Xs, Xmin) elapses from the time when the GNSS information becomes unusable.

[0099] The method by which a UE predicts its own device location information can be defined, specified, implemented by the UE, determined by the base station 10 or gNB, or notified by the base station 10 or gNB.

[0100] For example, the UE can continue to perform actions using the predicted location information of its own device as described in 1) or 2) below, or it can terminate the operation.

[0101] 1) The UE can start a timer or counter when GNSS information becomes unavailable. The period from start to end of the timer or the period from start to reach a predetermined value of the counter can be defined or set. For example, this period can be set using the parameter GNSS-ValidityDuration::=ENUMERATED{s10, s20, s30, s40, s50, s60, min5, min10, min15, min20, min25, min30, min50, min90, min120, infinity}. Additionally, s10 refers to 10 minutes, min5 refers to 5 minutes, and so on. The values ​​applied to this period can be determined based on conditions specified by the UE speed, SCS, satellite type, etc., or based on corresponding parameters.

[0102] The UE can use its predicted location information to calculate the TA and perform communication until the timer expires or the counter reaches a predetermined value. After the timer expires or the counter reaches the predetermined value, but before the GNSS information becomes available, the UE may choose not to perform communication. That is, in the RRC_CONNECTED state, the RRC connection can be released, and in the RRC_IDLE state, transmissions for the RRC connection may not be performed.

[0103] Alternatively, the timer or counter can be initialized and stopped at the point when the GNSS information becomes available, before the timer expires or the counter reaches a predetermined value.

[0104] 2) The UE can use its predicted location information to calculate its inherent TA and perform communication until it receives notification from base station 10 or gNB. After receiving this notification, and before GNSS information becomes available, the UE may choose not to perform communication. That is, in the RRC_CONNECTED state, the RRC connection can be released, and in the RRC_IDLE state, transmissions for the RRC connection can be omitted.

[0105] For this notification, a DCI format or field for prohibiting transmission can also be defined. This DCI format or field can be UE-specific signaling or group common signaling accompanying a specific RNTI. The UE can also apply a UL-related transmission prohibition after a period T has elapsed since receiving the DCI format or field. Period T can be the processing time between DL allocation and PUCCH, or the processing time between UL authorization and PUSCH, and can be defined for UL revocation or for this notification. Furthermore, the signaling used for this notification is not limited to a DCI format or field; for example, it can also be MAC-CE. If a predetermined value is notified in the TAC of the MAC-CE or DCI, the UE can determine that it has received the transmission prohibition notification.

[0106] Through the above action 2), even when GNSS information is unavailable, it is possible to predict the UE's location information and calculate the UE's inherent TA within a predetermined period.

[0107] The following explains action 3) importing more dynamic notifications. Action 3) can also be done through... Figure 10 or Figure 11 The flowchart shown is used to execute the procedure.

[0108] To execute this dynamic notification, the DL allocation and / or UL authorization may include a Timing Advance Command (TAC) field. For example, DCI formats 1_0 and 0_0, and / or 1_1 and 0_1, and / or other DCI formats may include a TA command. The UE may apply the TA command from the UL transmission corresponding to the DCI format, or from the UL transmission after a period T following the receipt of the DCI format. The period T can be the processing time between the DL allocation and the PUCCH, or the processing time between the UL authorization and the PUSCH, or it can be defined for this notification.

[0109] To execute this dynamic notification, a DCI format or field for the TA command can be defined. This DCI format or field can be UE-specific signaling or group common signaling accompanying a specific RNTI. The UE can also send an application TA command to the UL after a period T has elapsed since receiving the DCI format or field. Period T can be the processing time between DL allocation and PUCCH, or the processing time between UL authorization and PUSCH, and can also be defined for this dynamic notification.

[0110] The TA commands contained in the DCI format used by this dynamic notification may have the characteristics shown in 1) to 4).

[0111] 1) It can be an absolute value (e.g., 12 bits) or a relative value (e.g., 6 bits).

[0112] 2) The range of values ​​can be the same as or different from the TA commands contained in MAC-CE or RAR.

[0113] 3) The range of values ​​can be positive values ​​including 0, or positive or negative values ​​including 0.

[0114] 4) A set of functions f(t) for TA commands can also be defined or set. A single f(t) within this set can also be notified. Furthermore, time t can be... n UL sending application f(t) n ).

[0115] This dynamic notification can also be activated only when GNSS information becomes unavailable.

[0116] Furthermore, the UE can perform UL transmission by applying a TA command based on this dynamic notification when GNSS information becomes unavailable. Additionally, the base station 10 can generate the TA command for the dynamic notification by estimating the UE's location information. Moreover, the UE can calculate its inherent TA based on the TA command for the dynamic notification.

[0117] Through action 3) described above, when GNSS information becomes unavailable, the UE can continue UL transmission by more dynamically notifying the TA command.

[0118] The following explains the prohibition of notification sending for action 4). Action 4) can also be performed via... Figure 10 or Figure 11 The flowchart shown is used to execute the procedure.

[0119] A transmission prohibition notification can be sent to the UE. Before receiving the transmission prohibition notification from base station 10 or gNB, the UE can use its predicted location information to calculate its inherent TA and perform communication. After receiving the notification, and before GNSS information becomes available, the UE may also choose not to perform communication. That is, in the RRC_CONNECTED state, the RRC connection can be released, and in the RRC_IDLE state, transmissions for the RRC connection can be suspended.

[0120] For this notification, a DCI format or field for prohibiting transmission can also be defined. This DCI format or field can be UE-specific signaling or group common signaling accompanying a specific RNTI. The UE can also apply a UL-related transmission prohibition after a period T has elapsed since receiving the DCI format or field. Period T can be the processing time between DL allocation and PUCCH, or the processing time between UL authorization and PUSCH, and can be defined for UL revocation or for this notification. Furthermore, the signaling used for this notification is not limited to a DCI format or field; for example, it can also be MAC-CE. If a predetermined value is notified in the TAC of the MAC-CE or DCI, the UE can determine that it has received the transmission prohibition notification.

[0121] Through the above action 4), the UE can perform UL transmission before being notified of transmission prohibition and stop UL transmission after being notified, thus making the action explicit.

[0122] The following describes action 5) notifying the UE of location information determined based on RAT-dependent positioning or location determination from the gNB or LMF. Action 5) can also be performed via... Figure 10 or Figure 11 The flowchart shown is used to execute the procedure.

[0123] RAT-dependent localization can refer to location estimation methods based on E-CID (Enhanced-Cell ID), TDOA (Time Difference of Arrival), Round Trip Time (RTT), AoA (Angle of Arrival), and AoD (Angle of Departure). RAT-dependent localization and location determination based on network libraries can also be interchanged.

[0124] Location information can be accurate location information based on longitude and latitude, or location-related results obtained through measurement, calculation and / or determination, or auxiliary information or auxiliary parameters.

[0125] Location information can be associated with, for example, receive timing, send timing, and / or notification timing.

[0126] Action 5) may include some or all of the actions shown in a)-f) below.

[0127] a) The UE can perform location determination based on settings and / or notifications from the network database using gNB and / or LMF (Location Management Function).

[0128] (b) The gNB and / or LMF can send the UE's location information to the UE. The gNB and / or LMF can send the UE's location information to the UE periodically or non-periodically. When the UE is notified by the gNB and / or LMF that GNSS information is unavailable, or when location determination based on the network library settings and / or notifications from the gNB and / or LMF is completed, the gNB and / or LMF can send the UE's location information to the UE. The LMF can share the UE's location information with the gNB, or the gNB can transmit the UE's location information to the UE.

[0129] (c) When GNSS information is unavailable, the UE may use location information determined based on RAT-dependent positioning instead of GNSS information. Upon receiving updated location information from the gNB and / or LMF, the UE may use the updated location information after the time point at which it was received. Furthermore, regardless of whether GNSS information is available, location information determined based on RAT-dependent positioning may be used instead of GNSS information. For example, the decision to use GNSS information or location information determined based on RAT-dependent positioning may be based on notifications from the gNB and / or LMF.

[0130] d) UEs that do not support RAT-dependent positioning may also be denied network access.

[0131] e) The parameters used to calculate the UE's inherent TA can be assigned the same parameters as those of the common TA to replace the UE's location information. The parameters of the common TA can be, for example, differential coefficients of order 0, 1, 2, ...

[0132] f) The UE may start a timer or counter at the time it receives location information determined based on the RAT-dependent positioning from the gNB and / or LMF. The period from the start of the timer until its expiration or the period from the start of the counter until it reaches a predetermined value can be defined and set.

[0133] The UE can use the location information determined based on the RAT-dependent positioning to calculate its inherent TA and perform communication until the timer expires or the counter reaches a predetermined value. After the timer expires or the counter reaches the predetermined value, and before the GNSS information becomes available, the UE may not perform communication.

[0134] Before the timer expires or the counter reaches a predetermined value, when GNSS information becomes available, the UE can initialize or stop the timer or counter at the point when it becomes available. Upon acquiring new location information based on RAT-dependent positioning, the UE can restart the timer or counter.

[0135] Through the aforementioned action 5), when GNSS information cannot be utilized, the UE's inherent TA can be calculated and used by using location information based on RAT-dependent positioning.

[0136] The following explains action 6) on the UE side, calculating the location based on RAT-dependent positioning. Action 6) can also be performed via... Figure 10 or Figure 11 The flowchart shown is used to execute the procedure.

[0137] Action 6) may include some or all of the actions shown below a)-g).

[0138] a) The calculation of the location information on the UE side can be set or notified by the base station 10 or gNB.

[0139] b) The ability to report location information supported by the UE to the base station 10 or gNB.

[0140] c) The UE can receive a reference signal from the base station 10 or gNB and calculate its own device location information based on the received reference signal.

[0141] d) The UE can send a reference signal to the base station 10 or gNB, receive information corresponding to the reference signal from the base station 10 or gNB, and calculate its own device location information based on the received information.

[0142] e) The UE can receive auxiliary information (e.g., the transmission and reception times of the reference signal at the base station 10, gNB, satellite, or reference point, the transmission and reception power of the reference signal at the base station 10, gNB, satellite, or reference point, etc.) based on this auxiliary information.

[0143] f) can also be combined with c), d), and e above).

[0144] (g) The UE may start a timer or counter at the time when the location information is calculated or at the time when a reference signal or information is received from the gNB and / or LMF. The period from the start of the timer until its expiration or the period from the start of the counter until it reaches a predetermined value can be defined and set.

[0145] The UE can use the calculated location information to calculate its inherent TA and perform communication until the timer expires or the counter reaches a predetermined value. After the timer expires or the counter reaches the predetermined value, and before the GNSS information becomes available, the UE may not perform communication.

[0146] Before the timer expires or the counter reaches a predetermined value, when GNSS information becomes available, the UE can initialize or stop the timer or counter at the point when it becomes available. Upon recalculation of location information based on the RAT-dependent positioning, the UE can restart the timer or counter.

[0147] Through the aforementioned action 6), when GNSS information cannot be utilized, the UE's inherent TA can be calculated and used by using location information based on RAT-dependent positioning.

[0148] The following explains action 7) where the gNB notifies the UE of the location of the beam associated with the UE. Action 7) can also be performed via... Figure 10 or Figure 11 The flowchart shown is used to execute the procedure.

[0149] Action 7) may include some or all of the actions shown in a)-e) below.

[0150] a) Beam location can be broadcast via SIB or common signaling through beam index. When the UE is associated with beam #A of base station 10 or gNB, the UE can use the location information of beam #A or calculate the UE's inherent TA based on that location information.

[0151] (b) Beam location can also be notified via UE-specific signaling. The UE can use the notified beam location information or calculate its inherent TA based on that information.

[0152] c) The notified position included in the beam position can also refer to the beam's center position, the beam's reference point, the focal point of the beam's elliptical coverage area (footprint), the beam's edge point, etc. The notified beam position can be the beam position at the notified time point, or it can be a function of position f(t), or it can be at t... n Application of f(t) in UL transmission at a specific time point n ).

[0153] d) The parameters used to calculate the beam-inherent TA or UE-inherent TA can be assigned the same parameters as the common TA to replace the beam position. The parameters of the common TA can be, for example, 0th, 1st, 2nd, ... differential coefficients.

[0154] e) In action 7), “beam” can also be replaced with “cell”.

[0155] Through the aforementioned action 7), when GNSS information cannot be utilized, the UE's inherent TA can be calculated and used by using location information related to the associated beam.

[0156] The following explains action 8) which involves importing a notification for a larger value. Action 3) can also be done via... Figure 10 or Figure 11 The flowchart shown is used to execute the procedure.

[0157] The value of a TA command larger than the usual or existing TA command can also be notified via MAC-CE. A separate MAC-CE can be defined for notifying larger TA command values. When reporting the UE's capability to support this separate MAC-CE to base station 10, the UE can receive this separate MAC-CE from base station 10. The TA command in this separate MAC-CE can be composed of, for example, 20 to 24 bits in absolute values, and, for example, 14 bits in relative values.

[0158] To notify of a larger TA command value, reserved bits of an existing MAC-CE can also be used. When reporting to base station 10 the UE's capability to support TA commands using the reserved bits of the existing MAC-CE, the UE can receive the independent MAC-CE from base station 10. The TA command in the MAC-CE using the reserved bits of the existing MAC-CE can, for example, consist of 13 to 16 bits in absolute value.

[0159] You can also define or set a set of functions f(t) for TA commands with larger values. You can also notify one f(t) in this set. You can also specify time t. n UL sending application f(t) n ).

[0160] Additionally, when GNSS information becomes unavailable, the UE can apply a TA command to notify the larger value to perform UL transmission. Alternatively, the base station 10 can also generate a TA command to notify the larger value by estimating the UE's location information.

[0161] Through the aforementioned action 8), when GNSS information cannot be utilized, transmission can continue by notifying and using a larger TA command.

[0162] The following explains action 9) reporting to the gNB that GNSS is temporarily unavailable. Action 9) can also be performed via... Figure 10 or Figure 11 The flowchart shown is used to execute the procedure.

[0163] When GNSS information becomes unavailable, the UE can report this to base station 10 or gNB. Conversely, when GNSS information becomes available, the UE can report this to base station 10 or gNB.

[0164] For the signaling of this report, a periodic PUCCH resource can also be set up, similar to an SR (scheduling request), to send the PUCCH when GNSS information becomes unavailable or when GNSS information becomes available. For example, when GNSS information becomes unavailable, the PUCCH can be used to notify a value of 0, and when GNSS information becomes available, the PUCCH can be used to notify a value of 1.

[0165] In addition, a separate MAC-CE can be defined for the signaling of this report. A PUSCH carrying this MAC-CE can be sent when GNSS information becomes unavailable or when GNSS information becomes available.

[0166] The information contained in the report may include, for example, the period during which GNSS is available, the time when GNSS information becomes unavailable or becomes available again, and the predicted period during which GNSS becomes temporarily unavailable.

[0167] Through the aforementioned action 9), the base station 10 or gNB can determine whether the UE can utilize GNSS information or not, and appropriately control the UE.

[0168] The following explains action 10) notifying a UE that GNSS is temporarily unavailable. Action 10) can also be performed via... Figure 10 or Figure 11 The flowchart shown is used to execute the procedure.

[0169] Base station 10 or gNB can broadcast via SIB whether a UE temporarily unable to utilize GNSS is permitted or prohibited from UL transmission or connection to the cell. All UEs cap-on in the cell broadcasting the SIB can comply with this broadcast.

[0170] Base station 10 or gNB can notify UEs that are temporarily unable to use GNSS to perform UL transmissions or connect to the cell via UE-specific signaling (e.g., RRC parameters). UEs that receive this notification can also comply with it.

[0171] When a UE is notified that its GNSS information has become unavailable, the system can also notify whether or not the UE, whose GNSS is temporarily unavailable, is allowed to transmit UL data or connect to the cell. If no notification is given regarding whether or not the UE, whose GNSS is temporarily unavailable, is allowed to transmit UL data or connect to the cell, the system can be assumed to allow or disallow the UE to transmit UL data or connect to the cell.

[0172] Through the aforementioned action 10), the base station 10 or gNB can appropriately control the UE by allowing or disallowing UL transmission when the UE cannot utilize GNSS information.

[0173] The following explains the combination of actions 11) and 10). Action 11) can also be performed by... Figure 10 or Figure 11 The flowchart shown is used to execute the procedure.

[0174] For example, actions 10), 9), 3), and 1) can be performed in combination. That is, the UE can report to base station 10 or gNB that GNSS is temporarily unavailable. The UE with temporarily unavailable GNSS is allowed to transmit UL or connect to the cell, and the UE continues to use past (e.g., immediately preceding) GNSS information to notify TA commands via DCI in the case of temporarily unavailable GNSS. Alternatively, other combinations of the same actions can also be used.

[0175] Through the above operation 11), when GNSS information cannot be used, the base station 10 or gNB can perform appropriate control over the UE, and the UE can continue to transmit UL.

[0176] According to the above embodiments, even when GNSS information is unavailable in the NTN environment, terminal 20 can still calculate TA and perform UL synchronization.

[0177] That is, uplink synchronization can be performed in an NTN (Non-Terrestrial Network) system.

[0178] (Device structure)

[0179] Next, an example of the functional structure of the base station 10 and terminal 20 performing the processes and actions described above will be explained. The base station 10 and terminal 20 include the functions implemented in the above embodiments. However, the base station 10 and terminal 20 may each possess only a portion of the functions described in the embodiments.

[0180] <Base Station 10>

[0181] Figure 12 This is a diagram illustrating an example of the functional structure of base station 10 in an embodiment of the present invention. For example... Figure 12 As shown, the base station 10 has a transmitting unit 110, a receiving unit 120, a setting unit 130 and a control unit 140. Figure 12 The functional structure shown is merely an example. As long as the actions involved in the embodiments of this invention can be performed, the functional distinctions and names of the functional units can be arbitrary.

[0182] The transmitting unit 110 includes the function of generating a signal to be transmitted to the terminal 20 and wirelessly transmitting the signal. Additionally, the transmitting unit 110 transmits inter-network node messages to other network nodes. The receiving unit 120 includes the function of receiving various signals transmitted from the terminal 20 and obtaining, for example, higher-level information from the received signals. Furthermore, the transmitting unit 110 has the function of transmitting NR-PSS, NR-SSS, NR-PBCH, DL / UL control signals, etc., to the terminal 20. Additionally, the receiving unit 120 receives inter-network node messages from other network nodes.

[0183] The setting unit 130 stores preset setting information and various setting information sent to the terminal 20. The content of the setting information includes, for example, information related to communication in the NTN.

[0184] As described in the embodiment, the control unit 140 performs control related to communication in the NTN. Furthermore, the control unit 140 controls communication with the terminal 20 based on a UE capability report related to radio parameters received from the terminal 20. Alternatively, the signal transmission-related functions of the control unit 140 may be included in the transmitting unit 110, and the signal reception-related functions of the control unit 140 may be included in the receiving unit 120.

[0185] Terminal 20

[0186] Figure 13 This is a diagram illustrating an example of the functional structure of terminal 20 in an embodiment of the present invention. (See diagram for example.) Figure 13 As shown, the terminal 20 includes a transmitting unit 210, a receiving unit 220, a setting unit 230, and a control unit 240. Figure 13 The functional structure shown is merely an example. As long as the actions involved in the embodiments of this invention can be performed, the functional distinctions and names of the functional units can be arbitrary.

[0187] The transmitting unit 210 generates a transmission signal based on the transmission data and transmits the transmission signal wirelessly. The receiving unit 220 wirelessly receives various signals and obtains higher-layer signals from the received physical layer signals. Furthermore, the receiving unit 220 has the function of receiving NR-PSS, NR-SSS, NR-PBCH, DL / UL / SL control signals, etc., transmitted from the base station 10. For example, as D2D communication, the transmitting unit 210 transmits PSCCH (Physical Sidelink Control Channel), PSSCH (Physical Sidelink Shared Channel), PSDCH (Physical Sidelink Discovery Channel), PSBCH (Physical Sidelink Broadcast Channel), etc., to other terminals 20, and the receiving unit 120 receives PSCCH, PSSCH, PSDCH, or PSBCH from other terminals 20.

[0188] The setting unit 230 stores various setting information received from the base station 10 by the receiving unit 220. In addition, the setting unit 230 also stores preset setting information. The content of the setting information includes, for example, information related to communication in the NTN.

[0189] As described in the embodiment, the control unit 240 performs control related to communication in the NTN. Alternatively, the signal transmission-related functions of the control unit 240 may be included in the transmitting unit 210, and the signal reception-related functions of the control unit 240 may be included in the receiving unit 220.

[0190] (Hardware structure)

[0191] The block diagrams used in the description of the above embodiments ( Figure 12 as well as Figure 13 () represents a block of functional units. These functional blocks (components) are implemented through any combination of at least one of hardware and software. Furthermore, there are no particular limitations on the implementation method of each functional block. That is, each functional block can be implemented using a single device that is physically or logically combined, or by directly or indirectly (e.g., using wired, wireless, etc.) connecting two or more physically or logically separate devices. Functional blocks can also be implemented by combining software within one or more of the aforementioned devices.

[0192] The functions include judgment, decision, determination, calculation, calculation, processing, derivation, investigation, search, confirmation, receiving, sending, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assigning, but are not limited to these. For example, the functional block (structural part) that performs the sending function is called the transmitting unit or transmitter. In short, as mentioned above, there are no particular limitations on the implementation method.

[0193] For example, in one embodiment of this disclosure, the base station 10, terminal 20, etc., can also function as a computer for processing the wireless communication method of this disclosure. Figure 14 This is a diagram illustrating an example of the hardware structure of a base station 10 and a terminal 20 according to an embodiment of the present disclosure. The base station 10 and the terminal 20 described above can be configured as a computer device that physically includes a processor 1001, a storage device 1002, an auxiliary storage device 1003, a communication device 1004, an input device 1005, an output device 1006, and a bus 1007, etc.

[0194] Furthermore, in the following description, the term "device" can be replaced with "circuit," "device," "unit," etc. The hardware structure of base station 10 and terminal 20 can be configured to include one or more of the devices shown in the figures, or it can be configured to not include any of them.

[0195] The functions of base station 10 and terminal 20 are implemented by reading predetermined software (program) into hardware such as processor 1001 and storage device 1002, so that processor 1001 performs calculations and controls the communication of communication device 1004 or controls at least one of reading and writing data in storage device 1002 and auxiliary storage device 1003.

[0196] The processor 1001 controls the computer as a whole by instructing the operating system to operate. The processor 1001 may also be a central processing unit (CPU) that includes interfaces with peripheral devices, control units, arithmetic units, registers, etc. For example, the control unit 140 and control unit 240 described above can also be implemented using the processor 1001.

[0197] Additionally, the processor 1001 reads programs (program code), software modules, or data from at least one of the auxiliary storage devices 1003 and communication devices 1004, and performs various processes accordingly. As a program, a program is used that causes the computer to perform at least a portion of the actions described in the above embodiments. For example, Figure 12 The control unit 140 of the base station 10 shown can be implemented by a control program stored in the storage device 1002 and operated in the processor 1001. Alternatively, for example, Figure 13 The control unit 240 of the terminal 20 shown can also be implemented by a control program stored in the storage device 1002 and operated in the processor 1001. Although it has been described that the various processes described above are executed by one processor 1001, the various processes described above can also be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 can also be implemented by one or more chips. In addition, the program can also be sent from the network via a telecommunications line.

[0198] Storage device 1002 is a computer-readable recording medium, and may be composed of at least one of ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), etc. Storage device 1002 may also be referred to as a register, cache, main memory (main storage device), etc. Storage device 1002 can store programs (program code), software modules, etc., that are executable for implementing the communication method according to one embodiment of this disclosure.

[0199] The auxiliary storage device 1003 is a computer-readable recording medium, such as at least one of the following: CD-ROM (CompactDisc ROM) or other optical discs, hard disks, floppy disks, magneto-optical discs (e.g., compact discs, digital multifunction discs, Blu-ray discs, smart cards, flash memory (e.g., cards, sticks, key drives), floppy disks, magnetic stripes, etc. The aforementioned storage medium may, for example, be a database, server, or other suitable media that includes at least one of the storage device 1002 and the auxiliary storage device 1003.

[0200] Communication device 1004 is hardware (transceiver) used for communication between computers via at least one of a wired network and a wireless network. It is also referred to as a network device, network controller, network interface card (NIC), communication module, etc. Communication device 1004 may, for example, be configured to include high-frequency switches, duplexers, filters, frequency synthesizers, etc., to implement at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, transceiver antennas, amplifiers, transceiver units, transmission path interfaces, etc., can also be implemented using communication device 1004. The transceiver unit may also be physically or logically separated into a transmitting unit and a receiving unit.

[0201] Input device 1005 is an input device that accepts input from external sources (e.g., keyboard, mouse, microphone, switch, button, sensor, etc.). Output device 1006 is an output device that performs output to external sources (e.g., display, speaker, LED, etc.). Furthermore, input device 1005 and output device 1006 can also be integrated (e.g., a touch panel).

[0202] Furthermore, the processor 1001 and storage device 1002, among other devices, are connected via a bus 1007 for communicating information. The bus 1007 can be configured as a single bus or as different buses used between devices.

[0203] Furthermore, the base station 10 and the terminal 20 can be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), or a FPGA (Field Programmable Gate Array), and can also use this hardware to implement part or all of the functional blocks. For example, the processor 1001 can also be implemented using at least one of these hardware components.

[0204] Figure 15 An example of the structure of vehicle 2001 is shown. For example... Figure 15As shown, the vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a gearshift lever 2006, front wheels 2007, rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021-2029, an information service unit 2012, and a communication module 2013. The various forms / implementations described in this disclosure can also be applied to communication devices mounted on the vehicle 2001, for example, to the communication module 2013.

[0205] The drive unit 2002 may be composed, for example, an engine, a motor, or a hybrid power system of an engine and a motor. The steering unit 2003 includes at least a steering wheel (also called a steering wheel) and is configured to steer at least one of the front wheels and the rear wheels based on the operation of the steering wheel operated by the user.

[0206] The electronic control unit 2010 consists of a microprocessor 2031, a memory (ROM, RAM) 2032, and a communication port (I / O port) 2033. Signals from various sensors 2021 to 2029 of the vehicle 2001 are input to the electronic control unit 2010. The electronic control unit 2010 can also be referred to as an ECU (Electronic Control Unit).

[0207] The signals from various sensors 2021 to 2029 include current signals from current sensor 2021 that monitors motor current, speed signals of the front or rear wheels obtained by speed sensor 2022, air pressure signals of the front or rear wheels obtained by air pressure sensor 2023, vehicle speed signals obtained by vehicle speed sensor 2024, acceleration signals obtained by acceleration sensor 2025, accelerator pedal input signals obtained by accelerator pedal sensor 2029, brake pedal input signals obtained by brake pedal sensor 2026, gear lever operation signals obtained by gear lever sensor 2027, and detection signals obtained by object detection sensor 2028 for detecting obstacles, vehicles, pedestrians, etc.

[0208] The Information Service Unit 2012 comprises various devices such as a car navigation system, audio system, speakers, television, and radio, used to provide (output) various information such as driving information, traffic information, and entertainment information, and one or more ECUs that control these devices. The Information Service Unit 2012 uses information obtained from external devices via a communication module 2013, etc., to provide various multimedia information and multimedia services to the occupants of the vehicle 2001. The Information Service Unit 2012 may include input devices that accept input from external sources (e.g., keyboard, mouse, microphone, switch, button, sensor, touch panel, etc.) and output devices that perform output to external sources (e.g., display, speaker, LED lights, touch panel, etc.).

[0209] The Driver Assistance System 2030 comprises various devices used to prevent accidents or reduce driver workload, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning devices (e.g., GNSS), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps), gyroscope systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System)), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. Furthermore, the Driver Assistance System 2030 transmits and receives various information via the communication module 2013 to achieve driver assistance or autonomous driving functions.

[0210] The communication module 2013 can communicate with the microprocessor 2031 and the components of the vehicle 2001 via the communication port. For example, the communication module 2013 can send and receive data with the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, gear shift lever 2006, front wheel 2007, rear wheel 2008, axle 2009, microprocessor 2031 in the electronic control unit 2010, memory (ROM, RAM) 2032, and sensors 2021 to 2029 in the vehicle 2001 via the communication port 2033.

[0211] The communication module 2013, controlled by the microprocessor 2031 of the electronic control unit 2010, is a communication device capable of communicating with external devices. For example, it can transmit and receive various types of information with external devices via wireless communication. The communication module 2013 can be located inside or outside the electronic control unit 2010. External devices can be, for example, base stations, mobile stations, etc.

[0212] The communication module 2013 can wirelessly transmit to an external device at least one of the signals input to the electronic control unit 2010 from the various sensors 2021-2028, information obtained based on those signals, and information obtained via the information service unit 2012 based on input from an external source (user). The electronic control unit 2010, the various sensors 2021-2028, and the information service unit 2012 can also be referred to as input units that receive input. For example, the PUSCH transmitted by the communication module 2013 can contain information based on the aforementioned input.

[0213] The communication module 2013 receives various information (traffic information, signal information, vehicle-to-vehicle information, etc.) sent from external devices and displays it on the information service unit 2012 provided by the vehicle 2001. The information service unit 2012 can also be referred to as an output unit for outputting information (for example, outputting information to devices such as displays and speakers based on the PDSCH received by the communication module 2013 (or data / information decoded from the PDSCH). In addition, the communication module 2013 stores the various information received from external devices in a memory 2032 available to the microprocessor 2031. The microprocessor 2031 can also control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, gear lever 2006, front wheels 2007, rear wheels 2008, axles 2009, sensors 2021 to 2029, etc. provided by the vehicle 2001 based on the information stored in the memory 2032.

[0214] (Summary of implementation methods)

[0215] As described above, according to an embodiment of the present invention, a terminal is provided, comprising: a receiving unit that receives parameters and TA commands related to a common TA (Timing Advancement) for all users in the base station constituting an NTN (Non-Terrestrial Network); and a control unit that calculates the common TA based on the parameters, and performs uplink synchronization based on the TA commands, the calculated common TA, the device-specific TA, and an offset. When GNSS (Global Navigation Satellite System) information cannot be used, the control unit calculates the device-specific TA based on location information obtained based on RAT (Radio Access Technology).

[0216] With the above structure, in an NTN environment, even when GNSS information is unavailable, terminal 20 can still calculate TA and perform UL synchronization. That is, in an NTN (Non-Terrestrial Network) system, uplink synchronization can be performed.

[0217] Alternatively, when GNSS information is unavailable, the receiving unit receives its own location information from the base station, and the control unit uses this location information to calculate the device's inherent TA (Target Aspect Ratio). According to this structure, in an NTN (Network Neural Network) environment, even when GNSS information is unavailable, TA can be calculated and UL (Ultra-Low Length) synchronization can be performed.

[0218] Alternatively, when GNSS information is unavailable, the receiving unit receives parameters from the base station for calculating the device's inherent TA, and the control unit uses these parameters to calculate the device's inherent TA. According to this structure, in an NTN environment, even when GNSS information is unavailable, TA can be calculated and UL synchronization can be performed.

[0219] Alternatively, when GNSS information is unavailable, the control unit calculates its own location information and uses this location information to calculate the device's inherent TA (Tracking Time). According to this structure, even in an NTN environment where GNSS information is unavailable, TA can be calculated and UL (Ultra-Low Variable) synchronization can be performed.

[0220] Alternatively, the control unit can start a timer when GNSS information becomes unavailable, calculate its own device's position information, and use that position information to calculate the device's inherent TA (Tracking Time), until the timer expires. According to this structure, in an NTN environment, even when GNSS information is unavailable, TA can be calculated and UL (Ultra-Low Response) synchronization can be performed.

[0221] Furthermore, according to an embodiment of the present invention, a communication method is provided in which a terminal performs the following steps: receiving parameters and TA commands related to the common TA (Timing Advancement) of all users in the base station constituting an NTN (Non-Terrestrial Network); calculating the common TA based on the parameters, and performing uplink synchronization based on the TA command, the calculated common TA, the device-specific TA, and an offset; and calculating the device-specific TA based on location information when GNSS (Global Navigation Satellite System) information cannot be used, wherein the location information is obtained based on positioning dependent on RAT (Radio Access Technology).

[0222] With the above structure, in an NTN environment, even when GNSS information is unavailable, terminal 20 can still calculate TA and perform UL synchronization. That is, in an NTN (Non-Terrestrial Network) system, uplink synchronization can be performed.

[0223] (Supplement to the implementation method)

[0224] The embodiments of the present invention have been described above, but the disclosed invention is not limited to such embodiments. Those skilled in the art should understand various modifications, alterations, substitutions, and replacements. Specific numerical examples have been used to facilitate understanding of the invention, but unless otherwise specified, these values ​​are merely examples, and any appropriate values ​​may be used. The distinctions between items in the above description are not essential to the present invention. Items described in two or more items may be combined as needed, and items described in one item may be applied to items described in another item (as long as there is no contradiction). The boundaries of functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries of physical components. Multiple functional units may be operated by a single physical component, or a single functional unit may be operated by multiple physical components. Regarding the processing described in the embodiments, the order of processing may be interchanged unless there is a contradiction. For ease of explanation, a functional block diagram is used to illustrate the base station 10 and terminal 20, but such a device may also be implemented by hardware, software, or a combination thereof. The software operating according to the embodiments of the present invention via the processor of the base station 10 and the software operating according to the embodiments of the present invention via the processor of the terminal 20 may also be stored in random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, register, hard disk (HDD), removable disk, CD-ROM, database, server and other suitable storage media, respectively.

[0225] Furthermore, the notification of information is not limited to the forms / implementations described in this disclosure, and other methods may also be used. For example, information notification may be implemented through physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), higher layer signaling (e.g., RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling), broadcast information (MIB (Master Information Block), SIB (System Information Block)), other signals, or combinations thereof. Additionally, RRC signaling may be referred to as an RRC message, for example, it may also be an RRC Connection Setup message, an RRC Connection Reconfiguration message, etc.

[0226] The various forms / implementations described in this disclosure can also be applied to systems utilizing LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), FRA (Future Radio Access), NR (new Radio), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, UWB (Ultra-Wideband), Bluetooth (registered trademark), other suitable systems, and next-generation systems extended therefrom. Additionally, multiple systems can be combined (e.g., a combination of at least one of LTE and LTE-A with 5G, etc.) for application.

[0227] The processing procedures, timing, and flow of the various forms / implementations described in this specification may be rearranged in order, provided there is no contradiction. For example, the elements of various steps are indicated using an illustrative order for the methods described in this disclosure, but are not limited to the specific order indicated.

[0228] In this specification, certain actions performed by base station 10 may sometimes also be performed by its upper node, depending on the circumstances. In a network consisting of one or more network nodes having base station 10, it is obvious that various actions performed to communicate with terminal 20 can be performed by at least one of base station 10 and other network nodes besides base station 10 (e.g., considering MME or S-GW, but not limited to these). The above example illustrates the case where there is one other network node besides base station 10, but other network nodes can also be a combination of multiple other network nodes (e.g., MME and S-GW).

[0229] The information or signals described in this disclosure can be output from a higher (or lower) layer to a lower (or higher) layer. They can also be input or output via multiple network nodes.

[0230] Input or output information can be stored in a specific location (e.g., memory) or managed using a management table. Input or output information can be overwritten, updated, or appended. Output information can also be deleted. Input information can also be sent to other devices.

[0231] The determination in this disclosure can be made by a value represented by 1 bit (0 or 1), by a Boolean value (Boolean: true or false), or by a comparison of numerical values ​​(e.g., a comparison with a predetermined value).

[0232] Software, whether called software, firmware, middleware, microcode, hardware description language, or by other names, should be broadly interpreted as referring to commands, command sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc.

[0233] In addition, software, commands, information, etc., can be sent and received via a transmission medium. For example, when software is sent from a webpage, server, or other remote source using at least one of wired technologies (coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) etc.) and wireless technologies (infrared, microwave, etc.), at least one of these wired and wireless technologies is included within the definition of a transmission medium.

[0234] The information, signals, etc., described in this disclosure can also be represented using any of a variety of different technologies. For example, the data, commands, instructions, information, signals, bits, symbols, chips, etc., that may be involved in the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any combination of these.

[0235] Furthermore, the terms used in this disclosure and those necessary for understanding this disclosure may be replaced with terms that have the same or similar meanings. For example, at least one of the channel and symbol may also be a signal (signaling). Additionally, a signal may also be a message. Furthermore, a component carrier (CC) may also be referred to as carrier frequency, cell, frequency carrier, etc.

[0236] The terms “system” and “network” as used in this disclosure are used interchangeably.

[0237] Furthermore, the information, parameters, etc., described in this disclosure can be represented using absolute values, relative values ​​to predetermined values, or other corresponding information. For example, wireless resources can also be indicated using indexes.

[0238] The names used for the above parameters are non-limiting in any respect. Furthermore, the formulas, etc., using these parameters sometimes differ from those explicitly disclosed in this disclosure. Various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by all appropriate names, therefore the various names assigned to these channels and information elements are non-limiting in any respect.

[0239] In this disclosure, the terms "base station (BS)," "wireless base station," "base station device," "fixed station," "NodeB," "eNodeB (eNB)," "gNodeB (gNB)," "access point," "transmission point," "reception point," "transmission / reception point," "cell," "sector," "cell group," "carrier," and "component carrier" are used interchangeably. Sometimes, terms such as macro cell, small cell, femtocell, and picocell are also used to refer to base stations.

[0240] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, its coverage area can be divided into several smaller areas, each of which can also provide communication services through a base station subsystem (e.g., a small indoor base station (RRH: Remote Radio Head)). Terms such as "cell" or "sector" refer to a portion or all of the coverage area of ​​at least one of the base station and base station subsystem providing communication services within that coverage area.

[0241] In this disclosure, the base station sending information to the terminal can also be replaced by the base station instructing the terminal on information-based control / actions.

[0242] In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," and "terminal" are used interchangeably.

[0243] For mobile stations, those skilled in the art sometimes also use the following terms: subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handheld device, user agent, mobile client, client, or some other appropriate terms.

[0244] At least one of the base station and the mobile station can also be referred to as a transmitting device, a receiving device, a communication device, etc. Furthermore, at least one of the base station and the mobile station can also be a device mounted on a mobile body, the mobile body itself, etc. The mobile body refers to an object capable of movement, with an arbitrary speed. It also includes situations where the mobile body is stationary. Examples of mobile bodies include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, shovel cars, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, rear cars, rickshaws, ships and other watercraft, airplanes, rockets, artificial satellites, drones (registered trademark), multicopters, quadcopters, balloons, and objects mounted on them. Additionally, the mobile body can also be a mobile body that moves autonomously based on operating commands. This can be a means of transportation (such as a car, airplane, etc.), a mobile entity that moves unmanned (such as a drone, self-driving car, etc.), or a robot (humanized or unmanned). Furthermore, at least one of the base station and mobile station may also include a device that does not necessarily move during communication. For example, at least one of the base station and mobile station may be an IoT (Internet of Things) device such as a sensor.

[0245] Furthermore, the base station in this disclosure can also be replaced by a user terminal. For example, the communication between the base station and the user terminal can be replaced by communication between multiple terminals 20 (e.g., D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.), and various forms / implementations of this disclosure can also be applied. In this case, the terminal 20 can also be configured to have the functions of the base station 10 described above. In addition, terms such as "uplink" and "downlink" can be replaced with terms corresponding to communication between terminals (e.g., "side"). For example, uplink channel, downlink channel, etc. can also be replaced with side channel.

[0246] Similarly, the user terminal in this disclosure can also be replaced by a base station. In this case, the base station can also be configured to have the functions of the aforementioned user terminal.

[0247] The terms "determining" and "determining" as used in this disclosure sometimes encompass a variety of actions. For example, "determining" or "determining" may include actions such as judging, calculating, computing, processing, deriving, investigating, searching (e.g., searching in a table, database, or other data structure), and ascertaining, which are considered as actions of "determining" or "determining." Furthermore, "determining" or "determining" may include actions such as receiving (e.g., receiving information), transmitting (e.g., sending information), inputting, outputting, and accessing (e.g., accessing data in memory), which are considered as actions of "determining" or "determining." Moreover, "determining" or "determining" may include actions such as resolving, selecting, choosing, establishing, and comparing, which are considered as actions of "determining" or "determining." That is, "judgment" and "decision" can include matters that are considered as having been "judged" or "decided". In addition, "judgment (decision)" can also be replaced by "assuming", "expecting", "considering", etc.

[0248] The terms “connected,” “coupled,” or any variations thereof are intended to indicate any direct or indirect connection or combination between two or more elements, including cases where there is one or more intermediate elements between the two elements that are “connected” or “coupled.” The combination or connection between elements can be physical, logical, or a combination of these. For example, “access” can be used instead of “connected.” In the context of this disclosure, it can be understood that two elements are “connected” or “coupled” to each other using at least one of one or more wires, cables, and printed electrical connections, and, as some non-limiting and non-inclusive examples, using electromagnetic energy with wavelengths in the wireless frequency domain, microwave region, and light (including both visible and invisible regions) to “connect” or “couple” to each other.

[0249] The reference signal can be simply called RS (Reference Signal), or, depending on the standard applied, pilot.

[0250] As used in this disclosure, the word "based on" does not mean "based on only" unless otherwise expressly stated. In other words, the word "based on" means both "based on only" and "based on at least".

[0251] Any reference to elements using the designations "first," "second," etc., as used in this disclosure does not necessarily limit the number or order of these elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Therefore, references to the first and second elements do not imply that only two elements can be taken, or that the first element must precede the second element in any form.

[0252] Alternatively, the "unit" in the structure of the above devices can be replaced with "section", "circuit", "equipment", etc.

[0253] When the terms "include," "including," and their variations are used in this disclosure, these terms, like the term "comprising," imply inclusion. Furthermore, the term "or" as used in this disclosure does not refer to XOR.

[0254] A radio frame can consist of one or more frames in the time domain. Each frame in the time domain can be called a subframe. A subframe can also consist of one or more time slots in the time domain. A subframe can be a fixed duration (e.g., 1 ms) independent of the parameter set (numerology).

[0255] A parameter set can be communication parameters applied to at least one of the transmission and reception of a signal or channel. For example, a parameter set can represent at least one of the following: Subcarrier Spacing (SCS), bandwidth, symbol length, cyclic prefix length, Transmission Time Interval (TTI), number of symbols per TTI, radio frame structure, specific filtering processing performed by the transceiver in the frequency domain, and specific windowing processing performed by the transceiver in the time domain.

[0256] In the time domain, a time slot can be composed of one or more symbols (OFDM (Orthogonal Frequency Division Multiplexing) symbols, SC-FDMA (Single Carrier Frequency Division Multiple Access) symbols, etc.). A time slot can be a time unit based on a set of parameters.

[0257] A time slot can contain multiple mini-time slots. Each mini-time slot can consist of one or more symbols in the time domain. Additionally, a mini-time slot can also be called a sub-time slot. A mini-time slot can consist of fewer symbols than a time slot. PDSCH (or PUSCH) transmitted in time units larger than mini-time slots can be called PDSCH (or PUSCH) mapping type (type) A. PDSCH (or PUSCH) transmitted using mini-time slots can be called PDSCH (or PUSCH) mapping type (type) B.

[0258] Radio frames, subframes, time slots, mini-time slots, and symbols all represent time units for transmitting signals. Radio frames, subframes, time slots, mini-time slots, and symbols can each be referred to by other corresponding names.

[0259] For example, a subframe can be called a Transmission Time Interval (TTI), multiple consecutive subframes can also be called a TTI, and a time slot or a mini-time slot can also be called a TTI. That is, at least one of a subframe and a TTI can be a subframe (1ms) in existing LTE, a period shorter than 1ms (e.g., 1-13 symbols), or a period longer than 1ms. In addition, the unit representing TTI may not be called a subframe, but rather a time slot, mini-time slot, etc.

[0260] Here, TTI refers, for example, to the smallest unit of time for scheduling in wireless communication. For instance, in an LTE system, the base station schedules the allocation of radio resources (bandwidth, transmit power, etc., available to each terminal 20) in units of TTI. However, the definition of TTI is not limited to this.

[0261] The Time Interval (TTI) can be a unit of time for transmitting channel-coded data packets (transmission blocks), code blocks, codewords, etc., or it can be a processing unit such as scheduling or link adaptation. Furthermore, when a TTI is given, the actual time interval (e.g., the number of symbols) that the transmission block, code block, codeword, etc., are mapped to can be shorter than the TTI.

[0262] Furthermore, when one time slot or one mini time slot is referred to as a TTI, more than one TTI (i.e., more than one time slot or more than one mini time slot) can become the minimum time unit for scheduling. In addition, the number of time slots (mini time slots) constituting the minimum time unit for scheduling can also be controlled.

[0263] A TTI with a duration of 1ms can also be called a normal TTI (TTI in LTE Rel.8-12), a long TTI, a normal subframe, a long subframe, or a time slot. A TTI shorter than a normal TTI can also be called a shortened TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a mini time slot, a sub-time slot, or a time slot.

[0264] Furthermore, a long TTI (e.g., a typical TTI, a subframe, etc.) can be understood as a TTI with a duration of more than 1 ms, while a short TTI (e.g., a shortened TTI, etc.) can be understood as a TTI with a duration of less than a long TTI but more than 1 ms.

[0265] A resource block (RB) is a unit of resource allocation in both the time and frequency domains. In the frequency domain, it can contain one or more consecutive subcarriers. The number of subcarriers contained in an RB can be the same regardless of the parameter set, for example, it can be 12. The number of subcarriers contained in an RB can also be determined based on the parameter set.

[0266] In addition, the time domain of an RB can contain one or more symbols, which can be a time slot, a mini-time slot, a subframe, or a TTI in length. A TTI, a subframe, etc., can each be composed of one or more resource blocks.

[0267] In addition, one or more RBs can also be called Physical Resource Block (PRB), Sub-Carrier Group (SCG), Resource Element Group (REG), PRB Pair, RB Pair, etc.

[0268] In addition, a resource block can consist of one or more resource elements (REs). For example, one RE can be a radio resource area consisting of one subcarrier and one symbol.

[0269] The Bandwidth Part (BWP) (also known as partial bandwidth, etc.) can also represent a subset of contiguous common resource blocks (RBs) used for a certain parameter set in a certain carrier. Here, common RBs can be determined by indexing RBs based on a common reference point of that carrier. PRBs can be defined and numbered within a BWP.

[0270] A BWP can include a UL BWP and a DL BWP. One or more BWPs can be set for a UE within a single carrier.

[0271] At least one of the configured BWPs can be active, and it is not assumed that the UE will transmit or receive predetermined signals / channels outside of the active BWP. Furthermore, the terms "cell," "carrier," etc., used in this disclosure can be replaced with "BWP."

[0272] The structures of radio frames, subframes, time slots, mini-time slots, and symbols described above are merely illustrative. For example, the number of subframes contained in a radio frame, the number of time slots in each subframe or radio frame, the number of mini-time slots contained in a time slot, the number of symbols and RBs contained in a time slot or mini-time slot, the number of subcarriers contained in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, and other structures can be varied in many ways.

[0273] In this disclosure, for example, in cases where articles are added through translation, such as in English (e.g., a, an, and the), this disclosure may also include cases where the noun following these articles is in a plural form.

[0274] In this disclosure, the phrase "A and B are different" can mean "A and B are not the same." Furthermore, this phrase can also mean "A and B are each different from C." Terms such as "separate" and "combined" can also be interpreted in the same way as "different."

[0275] The various forms / implementations described in this disclosure can be used individually, in combination, or switched between each other during execution. Furthermore, the notification of predetermined information (e.g., a "It is X" notification) is not limited to being explicit, but can also be implicit (e.g., not notifying the predetermined information).

[0276] The present disclosure has been described in detail above, but it will be clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented as modifications and variations without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the present disclosure is for illustrative purposes only and is not intended to be limiting.

[0277] Label Explanation

[0278] 10 base stations

[0279] 110 Dispatch Department

[0280] 120 Receiving Department

[0281] 130 Setting Department

[0282] 140 Control Department

[0283] 20 terminals

[0284] 210 Sending Department

[0285] 220 Receiving Department

[0286] 230 Setting Department

[0287] 240 Control Department

[0288] 1001 processor

[0289] 1002 Storage device

[0290] 1003 Auxiliary storage device

[0291] 1004 Communication device

[0292] 1005 Input Device

[0293] 1006 Output Device

[0294] Vehicle 2001

[0295] 2002 Drive Unit

[0296] 2003 Steering Unit

[0297] 2004 Accelerator Pedal

[0298] 2005 Brake Pedal

[0299] 2006 gearshift lever

[0300] 2007 front wheel

[0301] 2008 rear wheel

[0302] 2009 axle

[0303] 2010 Electronic Control Department

[0304] 2012 Information Service Department

[0305] 2013 Communication Module

[0306] 2021 Current Sensor

[0307] 2022 Speed ​​Sensor

[0308] 2023 Barometric Pressure Sensor

[0309] 2024 vehicle speed sensor

[0310] 2025 Accelerometer

[0311] 2026 Brake Pedal Sensor

[0312] 2027 Gearshift sensor

[0313] 2028 Object Detection Sensor

[0314] 2029 Accelerator Pedal Sensor

[0315] 2030 Driver Assistance Systems Department

[0316] 2031 microprocessor

[0317] 2032 Memory (ROM, RAM)

[0318] 2033 Communication Port (IO Port)

Claims

1. A terminal having: The receiving unit receives from the base stations constituting the NTN (Non-Terrain Network) parameters and TA commands related to the timing advance common to all users in the base stations; and The control unit calculates a common transition time (TA) based on the parameters, and performs uplink synchronization based on the TA command, the calculated common TA, the device-specific TA, and the offset. When GNSS information, i.e., Global Navigation Satellite System information, cannot be used, the control unit calculates the device's inherent TA based on the location information, wherein... This location information is obtained based on location technology that relies on RAT (Radio Access Technology).

2. The terminal according to claim 1, wherein, When GNSS information is unavailable, the receiving unit receives its own location information from the base station. The control unit uses the position information of its own device to calculate the inherent TA of the device.

3. The terminal according to claim 1, wherein, When GNSS information cannot be used, the receiving unit receives parameters from the base station for calculating the device's inherent TA. The control unit uses the parameters to calculate the inherent TA of the device.

4. The terminal according to claim 1, wherein, When GNSS information cannot be used, the control unit calculates the position information of its own device and uses the position information of its own device to calculate the inherent TA of the device.

5. The terminal according to claim 1, wherein, The control unit starts a timer at the point when GNSS information becomes unusable, calculates its own device's position information, and uses the position information of its own device to calculate the device's inherent TA, until the timer expires.

6. A communication method in which a terminal performs the following steps: Receive parameters and TA commands related to timing advance that are common to all users in the base station constituting the NTN (non-terrestrial network); The common TA is calculated based on the parameters, and uplink synchronization is performed based on the TA command, the calculated common TA, the device-specific TA, and the offset. as well as When GNSS information, i.e., Global Navigation Satellite System information, cannot be used, the device's inherent TA is calculated based on location information, which is obtained based on positioning relying on RAT, i.e., Radio Access Technology.

Images