Terminal, base station and communication method

By using satellite ephemeris information and general timing parameters in NTN environments with 5G NR technology, the terminal can accurately correct the propagation delay, solve the problem of low signal timing control accuracy, and achieve accurate signal transmission timing under non-terrestrial networks control.

CN119072972APending Publication Date: 2024-12-03PANASONIC INTELLECTUAL PROPERTY CORP OF AMERICA
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202280095182.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2022-04-22
Publication Date
2024-12-03

AI Technical Summary

Technical Problem

In 5G NR technology, the accuracy of signal transmission timing control in non-terrestrial network (NTN) environments is difficult to improve, especially in satellite communications. Due to the altitude and mobility of the satellite, the propagation delay changes dramatically, resulting in difficulty in timing correction.

Method used

By transmitting satellite ephemeris information and general timing parameters between the terminal and the base station, the terminal can calculate and correct the delay time of the service link and the feeder link, thereby accurately controlling the transmission timing of the uplink signal.

Benefits of technology

The accuracy of signal transmission timing control is improved, the impact of delay changes in NTN environment is reduced, and the accurate reception of signals is ensured at the base station.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119072972A_ABST
    Figure CN119072972A_ABST
Patent Text Reader

Abstract

A terminal is provided with: a reception circuit that receives, in a first cell, control information relating to a reference point for a reference time in transmission timing control of an uplink signal addressed to a second cell different from the first cell; and a control circuit that controls the transmission timing based on the control information.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to a terminal, a base station and a communication method. Background Art

[0002] In terms of 5G standardization, the new radio access technology (NR) has been standardized by 3GPP (3rd Generation Partnership Project), and the specifications of NR version (Release) 15 (Rel.15) have been released.

[0003] Prior art literature

[0004] Non-patent literature

[0005] Non-patent document 1: 3GPP, TR 38.821, V16.1.0 “Solutions for NR to support non-terrestrial networks (NTN) (Release 16)”, 2021-05 Summary of the invention

[0006] However, there is still room for research on methods to improve the accuracy of signal transmission timing control.

[0007] The non-limiting embodiments of the present disclosure help to provide a terminal, a base station, and a communication method that can improve the accuracy of signal transmission timing control.

[0008] A terminal of one embodiment of the present disclosure includes: a receiving circuit, which receives control information related to a reference location for a reference time in a first cell, wherein the reference time is a reference time in the transmission timing control of an uplink signal sent to a second cell different from the first cell; and a control circuit, which controls the transmission timing based on the control information.

[0009] It should be noted that these general or specific aspects may be implemented by a system, an apparatus, a method, an integrated circuit, a computer program or a recording medium, or may be implemented by any combination of systems, apparatuses, methods, integrated circuits, computer programs and recording media.

[0010] According to an embodiment of the present disclosure, the accuracy of signal transmission timing control can be improved.

[0011] More advantages and effects of one embodiment of the present disclosure will be explained through the description and drawings. These advantages and / or effects are provided by several embodiments, and the features described in the description and drawings, but not necessarily all of them need to be provided in order to obtain one or more of the same features. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] FIG. 1 is a diagram showing an example of estimating time delays in a serving link and a feeder link.

[0013] FIG. 2 is a sequence diagram showing an example of conditional handover.

[0014] FIG. 3 is a diagram showing an example of switching.

[0015] FIG4 is a block diagram showing a configuration example of a part of a base station.

[0016] FIG5 is a block diagram showing a configuration example of a part of a terminal.

[0017] FIG6 is a block diagram showing an example of the configuration of a base station.

[0018] FIG7 is a block diagram showing an example of the configuration of a terminal.

[0019] FIG. 8 is a diagram showing an example of switching.

[0020] FIG. 9 is a diagram showing an example of switching.

[0021] FIG. 10 is a diagram showing an example of switching.

[0022] FIG. 11 is a diagram showing an example of switching.

[0023] FIG. 12 is a diagram showing an example of a method of determining epoch time.

[0024] FIG. 13 is a diagram showing an example of a method for determining an epoch time.

[0025] FIG. 14 is a diagram showing an example of notification of assistance information.

[0026] FIG15 is a diagram of an exemplary architecture of a 3GPP NR system.

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

[0028] FIG. 17 is a sequence diagram of the process of setting / resetting an RRC (Radio Resource Control) connection.

[0029] 18 is a schematic diagram showing the utilization scenarios of large-capacity high-speed communications (eMBB: enhanced Mobile Broadband), multi-simultaneous machine-type communications (mMTC: massive Machine Type Communications) and highly reliable and ultra-low latency communications (URLLC: Ultra Reliable and Low Latency Communications).

[0030] FIG19 is a block diagram representing an exemplary 5G system architecture for a non-roaming scenario. DETAILED DESCRIPTION

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

[0032] [About Non-Terrestrial Network (NTN)]

[0033] It has been standardized as a wireless access technology for terrestrial networks in NR Rel. 15. On the other hand, in NR, the expansion to non-terrestrial networks (NTN) such as communications using satellites or high-altitude pseudo-satellites (HAPS: High-altitude platform station) is being studied (for example, Non-Patent Document 1).

[0034] In the NTN environment, the coverage area (e.g., one or more cells) of the satellite for terminals on the ground (e.g., also called "user equipment (UE)") and terminals located in the sky such as aircraft or drones is formed by beams from the satellite. In addition, the round-trip time (RTT) of radio wave propagation between the terminal and the satellite depends on the altitude of the satellite (e.g., up to about 36,000 km) and the angle from the terminal, that is, the positional relationship between the satellite and the terminal.

[0035] For example, Non-Patent Document 1 describes that in NTN, the round trip time (RTT) of radio wave propagation between a base station and a terminal takes a maximum of about 540 ms.

[0036] In addition, non-patent document 1 records that in NTN, depending on the position of the terminal within the beam (or, coverage area or cell), a maximum delay difference of about 10 ms may occur (for example, the difference between the position farthest from the satellite and the position closest to the satellite within the beam).

[0037] In addition, in the case of a non-geostationary satellite such as a low-orbit satellite (LEO: Low Earth Orbit satellite), the satellite moves at a high speed of about 7.6 km per second, so the propagation delay amount changes dramatically compared to a terrestrial network.

[0038] (Timing Control)

[0039] In NR, for example, each terminal can perform timing control (e.g., timing adjustment) based on information for correcting (adjusting) timing notified by the base station (e.g., called a "timing advance (TA: Timing Advance) command") to make the reception timing of the signal sent from each terminal consistent in the base station (e.g., also called "gNB").

[0040] As described above, in the NTN, the propagation delay amount varies greatly compared to the terrestrial network, so the terminal calculates the round-trip delay time between the terminal and the base station, corrects the timing, and transmits the signal.

[0041] FIG. 1 is a diagram showing an example of processing in NTN (for example, delay time estimation processing).

[0042] For example, the delay time of the wireless link (e.g., called a "service link") between the terminal and the satellite can be calculated based on the terminal's location information and information related to the satellite's orbit or position. It should be noted that the terminal's location information can be obtained, for example, by a global navigation satellite system (GNSS: Global Navigation Satellite System) in the terminal. In addition, the information related to the satellite's orbit or position can be notified (e.g., broadcasted) to the terminal by the base station as "satellite ephemeris information (or satellite ephemeris)".

[0043] In addition, for example, the terminal may calculate the delay time of a wireless link (eg, called a "feeder link") between a terrestrial base station or gateway (GW) and a satellite based on a common TA parameter broadcasted from the base station.

[0044] The delay time of the feeder link changes with the movement of the satellite. Therefore, in addition to the delay time of the feeder link at a certain point in time, information related to the variation of the delay time, such as common TA drift and common TA drift variation, can also be notified to the terminal as common TA parameters.

[0045] Thus, in NTN, the round trip delay of the service link and the feeder link is corrected (eg, compensated) on the terminal side and the uplink signal is transmitted, so that the base station can receive the signal transmitted from each terminal within a predetermined time difference.

[0046] (Regarding control information for NTN)

[0047] From the base station to the terminal, at least one of the following information and parameters may be included as control information for NTN. The control information for NTN may be notified to the terminal through broadcast information such as a system information block (SIB).

[0048] Ephemeris; Satellite ephemeris information

[0049] Common TA parameters; Common TA parameters

[0050] Epoch time: the reference time for satellite ephemeris information and general TA parameters

[0051] Validity duration for UL syncinformation; Validity duration for SIB information

[0052] t-Service (the timing information on when the serving cell is going to stop serving the area); residual period of the cell

[0053] Cell reference location: a reference location used for cell selection or switching

[0054] Cell specific K_offset; offset used for scheduling

[0055] K_mac: information about the difference between the downlink transmission reference time point and the uplink reception synchronization reference time point

[0056] Here, the epoch time is, for example, the reference time of the satellite ephemeris and the universal TA parameters. The satellite ephemeris and the universal TA parameters are generated based on the epoch time and notify the value of the time point of the epoch time. The terminal can, for example, calculate the satellite position based on the epoch time and the satellite ephemeris information, and calculate the delay time of the feeder link based on the epoch time and the universal TA parameters.

[0057] In addition, for example, the epoch time of the satellite ephemeris and the general TA parameters of the serving cell is not an absolute time, but can be represented by a system frame number (SFN: system frame number) and a subframe number, and notified to the terminal.

[0058] In the terminal, for example, the time at the front end of the subframe of the notified SFN and subframe number (subframe start time) is interpreted as the epoch time. Here, because there is a propagation delay between the base station and the terminal, it is expected to clarify the time point in the process of signal propagation from the base station to the terminal that the epoch time represents the subframe start time, for example, it is expected to clarify the "reference point (RP: Reference Point)". For example, the reference point of the epoch time can also be the point where the uplink signal is synchronized (uplink synchronization reference point). For example, the epoch time can also be the subframe start time of the point where the uplink signal is synchronized.

[0059] It should be noted that the location where the uplink signal is synchronized (uplink synchronization reference location) may be, for example, a location where signals transmitted from each terminal in the cell to the base station are synchronized. For example, the location where the uplink signal is synchronized may be the transmitting end of the base station, the transmitting end of the satellite, or may be set to any location between the satellite and the base station.

[0060] For example, the terminal may calculate the satellite position and the universal TA value in the transmission timing of the terminal by taking into account the propagation delay between the reference point and the terminal, and transmit the data.

[0061] It should be noted that the satellite ephemeris information may include the following parameters, for example.

[0062] -Position and velocity state vector ephemeris format

[0063] Position (m)

[0064] Velocity (m / s)

[0065] -Orbital parameter ephemeris format

[0066] Semi-major axis α(m)

[0067] Eccentricity

[0068] Argument of periapsisω(rad)

[0069] Longitude of ascending node (Ω rad)

[0070] Inclination i (rad)

[0071] Mean anomaly M (rad) at epoch time

[0072] In addition, the common TA parameters may include the following parameters, for example.

[0073] TACommon; the common TA value at the time point of the epoch time

[0074] TACommonDrift; the change of common TA value

[0075] TACommonDriftVariation; the change in the common TA value change

[0076] It should be noted that satellite ephemeris information and general TA parameters are sometimes also referred to as "assistance information".

[0077] For example, the terminal can use the parameters contained in the control information for NTN to calculate the feeder link delay (round-trip delay) according to the following formula (1): common (t).

[0078]

[0079] Here,

[0080]

[0081]

[0082] It should be noted that the feeder link delay may also be the delay between the satellite and the location where the uplink signal is synchronized (reference location).

[0083] (Notification about neighboring cell information)

[0084] In NR, a terminal in RRC idle (RRC_IDLE) state or RRC inactive (RRC_INACTIVE) state performs neighbor cell measurement for cell reselection.

[0085] The information related to the neighboring cell used in the neighboring cell measurement can be notified (for example, broadcast) to the terminal by the base station. For example, the information related to the neighboring cell can be broadcast to the terminal by SIB type 2 (SIB2: SIB type 2). The information related to the neighboring cell can include, for example, at least one of the wireless parameters such as carrier frequency or subcarrier spacing (SCS: subcarrierspacing), and the information related to the time position of the SSB of the measurement object called "SSB measurement timing configuration (SMTC: SSB measurement timing configuration)". It should be noted that SSB is an abbreviation for Synchronization Signal (SS) / Physical Broadcast Channel (PBCH) block. In the neighboring cell measurement, quality measurements such as the reference signal received power (RSRP: Reference Signal Received Power), the reference signal received quality (RSRQ: Reference Signal Received Quality), and the signal to interference and noise ratio (SINR: Signal to Interference and Noise Ratio) of the neighboring cell can be performed.

[0086] In addition, in NR, for example, a terminal in the RRC connected (RRC_CONNECTED) state performs neighbor cell measurements for handover according to instructions from the base station and performs handover.

[0087] The information related to the neighboring cell used in the neighboring cell measurement for handover (for example, the information related to the neighboring cell described above) may be notified to the terminal by terminal-specific RRC signaling (for example, dedicated RRC signaling). For example, the information related to the neighboring cell may be notified by a base station (for example, a serving cell) to which the terminal is connected using an "RRC reconfiguration message".

[0088] In NTN, satellite ephemeris information and universal TA parameters of neighboring cells may be notified as information related to neighboring cells. Satellite ephemeris information and universal TA parameters of neighboring cells may be used, for example, by the terminal to adjust the measurement window in coordination with the movement of the satellite. In addition, when performing a handover, the terminal may use the satellite ephemeris information and universal TA parameters of the neighboring cells to perform timing adjustment (TA) for random access transmission (e.g., random access channel (RACH) transmission).

[0089] For example, there is still room for research on the method of notifying information related to neighboring cells.

[0090] (About Conditional Handover)

[0091] In NR (eg, Release 16), conditional handover (CHO) is introduced.

[0092] FIG. 2 is a sequence diagram showing an example of CHO.

[0093] In CHO, for example, the terminal receives an RRC reconfiguration message containing a switching condition (hereinafter referred to as "HO condition") in advance. For example, a base station serving as a switching source (for example, also referred to as a "source base station", "source gNB" or "source cell") can send a switching request (HO request message) to a base station serving as a switching destination (for example, also referred to as a "target base station", "target gNB" or "target cell"). The target base station can send a switching request response (HO request acknowledgement message) to the source base station. Then, the source base station can, for example, send an RRC reconfiguration message containing the HO condition to the terminal (UE) serving as the switching object.

[0094] The terminal may evaluate (or confirm, judge, monitor) whether the HO condition is met at any time. If the HO condition is met, the terminal may perform handover and perform access processing (eg, RACH processing) to the new cell (target base station).

[0095] For example, in Release 16, the HO condition uses a condition based on neighbor cell measurement. In the condition based on neighbor cell measurement, for example, the terminal can perform handover when the measurement results of RSRP, RSRQ, SINR, etc. of the neighbor cell meet a prescribed reference.

[0096] In NTN, for example, in addition to the condition based on neighbor cell measurement, at least one of a condition based on a timing reference and a condition based on a location reference is studied as a HO condition.

[0097] In a timing-based CHO, for example, the terminal may perform handover within a pre-notified time range. Alternatively, for example, the terminal may perform neighbor cell measurement within a pre-notified time range and perform handover if the neighbor cell measurement result meets a specified criterion.

[0098] In the location-based CHO, for example, the terminal may perform handover when the distance between the reference location of the cell to which the terminal is connected (e.g., the current cell or the serving cell) and the terminal is greater than a pre-notified value. Alternatively, the terminal may perform handover when the distance between the reference location of the current cell and the terminal is greater than the distance between the reference location of the adjacent cell and the terminal (or greater than a specified distance).

[0099] In this way, in NTN, by providing HO conditions to the terminal in advance, handover with reduced delay can be performed even in the case of high-speed cell handover such as LEO.

[0100] The conditional handover (CHO) has been described above.

[0101] As described above, in NTN, the epoch time notified from the base station to the terminal may be represented by the SFN and the subframe number.

[0102] FIG3 is a diagram showing a handover process in NTN as an example. In FIG3, for example, a UE receives an RRC reconfiguration message from gNB1 as a serving cell (or a source cell), and the RRC reconfiguration message includes satellite ephemeris information, common TA parameters, and information related to epoch time of gNB2 as a target cell (or a neighboring cell). When the terminal receives information related to epoch time, for example, it calculates the epoch time based on the timing of the SFN and subframe corresponding to the received signal from gNB1.

[0103] Here, in the terminal, the information related to the epoch time received together with the information of the satellite ephemeris and the universal TA parameters of the neighboring cell (for example, the cell of gNB2 in FIG. 3) may be based on the value of the SFN and the subframe number of the neighboring cell. In addition, for example, as shown in FIG. 3, the epoch time in the current cell (for example, the cell of gNB1) (for example, SFN=10, subframe 3) and the epoch time in the neighboring cell (for example, the cell of gNB2) (for example, SFN=25, subframe 0) may be different. Therefore, the UE may not be able to correctly interpret the epoch time corresponding to gNB2 based on the information related to the epoch time received from gNB1. In addition, for example, the UE may not be able to correctly calculate the epoch time when the reference location of the epoch time of the satellite ephemeris and the universal TA parameters of the neighboring cell is not determined (or, not shared). Therefore, the accuracy of the estimation of the satellite position using the satellite ephemeris and the estimation of the delay amount of the feeder link using the universal TA parameters is easily reduced.

[0104] It should be noted that “interpret” may be replaced by, for example, “determine,” “judge,” “determine,” “decide,” “calculate,” or “understand.”

[0105] In a non-limiting embodiment of the present disclosure, for example, the following method is described, that is, a method for a terminal to correctly determine an epoch time and a reference location of the epoch time, and to improve the accuracy of the estimation of the satellite position using the satellite ephemeris in the terminal and the estimation of the delay of the feeder link using the universal TA parameter. For example, the terminal can obtain information for interpreting the epoch time of the neighboring cell from the network side.

[0106] [Overview of Communication System]

[0107] A communication system according to an embodiment of the present disclosure includes a base station 100 and a terminal 200 .

[0108] FIG4 is a block diagram showing a configuration example of a part of the base station 100. In the base station 100 shown in FIG4, a control unit (e.g., corresponding to a control circuit) determines control information related to a reference point (reference point) for a reference time (e.g., epoch time) in a first cell (e.g., a serving cell), the reference time being a reference time in timing control of an uplink signal sent to a second cell different from the first cell. A transmission unit (e.g., corresponding to a transmission circuit) transmits the control information.

[0109] FIG5 is a block diagram showing a configuration example of a part of the terminal 200. In the terminal 200 shown in FIG5, a receiving unit (e.g., corresponding to a receiving circuit) receives control information related to a reference point for a reference time (e.g., epoch time) in a first cell (e.g., a serving cell), the reference time being a reference time in controlling the transmission timing of an uplink signal sent to a second cell different from the first cell. A control unit (e.g., corresponding to a control circuit) controls the transmission timing based on the control information.

[0110] [Structure of base station]

[0111] 6 is a block diagram showing an example of the configuration of the base station 100 according to the present embodiment. The base station 100 includes, for example, a data generation unit 101, a control unit 102, a data transmission processing unit 103, a wireless transmission unit 104, an antenna 105, a wireless reception unit 106, and a data reception processing unit 107.

[0112] At least one of the data generation unit 101, the control unit 102, the data transmission processing unit 103, and the data reception processing unit 107 shown in Fig. 6 may be included in the control unit shown in Fig. 4, for example. In addition, at least one of the wireless transmission unit 104 and the antenna 105 shown in Fig. 6 may be included in the transmission unit shown in Fig. 4, for example.

[0113] The data generation unit 101, for example, generates a downlink signal to be sent to each terminal 200, and outputs the generated downlink signal to the data transmission processing unit 103. The downlink signal generated in the data generation unit 101 may include at least one of signals such as user data (e.g., physical downlink shared channel (PDSCH: Physical Downlink Shared Channel)), control signals (e.g., physical downlink control channel (PDCCH: Physical Downlink Control Channel)), synchronization signals (e.g., SSB), reference signals (RS: Reference Signal) and medium access control (MAC: Medium Access Control) control information.

[0114] The control unit 102 may generate system information (eg, broadcast information) such as a master information block (MIB) or SIB and dedicated control information (eg, RRC control information such as an RRC reconfiguration message), and output the generated information to the data transmission processing unit 103 .

[0115] For example, the basic control information including the SFN may be notified to the terminal 200 using the MIB. In addition, for example, the SIB may include information (for example, the minimum necessary information) for accessing a cell (for example, the base station 100), neighboring cell information for neighboring cell measurement or cell selection, and other broadcast information. In addition, the system information (for example, the SIB) may also include control information for the NTN, the control information for the NTN including at least one of parameters such as a satellite ephemeris corresponding to the cell, a universal TA parameter, an epoch time, and a validity period. In addition, the system information (for example, the SIB) may also include, for example, information about neighboring cells for the NTN, the information about neighboring cells for the NTN including at least one of parameters such as a satellite ephemeris corresponding to the neighboring cell, a universal TA parameter, and an epoch time. The information about neighboring cells for the NTN may also include information corresponding to other cells (for example, neighboring cells), respectively.

[0116] It should be noted that an example of a method for transmitting information for neighboring cells (for example, including at least one of satellite ephemeris, common TA parameters, and epoch time) will be described later.

[0117] In addition, the control unit 102 may exchange cell information or SIB information with other base stations for handover or the like (for example, handover request or handover request response).

[0118] The data transmission processing unit 103 encodes and modulates, for example, the signal input from the data generation unit 101 and the signal input from the control unit 102 , and outputs the modulated signal to the wireless transmission unit 104 .

[0119] The wireless transmission unit 104 performs transmission processing such as D / A (Digital / Analog) conversion, up-conversion, and amplification on the signal input from the data transmission processing unit 103 , and transmits the wireless signal after the transmission processing from the antenna 105 .

[0120] The wireless receiving unit 106 performs reception processing such as down-conversion and A / D (Analog / Digital) conversion on the data signal (e.g., Physical Uplink Shared Channel (PUSCH)), control signal (e.g., Physical Uplink Control Channel (PUCCH)), or random access signal (e.g., Physical Random Access Channel (PRACH)) received from the terminal 200 via the antenna 105, and outputs the received processed signal to the data receiving processing unit 107.

[0121] The data reception processing unit 107 performs, for example, channel estimation, demodulation processing, and decoding processing on the reception signal input from the wireless reception unit 106. The data reception processing unit 107 outputs the decoded signal.

[0122] [Terminal structure]

[0123] Next, a configuration example of the terminal 200 will be described.

[0124] 7 is a block diagram showing an example of the configuration of the terminal 200 according to the present embodiment. The terminal 200 includes, for example, an antenna 201, a wireless receiving unit 202, a data receiving processing unit 203, a position information acquiring unit 204, a timing adjusting unit 205, a data transmission processing unit 206, and a wireless transmitting unit 207.

[0125] At least one of the data reception processing unit 203, the position information acquisition unit 204, the timing adjustment unit 205, and the data transmission processing unit 206 shown in Fig. 7 may be included in the control unit shown in Fig. 5, for example. In addition, at least one of the antenna 201 and the wireless receiving unit 202 shown in Fig. 7 may be included in the receiving unit shown in Fig. 5, for example.

[0126] The wireless receiving unit 202 performs reception processing such as down-conversion and A / D conversion on downlink signals such as data signals (e.g., PDSCH) and control signals (e.g., PDCCH) received from the base station 100 via the antenna 201, outputs the received processed signals to the data receiving processing unit 203, and outputs the reception timing information to the timing adjustment unit 205.

[0127] The data reception processing unit 203 performs, for example, demodulation processing and decoding processing on the reception signal (for example, PDCCH or PDSCH) input from the wireless reception unit 202. In the control signal (for example, PDCCH), for example, allocation information of a downlink data signal (for example, PDSCH) or allocation information of an uplink data signal (for example, PUSCH) may be included. In addition, in the downlink data signal (for example, PDSCH), for example, user data may be included. In addition, in the downlink data signal (for example, PDSCH), broadcast information such as system information, RRC control information (for example, RRC reset message), MAC control element (MACCE: MAC Control Element) control information, RACH response (for example, also referred to as "msg2", "Random Access Response (RAR: Random Access Response)") or TA command may also be included.

[0128] In addition, the data reception processing unit 203 receives and processes information for NTN (for example, including at least one of satellite ephemeris, universal TA parameters and epoch time) contained in broadcast information or RRC control information (for example, RRC reconfiguration message), and information for cell selection, adjacent cell measurement or switching, and outputs the received and processed signal to the timing adjustment unit 205.

[0129] The location information acquisition unit 204 acquires the location information (latitude, longitude, altitude, etc.) of the terminal 200. For example, the location information of the terminal 200 may be acquired through a GNSS function such as a global positioning system (GPS). The location information acquisition unit 204 outputs the acquired location information of the terminal 200 to the timing adjustment unit 205.

[0130] The timing adjustment unit 205 controls (adjusts) the transmission timing of the transmission signal (uplink signal), for example. The timing adjustment unit 205 outputs information related to the timing adjustment to the wireless transmission unit 207.

[0131] For example, the timing adjustment unit 205 may calculate the distance between the terminal 200 and the satellite based on the location information of the terminal 200 input from the location information acquisition unit 204 and the satellite ephemeris information input from the data reception processing unit 203. Then, the timing adjustment unit 205 may calculate the distance between the terminal 200 and the satellite based on the distance between the terminal 200 and the satellite and the radio wave propagation speed (approximately 3×10 8 m / s), and calculate the propagation delay time between the satellite and the terminal 200 (for example, the service link).

[0132] In addition, for example, the timing adjustment unit 205 may calculate the propagation delay time between the base station 100 and the satellite (eg, feeder link) based on the common TA parameters input from the data reception processing unit 203 .

[0133] For example, the timing adjustment unit 205 may use the epoch time information in at least one of estimating the position of the satellite based on the satellite ephemeris information and estimating the feeder link delay amount based on the universal TA parameter.

[0134] In addition, the timing adjustment unit 205 can adjust the transmission timing of the uplink signal (for example, uplink data or RACH signal) using the propagation delay time of the service link and the feeder link. For example, the timing adjustment unit 205 can also adjust the transmission timing of the uplink signal (for example, uplink data or RACH signal) according to the timing adjustment value (T TA ) performs timing adjustment to compensate for the propagation delay times of the service link and the feeder link respectively so that the base station 100 receives the signal at the specified timing.

[0135]

[0136] In formula (2), N TA For example, N indicates the TA value notified by the TA command. TAoffset Indicates the offset relative to the TA value, T c Indicates the basic time unit. In addition, T UEspecific represents the terminal-specific TA value based on the service link delay time estimated according to the location information of the terminal 200 and the location of the satellite, T common represents the universal TA value based on the feeder link delay time calculated according to the universal TA parameters. The first term of formula (2) is the same as Rel.15 NR specification, and formula (2) is the value of the first term plus the terminal-specific TA value (T UEspecific ) and general TA value (T common ) is the value obtained.

[0137] In addition, the timing adjustment unit 205 may perform timing adjustment based on the timing of receiving a signal (eg, an SSB signal) received from the base station 100 and input from the wireless reception unit 202 , for example, according to the timing adjustment value shown in equation (2).

[0138] The data transmission processing unit 206 performs error correction coding and modulation processing on the input transmission data, and outputs the modulated signal to the wireless transmission unit 207. The transmission data may be, for example, a signal transmitted in the time resource and frequency resource allocated by the base station 100 (e.g., PUSCH), or a signal transmitted in a random access process (e.g., also referred to as a "PRACH signal", "msg1").

[0139] The wireless transmission unit 207 performs transmission processing such as D / A (Digital / Analog) conversion, up-conversion, and amplification on the signal input from the data transmission processing unit 206, and transmits the wireless signal after the transmission processing from the antenna 201. The wireless transmission unit 207 can transmit the signal at the timing specified by the information input from the timing adjustment unit 205, for example.

[0140] [Base station and terminal operation examples]

[0141] Next, operation examples of the base station 100 and the terminal 200 are described.

[0142] In this embodiment, for example, the base station 100 generates information related to the epoch time of the neighboring cell according to the system frame number (SFN) and the subframe number in the cell (serving cell) of the base station 100. The base station 100 may, for example, convert the SFN and the subframe number of the epoch time of the neighboring cell into the SFN and the subframe number in the cell of the base station 100, regenerate the information related to the epoch time based on the converted SFN and the subframe number, and notify the terminal 200 in the cell of the base station 100.

[0143] Terminal 200 interprets the epoch time of the neighboring cell based on the SFN and subframe number of the connected cell (serving cell) or the cell that has received information related to the epoch time.

[0144] In addition, the reference location of the epoch time of the neighboring cell may be set to a location where the uplink signal in the neighboring cell is synchronized (e.g., an uplink synchronization reference location). It should be noted that the reference location of the epoch time of the neighboring cell may also be pre-defined in a specification (e.g., a standard). Alternatively, information related to the reference location of the epoch time of the neighboring cell (e.g., indicating that it is a location where the uplink signal in the neighboring cell is synchronized) may also be notified to the terminal 200.

[0145] Hereinafter, a method for transmitting information for neighboring cells (for example, including satellite ephemeris, common TA parameters, and epoch time) transmitted from base station 100 and a method for interpreting epoch time in terminal 200 will be described. As an example, two methods (method 1 and method 2) in the processing at the time of handover will be described respectively.

[0146] <Method 1>

[0147] In method 1, the base station 100, for example, converts the epoch time (e.g., SFN and subframe number) of the neighboring cell into a value based on the SFN and subframe number in the base station 100. For example, the control information related to the epoch time notified by the base station 100 to the terminal 200 indicates the epoch time of the base station 100 (e.g., the serving cell of the terminal 200) corresponding to the epoch time of the neighboring cell.

[0148] FIG. 8 is a diagram showing an operation example of handover of the base station 100 and the terminal 200 in method 1. As shown in FIG.

[0149] In the example shown in FIG8 , gNB1 (e.g., base station 100) communicates with UEs in cell 1 formed by satellite 1, and gNB2 communicates with UEs in cell 2 formed by satellite 2. The UE shown in FIG8 (e.g., terminal 200) is connected to gNB1.

[0150] For example, during handover, gNB1, which is the base station of the handover source (source base station), sends a handover request (HANDOVER REQUEST) to gNB2, which is the base station of the handover destination (target base station) (processing (1) shown in FIG8 ).

[0151] gNB1, which is the source base station, receives a handover request response (HANDOVER REQUESTACKNOWLEDGE) from gNB2, which is the target base station (processing (2) shown in FIG8 ).

[0152] The handover request response may include, for example, system information for receiving and accessing signals from the target base station (or target cell).

[0153] In addition, for example, as shown in FIG8, the handover request response may include satellite ephemeris information, general TA parameters, and information related to the epoch time for satellite 2 forming the target cell (cell 2). Here, the epoch time can be represented by an SFN and a subframe number. For example, in the handover request response, the value of the epoch time based on the SFN and subframe number of the timing of the target cell (e.g., cell 2) can be notified to the source base station (gNB1). In addition, the reference location of the epoch time can be set to the location where the uplink signal of the target cell is synchronized (e.g., an uplink synchronization reference location).

[0154] In the example shown in FIG8 , SFN25 and subframe 0 based on the timing of the target cell (cell 2) are notified to the source base station (gNB1) as the epoch time. In addition, in the example shown in FIG8 , the reference location of the epoch time of the target cell can be the transmission point of the target base station (gNB2) or the satellite 2 forming the target cell (cell 2).

[0155] The source base station (gNB1) notifies the UE in cell 1 of the control information such as the system information, satellite ephemeris information, common TA parameters, epoch time and validity period of the target cell obtained from the target base station (gNB2) (processing (3) shown in Figure 8). This information can be notified to the UE by, for example, an RRC message (RRC reset message) or SIB.

[0156] Here, in method 1, the source base station (gNB1) converts (or replaces) the SFN and subframe number based on the timing of the target cell (cell 2) to the SFN and subframe number based on the timing of the source cell (cell 1) of the source base station (gNB1) with respect to the epoch time. In the example shown in FIG8 , the source base station (gNB1) converts the SFN25 and subframe 0 of the target cell indicated by the information related to the epoch time to the SFN10 and subframe 3 of the source cell with the same timing as the SFN25 and subframe 0 of the target cell. The source base station (gNB1) can notify the UE in cell 1 of the information related to the epoch time indicating the converted SFN10 and subframe 3.

[0157] In addition, the information notified to the UE by the source base station (gNB1) may also include information related to the switching conditions.

[0158] In Figure 8, the UE determines (or evaluates, monitors) whether the notified handover condition is satisfied, for example, when receiving the above information from the gNB1 to which the UE is connected using an RRC message or SIB. For example, in order to determine the handover condition, or to confirm that the handover condition is satisfied, the UE may measure the reception quality using the SSB of the target cell.

[0159] In addition, for example, when the carrier frequencies of the connected cell and the adjacent cell are different, the UE can open the receiving window and receive the signal of the target cell at the arrival timing of the SSB signal of the target cell as the measurement object. In addition, the UE can, for example, close the receiving window and stop receiving the signal of the target cell at a timing different from the arrival timing of the SSB signal of the target cell as the measurement object. At this time, the UE can also use the satellite ephemeris information and the universal TA parameters of the target cell to estimate the propagation delay, and adjust the timing of the receiving window based on the estimated propagation delay.

[0160] In addition, the UE may access the target cell (e.g., send RACH) to perform handover (e.g., process (4) shown in FIG8 ). At this time, the UE may use the satellite ephemeris information and the universal TA parameters of the target cell to estimate the propagation delay (service link delay and feeder link delay), and send uplink RACH etc. based on the estimated propagation delay (e.g., adjust the transmission timing).

[0161] At this time, for example, the UE can interpret the epoch time of the target cell based on the SFN and subframe timing of the cell to which the UE is connected (the source cell). In the example shown in FIG8 , the UE interprets the epoch time as SFN10, subframe 3 based on the SFN and subframe timing of gNB1 as the source cell. Then, the UE can calculate the satellite position based on the interpreted epoch time according to the satellite ephemeris information, and calculate the feeder link delay (e.g., the universal TA value) based on the universal TA parameters.

[0162] In addition, in Figure 8, the reference location of the epoch time of the target cell is the location where the uplink signal of the target cell is synchronized (uplink synchronization reference location). The UE can also estimate the epoch time of the actual time based on the reception timing of the signal from the target cell and the estimated propagation delay between the UE and the reference location.

[0163] Thus, in method 1, the base station 100 converts the epoch time of the neighboring cell based on the SFN and subframe used by the base station 100, and notifies the terminal 200. Thus, in method 1, the terminal 200 can correctly determine the timing of the epoch time of the neighboring cell even when it cannot receive the signal of the neighboring cell (for example, a signal including the SFN of the neighboring cell such as MIB and PBCH).

[0164] It should be noted that, although the following case is described in method 1, that is, the case where the epoch time of the adjacent cell is converted based on the SFN and subframe used by the base station 100, it is not limited to this. For example, the base station 100 may also notify the terminal 200 of the epoch time of the adjacent cell generated based on the SFN and subframe used by the base station 100. Alternatively, the base station 100 may also notify the terminal 200 of the epoch time of the adjacent cell generated in an external device (e.g., a core network or other control device, etc.) based on the SFN and subframe used by the base station 100. In addition, at this time, information or parameters matching the epoch time based on the SFN and subframe used by the base station 100 may also be generated for the satellite ephemeris and the universal TA parameters.

[0165] <Method 2>

[0166] In method 2, the base station 100, for example, in addition to notifying the terminal 200 of the epoch time (e.g., SFN and subframe number) of the neighboring cell, also notifies the terminal 200 of a value regarding the difference between the SFN and subframe number corresponding to the epoch time in the base station 100 and the SFN and subframe number corresponding to the epoch time in the neighboring cell. For example, the control information related to the epoch time notified by the base station 100 to the terminal 200 indicates the difference between the epoch time of the neighboring cell and the epoch time of the base station 100 (e.g., the serving cell of the terminal 200).

[0167] FIG. 9 is a diagram showing an operation example of handover of the base station 100 and the terminal 200 in method 2. As shown in FIG.

[0168] In the example shown in FIG9 , gNB1 (e.g., base station 100) communicates with UEs in cell 1 formed by satellite 1, and gNB2 communicates with UEs in cell 2 formed by satellite 2. The UE shown in FIG9 (e.g., terminal 200) is connected to gNB1.

[0169] It should be noted that the process (1) (action related to the handover request) and the process (2) (action related to the handover request response) shown in FIG9 may be the same as the method 1 (FIG. 8). In addition, similarly to the method 1, the reference point of the epoch time of the target cell may be set to the point where the uplink signal of the target cell is synchronized (e.g., the uplink synchronization reference point).

[0170] Similar to method 1, the source base station (gNB1) notifies the UE (terminal 200) in cell 1 of control information such as system information, satellite ephemeris information, common TA parameters, epoch time and validity period of the target cell obtained from the target base station (gNB2) (processing (3) shown in Figure 9). This information can be notified to the UE by, for example, an RRC message (RRC reset message) or SIB.

[0171] Here, in method 2, the source base station (gNB1) can determine information about the difference (or, difference) in SFN between the target cell (cell 2) and the source cell (cell 1) with respect to the epoch time (for example, referred to as "SFN difference"). The source base station can also obtain information related to the SFN difference, for example, by exchanging information with the target base station. In the example shown in Figure 9, the source base station (gNB1) can generate a SFN difference, which represents the difference between SFN25 of the target cell and SFN10 of the source cell at the same timing, that is, 15. The source base station (gNB1) can notify the UE in cell 1 of the information related to the generated SFN difference.

[0172] In Figure 9, the UE determines (or evaluates, monitors) whether the notified handover condition is satisfied, for example, when receiving the above information from the gNB1 to which the UE is connected using an RRC message or SIB. For example, in order to determine the handover condition, or to confirm that the handover condition is satisfied, the UE may measure the reception quality using the SSB of the target cell.

[0173] In addition, the UE may access the target cell (e.g., send RACH) to perform handover (e.g., process (4) shown in FIG. 9 ). At this time, the UE may use the satellite ephemeris information and the universal TA parameters of the target cell to estimate the propagation delay (service link delay and feeder link delay), and send uplink RACH etc. based on the estimated propagation delay (e.g., adjust the transmission timing).

[0174] For example, the UE can interpret the time obtained by subtracting (or adding) the SFN difference from the epoch time notified by the source base station (gNB1) as the epoch time of the neighboring cell (e.g., the target cell) based on the timing of the SFN and subframe used by the gNB1 (source cell) to which the UE is connected as the epoch time of the neighboring cell (e.g., the target cell). In the example shown in FIG. 9, the UE can interpret the timing of SFN10 obtained by subtracting the SFN difference 15 from the SFN25 shown in the epoch time notified by gNB1 in the source cell as the timing of SFN25 in the neighboring cell. Then, the terminal 200 can calculate the satellite position based on the interpreted epoch time according to the satellite ephemeris information, and calculate the feeder link delay (e.g., the universal TA value) based on the universal TA parameters.

[0175] In addition, in Figure 9, the reference location of the epoch time of the target cell is the location where the uplink signal of the target cell is synchronized (uplink synchronization reference location). Therefore, the UE can also estimate the epoch time of the actual time based on the reception timing of the signal from the target cell and the estimated propagation delay between the UE and the reference location.

[0176] The UE can use the calculated information to adjust the timing of the reception window for measuring the quality of the target cell or to adjust the timing when accessing the target cell when performing handover.

[0177] Thus, in method 2, in addition to notifying the terminal 200 of the epoch time of the neighboring cell, the base station 100 also notifies the terminal 200 of the difference in SFN between the neighboring cell and the cell of the base station 100. Thus, in method 2, even when the terminal 200 cannot receive a signal from the neighboring cell (for example, a signal including the SFN of the neighboring cell such as MIB and PBCH), it is possible to determine (or derive) the timing of the SFN of the neighboring cell and correctly determine the epoch time of the neighboring cell.

[0178] It should be noted that the information related to the SFN difference may be separately notified to the terminal 200 by SIB or RRC control information, without being limited to the notification at the time of handover.

[0179] In addition, although the example of Figure 9 illustrates the following situation, that is, the base station 100 notifies the terminal 200 of the information related to the SFN difference, in addition to the SFN difference, the information about the difference in subframe numbers between the source cell and the target cell can also be notified to the terminal 200.

[0180] In the above, method 1 and method 2 are described.

[0181] For example, information related to SFN is notified to the terminal 200 by at least one of the MIB and PBCH broadcast in each cell (for example, sometimes also expressed as "MIB / PBCH"). For example, when the terminal 200 is located near a neighboring cell (for example, a target cell), the reception quality of the signal from the neighboring cell (for example, SNR: Signal to Noise Ratio) is good, and the terminal 200 is likely to receive the MIB / PBCH of the neighboring cell and obtain the SFN of the neighboring cell. On the other hand, when the terminal 200 is located far away from the neighboring cell, the SNR of the signal from the neighboring cell is poor, and the terminal 200 may not be able to receive the MIB / PBCH and obtain the SFN of the neighboring cell. For example, in the case of conditional switching, the terminal 200 receives information related to the neighboring cell (for example, including the epoch time of the neighboring cell) from the base station 100 before the actual timing of the switching. Therefore, at a timing before the actual switching timing, terminal 200 is likely to be located far from the neighboring cell and is likely to be unable to receive the MIB / PBCH of the neighboring cell (for example, information related to the SFN of the neighboring cell).

[0182] In this embodiment, the terminal 200 receives control information of the epoch time (e.g., reference time) in the transmission timing control (e.g., including the determination of the satellite position, or the calculation of the delay time of the feeder link) for determining the transmission timing of the uplink signal (e.g., RACH) sent to the adjacent cell, for example, in the cell to which the terminal 200 is connected, and controls the transmission timing based on the received control information.

[0183] For example, the terminal 200 can correctly interpret the epoch time of the neighboring cell contained in the control information (e.g., RRC reconfiguration message or SIB) received from the base station 100 as the serving cell based on the timing of the SFN and subframe in the serving cell. Therefore, for example, even if the information related to the SFN and / or subframe of the neighboring cell is received without using the MIB / PBCH or SIB of the neighboring cell, the terminal 200 can improve the estimation accuracy of the satellite position and feeder link delay in the neighboring cell.

[0184] In addition, even when the terminal 200 is located far away from a neighboring cell and does not receive the MIB / PBCH or SIB of the neighboring cell, for example, it is able to correctly interpret the epoch time of the neighboring cell and therefore correctly determine the validity period of the notified information related to the neighboring cell.

[0185] In addition, in the present embodiment, as shown in FIG. 8 and FIG. 9, information for an adjacent (or, target) cell (for example, including satellite ephemeris, universal TA parameters, and epoch time) is information generated in an adjacent (or, target) base station. In this case, the reference location of the epoch time can be set to a location where the uplink signal of the adjacent cell is synchronized. Thus, the base station 100 can easily generate information on satellite ephemeris and universal TA parameters of the adjacent cell based on the reference location of the epoch time. In addition, the terminal 200, for example, estimates the epoch time of the actual time based on the reception timing of the signal from the adjacent cell and the estimated propagation delay between the terminal 200 and the reference location when accessing the adjacent (target) cell by determining the reference location of the epoch time, thereby being able to appropriately calculate the TA value of the transmission timing of the uplink signal.

[0186] Therefore, according to the present embodiment, it is possible to improve the accuracy of uplink signal transmission timing control.

[0187] It should be noted that, when the handover is not triggered within the validity period calculated from the epoch time interpreted by the above method, the terminal 200 may determine that the handover has failed and notify the base station 100. In addition, the terminal 200 may also re-receive the RRC reconfiguration message or SIB updated with new parameters from the base station 100 after determining that the handover has failed.

[0188] (Implementation Method 2)

[0189] The configurations of base station 100 and terminal 200 in this embodiment may be the same as those in Embodiment 1, for example.

[0190] In this embodiment, for example, the base station 100 may not notify the terminal 200 that performs conditional handover in the cell of the base station 100 of the satellite ephemeris information, the universal TA parameters, and the information related to the epoch time of the target cell.

[0191] For example, the base station 100 (for example, the control unit 102) may notify the terminal 200 that performs a normal handover of the satellite ephemeris information, the universal TA parameters, and the epoch time information of the target cell using an RRC reconfiguration message during the handover. On the other hand, the base station 100 may not notify the terminal 200 that performs a conditional handover of the satellite ephemeris information, the universal TA parameters, and the epoch time information of the target cell. In addition, at this time, the base station 100 may not obtain this information from the target base station.

[0192] In addition, in this embodiment, for example, the terminal 200 can receive the satellite ephemeris information, universal TA parameters and epoch time information of the target cell from the target cell, without receiving the satellite ephemeris information, universal TA parameters and epoch time information of the target cell from the cell to which the terminal 200 is connected (for example, the source cell or the service cell).

[0193] For example, when the terminal 200 (e.g., the data reception processing unit 203) performs conditional handover, it may receive NTN-related information (e.g., SIB) from the target cell before accessing the target cell (e.g., RACH transmission), thereby acquiring satellite ephemeris information, universal TA parameters, and epoch time-related information of the target cell. When the terminal 200 performs conditional handover, it may not receive NTN-related information (e.g., epoch time-related information) of the target cell from the cell to which the terminal 200 is connected (e.g., the serving cell or the source cell).

[0194] For example, the terminal 200 can access the target cell (e.g., send RACH) after acquiring the satellite ephemeris information, universal TA parameters, and epoch time information of the target cell contained in the SIB. At this time, the terminal 200 can, for example, set the reference location of the epoch time of the target cell (e.g., an adjacent cell) as the synchronization location of the uplink in the target cell. It should be noted that the reference location of the epoch time of the target cell can also be pre-defined in a specification (e.g., a standard). Alternatively, information related to the reference location of the epoch time of the target cell (e.g., indicating that it is the location where the uplink signal in the target cell is synchronized) can also be notified to the terminal 200.

[0195] In addition, when the terminal 200 does not perform conditional handover, for example, it is not necessary for the terminal 200 to receive the information related to the NTN from the target cell.

[0196] It should be noted that the terminal 200 may receive information related to NTN of the target cell before RACH processing to the target cell in the handover from the source cell to the target cell. For example, the terminal 200 may also receive SIB related to NTN of the target cell when the handover condition is met and during the period from when the handover is triggered to when the RACH is sent.

[0197] In addition, the terminal 200 (for example, the timing adjustment unit 205), for example, can perform timing adjustment based on formula (2) after obtaining the satellite ephemeris information, universal TA parameters and epoch time information contained in the NTN-related information (for example, SIB) received from the target cell when accessing the target cell (for example, RACH sending).

[0198] FIG10 is a diagram showing an operation example of handover between the base station 100 and the terminal 200 in the present embodiment.

[0199] In the example shown in FIG10 , gNB1 (e.g., base station 100) communicates with UEs in cell 1 formed by satellite 1, and gNB2 communicates with UEs in cell 2 formed by satellite 2.

[0200] The UE (e.g., terminal 200) shown in FIG10 is connected to gNB1. In addition, in FIG10, the UE performs conditional switching. As shown in FIG10, for example, the UE moves from a position where the MIB / PBCH or SIB (e.g., SIB related to NTN) of cell 2 cannot be received in cell 1 to a position where the MIB / PBCH or SIB of cell 2 can be received.

[0201] For example, in a conditional handover, gNB1 as the source base station sends a handover request (HANDOVER REQUEST) to gNB2 as the target base station (processing (1) shown in Figure 10).

[0202] gNB1, which is the source base station, receives a handover request response (HANDOVER REQUESTACKNOWLEDGE) from gNB2, which is the target base station (processing (2) shown in FIG8 ).

[0203] The handover request response may include, for example, system information for receiving and accessing signals from the target base station (or target cell).

[0204] Here, in the case of conditional handover, the handover request response may not include satellite ephemeris information, common TA parameters, and information related to epoch time for satellite 2 forming the target cell (cell 2).

[0205] The source base station (gNB1) notifies the UE (terminal 200) in cell 1 of the system information of the target cell obtained from the target base station (gNB2) (processing (3) shown in Figure 10). This information can be notified to the UE by an RRC message (RRC reset message) or SIB, for example. In this way, the UE performing conditional handover in cell 1 does not obtain the satellite ephemeris information, common TA parameters and information related to the epoch time of the target cell (cell 2) from gNB1.

[0206] In Figure 10, when the UE receives system information from gNB1 to which the UE is connected using an RRC message or SIB, for example, it can determine (or evaluate, monitor) whether the switching condition is met in the same way as in Implementation 1.

[0207] The UE can access the target cell (e.g., RACH transmission) to perform the handover (e.g., process (4) shown in FIG. 10 ) when the handover condition is met. At this time, the UE can, for example, obtain the satellite ephemeris information, universal TA parameters, and information related to the epoch time of the target cell by receiving the MIB or SIB related to the NTN of the target cell from the target cell before the RACH is transmitted. For example, if the terminal 200 cannot receive the MIB (e.g., including the SFN of the target cell) or SIB related to the NTN of the target cell, it will not obtain the satellite ephemeris information, universal TA parameters, and information related to the epoch time of the target cell.

[0208] Next, the UE may use the satellite ephemeris information and universal TA parameters of the target cell to estimate the propagation delay (service link delay and feeder link delay), and based on the estimated propagation delay, send uplink RACH, etc. (eg, adjust the transmission timing).

[0209] At this time, the UE can interpret the epoch time of the target cell based on the SFN and subframe timing of the target cell. In the example shown in Figure 10, the UE interprets the epoch time of the target cell as SFN25, subframe 0 based on the SFN and subframe timing of gNB2 as the target cell. Then, the UE can calculate the satellite position based on the interpreted epoch time according to the satellite ephemeris information, and calculate the feeder link delay (e.g., the universal TA value) according to the universal TA parameters.

[0210] In addition, in Figure 10, the reference location of the epoch time of the target cell is the location where the uplink signal of the target cell is synchronized (uplink synchronization reference location). The UE can also estimate the epoch time of the actual time based on the reception timing of the signal from the target cell and the estimated propagation delay between the UE and the reference location.

[0211] Thus, in this embodiment, the terminal 200, for example, in the cell to which the terminal 200 is connected, receives control information of the epoch time (e.g., reference time) in the transmission timing control (e.g., including the determination of the satellite position or the calculation of the delay time of the feeder link) for determining the transmission timing of the uplink signal (e.g., RACH) sent to the adjacent cell from an adjacent cell, and controls the transmission timing based on the received control information.

[0212] The base station 100 (e.g., the source base station) does not notify the following terminal 200 of the satellite ephemeris information, the universal TA parameter, and the epoch time of the target cell, which is a terminal that may not be able to receive the MIB information from the target cell of the conditional handover (e.g., cannot obtain the SFN of the target cell) and cannot correctly interpret the epoch time of the target cell. Thus, the amount of notification information such as control overhead can be reduced.

[0213] In addition, when the terminal 200 is close to the target cell, the terminal 200 obtains the satellite ephemeris information, the universal TA parameters and the epoch time information contained in the SIB of the target cell. In this case, the terminal 200 can obtain the SFN of the target cell based on the MIB information from the target cell, and therefore can correctly interpret the epoch time of the target cell.

[0214] In addition, in the present embodiment, the information for the adjacent (or, target) cell (for example, including satellite ephemeris, universal TA parameters and epoch time) is information generated in the adjacent (or, target) base station. In this case, the reference location of the epoch time can be set to the location where the uplink signal of the target cell (for example, the adjacent cell) is synchronized. The terminal 200 estimates the epoch time of the actual time by, for example, determining the reference location of the epoch time, the reception timing of the signal from the target cell when accessing the target cell, and the estimated propagation delay between the terminal 200 and the reference location, thereby being able to appropriately calculate the TA value of the transmission timing of the uplink signal.

[0215] In addition, the terminal 200 only needs to obtain the satellite ephemeris information, the universal TA parameters and the epoch time information of the target cell before accessing the target cell. Therefore, for the terminal 200, it is highly likely that there is enough time from receiving the notification of the conditional handover to accessing the target cell, and the timing of executing the handover can be estimated according to the handover condition, so the terminal 200 can have enough time to receive the SIB of the target cell.

[0216] Therefore, according to the present embodiment, it is possible to improve the accuracy of uplink signal transmission timing control.

[0217] (Implementation 3)

[0218] The configurations of base station 100 and terminal 200 in this embodiment may be the same as those in Embodiment 1, for example.

[0219] In this embodiment, for example, the base station 100 may directly notify the terminal 200 of the information related to the epoch time based on the SFN and subframe number of the target cell acquired from the target cell.

[0220] For example, the base station 100 (e.g., the control unit 102) may use an RRC reconfiguration message to notify the terminal 200 performing a normal handover or a conditional handover of the satellite ephemeris information, the universal TA parameters, and the epoch time information of the target cell. Here, the epoch time may be the epoch time based on the SFN and the subframe number of the target cell.

[0221] In addition, for example, the reference location of the epoch time may be set as the synchronization location of the uplink in the target cell. It should be noted that the reference location of the epoch time of the target cell may also be pre-defined in a specification (e.g., a standard). Alternatively, information related to the reference location of the epoch time of the target cell (e.g., indicating that it is a location where the uplink signal in the target cell is synchronized) may also be notified to the terminal 200.

[0222] In addition, in this embodiment, for example, the terminal 200 (for example, the data reception processing unit 203) receives an RRC reconfiguration message from the base station 100 (for example, the service cell or the source cell) and obtains the satellite ephemeris information, universal TA parameters and epoch time information of the target cell.

[0223] In addition, the terminal 200 may, for example, obtain information related to the SFN of the target cell from the target cell (e.g., a neighboring cell). The information related to the SFN of the target cell may also be notified by, for example, the MIB / PBCH from the target cell. For example, when the terminal 200 is located close to the target cell (e.g., when the SNR of the signal from the target cell is sufficient), the SFN of the target cell may be obtained.

[0224] In addition, terminal 200 can, for example, interpret the epoch time at the time point when the SFN of the target cell is acquired, and determine the satellite position and calculate the propagation delay (for example, TA value) based on the satellite ephemeris information and general TA parameters notified by the source cell.

[0225] In addition, when transmitting RACH to the target cell, the terminal 200 (eg, the timing adjustment unit 205) may perform timing adjustment according to equation (2) based on the satellite ephemeris information, the common TA parameters, and the epoch time information of the target cell.

[0226] At this time, the reference location of the epoch time is the location where the uplink signal of the target cell is synchronized. Therefore, terminal 200 can also estimate the epoch time of the actual time based on the reception timing of the signal from the target cell and the estimated propagation delay between terminal 200 and the reference location.

[0227] In this way, terminal 200 receives control information related to NTN of the target cell (for example, including the epoch time of the target cell) from the cell to which terminal 200 is connected (for example, the source cell or the serving cell), and receives information related to SFN of the target cell from the target cell.

[0228] FIG11 is a diagram showing an operation example of handover between the base station 100 and the terminal 200 in the present embodiment.

[0229] In the example shown in Figure 11, gNB1 (for example, base station 100) communicates with the UE in cell 1 formed by satellite 1 (satellite 1), and gNB2 (for example, base station 100) communicates with the UE in cell 2 formed by satellite 2 (satellite 2).

[0230] The UE (e.g., terminal 200) shown in FIG11 is connected to gNB1. As shown in FIG11, the UE moves, for example, in cell 1, from a position where the MIB / PBCH or SIB (e.g., SIB related to NTN) of cell 2 cannot be received to a position where the SIB / PBCH or SIB of cell 2 can be received.

[0231] 11 , process (1) and process (2) may be the same as in Embodiment 1. In addition, the reference point of the epoch time may be set to a point at which the uplink signal of the target cell is synchronized (eg, an uplink synchronization reference point).

[0232] The source base station (gNB1) notifies the UE in cell 1 of the system information, satellite ephemeris information, common TA parameters and epoch time information of the target cell obtained from the target base station (gNB2) (processing (3) shown in Figure 11). This information can be notified to the UE by an RRC message (RRC reset message) or SIB, for example.

[0233] In Figure 11, when the UE receives an RRC message or SIB from gNB1 to which the UE is connected, the UE can determine (or evaluate, monitor) whether the switching condition is met, in the same way as in Implementation 1.

[0234] Here, the UE may not interpret the epoch time of the target cell received from the source cell (cell 1) when it does not receive the MIB / PBCH (e.g., including the SFN of the target cell) from the target cell (cell 2). Then, the terminal 200 may interpret the epoch time of the target cell received from the source cell (cell 1) when, for example, it is close to the target cell and receives the MIB / PBCH (e.g., including the SFN of the target cell) from the target cell (cell 2).

[0235] In this way, the UE receives satellite ephemeris information, universal TA parameters and epoch time information of the target cell from the source base station (or source cell), and receives SFN information for interpreting the epoch time from the target base station (or target cell).

[0236] Then, the UE may calculate the satellite position based on the interpreted epoch time according to the satellite ephemeris information, and calculate the feeder link delay (eg, the universal TA value) according to the universal TA parameters.

[0237] For example, the information related to SFN is notified to the terminal 200 by the MIB / PBCH broadcasted in each cell. For example, when the terminal 200 is located near a neighboring cell (e.g., a target cell), the reception quality (e.g., SNR) of the signal from the neighboring cell is good, and the terminal 200 is likely to receive the MIB / PBCH of the neighboring cell and obtain the SFN of the neighboring cell. On the other hand, when the terminal 200 is located far from the neighboring cell, the SNR of the signal from the neighboring cell is poor, and the terminal 200 may not be able to receive the MIB / PBCH and obtain the SFN of the neighboring cell. For example, in the case of conditional handover, the terminal 200 receives the information related to the neighboring cell (e.g., including the epoch time of the neighboring cell) from the base station 100 before the actual timing of the handover. Therefore, at a timing earlier than the actual timing of the handover, the terminal 200 is likely to be located far from the neighboring cell, and the MIB / PBCH of the neighboring cell (e.g., information related to the SFN of the neighboring cell) is likely to be unable to be received. In this case, the terminal 200 cannot correctly interpret the information based on the epoch time of the SFN of the target cell.

[0238] In contrast, in this embodiment, the terminal 200 receives the satellite ephemeris information, the universal TA parameters, and the epoch time information based on the SFN of the target cell from the currently connected cell (source cell). In addition, when the terminal 200 is located close to the target cell, it receives the MIB / PBCH of the target cell from the target cell and obtains the SFN information. Thus, in this embodiment, after obtaining the SFN information of the target cell, the terminal 200 interprets the epoch time information notified by the source cell. Thus, the terminal 200 can correctly interpret (or derive) the epoch time based on the SFN of the target cell and appropriately estimate the satellite position information and the feeder link delay time.

[0239] In addition, in the present embodiment, the information for the adjacent (or, target) cell (for example, including satellite ephemeris, universal TA parameters and epoch time) is information generated in the adjacent (or, target) base station. In this case, the reference location of the epoch time can be set to the location where the uplink signal of the adjacent cell is synchronized. The terminal 200 estimates the epoch time of the actual time based on the reception timing of the signal from the target cell when accessing the target cell and the estimated propagation delay between the terminal 200 and the reference location, for example, by determining the reference location of the epoch time, thereby being able to appropriately calculate the TA value of the transmission timing of the uplink signal.

[0240] In addition, the terminal 200 only needs to obtain the satellite ephemeris information, general TA parameters and epoch time information of the target cell before accessing the target cell. Therefore, for the terminal 200, there is a high possibility that there is enough time from receiving the notification of conditional switching to accessing the target cell, and the timing of executing the switching can be estimated according to the switching condition. Therefore, the terminal 200 can have sufficient time to receive the MIB of the target cell and perform timing adjustment for RACH transmission (for example, calculation of the TA value).

[0241] It should be noted that the base station 100 may also notify the terminal 200 of the satellite ephemeris information, the common TA parameters, and the epoch time information of the target cell at a plurality of timings.

[0242] For example, in NR, the information related to SFN is 10 bits of information, and its value ranges from 0 to 1023. Therefore, SFN is reset to 0 in a cycle of 1024 frames (for example, called "SFN cycle") according to the SFN cycle. For example, 1 frame is 10 ms, so SFN is reset every 10.24 seconds. Therefore, for example, as shown in FIG. 12, the terminal 200 may not be able to determine which SFN cycle the SFN and subframe number corresponding to the epoch time received in the past refer to when receiving the MIB / PBCH of the neighboring cell (for example, the target cell) and obtaining (for example, reading) the SFN of the neighboring cell.

[0243] For example, in FIG12 , the terminal 200 acquires the epoch time of the target cell during SFN cycle 1, and acquires the SFN of the target cell during SFN cycle 2. In this case, the terminal 200 cannot determine whether the SFN and the subframe number indicating the epoch time of the target cell correspond to SFN cycle 2, SFN cycle 1, or an SFN cycle earlier than SFN cycle 1.

[0244] Therefore, for example, as shown in FIG. 13, the base station 100 may notify the terminal 200 of the satellite ephemeris information, the universal TA parameters, and the epoch time information of the target cell at least in one SFN cycle (e.g., 10.24 seconds). The satellite ephemeris information, the universal TA parameters, and the epoch time information of the target cell may be notified to the terminal 200 by, for example, an RRC reset message. The terminal 200 may, for example, receive the satellite ephemeris information, the universal TA parameters, and the epoch time information of the target cell at least in one SFN cycle.

[0245] Here, the satellite ephemeris information, universal TA parameters, and epoch time information of the target cell may be updated to match the epoch time represented by the latest SFN, for example. For example, for information notified in SFN cycle 1, information based on SFN cycle 1 may be notified, and for information notified in SFN cycle 2, information based on SFN cycle 2 may be notified.

[0246] The terminal 200, for example, receives the satellite ephemeris information, the universal TA parameters and the epoch time information of the target cell by using the RRC reset message at multiple timings. At this time, the terminal 200 may also judge (or assume) the SFN indicated by the epoch time as the SFN of the same SFN cycle as the timing at which the RRC reset message is received. Alternatively, the terminal 200 may also judge (or assume) the SFN indicated by the epoch time as the SFN closest to the timing at which the RRC reset message is received.

[0247] As a result, when the terminal 200 receives the MIB of the target cell and acquires the SFN, it can uniquely identify the SFN indicated by the epoch time, and can correctly interpret the epoch time.

[0248] It should be noted that although the following example is described, that is, the satellite ephemeris information, the universal TA parameters, and the epoch time information of the target cell are notified to the terminal 200 by the RRC reconfiguration message, it is not limited to this, and it can also be broadcast by the SIB. In this case, the terminal 200 can also receive the relevant SIB for a specified interval (for example, the interval of the SFN cycle).

[0249] (Implementation 4)

[0250] The configurations of the base station 100 and the terminal 200 of this embodiment may be the same as those of Embodiment 1. The communication system of this embodiment may include an NTN control device (also referred to as an “NTN control center”) 300 in addition to the base station 100 and the terminal 200 .

[0251] The NTN control device 300 controls, for example, a plurality of base stations 100 and satellites. For example, the NTN control device 300 may generate at least one of satellite ephemeris and universal TA parameters corresponding to the plurality of base stations 100 (or satellites), respectively.

[0252] The NTN control device 300 may, for example, notify each base station 100 of at least one of the auxiliary information (e.g., satellite ephemeris and common TA parameters) notified from each base station 100 to the terminal 200. For example, the base station 100 (e.g., the control unit 102) receives auxiliary information (e.g., including satellite ephemeris and common TA parameters) related to the satellite used by each base station 100 from the NTN control device 300. Then, the base station 100 may notify the terminal 200 of the received information. It should be noted that the notification to the terminal 200 may be performed using SIB or RRC control information.

[0253] Here, the information sent from the NTN control device 300 to the base station 100 and the information notified from the base station 100 to the terminal 200 may also include information related to the cell (service cell) formed by the base station 100 and information related to the adjacent cell (or target cell) not formed by the base station 100.

[0254] In addition, the base station 100 (e.g., the control unit 102) may directly notify the terminal 200 of the information including the satellite ephemeris and the universal TA parameters received from the NTN control device 300. In this case, the location (e.g., the serving cell or the neighboring cell) set by the NTN control device 300 may be set as the reference location of the epoch time.

[0255] Alternatively, the base station 100 may estimate the satellite orbit, for example, and based on the estimated satellite orbit, generate new information according to the information including the satellite ephemeris and the universal TA parameters received from the NTN control device 300, and notify the terminal 200. In this case, the reference location of the base station 100 that generated the information, for example, the reference location of the serving cell for the terminal 200, may be set as the reference location of the epoch time.

[0256] FIG14 is a diagram showing an example of operations of the base station 100 (gNB), the terminal 200 (UE), and the NTN control device 300 (NTN control center) in this embodiment.

[0257] In the example shown in FIG14 , gNB1 (e.g., base station 100) communicates with UEs in cell 1 formed by satellite 1, and gNB2 communicates with UEs in cell 2 formed by satellite 2. The UE shown in FIG14 (e.g., terminal 200) is connected to gNB1.

[0258] 14, for example, NTN control device 300 obtains information on satellite position and time from each satellite (for example, satellite 1 and satellite 2). For communication for obtaining information on satellite position and time, a control line different from the communication line for NTN, such as a telemetry line, is assumed.

[0259] For example, the NTN control device 300 can generate information (eg, auxiliary information) related to each satellite (eg, satellite 1 and satellite 2) such as satellite ephemeris information and universal TA parameters based on information related to satellite position and time acquired from each satellite.

[0260] Next, the NTN control device 300 notifies each base station 100 (e.g., gNB1 and gNB2) of the generated information, for example. At this time, the NTN control device 300 may, for example, notify each base station 100 of information related to the satellite (or base station) forming the adjacent cell in addition to the information corresponding to the base station 100. In the example shown in FIG. 14, two pieces of information, namely, information related to satellite 1 and information related to satellite 2, are notified to gNB1 and gNB2, respectively.

[0261] Each base station 100 notifies the terminal 200 (UE) of the satellite-related information (for example, satellite ephemeris information and common TA parameters) received from the NTN control device 300. In addition, each base station 100 notifies the terminal 200 of, for example, the satellite-related information and the information related to the epoch time. The information related to the epoch time may include, for example, information related to the SFN and subframe notified as the epoch time, and information related to the reference point for the epoch time.

[0262] The following describes methods for setting information related to epoch time (for example, method 1 and method 2).

[0263] <Method 1>

[0264] In method 1, the base station 100 may directly notify the terminal 200 of the satellite ephemeris information and the general TA parameter information generated in the NTN control device 300, for example.

[0265] In this case, the information related to the epoch time may be generated, for example, in the NTN control device 300. For example, the NTN control device 300 may set the SFN and subframe number notified as the epoch time, and the reference point of the epoch time.

[0266] For example, the specification (e.g., standard) may predefine which cell (e.g., serving cell or neighboring cell) the SFN and subframe number and the reference point are based on. Alternatively, information related to the cell serving as a reference for the SFN and subframe number (e.g., referred to as "information related to the SFN and subframe number") may be notified to the base station 100, and information related to the cell serving as a reference for the reference point (e.g., referred to as "information related to the reference point") may also be notified to the base station 100.

[0267] For example, the information related to the SFN and the subframe may indicate which cell (e.g., the serving cell or the neighboring cell) the SFN and the subframe number notified as the epoch time are based on. In addition, for example, the information related to the reference location may indicate which cell (e.g., the serving cell or the neighboring cell) the reference location at the epoch time is the synchronization location of the uplink signal. The information related to the SFN and the subframe number notified as the epoch time and the information related to the reference location may include a cell ID, and may also include a value indicating a cell among the serving cell and the neighboring cell as a parameter indicating which cell is based on.

[0268] For example, in addition to notifying the terminal 200 of the satellite ephemeris, the universal TA parameters, and the epoch time, the base station 100 may also notify the terminal 200 of information related to the SFN and the subframe number, and information related to the reference location. The information related to the SFN and the subframe number, and the information related to the reference location may each be notified to the terminal 200 individually, or may be notified to the terminal 200 as universal information.

[0269] The terminal 200 can determine, for example, which cell the SFN and subframe number are based on based on the information related to the SFN and subframe number notified as the epoch time, and can determine, based on the information related to the reference location, which cell the reference location is where the uplink signal is synchronized. Then, the terminal 200 can interpret the epoch time based on the determined SFN and subframe number and the reference location, and calculate the TA value at the time of uplink transmission.

[0270] Thus, in method 1, the following information indicating which cell the SFN and subframe number notified as the epoch time and the reference location of the epoch time are based on are notified to the terminal 200. As a result, the terminal 200 can determine the SFN, subframe number and reference location for the epoch time and appropriately interpret the epoch time, so that the satellite position information and the universal TA value can be appropriately derived and the TA value at the time of uplink transmission can be calculated with high accuracy.

[0271] <Method 2>

[0272] In method 2, the base station 100 can, for example, use the satellite ephemeris information and the information of the universal TA parameters generated in the NTN control device 300 to newly generate (for example, update) at least one of the satellite ephemeris information and the universal TA parameters of the cell (for example, the service cell) of the base station 100 and the adjacent cell, and notify the terminal 200 of the generated information.

[0273] For example, the base station 100 can estimate the satellite orbits for the satellites to which the base station 100 is connected (or utilized) and the satellites of the neighboring cells, and based on the estimated satellite orbits, newly generate at least one of the satellite ephemeris information and general TA parameter information for the cell of the base station 100 and the neighboring cells.

[0274] Thus, the base station 100 can notify the terminal 200 of more accurate satellite ephemeris information and common TA parameter information, for example, based on the satellite orbits of satellites forming each cell.

[0275] At this time, the information related to the epoch time may be generated in the base station 100, for example. For example, the base station 100 may set the epoch time (for example, SFN and subframe) based on the SFN and subframe number of the cell formed by the base station 100. In addition, the base station 100 may set the reference location of the epoch time to a reference location corresponding to the base station 100 (or the cell formed by the base station 100), for example. In this case, the information related to the SFN and subframe number may indicate that the SFN and subframe number notified as the epoch time are based on the serving cell. In addition, for example, the information related to the reference location may indicate whether the reference location of the epoch time is a synchronization location of the uplink signal in the serving cell.

[0276] In this way, for example, when information for a neighboring (or, target) cell (e.g., including satellite ephemeris, universal TA parameters, and epoch time) is generated in a device (e.g., base station 100 or NTN control device 300) that is different from the neighboring (or, target) base station, the reference location of the epoch time can be set to the location where the uplink signal of the serving cell is synchronized.

[0277] For example, when the terminal 200 receives satellite ephemeris information, general TA parameter information and epoch time information, it can determine that the SFN and subframe number information notified as the epoch time, and the reference location of the epoch time are based on the service cell, interpret the epoch time, and calculate the TA value when the uplink is sent.

[0278] Because the SFN and subframe number notified as the epoch time and the reference location of the epoch time are set based on the service cell, the terminal 200 can properly interpret the epoch time in the service cell and properly derive the satellite position information and the general TA value of the service cell and the adjacent cells, thereby being able to calculate the TA value during uplink transmission with high accuracy.

[0279] In addition, the terminal 200 can interpret the epoch time without receiving a signal from a neighboring cell, for example. Therefore, even in an environment where a signal from a neighboring cell cannot be received, the satellite position information and the universal TA value in the neighboring cell can be derived.

[0280] It should be noted that the NTN control device 300 may generate satellite ephemeris information and notify each base station 100, and each base station may generate a common TA parameter. In addition, for example, the epoch time for the satellite ephemeris information and the epoch time for the common TA parameter may be different.

[0281] In the above, method 1 and method 2 are described.

[0282] Thus, in the present embodiment, the base station 100 determines control information related to a reference location for an epoch time (for example, information indicating a location at which an uplink signal of which cell is synchronized) in a serving cell, and transmits the information to the terminal 200. The epoch time is an epoch time in the timing control of an uplink signal sent to a neighboring cell (or a target cell). The terminal 200 receives the control information related to the reference location for the epoch time of the neighboring cell (or the target cell) in the serving cell, and controls the transmission timing of the uplink signal sent to the neighboring cell based on the control information.

[0283] Thus, the terminal 200 can determine (or share) the reference location of the epoch time of the satellite ephemeris and common TA parameters for the neighboring cells, and can therefore correctly interpret the epoch time, thereby improving the accuracy of the estimate of the satellite position using the satellite ephemeris for the neighboring cells and the accuracy of the estimate of the delay of the feeder link using the common TA parameters.

[0284] Therefore, according to the present embodiment, it is possible to improve the accuracy of uplink signal transmission timing control.

[0285] (Implementation 5)

[0286] The configurations of base station 100 and terminal 200 in this embodiment may be the same as those in Embodiment 1, for example.

[0287] In this embodiment, for example, the epoch time of the satellite ephemeris information and the universal TA parameter information of the neighboring cell (or the target cell) may be represented by an absolute time (eg, in the form of a time).

[0288] For example, similarly to any one of Embodiments 1 to 4, the base station 100 (eg, the control unit 102 ) generates the epoch time of the satellite ephemeris information and the common TA parameter information for the base station 100 (eg, the serving cell) as the SFN and the subframe number.

[0289] On the other hand, base station 100 generates the epoch time of satellite ephemeris information and universal TA parameter information for neighboring cells or base stations as time information. The time format may be, for example, absolute time, Coordinated Universal Time (UTC) or UNIX (registered trademark) time.

[0290] In addition, the base station 100 (for example, the control unit 102) may broadcast time information to the terminal 200 that cannot use the GNSS function such as GPS. For example, the base station 100 may also notify the terminal 200 of information such as the relationship between the timing and time of the SFN including SIB9 specified in 3GPP TS38.331 (for example, the start time of the SFN of the SIB9 transmission, etc.).

[0291] For example, when the GNSS function is available, the terminal 200 acquires the time information using the GNSS function. Alternatively, when the GNSS function is not available, the terminal 200 acquires the time information by, for example, receiving SIB9.

[0292] Next, when receiving the satellite ephemeris information, the common TA parameter information and the epoch time information corresponding to the information for the neighboring cells, the terminal 200 interprets the epoch time as the time information.

[0293] Thus, the terminal 200 can appropriately interpret the epoch time regardless of which cell the epoch time for the satellite ephemeris information and the common TA parameter information for the neighboring cells notified by the base station 100 is based on.

[0294] In the above, each embodiment of the present disclosure has been described.

[0295] Furthermore, although an example of conditional handover is described in each of the above embodiments, the present invention is not limited to this, and the same method can be used when notifying neighboring cell information for normal handover or cell selection.

[0296] In addition, in each of the above-mentioned embodiments, different actions may be performed in handover and cell selection. For example, the base station 100 may also notify the terminal 200 of the epoch time based on the SFN and subframe number of the base station 100 (for example, the serving cell) and the auxiliary information (satellite ephemeris, universal TA parameter) as information related to the neighboring cell for cell selection or neighboring cell measurement, and notify the terminal 200 of the epoch time based on the SFN and subframe number of the target base station or the target cell and the auxiliary information (satellite ephemeris, universal TA parameter) as information related to the target cell for handover. In addition, the reference location of the epoch time of the auxiliary information (satellite ephemeris, universal TA parameter) of the neighboring cell used for cell selection or neighboring cell measurement may be set to the synchronization location of the uplink signal in the serving cell, and the reference location of the epoch time of the auxiliary information (satellite ephemeris, universal TA parameter) of the target cell used for handover may be set to the synchronization location of the uplink signal in the target cell. In the case of cell selection or neighboring cell measurement, at the time of receiving this information from the base station 100, the terminal 200 may be located at a position where the MIB, PBCH or SIB of the neighboring cell cannot be received. Therefore, by notifying the terminal 200 of the epoch time, satellite ephemeris and universal TA parameters based on the SFN and subframe number of the serving cell, the terminal 200 can correctly interpret the information of the epoch time according to the SFN and subframe timing of the serving cell, so that the measurement window can be properly controlled using the information of the satellite ephemeris and universal TA parameters. In addition, at the time of handover, the terminal 200 is likely to be located near the neighboring cell. Therefore, by notifying the terminal 200 of the epoch time, satellite ephemeris and universal TA parameters based on the SFN and subframe number of the target cell, the terminal 200 can obtain the information of the SFN and subframe of the target cell using the MIB / PBCH of the target cell, so that the epoch time information can be correctly interpreted, so that the information of the satellite ephemeris and universal TA parameters can be used to access the target cell.

[0297] It should be noted that the neighboring cell related information used for cell selection or neighboring cell measurement may be broadcast by SIB, and the neighboring cell related information used for handover may be notified to terminal 200 by RRC control information such as RRC reconfiguration message.

[0298] In addition, as the satellite ephemeris information and common TA parameter information of the adjacent cell, the base station 100 can also notify the terminal 200 of the following information, for example, which is information about whether this information is the same as the satellite ephemeris information and common TA parameter information of the cell (for example, the service cell) of the base station 100.

[0299] In addition, the satellite ephemeris information and the general TA parameter information may be notified as “epoch time (EpochTime)” and “TA information (TAInfo)”, respectively, in NTN-Config of SIB19, for example.

[0300] In addition, in each of the above embodiments, when information such as satellite ephemeris and universal TA parameters is notified to the terminal 200 by SIB, the epoch time may be implicitly notified using the first (e.g., starting time point) subframe or the last (e.g., ending time point) subframe of the SI window (SI-window) in which the SIB is sent. In this case, the base station 100 notifies the terminal 200 of the epoch time, satellite ephemeris, and universal TA parameters based on the timing of the SFN and / or subframe of the base station 100 (e.g., the serving cell) as information of the neighboring cell. Alternatively, when the epoch time, satellite ephemeris, and universal TA parameters based on the timing of the SFN and / or subframe of the base station 100 (e.g., the serving cell) are notified to the terminal 200, the epoch time may be implicitly notified using the first subframe or the last subframe of the SI window in which the SIB is sent.

[0301] In addition, in each of the above embodiments, the cell can be an area defined by the received power of the SSB or the channel state information reference signal (CSI-RS: Channel State Information-Reference Signal) sent by the base station (or satellite), or an area defined by a geographical location. In addition, the cell in each of the above embodiments can also be replaced by a beam defined by the SSB.

[0302] In addition, in each of the above-mentioned embodiments, the satellite ephemeris information as information related to the satellite position may be broadcast by the system information, or may be reserved in advance by the terminal 200. In addition, the satellite ephemeris information may also be updated when communication is possible. In addition, the terminal 200 may also use information different from the satellite ephemeris information to determine the satellite position.

[0303] In addition, in each of the above-mentioned embodiments, the base station may be replaced by a “network”.

[0304] In addition, although the target cell during handover is used as an example in the above embodiments, the target cell may be replaced by a neighboring cell. In addition, the neighboring cell may be replaced by a cell different from the serving cell. In addition, not limited to handover, a method of the present disclosure may also be applied to the case of neighboring cell measurement for cell selection or cell reselection.

[0305] In addition, the satellite ephemeris and universal TA parameters of the neighboring cells are broadcast by the SIB as neighboring cell information, and the terminal 200 may also use this information when selecting or reselecting a cell in the RRC idle state. In addition, in the RRC connected state, when switching, the terminal 200 may be notified of the following information using the terminal-specific RRC control information, which indicates which neighboring cell information is used as the target cell information. Thus, the amount of information notified to the terminal 200 during switching can be reduced.

[0306] In addition, in each of the above-mentioned embodiments, the terminal 200 may use other signals such as CSI-RS instead of the SSB signal to measure the reception quality.

[0307] In addition, although the above embodiments describe examples of using GNSS such as GPS (for example, position detection using satellite signals), the present invention is not limited thereto, and for example, position detection using ground cellular base stations, position detection using WiFi (registered trademark) signals or Bluetooth (registered trademark) signals, position detection using acceleration sensors, etc., or position detection using a combination of these detection methods may also be performed. In addition, altitude information may also be obtained from a barometric pressure sensor, etc.

[0308] In addition, although the above embodiment describes the transmission of the uplink from the terminal 200 to the base station 100, an embodiment of the present disclosure is not limited thereto, and may also be applied to data in the downlink from the base station 100 to the terminal 200, or in a link (e.g., a side link) between the terminals 200. In addition, although the transmission of the RACH signal is described as an example of uplink transmission in the above embodiment, the transmission object is not limited to the RACH, and may also be other signals or channels.

[0309] In addition, an embodiment of the present disclosure can be applied independently of the type of satellite, such as a geostationary satellite (GEO), a medium earth orbit satellite (MEO), a LEO, or a high elliptical orbit satellite (HEO). In addition, an embodiment of the present disclosure can also be applied to non-terrestrial communications, such as HAPS or drone base stations.

[0310] In addition, although the NTN environment (e.g., satellite communication environment) is used as an example in the above embodiments for description, the present disclosure is not limited thereto. The present disclosure may also be applied to other communication environments (e.g., at least one terrestrial cellular environment in LTE and NR). For example, an embodiment of the present disclosure may also be applied to terrestrial communications in an environment where, for example, the cell size is large and the propagation delay between the base station 100 and the terminal 200 is longer (e.g., above a threshold). In addition, even outside the NTN, communication applications for application switching or cell selection may also be applied.

[0311] In addition, in the above-mentioned embodiments, the satellite communication method may be a structure in which the base station function exists on the satellite (for example, a "regenerative satellite"), or a structure in which the base station function exists on the ground and the satellite relays the communication between the base station and the terminal (for example, a "transparent satellite"). For example, in one embodiment of the present disclosure, the downlink and the uplink may also be a link between the terminal and the satellite, or a link via the satellite.

[0312] In addition, the various parameters in the above-mentioned embodiments are examples and may be other values. For example, the SFN at the epoch time, the subframe number at the epoch time, the number of frames in one cycle of the SFN, and the number of cells (or the number of satellites) are not limited to the values ​​shown in the above examples. In addition, the reference location at the epoch time is not limited to one of the gNB and the satellite, but may be other locations.

[0313] In addition, the method of notifying the terminal 200 of control information from the base station 100 is not limited to the above example, and may be notified (or broadcast, indicated, set) by at least one of system information such as MIB and SIB, RRC control information, MAC control information and downlink control information (DCI: Downlink Control Information), or may be pre-set to the terminal 200, or may be pre-specified in the standard.

[0314] The base station may be referred to as a “gNodeB” or a “gNB.” In addition, the terminal may also be referred to as a “UE.”

[0315] Time resource units such as system frames and subframes may also be replaced by time slots, mini-time slots, frames, subframes, and the like.

[0316] In addition, the expression "...part" in the above-mentioned embodiments may be replaced by other expressions such as "...circuitry", "...device", "...unit" or "...module".

[0317] (Replenish)

[0318] The information indicating whether the terminal 200 supports the functions, actions or processes shown in the above-mentioned embodiments may be sent (or notified) by the terminal 200 to the base station 100 as capability information or capability parameters of the terminal 200, for example.

[0319] The capability information may also include the following information elements (IE: Information Element), which individually indicate whether the terminal 200 supports at least one of the functions, actions, and processes shown in the above embodiments. Alternatively, the capability information may also include the following information elements, which indicate whether the terminal 200 supports a combination of two or more of the functions, actions, and processes shown in the above embodiments.

[0320] The base station 100 may, for example, determine (or decide or assume) a function, action or process supported (or not supported) by the terminal 200 that sends the capability information based on the capability information received from the terminal 200. The base station 100 may implement an action, process or control corresponding to the result of the determination based on the capability information. For example, the base station 100 may control communication for NTN based on the capability information received from the terminal 200.

[0321] It should be noted that the terminal 200 does not support a part of the functions, actions or processes shown in the above embodiments, which may also be replaced by limiting such a part of the functions, actions or processes in the terminal 200. For example, information or requests related to such limitations may also be notified to the base station 100.

[0322] The information related to the capability or limitation of the terminal 200 may be defined in the standard, for example, or may be implicitly notified to the base station 100 by being associated with information known to the base station 100 or information transmitted to the base station 100 .

[0323] (Control signal)

[0324] In the present disclosure, a downlink control signal (or downlink control information) associated with an embodiment of the present disclosure may be, for example, a signal (or information) sent in a physical downlink control channel (PDCCH: Physical Downlink Control Channel) of the physical layer, or a signal (or information) sent in a medium access control control element (MAC CE: Medium Access Control Control Element) or a radio resource control (RRC: Radio Resource Control) of a higher layer. In addition, the signal (or information) is not limited to the case of being notified by a downlink control signal, and may be pre-defined in a specification (or standard), or may be pre-set in a base station and a terminal.

[0325] In the present disclosure, an uplink control signal (or uplink control information) associated with an embodiment of the present disclosure may be, for example, a signal (or information) sent in a PUCCH of a physical layer, or a signal (or information) sent in a MAC CE or RRC of a higher layer. In addition, the signal (or information) is not limited to the case where it is notified by an uplink control signal, and may be pre-defined in a specification (or standard), or may be pre-set in a base station and a terminal. In addition, the uplink control signal may be, for example, changed to uplink control information (UCI: uplink control information), first stage (1st stage) sidelink control information (SCI: sidelink control information), or second stage (2nd stage) SCI.

[0326] (Base Station)

[0327] In one embodiment of the present disclosure, the base station may also be a transceiver point (TRP: Transmission Reception Point), a cluster head, an access point, a remote radio head (RRH: Remote Radio Head), an eNodeB (eNB), a gNodeB (gNB), a base station (BS: Base Station), a base transceiver station (BTS: Base Transceiver Station), a mother machine, a gateway, etc. In addition, in the sidelink communication, the terminal may also assume the role of the base station. In addition, the base station may also be replaced by a relay device that relays the communication between the high-level node and the terminal. In addition, the base station may also be replaced by a roadside device.

[0328] (Uplink / Downlink / Sidelink)

[0329] An embodiment of the present disclosure can be applied to any link in the uplink, downlink and sidelink. For example, an embodiment of the present disclosure can also be applied to the physical uplink shared channel (PUSCH: Physical Uplink Shared Channel), physical uplink control channel (PUCCH: Physical UplinkControl Channel), physical random access channel (PRACH: Physical Random Access Channel) of the uplink, physical downlink shared channel (PDSCH: Physical Downlink Shared Channel), PDCCH, physical broadcast channel (PBCH: Physical Broadcast Channel) of the downlink, or physical sidelink shared channel (PSSCH: Physical Sidelink Shared Channel), physical sidelink control channel (PSCCH: PhysicalSidelink Control Channel), physical sidelink broadcast channel (PSBCH: Physical SidelinkBroadcast Channel) of the sidelink.

[0330] It should be noted that PDCCH, PDSCH, PUSCH and PUCCH are examples of downlink control channels, downlink data channels, uplink data channels and uplink control channels, respectively. In addition, PSCCH and PSSCH are examples of sidelink control channels and sidelink data channels. In addition, PBCH and PSBCH are examples of broadcast channels, and PRACH is an example of a random access channel.

[0331] (Data Channel / Control Channel)

[0332] An embodiment of the present disclosure may be applied to any channel in a data channel and a control channel. For example, the channel in an embodiment of the present disclosure may be replaced with a PDSCH, PUSCH, PSSCH of a data channel, or a PDCCH, PUCCH, PBCH, PSCCH, PSBCH of a control channel.

[0333] (Reference signal)

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

[0335] (Time interval)

[0336] In one embodiment of the present disclosure, the unit of time resources is not limited to one of a time slot and a symbol or a combination thereof, and may be, for example, a frame, a superframe, a subframe, a time slot, a time slot subslot, a minislot, or a symbol, an OFDM (Orthogonal Frequency Division Multiplexing) symbol, a single carrier-frequency division multiplexing (SC-FDMA) symbol, or other time resource units. In addition, the number of symbols contained in one time slot is not limited to the number of symbols exemplified in the above-mentioned embodiment, and may be other numbers of symbols.

[0337] (frequency band)

[0338] An embodiment of the present disclosure may be applied to any one of a licensed band and an unlicensed band.

[0339] (communication)

[0340] An embodiment of the present disclosure may be applied to any communication between a base station and a terminal (Uu link communication), between terminals (sidelink communication), and in-vehicle wireless communication technology (V2X: Vehicle to Everything). For example, the channel in an embodiment of the present disclosure may be changed to one of PSCCH, PSSCH, physical sidelink feedback channel (PSFCH: Physical Sidelink Feedback Channel), PSBCH, PDCCH, PUCCH, PDSCH, PUSCH, and PBCH.

[0341] In addition, an embodiment of the present disclosure can be applied to any of a terrestrial network and a non-terrestrial network (NTN: Non-Terrestrial Network) using a satellite or a high altitude pseudo satellite (HAPS: High Altitude Pseudo Satellite). In addition, an embodiment of the present disclosure can also be applied to a terrestrial network such as a network with a large cell size and an ultra-wideband transmission network where the transmission delay is greater than the symbol length or the time slot length.

[0342] (Antenna port)

[0343] In one embodiment of the present disclosure, an antenna port refers to a logical antenna (antenna group) composed of one or more physical antennas. For example, an antenna port does not necessarily refer to a physical antenna, but sometimes refers to an array antenna composed of multiple antennas. For example, it may be that the antenna port is not specified to be composed of several physical antennas, but is specified as the minimum unit that the terminal can send a reference signal (reference signal). In addition, an antenna port is sometimes also specified as the minimum unit multiplied by the weight of a precoding vector.

[0344] <5G NR system architecture and protocol stack>

[0345] 3GPP is continuing work to implement the next version of fifth generation mobile technology (also referred to simply as "5G"), including the development of new radio access technology (NR) operating in the frequency range up to 100 GHz. The first version of the 5G standard was completed in late 2017, which enabled the transition to trial production of terminals (e.g., smartphones) compliant with the 5G NR standard and commercial deployment.

[0346] For example, the system architecture as a whole envisions a NG-RAN (Next Generation Radio Access Network) including gNBs. The gNB provides the UE-side termination of the protocols of the user plane (SDAP (Service Data Adaptation Protocol) / PDCP (Packet Data Convergence Protocol) / RLC (Radio Link Control) / MAC / PHY (Physical Layer)) and control plane (RRC) of the NG radio access. The gNBs are connected to each other through an Xn interface. In addition, the gNB is connected to the NGC (Next Generation Core) through a Next Generation (NG) interface, more specifically, to the AMF (Access and Mobility Management Function) (e.g., a specific core entity that executes the AMF) through an NG-C interface, and in addition, to the UPF (User Plane Function) (e.g., a specific core entity that executes the UPF) through an NG-U interface. FIG. 15 shows the NG-RAN architecture (eg, refer to 3GPP TS 38.300 v15.6.0, section 4).

[0347] The protocol stack of the user plane of NR (e.g., refer to 3GPP TS 38.300, Section 4.4.1) includes the PDCP (Packet Data Convergence Protocol (see Section 6.4 of TS 38.300)) sublayer, the RLC (Radio Link Control (see Section 6.3 of TS 38.300)) sublayer and the MAC (Media Access Control (see Section 6.2 of TS 38.300)) sublayer terminated on the network side in the gNB. In addition, a sublayer (SDAP: Service Data Adaptation Protocol) of the new access stratum (AS: Access Stratum) has been introduced on PDCP (e.g., refer to Section 6.5 of 3GPP TS 38.300). In addition, a protocol stack of the control plane is defined for NR (e.g., refer to TS 38.300, Section 4.4.2). An overview of the functions of Layer 2 is described in Section 6 of TS 38.300. The functions of the PDCP sublayer, RLC sublayer and MAC sublayer are listed in Sections 6.4, 6.3 and 6.2 of TS 38.300 respectively. The functions of the RRC layer are listed in Section 7 of TS 38.300.

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

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

[0350] The use cases / extended scenarios of NR may include enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), and massive machine type communications (mMTC), which have various requirements in terms of data rate, latency, and coverage. For example, eMBB is expected to support peak data rates (20 Gbps in the downlink and 10 Gbps in the uplink) and effective (user-experienced) data rates that are about 3 times the data rates provided by IMT-Advanced (International Mobile Telecommunications-Advanced). On the other hand, in the case of URLLC, more stringent requirements are proposed for ultra-low latency (the latency of the user plane is 0.5 ms in UL and DL, respectively) and high reliability (within 1 ms, 1-10-5). Finally, in mMTC, preferably, a high connection density is required (1,000,000 devices / km in an urban environment). 2 ), wide coverage in harsh environments and extremely long battery life (15 years) for a cheap device.

[0351] Therefore, sometimes the parameter set of OFDM that is suitable for one use case (for example, subcarrier spacing (SCS: SubCarrier Spacing), OFDM codeword length, cyclic prefix (CP: Cyclic Prefix) length, number of codewords per scheduling interval) is invalid for other use cases. For example, in low-latency services, it is preferred that the codeword length is shorter than that of mMTC services (therefore, the subcarrier spacing is larger) and / or the number of codewords per scheduling interval (also called "TTI (Transmission Time Interval)") is small. Moreover, in extended scenarios where the delay spread of the channel is large, it is preferred that the CP length is longer than that of scenarios where the delay spread is short. The subcarrier spacing can also be optimized according to the situation to maintain the same CP overhead. The value of the subcarrier spacing supported by NR can be more than one. Correspondingly, subcarrier spacings of 15kHz, 30kHz, 60kHz... are currently considered. The codeword length Tu and the subcarrier spacing Δf are directly related according to the formula Δf=1 / Tu. Similar to the LTE system, the term “resource element” can be used to represent the minimum resource unit composed of one subcarrier with a length of one OFDM / SC-FDMA (Single-Carrier Frequency Division Multiple Access) symbol.

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

[0353] <Functional separation between NG-RAN and 5GC in 5G NR>

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

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

[0356] - Radio Bearer Control, Radio Admission Control, Connection Mobility Control, and Radio Resource Management functions such as dynamically allocating (scheduling) resources to UEs in both uplink and downlink;

[0357] -IP (Internet Protocol) header compression, encryption and integrity protection of data;

[0358] - Selection of the AMF when attaching the UE in case the routing towards the AMF cannot be decided based on the information provided by the UE;

[0359] - Routing of user plane data towards UPF;

[0360] - Routing of control plane information towards the AMF;

[0361] -Set up and disconnect connections;

[0362] - Scheduling and sending of paging messages;

[0363] - Scheduling and sending of system broadcast information (AMF or operation, admission, maintenance function (OAM) as the originator);

[0364] - Settings for measurements and measurement reports for mobility and scheduling;

[0365] - Packet marking of the transmission class in uplink;

[0366] -Session management;

[0367] - Network slicing support;

[0368] - Management of QoS (Quality of Service) flows and mapping to data radio bearers;

[0369] - Support of UE in RRC_INACTIVE state;

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

[0371] -Sharing of wireless access networks;

[0372] -Dual connection;

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

[0374] The access and mobility management function (AMF) hosts the following main functions:

[0375] - Functionality to terminate non-access stratum (NAS) signaling;

[0376] -Security of NAS signaling;

[0377] - Security control of access layer (AS);

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

[0379] - the possibility of reaching the UE in idle mode (including the control and execution of paging retransmission);

[0380] - Management of the registration area;

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

[0382] -Access authentication;

[0383] - Access permission including roaming permission check;

[0384] -Mobility management control (subscription and policy);

[0385] - Network slicing support;

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

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

[0388] - Anchor point for intra-RAT (Radio Access Technology) mobility / inter-RAT (Inter-RAT) mobility (where applicable);

[0389] - External PDU (Protocol Data Unit) session point for interconnection with data networks;

[0390] -Packet routing and forwarding;

[0391] -Policy rule enforcement for packet inspection and user plane;

[0392] - Business usage reporting;

[0393] - Uplink classifier for supporting routing of traffic towards data networks;

[0394] -BranchingPoint used to support multi-homed PDU session;

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

[0396] - Verification of uplink services (mapping of SDF (Service Data Flow) to QoS flows);

[0397] - Downlink packet buffering and downlink data notification triggering function.

[0398] Finally, the Session Management Function (SMF) hosts the following main functions:

[0399] -Session management;

[0400] -Allocation and management of UE IP addresses;

[0401] - UPF selection and control;

[0402] - Traffic steering configuration function in the user plane function (UPF) for directing traffic to the appropriate destination;

[0403] - Enforcement of policies and QoS in the control part;

[0404] -Notification of downlink data.

[0405] <RRC connection setup and re-setup process>

[0406] Figure 17 shows several interactions between the UE, gNB and AMF (5GC entity) when the UE in the NAS part transitions from RRC_IDLE (RRC Idle) to RRC_CONNECTED (RRC Connected) (refer to TS 38.300 v15.6.0).

[0407] RRC is a high-layer signaling (protocol) used for the configuration of UE and gNB. Through this transition, AMF prepares UE context data (which includes, for example, PDU session context, security keys, UE radio capabilities (UE Radio Capability), UE security capabilities (UE Security Capabilities), etc.), and sends it to gNB together with the initial context setup request (INITIAL CONTEXTSETUP REQUEST). Next, the gNB activates AS security together with the UE. The gNB sends a Security Mode Command (SecurityModeCommand) message to the UE, and the UE responds to the gNB with a Security Mode Complete (SecurityModeComplete) message to activate AS security. Then, the gNB sends an RRC Reconfiguration (RRCReconfiguration) message to the UE, and the gNB receives an RRC Reconfiguration Complete (RRCReconfigurationComplete) from the UE for the RRC Reconfiguration message, thereby reconfiguring the Signaling Radio Bearer 2 (SRB2) and the Data Radio Bearer (DRB). For signaling-only connections, since SRB2 and DRB are not configured, the steps related to RRC reconfiguration can be omitted. Finally, the gNB notifies the AMF of the completion of the setup process using the INITIAL CONTEXT SETUP RESPONSE.

[0408] Therefore, the present disclosure provides the following fifth generation core network (5GC) entity (e.g., AMF, SMF, etc.), which includes: a control circuit, which, when in action, establishes a next generation (Next Generation, NG) connection with a gNodeB (gNodeB); and a sending unit, which, when in action, sends an initial context setting message to the gNodeB via the NG connection to set a signaling radio bearer between the gNodeB and the user equipment (UE: User Equipment). Specifically, the gNodeB sends a radio resource control (RRC) signaling containing a resource allocation setting information element (IE: Information Element) to the UE via the signaling radio bearer. Then, the UE sends in the uplink or receives in the downlink based on the resource allocation setting.

[0409] <Application scenarios of IMT after 2020>

[0410] Figure 18 shows several use cases for 5G NR. In the 3rd generation partnership project new radio (3GPP NR), three use cases supporting a wide range of services and applications conceived through IMT-2020 have been studied. The planning and formulation of the first phase of specifications for large-capacity high-speed communications (eMBB: enhanced mobile broadband) has been completed. In current and future work, in addition to gradually expanding support for eMBB, it also includes standardization for ultra-reliable and low-latency communications (URLLC: ultra-reliable and low-latency communications) and multiple simultaneous machine-type communications (mMTC: massive machine-type communications). Figure 18 shows several examples of conceptual utilization scenarios of IMT after 2020 (for example, refer to Figure 2 of ITU-R M.2083).

[0411] The use cases of URLLC have strict requirements related to performance such as throughput, latency (delay) and availability. The use cases of URLLC are conceived as an element technology for realizing future applications such as wireless control of industrial production processes or manufacturing processes, remote medical surgery, automation of power transmission and distribution in smart grids, and traffic safety. The ultra-high reliability of URLLC is supported by determining technologies that meet the requirements set by TR38.913. In version 15 of NR URLLC, as an important requirement, the target user plane latency is 0.5ms in UL (uplink) and 0.5ms in DL (downlink). The overall URLLC requirement for a packet transmission is that the block error rate (BLER) is 1E-5 for a packet size of 32 bytes when the user plane latency is 1ms.

[0412] Considering the physical layer, a number of possible approaches can be used to improve reliability. Current scope for improving reliability includes defining additional CQI (Channel Quality Indicator) tables for URLLC, more compact DCI formats, repetition of PDCCH, etc. However, as NR (an important prerequisite for NR URLLC) becomes more stable and further developed, the scope can be expanded to achieve ultra-high reliability. Specific use cases for NR URLLC in Release 15 include Augmented Reality / Virtual Reality (AR / VR), e-Health, e-Safety and critical applications.

[0413] In addition, the technical enhancements of the NR URLLC target are aimed at improving latency and increasing reliability. Technical enhancements for improving latency include configurable parameter sets, non-slot-based scheduling with flexible mapping, unauthorized (configured authorized) uplink, slot-level repetition in the data channel, and preemption in the downlink. Preemption means stopping the transmission of allocated resources and using the allocated resources for other transmissions that are requested later and meet the necessary conditions of lower latency / higher priority. Therefore, the allowed transmission will be replaced by the subsequent transmission. Preemption can be applied regardless of the specific service type. For example, the transmission of service type A (URLLC) can also be replaced by the transmission of service type B (eMBB, etc.). Technical enhancements related to reliability improvement include dedicated CQI / MCS tables for target BLER of 1E-5.

[0414] The use case of mMTC (Massive Machine Type Communications) is characterized by the fact that typically there are a very large number of connected devices that send relatively small amounts of data that are not susceptible to latency. The devices are required to be low-priced and have very long battery life. From the NR point of view, utilizing very narrow bandwidth portions is one solution that can save power in the UE and extend its battery life.

[0415] As mentioned above, it is predicted that the room for reliability improvement in NR will be further expanded. It is one of the important requirements for all situations. For example, the important requirement related to URLLC and mMTC is high reliability or ultra-high reliability. From the wireless point of view and the network point of view, reliability can be improved in several mechanisms. In general, there are two to three important areas that may help improve reliability. These areas include compact control channel information, repetition of data channels / control channels, and diversity related to frequency domain, time domain and / or space domain. These areas can be used universally to improve reliability regardless of the specific communication scenario.

[0416] For NR URLLC, further use cases with stricter requirements are envisioned, such as factory automation, transportation, and power transmission. The strict requirements are high reliability (up to 10-6 reliability), high availability, packet size up to 256 bytes, time synchronization up to a few microseconds (μs) (the value can be set to 1μs or a few microseconds depending on the frequency range and short latency of around 0.5ms to 1ms (for example, 0.5ms latency in the user plane is set as the target) for the use case.

[0417] Moreover, regarding NR URLLC, from the perspective of the physical layer, there may be several technical enhancements. These technical enhancements include the enhancement of PDCCH (Physical Downlink Control Channel) related to compact DCI, repetition of PDCCH, and increased monitoring of PDCCH. In addition, the enhancement of UCI (Uplink Control Information) is related to the enhancement of enhanced HARQ (Hybrid Automatic Repeat Request) and CSI feedback. In addition, there may be enhancement of PUSCH related to frequency hopping at the mini-slot level and enhancement of retransmission / repetition. The term "mini-slot" refers to a transmission time interval (TTI) that contains fewer symbols than a slot (a slot has 14 symbols).

[0418] <QoS Control>

[0419] The 5G QoS (Quality of Service) model is based on QoS flows, supporting both QoS flows that require guaranteed bit rate (GBR: Guaranteed Bit Rate QoS flows) and QoS flows that do not require guaranteed bit rate (non-GBR QoS flows). Therefore, at the NAS level, QoS flows are the most fine-grained QoS divisions in a PDU session. QoS flows are determined within a PDU session based on the QoS flow ID (QFI: QoS Flow ID) transmitted by the encapsulation header via the NG-U interface.

[0420] For each UE, 5GC establishes more than one PDU session. For each UE, in conjunction with the PDU session, NG-RAN establishes at least one data radio bearer (DRB), for example as described above with reference to Figure 17. In addition, the DRB added to the QoS flow of the PDU session can also be set later (when to set it depends on NG-RAN). NG-RAN maps packets belonging to various PDU sessions to various DRBs. The NAS-level packet filters in the UE and 5GC are used to associate UL packets and DL packets with QoS flows, and the AS-level mapping rules in the UE and NG-RAN associate UL QoS flows and DL QoS flows with DRBs.

[0421] Figure 19 shows the non-roaming reference architecture of 5G NR (refer to TS 23.501 v16.1.0, section 4.23). The application function (AF) (for example, an external application server hosting the 5G service illustrated in Figure 18) interacts with the 3GPP core network to provide services. For example, accessing the Network Exposure Function (NEF) to support applications that affect the routing of the service, or interacting with the policy framework for policy control (for example, QoS control) (refer to the Policy Control Function (PCF)). Based on the operator's deployment, the operator considers that trusted application functions can interact directly with the associated network function (Network Function). Application functions that are not allowed by the operator to directly access the network function interact with the associated network function via the NEF using an open framework to the outside.

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

[0423] Therefore, the present disclosure provides the following application server (for example, AF of 5G architecture), which includes: a sending unit, which, in action, sends a request for QoS requirements for at least one of URLLC service, eMMB service and mMTC service to at least one of the functions of 5GC (for example, NEF, AMF, SMF, PCF, UPF, etc.) in order to establish a PDU session of a wireless bearer between a g-node B and a UE corresponding to the QoS requirements; and a control circuit, which, in action, uses the established PDU session to provide service.

[0424] The present disclosure can be implemented by software, hardware, or software in cooperation with hardware. The functional blocks used in the description of the above embodiments are partially or entirely implemented as LSI (Large Scale Integration) as an integrated circuit, and the processes described in the above embodiments may also be partially or entirely controlled by one LSI or a combination of LSIs. LSI can be composed of individual chips, or it can be composed of one chip in a manner that includes part or all of the functional blocks. LSI may also include data input and output. LSI may also be referred to as "IC (Integrated Circuit)", "System LSI", "Super LSI", "Ultra LSI" depending on the degree of integration.

[0425] The method of integrated circuitization is not limited to LSI, and can also be implemented by a dedicated circuit, a general-purpose processor or a dedicated processor. In addition, an FPGA (Field Programmable Gate Array) that can be programmed after LSI manufacturing, or a reconfigurable processor (Reconfigurable Processor) that can reconfigure the connection or setting of the circuit block inside the LSI can also be used. The present disclosure can also be implemented as digital processing or analog processing.

[0426] Furthermore, if integrated circuit technology that replaces LSI emerges as semiconductor technology advances or other technologies are derived, it is of course possible to use this technology to achieve integration of functional blocks. There is also the possibility of applying biotechnology, etc.

[0427] The present disclosure can be implemented in all kinds of devices, equipment, and systems (collectively referred to as "communication devices") with communication functions. The communication device may also include a wireless transceiver and a processing / control circuit. The wireless transceiver may also include a receiving unit and a transmitting unit, or perform the functions of these parts. The wireless transceiver (transmitting unit, receiving unit) may also include an RF (Radio Frequency) module and one or more antennas. The RF module may also include an amplifier, an RF modulator / demodulator, or a device similar to these. Non-limiting examples of communication devices include: telephones (mobile phones, smart phones, etc.), tablet computers, personal computers (PCs) (laptops, desktops, notebook computers, etc.), cameras (digital cameras, digital video cameras, etc.), digital players (digital audio / video players, etc.), wearable devices (wearable cameras, smart watches, tracking devices, etc.), game consoles, e-book readers, telehealth / telemedicine (telehealth / medical prescription) equipment, vehicles with communication functions or transportation vehicles (cars, airplanes, ships, etc.), and combinations of the above-mentioned various devices.

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

[0429] The communication includes data communication performed by a cellular system, a wireless LAN (Local Area Network) system, a communication satellite system, etc., and also includes data communication performed by a combination of these systems.

[0430] In addition, the communication device also includes devices such as controllers or sensors connected or linked to the communication device that performs the communication function described in the present invention. For example, it includes a controller or sensor that generates a control signal or data signal used by the communication device that performs the communication function of the communication device.

[0431] In addition, the communication device includes infrastructure equipment that communicates with the above-mentioned non-limiting various devices or controls the above-mentioned various devices, such as base stations, access points, and all other devices, equipment, and systems.

[0432] A terminal of one embodiment of the present disclosure includes: a receiving circuit, which receives control information related to a reference location for a reference time in a first cell, wherein the reference time is a reference time in the transmission timing control of an uplink signal sent to a second cell different from the first cell; and a control circuit, which controls the transmission timing based on the control information.

[0433] In one embodiment of the present disclosure, the control information indicates which of the first cell and the second cell the reference location is a synchronization location of an uplink signal.

[0434] In one embodiment of the present disclosure, the receiving circuit receives information indicating which of the first cell and the second cell the reference time is based on.

[0435] In one embodiment of the present disclosure, when information related to the transmission timing control is generated in the base station of the second cell, the control information indicates that the reference location is a location where an uplink signal of the second cell is synchronized.

[0436] In one embodiment of the present disclosure, when the information related to the transmission timing control is generated in a device different from the base station of the second cell, the control information indicates that the reference location is a location where uplink signals are synchronized in the first cell.

[0437] In one embodiment of the present disclosure, the reference time for the second cell is represented by absolute time.

[0438] A base station of one embodiment of the present disclosure includes: a control circuit, which determines control information related to a reference location for a reference time in a first cell, wherein the reference time is a reference time in a transmission timing control of an uplink signal sent to a second cell different from the first cell; and a transmission circuit, which sends the control information.

[0439] In a communication method of one embodiment of the present disclosure, the terminal performs the following processing: receiving control information related to a reference location for a reference time in a first cell, wherein the reference time is a reference time in a transmission timing control of an uplink signal sent to a second cell different from the first cell; and controlling the transmission timing based on the control information.

[0440] In a communication method of one embodiment of the present disclosure, the base station performs the following processing: determines control information related to a reference location for a reference time in a first cell, wherein the reference time is a reference time in a timing control of a transmission of an uplink signal sent to a second cell different from the first cell; and sends the control information.

[0441] Industrial Applicability

[0442] One aspect of the present disclosure is useful for a wireless communication system.

[0443] Description of Reference Numerals

[0444] 100 Base Stations

[0445] 101 Data Generation Unit

[0446] 102 Control Department

[0447] 103, 206 Data transmission processing unit

[0448] 104, 207 Wireless Transmission Unit

[0449] 105, 201 Antenna

[0450] 106, 202 wireless receiving unit

[0451] 107, 203 Data receiving and processing unit

[0452] 200 Terminal

[0453] 204 Location information acquisition unit

[0454] 205 Timing Adjustment Department

[0455] 300 NTN control unit.

Claims

1. A terminal, characterized in that: include: a receiving circuit for receiving, in a first cell, control information related to a reference location for a reference time, the reference time being a reference time in a transmission timing control of an uplink signal sent to a second cell different from the first cell; as well as The control circuit controls the transmission timing based on the control information.

2. The terminal according to claim 1, wherein: The control information indicates whether the reference point is a synchronization point of an uplink signal in the first cell or the second cell.

3. The terminal according to claim 1, wherein: The receiving circuit receives information indicating whether the reference time is based on the first cell or the second cell.

4. The terminal according to claim 1, wherein: When the information related to the transmission timing control is generated in the base station of the second cell, the control information indicates that the reference point is a point at which uplink signals are synchronized in the second cell.

5. The terminal according to claim 1, wherein: When the information related to the transmission timing control is generated in a device different from the base station of the second cell, the control information indicates that the reference point is a point at which uplink signals are synchronized in the first cell.

6. The terminal according to claim 1, wherein: The reference time for the second cell is represented by absolute time.

7. A base station, characterized in that: include: a control circuit that determines, in a first cell, control information related to a reference point for a reference time, the reference time being a reference time in a transmission timing control of an uplink signal to a second cell different from the first cell; as well as The sending circuit sends the control information.

8. A communication method, characterized in that: The terminal performs the following processing: receiving, in a first cell, control information related to a reference location for a reference time, the reference time being a reference time in controlling a transmission timing of an uplink signal sent to a second cell different from the first cell; as well as Based on the control information, the transmission timing is controlled.

9. A communication method, characterized in that: The base station performs the following processing: determining, in a first cell, control information related to a reference point for a reference time, the reference time being a reference time in controlling a transmission timing of an uplink signal to a second cell different from the first cell; as well as The control information is sent.