Terminal and wireless communication method
By applying common or independent physical channel settings in RedCap UE, the performance differences and configuration complexity of RedCap UE in non-terrestrial networks are resolved, achieving efficient wireless communication optimization.
Patent Information
- Application Number
- CN202380100664.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-07-25
- Publication Date
- 2026-02-17
AI Technical Summary
When using non-terrestrial networks, RedCap UEs suffer from performance limitations due to antenna gain and transmit power constraints, resulting in inferior performance compared to handheld UEs such as smartphones. Furthermore, independent configuration can lead to increased complexity and overhead.
A terminal is provided, comprising a control unit and a communication unit, capable of applying common or independent physical channel settings of conventional terminals and RedCap UEs in non-terrestrial networks, and optimizing wireless communication by receiving broadcast information to make appropriate settings and ignore unnecessary settings.
It enables efficient execution of appropriate settings for both regular UEs and RedCap UEs in non-terrestrial networks, reducing setup overhead and optimizing the performance of each UE.
Smart Images

Figure CN121549060A_ABST
Abstract
Description
Technical Field
[0001] This disclosure relates to terminals with reduced capabilities and wireless communication methods. Background Technology
[0002] The 3rd Generation Partnership Project (3GPP: registered trademark) standardized the fifth-generation mobile communication system (also known as 5G, New Radio (NR), or Next Generation (NG)) and also standardized the next generation, known as Beyond 5G, 5G Evolution, or 6G.
[0003] 3GPP Release-17 specifies support for User Equipment (UE) with reduced capabilities. Such UEs are also known as RedCap UEs (reduced UE capability), and are appropriately used for industrial wireless sensors (factory sensors), video surveillance, and wearable devices. For RedCap UEs, the number of receiving antennas (also called RX branches) that can be installed is limited.
[0004] Furthermore, in 3GPP Release-18, the introduction of a new RedCap UE (also known as eRedCap UE) that can further limit bandwidth and peak data rate was studied (Non-Patent Document 1).
[0005] Existing technical documents
[0006] Non-patent literature
[0007] Non-patent document 1, “Revised WID on Enhanced support of reduced capability NRdevices”, RP-223544, 3GPP TSG RAN Meeting #98-e, 3GPP, December 2022. Summary of the Invention
[0008] RedCap UEs (including eRedCap UEs) have limitations in capabilities, such as antenna gain and transmit power, which put them at a performance disadvantage compared to typical handheld UEs such as smartphones.
[0009] In particular, when using a non-terrestrial network (NTN), timing advance (TA), which includes adjusting the uplink (UL) transmission timing, may require a separate setting for RedCap UEs that takes into account such performance differences. On the other hand, if a setting is specified separately from that of a normal UE, the setup becomes complex, raising concerns about increased overhead associated with the setting.
[0010] Therefore, the following disclosure is made in view of the situation and its purpose is to provide a terminal and wireless communication method that can efficiently perform appropriate settings corresponding to a typical UE or RedCap UE even when using a non-terrestrial network.
[0011] One aspect of this disclosure is a terminal (UE200) comprising: a control unit (control unit 270) that sets a physical channel common to both a normal terminal and a capability-reduced terminal, wherein the capability of the capability-reduced terminal is reduced compared to the normal terminal; and a communication unit (wireless signal transceiver unit 210) that uses the physical channel to perform wireless communication via a non-terrestrial network.
[0012] One aspect of this disclosure is a terminal (UE200) comprising: a control unit (control unit 270) that sets a physical channel independently of the normal terminal for a capability-reduced terminal whose capabilities are reduced compared to the normal terminal; and a communication unit (wireless transceiver unit 210) that uses the physical channel to perform wireless communication via a non-terrestrial network.
[0013] One aspect of this disclosure is a terminal (UE200) comprising: a receiver (control signal) The reference signal processing unit (240) receives broadcast information indicating that the capability-reduced terminal, whose capability is reduced compared to a normal terminal, applies settings independent of the normal terminal; and the control unit (control unit 270) executes settings applied via a non-terrestrial network based on the broadcast information.
[0014] One aspect of the present invention is a terminal (UE200) comprising: a receiving unit (control signal) The reference signal processing unit (240) receives broadcast information that applies settings common to both the normal terminal and the capability-reduced terminal, wherein the capability of the capability-reduced terminal is reduced compared to the normal terminal; and the control unit (control unit 270) executes settings for the capability-reduced terminal while ignoring at least a portion of the settings when the network is not terrestrial. Attached Figure Description
[0015] Figure 1 This is a schematic diagram of the overall structure of the wireless communication system 10.
[0016] Figure 2 This is a diagram illustrating an example of the structure of wireless frames, subframes, and time slots used in the wireless communication system 10.
[0017] Figure 3 This is the function block structure diagram of gNB100 and UE200.
[0018] Figure 4 This is a diagram showing an example of the formula for calculating the TA value via NTN.
[0019] Figure 5 This is a diagram illustrating the timing example between UE and gNB in action example 1.
[0020] Figure 6 This is a diagram showing the timing example (one of) between UE and gNB in action example 2.
[0021] Figure 7 This is a diagram showing the timing example (second one) between UE and gNB in action example 2.
[0022] Figure 8 This is a diagram illustrating an example of the hardware structure of gNB100 and UE200.
[0023] Figure 9 This is a diagram showing a structural example of vehicle 2001. Detailed Implementation
[0024] The embodiments are described below with reference to the accompanying drawings. Furthermore, the same or similar reference numerals are used to denote the same function and structure, and their descriptions are omitted where appropriate.
[0025] (1) Overall general structure of wireless communication system
[0026] Figure 1 This is a schematic diagram of the overall structure of the wireless communication system 10 in this embodiment. The wireless communication system 10 is a wireless communication system that follows 5G New Radio (NR) and includes a Next Generation-Radio Access Network (NG-RAN20) 20 and a terminal 200 (UE (User Equipment) 200).
[0027] Alternatively, the wireless communication system 10 can also be a wireless communication system that follows the methods referred to as Beyond 5G, 5G Evolution, or 6G.
[0028] NG-RAN20 includes a radio base station 100 (hereinafter, gNB100). Furthermore, the specific structure of the wireless communication system 10, including the number of gNB100 and UE200, is not limited to... Figure 1 The example shown.
[0029] NG-RAN20 actually includes multiple NG-RAN nodes, specifically multiple gNBs (or ng-eNBs), and is connected to a 5G-compliant core network (e.g., 5GC). Additionally, NG-RAN20 and the core network can be simply referred to as "network".
[0030] The gNB100 is a 5G-compliant wireless base station that performs 5G-compliant wireless communication with the UE200. The gNB100 and UE200 can support Massive MIMO (Multiple-Input Multiple-Output) which generates more directional beams BM by controlling the wireless signals transmitted from multiple antenna elements, Carrier Aggregation (CA) which uses multiple component carriers (CC), and Dual Connectivity (DC) which allows simultaneous communication between the UE and two NG-RAN nodes.
[0031] In this implementation, the wireless communication system 10 may include a non-terrestrial network (NTN). In the NTN, services are provided in areas that cannot be covered by a terrestrial network (TN) due to cost or other reasons, by utilizing satellites such as satellite 150 (hereinafter referred to as satellite 150). The NTN enables the provision of more reliable services. For example, NTN is envisioned for application in IoT (Internet of Things), ships, buses, trains, and critical communications. Furthermore, the NTN offers scalability based on efficient multicast or broadcast.
[0032] Additionally, a network that includes gNB100 and UE200 but not satellite 150 can be referred to as TN, in contrast to NTN. Furthermore, satellite 150 can function as a gNB (radio base station). The type of satellite 150 is not particularly limited; for example, it can be a geostationary orbit satellite (GEO) or a low Earth orbit satellite (LEO). Alternatively, high-altitude platform stations (HAPS) can also be used.
[0033] In this embodiment, gNB100 may have an NTN gateway 100X. The NTN gateway 100X sends downlink signals to satellite 150. The NTN gateway 100X receives uplink signals from satellite 150.
[0034] Satellite 150 relays downlink signals received from NTN gateway 100X to UE200. Satellite 150 also relays uplink signals received from UE200 to NTN gateway 100X. Satellite 150 can be interpreted as a TRP (Transmission-Reception Point), a repeater, or a relay station.
[0035] To achieve coverage enhancement (CE), the UE200 can support repeated transmissions of uplink channels such as PUCCH (Physical Uplink Control Channel) and PDSCH (Physical Downlink Shared Channel). As a coverage enhancement mode, it can correspond to CE Mode A and CE Mode B (refer to 3GPP TS38.213, etc.). CE Mode refers to a technique that effectively extends the cell's coverage by periodically reducing the threshold of the Reference Signal Received Power (RSRP) / RSRQ (Reference Signal Received Quality). It also specifies the number of attempts for the corresponding random access procedure (RA).
[0036] Additionally, regarding coverage enhancement, multi-slot PUSCH transport block processing (TBoMS) can also be applied, which processes transport blocks (TBs) via PUSCH allocated to multiple time slots.
[0037] There is no particular limitation on the type of UE200, but in this embodiment, the capabilities of UE200 can be reduced. There is no particular limitation on the reduced capabilities; for example, capabilities (actions) related to measurements used for Radio Resource Management (RRM) can be reduced (or restricted, mitigated, etc.).
[0038] Such UEs can also be called RedCap UEs (reduced UE capability). RedCap UEs can be interpreted, for example, as a category of UEs used for industrial wireless sensors, video surveillance, and wearable devices.
[0039] Alternatively, RedCap UE may not necessarily refer to a reduced capability; it could also be interpreted as a UE geared towards IoT (Internet of Things). RedCap UE can also be referred to as a specific type of UE.
[0040] On the other hand, a non-RedCap UE can also be interpreted as a normal UE (normal terminal) with normal capabilities, or a UE oriented towards eMBB (enhanced Mobile Broadband) or URLLC (Ultra-Reliable and Low Latency Communications). Furthermore, normal UEs may include UEs oriented towards eMBB or URLLC.
[0041] Regarding RedCap UEs, 3GPP Release-17 specifies that the number of installed receive antennas (also known as RX branches) can vary. Specifically, there can 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 is not necessarily limited to 1 RX branch or 2 RX branches.
[0042] Furthermore, the functionality (capabilities) of a RedCap UE can be further reduced. Specifically, compared to a RedCap UE, bandwidth and peak data rate are further limited. Such a RedCap UE can be specified in 3GPP Release-18, and to distinguish it from the RedCap UE of Release-17, it can also be called an eRedCap UE (enhanced reduced UE capability). Additionally, unless otherwise specified, a UE labeled as RedCap UE can be interpreted as including an eRedCap UE.
[0043] For example, in the case of an eRedCap UE, the baseband (BB) bandwidth used for transmission and reception on a specific channel can be limited to 5MHz or 10MHz (typically 20MHz), or the peak data rate can be further reduced by changing specific parameters. Additionally, the subcarrier spacing (SCS) can be applied at 15kHz or 30kHz.
[0044] In addition, UE200 may include UEs targeting NB-IoT (Narrow Band Internet of Things) and eMTC (enhanced Machine Type Communication). In such UE200 (including RedCap UE), multi-TB scheduling that performs scaling by treating multiple transport blocks (TBs) as objects can be applied.
[0045] Figure 2 An example of the structure of wireless frames, subframes, and time slots used in wireless communication system 10 is shown.
[0046] like Figure 2 As shown, one time slot consists of 14 symbols. The larger (wider) the SCS, the shorter the symbol period (and time slot period). SCS is not limited to... Figure 2 The intervals (frequency) shown. For example, 480kHz, 960kHz, etc. can also be used.
[0047] Furthermore, the number of symbols constituting one time slot does not necessarily have to be 14 symbols (e.g., 28 symbols, 56 symbols). In addition, the number of time slots in each subframe can vary depending on the SCS.
[0048] in addition, Figure 2 The time direction (t) shown can also be referred to as the time domain, symbol period, or symbol time, etc. Furthermore, the frequency direction can also be referred to as the frequency domain, resource block, subcarrier, or bandwidth part (BWP), etc.
[0049] (2) Functional block structure of wireless communication system
[0050] Next, the functional block structure of the wireless communication system 10 will be described. Specifically, the functional block structures of gNB100 and UE200 will be described.
[0051] Figure 3 This is the function block structure diagram of gNB100 and UE200. The following is a description of UE200. Figure 3 As shown, the UE200 includes a wireless signal transceiver unit 210, an amplifier unit 220, a modem unit 230, and a control signal transceiver unit 20. Reference signal processing unit 240, encoding / decoding unit 250, data transceiver unit 260 and control unit 270.
[0052] The radio transceiver unit 210 transmits and receives radio signals that comply with NR. The radio transceiver unit 210 supports massive MIMO, CA that uses multiple CCs together, and DC that allows simultaneous communication between the UE and two NG-RAN nodes.
[0053] Furthermore, the wireless transceiver unit 210 uses a physical channel to perform wireless communication via a non-terrestrial network (NTN). In this embodiment, the wireless transceiver unit 210 can be configured as a communication unit.
[0054] A physical channel can contain both uplink (UL) and downlink (DL) channels. Specifically, it can contain PUCCH and PDSCH. PUCCH can be interpreted as the control channel in the UL direction (uplink control channel). PDSCH can be interpreted as the data channel in the DL direction (downlink data channel).
[0055] In addition to PUCCH and PDSCH, this physical channel may also include PRACH (Physical Random Access Channel) and PDCCH (Physical Downlink Control Channel). Furthermore, PUSCH (Physical Uplink Shared Channel) may or may not be included in this physical channel.
[0056] The amplification unit 220 is composed of a power amplifier (PA) and a low-noise amplifier (LNA). The amplification unit 220 amplifies the signal output from the modem 230 to a predetermined power level. Furthermore, the amplification unit 220 amplifies the RF signal output from the wireless transceiver unit 210.
[0057] The modem 230 performs data modulation / demodulation, transmit power setting, and resource block allocation for each predetermined communication destination (gNB100, etc.). Cyclic prefix-orthogonal frequency division multiplexing (CP-OFDM) / discrete Fourier transform-spread (DFT-S-OFDM) can also be applied in the modem 230. Furthermore, DFT-S-OFDM can be used not only for the uplink (UL) but also for the downlink (DL).
[0058] control signals The reference signal processing unit 240 performs processing related to various control signals transmitted and received by the UE200, as well as processing related to various reference signals transmitted and received by the UE200.
[0059] Specifically, control signals The reference signal processing unit 240 receives various control signals transmitted from the gNB 100 via a predetermined control channel, such as control signals from the Radio Resource Control (RRC) layer. Furthermore, the control signals... The reference signal processing unit 240 sends various control signals to the gNB100 via a predetermined control channel.
[0060] control signals The reference signal processing unit 240 performs processing using reference signals (RS) such as demodulation reference signal (DMRS) and phase tracking reference signal (PTRS).
[0061] DMRS is a terminal-specific reference signal (pilot signal) used to estimate fading channels used in data demodulation, and is known between the base station and the terminal. PTRS is a terminal-specific reference signal used to estimate phase noise, which is a problem in the high-frequency band.
[0062] In addition to DMRS and PTRS, the reference signal may also include Channel State Information-Reference Signal (CSI-RS), Sounding Reference Signal (SRS), and Positioning Reference Signal (PRS) for location information.
[0063] In addition, channels include control channels and data channels. Control channels may include PDCCH (Physical Downlink Control Channel), PUCCH (Physical Uplink Control Channel), RACH (Random Access Channel, a DCI containing a Random Access Radio Network Temporary Identifier (RA-RNTI)), and PBCH (Physical Broadcast Channel), etc.
[0064] In addition, data channels include PDSCH (Physical Downlink Shared Channel) and PUSCH (Physical Uplink Shared Channel). Data can refer to data transmitted via a data channel.
[0065] In this embodiment, the control signal The reference signal processing unit 240 can receive broadcast information that applies settings independent of the Normal UE to a RedCap UE (reduced capability UE), whose capabilities are reduced compared to a Normal UE (normal terminal). In this embodiment, the control signal The reference signal processing unit 240 can be configured as a receiving unit.
[0066] In addition, control signals The reference signal processing unit 240 can also receive broadcast information that applies to both Normal UE and RedCap UE, whose capabilities are reduced compared to Normal UE.
[0067] The broadcast information here typically corresponds to system information (SIB) broadcast from the network, specifically NTN-specific SIBs. However, it is not limited to such SIBs; it can be MIBs (Master Information Blocks) or lower-level control information, such as DCI.
[0068] The encoding / decoding unit 250 performs data segmentation / linking and channel encoding / decoding, etc., for each predetermined communication destination (gNB100 or other gNB).
[0069] Specifically, the encoding / decoding unit 250 divides the data output from the data transceiver unit 260 into predetermined sizes and performs channel coding on the divided data. Furthermore, the encoding / decoding unit 250 decodes the data output from the modem unit 230 and concatenates the decoded data.
[0070] The data transceiver unit 260 performs the transmission and reception of Protocol Data Units (PDUs) and Service Data Units (SDUs). Specifically, the data transceiver unit 260 performs the assembly / disassembly of PDUs / SDUs in multiple layers (Media Access Control (MAC), Radio Link Control (RLC), and Packet Data Convergence Protocol (PDCP), etc.). In addition, the data transceiver unit 260 performs error correction and retransmission control based on Hybrid Automatic Repeat Request (ARQ).
[0071] The control unit 270 controls the functional blocks that constitute the UE 200. In particular, in this embodiment, the control unit 270 is capable of executing settings related to the RedCap UE when using NTN.
[0072] Specifically, the control unit 270 can configure physical channels that apply settings common to both Normal UEs (normal terminals) and RedCap UEs with reduced capabilities than Normal UEs. Specifically, the control unit 270 can configure PUCCH and / or PDSCH that apply settings common to both Normal UEs and RedCap UEs.
[0073] Here, "common settings" can refer to setting the same parameter for both Normal UE and RedCap UE. For example, this parameter could be the number of repetitions for the physical channel, as will be discussed later.
[0074] Alternatively, the control unit 270 may configure a physical channel with settings independent of the Normal UE for RedCap UEs whose capabilities are reduced compared to the Normal UE. The physical channel and parameters being applied may be the same as those used in common settings, or some may be different.
[0075] The control unit 270 can set at least one of PUCCH or PDSCH, for example, to apply independent settings regarding the number of retransmissions for Normal UE and RedCap UE. In this case, the settings of the channel when UE200 is a Normal UE can certainly be different from the settings of the channel when UE200 is a RedCap UE. However, it is not excluded that the settings of both are the same.
[0076] Furthermore, the control unit 270 can be based on the control signal The settings applied in the case of non-terrestrial network (NTN) are executed based on the broadcast information (SIB) received by the reference signal processing unit 240. Specifically, the control unit 270 controls the signal... When the reference signal processing unit 240 receives an NTN-specific SIB (Signal Block Instruction) that specifies settings for RedCap UE that are independent of those for Normal UE, it can execute settings applied in wireless communication via NTN based on the settings contained in the SIB.
[0077] Alternatively, the control unit 270 can also control the signal via the NTN. When the reference signal processing unit 240 receives an NTN-specific SIB containing settings common to both the RedCap UE and the Normal UE, it ignores at least a portion of the settings contained in the SIB and executes settings for the RedCap UE. Furthermore, the control unit 270's ignoring of at least a portion of the settings contained in the SIB can be limited to the NTN case; in the TN case, settings applied in wireless communication via the TN can be executed based on the settings content of the SIB.
[0078] (3) Operation of wireless communication system
[0079] Next, the operation of the wireless communication system 10 will be explained. Specifically, the operation related to the execution of wireless communication via NTN will be explained when the UE200 is a Normal UE or a RedCap UE.
[0080] (3.1) Background and topic
[0081] 3GPP considers the following items as subjects of its research regarding RedCap UE (which may also include eRedCap UE).
[0082] • Reduction of maximum bandwidth
[0083] • Reduction of the minimum number of receive antennas (RX branch) / DL MIMO layers
[0084] Maximum modulation mode
[0085] Half-duplexing of Frequency Division Duplex (FDD)
[0086] • Relaxed processing time regulations
[0087] • Relaxed RRM requirements for UEs located in the center of the cell
[0088] In addition, 3GPP will focus its research on the following NTN-specific features that may affect RedCap UE.
[0089] Common DL / UL performance for Normal UE and RedCap UE
[0090] • NTN's unique Timing Advance (TA) adjustment
[0091] Simultaneous operation of the GNSS (Global Navigation Satellite System) and Uu (UE-gNB) interfaces
[0092] Public TA parameters
[0093] UL repeatedly sends TA updates en route.
[0094] ·2-step RACH
[0095] Regarding this research, concerning the channels (common channels) commonly set for Normal UEs and RedCap UEs and the parameters related to TA adjustment, the following issues are envisioned.
[0096] (i) Common Channel
[0097] Compared to Normal UEs (handheld UEs such as smartphones), RedCap UEs are more likely to have performance disadvantages in areas such as antenna gain and transmit power. To support RedCap UEs in NTNs, channel repletion in DL / UL is essential. Furthermore, due to these performance differences, the required settings for Normal UEs and RedCap UEs may differ.
[0098] (ii) Adjust relevant common parameters for TA.
[0099] Figure 4 An example of the formula for calculating the TA value via NTN is shown. Figure 4As shown, in the case of via NTN, the UE-inherent TA(N) is used to compensate for the delay of the serving link (UE-to-satellite). TA,UE-specific ), and specifically the network-controlled common TA (N) between the Reference Point (RP) and satellites on the feeder link side. TA,common N TA,UE-specific The current location (location information) of the UE can be used to calculate this.
[0100] When using NTN, regarding TA adjustments, the ntn-Config of the NTN-specific SIB (SIB19) can include the following parameters.
[0101] • Satellite orbital information (Satellite ephemeris)
[0102] ·Common TA parameter
[0103] ·ta-Common-r17 (Common TA value based on network control)
[0104] ·ta-CommonDrift-r17 (Drift rate of Common TA)
[0105] •ta-CommonDriftVariant-r17 (Drift variation of Common TA)
[0106] Validity period
[0107] • Validation of TA reports
[0108] The following parameters can be set in the NTN-specific SIB.
[0109] • distanceThresh-r17 (distance from the reference location of the serving cell)
[0110] ·ntn-NeighCellConfigList-r17 (NTN Neighbor Cell List)
[0111] ·ntn-NeighCellConfigListExt-v1720 (NTN Neighbor Cell List)
[0112] In the case of RedCap UEs, the operation of the UE related to the aforementioned parameters can become complex. Below are examples of operations that can resolve the aforementioned issues related to common parameters concerning common channels and TA adjustment. Additionally, the parameters included in the aforementioned NTN-specific SIB can be applied using the following examples of operations.
[0113] (3.2) Action Summary
[0114] When the RedCap UE performs wireless communication with the gNB100 via the NTN, the channel settings common to the Normal UE can also be applied. In addition, when the RedCap UE performs wireless communication with the gNB100 via the NTN, the inherent SIB parameters (NTN-specific SIB: the SIB inherent to the NTN) can be set when communicating via the NTN.
[0115] For channels shared by Normal UE and RedCap UE (which can also be interpreted as channels applying common settings), either separate configurations or joint configurations (common settings) from both Normal UE and RedCap UE can be applied. Based on this method of configuring channels shared by Normal UE and RedCap UE, the configuration format of these common channels can be clearly defined.
[0116] (3.3) Example 1 of the action
[0117] In this example, regarding the common channel, either the separate configuration in the Normal UE and the RedCap UE, or the joint configuration in the Normal UE and the RedCap UE, can be applied. Furthermore, the common channel refers to a specific physical channel, typically including PUCCH and PDSCH. Additionally, as mentioned above, besides PUCCH and PDSCH, PRACH, PDCCH, and PUSCH can also be considered. However, PUSCH may not be considered.
[0118] Figure 5 The timing example between the UE and gNB in Action Example 1 is shown. Specifically, regarding the repetition of PUCCH, any of the following settings can be applied.
[0119] •(i): Joint settings in Normal UE and RedCap UE
[0120] •(ii): Independent settings in Normal UE and RedCap UE
[0121] In this case, the range of values for the number of repeated transmissions can also differ between Normal UE and RedCap UE. For example, in the case of Normal UE, it can be set to any one of 1 / 2 / 4 / 8, while in the case of RedCap UE, it can be set to any one of 1 / 2 / 4 / 8 / 12 / 16, etc.
[0122] The repetition of PUCCH can include the following parameters.
[0123] • Repetition factor (number of repetitions)
[0124] • After sending a PUCCH with HARQ-ACK (hybrid automatic repeat request-acknowledgement) corresponding to a PDSCH scheduled by a DCI that has been scrambled with CRC (Cyclic Redundancy Checksum) via TC-RNTI (Temporary C-RNTI), whether to apply Repetition to the PUCCH before providing dedicated PUCCH settings (Alternatively, PUCCH sending with HARQ-ACK corresponding to a PDSCH scheduled by a DCI that has been scrambled with TC-RNTI can also apply Repetition without depending on this parameter).
[0125] • The RSRP threshold that determines whether to send repetition-related information (e.g., UE capabilities) via Msg3 PUSCH (or PRACH) during the random access procedure.
[0126] In addition, any of the following settings can be applied to PDSCH.
[0127] (iii) Joint settings in Normal UE and RedCap UE
[0128] (iv) Independent settings in Normal UE and RedCap UE
[0129] In this case, the range of values for the number of repeated transmissions can also differ between Normal UE and RedCap UE, just like with PUCCH. For example, in the case of Normal UE, it can be set to any one of 1 / 2 / 4 / 8, while in the case of RedCap UE, it can be set to any one of 1 / 2 / 4 / 8 / 12 / 16, etc.
[0130] The following parameters can be included in PDSCH.
[0131] • DL aggregation or repetition
[0132] • DMRS (Joint Channel Estimation)
[0133] · PDSCH's TBoMS
[0134] Furthermore, the parameters related to PUCCH repetition and PDSCH mentioned above can also be determined by the network and instructed to the UE. For example, in the case of applying the independent settings for RedCap UEs, the RedCap UE can use the parameters specified by those independent settings.
[0135] Without applying the independent settings for RedCap UE, RedCap UE (and Normal UE) can use parameters set for Normal UE. Furthermore, these parameters (independent or combined settings) can be included in the NTN-specific SIB.
[0136] According to this example, since the independent settings of the common channel can be applied, the performance of Normal UEs and RedCap UEs can be optimized independently. On the other hand, since the joint settings of the common channel can also be applied, the settings are common, which can optimize the performance of each UE while reducing the overhead of setting all types of UEs.
[0137] (3.4) Example 2 of the action
[0138] In this action example, any of the following settings can be applied to the NTN-specific SIB.
[0139] • (i) Separate configuration in Normal UE and RedCap UE
[0140] (ii): When the NTN-specific SIB represents the joint configuration of the Normal UE and the RedCap UE, the RedCap UE ignores at least a portion of the configuration based on the NTN-specific SIB.
[0141] Figure 6The timing example between the UE and gNB in Action Example 2 is shown (one of them). Specifically, when the settings are set independently in the Normal UE and RedCap UE, the following parameters can be included in the NTN-specific SIB (the SIB inherent to NTN).
[0142] Parameters related to TA adjustment
[0143] • Satellite orbital information (Satellite ephemeris), Common TA parameters (ta-Common / ta-CommonDrift / ta-CommonDriftVariant), and validity period.
[0144] • Validation of TA reports
[0145] • Parameters related to measurement
[0146] • distanceThresh (distance from the base location of the serving cell)
[0147] • NTN Neighbor Cell List (ntn-NeighCellConfigList, ntn-NeighCellConfigListExt)
[0148] In cases where settings are independent for Normal UEs and RedCap UEs, for example, within the same SIB, independent settings (SIB) or independent parameters (NTN-Config-RedCap, etc.) can be included. Specifically, ntn-NeighCellConfigList can contain NTN-Config of neighboring cells, and ntn-NeighCellConfigRedCapList (which may be a provisional name) can contain NTN-Config-RedCap of neighboring cells (settings specific to RedCap UEs).
[0149] Additionally, parameters defined for Normal UEs may include those not defined for RedCap UEs (e.g., ta-CommonDriftVariant, TA report validity). Furthermore, the range of values for this parameter may differ between Normal and RedCap UEs. For example, a smaller value may be used or set compared to the set validity period (because ta-CommonDriftVariant cannot be used).
[0150] Figure 7The following is a timing example (second example) between the UE and gNB in Action Example 2. Specifically, when the NTN-specific SIB indicates a joint configuration of the Normal UE and the RedCap UE, common parameters can be set between the Normal UE and the RedCap UE, and the RedCap UE can ignore some of these parameters.
[0151] Specifically, some parameters set for Normal UEs are not used for RedCap UEs. For example, RedCap UEs can ignore ta-CommonDriftVariant (common TA is calculated using ta-Common / ta-CommonDrift, see [link]). Figure 4 ), and TA report validity (TA reports are not executed). Additionally, it is possible to configure and / or notify that this part of the parameters is not used, or which parameter is not used. For this configuration and / or notification, independent parameters in the NTN-specific SIB can be used, or independent signaling for each UE can be used.
[0152] Furthermore, regarding the NTN-specific SIB, independent settings and joint settings from the Normal UE and RedCap UE can be combined. Additionally, in the joint settings, at least some of the aforementioned settings can be ignored, or they can be omitted. Furthermore, regarding the NTN-specific SIB, independent settings from the Normal UE and RedCap UE can be combined with settings that ignore at least some settings based on the NTN-specific SIB. For example, independent settings can be applied to some parameters, while settings that ignore other parameters can be applied. Moreover, even when such settings are combined, even when settings that ignore at least some settings based on the NTN-specific SIB are applied, the result is that independent settings can be applied to all parameters, without applying settings that ignore some settings.
[0153] According to this example, the NTN-specific SIB can also be configured independently for the Normal UE and the RedCap UE. Alternatively, when the NTN-specific SIB represents a joint configuration for the Normal UE and the RedCap UE, the RedCap UE can ignore at least some of the configurations based on the NTN-specific SIB. Therefore, it eliminates the need for NTN-specific operating rules for the RedCap UE, which can help reduce the cost of the RedCap UE.
[0154] (4) Other implementation methods
[0155] The above describes the implementation method, but it is not limited to the described implementation method. Various modifications and improvements can be made, which will be obvious to those skilled in the art.
[0156] For example, in the above implementation, it was described under the premise that RedCap UE and eRedCap UE have reduced certain capabilities. However, as mentioned above, RedCap UE and eRedCap UE may not necessarily have reduced capabilities. They can also be interpreted as UEs for URLLC (Ultra-Reliable and Low Latency Communications) or IoT (Internet of Things), as long as they are specific types of UEs that can be distinguished from Non-RedCap UEs.
[0157] Furthermore, in the above description, the terms configure, activate, update, indicate, enable, specify, and select can be interchanged. Similarly, the terms link, associate, correspond, and map can be interchanged, as can allocate, assign, monitor, and map.
[0158] Furthermore, specific, dedicated, UE specific, and UE dedicated can be used interchangeably. Similarly, common, shared, group-common, UE common, and UE shared can also be used interchangeably.
[0159] The block diagram used in the description of the above embodiments ( Figure 3 The diagram illustrates blocks organized by function. These functional blocks (components) are implemented through any combination of at least one of hardware and software. Furthermore, there are no particular limitations on the implementation method of each functional block. That is, each functional block can be implemented using a single device that is physically or logically combined, or by directly or indirectly (e.g., using wired, wireless, etc.) connecting two or more physically or logically separate devices. Functional blocks can be implemented by combining software with the aforementioned single or multiple devices.
[0160] The functions include judgment, decision, determination, calculation, calculation, processing, derivation, investigation, search, confirmation, receiving, sending, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assigning, but are not limited to these. For example, the functional block (structural part) that enables sending is called the transmitting unit or transmitter. In short, as mentioned above, there are no particular limitations on the implementation method.
[0161] Furthermore, the aforementioned gNB100 and UE200 (the device) can also function as a computer for processing the wireless communication method disclosed herein. Figure 8 This is a diagram illustrating an example of the hardware structure of the device. (As shown...) Figure 8 As shown, the device can also be configured as a computer device including a processor 1001, a memory 1002, a storage device 1003, a communication device 1004, an input device 1005, an output device 1006, and a bus 1007.
[0162] Additionally, in the following description, the term "device" can be replaced with "circuit," "device," "unit," etc. The hardware structure of this device can be configured as either a device comprising one or more of the illustrated components, or a device that does not comprise any of the components.
[0163] The functional blocks of the device (refer to) Figure 3 This can be achieved through any hardware element or combination of hardware elements of the computer device.
[0164] Furthermore, the functions of the device are implemented by reading predetermined software (programs) into hardware such as processor 1001 and memory 1002, so that processor 1001 performs calculations and controls communication of communication device 1004 or controls at least one of reading and writing data in memory 1002 and storage device 1003.
[0165] The processor 1001 controls the computer as a whole by instructing the operating system to operate. The processor 1001 may also be a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic units, registers, etc.
[0166] Furthermore, the processor 1001 reads programs (program code), software modules, data, etc., from at least one direction of memory 1002 in the storage device 1003 and the communication device 1004, and performs various processes accordingly. The program is used to cause the computer to perform at least a portion of the actions described in the above embodiments. Moreover, the various processes described above can be executed by one processor 1001, or by two or more processors 1001 simultaneously or sequentially. The processor 1001 can also be implemented using one or more chips. Additionally, the program can be transmitted from a network via a telecommunications line.
[0167] The memory 1002 is a computer-readable recording medium, and may be composed of at least one of the following: read-only memory (ROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), and random access memory (RAM). The memory 1002 may be referred to as a register, cache memory, main memory (main storage device), etc. The memory 1002 may store programs (program code), software modules, etc., capable of executing the methods involved in one embodiment of this disclosure.
[0168] Storage device 1003 is a computer-readable recording medium, and may be composed of at least one of the following: optical discs such as CD-ROM (Compact Disc ROM), hard disk drives, floppy disks, magneto-optical discs (e.g., compact discs, digital multipurpose discs, Blu-ray discs), smart cards, flash memory (e.g., cards, sticks, key drives), floppy disks, magnetic stripes, etc. Storage device 1003 may also be referred to as an auxiliary storage device. The aforementioned recording medium may, for example, be a database, server, or other suitable media that includes at least one of memory 1002 and storage device 1003.
[0169] The communication device 1004 is hardware (transceiver) used for communication between computers via at least one of a wired network and a wireless network. For example, it may also be called a network device, network controller, network card, communication module, etc.
[0170] The communication device 1004 may also be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc., to realize at least one of frequency division duplex (FDD) and time division duplex (TDD).
[0171] Input device 1005 is an input device that accepts input from external sources (e.g., keyboard, mouse, microphone, switch, button, sensor, etc.). Output device 1006 is an output device that performs output to external sources (e.g., display, speaker, LED, etc.). Alternatively, input device 1005 and output device 1006 can also be integrated (e.g., a touch panel).
[0172] Furthermore, devices such as processor 1001 and memory 1002 are connected via bus 1007 for communicating information. Bus 1007 can be a single bus or can be composed of different buses between devices.
[0173] Furthermore, the device can 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), and a field-programmable gate array (FPGA), which can be used to implement some or all of the functional blocks. For example, the processor 1001 can also be implemented using at least one of these hardware components.
[0174] Furthermore, the notification of information is not limited to the forms / implementations described in this disclosure, and other methods may also be used. For example, the notification of information may be implemented through 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 combinations thereof. In addition, RRC signaling may also be referred to as an RRC message, for example, it may be an RRC Connection Setup message, an RRC Connection Reconfiguration message, etc.
[0175] The various forms / implementations described in this disclosure can also be applied to systems utilizing Long Term Evolution (LTE), LTE-Advanced (LTE-A), Super 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (x being, for example, an integer or 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, and Ultra-Wideband (UMB). A system of at least one of UWB, Bluetooth (registered trademark), other suitable systems, and next-generation systems based on these systems. Furthermore, multiple systems can be combined (e.g., a combination of at least one of LTE and LTE-A with 5G, etc.) for application.
[0176] The processing steps, timing, and processes described in this disclosure can be rearranged in order without contradiction. For example, the illustrated order is used to indicate the elements of each step in the methods described in this disclosure, but the order is not limited to the specific order indicated.
[0177] In this disclosure, certain actions performed by the base station are sometimes also performed by its upper node, depending on the circumstances. In a network consisting of one or more network nodes having a base station, it is obvious that various actions performed to communicate with a terminal can be performed by at least one of the base station and other network nodes besides the base station (e.g., considering an MME or S-GW, but not limited to these). The above illustration depicts a single network node other than the base station, but it can also be a combination of multiple other network nodes (e.g., an MME and an S-GW).
[0178] Information and signals (such as data) can be output from a higher (or lower) layer to a lower (or higher) layer. They can also be input or output through multiple network nodes.
[0179] Input or output information can be stored in a specific location (e.g., memory) or managed using a management table. Input and output information can be overwritten, updated, or appended. Output information can also be deleted. Input information can also be sent to other devices.
[0180] The determination can be made by the value represented by 1 bit (0 or 1), by a Boolean value (Boolean: true or false), or by comparing numerical values (e.g., comparing with a predetermined value).
[0181] The various forms / implementations described in this disclosure can be used individually, in combination, or switched between each other during execution. Furthermore, the notification of predetermined information (e.g., a "It is X" notification) is not limited to being explicit, but can also be implicit (e.g., not notifying the predetermined information).
[0182] Software, whether called software, firmware, middleware, microcode, hardware description language, or by other names, should be broadly interpreted as referring to commands, command sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc.
[0183] In addition, software, commands, and information can also be sent and received via transmission media. For example, when software is sent from a website, server, or other remote source using at least one of wired technologies (coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL) etc.) and wireless technologies (infrared, microwave, etc.), at least one of these wired and wireless technologies is included within the definition of transmission media.
[0184] The information, signals, etc., described in this disclosure can also be represented using any of a variety of different technologies. For example, the data, commands, instructions, information, signals, bits, symbols, chips, etc., that may be involved in the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any combination of these.
[0185] Furthermore, the terms used in this disclosure and those necessary for understanding this disclosure may be replaced with terms that have the same or similar meanings. For example, at least one of the channel and symbol may also be a signal (signaling). Additionally, a signal may also be a message. Furthermore, a component carrier (CC) may also be referred to as carrier frequency, cell, frequency carrier, etc.
[0186] The terms “system” and “network” as used in this disclosure are used interchangeably.
[0187] Furthermore, the information, parameters, etc., described in this disclosure may be represented using absolute values, relative values to predetermined values, or other corresponding information. For example, wireless resources may also be indicated using indexes.
[0188] The names used for the above parameters are non-limiting in any respect. Furthermore, the formulas, etc., using these parameters may sometimes differ from those explicitly disclosed in this disclosure. Various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by any appropriate name, and therefore the various names assigned to these channels and information elements are non-limiting in any respect.
[0189] In this disclosure, the terms "Base Station (BS)," "wireless 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" are used interchangeably. Sometimes, terms such as macro cell, small cell, femtocell, and picocell are also used to refer to base stations.
[0190] 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 also provide communication services through the base station subsystem (e.g., a small indoor base station (Remote Radio Head: RRH)).
[0191] Terms such as “cell” or “sector” refer to a portion or the entire coverage area of at least one of the base stations and base station subsystems that provide communication services within that coverage area.
[0192] In this disclosure, the base station sending information to the terminal can also be replaced by the base station instructing the terminal on information-based control / actions.
[0193] In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," and "terminal" are used interchangeably.
[0194] For mobile stations, those skilled in the art sometimes also use the following terms: subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handheld device, user agent, mobile client, client, or some other appropriate terms.
[0195] At least one of the base station and mobile station can also be referred to as a transmitting device, receiving device, communication device, etc. Additionally, at least one of the base station and mobile station can also be a device mounted on a mobile body, the mobile body itself, etc. The mobile body can be a vehicle (e.g., a car, an airplane, etc.), a mobile body moving in an unmanned manner (e.g., a drone, an autonomous vehicle, etc.), or a robot (humanized or unmanned). Furthermore, at least one of the base station and mobile station also includes devices that do not necessarily move during communication. For example, at least one of the base station and mobile station can be an IoT (Internet of Things) device such as a sensor.
[0196] Furthermore, the base station in this disclosure can also be replaced by a mobile station (user terminal, hereinafter the same). For example, various forms / implementations of this disclosure can also be applied to structures that replace communication between the base station and the mobile station with communication between multiple mobile stations (e.g., also referred to as D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.). In this case, the structure can also be configured such that the mobile station has the functions of the base station. In addition, terms such as "uplink" and "downlink" can also be replaced with terms corresponding to communication between terminals (e.g., "side"). For example, uplink channel, downlink channel, etc. can be replaced with side channel (or side link).
[0197] Similarly, the mobile station in this disclosure can be replaced by a base station. In this case, the base station can also be configured to have the functions of a mobile station.
[0198] A radio frame can consist of one or more frames in the time domain. Each frame in the time domain is called a subframe. A subframe can also consist of one or more time slots in the time domain. A subframe can have a fixed duration (e.g., 1 ms) independent of the parameter set (numerology).
[0199] A parameter set can be communication parameters applied to at least one of the transmission and reception of a signal or channel. For example, a parameter set can represent at least one of the following: Subcarrier Spacing (SCS), bandwidth, symbol length, cyclic prefix length, Transmission Time Interval (TTI), number of symbols per TTI, radio frame structure, specific filtering processing performed by the transceiver in the frequency domain, and specific windowing processing performed by the transceiver in the time domain.
[0200] In the time domain, a time slot can be composed of one or more symbols (OFDM (Orthogonal Frequency Division Multiplexing) symbols, SC-FDMA (Single Carrier Frequency Division Multiple Access) symbols, etc.). A time slot can be a time unit based on a set of parameters.
[0201] A time slot can contain multiple mini-time slots. Each mini-time slot can consist of one or more symbols in the time domain. Furthermore, a mini-time slot can also be called a sub-time slot. A mini-time slot can consist of fewer symbols than a time slot. PDSCH (or PUSCH) transmitted in a time unit larger than a mini-time slot can also be called PDSCH (or PUSCH) mapping type A. PDSCH (or PUSCH) transmitted using mini-time slots can also be called PDSCH (or PUSCH) mapping type B.
[0202] Radio frames, subframes, time slots, mini-time slots, and symbols all represent time units for transmitting signals. Radio frames, subframes, time slots, mini-time slots, and symbols can each be referred to by other corresponding names.
[0203] For example, a single subframe can be called a Transmission Time Interval (TTI), multiple consecutive subframes can also be called a TTI, and a single time slot or a single mini-time slot can also be called a TTI. That is, at least one of a subframe or TTI can be a subframe (1ms) in existing LTE, a period shorter than 1ms (e.g., 1-13 symbols), or a period longer than 1ms. Furthermore, the unit representing TTI can also be called a time slot, mini-time slot, etc., instead of a subframe.
[0204] Here, TTI refers, for example, to the smallest unit of time for scheduling in wireless communication. For instance, in an LTE system, the base station schedules the allocation of radio resources (bandwidth, transmit power, etc., available to each user terminal) in TTI units. However, the definition of TTI is not limited to this.
[0205] The Time Interval (TTI) can be a unit of time for transmitting channel-coded data packets (transmission blocks), code blocks, codewords, etc., or it can be a processing unit such as scheduling or link adaptation. Furthermore, when a TTI is given, the actual time interval (e.g., the number of symbols) that the transmission block, code block, codeword, etc., are mapped to can be shorter than that TTI.
[0206] Furthermore, when one time slot or one mini time slot is referred to as a TTI, more than one TTI (i.e., more than one time slot or more than one mini time slot) can become the minimum time unit for scheduling. In addition, the number of time slots (mini time slots) constituting the minimum time unit for scheduling can also be controlled.
[0207] A TTI with a duration of 1ms is also called a normal TTI (TTI in LTE Rel.8-12), a long TTI, a normal subframe, a long subframe, or a time slot. A TTI shorter than a normal TTI can also be called a shortened TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a mini time slot, a sub-time slot, or a time slot.
[0208] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) can be understood as a TTI with a duration of more than 1ms, and a short TTI (e.g., a shortened TTI, etc.) can be understood as a TTI with a duration of less than a long TTI but more than 1ms.
[0209] A resource block (RB) is a unit of resource allocation in both the time and frequency domains. In the frequency domain, it can contain one or more consecutive subcarriers. The number of subcarriers contained in an RB can be the same regardless of the parameter set, for example, it can be 12. The number of subcarriers contained in an RB can also be determined based on the parameter set.
[0210] Furthermore, the temporal domain of an RB can include one or more symbols, or it can be the length of one time slot, one mini-time slot, one subframe, or one TTI. A TTI, a subframe, etc., can also be composed of one or more resource blocks.
[0211] In addition, one or more RBs can also be called Physical Resource Block (PRB), Sub-Carrier Group (SCG), Resource Element Group (REG), PRB pair, RB pair, etc.
[0212] Furthermore, a resource block can consist of one or more resource elements (REs). For example, one RE can be a radio resource area consisting of one subcarrier and one symbol.
[0213] The Bandwidth Part (BWP) (also known as partial bandwidth, etc.) can represent a subset of contiguous common resource blocks (RBs) used for a certain parameter set in a given carrier. Here, common RBs can be determined by indexing RBs based on a common reference point of that carrier. PRBs can be defined and numbered within a BWP.
[0214] A BWP can include a UL BWP and a DL BWP. One or more BWPs can be set for a UE within a single carrier.
[0215] At least one of the configured BWPs can be active, and the scenario of the UE transmitting or receiving predetermined signals / channels outside of the active BWP is not considered. Furthermore, the terms "cell," "carrier," etc., used in this disclosure can be replaced with "BWP."
[0216] The structures of radio frames, subframes, time slots, mini-time slots, and symbols described above are merely illustrative. For example, the number of subframes contained in a radio frame, the number of time slots in each subframe or radio frame, the number of mini-time slots contained within a time slot, the number of symbols and RBs contained in a time slot or mini-time slot, the number of subcarriers contained in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, etc., can be varied in many ways.
[0217] The terms “connected,” “coupled,” or any variations thereof are intended to indicate any direct or indirect connection or combination between two or more elements, including cases where there is one or more intermediate elements between the two elements that are “connected” or “coupled.” The combination or connection between elements can be physical, logical, or a combination of these. For example, “access” can be used instead of “connected.” In the context of this disclosure, it can be understood that two elements are “connected” or “coupled” to each other using at least one of one or more wires, cables, and printed electrical connections, and, as some non-limiting and non-inclusive examples, using electromagnetic energy with wavelengths in the wireless frequency domain, microwave region, and light (including both visible and invisible regions) to “connect” or “couple” to each other.
[0218] The reference signal can be simply called the Reference Signal (RS), or, depending on the standard applied, the pilot.
[0219] As used in this disclosure, the word "based on" does not mean "based on only" unless otherwise expressly stated. In other words, the word "based on" means both "based on only" and "based on at least".
[0220] Alternatively, the "unit" in the structure of the above devices can be replaced with "section", "circuit", "equipment", etc.
[0221] Any reference to elements using the designations "first," "second," etc., as used in this disclosure does not necessarily limit the number or order of these elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Therefore, reference to the first and second elements does not imply that only two elements can be used there, or that the first element must precede the second element in some form.
[0222] When the terms "include," "including," and their variations are used in this disclosure, these terms, like the term "comprising," imply inclusion. Furthermore, the term "or" as used in this disclosure does not refer to XOR.
[0223] In this disclosure, for example, in cases where articles are added through translation, such as in English (a, an, and the), this disclosure also includes cases where the noun following these articles is in a plural form.
[0224] The terms "determining" and "determining" as used in this disclosure sometimes encompass a variety of actions. For example, "determining" or "determining" may include situations where actions such as judging, calculating, computing, processing, deriving, investigating, searching (e.g., searching in a table, database, or other data structure), and ascertaining are considered as "determining" or "determining." Furthermore, "determining" or "determining" may include situations where actions such as receiving (e.g., receiving information), transmitting (e.g., sending information), inputting, outputting, and accessing (e.g., accessing data in memory) are considered as "determining" or "determining." Additionally, "determining" or "determining" may include situations where actions such as resolving, selecting, choosing, establishing, and comparing are considered as "determining" or "determining." That is, "judgment" and "decision" can include situations where certain actions are regarded as having been "judged" or "decided". In addition, "judgment (decision)" can also be replaced by "assuming", "expecting", "considering", etc.
[0225] In this disclosure, the phrase "A and B are different" can mean "A and B are different from each other." Additionally, this phrase can also mean "A and B are each different from C." Terms such as "separate" and "combined" can also be interpreted in the same way as "different."
[0226] Figure 9 An example of the structure of vehicle 2001 is shown. For example... Figure 9 As shown, the vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a gear 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.
[0227] The drive unit 2002 may consist of, for example, an engine, a motor, or a hybrid powertrain of an engine and a motor. The steering unit 2003 includes at least a steering wheel (also called a steering wheel), configured to steer at least one of the front and rear wheels based on user-operated steering wheel movements. The electronic control unit 2010 consists of a microprocessor 2031, a memory (ROM, RAM) 2032, and a communication port (I / O port) 2033. Signals from various sensors 2021-2027 present in the vehicle are input to the electronic control unit 2010. The electronic control unit 2010 may also be referred to as an ECU (Electronic Control Unit).
[0228] The signals from various sensors 2021 to 2028 include current signals from current sensor 2021 that senses the current of the motor, speed signals of the front and rear wheels obtained by speed sensor 2022, air pressure signals of the front and rear wheels obtained by air pressure sensor 2023, vehicle speed signals obtained by vehicle speed sensor 2024, acceleration signals obtained by acceleration sensor 2025, accelerator pedal input signals obtained by accelerator pedal sensor 2029, brake pedal input signals obtained by brake pedal sensor 2026, gear lever operation signals obtained by gear lever sensor 2027, and detection signals for detecting obstacles, vehicles, pedestrians, etc. obtained by object detection sensor 2028.
[0229] The Information Service Unit 2012 consists of various devices such as a car navigation system, audio system, speakers, television, and radio, which provide (output) various information such as driving information, traffic information, and entertainment information, and one or more ECUs that control these devices. The Information Service Unit 2012 uses information obtained from external devices via a communication module 2013, etc., to provide various multimedia information and multimedia services to the occupants of vehicle 1.
[0230] The Information Services Department 2012 may include input devices (such as keyboards, mice, microphones, switches, buttons, sensors, touch panels, etc.) that accept input from external sources, and may also include output devices (such as monitors, speakers, LEDs, touch panels, etc.) that implement output to external sources.
[0231] The Driver Assistance System 2030 comprises various devices used to prevent accidents or reduce driver workload, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning devices (e.g., GNSS), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps), gyroscope systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System)), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. Furthermore, the Driver Assistance System 2030 transmits and receives various information via the communication module 2013 to achieve driver assistance or autonomous driving functions.
[0232] The communication module 2013 can communicate with the microprocessor 2031 and the components of the vehicle 1 via the communication port. For example, the communication module 2013 can send and receive data with the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, gear shift lever 2006, left and right front wheels 2007, left and right rear wheels 2008, axle 2009, microprocessor 2031 in the electronic control unit 2010, memory (ROM, RAM) 2032, and sensors 2021 to 2028 in the vehicle 2001 via the communication port 2033.
[0233] The communication module 2013, controlled by the microprocessor 2031 of the electronic control unit 2010, is a communication device capable of communicating with external devices. For example, it can transmit and receive various types of information with external devices via wireless communication. The communication module 2013 can be located inside or outside the electronic control unit 2010. External devices can be, for example, base stations, mobile stations, etc.
[0234] The communication module 2013 can also wirelessly transmit at least one of the signals input to the electronic control unit 2010 from the various sensors 2021-2028, the information obtained based on those signals, and the information obtained via the information service unit 2012 based on input from an external source (user) to an external device. The electronic control unit 2010, the various sensors 2021-2028, and the information service unit 2012 can also be referred to as input units that receive input. For example, the PUSCH transmitted by the communication module 2013 may include information based on the aforementioned inputs.
[0235] The communication module 2013 receives various information (traffic information, signal information, inter-vehicle information, etc.) sent from external devices and displays it on the information service unit 2012 of the vehicle. The information service unit 2012 can also be referred to as an output unit for outputting information (for example, outputting information to devices such as displays and speakers based on the PDSCH received by the communication module 2013 (or data / information decoded from the PDSCH). In addition, the communication module 2013 stores the various information received from external devices in a memory 2032 available to the microprocessor 2031. The microprocessor 2031 can also control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, gear shift lever 2006, left and right front wheels 2007, left and right rear wheels 2008, axles 2009, sensors 2021 to 2028, etc., of the vehicle 2001 based on the information stored in the memory 2032.
[0236] The present disclosure has been described in detail above, but it will be clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered ways without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the description in this disclosure is for illustrative purposes only and is not intended to be limiting in any way.
[0237] (Postscript)
[0238] The above disclosure can also be expressed as follows: The first feature is a terminal comprising: a control unit that sets a physical channel that applies a common setting to both a normal terminal and a capability-reduced terminal, wherein the capability of the capability-reduced terminal is reduced compared to the normal terminal; and a communication unit that uses the physical channel to perform wireless communication via a non-terrestrial network.
[0239] The second feature is a terminal comprising: a control unit that sets a physical channel independently of the capability-reducing terminal, which has reduced capabilities compared to a normal terminal; and a communication unit that uses the physical channel to perform wireless communication via a non-terrestrial network.
[0240] The third feature is that, in the first or second feature, the control unit sets at least one of an independently configured uplink control channel or downlink data channel to be applied for the number of repeated transmissions.
[0241] The fourth feature is a terminal comprising: a receiving unit that receives broadcast information for a capability-reducing terminal application with reduced capabilities compared to a normal terminal, and settings independent of the normal terminal; and a control unit that executes settings applied via a non-terrestrial network based on the broadcast information.
[0242] The fifth feature is a terminal comprising: a receiving unit that receives broadcast information applying settings common to both a normal terminal and a capability-reduced terminal, wherein the capability of the capability-reduced terminal is reduced compared to the normal terminal; and a control unit that, when transmitted via a non-terrestrial network, ignores at least a portion of the settings and executes settings for the capability-reduced terminal.
[0243] Label Explanation
[0244] 10 Wireless Communication Systems
[0245] 20 NG-RAN
[0246] 100 gNB
[0247] 100X NTN Gateway
[0248] 150 satellites
[0249] 200 UE
[0250] 210 Wireless Signal Transceiver Unit
[0251] 220 Enlarged Section
[0252] 230 Modulation and Demodulation Section
[0253] 240 control signal Reference Signal Processing Unit
[0254] 250 Encoding / Decoding Unit
[0255] 260 Data Transceiver Department
[0256] 270 Control Department
[0257] 1001 processor
[0258] 1002 Memory
[0259] 1003 Storage device
[0260] 1004 Communication device
[0261] 1005 Input Device
[0262] 1006 Output Device
[0263] 1007 bus
[0264] Vehicle 2001
[0265] 2002 Drive Unit
[0266] 2003 Steering Unit
[0267] 2004 Accelerator Pedal
[0268] 2005 Brake Pedal
[0269] 2006 gearshift lever
[0270] Front wheels around 2007
[0271] 2008 rear wheels (left and right)
[0272] 2009 axle
[0273] 2010 Electronic Control Department
[0274] 2012 Information Service Department
[0275] 2013 Communication Module
[0276] 2021 Current Sensor
[0277] 2022 Speed Sensor
[0278] 2023 Barometric Pressure Sensor
[0279] 2024 vehicle speed sensor
[0280] 2025 Accelerometer
[0281] 2026 Brake Pedal Sensor
[0282] 2027 Gearshift sensor
[0283] 2028 Object Detection Sensor
[0284] 2029 Accelerator Pedal Sensor
[0285] 2030 Driver Assistance Systems Department
[0286] 2031 microprocessor
[0287] 2032 Memory (ROM, RAM)
[0288] 2033 Communication Port
Claims
1. A terminal, comprising: The control unit uses a physical channel with settings common to both conventional and low-capacity terminals. Compared to the usual terminal, the capabilities of the capability-reduced terminal are reduced. as well as The communications unit uses the physical channel to perform wireless communication via a non-terrestrial network.
2. A terminal, comprising: The control unit sets physical channels that are independent of those settings for a capability-reduced terminal compared to a normal terminal; and The communications unit uses the physical channel to perform wireless communication via a non-terrestrial network.
3. The terminal according to claim 2, wherein, The control unit sets at least one of an independently configured uplink control channel or downlink data channel to be applied for the number of repeated transmissions.
4. A terminal, comprising: The receiving unit receives broadcast information configured independently of the ordinary terminal for a terminal application with reduced capabilities compared to the ordinary terminal; and The control unit executes settings applicable when the broadcast information is transmitted via a non-terrestrial network.
5. A terminal, comprising: The receiving unit receives broadcast information that uses settings common to both conventional and degraded terminals. Compared to the typical terminal, the capabilities of the capability-reduced terminal are reduced. as well as The control unit, when traversing a non-terrestrial network, ignores at least a portion of the settings and executes settings for the reduced-capability terminal.
6. A wireless communication method in a terminal, comprising the following steps: The physical channel is configured using settings common to both conventional and degraded terminals. Compared to the typical terminal, the capabilities of the capability-reduced terminal are reduced. as well as Wireless communication via non-terrestrial networks is performed using the physical channel.