Terminal and wireless communication method

Abstract

This terminal sets the timing adjustment value of uplink transmission on the basis of position information indicating the terminal position, and transmits the uplink at the set timing. The terminal transitions from a connected state in a wireless resource control layer to an inactive state, and acquires the position information.

Description

Terminal and wireless communication method

[0001] The present disclosure relates to reduced capability terminals and wireless communication methods.

[0002] The 3rd Generation Partnership Project (3GPP: registered trademark) is developing specifications for the 5th generation mobile communication system (5G, also known as New Radio (NR) or Next Generation (NG)), and is also developing specifications for the next generation, known as Beyond 5G, 5G Evolution, or 6G.

[0003] 3GPP Release-17 specifies support for reduced-capability terminals (User Equipment, UE). Such UEs are also called RedCap UEs (reduced UE capability) and are suitable for industrial wireless sensors, video surveillance, and wearable terminals. RedCap UEs are limited in the number of receive antennas (also called RX branches).

[0004] In addition, 3GPP Release-18 is considering the introduction of a new RedCap UE (which may also be called eRedCap UE) that may further restrict bandwidth, peak data rate, etc. (Non-Patent Document 1).

[0005] "Revised WID on Enhanced support of reduced capability NR devices", RP-223544, 3GPP TSG RAN Meeting #98-e, 3GPP, December 2022

[0006] When using a non-terrestrial network (NTN), the UE needs to acquire its current location using a global navigation satellite system (GNSS) or the like, and set a timing advance (TA) to adjust the uplink transmission timing based on the acquired location information.

[0007] However, in the case of RedCap UE, from the viewpoint of reducing manufacturing costs, it may not be possible to simultaneously acquire location information and transmit uplink (UL) and receive downlink (DL) via the Uu interface (between the UE and the radio base station (gNB)).

[0008] Therefore, the following disclosure has been made in consideration of this situation, and aims to provide a terminal and a wireless communication method that can efficiently acquire location information and perform UL transmission / DL reception even when using a non-terrestrial network, etc.

[0009] One aspect of the present disclosure is a terminal (UE) that includes a control unit (control unit 270) that sets a timing adjustment value for uplink transmission based on location information indicating the terminal location, and a communication unit (radio signal transceiver unit 210) that transmits the uplink at the set timing, and the control unit is a terminal (UE) that transitions from a connected state to an inactive state in a radio resource control layer and acquires the location information.

[0010] One aspect of the present disclosure includes a control unit (control unit 270) that sets a timing adjustment value for uplink transmission based on location information indicating the terminal location, and a communication unit (radio signal transceiver unit 210) that transmits the uplink at the set timing, wherein the control unit is a terminal (UE200) that transitions from a connected state or an inactive state in a radio resource control layer to an idle state and acquires the location information.

[0011] FIG. 1 is a schematic diagram of the overall configuration of a wireless communication system 10. FIG. 2 is a diagram showing an example of the configuration of a wireless frame, subframe, and slot used in the wireless communication system 10. FIG. 3 is a functional block diagram of a gNB 100 and a UE 200. FIG. 4 is a diagram showing an example of a formula for calculating a TA value when passing through an NTN. FIG. 5 is a diagram showing an example (part 1) of a communication sequence between a gNB and a UE according to an operation example 1. FIG. 6 is a diagram showing an example (part 2) of a communication sequence between a gNB and a UE according to an operation example 1. FIG. 7 is a diagram showing an example (part 1) of a location information acquisition operation according to an operation example 2. FIG. 8 is a diagram showing an example (part 2) of a location information acquisition operation according to an operation example 2. FIG. 9 is a diagram showing an example of the hardware configuration of a gNB 100 and a UE 200. FIG. 10 is a diagram showing an example of the configuration of a vehicle 2001.

[0012] Hereinafter, embodiments will be described with reference to the drawings. Note that the same or similar reference numerals are used to designate the same functions or configurations, and descriptions thereof will be omitted as appropriate.

[0013] (1) Overall Schematic Configuration of Wireless Communication System Fig. 1 is a diagram showing the overall schematic configuration of a wireless communication system 10 according to this embodiment. The wireless communication system 10 is a wireless communication system conforming to 5G New Radio (NR) and includes a Next Generation-Radio Access Network 20 (hereinafter, NG-RAN 20) and a terminal 200 (hereinafter, UE (User Equipment) 200).

[0014] The wireless communication system 10 may be a wireless communication system conforming to a system called Beyond 5G, 5G Evolution, or 6G.

[0015] The NG-RAN 20 includes a radio base station 100 (hereinafter, gNB 100). Note that the specific configuration of the radio communication system 10, including the number of gNBs 100 and UEs 200, is not limited to the example shown in FIG. 1 .

[0016] The NG-RAN 20 actually includes a plurality of NG-RAN nodes, specifically, gNBs (or ng-eNBs), and is connected to a core network conforming to 5G (for example, 5GC). Note that the NG-RAN 20 and the core network may be simply referred to as a "network."

[0017] The gNB100 is a 5G-compliant radio base station that performs 5G-compliant radio communication with the UE 200. The gNB100 and UE 200 are capable of supporting Massive MIMO (Multiple-Input Multiple-Output), which generates a more directional beam (BM) by controlling radio signals transmitted from multiple antenna elements, Carrier Aggregation (CA), which aggregates multiple component carriers (CCs), and Dual Connectivity (DC), which simultaneously communicates between the UE and two NG-RAN nodes.

[0018] In an embodiment, the wireless communication system 10 may include a non-terrestrial network (NTN). In an NTN, services are provided to areas that cannot be covered by a terrestrial network (TN) due to cost or other reasons by utilizing an NTN such as an artificial satellite 150 (hereinafter, satellite 150). The NTN can provide more reliable services. For example, the NTN is expected to be applied to IoT (Internet of Things), ships, buses, trains, and critical communications. The NTN also has scalability through efficient multicast or broadcast.

[0019] A network including the gNB 100 and the UE 200 but not including the satellite 150 may be referred to as a TN in contrast to an NTN. The satellite 150 may have the function of a gNB (radio base station). The type of satellite 150 is not particularly limited, and may be, for example, a geostationary orbit satellite (GEO) or a low earth orbit satellite (LEO). Alternatively, a high-altitude platform station (HAPS) may be used.

[0020] In this embodiment, the gNB 100 may include an NTN gateway 100X. The NTN gateway 100X transmits downlink signals to the satellite 150. The NTN gateway 100X receives uplink signals from the satellite 150.

[0021] The satellite 150 relays the downlink signal received from the NTN gateway 100X to the UE 200. The satellite 150 relays the uplink signal received from the UE 200 to the NTN gateway 100X. The satellite 150 may be interpreted as a TRP (Transmission-Reception Point), or as a repeater or relay.

[0022] The UE 200 may acquire location information indicating the current location of the UE 200. Specifically, the UE 200 may acquire location information (e.g., longitude and latitude information) of the UE 200 using a global navigation satellite system (GNSS 170). Note that the location information does not necessarily have to be acquired by the GNSS 170, and may be acquired by another method (e.g., using the positional relationship between a plurality of gNBs 100 and the UE 200).

[0023] Furthermore, UE200 may be a RedCap UE as described later. In the case of a RedCap UE, from the viewpoint of reducing manufacturing costs, etc., it may not be possible to simultaneously acquire location information using GNSS170 and perform uplink (UL) transmission / downlink (DL) reception via the Uu interface (between the UE and the radio base station (gNB)). Specifically, when acquiring location information using GNSS170, UE200 may suspend UL / DL transmission / reception using the Uu interface. Furthermore, UE200 may not be able to acquire location information using GNSS170 when using the Uu interface.

[0024] To achieve Coverage Enhancement (CE), the UE 200 may support repetition of uplink channels (e.g., PUCCH (Physical Uplink Control Channel) and PDSCH (Physical Downlink Shared Channel)). The UE 200 may support CE Mode A and CE Mode B (see 3GPP TS38.213, etc.) as coverage enhancement modes (CE Mode). CE Mode is a technology that effectively enhances cell coverage by gradually lowering the threshold of the received power level (RSRP: Reference Signal Received Power / RSRQ: Reference Signal Received Quality). The number of attempts of a random access procedure (RA procedure) according to the mode is also specified.

[0025] Furthermore, for coverage extension, TB processing over multi-slot PUSCH (TBoMS) may be applied, which processes a transport block (TB) via a PUSCH allocated to multiple slots.

[0026] Although the type of UE 200 is not particularly limited, in the present embodiment, the capability of UE 200 may be reduced. The reduced capability is not particularly limited, but for example, capability (operation) related to measurements for radio resource management (RRM) may be reduced (which may be restricted, reduced, or the like).

[0027] Such a UE may be called a RedCap UE (reduced UE capability), etc. RedCap UE may be interpreted as a category of UE used for, for example, industrial wireless sensors, video surveillance, and wearable devices.

[0028] Alternatively, the RedCap UE may not necessarily have reduced capabilities and may be interpreted as a UE for IoT (Internet of Things), etc. The RedCap UE may also be referred to as a specific type of UE.

[0029] On the other hand, a non-RedCap UE may be interpreted as a normal UE having normal capabilities, or a UE for enhanced Mobile Broadband (eMBB), or Ultra-Reliable and Low Latency Communications (URLLC). Note that a normal UE may include a UE for eMBB or URLLC.

[0030] The RedCap UE is specified in 3GPP Release-17 and may have different numbers of receive antennas (also called RX branches). Specifically, there may be RedCap UEs with one receive antenna (1 RX branch) and RedCap UEs with two receive antennas (2 RX branches). However, the number of receive antennas does not necessarily have to be limited to 1 RX branch and 2 RX branches.

[0031] Furthermore, the functionality (capabilities) of a RedCap UE may be further reduced. Specifically, the bandwidth and peak data rate may be further restricted compared to a RedCap UE. Such a RedCap UE may be specified in 3GPP Release-18 and may be called an eRedCap UE (enhanced reduced UE capability) to distinguish it from a RedCap UE of Release-17. Note that when a term "RedCap UE" is used, it may be interpreted as including an eRedCap UE unless otherwise specified.

[0032] For example, in the case of an eRedCap UE, the baseband (BB) bandwidth used for transmitting and receiving a specific channel may be limited to 5 MHz or 10 MHz (usually 20 MHz), and the peak data rate may be further reduced by changing certain parameters. In addition, the subcarrier spacing (SCS) may be 15 kHz or 30 kHz.

[0033] The RedCap UE does not have to support simultaneous operation of acquiring location information using GNSS 170 and UL transmission or DL ​​reception. However, the RedCap UE may support simultaneous operation of acquiring location information and UL transmission or DL ​​reception.

[0034] Furthermore, the UE 200 may include a UE for Narrow Band Internet of Things (NB-IoT) and enhanced Machine Type Communication (eMTC). In such a UE 200 (including RedCap UE), multi-TB scheduling, which performs scaling for multiple transport blocks (TBs), may be applied.

[0035] FIG. 2 shows an example of the configuration of radio frames, subframes, and slots used in the radio communication system 10.

[0036] As shown in Figure 2, one slot consists of 14 symbols, and the larger (wider) the SCS, the shorter the symbol period (and slot period). The SCS is not limited to the interval (frequency) shown in Figure 2. For example, 480 kHz, 960 kHz, etc. may be used.

[0037] Furthermore, the number of symbols constituting one slot does not necessarily have to be 14 (for example, 28 symbols or 56 symbols). Furthermore, the number of slots per subframe may differ depending on the SCS.

[0038] The time direction (t) shown in Fig. 2 may be called a time domain, a symbol period, or a symbol time, etc. The frequency direction may be called a frequency domain, a resource block, a subcarrier, a bandwidth part (BWP), etc.

[0039] (2) Functional Block Configuration of Wireless Communication System Next, a functional block configuration of the wireless communication system 10 will be described. Specifically, the functional block configurations of the gNB 100 and the UE 200 will be described.

[0040] 3 is a functional block diagram of the gNB 100 and the UE 200. The following describes the UE 200. As shown in FIG. 3, the UE 200 includes a radio signal transmitting / receiving unit 210, an amplifier unit 220, a modulation / demodulation unit 230, a control signal / reference signal processing unit 240, an encoding / decoding unit 250, a data transmitting / receiving unit 260, and a control unit 270.

[0041] The radio signal transmission / reception unit 210 transmits and receives radio signals conforming to NR. The radio signal transmission / reception unit 210 supports Massive MIMO, CA that uses a bundle of multiple CCs, and DC that simultaneously communicates between a UE and two NG-RAN nodes.

[0042] Furthermore, the radio signal transmitting / receiving unit 210 may transmit uplink (UL) and receive downlink (DL) signals using the Uu interface. The radio signal transmitting / receiving unit 210 can transmit UL signals at set timing. In this embodiment, the radio signal transmitting / receiving unit 210 may constitute a communication unit.

[0043] The radio signal transmitting / receiving unit 210 may transmit the UL at a timing adjusted by a timing advance (TA). As will be described later, the TA may be determined based on location information of the UE 200.

[0044] The amplifier unit 220 is configured by a PA (Power Amplifier) / LNA (Low Noise Amplifier), etc. The amplifier unit 220 amplifies the signal output from the modulation / demodulation unit 230 to a predetermined power level. The amplifier unit 220 also amplifies the RF signal output from the radio signal transmission / reception unit 210.

[0045] The modem unit 230 performs data modulation / demodulation, transmission power setting, resource block allocation, etc. for each predetermined communication destination (e.g., gNB 100). The modem unit 230 may apply Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) / Discrete Fourier Transform - Spread (DFT-S-OFDM). Furthermore, DFT-S-OFDM may be used not only for the uplink (UL) but also for the downlink (DL).

[0046] The control signal and reference signal processor 240 executes processing related to various control signals transmitted and received by the UE 200 and processing related to various reference signals transmitted and received by the UE 200 .

[0047] Specifically, the control signal / reference signal processing unit 240 receives various control signals, for example, control signals of a radio resource control layer (RRC), transmitted via a predetermined control channel from the gNB 100. In addition, the control signal / reference signal processing unit 240 transmits various control signals to the gNB 100 via a predetermined control channel.

[0048] The control signal / reference signal processor 240 performs processing using reference signals (RS) such as a Demodulation Reference Signal (DMRS) and a Phase Tracking Reference Signal (PTRS).

[0049] DMRS is a terminal-specific reference signal (pilot signal) known between the base station and the terminal to estimate the fading channel used for data demodulation, while PTRS is a terminal-specific reference signal intended to estimate phase noise, which is an issue in high frequency bands.

[0050] In addition to the DMRS and PTRS, the reference signals may also include a Channel State Information-Reference Signal (CSI-RS), a Sounding Reference Signal (SRS), and a Positioning Reference Signal (PRS) for position information.

[0051] The channels include a control channel and a data channel. The control channels may include a physical downlink control channel (PDCCH), a physical uplink control channel (PUCCH), a random access channel (RACH, DCI including a random access radio network temporary identifier (RA-RNTI)), a physical broadcast channel (PBCH), etc.

[0052] Furthermore, the data channel includes a physical downlink shared channel (PDSCH), a physical uplink shared channel (PUSCH), etc. Data may refer to data transmitted via a data channel.

[0053] The encoding / decoding unit 250 performs data division / concatenation and channel coding / decoding for each predetermined communication destination (gNB 100 or another gNB).

[0054] Specifically, the encoding / decoding unit 250 divides the data output from the data transmitting / receiving unit 260 into pieces of a predetermined size, performs channel coding on the divided data, decodes the data output from the modem unit 230, and concatenates the decoded data.

[0055] The data transmitter / receiver 260 transmits and receives Protocol Data Units (PDUs) and Service Data Units (SDUs). Specifically, the data transmitter / receiver 260 assembles and disassembles PDUs / SDUs in multiple layers (such as a Medium Access Control layer (MAC), a Radio Link Control layer (RLC), and a Packet Data Convergence Protocol layer (PDCP)). The data transmitter / receiver 260 also performs data error correction and retransmission control based on Hybrid Automatic Repeat Request (Hybrid ARQ).

[0056] The control unit 270 controls each functional block that configures the UE 200. In particular, in this embodiment, the control unit 270 can execute settings related to RedCap UE when using NTN.

[0057] Specifically, the control unit 270 may set a timing advance (TA) for uplink (UL) transmission based on location information indicating the current location (terminal location) of the UE 200.

[0058] More specifically, the control unit 270 may calculate a TA value when passing through an NTN. When passing through an NTN, a UE-specific TA (NTN) is used to compensate for the delay of the service link (between the UE and the satellite). TA, UE-specific ) and the feeder link side, specifically, the common TA (N TA, common ) is used. N TA, UE-specific may be calculated using the current location (location information) of the UE.

[0059] If the UE 200 is a RedCap UE and is unable to simultaneously acquire location information and perform UL transmission or downlink (DL) reception via the radio signal transceiver 210 (Uu interface), the control unit 270 may transition from a connected state (RRC_CONNECTED) in the radio resource control layer (RRC) to an inactive state (RRC_INACTIVE) and acquire location information.

[0060] In RRC_INACTIVE, the UE 200 and the radio access network (RAN) retain the UE context, but the radio bearer configuration is released. Specifically, in RRC_INACTIVE, the UE AS (Access Stratum) context is retained by the gNB 100 and the UE 200, but the Signaling Radio Bearer (SRB) / Data Radio Bearer (DRB) configuration is released within the gNB 100.

[0061] Furthermore, the control unit 270 may transition from RRC_CONNECTED or RRC_INACTIVE to an idle state (RRC_IDLE) to acquire location information. RRC_IDLE may indicate a state in which all RRC settings related to the UE 200 are released.

[0062] The control unit 270 may determine, based on an instruction from the network, whether or not simultaneous operation of acquiring location information using the GNSS 170 and UL transmission or DL ​​reception by the wireless signal transmitting / receiving unit 210 is required.

[0063] For example, the control unit 270 may determine whether or not the system information (SIB: System Information Block) indicates that the network must simultaneously perform location information acquisition and UL transmission or DL ​​reception. Note that the instruction from the network is not limited to an SIB (e.g., SIB1), but may be broadcast information such as an MIB (Master Information Block), or signaling in a higher layer (e.g., RRC) or a lower layer.

[0064] When the control unit 270 receives an instruction from the network via the NTN indicating that simultaneous operation of acquiring location information and UL transmission or DL ​​reception is required, and when the UE 200 does not support such simultaneous operation, the control unit 270 may assume that connection to the network via the NTN is prohibited. Note that even in this case, the control unit 270 may assume that connection to the network via the TN is not prohibited. Alternatively, in this case, the control unit 270 may assume that connection to the network via the TN is prohibited.

[0065] Furthermore, the control unit 270 may transmit capability information (UE Capability Information) indicating whether the simultaneous operation is supported to the network. For example, the control unit 270 may transmit the UE Capability Information to the network by PRACH, Msg.3 PUSCH, or signaling in a higher or lower layer.

[0066] (3) Operation of the Wireless Communication System Next, a description will be given of the operation of the wireless communication system 10. Specifically, a description will be given of the operation related to the execution of wireless communication via the NTN when the UE 200 is a Normal UE or a RedCap UE.

[0067] (3.1) Background and Issues 3GPP is considering the following items regarding RedCap UE (which may include eRedCap UE):

[0068] - Reduction of maximum bandwidth - Reduction of minimum number of receiving antennas (RX branch) / DL MIMO layers - Maximum modulation method - Half-duplexing of frequency division duplex (FDD) - Relaxation of processing time regulations - Relaxation of RRM requirements for UEs located at the center of the cell 3GPP is also considering the following NTN-specific features that may affect RedCap UEs:

[0069] ・Common DL / UL performance for normal UE and RedCap UE ・NTN-specific Timing Advance (TA) adjustment ・Simultaneous operation of GNSS (global navigation satellite system) and Uu (UE-gNB) interfaces ・Common TA parameters ・TA update during UL repeat transmission ・Two-step RACH Figure 4 shows an example of the calculation formula for the TA value when going through an NTN. As shown in Figure 4, when going through an NTN, a UE-specific TA (N TA, UE-specific ) and the feeder link side, specifically, the common TA (N TA, common ) is used. N TA, UE-specific may be calculated using the current location (location information) of the UE.

[0070] When NTN is used, the TA value is determined by the UE, and the N TA, UE-specific It is assumed that the location information of the UE is acquired using GNSS.

[0071] However, in the case of RedCap UE, in order to reduce costs, GNSS acquisition may not be possible simultaneously with DL / UL communication. 3GPP Release-17 specifies that GNSS-based acquisition of UE location information should be performed in the RRC_IDLE state (in the case of IoT (Internet of Things)-NTN). On the other hand, in the RRC_CONNECTED state, acquisition of GNSS-based location information is not expected. After a certain period of time has passed, if the location information is old, the UE transitions to the RRC_IDLE state to acquire location information.

[0072] For RedCap UE, it is necessary to efficiently acquire location information and perform DL / UL communication (Uu interface) especially when going through NTN, while assessing the performance of RedCap UE. Below, we will explain an example of operation that can solve these problems.

[0073] (3.2) Overview of Operation Below, we will explain the regulations and operations (Operation Example 1) regarding the simultaneous operation of RedCap UE's GNSS-based location information acquisition (which may also be called GNSS acquisition) and the Uu interface when going via NTN, and the specific operations (Operation Example 2) when the RedCap UE does not support the simultaneous operation of the location information acquisition and the Uu interface.

[0074] Note that the following operation example may also be applied to Small Data Transmission (SDT) enabled in RRC_INACTIVE. Specifically, different mechanisms may be applied to SDT in RRC_INACTIVE and data transmission / reception in RRC_CONNECTED.

[0075] (3.3) Operation Example 1 With regard to simultaneous operation of RedCap UE's GNSS-based location information acquisition and Uu interface when going via NTN, any of the following may be specified.

[0076] (a): RedCap UE supports simultaneous operation of GNSS-based location information acquisition and Uu interface (UL / DL communication). If a UE (assuming a RedCap UE here) does not support this simultaneous operation, it may be considered that the RedCap UE's access to cells formed by the NTN (NTN cells) is restricted.

[0077] (b): The network informs the UE via MIB or SIB whether it is mandatory for the RedCap UE to support GNSS location acquisition and simultaneous operation with the Uu interface.

[0078] Fig. 5 shows an example (part 1) of a communication sequence between a gNB and a UE according to Operation Example 1. As shown in Fig. 5, the gNB may use MIB or SIB to notify the UE whether or not support for simultaneous operation of GNSS location information acquisition by the RedCap UE and the Uu interface is required (for example, ntn-config may be used).

[0079] If a UE (assumed to be a RedCap UE here) is notified that support for the simultaneous operation is mandatory and does not support the simultaneous operation, the UE may consider that its access to a cell formed by an NTN (NTN cell) is restricted.

[0080] (c): UEs that support simultaneous operation of location information acquisition and the Uu interface (Normal UEs) and non-supporting UEs that do not support such simultaneous operation (RedCap UEs) are permitted to access the network.

[0081] Fig. 6 shows an example (part 2) of a communication sequence between a gNB and a UE according to operation example 1. As shown in Fig. 6, the gNB may use an MIB or SIB to notify the UE whether access by Normal UE and RedCap UE via the NTN is permitted.

[0082] The UE may report whether it supports simultaneous operation of location information acquisition and the Uu interface via the PRACH, Msg.3 PUSCH, or signaling in a higher or lower layer.

[0083] (d) It is assumed that the RedCap UE does not support simultaneous location information acquisition and Uu interface operation, i.e., the RedCap UE performs location information acquisition and Uu interface at different times.

[0084] Note that "simultaneous operation of obtaining location information using GNSS and the Uu interface" may be interpreted as follows:

[0085] - Location information is not (cannot be) obtained using GNSS in the RRC_CONNECTED and / or RRC_INACTIVE state. - Location information is not (cannot be) obtained using GNSS during DL reception and / or UL transmission. - Location information is not (cannot be) obtained using GNSS during the active period of discontinuous reception (DRX). In addition, a UE that can simultaneously perform location information acquisition using GNSS and the Uu interface is a RedCap UE, and a UE that cannot perform these simultaneous operations may be an eRedCap UE.

[0086] This operation example clarifies whether RedCap UEs need to simultaneously operate the Uu interface and obtain location information using GNSS when passing through the NTN, which is expected to result in stable operation of the RedCap UEs. Furthermore, eliminating the need to support such simultaneous operation reduces UE manufacturing costs. Furthermore, restricting (prohibiting) network access for UEs that do not support such simultaneous operation simplifies processing on the network (gNB) side, potentially contributing to cost reductions.

[0087] (3.4) Operation Example 2: If the RedCap UE does not support simultaneous operation of the location information acquisition and the Uu interface, the UE (RedCap UE) may operate as follows: Specifically, if the location information held by the UE is old (a certain period of time has passed since acquisition), the UE may operate as follows.

[0088] (a): The UE transitions from RRC_CONNECTED to RRC_INACTIVE and acquires its location information using GNSS.

[0089] FIG. 7 illustrates a location information acquisition operation example (part 1) according to operation example 2. The suspendConfig (configuration for RRC_INACTIVE) may be provided in advance by the gNB. As illustrated in FIG. 7 , when the location information becomes stale or before the location information becomes stale, the UE may transition from RRC_CONNECTED to RRC_INACTIVE and acquire the location information. Furthermore, when the location information becomes stale or before the location information becomes stale, the UE may report to the network that it will (have) transitioned to RRC_INACTIVE and / or the timing of the transition.

[0090] The timing and / or window of the report may be configured by the gNB or determined by the UE, and may be configured to correspond to the gnss-validityDuration (the remaining validity period of the location information).

[0091] When returning from RRC_INACTIVE to RRC_CONNECTED, the UE may behave as follows:

[0092] Once location information acquisition is complete, execute the RRC resumption process (resume or connection reestablishment).

[0093] Once location information acquisition is complete, the UE returns to RRC_CONNECTED without performing the RRC restart procedure. In this case, the UE may send related information (e.g., the transition, gnss-validityDuration) to the gNB.

[0094] A timer is started when the UE transitions to RRC_INACTIVE. This timer may be configured by the gNB or the UE. When this timer expires, the UE returns to RRC_CONNECTED without performing an RRC resume procedure (resume or connection reestablishment). In this case, the UE performs location acquisition while the timer is running. If the location acquisition fails, the UE may transition to RRC_IDLE. The UE may also send related information (e.g., the transition, gnss-validityDuration) to the gNB.

[0095] By transitioning from RRC_CONNECTED to RRC_INACTIVE and acquiring the location information of the UE using GNSS, it is possible to reduce delays in acquiring the location information.

[0096] (b): The UE transitions from RRC_CONNECTED or RRC_INACTIVE to RRC_IDLE and acquires its location information using GNSS.

[0097] Fig. 8 shows a location information acquisition operation example (part 2) according to operation example 2. As shown in Fig. 8 , when the location information becomes outdated or before the location information becomes outdated, the UE may transition from RRC_CONNECTED or RRC_INACTIVE to RRC_IDLE and acquire the location information.

[0098] In this case, the UE may perform the same operation as that performed when a normal UE transitions to RRC_IDLE via a TN (or other cases). Alternatively, the operation (a) above may be performed with RRC_IDLE substituted for RRC_INACTIVE. This may avoid complex UE implementation.

[0099] Either the operation of transitioning from RRC_CONNECTED to RRC_INACTIVE and acquiring the location information (above (a)) or the operation of transitioning from RRC_CONNECTED or RRC_INACTIVE to RRC_IDLE and acquiring the location information (above (b)) may be applied or instructed via MIB / SIB or UE-specific configuration (signaling).

[0100] In addition, it may be determined whether the operation (a) or (b) is applied depending on the capabilities of the UE (for example, whether the RRC_INACTIVE state is supported).

[0101] With regard to establishing or re-establishing a connection in RRC, the RedCap UE may re-acquire the location information before establishing or re-establishing the connection, i.e., at the start of the procedure to transition from RRC_IDLE / RRC_INACTIVE to RRC_CONNECTED.

[0102] The transition from RRC_IDLE / RRC_INACTIVE to RRC_CONNECTED may be initiated only if the UE has valid location information. The UE may send relevant information (e.g., gnss-validityDuration) to the gNB, which reduces the probability of location information expiry.

[0103] According to this operation example, the specific operation when the RedCap UE does not support simultaneous operation of the location information acquisition and the Uu interface becomes clear, and the location information using GNSS can be reliably acquired after transitioning to the RRC_INACTIVE or RRC_IDLE state. This enables the RedCap UE to reduce costs while determining an appropriate TA value even when using NTN, thereby improving communication quality.

[0104] (4) Other Embodiments Although the embodiments have been described above, it will be obvious to those skilled in the art that the present invention is not limited to the description of the embodiments, and that various modifications and improvements are possible.

[0105] For example, in the above-described embodiment, RedCap UE and eRedCap UE are described under the assumption that they have some reduced capability, but as described above, RedCap UE and eRedCap UE do not necessarily have reduced capability and may be interpreted as UE for URLLC (Ultra-Reliable and Low Latency Communications) or IoT (Internet of Things), etc., as long as they are a specific type of UE that can be distinguished from Non-RedCap UE.

[0106] Also, in the above description, configure, activate, update, indicate, enable, specify, and select may be interchangeable. Similarly, link, associate, correspond, and map may be interchangeable, and allocate, assign, monitor, and map may be interchangeable.

[0107] Furthermore, specific, dedicated, UE-specific, and UE-dedicated may be interchangeable. Similarly, common, shared, group-common, UE-common, and UE-shared may be interchangeable.

[0108] The block diagram ( FIG. 3 ) used to explain the above-described embodiment shows functional blocks. These functional blocks (components) are realized by any combination of hardware and / or software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are directly or indirectly connected (e.g., wired, wireless, etc.) and these multiple devices. The functional block may also be realized by combining software with the single device or multiple devices.

[0109] Functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission is called a transmitting unit or transmitter. As mentioned above, there are no particular limitations on how each is implemented.

[0110] Furthermore, the above-described gNB100 and UE200 (the devices) may function as a computer that performs processing of the wireless communication method of the present disclosure. Figure 9 is a diagram showing an example of the hardware configuration of the devices. As shown in Figure 9, the devices may be configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0111] In the following description, the term "apparatus" can be interpreted as a circuit, a device, a unit, etc. The hardware configuration of the apparatus may be configured to include one or more of the apparatuses shown in the drawings, or may be configured to exclude some of the apparatuses.

[0112] Each functional block of the device (see FIG. 3) is realized by any hardware element of the computer device or a combination of the hardware elements.

[0113] In addition, each function of the device is realized by loading specified software (programs) onto hardware such as processor 1001 and memory 1002, causing processor 1001 to perform calculations, control communication via communication device 1004, and control at least one of reading and writing data in memory 1002 and storage 1003.

[0114] The processor 1001 controls the entire computer by running, for example, an operating system, and may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control unit, an arithmetic unit, and registers.

[0115] The processor 1001 also reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and executes various processes in accordance with these. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. Furthermore, the various processes described above may be executed by a single processor 1001, or may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may be transmitted from a network via a telecommunications line.

[0116] The memory 1002 is a computer-readable recording medium and may be configured by at least one of, for example, a read-only memory (ROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a random access memory (RAM), etc. The memory 1002 may also be called a register, a cache, a main memory (primary storage device), etc. The memory 1002 may store a program (program code), a software module, etc., capable of executing a method according to an embodiment of the present disclosure.

[0117] Storage 1003 is a computer-readable recording medium, and may be, for example, at least one of an optical disk such as a Compact Disc ROM (CD-ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray disc), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy disk, a magnetic strip, etc. Storage 1003 may also be referred to as an auxiliary storage device. The above-mentioned recording medium may be, for example, a database, a server, or other suitable medium including at least one of memory 1002 and storage 1003.

[0118] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also called, for example, a network device, a network controller, a network card, or a communication module.

[0119] The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize, for example, at least one of Frequency Division Duplex (FDD) and Time Division Duplex (TDD).

[0120] The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that receives input from the outside. The output device 1006 is an output device (e.g., a display, a speaker, an LED lamp, etc.) that outputs to the outside. Note that the input device 1005 and the output device 1006 may be integrated into one device (e.g., a touch panel).

[0121] Furthermore, each device such as the processor 1001 and the memory 1002 is connected to a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between each device.

[0122] Furthermore, the device may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized by the hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

[0123] Furthermore, the notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., RRC signaling, Medium Access Control (MAC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB))), other signals, or a combination thereof. Furthermore, the RRC signaling may be referred to as an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.

[0124] Each aspect / embodiment described in the present disclosure may be applied to at least one of a system using Long Term Evolution (LTE), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, a 4th generation mobile communication system (4G), a 5th generation mobile communication system (5G), a 6th generation mobile communication system (6G), an xth generation mobile communication system (xG) (where x is, for example, an integer or a decimal), Future Radio Access (FRA), New Radio (NR), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), or other suitable system, and a next-generation system extended based on these. Furthermore, a combination of multiple systems (e.g., a combination of at least one of LTE and LTE-A with 5G) may also be applied.

[0125] The order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be changed unless it is consistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.

[0126] In the present disclosure, a specific operation described as being performed by a base station may also be performed by its upper node in some cases. In a network consisting of one or more network nodes having a base station, it is clear that various operations performed for communication with a terminal may be performed by at least one of the base station and another network node other than the base station (e.g., MME or S-GW, etc., but are not limited to these). Although the above example illustrates a case where there is one other network node other than the base station, a combination of multiple other network nodes (e.g., MME and S-GW) may also be used.

[0127] Information, signals (information, etc.) may be output from a higher layer (or a lower layer) to a lower layer (or a higher layer), or may be input and output via multiple network nodes.

[0128] The input and output information may be stored in a specific location (for example, a memory) or may be managed using a management table. The input and output information may be overwritten, updated, or added to. The output information may be deleted. The input information may be transmitted to another device.

[0129] The determination may be made based on a value represented by one bit (0 or 1), a Boolean value (true or false), or a numerical comparison (e.g., comparison with a predetermined value).

[0130] The aspects / embodiments described in this disclosure may be used alone, in combination, or switched depending on the implementation. Notification of predetermined information (e.g., notification that "X is true") is not limited to explicit notification, but may be implicit (e.g., not notifying the predetermined information).

[0131] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0132] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), then these wired and / or wireless technologies are included within the definition of transmission media.

[0133] The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0134] Note that terms described in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of a channel and a symbol may be a signal (signaling). Furthermore, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, a cell, a frequency carrier, etc.

[0135] As used in this disclosure, the terms "system" and "network" are used interchangeably.

[0136] Furthermore, the information, parameters, etc. described in the present disclosure may be expressed using absolute values, may be expressed using relative values ​​from a predetermined value, or may be expressed using other corresponding information. For example, a radio resource may be indicated by an index.

[0137] The names used for the above-described parameters are not intended to be limiting in any way. Furthermore, the mathematical expressions using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (e.g., PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not intended to be limiting in any way.

[0138] In this disclosure, terms such as "base station (BS)," "radio base station," "fixed station," "NodeB," "eNodeB (eNB)," "gNodeB (gNB)," "access point," "transmission point," "reception point," "transmission / reception point," "cell," "sector," "cell group," "carrier," and "component carrier" may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

[0139] A base station can accommodate one or more (e.g., three) cells (also called sectors). When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be divided into multiple smaller areas, and each smaller area can be provided with communication services by a base station subsystem (e.g., a small indoor base station (Remote Radio Head: RRH)).

[0140] The terms "cell" or "sector" refer to part or all of the coverage area of ​​a base station and / or base station subsystem that provides communication services within that coverage area.

[0141] In the present disclosure, the base station transmitting information to a terminal may be interpreted as the base station instructing the terminal to control or operate based on the information.

[0142] In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," etc. may be used interchangeably.

[0143] A mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.

[0144] At least one of the base station and the mobile station may be referred to as a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile object, the mobile object itself, etc. The mobile object may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may also include devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.

[0145] Furthermore, a base station in the present disclosure may be read as a mobile station (user terminal, the same applies hereinafter). For example, the aspects / embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a mobile station is replaced with communication between multiple mobile stations (which may be called, for example, Device-to-Device (D2D) or Vehicle-to-Everything (V2X)). In this case, the mobile station may be configured to have the functions of a base station. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, terms such as an uplink channel and a downlink channel may be read as a side channel (or sidelink).

[0146] Similarly, a mobile station in the present disclosure may be interpreted as a base station, in which case the base station may have the functions of a mobile station.

[0147] A radio frame may be composed of one or more frames in the time domain. Each of the one or more frames in the time domain may be called a subframe. A subframe may further be composed of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.

[0148] Numerology may be communication parameters that apply to the transmission and / or reception of a signal or channel, such as subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame structure, specific filtering operations performed by the transceiver in the frequency domain, and specific windowing operations performed by the transceiver in the time domain.

[0149] A slot may consist of one or more symbols in the time domain (such as an Orthogonal Frequency Division Multiplexing (OFDM) symbol, a Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol, etc.) A slot may be a numerology-based time unit.

[0150] A slot may include multiple minislots. Each minislot may consist of one or more symbols in the time domain. A minislot may also be called a subslot. A minislot may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called PDSCH (or PUSCH) mapping type B.

[0151] The radio frame, subframe, slot, minislot, and symbol all represent time units for transmitting signals, and may be referred to by other names corresponding to the radio frame, subframe, slot, minislot, and symbol.

[0152] For example, one subframe may be referred to as a transmission time interval (TTI), multiple consecutive subframes may be referred to as a TTI, or one slot or one minislot may be referred to as a TTI. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (e.g., 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc., instead of a subframe.

[0153] Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, a base station schedules each user terminal to allocate radio resources (such as frequency bandwidth and transmission power that can be used by each user terminal) in TTI units. Note that the definition of TTI is not limited to this.

[0154] The TTI may be a transmission time unit for a channel-encoded data packet (transport block), a code block, a code word, etc., or may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the time interval (e.g., the number of symbols) to which a transport block, a code block, a code word, etc. is actually mapped may be shorter than the TTI.

[0155] In addition, when one slot or one minislot is called a TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit for scheduling, and the number of slots (minislots) constituting the minimum time unit for scheduling may be controlled.

[0156] A TTI having a time length of 1 ms may be referred to as a regular TTI (TTI in LTE Rel. 8-12), normal TTI, long TTI, regular subframe, normal subframe, long subframe, slot, etc. A TTI shorter than a regular TTI may be referred to as a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.

[0157] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length shorter than the TTI length of a long TTI and equal to or greater than 1 ms.

[0158] A resource block (RB) is a resource allocation unit in the time domain and the frequency domain, and may include one or more consecutive subcarriers in the frequency domain. The number of subcarriers included in an RB may be the same regardless of numerology, for example, 12. The number of subcarriers included in an RB may be determined based on numerology.

[0159] The time domain of an RB may include one or more symbols and may have a length of one slot, one minislot, one subframe, or one TTI, each of which may consist of one or more resource blocks.

[0160] Note that one or more RBs may also be called a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, etc.

[0161] Furthermore, a resource block may be composed of one or more resource elements (REs). For example, one RE may be a radio resource region of one subcarrier and one symbol.

[0162] A Bandwidth Part (BWP) (which may also be referred to as a fractional bandwidth) may represent a subset of contiguous common resource blocks (RBs) for a given numerology on a given carrier, where the common RBs may be identified by their index relative to a common reference point of the carrier. PRBs may be defined in a given BWP and numbered within that BWP.

[0163] The BWP may include a BWP for UL (UL BWP) and a BWP for DL ​​(DL BWP). One or more BWPs may be configured for a UE within one carrier.

[0164] At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given signal / channel outside the active BWP. Note that the terms "cell," "carrier," etc. in this disclosure may be read as "BWP."

[0165] The above-described structures of the radio frame, subframe, slot, minislot, and symbol are merely examples. For example, the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, and other configurations may be changed in various ways.

[0166] The terms "connected," "coupled," or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access." As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using one or more wires, cables, and / or printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples.

[0167] The reference signal may also be abbreviated as Reference Signal (RS) and may be called a pilot depending on the applicable standard.

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

[0169] The "means" in the configuration of each of the above devices may be replaced with "part," "circuit," "device," etc.

[0170] As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed therein or that the first element must precede the second element in some way.

[0171] When the terms "include," "including," and variations thereof are used in this disclosure, these terms are intended to be inclusive, similar to the term "comprising." Furthermore, when the term "or" is used in this disclosure, it is not intended to be an exclusive or.

[0172] In this disclosure, where articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.

[0173] As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of actions. "Determining" and "determining" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiring (e.g., searching in a table, database, or other data structure), ascertaining, and the like. "Determining" and "determining" may also include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), and the like. Furthermore, "judgment" and "decision" can include regarding resolving, selecting, choosing, establishing, comparing, etc. as having been "judged" or "decided." In other words, "judgment" and "decision" can include regarding some action as having been "judged" or "decided." Furthermore, "judgment (decision)" can be interpreted as "assuming," "expecting," "considering," etc.

[0174] In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "coupled" may also be interpreted in the same way as "different."

[0175] 10 shows an example of the configuration of a vehicle 2001. As shown in Fig. 10, the vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, left and right front wheels 2007, left and right rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021 to 2029, an information service unit 2012, and a communication module 2013.

[0176] The drive unit 2002 is composed of, for example, an engine, a motor, or a hybrid of an engine and a motor. The steering unit 2003 includes at least a steering wheel (also called a handle) and is configured to steer at least one of the front wheels and the rear wheels based on the operation of the steering wheel operated by the user. The electronic control unit 2010 is composed of a microprocessor 2031, memory (ROM, RAM) 2032, and a communication port (IO port) 2033. Signals from various sensors 2021 to 2027 provided in the vehicle are input to the electronic control unit 2010. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).

[0177] The signals from the various sensors 2021 to 2028 include a current signal from a current sensor 2021 that senses the current of the motor, a rotation speed signal of the front and rear wheels obtained by a rotation speed sensor 2022, an air pressure signal of the front and rear wheels obtained by an air pressure sensor 2023, a vehicle speed signal obtained by a vehicle speed sensor 2024, an acceleration signal obtained by an acceleration sensor 2025, an accelerator pedal depression amount signal obtained by an accelerator pedal sensor 2029, a brake pedal depression amount signal obtained by a brake pedal sensor 2026, a shift lever operation signal obtained by a shift lever sensor 2027, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. obtained by an object detection sensor 2028.

[0178] The information service unit 2012 is composed of various devices, such as a car navigation system, an audio system, speakers, a television, and a radio, for providing (outputting) various types of information, such as driving information, traffic information, and entertainment information, and one or more ECUs for controlling these devices. The information service unit 2012 uses information acquired from external devices via the communication module 2013, etc., to provide various types of multimedia information and multimedia services to the occupants of the vehicle 1.

[0179] The information service unit 2012 may include input devices (e.g., keyboards, mice, microphones, switches, buttons, sensors, touch panels, etc.) that accept input from the outside, and may also include output devices (e.g., displays, speakers, LED lamps, touch panels, etc.) that output to the outside.

[0180] The driving assistance system unit 2030 is composed of various devices that provide functions for preventing accidents and reducing the driver's driving burden, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS, etc.), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps, etc.), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System), etc.), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. The driving assistance system unit 2030 also transmits and receives various information via the communication module 2013 to realize driving assistance functions or autonomous driving functions.

[0181] The communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 1 via the communication port. For example, the communication module 2013 transmits and receives data via the communication port 2033 to and from a driving unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, left and right front wheels 2007, left and right rear wheels 2008, an axle 2009, a microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021 to 2028, which are provided in the vehicle 2001.

[0182] The communication module 2013 is a communication device that can be controlled by the microprocessor 2031 of the electronic control unit 2010 and can communicate with an external device. For example, it transmits and receives various information to and from the external device via wireless communication. The communication module 2013 may be located either inside or outside the electronic control unit 2010. The external device may be, for example, a base station, a mobile station, or the like.

[0183] The communication module 2013 may transmit at least one of signals from the above-mentioned various sensors 2021 to 2028 input to the electronic control unit 2010, information obtained based on the signals, and information based on input from the outside (user) obtained via the information service unit 2012 to an external device via wireless communication. The electronic control unit 2010, the various sensors 2021 to 2028, the information service unit 2012, etc. may be referred to as input units that accept input. For example, the PUSCH transmitted by the communication module 2013 may include information based on the above-mentioned input.

[0184] The communication module 2013 receives various information (traffic information, traffic signal information, vehicle-to-vehicle information, etc.) transmitted from external devices and displays it on an information service unit 2012 provided in the vehicle. The information service unit 2012 may also be called an output unit that outputs information (for example, outputs information to a device such as a display or speaker based on the PDSCH (or data / information decoded from the PDSCH) received by the communication module 2013). The communication module 2013 also stores the various information received from external devices in a memory 2032 that can be used by the microprocessor 2031. Based on the information stored in the memory 2032, the microprocessor 2031 may control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, left and right front wheels 2007, left and right rear wheels 2008, axles 2009, sensors 2021 to 2028, and the like provided in the vehicle 2001.

[0185] Although the present disclosure has been described in detail above, it is clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the present disclosure.

[0186] (Additional Note) The above disclosure may be expressed as follows: A first feature is a terminal including: a controller that sets a timing adjustment value for uplink transmission based on location information indicating a terminal location; and a communication unit that transmits the uplink at a set timing, wherein the controller transitions from a connected state to an inactive state in a radio resource control layer and acquires the location information.

[0187] A second feature is that the terminal includes a control unit that sets a timing adjustment value for uplink transmission based on location information indicating the terminal location, and a communication unit that transmits the uplink at the set timing, and the control unit transitions from a connected state or an inactive state in a radio resource control layer to an idle state and acquires the location information.

[0188] A third feature is that, in the first or second feature, the control unit determines, based on an instruction from a network, whether or not simultaneous operation of acquiring the location information and performing the uplink transmission or downlink reception by the communication unit is required.

[0189] A fourth feature is the third feature, wherein the control unit assumes that connection to the network via a non-terrestrial network is prohibited when the terminal does not support the simultaneous operation.

[0190] In a fifth feature based on the third feature, the control unit transmits capability information indicating whether the simultaneous operation is supported to the network.

[0191] 10 Wireless communication system 20 NG-RAN 100 gNB 100X NTN Gateway 150 Satellite 170 GNSS 200 UE 210 Wireless signal transceiver 220 Amplifier 230 Modulation / demodulation unit 240 Control signal / reference signal processing unit 250 Encoding / decoding unit 260 Data transceiver 270 Control unit 1001 Processor 1002 Memory 1003 Storage 1004 Communication device 1005 Input device 1006 Output device 1007 Bus 2001 Vehicle 2002 Drive unit 2003 Steering unit 2004 Accelerator pedal 2005 Brake pedal 2006 Shift lever 2007 Left and right front wheels 2008 Left and right rear wheels 2009 Axle 2010 Electronic control unit 2012 Information service unit 2013 Communication module 2021 Current sensor 2022 RPM sensor 2023 Air pressure sensor 2024 Vehicle speed sensor 2025 Acceleration sensor 2026 Brake pedal sensor 2027 Shift lever sensor 2028 Object detection sensor 2029 Accelerator pedal sensor 2030 Driving assistance system section 2031 Microprocessor 2032 Memory (ROM, RAM) 2033 Communication port

Claims

1. A terminal comprising: a control unit that sets a timing adjustment value for uplink transmission based on location information indicating the terminal location; and a communication unit that transmits the uplink at the set timing, wherein the control unit transitions from a connected state to an inactive state in a radio resource control layer and acquires the location information.

2. A terminal comprising: a control unit that sets a timing adjustment value for uplink transmission based on location information indicating the terminal location; and a communication unit that transmits the uplink at the set timing, wherein the control unit transitions from a connected state or an inactive state in a radio resource control layer to an idle state and acquires the location information.

3. A terminal as described in claim 1 or 2, wherein the control unit determines, based on an instruction from a network, whether or not it is necessary to simultaneously acquire the location information and perform the uplink transmission or downlink reception by the communication unit.

4. The terminal of claim 3, wherein the control unit assumes that connection to the network via the non-terrestrial network is prohibited if it receives an indication from the network via a non-terrestrial network that the simultaneous operation is required and if the terminal does not support the simultaneous operation.

5. The terminal according to claim 3, wherein the control unit transmits capability information indicating whether the simultaneous operations are supported or not to the network.

6. A wireless communication method in a terminal, comprising: a step of setting a timing adjustment value for uplink transmission based on location information indicating the terminal location; a step of transmitting the uplink at the set timing; and a step of transitioning from a connected state to an inactive state in a radio resource control layer and acquiring the location information.

Images