Method and apparatus for uplink transmission in non-terrestrial network

Abstract

Provided are a method for performing wireless communication and an apparatus supporting same. The method may comprise the steps of: acquiring, by a first device, information related to a second sync raster; on the basis of the information related to the second sync raster, receiving, by the first device, a second synchronization signal block from a second device; and acquiring, by the first device, synchronization on the basis of the second synchronization signal block. For example, the second synchronization signal block may be a synchronization signal block simplified compared to a first synchronization signal block on a first sync raster.

Description

Uplink transmission method and device in a non-terrestrial network

[0001] The present disclosure relates to non-terrestrial networks. More specifically, the present disclosure relates to an uplink transmission method in a non-terrestrial network and an apparatus supporting the same.

[0002] 5G NR is a successor technology to LTE (long term evolution) and is a new clean-slate type mobile communication system with characteristics such as high performance, low latency, and high availability. 5G NR can utilize all available spectrum resources, ranging from low frequency bands below 1 GHz to mid-frequency bands from 1 GHz to 10 GHz, and high frequency (millimeter wave) bands above 24 GHz.

[0003] The 6G (wireless communication) system aims for (i) very high data rates per device, (ii) a very large number of connected devices, (iii) global connectivity, (iv) very low latency, (v) reduced energy consumption of battery-free IoT (internet of things) devices, (vi) ultra-reliable connectivity, and (vii) connected intelligence with machine learning capabilities. The vision of the 6G system can be in four aspects: intelligent connectivity, deep connectivity, holographic connectivity, and ubiquitous connectivity, and the 6G system can satisfy requirements such as those shown in Table 1 below. For example, Table 1 may represent an example of the requirements for a 6G system.

[0004] Maximum data rate per device 1 Tbps E2E latency 1 ms Maximum spectral efficiency 100 bps / Hz Mobility support up to 1000 km / hr Satellite integration Fully AI Fully autonomous driving Fully XR Fully haptic communication Fully

[0005] According to one embodiment of the present disclosure, a method may be provided. For example, the method may include: a first device acquiring information related to a second sync raster; a first device receiving a second synchronization signal block from a second device based on the information related to the second sync raster; and a first device acquiring synchronization based on the second synchronization signal block. For example, the second synchronization signal block may be a simplified synchronization signal block compared to a first synchronization signal block on a first sync raster.

[0006] According to one embodiment of the present disclosure, a first device may be provided. For example, the first device may include at least one transceiver; at least one processor; and at least one memory connected to the at least one processor and storing instructions. For example, the instructions may cause the first device, based on execution by the at least one processor: to obtain information related to a second sync raster; to receive a second synchronization signal block from a second device based on the information related to the second sync raster; and to obtain synchronization based on the second synchronization signal block. For example, the second synchronization signal block may be a simplified synchronization signal block compared to a first synchronization signal block on a first sync raster.

[0007] According to one embodiment of the present disclosure, a processing device (configured to control a first device) may be provided. For example, the processing device may include at least one processor; and at least one memory connected to the at least one processor and storing instructions. For example, the instructions may cause the first device, based on execution by the at least one processor: to obtain information related to a second sync raster; to receive a second synchronization signal block from the second device based on the information related to the second sync raster; and to obtain synchronization based on the second synchronization signal block. For example, the second synchronization signal block may be a simplified synchronization signal block compared to a first synchronization signal block on a first sync raster.

[0008] According to one embodiment of the present disclosure, a non-transient computer-readable storage medium recording instructions may be provided. For example, when the instructions are executed, the first device may: acquire information related to a second sync raster; receive a second synchronization signal block from a second device based on the information related to the second sync raster; and acquire synchronization based on the second synchronization signal block. For example, the second synchronization signal block may be a simplified synchronization signal block compared to a first synchronization signal block on a first sync raster.

[0009] According to one embodiment of the present disclosure, a method may be provided. For example, the method may include: a step in which a second device transmits information related to a second sync raster to a first device; a step in which, based on the information related to the second sync raster, the second device transmits a second synchronization signal block to the first device; and a step in which, based on the second synchronization signal block, the second device obtains synchronization. For example, the second synchronization signal block may be a simplified synchronization signal block compared to a first synchronization signal block on a first sync raster.

[0010] According to one embodiment of the present disclosure, a second device may be provided. For example, the second device may include at least one transceiver; at least one processor; and at least one memory connected to the at least one processor and storing instructions. For example, based on the instructions executed by the at least one processor, the second device may: transmit information related to a second sync raster to the first device; transmit a second synchronization signal block to the first device based on the information related to the second sync raster; and acquire synchronization based on the second synchronization signal block. For example, the second synchronization signal block may be a simplified synchronization signal block compared to a first synchronization signal block on a first sync raster.

[0011] According to one embodiment of the present disclosure, a processing device (configured to control a second device) may be provided. For example, the processing device may include at least one processor; and at least one memory connected to the at least one processor and storing instructions. For example, the instructions may cause the second device, based on execution by the at least one processor: to transmit information related to a second sync raster to the first device; to transmit a second synchronization signal block to the first device based on the information related to the second sync raster; and to obtain synchronization based on the second synchronization signal block. For example, the second synchronization signal block may be a simplified synchronization signal block compared to a first synchronization signal block on a first sync raster.

[0012] According to one embodiment of the present disclosure, a non-transient computer-readable storage medium recording instructions may be provided. For example, when the instructions are executed, the second device may cause: to transmit information related to a second sync raster to the first device; to transmit a second synchronization signal block to the first device based on the information related to the second sync raster; and to obtain synchronization based on the second synchronization signal block. For example, the second synchronization signal block may be a simplified synchronization signal block compared to a first synchronization signal block on a first sync raster.

[0013] FIG. 1 illustrates a communication procedure between devices according to one embodiment of the present disclosure.

[0014] FIG. 2 shows a radio protocol architecture according to one embodiment of the present disclosure.

[0015] FIG. 3 shows the structure of a wireless frame according to one embodiment of the present disclosure.

[0016] FIG. 4 shows a slot structure of a frame according to one embodiment of the present disclosure.

[0017] FIG. 5 shows an example of a BWP according to one embodiment of the present disclosure.

[0018] FIG. 6 shows a communication structure that can be provided in a 6G system according to one embodiment of the present disclosure.

[0019] FIG. 7 illustrates an example of a communication scenario based on a 6G system according to an embodiment of the present disclosure.

[0020] FIG. 8 shows a non-terrestrial network scenario according to one embodiment of the present disclosure.

[0021] FIG. 9 shows a non-terrestrial network scenario according to one embodiment of the present disclosure.

[0022] FIG. 10 shows examples of an NTN access network according to one embodiment of the present disclosure.

[0023] FIG. 11 illustrates an example of possible options for an NTN architecture according to one embodiment of the present disclosure.

[0024] FIG. 12 illustrates an example of possible options for an NTN architecture according to one embodiment of the present disclosure.

[0025] FIG. 13 illustrates a procedure for downlink transmission and reception according to one embodiment of the present disclosure.

[0026] FIG. 14 illustrates a procedure for uplink transmission and reception according to one embodiment of the present disclosure.

[0027] FIG. 15 shows an example of NTN according to one embodiment of the present disclosure.

[0028] FIG. 16 is according to one embodiment of the present disclosure, class It shows an example of.

[0029] FIG. 17 shows examples of UE-specific TA and common TA according to one embodiment of the present disclosure.

[0030] FIG. 18 shows an example of an uplink-downlink timing relationship according to one embodiment of the present disclosure.

[0031] FIG. 19 shows an example of TA mismatch within a beam / cell according to one embodiment of the present disclosure.

[0032] FIG. 20 shows an example of an orbital parameter orbital format according to one embodiment of the present disclosure.

[0033] FIG. 21 illustrates a procedure performed by a first device according to one embodiment of the present disclosure.

[0034] FIG. 22 illustrates a procedure performed by a second device according to one embodiment of the present disclosure.

[0035] FIG. 23 shows a communication system (1) according to one embodiment of the present disclosure.

[0036] FIG. 24 shows a wireless device according to one embodiment of the present disclosure.

[0037] FIG. 25 shows a signal processing circuit for a transmission signal according to one embodiment of the present disclosure.

[0038] FIG. 26 shows a wireless device according to one embodiment of the present disclosure.

[0039] FIG. 27 shows a portable device according to one embodiment of the present disclosure.

[0040] In the present disclosure, "A or B" may mean "only A," "only B," or "both A and B." Alternatively, in the present disclosure, "A or B" may be interpreted as "A and / or B." For example, in the present disclosure, "A, B or C" may mean "only A," "only B," "only C," or "any combination of A, B and C."

[0041] A slash ( / ) or a comma used in the present disclosure may mean "and / or." For example, "A / B" may mean "A and / or B." Accordingly, "A / B" may mean "only A," "only B," or "both A and B." For example, "A, B, C" may mean "A, B or C."

[0042] In the present disclosure, "at least one of A and B" may mean "only A," "only B," or "both A and B." Additionally, in the present disclosure, the expressions "at least one of A or B" or "at least one of A and / or B" may be interpreted as synonymous with "at least one of A and B."

[0043] Additionally, in the present disclosure, "at least one of A, B and C" may mean "only A," "only B," "only C," or "any combination of A, B and C." Additionally, "at least one of A, B or C" or "at least one of A, B and / or C" may mean "at least one of A, B and C."

[0044] Additionally, parentheses used in the present disclosure may mean "for example." Specifically, when indicated as "control information (PDCCH)," "PDCCH" may be proposed as an example of "control information." In other words, the "control information" of the present disclosure is not limited to "PDCCH," and "PDCCH" may be proposed as an example of "control information." Furthermore, even when indicated as "control information (e.g., PDCCH)," "PDCCH" may be proposed as an example of "control information."

[0045] In the following explanation, 'when, if, in case of' can be replaced with 'based on'.

[0046] Technical features described individually within one drawing in this disclosure may be implemented individually or simultaneously.

[0047] In the present disclosure, a higher layer parameter may be a parameter that is set for the terminal, pre-set, or pre-defined. For example, a base station or a network may transmit the higher layer parameter to the terminal. For example, the higher layer parameter may be transmitted via radio resource control (RRC) signaling or medium access control (MAC) signaling.

[0048] In the present disclosure, "configured or defined" may be interpreted as being configured or pre-configured to a device through pre-defined signaling from a base station or network (e.g., SIB, MAC, RRC, DCI (downlink control information), etc.). In the present disclosure, "configured or defined" may be interpreted as being configured or pre-configured to a device through pre-defined signaling from another device (e.g., MAC, RRC, SCI (sidelink control information), control information signaled between devices, etc.). In the present disclosure, "configured or defined" may be interpreted as being pre-configured to a device.

[0049] In the present disclosure, user equipment (UE) may refer to a device, a portable device, a wireless device, etc. In the present disclosure, a base station (BS) may refer to a radio access network (RAN) node, a non-terrestrial network (NTN) cell / node, a transmission reception point (TRP), a network, an integrated access and backhaul (IAB) node, a device, a portable device, a wireless device, etc.

[0050] The technology proposed in this disclosure can be used in various wireless communication systems such as CDMA (code division multiple access), FDMA (frequency division multiple access), TDMA (time division multiple access), OFDMA (orthogonal frequency division multiple access), and SC-FDMA (single carrier frequency division multiple access). CDMA can be implemented with wireless technologies such as UTRA (universal terrestrial radio access) or CDMA2000. TDMA can be implemented with wireless technologies such as GSM (global system for mobile communications), GPRS (general packet radio service), and EDGE (enhanced data rates for GSM evolution). OFDMA can be implemented with wireless technologies such as IEEE (institute of electrical and electronics engineers) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, E-UTRA (evolved UTRA), LTE (long term evolution), and 5G NR.

[0051] The technology proposed in this disclosure can be implemented as 6G wireless technology and can be applied to various 6G systems. For example, 6G systems may have key factors such as eMBB (enhanced mobile broadband), URLLC (ultra-reliable low latency communications), mMTC (massive machine-type communication), AI (artificial intelligence) integrated communication, tactile internet, high throughput, high network capacity, high energy efficiency, low backhaul and access network congestion, and enhanced data security.

[0052] FIG. 1 illustrates a communication procedure between devices according to one embodiment of the present disclosure. The embodiment of FIG. 1 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, suggestions, methods, and / or operations of the embodiments may be omitted.

[0053] Referring to FIG. 1, in step S101, the first device and the second device can perform synchronization. For example, the first device may be a terminal and / or at least one of the devices proposed in the present disclosure. For example, the second device may be a base station, a network, a RAN node, an NTN node / cell, a TRP, a terminal and / or at least one of the devices proposed in the present disclosure. For example, the first device may perform an initial cell search operation. For example, the first device may detect at least one synchronization signal transmitted according to a rule predefined by the second device. Here, for example, the synchronization signal may include a plurality of synchronization signals (e.g., primary synchronization signal, secondary synchronization signal, etc.) classified according to structure or use. Through this, the first device can identify the boundaries of the frame, subframe, time unit, slot, and / or symbol of the second device, and the first device can obtain information about the second device (e.g., cell identifier).

[0054] In step S103, the first device may obtain system information transmitted by the second device. For example, the system information may include information related to the attributes, characteristics, and / or capabilities of the second device that are necessary to connect to the second device and use the service. For example, the system information may be classified according to content (e.g., whether it is essential for connection), transmission structure (e.g., the channel used, whether it is provided on-demand), etc. For example, the system information may be classified into a master information block (MIB) and a system information block (SIB). For example, if necessary, the first device may transmit a signal requesting the system information prior to receiving the system information. For example, the request and provision of the system information may be performed after a random access procedure described later.

[0055] In step S105, the first device and the second device may perform a random access procedure. For example, the first device may transmit and / or receive at least one message for the random access procedure (e.g., random access preamble, random access response message, etc.) based on information related to the random access channel of the second device obtained through system information (e.g., channel location, channel structure, structure of supported preamble, etc.). For example, the first device may transmit a preamble (e.g., Msg1) through the random access channel, and the first device may receive a random access response message (e.g., Msg2). The first device may transmit a message (e.g., Msg3) containing information related to the first device (e.g., identification information) to the second device using scheduling information included in the random access response message, and the first device may receive a message (e.g., Msg4) for contention resolution and / or connection establishment. For example, Msg1 and Msg3 can be transmitted and received as a single message (e.g., MsgA), and / or Msg2 and Msg4 can be transmitted and received as a single message (e.g., MsgB).

[0056] In step S107, the first device and the second device may perform signaling of control information. Here, for example, the control information may be defined in various layers, such as a layer controlling the connection (e.g., a radio resource control (RRC) layer), a layer handling mapping between a logical channel and a transmission channel (e.g., a media access control (MAC) layer), and a layer handling a physical channel (e.g., a physical (PHY) layer). For example, the first device and the second device may perform at least one of signaling to establish a connection, signaling to determine settings related to communication, and / or signaling to indicate allocated resources. For example, the control information may be signaled / transmitted through a control channel. For example, the control information and / or the control channel may be used to schedule at least one of data, a data channel (e.g., a shared channel), and / or control information on the data channel.

[0057] In step S109, the first device and the second device may transmit and / or receive data. For example, the first device and the second device may process data based on signaling of control information and transmit and / or receive it. For example, when transmitting data, the first device or the second device may perform at least one of channel encoding, rate matching, scrambling, constellation mapping, layer mapping, waveform modulation, antenna mapping, and / or resource mapping on the information bits. For example, when receiving data, the first device or the second device may perform at least one of signal extraction from resources, antenna-specific waveform demodulation, signal placement considering layer mapping, constellation demapping, descrambling, and / or channel decoding.

[0058] For example, the layers of the radio interface protocol between the first device and the second device can be classified into L1 (layer 1), L2 (layer 2), L3 (layer 3), etc. For example, the physical layer belonging to layer 1 can provide an information transfer service using a physical channel, and the radio resource control (RRC) layer located at layer 3 can perform the role of controlling radio resources between the first device and the second device. To this end, for example, the RRC layer can exchange RRC messages between the first device and the second device.

[0059] FIG. 2 illustrates a radio protocol architecture according to one embodiment of the present disclosure. The embodiment of FIG. 2 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of said embodiment may be omitted. For example, FIG. 2(a) may represent a radio protocol stack in the user plane for uplink communication or downlink communication, and FIG. 2(b) may represent a radio protocol stack in the control plane for uplink communication or downlink communication. For example, FIG. 2(c) may represent a radio protocol stack in the user plane for device-to-device communication, and FIG. 2(d) may represent a radio protocol stack in the control plane for device-to-device communication.

[0060] For example, the physical layer can provide information transmission services to upper layers using a physical channel. For example, the physical layer can be connected to the upper layer, the MAC (medium access control) layer, through a transport channel. For example, data can be transmitted between the MAC layer and the physical layer through a transport channel. For example, transport channels can be classified according to how and with what characteristics data is transmitted through a wireless interface. For example, data can be transmitted through a physical channel between different physical layers, for example, between the physical layers of a first device and a second device. For example, the physical channel can be modulated using the OFDM (orthogonal frequency division multiplexing) method, and time and frequency can be utilized as wireless resources.

[0061] For example, the MAC layer can provide services to the upper layer, the RLC (radio link control) layer, through logical channels. For example, the MAC layer can provide mapping functions from multiple logical channels to multiple transmission channels. For example, the MAC layer can provide logical channel multiplexing functions through mapping from multiple logical channels to a single transmission channel. For example, the MAC sublayer can provide data transmission services over logical channels.

[0062] For example, the RLC layer can perform concatenation, segmentation, and reassembly of RLC service data units (SDUs). For example, to guarantee various quality of service (QoS) required by a radio bearer (RB), the RLC layer can provide three modes of operation: transparent mode (TM), unacknowledged mode (UM), and acknowledged mode (AM). For example, AM RLC can provide error correction through automatic repeat requests (ARQ).

[0063] For example, the RRC (radio resource control) layer may be defined only in the control plane. For example, the RRC layer may be responsible for controlling logical channels, transmission channels, and physical channels in relation to the configuration, reconfiguration, and release of radio bearers. For example, RB may refer to a logical path provided by the first layer (e.g., physical layer) and the second layer (e.g., MAC layer, RLC layer, PDCP (packet data convergence protocol) layer, SDAP (service data adaptation protocol) layer, etc.) for data transfer between a first device and a second device.

[0064] For example, the functions of the PDCP layer in the user plane may include the delivery of user data, header compression, and ciphering. For example, the functions of the PDCP layer in the control plane may include the delivery of control plane data and encryption / integrity protection.

[0065] For example, the establishment of an RB can mean the process of defining the characteristics of the wireless protocol layer and channel to provide specific services, and setting each specific parameter and method of operation. For example, an RB can be divided into two types: an SRB (signaling radio bearer) and a DRB (data radio bearer). For example, an SRB can be used as a channel to transmit RRC messages in the control plane, and a DRB can be used as a channel to transmit user data in the user plane.

[0066] For example, if an RRC connection is established between the RRC layer of the terminal and the RRC layer of the base station, the terminal is in the RRC_CONNECTED state, and if not, it may be in the RRC_IDLE state. For example, in the case of NR, an additional RRC_INACTIVE state is defined, and a terminal in the RRC_INACTIVE state maintains a connection with the core network while releasing the connection with the base station.

[0067] For example, a downlink transmission channel may include at least one of a broadcast channel (BCH) that transmits system information and / or a shared channel (SCH) that transmits user traffic or control messages. For example, traffic or control messages for a downlink multicast or broadcast service may be transmitted via a downlink SCH or via a separate multicast channel (MCH). Meanwhile, an uplink transmission channel may include at least one of a random access channel (RACH) that transmits initial control messages and / or a shared channel (SCH) that transmits user traffic or control messages. For example, a logical channel located above the transmission channel and mapped to the transmission channel may include at least one of a broadcast control channel (BCCH), a paging control channel (PCCH), a common control channel (CCCH), a multicast control channel (MCCH), and / or a multicast traffic channel (MTCH).

[0068] FIG. 3 shows the structure of a wireless frame according to one embodiment of the present disclosure. The embodiment of FIG. 3 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.

[0069] Referring to FIG. 3, radio frames may be used, for example, in uplink transmission, downlink transmission, and / or device-to-device transmission. For example, a radio frame may have a length of 10 ms and may be defined as two 5 ms half-frames (HF). For example, a half-frame may contain five 1 ms subframes (SF). For example, a subframe may be divided into one or more slots, and the number of slots within a subframe may be determined by subcarrier spacing (SCS). For example, each slot may contain 12 or 14 OFDM(A) symbols according to a cyclic prefix (CP).

[0070] For example, when normal CP is used, each slot may contain 14 symbols. For example, when extended CP is used, each slot may contain 12 symbols. Here, for example, the symbols may include OFDM symbols (or CP-OFDM symbols) and SC-FDMA (single carrier-FDMA) symbols (or DFT-s-OFDM (Discrete Fourier Transform-spread-OFDM) symbols).

[0071] Table 2 below shows the number of symbols per slot (N) according to the SCS setting (u) when Normal CP or Extended CP is used. slot symb ), number of slots per frame (N frame,u slot ) and the number of slots per subframe (N subframe,u slot ) exemplifies.

[0072] CP Type SCS (15*2 u )N slot symb N frame,u slot N subframe,u slotNormal CP 15kHz (u=0) 1410 130kHz (u=1) 1420 260kHz (u=2) 1440 4120kHz (u=3) 1480 8240kHz (u=4) 14160 16 Extended CP 60kHz (u=2) 1240 4

[0073] For example, OFDM(A) numerology (e.g., SCS, CP length, etc.) may be configured differently among multiple cells merged into a single terminal. Accordingly, the (absolute time) interval of a time resource (e.g., subframe, slot, or TTI (transmit time interval)) composed of the same number of symbols may be configured differently among the merged cells. For example, in the present disclosure, time resources such as subframes, slots, TTI, etc. may be referred to as time units.

[0074] For example, multiple numerologies or SCSs may be supported to support various services. For example, if the SCS is 15 kHz, a wide area in traditional cellular bands may be supported, and if the SCS is 30 kHz / 60 kHz, dense-urban, lower latency, and wider carrier bandwidth may be supported. For example, if the SCS is 60 kHz or higher, a bandwidth greater than 24.25 GHz may be supported to overcome phase noise.

[0075] FIG. 4 shows a slot structure of a frame according to one embodiment of the present disclosure. The embodiment of FIG. 4 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, suggestions, methods, and / or operations of the embodiments may be omitted.

[0076] Referring to FIG. 4, for example, a slot may include multiple symbols in the time domain. For example, a carrier may include multiple subcarriers in the frequency domain. For example, a resource block (RB) may be defined as multiple consecutive subcarriers in the frequency domain. For example, a bandwidth part (BWP) may be defined as multiple consecutive (P)RBs ((physical) resource blocks) in the frequency domain and may correspond to a single numerology (e.g., SCS, CP length, etc.). For example, a carrier may include up to N BWPs (where N is a positive integer). For example, data communication may be performed through an active BWP. For example, each element may be referred to as a resource element (RE) in a resource grid and may be mapped to a single complex symbol.

[0077] For example, a BWP can be a continuous set of PRBs in a given numerology. For example, a PRB can be selected from a continuous subset of common resource blocks (CRBs) for a given numerology on a given carrier.

[0078] For example, the BWP may be at least one of an active BWP, an initial BWP, and / or a default BWP. For example, the terminal may not monitor downlink radio link quality on DL BWPs other than the active DL BWP on the PCell (primary cell). For example, the terminal may not receive PDCCH (physical downlink control channel), PDSCH (physical downlink shared channel), or CSI-RS (channel state information-reference signal) (except for RRM (radio resource management)) outside of the active DL BWP. For example, the terminal may not trigger CSI (channel state information) reporting for an inactive DL BWP. For example, the terminal may not transmit PUCCH (physical uplink control channel) or PUSCH (physical uplink shared channel) outside of the active UL (uplink) BWP. For example, for the downlink, the initial BWP can be given as a consecutive set of resource blocks (RBs) for the remaining minimum system information (RMSI) CORESET (control resource set) (set by the physical broadcast channel (PBCH)). For example, for the uplink, the initial BWP can be given by the system information block (SIB) for the random access procedure. For example, the default BWP can be set by the upper layer. For example, the initial value of the default BWP can be the initial DL BWP.For energy saving, if the terminal fails to detect DCI (downlink control information) for a certain period, the terminal can switch the active BWP of the terminal to the default BWP.

[0079] FIG. 5 illustrates an example of a BWP according to an embodiment of the present disclosure. The embodiment of FIG. 5 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted. In the embodiment of FIG. 5, it is assumed that there are three BWPs.

[0080] Referring to FIG. 5, for example, a common resource block (CRB) may be a numbered carrier resource block from one end of the carrier band to the other, and a PRB may be a numbered resource block within each BWP. For example, point A may indicate a common reference point for the resource block grid.

[0081] For example, BWP is point A, offset from point A (N start BWP ) and bandwidth (N size BWP It can be set by ). For example, point A may be an external reference point of the PRB of a carrier where the subcarrier 0 of all numerologies (e.g., all numerologies supported by the network in that carrier) are aligned. For example, offset may be the PRB interval between the lowest subcarrier in a given numerology and point A. For example, bandwidth may be the number of PRBs in a given numerology.

[0082] FIG. 6 illustrates a communication structure that can be provided in a 6G system according to one embodiment of the present disclosure. The embodiment of FIG. 6 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of said embodiments may be omitted.

[0083] As core implementation technologies for 6G systems, technologies such as artificial intelligence (AI), THz (Terahertz) communication, optical wireless technology, free space optical transmission (FSO) backhaul networks, massive MIMO (multiple input multiple output) technology, blockchain, 3D networking, quantum communication, unmanned aerial vehicles, cell-free communication, wireless information and energy transfer (WIET), integration of sensing and communication, integration of access backhaul networks, holographic beamforming, big data analysis, and large intelligent surface (LIS) can be adopted.

[0084] - Artificial Intelligence: Introducing AI into communications can streamline and enhance real-time data transmission. AI can determine how complex target tasks are performed using numerous analyses. For example, AI can increase efficiency and reduce processing latency. Time-consuming tasks such as handover, network selection, and resource scheduling can be performed instantly using AI. AI can also play a significant role in M2M, machine-to-human, and human-to-machine communication. Furthermore, AI can enable rapid communication in Brain-Computer Interfaces (BCI). AI-based communication systems can be supported by metamaterials, intelligent structures, intelligent networks, intelligent devices, intelligent cognitive radios, self-sustaining wireless networks, and machine learning.

[0085] - THz Communication: Data transmission rates can be increased by expanding bandwidth. This can be achieved by using sub-THz communication with wide bandwidth and applying advanced large-scale MIMO technology. THz waves, also known as sub-millimeter radiation, generally refer to a frequency band between 0.1 THz and 10 THz with corresponding wavelengths ranging from 0.03 mm to 3 mm. The 100 GHz-300 GHz band range (Sub-THz band) is considered the primary portion of the THz band for cellular communication. Adding the Sub-THz band to the mmWave band increases 6G cellular communication capacity. Among the defined THz bands, the 300 GHz-3 THz band is located in the far-infrared (IR) frequency band. Although the 300 GHz-3 THz band is part of the optical band, it lies at the boundary of the optical band and immediately following the RF band. Therefore, this 300 GHz-3 THz band exhibits similarities to RF. Key characteristics of THz communication include (i) widely available bandwidth to support very high data transmission rates, and (ii) high path loss occurring at high frequencies (highly directional antennas are indispensable). The narrow beam width generated by highly directional antennas reduces interference. The small wavelength of THz signals allows a much larger number of antenna elements to be integrated into devices and BSs operating in this band. This enables the use of advanced adaptive array technologies that can overcome range limitations.

[0086] - Large-scale MIMO technology

[0087] - Hologram beamforming (HBF)

[0088] - Optical wireless technology

[0089] - Free Space Optical Transmission Backhaul Network (FSO backhaul network)

[0090] - Quantum communication

[0091] - Cell-free communication

[0092] - Integration of wireless information and power transmission

[0093] - Integration of wireless communication and sensing

[0094] - Integrated access and backhaul network

[0095] - Big data analysis

[0096] - Reconfigurable intelligent metasurface

[0097] - Metaverse

[0098] - blockchain

[0099] - Advanced Air Mobility (AAM): AAM can be a broad concept encompassing Urban Air Mobility (UAM), Regional Air Mobility (RAM), and Uncrewed Aerial Systems (UAS). For example, AAM may include UAM, RAM, UAS, and UAVs (uncrewed aerial vehicles).

[0100] - Autonomous driving (self-driving): V2X (vehicle to everything), a core element of building autonomous driving infrastructure, refers to technologies that enable vehicles to communicate and share with various elements on the road to perform autonomous driving, such as wireless communication between vehicles (vehicle to vehicle, V2V) and between vehicles and infrastructure (vehicle to infrastructure, V2I).

[0101] - Non-terrestrial Network (NTN): An NTN may refer to a network or network segment that utilizes RF (radio frequency) resources mounted on a satellite (or UAS platform). The use of NTN services may be considered to secure wider coverage or to provide wireless communication services in locations where the installation of wireless communication base stations is difficult.

[0102] - Integrated Sensing and Communication (ISAC): Wireless sensing is a technology that uses radio frequencies to determine the instantaneous linear velocity, angle, distance (range), etc., of an object, thereby obtaining information about the characteristics of the environment and / or objects within the environment.

[0103] - Reconfigurable Intelligent Surface (RIS): An RIS can be used to manipulate and enhance signal propagation in a wireless communication environment. For example, an RIS can be composed of many small antennas or metasurfaces arranged on a surface, each of which can actively control the phase, amplitude, polarization, etc., of the reflected signal. For instance, an RIS can improve signal reception by controlling the path, phase, and / or strength of the propagating signal. For instance, power consumption can be very low because power is consumed only for controlling the phase and amplitude of the small antennas. For instance, since an RIS can be reconfigured to suit various environments, it can meet diverse communication requirements and operate effectively in dynamic network environments.

[0104] FIG. 7 illustrates an example of a communication scenario based on a 6G system according to an embodiment of the present disclosure. The embodiment of FIG. 7 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.

[0105] Referring to FIG. 7, NTN communication can be performed based on a satellite network, HIBS (high-altitude platform stations (HAPS) as international mobile telecommunications (IMT) base stations (BS)), and an aeronautical communication-capable terminal (e.g., AAM). For example, to improve coverage, devices such as a satellite network, HIBS, and an aeronautical communication-capable terminal (e.g., AAM) can act as relays. For example, an AAM can communicate with a base station, a satellite network, etc., and / or an AAM can communicate directly with a terminal, another AAM, etc.

[0106] FIG. 8 illustrates a non-terrestrial network scenario according to one embodiment of the present disclosure. FIG. 9 illustrates a non-terrestrial network scenario according to one embodiment of the present disclosure. The embodiments of FIG. 8 and FIG. 9 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.

[0107] FIG. 8 illustrates a non-terrestrial network scenario based on a transparent payload, and FIG. 9 illustrates a non-terrestrial network scenario based on a regenerative payload. For example, a non-terrestrial network may generally include the following elements.

[0108] - One or more satellite gateways connecting non-terrestrial networks to public data networks

[0109] - Feeder link or wireless link between the satellite gateway and the satellite (or UAS platform)

[0110] - Service link or wireless link between user equipment and satellite (or UAS platform)

[0111] - A satellite (or UAS platform) capable of implementing transparent or regenerated (including onboard processing) payloads. For example, the satellite (or UAS platform) can generate multiple beams across a given service area, typically defined by a line of sight. For example, the beam footprint may typically be elliptical. For example, the line of sight of the satellite (or UAS platform) may vary depending on the onboard antenna diagram and the minimum elevation angle. For example, for a transparent payload, radio frequency filtering, frequency conversion, and amplification may be performed. Thus, the repeating waveform signal in the payload may not be altered. For example, for a regenerated payload, radio frequency filtering, frequency conversion, and amplification, as well as demodulation / decoding, switching and / or routing, and coding / modulation may be performed. This can effectively be equivalent to equipping the satellite (or UAS platform) with all base station functions.

[0112] - Optionally, Inter-satellite Link (ISL)

[0113] - User equipment can be serviced by a satellite (or UAS platform) within the target service area.

[0114] FIG. 10 illustrates examples of an NTN access network according to one embodiment of the present disclosure. FIG. 10(a) illustrates an example of a transparent payload according to one embodiment of the present disclosure. FIG. 10(b) illustrates an example of a regenerated payload according to one embodiment of the present disclosure. An embodiment of FIG. 10 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of said embodiments may be omitted.

[0115] Referring to FIG. 10(a), for example, the satellite / HAPS can perform only the role of a simple repeater, receive uplink signals from the UE and transmit them to the Gateway, and relay downlink signals generated at the Gateway back to the UE. Here, for example, communication between the UE and the satellite can use NR radio frequency f1, and communication between the satellite and the Gateway can use NR radio frequency f2. For example, the actual 5G radio access network (e.g., 5G RAN) function is deployed at the Gateway or ground base station (e.g., gNB) located on the ground and can be coupled with the 5G core network (e.g., 5G CN). Thus, for example, the satellite can operate as a simple transponder structure that transparently transmits signals at the physical layer level without performing separate signal processing functions. For example, the transparent payload of FIG. 10(a) may be related to the transparent payload of FIG. 8. For example, the transparent payload of Fig. 10(a) may be related to the NTN architecture discussed in 3GPP Rel-17 and Rel-18.

[0116] Referring to FIG. 10(b), for example, the satellite / HAPS itself may be equipped with 5G RAN functions and may possess payload processing capabilities that include base station functions, rather than being a simple repeater. For example, communication between the UE and the satellite may use NR radio frequency f1, and communication between the satellite and the gateway may use NR radio frequency f2. Here, for example, the gateway is connected to a 5G core network (e.g., 5G CN), and since the satellite can directly provide RAN functions to the UE, it can replace or supplement a ground base station (e.g., gNB). For example, since the satellite has a structure that transmits NR signals after receiving, demodulating, and processing them, rather than simply relaying them, more intelligent wireless resource control and quality of service management are possible. For example, the regeneration payload in FIG. 10(b) may be related to the regeneration payload in FIG. 9. For example, the replay payload of Fig. 10 (b) may be related to the NTN architecture that can be discussed in 3GPP Rel-19 and thereafter.

[0117] FIG. 11 illustrates an example of possible options for an NTN architecture according to one embodiment of the present disclosure. The embodiment of FIG. 11 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of said embodiment may be omitted.

[0118] Referring to FIG. 11, an NTN may be disclosed that features an access network servicing UEs based, for example, a ground-based gNB (satellite hub or gateway level) and a satellite / aerial carrying a bent pipe payload. In FIG. 11, for example, the satellite or aerial may relay “satellite-friendly” NR signals between the gNB and the UEs in a transparent manner. For example, the UE may communicate with the satellite via a radio interface (e.g., Uu), and the satellite may transmit the signal to a ground base station (e.g., gNB). For example, the gNB may perform the role of a 5G radio access network (e.g., RAN) and may be connected to a 5G / 6G core (e.g., 5GC / 6GC) via an NG interface (e.g., NGc, NGu). For example, 5GC / 6GC can be connected to an external data network through the N6 interface. Therefore, for example, in this structure, a satellite can extend the wireless section to mediate the connection between the UE and the ground base station, and subsequent procedures can operate in the same way as the existing 5G structure. For example, the NTN architecture of FIG. 11 can be related to the transparent payload of FIG. 10 (a).

[0119] FIG. 12 illustrates an example of possible options for an NTN architecture according to one embodiment of the present disclosure. The embodiment of FIG. 12 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of said embodiment may be omitted.

[0120] Referring to FIG. 12, an NTN may be disclosed that features an access network for servicing UEs based on, for example, a satellite / aerial equipped with a gNB. In FIG. 12, for example, the satellite or aerial may include all or part of a gNB for generating / receiving “satellite-friendly” NR signals for transmitting and receiving with UEs. For example, this may require sufficient on-board processing power to deploy gNB or relay node functions. For example, a UE may communicate with the satellite via a radio interface (e.g., Uu), and the satellite may transmit the signal to a ground base station (e.g., gNB). For example, the gNB can perform the role of a 5G wireless access network (e.g., RAN) and can be connected to a 5G / 6G core (e.g., 5GC / 6GC) via an NG interface (e.g., NGc, NGu). For example, the 5GC / 6GC can be connected to an external data network via an N6 interface. Thus, for example, in this structure, a satellite can extend the wireless section to mediate the connection between the UE and the ground base station, and subsequent procedures can operate in the same way as the existing 5G structure. For example, the NTN architecture of FIG. 12 can be related to the replay payload of FIG. 10 (b).

[0121] FIG. 13 illustrates a procedure for downlink transmission and reception according to one embodiment of the present disclosure. The embodiment of FIG. 13 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.

[0122] Referring to FIG. 13, for example, in step S1310, the base station can schedule downlink transmissions such as frequency / time resources, a transport layer, a downlink precoder, an MCS, etc. For example, the base station can determine a beam for the terminal's PDSCH transmission through the operations described above.

[0123] For example, in step S1320, the terminal can receive downlink control information (DCI: Downlink Control Information) for downlink scheduling (e.g., including scheduling information of the PDSCH) from the base station on the PDCCH.

[0124] For example, DCI format 1_0 or 1_1 may be used for downlink scheduling, and in particular, DCI format 1_1 may include the following information: Identifier for DCI formats, Bandwidth part indicator, Frequency domain resource assignment, Time domain resource assignment, PRB bundling size indicator, Rate matching indicator, ZP CSI-RS trigger, Antenna port(s), Transmission configuration indication (TCI), SRS request, DMRS (Demodulation Reference Signal) sequence initialization

[0125] For example, the number of DMRS ports can be scheduled according to each state indicated in the antenna port(s) field, and SU (Single-user) / MU (Multi-user) transmission scheduling can also be performed.

[0126] For example, the TCI field consists of 3 bits, and the QCL for the DMRS can be dynamically indicated by indicating up to 8 TCI states depending on the TCI field value.

[0127] For example, in step S1330, the terminal can receive downlink data from the base station on the PDSCH.

[0128] For example, if the terminal detects a PDCCH containing DCI format 1_0 or 1_1, it can decode the PDCCH according to instructions from the corresponding DCI.

[0129] For example, when a terminal receives a PDSCH scheduled by DCI format 1, the terminal may have a DMRS configuration type set by the upper layer parameter 'dmrs-Type', and the DMRS type may be used to receive the PDSCH. For example, the terminal may have a maximum number of front-loaded DMRA symbols for the PDSCH set by the upper layer parameter 'maxLength'.

[0130] For example, in the case of DMRS configuration type 1, if a terminal is scheduled with a single codeword and an antenna port mapped to an index of {2, 9, 10, 11 or 30} is assigned, or if a terminal is scheduled with two codewords, the terminal can assume that all remaining orthogonal antenna ports are not associated with PDSCH transmission to another terminal.

[0131] For example, in the case of DMRS configuration type 2, if a terminal is scheduled with a single codeword and an antenna port mapped to an index of {2, 10, or 23} is assigned, or if a terminal is scheduled with two codewords, the terminal can assume that all remaining orthogonal antenna ports are not associated with PDSCH transmission to another terminal.

[0132] For example, when a terminal receives PDSCH, the precoding granularity P' can be assumed to be a consecutive block of resources in the frequency domain. For example, P' can correspond to one of the values ​​{2, 4, broadband}.

[0133] For example, if P' is determined to be broadband, the terminal does not expect to be scheduled with non-contiguous PRBs, and the terminal can assume that the same precoding is applied to the allocated resources.

[0134] For example, if P' is determined to be either {2 or 4}, the Precoding Resource Block Group (PRG) can be divided into P' consecutive PRBs. For example, the actual number of consecutive PRBs within each PRG can be one or more. For example, the UE may assume that the same precoding is applied to consecutive downlink PRBs within the PRG.

[0135] For example, to determine the modulation order, target code rate, and transport block size within the PDSCH, the terminal can first read the 5-bit MCD field within the DCI and determine the modulation order and target code rate. Then, it can read the redundancy version field within the DCI and determine the redundancy version. Then, the terminal can determine the transport block size using the number of layers and the total number of allocated PRBs before rate matching.

[0136] FIG. 14 illustrates a procedure for uplink transmission and reception according to one embodiment of the present disclosure. The embodiment of FIG. 14 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.

[0137] Referring to FIG. 14, for example, in step S1410, the base station can schedule uplink transmissions such as frequency / time resources, transport layer, uplink precoder, MCS, etc. For example, the base station can determine a beam for the terminal's PUSCH transmission through the operations described above.

[0138] For example, in step S1420, the terminal may receive a DCI on the PDCCH for uplink scheduling (e.g., including scheduling information of the PUSCH) from the base station.

[0139] For example, DCI format 0_0 or 0_1 may be used for uplink scheduling, and in particular, DCI format 0_1 ​​may include the following information: DCI format identifier, UL / SUL (Supplementary uplink) indicator, Bandwidth part indicator, Frequency domain resource assignment, Time domain resource assignment, Frequency hopping flag, Modulation and coding scheme (MCS), SRS resource indicator (SRI), Precoding information and number of layers, Antenna port(s), SRS request, DMRS sequence initialization, UL-SCH (Uplink Shared Channel) indicator

[0140] For example, the SRS resource indicator field may indicate SRS resources configured within the SRS resource set associated with the upper-level parameter 'usage'. For instance, 'spatialRelationInfo' can be set for each SRS resource, and its value can be one of {CRI, SSB, SRI}.

[0141] For example, in step S1430, the terminal can transmit uplink data to the base station over PUSCH.

[0142] For example, if the terminal detects a PDCCH containing DCI format 0_0 or 0_1, it can transmit the corresponding PUSCH according to the instructions given by the DCI.

[0143] For example, two transmission methods (e.g., codebook-based transmission for PUSCH transmission and non-codebook-based transmission for PUSCH transmission) may be supported:

[0144] i) For example, when the upper layer parameter 'txConfig' is set to 'codebook', the terminal can be configured for codebook-based transmission. For example, when the upper layer parameter 'txConfig' is set to 'nonCodebook', the terminal can be configured for non-codebook-based transmission. For example, if the upper layer parameter 'txConfig' is not set, the terminal may not expect to be scheduled by DCI format 0_1. For example, if PUSCH is scheduled by DCI format 0_0, the PUSCH transmission may be based on a single antenna port.

[0145] For example, in the case of codebook-based transmission, PUSCH can be scheduled in DCI format 0_0, DCI format 0_1, or semi-statically. For example, if this PUSCH is scheduled by DCI format 0_1, the terminal can determine the PUSCH transmission precoder based on SRI, TPMI (transmit precoding matrix indicator), and transmission rank from the DCI, as given by the SRS resource indicator field and the precoding information and number of layers fields. For example, TPMI is used to indicate the precoder to be applied across the antenna port and may correspond to the SRS resource selected by SRI when multiple SRS resources are set. For example, when a single SRS resource is set, TPMI is used to indicate the precoder to be applied across the antenna port and may correspond to that single SRS resource. For example, a transmission precoder may be selected from an uplink codebook having the same number of antenna ports as the upper layer parameter 'nrofSRS-Ports'. For example, when the upper layer set to 'codebook' is set to the parameter 'txConfig', the terminal may have at least one SRS resource configured. For example, the SRI indicated in slot n is associated with the most recent transmission of the SRS resource identified by the SRI, where the SRS resource may precede the PDCCH (e.g., slot n) carrying the SRI.

[0146] ii) For example, in the case of non-codebook-based transmission, PUSCH may be scheduled in DCI format 0_0, DCI format 0_1, or semi-statically. For example, when multiple SRS resources are configured, the terminal may determine the PUSCH precoder and transmission rank based on a broadband SRI, where the SRI may be given by an SRS resource indicator within the DCI or by the upper layer parameter 'srs-ResourceIndicator'. For example, the terminal utilizes one or multiple SRS resources for SRS transmission, where the number of SRS resources may be configured for simultaneous transmission within the same RB based on UE capabilities. For example, only one SRS port may be configured per SRS resource. For example, only one SRS resource may be configured with the upper layer parameter 'usage' set to 'nonCodebook'. For example, the maximum number of SRS resources that can be set for non-codebook-based uplink transmissions may be 4. For example, the SRI indicated in slot n is associated with the most recent transmission of the SRS resource identified by the SRI, where the SRS transmission may precede the PDCCH (e.g., slot n) carrying the SRI.

[0147] FIG. 15 illustrates an example of NTN according to one embodiment of the present disclosure. The embodiment of FIG. 15 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.

[0148] Referring to Fig. 15, examples according to NTN platform types can be shown. For example, examples according to NTN platform types may be HAPS (High-Altitude Platform Station), LEO (Low Earth orbit), MEO (Medium Earth orbit), or GEO (Geo-stationary Earth orbit).

[0149] For example, parameters related to the HAPS (High-Altitude Platform Station) may be as follows. For example, the altitude of the HAPS (High-Altitude Platform Station) may be 20 km. For example, the beam footprint size of the HAPS (High-Altitude Platform Station) may be 5-200 km.

[0150] For example, parameters related to LEO (Low Earth orbit) may be as follows. For example, the altitude of LEO (Low Earth orbit) may be 300–1500 km. For example, the beam footprint size of LEO (Low Earth orbit) may be 100–1000 km. For example, the satellite velocity of LEO (Low Earth orbit) may be 7.56 km / sec (for LEO-600). For example, the maximum propagation delay of LEO (Low Earth orbit) may be 25.77 msec (for LEO-600).

[0151] For example, parameters related to MEO (Medium Earth orbit) may be as follows. For example, the altitude of MEO (Medium Earth orbit) may be 7,000–25,000 km. For example, the beam footprint size of MEO (Medium Earth orbit) may be 100–1,500 km. For example, the maximum propagation delay of MEO (Medium Earth orbit) may be 95.19 msec (for MEO-10000).

[0152] For example, parameters related to the GEO (Geo-stationary Earth orbit) may be as follows. For example, the altitude of the GEO (Geo-stationary Earth orbit) may be 35,786 km. For example, the beam footprint size of the GEO (Geo-stationary Earth orbit) may be 200-3,500 km. For example, the satellite velocity of the GEO (Geo-stationary Earth orbit) may be 3.1 km / sec (negligible). For example, the maximum propagation delay of the GEO (Geo-stationary Earth orbit) may be 541.46 msec.

[0153] For example, to effectively operate an NTN with a very long RTT, the scheduling offset is class This can be introduced.

[0154] FIG. 16 is according to one embodiment of the present disclosure, class Examples of are shown. The embodiment of FIG. 16 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, suggestions, methods, and / or operations of the embodiments may be omitted.

[0155] Referring to Fig. 16, for example, class Examples of can be presented. For example, service link RTT can be the RTT between the terminal and the satellite. For example, feeder link RTT can be the RTT between the satellite and the base station. For example, common TA can be the TA between the satellite and the RP. For example, can be an offset value representing the RTT of the uplink time synchronization reference point (RP). For example, can mean the sum of the service link RTT and the common TA (if indicated). For example, may be an offset value representing the RTT between the RP and the gNB. For example, the feeder link RTT is the common TA (if indicated) and It can mean the sum of.

[0156] FIG. 17 illustrates examples of UE-specific TA and common TA according to one embodiment of the present disclosure. The embodiment of FIG. 17 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, suggestions, methods, and / or operations of the embodiments may be omitted.

[0157] Referring to FIG. 17, terminal-specific TA can be acquired to compensate for transmission delays on the service link, and common TA can be acquired to compensate for transmission delays between the RP (reference point) and the satellite.

[0158] For example, in an NTN-based communication system, a terminal can calculate a TA based on the terminal's GNSS (global navigation satellite system) capabilities (e.g., terminal location) and orbit-related upper-layer parameters transmitted from the base station, and this is a terminal-specific TA ( It can be referred to as ). For example, if orbit-related upper-layer parameters are not received from the base station, the terminal-specific TA may be set to 0. For example, common TA parameters, which are upper-layer parameters transmitted from the base station (e.g., , , and / or TA obtained based on ) common TA( It can be referred to as ). For example, if common TA parameters are not transmitted from the base station, the common TA can be set to 0. Accordingly, for example, in an NTN-based communication system, the total TA value (TTA) is “ It can be obtained as ”. For example, can refer to the TA offset value provided to the terminal per serving cell, and can mean a value obtained based on the timing advance command.

[0159] Referring to FIG. 17, for example, in Rel-17 NTN, the terminal can calculate the TA itself based on the terminal's GNSS capability and base station guidance information (e.g., ephemeris information), which can be designated as a terminal-specific (UE-specific) TA. For example, a TA calculated based on common TA parameters indicated by the base station can be designated as a common TA, and the final TA based thereon can be based on FIG. 18 and the description related to FIG. 18.

[0160] FIG. 18 illustrates an example of an uplink-downlink timing relationship according to one embodiment of the present disclosure. The embodiment of FIG. 18 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, suggestions, methods, and / or operations of the embodiments may be omitted.

[0161] Referring to FIG. 18, the uplink frame number i for the transmission from the UE is before the start of the corresponding downlink frame from the UE You can start here

[0162] - and ...can be given in Section 4.2 of TS 38.213, and This may be excluded for msgA transmissions on PUSCH that are to be used;

[0163] - It can be derived from the upper-level parameters ta-Common, ta-CommonDrift, and ta-CommonDriftVariant if indicated, and otherwise It could be;

[0164] - is calculated by the UE based on UE position and serving-satellite-orbit-related upper-layer parameters if indicated, and otherwise It could be.

[0165] For example, there may be TA misalignment.

[0166] For example, in NR NTN, a TA mismatch may occur if the gNB does not receive a TA report, if the existing TA report is outdated, or if the granularity of the TA report is insufficient. For example, if the UE does not perform any TA reporting, the gNB [uses] several key scheduling variables (e.g., , Since ) cannot be configured, the above scenario (e.g., no TA reporting) may not be considered a feasible scenario. Therefore, assuming that the UE performs TA reporting, the magnitude of TA mismatch caused by TA reporting obsolescence and / or TA reporting granularity may need to be addressed. For example, if the UE performs TA reporting on NR NTN, TA discrepancies may occur primarily due to outdated TA reporting and / or coarse TA reporting granularity. For example, to support HD-FDD (e)RedCap UE, issues regarding quantitative-level TA misalignment between the gNB and the UE may need to be addressed.

[0167] Meanwhile, differences resulting from outdated TA reporting may occur when the UE location changes, and may occur proportionally to RTT differences depending on the UE location within the cell (e.g., the difference between the minimum TA and the maximum TA).

[0168] FIG. 19 illustrates an example of TA mismatch within a beam / cell according to one embodiment of the present disclosure. The embodiment of FIG. 19 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, suggestions, methods, and / or operations of said embodiments may be omitted.

[0169] Referring to Fig. 19, for example, assuming an LEO of 600 km, a beam size of 50 km, and a target elevation angle of 30 degrees, the difference between the shortest RTT (minimum TA) and the longest RTT (maximum TA) can be within about 300 µs, which corresponds to about 4 to 5 OFDM symbols using a 15 kHz SCS.

[0170] For example, assuming an LEO of 600 km, a beam size of 50 km, and a target elevation angle of 30 degrees, the difference between the shortest RTT (minimum TA) and the longest RTT (maximum TA) is within approximately 300 µs, which corresponds to about 4 to 5 OFDM symbols with a 15 kHz SCS. For example, considering that the TA reported granularity of NTN is 1 ms (e.g., 14 OFDM symbols using a 15 kHz SCS), in the LEO example, the main cause of the TA discrepancy may be the TA reported granularity rather than the old TA reported. For example, for an LEO of 600 km, a beam size of 50 km, and a target elevation angle of 30 degrees, the difference between the minimum TA and the maximum TA may be smaller than the TA reported granularity (e.g., 1 ms). For example, in the case of HD-FDD (e)RedCap UE support, issues regarding the enhanced TA reporting mechanism, particularly TA reporting granularity, may need to be addressed.

[0171] For example, there may be a DL / UL collision under TA misalignment.

[0172] When comparing the timing advances of NTN and TN due to satellite movement, the timing advance of the service link between the satellite and the UE can be estimated by the UE itself. For example, the gNB can obtain the TA value through TA reporting, but due to the current 1ms granularity reported by the TA, the gNB cannot obtain the exact TA used by the UE, and the UE side cannot know when or which transmission will collide. For example, since the rule for when a DL reception collides with a UL transmission is intended to avoid collisions through gNB scheduling, the NTN gNB may experience difficulties in determining whether the UE is in an uplink slot or a downlink slot.

[0173] For example, the terminal may receive satellite orbit information through system information and / or RRC signaling. For example, satellite orbit information may be implemented / supported in a position and velocity state vector orbit format and / or an orbital parameter orbit format. For example, the position and velocity state vector orbit format may be composed of less than 17 bytes (e.g., 132 bits). For example, the field size for position (x, y, z)(m) may be 78 bits, and the field size for velocity (vx, vy, vz)(m / s) may be 54 bits. For example, the orbital parameter orbit format may be composed of less than 21 bytes (e.g., 164 bits).

[0174] FIG. 20 illustrates an example of an orbital parameter orbital format according to one embodiment of the present disclosure. The embodiment of FIG. 20 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, suggestions, methods, and / or operations of the embodiments may be omitted.

[0175] Referring to FIG. 20, information related to the orbital parameter orbit format (e.g., ephemeral information) includes the semi-major axis "α" (e.g., 33 bits) [m], the eccentricity "e" (in an elliptical satellite orbit, 0 <e<1) (예를 들어, 20 비트), 근점 편각(argument of periapsis) "ω"(예를 들어, 28 비트) [rad], 승교점 경도(longitude of ascending node) "Ω" (예를 들어, 28 비트) [rad], (궤도) 경사(inclination) "i" (예를 들어, 27 비트) [rad], 및 / 또는 평균 근점 이각(mean anomaly) "M0" = 에포크 t0 [JD]에서 M(t0) (예를 들어, 28 비트) [rad] 중 적어도 어느 하나를 포함할 수 있다.

[0176] Recently, active research has been conducted in the field of mobile communications on non-terrestrial (NTN) networks that utilize satellites, drones, and other devices as network nodes. For example, satellites in NTN can be broadly classified into GSO satellites, which possess geosynchronous orbits (GSO), and NGSO satellites, which do not possess geosynchronous orbits (Non-GSO, NGSO). Additionally, satellites can be classified into low earth orbit (LEO), medium earth orbit (MEO), and high earth orbit (HEO) based on their altitude. In the field of mobile communications, LEO-based NTN support methods, which offer relatively lower costs and higher data transmission rates, are primarily being researched. However, LEO satellites are NGSO satellites and are characterized by very high speeds required to maintain their orbits due to their proximity to the Earth's surface. Therefore, to provide services to ground terminals via LEO satellites, it is necessary to overcome Doppler shifts caused by high relative velocities and / or significant time delays associated with high altitudes.

[0177] Recently, active research has been conducted in the field of mobile communications on non-terrestrial (NTN) networks that utilize satellites, drones, and the like as network nodes. For example, satellites in NTN can be broadly classified into GSO satellites, which have a geosynchronous orbit (GSO), and NGSO satellites, which do not have a geosynchronous orbit (Non-GSO). Additionally, satellites can be classified into low earth orbit (LEO), medium earth orbit (MEO), and high earth orbit (HEO) depending on their altitude. In the field of mobile communications, LEO-based NTN support methods, which offer relatively lower costs and higher data transmission rates, are primarily being researched. Here, the aforementioned satellite-based non-terrestrial networks may possess channel characteristics such as large path attenuation and / or long time delay and / or large Doppler shift due to high altitude and / or high relative velocity.

[0178] Recently, the telecommunications sector has been actively discussing the introduction of non-terrestrial networks (NTNs) that utilize satellites as network nodes. Satellites supporting the aforementioned NTNs can be classified according to their flight orbits and characteristics, such as geostationary earth orbit (GEO), medium earth orbit (MEO), and low earth orbit (LEO), and generally possess the characteristic of being at very high altitudes. Consequently, the service area of ​​these satellites can have very wide coverage characteristics, and the number of target terminals within that service area may be relatively large. Therefore, the NTN service may require support for multiplexing for multiple terminal(s). Here, since ground terminals are constrained by transmission power, coverage extension technology may be applied to ensure that a signal of sufficient magnitude reaches the high-altitude NTN during uplink transmission. For example, a terminal can achieve coverage extension by repeating the physical uplink shared channel (PUSCH), which is the uplink data channel, over the time axis. Here, the terminal may transmit the PUSCH using the DFT-s-OFDM (discrete Fourier transform spread orthogonal frequency division multiplexing) method for coverage gain. Here, the DFT-s-OFDM modulation method may refer to a modulation method in which DFT precoding (or DFT spreading) is applied as part of TF (transform) precoding prior to OFDM modulation. Meanwhile, the efficiency of resource utilization may decrease due to repeated transmissions in the coverage extension technology, and an uplink multiplexing method using OCC (orthogonal cover code) may be effective.Here, the OCC may refer to an OCC applied in the time axis and / or frequency axis for uplink transmission. Here, in order to maintain orthogonality between different OCCs, it must be assumed that there is minimal change in the channel within the time and / or frequency interval where the OCC is applied. Here, for a terminal receiving NTN-based services, problems such as Doppler shift due to high relative speeds between the satellite and the terminal and / or time delay due to long communication distances between the satellite and the terminal may be exacerbated compared to conventional terrestrial network (TN)-based communication. Therefore, to achieve OCC-based uplink multiplexing and / or capacity enhancement in the NTN, it must be possible to verify whether uplink transmission between the base station and / or the terminal is suitable for applying OCC. For example, the base station may require the terminal to achieve time axis and / or frequency axis synchronization accuracy within a certain level during OCC-based uplink transmission. For example, a base station may apply OCC only in cases where the terminal can pre-compensate for Doppler shift, etc., within a certain error level by utilizing satellite orbit information, etc. Hereinafter, the present disclosure may propose a pre-compensation-based uplink transmission method in NTN and an apparatus supporting the same.

[0179] In non-terrestrial networks (NTN) or long-cycle downlink synchronization environments, the following problems may exist.

[0180] - Problem of extending the SSB transmission cycle

[0181] In an NTN environment, due to satellite EIRP constraints and multiple cell / beam simultaneous service issues, the downlink transmission period of a conventional synchronization signal block (SSB) can increase from 20 ms to 160 ms or more.

[0182] In this case, the UE must perform long-term monitoring to detect the synchronization signal, and considering the number of repeated detections required by the standard, the synchronization acquisition delay and power consumption may increase excessively.

[0183] - Problem of increasing frequency search complexity

[0184] In the conventional method, the terminal must search for the synchronization signal block across the entire dense first sync raster, so the search complexity can increase rapidly.

[0185] - Inefficiency caused by the combination of synchronization-only signals and system information signals

[0186] Since conventional SSBs include PSS / SSS and PBCH together, the terminal may bear the burden of receiving unnecessary system information even for pure synchronization purposes.

[0187] In non-terrestrial networks (NTN) or long-cycle downlink synchronization environments, the following problems may also exist.

[0188] - Problem of unnecessary continuous monitoring in conventional synchronization signal blocks

[0189] Even after the terminal has already obtained rough synchronization through a simplified synchronization signal block, there may be inefficiency in the conventional method where the first synchronization signal block (SSB) must always be monitored periodically.

[0190] - Continued terminal burden due to conventional SSB monitoring

[0191] Since the first synchronization signal block includes a PBCH, the terminal may still have a high complexity of monitoring and decoding burden.

[0192] The proposed method(s) of the present disclosure are described below with non-terrestrial networks as embodiments, but the proposed method(s) of the present disclosure can be extended and applied to terrestrial networks as well.

[0193] [Proposed Plan #01] When there may be (pre)requirement(s) to support (a specific type) uplink transmission between a base station and a terminal, as one type of said (pre)requirement(s), (pre)requirement(s) for time synchronization error and / or Doppler shift line-compensation (at the terminal end) may be defined in a form including one or more of the following:

[0194] (1) Allowable (maximum) time axis and / or frequency axis synchronization error (range) (per slot / symbol)

[0195] (2) Allowable (maximum) time axis and / or frequency axis synchronization error (range) (based on the start time of transmission)

[0196] (3) (Maximum) rate of change of time axis and / or frequency axis synchronization error (during transmission)

[0197] A. For example, it may be a time drift rate and / or a Doppler drift rate, etc.

[0198] Here, for example, the above (specific type) uplink transmission may refer to an uplink transmission with an orthogonal cover code (OCC) applied (in the time axis and / or frequency axis). For example, when transmitting an uplink with the above OCC applied between a base station and a terminal, (pre) requirements for time delay and / or Doppler shift line-compensation (at the terminal end) may be met.

[0199] Here, for example, the above (pre)requirement(s) may be (pre)requirement(s) for a specific type of terminal. For example, they may be (pre)requirement(s) for an NTN service terminal.

[0200] For example, let us assume that in a next-generation mobile communication system based on a non-terrestrial network according to an embodiment of the present disclosure, a terminal transmits an uplink data channel (e.g., PUSCH). For example, the non-terrestrial network may consist of a terminal, a satellite, and a base station, and the terminal and the satellite may be connected by a service link, and the satellite and the base station may be connected by a feeder link. Here, for example, due to the long distance and high relative speed between the terminal and the satellite, time-axis and / or frequency-axis synchronization errors may occur in the service link, etc. For example, time-axis synchronization errors and / or Doppler shifts may occur. Here, for example, time-axis and / or frequency-axis synchronization errors (within a certain level) may be required during uplink transmission (of a specific type) between the base station and the terminal.

[0201] Here, for example, in order to achieve time-axis and / or frequency-axis synchronization errors (within a certain level) during uplink transmission (of a specific type), requirement(s) for time synchronization error and / or Doppler shift line-compensation (at the terminal end) may be defined. For example, when a base station intends to set / instruct a terminal to perform uplink transmission with applied OCC (time-axis and / or frequency-axis) for purposes such as uplink multiplexing and / or capacity enhancement, requirement(s) for time synchronization error and / or Doppler shift line-compensation (at the terminal end) to maintain orthogonality between said OCC(s) may be defined. Here, for example, said requirement(s) may be defined in a form including one or more of the following.

[0202] (1) Allowable (maximum) time axis and / or frequency axis synchronization error (range) (per slot / symbol)

[0203] (2) Allowable (maximum) time axis and / or frequency axis synchronization error (range) (based on the start time of transmission)

[0204] (3) (Maximum) rate of change of time axis and / or frequency axis synchronization error (during transmission)

[0205] A. For example, it may be a time drift rate and / or a Doppler drift rate, etc.

[0206] According to the proposed method of the present disclosure, there is an advantage in that the same definition of time synchronization error and / or Doppler shift line-compensation requirement(s) (at the terminal end) can be used during uplink transmission (of a specific type) between a base station and a terminal, and based on this, the base station can expect to receive a signal of a promised and / or defined form for the uplink transmission (of a specific type).

[0207] The above [Proposed Plan #01] may be applied in combination with other proposed plans within the scope where the proposed operations do not conflict.

[0208] [Proposed Method #02] When there may exist (pre)requirement(s) to support (a specific type) uplink transmission between a base station and a terminal, the base station and / or terminal may recognize (pre)requirement(s) regarding time synchronization error and / or Doppler shift line-compensation (at the terminal end) as one type of said (pre)requirement(s) in one or more of the following ways.

[0209] (1) Prior agreement / definition between base station and terminal

[0210] (2) Base station sets / instructs terminal

[0211] (3) The terminal reports to the base station the supported time synchronization error and / or Doppler shift line-compensation level / capability information.

[0212] Here, for example, the above (specific type) uplink transmission may refer to an uplink transmission with an orthogonal cover code (OCC) applied (in the time axis and / or frequency axis). For example, when transmitting an uplink with the above OCC applied between a base station and a terminal, (pre) requirements for time delay and / or Doppler shift line-compensation (at the terminal end) may be met.

[0213] Here, for example, the above (pre)requirement(s) may be (pre)requirement(s) for a specific type of terminal. For example, they may be (pre)requirement(s) for an NTN service terminal.

[0214] For example, let us assume that in a next-generation mobile communication system based on a non-terrestrial network according to an embodiment of the present disclosure, a terminal transmits an uplink data channel (e.g., PUSCH). For example, the non-terrestrial network may consist of a terminal, a satellite, and a base station, and the terminal and the satellite may be connected by a service link, and the satellite and the base station may be connected by a feeder link. Here, for example, due to the long distance and high relative speed between the terminal and the satellite, time-axis and / or frequency-axis synchronization errors may occur in the service link, etc. For example, time-axis synchronization errors and / or Doppler shifts may occur. Here, for example, time-axis and / or frequency-axis synchronization errors (within a certain level) may be required during uplink transmission (of a specific type) between the base station and the terminal.

[0215] Here, for example, the (pre)requirement for the time axis and / or frequency axis synchronization error (within a certain level) may be defined as the (pre)requirement(s) for the time synchronization error and / or Doppler shift line-compensation (at the terminal end). Here, for example, the base station and / or terminal may recognize the (pre)requirement(s) for the line-compensation in one or more of the following ways.

[0216] (1) Prior agreement / definition between base station and terminal

[0217] (2) Base station sets / instructs terminal

[0218] (3) The terminal reports to the base station the supported time synchronization error and / or Doppler shift line-compensation level / capability information.

[0219] For example, when a base station intends to set / instruct a terminal to perform uplink transmission with OCC applied (in the time axis and / or frequency axis) for purposes such as uplink multiplexing and / or capacity enhancement, time synchronization error and / or Doppler shift pre-compensation requirement(s) (at the terminal end) may be defined to maintain orthogonality between said OCC(s). For example, said pre-compensation requirement(s) may be pre-agreed upon / defined or set / instructed by the base station to the terminal. For example, the terminal may report its time synchronization error and / or Doppler shift pre-compensation capability (at the terminal end) to the base station, and the base station may determine whether to apply OCC in uplink transmission by referring to said terminal's capability. According to the proposed method of the present disclosure, there is an advantage in that the base station and the terminal can have the same awareness of the time synchronization error and / or Doppler shift line-compensation requirement(s) during uplink transmission (of a specific type) between them, and based on this, the base station can expect to receive a signal of a promised and / or defined form for the uplink transmission (of a specific type).

[0220] The above [Proposed Plan #02] may be applied in combination with other proposed plans within the scope where the proposed operations do not conflict.

[0221] [Proposed Plan #03] When there may be (pre)requirement(s) to support (a specific type) uplink transmission between a base station and a terminal, (pre)requirement(s) to support uplink transmission with OCC (orthogonal cover code) applied, as one type of the said (pre)requirement(s), may be defined / configured / instructed / reported by classifying them according to one or more of the following criteria.

[0222] (1) OCC type

[0223] A. For example, OCC types can be classified according to the area where OCC is applied. For instance, they can be classified into types where OCC is applied within (OFDM) symbols, types where OCC is applied between (OFDM) symbol groups, types where OCC is applied between (OFDM) slot groups, and so on.

[0224] B. For example, OCC types can be distinguished according to the OCC code. For instance, they can be classified into types to which Walsh-Hadamard codes are applied, types to which DFT codes are applied, and so on.

[0225] (2) OCC application unit

[0226] A. For example, it may refer to time axis and / or frequency axis resource units to which OCC is applied.

[0227] (3) OCC length

[0228] A. For example, it can mean the OCC code length.

[0229] (4) OCC identifier

[0230] A. For example, it can mean an index for an OCC code.

[0231] (5) OFDM numerology

[0232] A. For example, it may refer to subcarrier spacing, symbol duration, cyclic prefix length, etc. in OFDM transmission methods.

[0233] Here, for example, the above (pre)requirement(s) may be pre-agreed upon / defined between the base station and the terminal, or the base station may set / instruct the terminal.

[0234] Here, for example, the above (specific type) uplink transmission may refer to an uplink transmission with an orthogonal cover code (OCC) applied (in the time axis and / or frequency axis). For example, when transmitting an uplink with the above OCC applied between a base station and a terminal, (pre) requirements for time delay and / or Doppler shift line-compensation (at the terminal end) may be met.

[0235] Here, for example, the (pre)requirement(s) for supporting uplink transmission with the orthogonal cover code (OCC) applied may be (pre)requirement(s) for time synchronization error and / or Doppler shift line-compensation (at the terminal end).

[0236] Here, for example, the above (pre)requirement(s) may be (pre)requirement(s) for a specific type of terminal. For example, they may be (pre)requirement(s) for an NTN service terminal.

[0237] For example, let us assume that in a next-generation mobile communication system based on a non-terrestrial network according to an embodiment of the present disclosure, a terminal transmits an uplink data channel (e.g., PUSCH). For example, the non-terrestrial network may consist of a terminal, a satellite, and a base station, and the terminal and the satellite may be connected by a service link, and the satellite and the base station may be connected by a feeder link. Here, for example, due to the long distance and high relative speed between the terminal and the satellite, time-axis and / or frequency-axis synchronization errors may occur in the service link, etc. For example, time-axis synchronization errors and / or Doppler shifts may occur. Here, for example, time-axis and / or frequency-axis synchronization errors (within a certain level) may be required during uplink transmission (of a specific type) between the base station and the terminal.

[0238] Here, for example, the above (specific type) uplink transmission may mean an uplink transmission to which an orthogonal cover code (OCC) is applied (time axis and / or frequency axis). Here, for example, to achieve the above time axis and / or frequency axis synchronization error (within a certain level), (pre)requirements for time delay and / or Doppler shift line-compensation (at the terminal end) may be defined. For example, in a non-terrestrial network according to one embodiment of the present disclosure, when the OCC is applied uplink transmission between a base station and a terminal, the (pre)requirements for time delay and / or Doppler shift line-compensation (at the terminal end) may be satisfied. Here, for example, the (pre)requirement(s) may be (pre)defined, or set / instructed by the base station to the terminal, or reported by the terminal to the base station. Here, for example, the above (pre)requirement(s) may be defined / configured / instructed / reported by classifying them according to one or more criteria, such as OCC type, OCC application unit, OCC length, OCC identification information, and OFDM numerology. For example, (pre)requirement(s) may be defined / configured / instructed / reported according to combinations of OCC application unit and OCC length. Here, for example, the proposed method of the present disclosure may include a method in which, when a terminal reports a support / capability level for time synchronization error and / or Doppler shift line-compensation (at the terminal end) to a base station, the support / capability level is reported by classifying it according to one or more criteria, such as OCC type, OCC application unit, OCC length, OCC identification information, and OFDM numerology.For example, when a terminal reports support(s) for time delay and / or Doppler shift line-compensation (at the terminal end) to a base station (or network), it may report support(s) distinguished by one or more criteria, such as OCC type, OCC application unit, OCC length, OCC identification information, and OFDM numerology. For example, it may report line-compensation support(s) for each combination of OCC application unit and OCC length. According to the proposed method of the present disclosure, there is an advantage that when performing OCC-based uplink transmission between a base station and a terminal, appropriate (pre)requirement(s) for each detailed setting of the OCC can be shared.

[0239] The above [Proposed Plan #03] may be applied in combination with other proposed plans within the scope where the proposed operations do not conflict.

[0240] [Proposed Plan #04] When there may be (pre)requirement(s) to support (a specific type) uplink transmission between a base station and a terminal, the terminal may report to the base station whether the (pre)requirement(s) are met and / or not met.

[0241] Here, for example, the above (specific type) uplink transmission may refer to an uplink transmission with an orthogonal cover code (OCC) applied (in the time axis and / or frequency axis). For example, when transmitting an uplink with the above OCC applied between a base station and a terminal, (pre) requirements for time delay and / or Doppler shift line-compensation (at the terminal end) may be met.

[0242] Here, for example, the above (pre)requirement(s) may be pre-agreed upon / defined between the base station and the terminal, or the base station may set / instruct the terminal.

[0243] Here, for example, the above (pre)requirement(s) may be (pre)requirement(s) for time synchronization error and / or Doppler shift line-compensation (at the terminal end) during uplink transmission with OCC (orthogonal cover code) applied (hereinafter referred to as the first requirement(s).

[0244] Here, for example, the first requirement(s) above may be a requirement for the level / range of the time axis and / or frequency axis synchronization error.

[0245] Here, for example, the above (pre)requirement(s) may be (pre)requirement(s) for a specific type of terminal. For example, they may be (pre)requirement(s) for an NTN service terminal.

[0246] For example, let us assume that in a next-generation mobile communication system based on a non-terrestrial network according to an embodiment of the present disclosure, a terminal transmits an uplink data channel (e.g., PUSCH). For example, the non-terrestrial network may consist of a terminal, a satellite, and a base station, and the terminal and the satellite may be connected by a service link, and the satellite and the base station may be connected by a feeder link. Here, for example, due to the long distance and high relative speed between the terminal and the satellite, time-axis and / or frequency-axis synchronization errors may occur in the service link, etc. For example, time-axis synchronization errors and / or Doppler shifts may occur. Here, for example, time-axis and / or frequency-axis synchronization errors (within a certain level) may be required during uplink transmission (of a specific type) between the base station and the terminal.

[0247] Here, for example, the above (specific type) uplink transmission may mean an uplink transmission to which an orthogonal cover code (OCC) is applied (in the time axis and / or frequency axis). Here, for example, to achieve the above time axis and / or frequency axis synchronization error (within a certain level), (pre)requirements for time delay and / or Doppler shift line-compensation (at the terminal end) may be defined. For example, in a non-terrestrial network according to one embodiment of the present disclosure, when the OCC-applied uplink transmission between a base station and a terminal, the (pre)requirements for time delay and / or Doppler shift line-compensation (at the terminal end) may be satisfied. Here, for example, the (pre)requirement(s) may be (pre)defined or set / instructed by the base station to the terminal. Here, for example, the base station may set / instruct OCC-based uplink transmission only when the terminal satisfies the (pre)requirement(s) for line-compensation. Accordingly, the terminal must be able to report to the base station whether the above (pre)requirement(s) are satisfied or not satisfied. For example, (pre)requirement(s) for time synchronization error (at the terminal end) and / or Doppler shift line-compensation by OCC type / OCC application unit / OCC length between the base station and the terminal are (pre)defined, and the terminal can report to the base station whether the (pre)requirement(s) by OCC type / OCC application unit / OCC length are satisfied and / or not satisfied. Here, for example, the reporting form may be a terminal capability reporting form. According to the proposed method of the present disclosure, when performing OCC-based uplink transmission between the base station and the terminal, there is an advantage that the base station can identify the OCC setting(s) that the terminal supports and apply the OCC that the terminal supports at an effective time.

[0248] The above [Proposed Plan #04] may be applied in combination with other proposed plans within the scope where the proposed operations do not conflict.

[0249] [Proposed Method #05] When there are (pre) requirement(s) (hereinafter referred to as the first requirement(s)) when an uplink transmission with an orthogonal cover code (OCC) applied between a base station and a terminal, if the terminal fails to satisfy the first requirement(s) for an OCC-based uplink transmission set / instructed by the base station, it may perform one or more of the following exception handling operations.

[0250] (1) Omission of (configured / instructed) OCC-based uplink transmission

[0251] (2) OCC not applied when transmitting (configured / instructed) OCC-based uplink

[0252] (3) Apply OCC (default) when transmitting an uplink based on (configured / instructed) OCC

[0253] Here, for example, the first requirement(s) may be pre-agreed upon / defined between the base station and the terminal, or the base station may set / instruct the terminal.

[0254] Here, for example, the first requirement(s) above may be (pre) requirement(s) for time synchronization error (at the terminal) and / or Doppler shift line-compensation (pre-compensation).

[0255] Here, for example, the first requirement(s) above may be (pre) requirement(s) for the level / range of time axis and / or frequency axis synchronization error.

[0256] Here, for example, the above (default) OCC may refer to an OCC (pre-agreed) between the base station and the terminal or an OCC set by the base station.

[0257] Here, for example, the above (pre)requirement(s) may be (pre)requirement(s) for a specific type of terminal. For example, they may be (pre)requirement(s) for an NTN service terminal.

[0258] For example, let us assume that in a next-generation mobile communication system based on a non-terrestrial network according to an embodiment of the present disclosure, a terminal transmits an uplink data channel (e.g., PUSCH). For example, the non-terrestrial network may consist of a terminal, a satellite, and a base station, and the terminal and the satellite may be connected by a service link, and the satellite and the base station may be connected by a feeder link. Here, for example, due to the long distance and high relative speed between the terminal and the satellite, time-axis and / or frequency-axis synchronization errors may occur in the service link, etc. For example, time-axis synchronization errors and / or Doppler shifts may occur. Here, for example, time-axis and / or frequency-axis synchronization errors (within a certain level) may be required during uplink transmission (of a specific type) between the base station and the terminal.

[0259] The above (specific type) uplink transmission may refer to an uplink transmission to which an orthogonal cover code (OCC) is applied (in the time axis and / or frequency axis). Here, for example, to achieve the above time axis and / or frequency axis synchronization error (within a certain level), (pre) requirements for time delay and / or Doppler shift line-compensation (at the terminal end) may be defined. For example, in a non-terrestrial network according to an embodiment of the present disclosure, when an uplink transmission with the above OCC is applied between a base station and a terminal, (pre) requirements for time delay and / or Doppler shift line-compensation (at the terminal end) may be satisfied. Here, for example, if the base station has set / instructed the terminal to perform an uplink transmission with the above OCC applied, but the terminal does not satisfy the (pre) requirement(s) for the application of the above OCC, an exception handling operation for the transmission may be required. For example, if the terminal does not meet the above (pre)requirement(s) for an OCC-based uplink transmission set / instructed by the base station, it may perform one or more of the following exception handling actions.

[0260] (1) Omission of (configured / instructed) OCC-based uplink transmission

[0261] (2) OCC not applied when transmitting (configured / instructed) OCC-based uplink

[0262] (3) Apply OCC (default) when transmitting an uplink based on (configured / instructed) OCC

[0263] According to the proposed method of the present disclosure above, there is an advantage in that it can support an exception handling operation when the terminal fails to satisfy the (pre)requirement(s) for the transmission during (a specific type) uplink transmission between the base station and the terminal, thereby clarifying the uplink transmission operation between the base station and the terminal.

[0264] The above [Proposed Plan #05] may be applied in combination with other proposed plans within the scope where the proposed operations do not conflict.

[0265] [Proposed Method #06] When an uplink transmission with an orthogonal cover code (OCC) applied between a base station and a terminal exists (preliminary) requirement(s) (hereinafter referred to as the first requirement(s)), the terminal may report to the base station, including one or more of the following information as supported OCC information.

[0266] (1) (Supportable) OCC types

[0267] (2) (Supportable) OCC Application Units

[0268] (3) (Supportable) OCC length

[0269] (4) (Supportable) OCC identifier (e.g., OCC index)

[0270] Here, for example, the first requirement(s) may be pre-agreed upon / defined between the base station and the terminal, or the base station may set / instruct the terminal.

[0271] Here, for example, the first requirement(s) above may be (pre) requirement(s) for time synchronization error (at the terminal) and / or Doppler shift line-compensation (pre-compensation).

[0272] Here, for example, the above (pre)requirement(s) may be (pre)requirement(s) for a specific type of terminal. For example, they may be (pre)requirement(s) for an NTN service terminal.

[0273] For example, let us assume that in a next-generation mobile communication system based on a non-terrestrial network according to an embodiment of the present disclosure, a terminal transmits an uplink data channel (e.g., PUSCH). For example, the non-terrestrial network may consist of a terminal, a satellite, and a base station, and the terminal and the satellite may be connected by a service link, and the satellite and the base station may be connected by a feeder link. Here, for example, due to the long distance and high relative speed between the terminal and the satellite, time-axis and / or frequency-axis synchronization errors may occur in the service link, etc. For example, time-axis synchronization errors and / or Doppler shifts may occur. Here, for example, time-axis and / or frequency-axis synchronization errors (within a certain level) may be required during uplink transmission (of a specific type) between the base station and the terminal.

[0274] The above (specific type) uplink transmission may refer to an uplink transmission to which an orthogonal cover code (OCC) is applied (in the time axis and / or frequency axis). Here, for example, to achieve the above time axis and / or frequency axis synchronization error (within a certain level), (pre)requirements for time delay and / or Doppler shift line-compensation (at the terminal end) may be defined. For example, in a non-terrestrial network according to an embodiment of the present disclosure, when the OCC is applied to an uplink transmission between a base station and a terminal, the (pre)requirements for time delay and / or Doppler shift line-compensation (at the terminal end) may be satisfied. Here, for example, the (pre)requirement(s) may be (pre)agreed upon / defined between the base station and the terminal. Here, for example, the terminal may report supportable OCC information to the base station (or network) based on the (pre)requirement(s). For example, the terminal may report information to the base station such as (supported) OCC types, (supported) OCC application units, (supported) OCC lengths, and (supported) OCC identifiers (e.g., OCC index). According to the proposed method of the present disclosure, there is an advantage that the base station can obtain OCC information supported by the terminal in advance and set / instruct a valid OCC during uplink transmission.

[0275] Alternatively, a method may be considered in which the terminal reports to the base station, including one or more of the following information as OCC information that can be supported.

[0276] (1) All or some of the (supported) OCC types

[0277] (2) All or part of the (supported) OCC coverage units

[0278] (3) All or part of the (supported) OCC length

[0279] (4) All or part of the (supported) OCC identifiers (e.g., OCC index)

[0280] For example, the terminal may report to the base station information regarding all or part of the OCC resource setting(s) it supports. For example, the said part of the information may refer to the OCC resource setting(s) preferred by the terminal, or it may be a setting recommended by the terminal to the base station. Here, for example, upon receiving the report from the terminal, the base station may determine whether to apply it and then apply it. Here, for example, the base station may apply a specific setting among the setting(s) reported by the terminal as supported.

[0281] The proposed method of the present disclosure above can be obviously extended and applied even in cases where prior requirements are not specified.

[0282] The above [Proposed Plan #06] may be applied in combination with other proposed plans within the scope where the proposed operations do not conflict.

[0283] [Proposed Method #07] When a terminal can apply OCC to an uplink transmission signal (and / or its repeated transmission), the terminal reports (terminal) capability information regarding said OCC (supportable) to the base station, and the base station may assume that one or more of the following condition(s) are satisfied for said (supportable) OCC.

[0284] (1) Maintaining phase continuity (of terminal signal) (within OCC application interval)

[0285] (2) Maintaining power consistency (of terminal signals) (within OCC application interval)

[0286] (3) (When transferring resources with OCC applied) Time difference pre-compensation (within a certain level)

[0287] (4) (When transmitting resources with OCC applied) Doppler shift pre-compensation (within a certain level)

[0288] (5) (Per OCC application unit) Repeated generation and / or mapping of the same signal

[0289] (6) Support for OCC application (for uplink transmission signals)

[0290] Here, for example, whether the above OCC is applied can be set / instructed by the base station.

[0291] Here, for example, the above OCC may be applied between repeated transmissions.

[0292] Here, for example, the uplink transmission signal may be an uplink data channel (e.g., PUSCH).

[0293] Here, for example, the establishment of phase continuity and / or power consistency may mean that the phase and / or power change (of the terminal signal) is within a certain (error) range.

[0294] Here, for example, the time difference line-compensation and / or Doppler shift line-compensation may mean that the time axis and / or frequency axis synchronization is within a certain (error) range. Here, for example, the requirements and / or error range for the time difference line-compensation and / or Doppler shift line-compensation may be (pre)set and / or (pre)defined between the base station and the terminal.

[0295] Here, for example, when the terminal reports capability information for (supportable) OCC, it may include OCC length and / or OCC application unit information. For example, if the OCC length is 4 and the OCC application unit is 1 Slot, an OCC of length 4 may be applied to 4 slot(s).

[0296] For example, let us assume that in a next-generation mobile communication system based on a non-terrestrial network according to an embodiment of the present disclosure, a terminal transmits an uplink data channel (e.g., PUSCH). For example, the non-terrestrial network may consist of a terminal, a satellite, and a base station, and the terminal and the satellite may be connected via a service link, while the satellite and the base station may be connected via a feeder link. Here, for example, the area serviced by the non-terrestrial network, for example, the satellite, may be relatively much wider than conventional cell coverage, and the terminal may need to perform repetitive transmissions in the uplink to support coverage. Here, for example, the efficiency of resource utilization may be reduced during such repetitive transmissions, and a method to increase uplink transmission capacity by supporting OCC (orthogonal cover code)-based multiplexing during uplink repetitive transmissions may be considered. Here, for example, the base station must be able to determine whether OCC application is possible during uplink transmission by the terminal, and the terminal may report capability information regarding the OCC to the base station.

[0297] Here, for example, the terminal may convey its OCC application capability to the base station by reporting (supported) OCC information. Here, for example, the base station may expect that the following condition(s) are satisfied for the (supported) OCC reported by the terminal.

[0298] (1) Maintaining phase continuity (of terminal signal) (within OCC application interval)

[0299] (2) Maintaining power consistency (of terminal signals) (within OCC application interval)

[0300] (3) (When transferring resources with OCC applied) Time difference pre-compensation (within a certain level)

[0301] (4) (When transmitting resources with OCC applied) Doppler shift pre-compensation (within a certain level)

[0302] (5) (Per OCC application unit) Repeated generation and / or mapping of the same signal

[0303] (6) Support for OCC application (for uplink transmission signals)

[0304] Here, for example, in the case of a terminal that characteristically supports communication with a non-terrestrial network, the base station may assume that if the terminal reports support capability for a (specific) OCC, said terminal can support time difference and / or Doppler shift line-compensation (within a certain level) within the interval where said OCC is applied. Here, for example, the requirement(s) for the accuracy of said time difference and / or Doppler shift line-compensation may be (pre)configured and / or defined between the base station and the terminal. Here, for example, support capability for said (specific) OCC may imply the maintenance of phase continuity and / or power consistency within the interval where the OCC is applied. Here, for example, the above OCC may be an OCC applied during repeated transmissions of an uplink data channel (e.g., PUSCH), and in the above case, the ability to support (specific) OCC may imply that support for repeated PUSCH transmissions is possible. According to the proposed method of the present disclosure, there is an advantage in that when a terminal reports its OCC support capability to a base station, the base station can naturally identify the relevant detailed capability, thereby enabling the base station to accurately identify the terminal's capability.

[0305] The above [Proposed Plan #07] may be applied in combination with other proposed plans within the scope where the proposed operations do not conflict.

[0306] [Proposed Plan #08] When a terminal can apply OCC (hereinafter OCC) to an uplink transmission signal (and / or its repeated transmission), the terminal may report one or more of the following (terminal) capability information to the base station, and the base station may determine that the terminal has the capability to support the said OCC if a (specific) combination of (terminal) capabilities is supported.

[0307] (1) Ability to maintain phase continuity (of terminal signals) (within a certain time / frequency interval)

[0308] (2) Ability to maintain power consistency (of terminal signals) within a certain time / frequency interval

[0309] (3) Time difference pre-compensation capability (within a certain time / frequency interval)

[0310] (4) Doppler shift pre-compensation capability (within a specific time / frequency interval)

[0311] (5) Repetitive generation and / or mapping capability of the same signal (or repetitive transmission capability of PUSCH)

[0312] (6) OCC applied signal generation capability (for uplink transmission signals)

[0313] Here, for example, whether the above OCC is applied can be set / instructed by the base station.

[0314] Here, for example, the above OCC may be applied between repeated transmissions.

[0315] Here, for example, the uplink transmission signal may be an uplink data channel (e.g., PUSCH).

[0316] Here, for example, the maintenance of phase continuity and / or establishment of power consistency may mean that the phase and / or power change (of the terminal signal) is within a certain (error) range.

[0317] Here, for example, the time difference line-compensation and / or Doppler shift line-compensation may mean that the time axis and / or frequency axis synchronization is within a certain (error) range. Here, for example, the requirements and / or error range for the time difference line-compensation and / or Doppler shift line-compensation may be (pre)set and / or (pre)defined between the base station and the terminal.

[0318] Here, for example, the terminal may report terminal capabilities related to phase continuity and / or power consistency in the form of terminal capabilities related to DM-RS Bundling (e.g., maxDMRS-BundlingDuration). Here, for example, maxDMRS-BundlingDuration may refer to the maximum time interval during which the terminal can maintain phase continuity and / or power consistency, etc.

[0319] For example, let us assume that in a next-generation mobile communication system based on a non-terrestrial network according to an embodiment of the present disclosure, a terminal transmits an uplink data channel (e.g., PUSCH). For example, the non-terrestrial network may consist of a terminal, a satellite, and a base station, and the terminal and the satellite may be connected via a service link, while the satellite and the base station may be connected via a feeder link. Here, for example, the area serviced by the non-terrestrial network, for example, the satellite, may be relatively much wider than conventional cell coverage, and the terminal may need to perform repetitive transmissions in the uplink to support coverage. Here, for example, the efficiency of resource utilization may be reduced during such repetitive transmissions, and a method to increase uplink transmission capacity by supporting OCC (orthogonal cover code)-based multiplexing during uplink repetitive transmissions may be considered. Here, for example, the base station must be able to determine whether OCC application is possible during uplink transmission by the terminal, and the terminal may report capability information regarding the OCC to the base station.

[0320] Here, for example, the terminal may transmit OCC application capability to the base station by reporting one or more terminal capability(s) related to OCC application. For example, the terminal may report one or more of the following capability(s), and the base station may recognize that the terminal has OCC application capability from the combination of said capability(s).

[0321] (1) Ability to maintain phase continuity (of terminal signals) (within a certain time / frequency interval)

[0322] (2) Ability to maintain power consistency (of terminal signals) within a certain time / frequency interval

[0323] (3) Time difference pre-compensation capability (within a certain time / frequency interval)

[0324] (4) Doppler shift pre-compensation capability (within a specific time / frequency interval)

[0325] (5) Repetitive generation and / or mapping capability of the same signal (or repetitive transmission capability of PUSCH)

[0326] (6) OCC applied signal generation capability (for uplink transmission signals)

[0327] Here, for example, the capability to generate OCC-applied signals (for uplink transmission signals) may simply mean that the terminal is capable of generating signals with OCC applied, and may not guarantee orthogonality between OCCs. For example, even if the terminal reports the capability to generate OCC-applied signals, if the terminal reports that it lacks the capability to maintain phase continuity and / or power consistency, or reports that the duration for maintaining phase continuity and / or power consistency is shorter than the OCC length and / or OCC application duration, the base station may determine that it is difficult for the terminal to support OCC that guarantees orthogonality and may not configure OCC application for uplink transmission. For example, for the base station to configure OCC for uplink transmission, one or more OCC-related terminal capability(s) must be supported. According to the proposed method of the present disclosure above, when a terminal reports its OCC support capabilities to a base station, the base station can naturally identify the relevant detailed capabilities, thereby enabling the base station to accurately identify the terminal's capabilities.

[0328] The above [Proposed Plan #08] may be applied in combination with other proposed plans within the scope where the proposed operations do not conflict.

[0329] [Proposed Method #09] When a terminal can apply OCC (hereinafter OCC) to an uplink transmission signal (and / or its repeated transmission), the terminal can report information regarding the OCC-related (terminal) capability to the base station through a first process, and the terminal can report information regarding the validity (or whether the OCC application condition is satisfied) of the OCC (within a certain time / frequency interval) to the base station through a second process (distinguished from the first process).

[0330] Here, for example, the second process may include one or more of the following methods.

[0331] (1) The base station can send a trigger signal, and the terminal can report when it receives the trigger signal.

[0332] (2) The base station can set up an event, and the terminal can report when the event occurs.

[0333] (3) The terminal can report.

[0334] Here, for example, whether the above OCC is applied can be set / instructed by the base station.

[0335] Here, for example, the above OCC may be applied between repeated transmissions.

[0336] Here, for example, the uplink transmission signal may be an uplink data channel (e.g., PUSCH).

[0337] Here, for example, the base station may transmit to the terminal event settings and / or reporting (resource) settings, etc., for reporting information related to the validity (or OCC application conditions) of the OCC.

[0338] Here, for example, the terminal may report information related to the validity (or OCC application conditions) of the OCC to the base station in the form of terminal assistance information (UE assistance information), etc.

[0339] Here, for example, the validity of the OCC (or the OCC application condition) may refer to information related to conditions for maintaining OCC-based orthogonality. For example, it may refer to whether the time and / or frequency axis synchronization conditions for the application of the OCC are satisfied.

[0340] For example, let us assume that in a next-generation mobile communication system based on a non-terrestrial network according to an embodiment of the present disclosure, a terminal transmits an uplink data channel (e.g., PUSCH). For example, the non-terrestrial network may consist of a terminal, a satellite, and a base station, and the terminal and the satellite may be connected via a service link, while the satellite and the base station may be connected via a feeder link. Here, for example, the area serviced by the non-terrestrial network, for example, the satellite, may be relatively much wider than conventional cell coverage, and the terminal may need to perform repetitive transmissions in the uplink to support coverage. Here, for example, the efficiency of resource utilization may be reduced during such repetitive transmissions, and a method to increase uplink transmission capacity by supporting OCC (orthogonal cover code)-based multiplexing during uplink repetitive transmissions may be considered. Here, for example, the base station must be able to determine whether OCC application is possible during uplink transmission by the terminal, and the terminal may report capability information regarding the OCC to the base station.

[0341] Here, for example, the conditions for a terminal to apply OCC during uplink transmission can be broadly divided into internal terminal conditions and external terminal conditions. Here, for example, the internal terminal conditions for applying OCC may be included in the terminal's OCC support capabilities and reported as a first process, and the external terminal conditions for applying OCC may be reported as a separate second process distinct from the first process. For example, the terminal may report capabilities such as the capability to maintain phase continuity and / or power consistency, the capability to repeat PUSCH transmission, and the capability to generate OCC-applied signals as terminal capabilities, and the capability for time difference and / or Doppler shift pre-compensation may be reported as a separate process. For example, it may be reported as one or more of the following methods.

[0342] (1) The base station can send a trigger signal, and the terminal can report when it receives the trigger signal.

[0343] (2) The base station can set up an event, and the terminal can report when the event occurs.

[0344] (3) The terminal can report.

[0345] Here, for example, when the terminal reports information related to the OCC validity to the base station, it may report by utilizing explicit reporting resources and / or by modifying / utilizing existing resources, such as including it in DM-RS (demodulation reference signal) scrambling information. According to the proposed method of the present disclosure, (dynamic) elements based on external environments, such as the channel environment, among the OCC application conditions may be reported through a separate process other than the statically reported terminal capability reporting process, thereby helping the base station and / or terminal to dynamically identify the OCC application conditions.

[0346] The above [Proposed Plan #09] may be applied in combination with other proposed plans within the scope where the proposed operations do not conflict.

[0347] [Proposed Method #10] When a terminal can apply OCC to an uplink data channel (and / or its repeated transmissions), the OCC length and / or OCC index and / or OCC type and / or whether OCC is applied for an uplink data channel scheduled with a fallback DCI (e.g., DCI format 0_0) can be determined by one or more of the following methods.

[0348] (1) The base station is set to an upper layer signal (e.g., RRC signaling).

[0349] (2) (Prior) agreement / definition between base station and terminal

[0350] Here, for example, the base station may transmit (upper layer) configuration information for an uplink data channel scheduled with a fallback DCI separately from (upper layer) configuration information for an uplink data channel scheduled with a non-fallback DCI.

[0351] Here, for example, the above OCC may be applied between a single transmission and / or repeated transmissions.

[0352] For example, let us assume that in a next-generation mobile communication system based on a non-terrestrial network according to an embodiment of the present disclosure, a terminal transmits an uplink data channel (e.g., PUSCH). Here, for example, a method of supporting multiplexing by applying OCC to the uplink data channel to support uplink capacity increase, etc., may be considered. Here, for example, if the uplink data channel (e.g., PUSCH) is scheduled with a fallback DCI (e.g., DCI format 0_0), it may be difficult to dynamically indicate OCC-related resource information because there is not a sufficient bit field within the fallback DCI. Accordingly, in the present disclosure, when a terminal can apply OCC to an uplink data channel (and / or its repeated transmissions), the OCC length and / or OCC index and / or OCC type and / or whether OCC is applied for an uplink data channel scheduled with a fallback DCI (e.g., DCI format 0_0) may be determined by one or more of the following methods.

[0353] (1) The base station is set to an upper layer signal (e.g., RRC signaling).

[0354] (2) (Prior) agreement / definition between base station and terminal

[0355] Here, for example, the base station may transmit (upper layer) configuration information for an uplink data channel scheduled with a fallback DCI (e.g., DCI format 0_0) separately from (upper layer) configuration information for an uplink data channel scheduled with a non-fallback DCI (e.g., DCI format 0_1). For example, or the base station may only set whether to apply OCC to a fallback DCI-based uplink data channel, and other OCC configuration information, such as the OCC index and / or OCC length, may be determined according to a predefined / agreed method. For example, when the base station sets / instructs the application of OCC for an uplink data channel scheduled with a fallback DCI, the terminal may apply a (default) OCC index or a (default) OCC code to the corresponding uplink data channel. For example, the above (default) OCC code may be a code in which all OCC elements are 1 and expressed as [+1, +1, … , +1].

[0356] The above [Proposed Plan #10] may be applied in combination with other proposed plans within the scope where the proposed operations do not conflict.

[0357] In non-terrestrial networks (NTN) or long-cycle downlink synchronization environments, the following problems may exist.

[0358] - Problem of extending the SSB transmission cycle

[0359] In an NTN environment, due to satellite EIRP constraints and multiple cell / beam simultaneous service issues, the downlink transmission period of a conventional synchronization signal block (SSB) can increase from 20 ms to 160 ms or more.

[0360] In this case, the UE must perform long-term monitoring to detect the synchronization signal, and considering the number of repeated detections required by the standard, the synchronization acquisition delay and power consumption may increase excessively.

[0361] - Problem of increasing frequency search complexity

[0362] In the conventional method, the terminal must search for the synchronization signal block across the entire dense first sync raster, so the search complexity can increase rapidly.

[0363] - Inefficiency caused by the combination of synchronization-only signals and system information signals

[0364] Since conventional SSBs include PSS / SSS and PBCH together, the terminal may bear the burden of receiving unnecessary system information even for pure synchronization purposes.

[0365] [Proposed Method #11] When a base station can transmit a simplified synchronization signal block utilizing all or part of a synchronization signal block to a terminal, the terminal can receive the simplified synchronization signal block by utilizing a (separate) synchronization raster (second synchronization raster) that is distinct from the synchronization raster (first synchronization raster) used to transmit the conventional synchronization signal block.

[0366] Here, for example, the synch raster may refer to a subset of RF reference frequencies used by the terminal to detect a synchronization signal block.

[0367] Here, for example, the conventional synchronous signal block may be a signal transmitted for synchronous and system information detection, and may be composed of a PSS (primary synchronous signal) and / or an SSS (secondary synchronous signal) and / or a PBCH (physical broadcast channel).

[0368] Here, for example, the simplified synchronous signal block may be a signal transmitted purely for synchronous purposes and may consist of a primary synchronous signal (PSS) and / or a secondary synchronous signal (SSS).

[0369] Here, for example, information such as whether to support / transmit the simplified synchronization signal block and / or time / frequency / power resource settings may be provided to the terminal through a conventional synchronization signal block and / or a (separate) SIB (system Information block).

[0370] Here, for example, the simplified synchronization signal block may be restricted so that the terminal utilizes it only for synchronization purposes and does not utilize it as a measurement resource for RRM (radio resource management) and / or BM (beam management), etc. For example, or the base station may set / instruct the terminal whether to allow the simplified synchronization signal block as a measurement resource.

[0371] For example, in a next-generation mobile communication system based on a non-terrestrial network according to an embodiment of the present disclosure, a single satellite can provide service over a very wide area, and the number of service target cells / beams may be hundreds or more. Here, for example, due to the physical characteristics of the satellite, it may be difficult to simultaneously support (nominal) (maximum) EIRP (effective isotopically radiated power) for all service target cells. Therefore, the NTN may perform downlink transmission to avoid simultaneous transmission between cells as much as possible. Here, for example, the NTN may be configured to avoid simultaneous transmission as much as possible for synchronization signal blocks for synchronization and system information acquisition. For example, a very long period may be set / supported for the synchronization signal blocks. Here, for example, since the synchronization performance of the terminal may be affected as the time axis period of the synchronization signal block increases in the NTN, support for the transmission of simplified synchronization signal blocks may be considered to compensate for this. Here, for example, the simplified synchronization signal block may be a signal transmitted purely for synchronization purposes. For example, the simplified synchronization signal block may be composed of a primary synchronous signal (PSS) and / or a secondary synchronous signal (SSS). Here, for example, the simplified synchronization signal block may be transmitted at a location distinct from the frequency axis resource location where the conventional synchronization signal block is transmitted, so as not to affect the detection performance of the conventional synchronization signal block; however, since the configuration information that can be indicated within the conventional synchronization signal block is limited, it may be difficult to explicitly indicate the frequency axis location information of the simplified synchronization signal block. For example, the conventional synchronization signal block may only indicate the presence or absence of the simplified synchronization signal, and the terminal may subsequently have to perform the detection of the simplified synchronization signal itself by utilizing prior information.Accordingly, in the present disclosure, when a base station can transmit a simplified synchronization signal block utilizing all or part of a synchronization signal block to a terminal, the terminal may receive the simplified synchronization signal block by utilizing a (separate) synchronization raster (second synchronization raster) that is distinguished from a (first synchronization raster) for transmitting the synchronization signal block. Here, for example, the base station may provide information such as whether to support / transmit the simplified synchronization signal block and / or time / frequency / power resource settings to the terminal through a conventional synchronization signal block and / or a (separate) SIB (system Information block).

[0372] The above [Proposed Plan #11] may be applied in combination with other proposed plans(s) to the extent that the proposed operations do not conflict.

[0373] In non-terrestrial networks (NTN) or long-cycle downlink synchronization environments, the following problems may also exist.

[0374] - Problem of unnecessary continuous monitoring in conventional synchronization signal blocks

[0375] Even after the terminal has already obtained rough synchronization through a simplified synchronization signal block, there may be inefficiency in the conventional method where the first synchronization signal block (SSB) must always be monitored periodically.

[0376] - Continued terminal burden due to conventional SSB monitoring

[0377] Since the first synchronization signal block includes a PBCH, the terminal may still have a high complexity of monitoring and decoding burden.

[0378] According to the present disclosure, the following effects can be obtained.

[0379] - Reduction in terminal synchronous search complexity

[0380] Since the simplified synchronization signal block is searched only on the second sync raster, the terminal can acquire synchronization in an environment where the number of frequency candidates is significantly reduced without needing to search the entire dense first sync raster.

[0381] Accordingly, search complexity can be significantly reduced.

[0382] - Maintain synchronous performance even in long-cycle SSB environments

[0383] Even if the transmission period of the conventional SSB is extended, the terminal can maintain / reacquire synchronization more quickly and stably through a simplified second synchronization signal block.

[0384] - - It can be particularly effective in environments requiring an SSB cycle of 160 ms or more, such as NTN.

[0385] - Reduced terminal power consumption

[0386] By utilizing only a simplified synchronization signal block that does not include a PBCH, unnecessary demodulation and decoding operations are eliminated, thereby reducing terminal power consumption.

[0387] - Conventional synchronization signal block performance protection

[0388] By receiving the simplified synchronization signal block at a frequency position distinct from the first sync raster, interference with the detection performance and system information transmission performance of the conventional SSB can be avoided.

[0389] [Proposed Method #11-2] When a base station can transmit a simplified synchronization signal block utilizing all or part of a synchronization signal block to a terminal, the terminal may receive the simplified synchronization signal block by utilizing a (separate) synchronization raster (second synchronization raster) that is distinct from the synchronization raster (first synchronization raster) used to transmit the conventional synchronization signal block. Here, for example, the first synchronization raster may be an on-demand synchronization raster. For example, the first synchronization raster may be an on-demand synchronization raster based on the second synchronization raster. For example, the first synchronization raster may be an on-demand synchronization raster that is requested and transmitted based on the second synchronization raster. Here, for example, the second synchronization raster may be an always-on synchronization raster.

[0390] Here, for example, the synch raster may refer to a subset of RF reference frequencies used by the terminal to detect a synchronization signal block.

[0391] Here, for example, the conventional synchronous signal block may be a signal transmitted for synchronous and system information detection, and may be composed of a PSS (primary synchronous signal) and / or an SSS (secondary synchronous signal) and / or a PBCH (physical broadcast channel).

[0392] Here, for example, the simplified synchronous signal block may be a signal transmitted purely for synchronous purposes and may consist of a primary synchronous signal (PSS) and / or a secondary synchronous signal (SSS).

[0393] Here, for example, information such as whether to support / transmit the simplified synchronization signal block and / or time / frequency / power resource settings may be provided to the terminal through a conventional synchronization signal block and / or a (separate) SIB (system Information block).

[0394] Here, for example, the simplified synchronization signal block may be restricted so that the terminal utilizes it only for synchronization purposes and does not utilize it as a measurement resource for RRM (radio resource management) and / or BM (beam management), etc. For example, or the base station may set / instruct the terminal whether to allow the simplified synchronization signal block as a measurement resource.

[0395] For example, in a next-generation mobile communication system based on a non-terrestrial network according to an embodiment of the present disclosure, a single satellite can provide service over a very wide area, and the number of service target cells / beams may be hundreds or more. Here, for example, due to the physical characteristics of the satellite, it may be difficult to simultaneously support (nominal) (maximum) EIRP (effective isotopically radiated power) for all service target cells. Therefore, the NTN may perform downlink transmission to avoid simultaneous transmission between cells as much as possible. Here, for example, the NTN may be configured to avoid simultaneous transmission as much as possible for synchronization signal blocks for synchronization and system information acquisition. For example, a very long period may be set / supported for the synchronization signal blocks. Here, for example, since the synchronization performance of the terminal may be affected as the time axis period of the synchronization signal block increases in the NTN, support for the transmission of simplified synchronization signal blocks may be considered to compensate for this. Here, for example, the simplified synchronization signal block may be a signal transmitted purely for synchronization purposes. For example, the simplified synchronization signal block may be composed of a primary synchronous signal (PSS) and / or a secondary synchronous signal (SSS). Here, for example, the simplified synchronization signal block may be transmitted at a location distinct from the frequency axis resource location where the conventional synchronization signal block is transmitted, so as not to affect the detection performance of the conventional synchronization signal block; however, since the configuration information that can be indicated within the conventional synchronization signal block is limited, it may be difficult to explicitly indicate the frequency axis location information of the simplified synchronization signal block. For example, the conventional synchronization signal block may only indicate the presence or absence of the simplified synchronization signal, and the terminal may subsequently have to perform the detection of the simplified synchronization signal itself by utilizing prior information.Accordingly, in the present disclosure, when a base station can transmit a simplified synchronization signal block utilizing all or part of a synchronization signal block to a terminal, the terminal may receive the simplified synchronization signal block by utilizing a (separate) sync raster (second sync raster) that is distinct from the sync raster (first sync raster) for transmitting the synchronization signal block. Here, for example, the first sync raster may be an on-demand sync raster. For example, the first sync raster may be an on-demand sync raster based on the second sync raster. For example, the first sync raster may be an on-demand sync raster that is requested and transmitted based on the second sync raster. Here, for example, the second sync raster may be an always-on sync raster. Here, for example, the base station may provide information such as whether to support / transmit the simplified synchronization signal block and / or time / frequency / power resource settings to the terminal through a conventional synchronization signal block and / or a (separate) SIB (system Information block).

[0396] According to the present disclosure, the following effects can be obtained.

[0397] - Establishment of a two-step synchronization structure for terminal operation

[0398] - - The terminal can (i) acquire primary synchronization with a simplified synchronization signal block based on a second sync raster, and (ii) request and monitor the first synchronization signal block only when necessary to perform precise synchronization and acquire system information.

[0399] Accordingly, unnecessary conventional SSB continuous monitoring has been eliminated.

[0400] - Further reduction in terminal power consumption and computational complexity

[0401] Since the reception of conventional SSB (including PBCH) is limited to a request-based system, the terminal may only need to process a minimum number of signals during the synchronization maintenance phase.

[0402] - - In particular, it can effectively mitigate power consumption issues caused by prolonged standby / monitoring in NTN environments.

[0403] - Ensuring scalability for future on-demand SSB / energy saving scenarios

[0404] It can provide foundational technology for energy-efficient synchronous structures in next-generation mobile communication environments.

[0405] The above [Proposed Plan #11-2] may be applied in combination with other proposed plans within the scope where the proposed operations do not conflict.

[0406] In non-terrestrial networks (NTN) or long-cycle downlink synchronization environments, the following problems may exist.

[0407] - Problem of unnecessary continuous monitoring in conventional synchronization signal blocks

[0408] Even after the terminal has already obtained rough synchronization through a simplified synchronization signal block, there may be inefficiency in the conventional method where the first synchronization signal block (SSB) must always be monitored periodically.

[0409] - Continued terminal burden due to conventional SSB monitoring

[0410] Since the first synchronization signal block includes a PBCH, the terminal may still have a high complexity of monitoring and decoding burden.

[0411] [Proposed Method #12] When a terminal can transmit an uplink wake-up signal (UL WUS) to a base station for a request for synchronous signal block (SSB) and / or system information block (SIB) and / or random access channel (RACH) resources, if the base station is an NTN base station, one or more of the following operations may be supported.

[0412] (1) Satellite information can be utilized in the downlink synchronization process for UL WUS transmission.

[0413] A. For example, downlink synchronization information of (adjacent) cell(s) serviced from the same satellite can be utilized in the serving cell downlink synchronization process.

[0414] (2) Satellite information can be utilized in the transmission power control process for UL WUS transmission.

[0415] A. For example, (expected) path attenuation can be calculated based on the relative positions of the satellite and the terminal and utilized in the transmission power control process.

[0416] (3) Satellite information can be used when determining the transmission beam for UL WUS transmission.

[0417] A. For example, the transmission beam can be determined based on the relative positions of the satellite and the terminal.

[0418] (4) Satellite information can be used for UL WUS transmission trigger conditions.

[0419] A. For example, if the satellite approaches within a certain distance from the terminal, UL WUS transmission may be triggered.

[0420] Here, for example, the satellite information may include GNSS (global navigation satellite system) information and / or satellite ephemeris information, etc.

[0421] Here, for example, satellite ephemeris information may be information including the satellite's orbital movement, position, etc.

[0422] Here, for example, the synchronization signal block (SSB) may be a signal transmitted for synchronization and system information detection, and may be composed of a PSS (primary synchronous signal) and / or an SSS (secondary synchronous signal) and / or a PBCH (physical broadcast channel).

[0423] Here, for example, in the case of an on-demand SSB requested and transmitted by the UL WUS, the PBCH may contain information different from the PBCH within the conventional SSB. For example, the PBCH within the on-demand SSB may include (subsequent) (on-demand) SSB resource setting information and / or RACH resource setting information linked to the (on-demand) SSB. For example, the on-demand SSB may also be restricted from being utilized as a measurement resource for RRM (radio resource management) and / or BM (beam management), etc. For example, or the base station may set / instruct the terminal whether to allow the on-demand SSB as a measurement resource.

[0424] Here, for example, whether the UL WUS is supported may be determined by whether it is provided through a synchronization signal block and / or SIB, or by whether a (specific) downlink synchronization signal supported for UL WUS transmission is detected. For example, when a unique downlink synchronization signal can be transmitted for UL WUS transmission, the terminal may expect that the corresponding base station will support UL WUS reception when the unique synchronization signal is detected. For example, or the terminal may perform UL WUS transmission without checking whether the UL WUS signal is supported, but may have a waiting time constraint between the UL WUS transmission and the next transmission.

[0425] Here, for example, during the transmission power control process for the above UL WUS transmission, the target reception power and / or target transmission power may be (pre-)defined / set between the base station and the terminal.

[0426] For example, in a next-generation mobile communication system based on a non-terrestrial network according to an embodiment of the present disclosure, a single satellite can provide service over a very wide area, and the number of service target cells / beams may be hundreds or more. Here, for example, due to the physical characteristics of the satellite, it may be difficult to simultaneously support (nominal) (maximum) EIRP (effective isotopically radiated power) for all service target cells. Therefore, the NTN may perform downlink transmission to avoid simultaneous transmission between cells as much as possible. Here, for example, the NTN may be configured to avoid simultaneous transmission as much as possible for common signal(s), such as synchronization signal blocks and / or SIBs (system information blocks) for synchronization and system information acquisition. Here, for example, the NTN may consider a method of performing transmission of said common signals when requested by a terminal, instead of lowering the (time axis) transmission density of the common signals. For example, a terminal may transmit an uplink wake-up signal (UL WUS) to a base station to request synchronous signal block (SSB) and / or system information block (SIB) and / or random access channel (RACH) resources. Here, for example, if the base station is an NTN base station, the terminal may support the UL WUS transmission process in a smarter way. For example, the terminal may support UL WUS transmission by utilizing satellite information as follows.

[0427] (1) Satellite information can be utilized in the downlink synchronization process for UL WUS transmission.

[0428] A. For example, downlink synchronization information of (adjacent) cell(s) serviced from the same satellite can be utilized in the serving cell downlink synchronization process.

[0429] (2) Satellite information can be utilized in the transmission power control process for UL WUS transmission.

[0430] A. For example, (expected) path attenuation can be calculated based on the relative positions of the satellite and the terminal and utilized in the transmission power control process.

[0431] (3) Satellite information can be used when determining the transmission beam for UL WUS transmission.

[0432] A. For example, the transmission beam can be determined based on the relative positions of the satellite and the terminal.

[0433] (4) Satellite information can be used for UL WUS transmission trigger conditions.

[0434] A. For example, if the satellite approaches within a certain distance from the terminal, UL WUS transmission may be triggered.

[0435] Here, for example, the satellite information may include GNSS (global navigation satellite system) information and / or satellite ephemeris information, etc. Here, for example, the satellite ephemeris information may be information including the satellite's orbital movement, position, etc. Here, for example, the synchronization signal block (SSB) may be a signal transmitted for synchronization and system information detection, and may be composed of a PSS (primary synchronous signal) and / or SSS (secondary synchronous signal) and / or PBCH (physical broadcast channel). Here, for example, in the case of an on-demand SSB transmitted upon request by the UL WUS, the PBCH may include information different from the PBCH within the conventional SSB. For example, a PBCH within an on-demand SSB may include (subsequent) (on-demand) SSB resource configuration information and / or RACH resource configuration information linked with the (on-demand) SSB. According to the proposed method of the present disclosure, a terminal transmitting UL WUS to an NTN base station has the advantage of supporting an efficient UL WUS transmission process by additionally utilizing satellite information compared to a terminal transmitting UL WUS to a non-NTN base station.

[0436] According to the present disclosure, the following effects can be obtained.

[0437] - Establishment of a two-step synchronization structure for terminal operation

[0438] - - The terminal can (i) acquire primary synchronization with a simplified synchronization signal block based on a second sync raster, and (ii) request and monitor the first synchronization signal block only when necessary to perform precise synchronization and acquire system information.

[0439] Accordingly, unnecessary conventional SSB continuous monitoring has been eliminated.

[0440] - Further reduction in terminal power consumption and computational complexity

[0441] Since the reception of conventional SSB (including PBCH) is limited to a request-based system, the terminal may only need to process a minimum number of signals during the synchronization maintenance phase.

[0442] - - In particular, it can effectively mitigate power consumption issues caused by prolonged standby / monitoring in NTN environments.

[0443] - Ensuring scalability for future on-demand SSB / energy saving scenarios

[0444] It can provide foundational technology for energy-efficient synchronous structures in next-generation mobile communication environments.

[0445] The above [Proposed Plan #12] may be applied in combination with other proposed plans(s) to the extent that the proposed operations do not conflict.

[0446] Although the embodiments of the present disclosure are described as examples of non-ground networks, they can be extended to ground networks as well.

[0447] Combinations of various embodiments of the present disclosure may be applied differently depending on the payload type of the satellite (e.g., regenerative payload or transparent payload).

[0448] Combinations of various embodiments of the present disclosure may be applied differently to the type of non-geostational network node (e.g., GEO (geostationary earth orbit), NGEO (non-geostationary earth orbit), LEO (low earth orbit), MEO (medium earth orbit), HASP (high altitude satellite platform), drone) or altitude or fixed beam footprint or cell-moving beam footprint.

[0449] For example, in the embodiments of the present disclosure, the TDD setting and utilization are not limited to the TDD band, and can be extended to combinations of the FDD band and / or specific DL band and / or UL band.

[0450] For example, in an embodiment of the present disclosure, a base station or network node may be a satellite. For example, a base station or network node may be associated with a transparent payload. For example, a base station or network node may be associated with a regenerated payload.

[0451] A combination of embodiments of the present disclosure may operate in conjunction with each other.

[0452] Various embodiments of the present disclosure may be applied differently depending on the link type (DL, UL, SL) and / or the data type (SIB, group cast, unicast) and / or the search space type (CSS (common search space), USS (UE-specific search space)) where the scheduling PDCCH is detected and / or the base station node type and / or altitude and / or whether there is a power constraint. For example, a combination of various embodiments of the present disclosure may be applied only when involved in SIB transmission.

[0453] For example, in the present disclosure, "specific threshold" may mean a threshold that is predefined or (pre-)set by an upper layer (including the application layer) of a network, base station, or terminal. For example, in the present disclosure, "specific set value" may mean a value that is predefined or (pre-)set by an upper layer (including the application layer) of a network, base station, or terminal. For example, in the present disclosure, "set by the network / base station" may mean an action in which a base station sets to a UE (pre-) through upper layer RRC signaling, sets / signals to a UE through MAC CE, or signals to a UE through DCI.

[0454] For example, in this disclosure, various names are exemplary and may be replaced or considered as other names performing the same or similar functions based on the content described in each step (regardless of the name).

[0455] FIG. 21 illustrates a procedure performed by a first device according to one embodiment of the present disclosure. The embodiment of FIG. 21 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, suggestions, methods, and / or operations of said embodiments may be omitted.

[0456] Referring to FIG. 21, in step S2110, the first device can obtain information related to the second sync raster. In step S2120, the first device can receive a second synchronization signal block from the second device based on the information related to the second sync raster. In step S2130, the first device can obtain synchronization based on the second synchronization signal block. For example, the second synchronization signal block may be a simplified synchronization signal block compared to the first synchronization signal block on the first sync raster.

[0457] For example, the simplified synchronization signal block above includes only synchronization signals, method.

[0458] For example, the synchronization signal may include at least one of a primary synchronization signal and a secondary synchronization signal.

[0459] For example, the first device may acquire information related to the first sync raster. For example, based on the information related to the first sync raster, the first device may monitor the first synchronization signal block. For example, the first synchronization signal block may include a primary synchronization signal, a secondary synchronization signal, and a physical broadcast channel.

[0460] For example, the second synchronization signal block can be received independently of the first synchronization signal block.

[0461] For example, the first device may transmit a signal to the second device to request the first synchronization signal block. For example, the information related to the first sync raster may be obtained based on the signal to request the first synchronization signal block. For example, the monitoring of the first synchronization signal block may be performed based on the signal to request the first synchronization signal block.

[0462] For example, the signal for requesting the first synchronization signal block may be a UL (uplink) WUS (wake-up signal).

[0463] For example, the first sink raster may be an on-demand sink raster based on the second sink raster. For example, the second sink raster may be an always-on sink raster.

[0464] For example, a method in which the support of the second synchronization signal block is provided based on the first synchronization signal block.

[0465] For example, the first device may transmit a signal to the second device to request a resource for a random access channel based on the synchronization. For example, the first device may transmit the random access channel to the second device on the resource for the random access channel.

[0466] For example, the transmission of a signal to request the resource for the random access channel can be triggered based on celestial information.

[0467] For example, a signal to request the resource for the random access channel may be UL WUS.

[0468] For example, the first device may be a terminal. For example, the second device may be at least one of a base station or a non-terrestrial network.

[0469] The proposed method above may be applied to a device according to various embodiments of the present disclosure. For example, a processor (102) of a first device (100) may obtain information related to a second sync raster (for example, the processor (102) of the first device (100) may control a transceiver (106) to obtain information related to the second sync raster). For example, the processor (102) of the first device (100) may receive a second sync signal block from a second device based on the information related to the second sync raster (for example, the processor (102) of the first device (100) may control a transceiver (106) to receive a second sync signal block from a second device based on the information related to the second sync raster). For example, the processor (102) of the first device (100) can obtain synchronization based on the second synchronization signal block (for example, the processor (102) of the first device (100) can control the transceiver (106) to obtain synchronization based on the second synchronization signal block). For example, the second synchronization signal block may be a simplified synchronization signal block compared to the first synchronization signal block on the first sync raster.

[0470] According to one embodiment of the present disclosure, a first device may be provided. For example, the first device may include at least one transceiver; at least one processor; and at least one memory connected to the at least one processor and storing instructions. For example, the instructions may cause the first device, based on execution by the at least one processor: to obtain information related to a second sync raster; to receive a second synchronization signal block from a second device based on the information related to the second sync raster; and to obtain synchronization based on the second synchronization signal block. For example, the second synchronization signal block may be a simplified synchronization signal block compared to a first synchronization signal block on a first sync raster.

[0471] For example, the simplified synchronization signal block above includes only synchronization signals, method.

[0472] For example, the synchronization signal may include at least one of a primary synchronization signal and a secondary synchronization signal.

[0473] For example, the first device may acquire information related to the first sync raster. For example, based on the information related to the first sync raster, the first device may monitor the first synchronization signal block. For example, the first synchronization signal block may include a primary synchronization signal, a secondary synchronization signal, and a physical broadcast channel.

[0474] For example, the second synchronization signal block can be received independently of the first synchronization signal block.

[0475] For example, the first device may transmit a signal to the second device to request the first synchronization signal block. For example, the information related to the first sync raster may be obtained based on the signal to request the first synchronization signal block. For example, the monitoring of the first synchronization signal block may be performed based on the signal to request the first synchronization signal block.

[0476] For example, the signal for requesting the first synchronization signal block may be a UL (uplink) WUS (wake-up signal).

[0477] For example, the first sink raster may be an on-demand sink raster based on the second sink raster. For example, the second sink raster may be an always-on sink raster.

[0478] For example, a method in which the support of the second synchronization signal block is provided based on the first synchronization signal block.

[0479] For example, the first device may transmit a signal to the second device to request a resource for a random access channel based on the synchronization. For example, the first device may transmit the random access channel to the second device on the resource for the random access channel.

[0480] For example, the transmission of a signal to request the resource for the random access channel can be triggered based on celestial information.

[0481] For example, a signal to request the resource for the random access channel may be UL WUS.

[0482] For example, the first device may be a terminal. For example, the second device may be at least one of a base station or a non-terrestrial network.

[0483] According to one embodiment of the present disclosure, a processing device (configured to control a first device) may be provided. For example, the processing device may include at least one processor; and at least one memory connected to the at least one processor and storing instructions. For example, the instructions may cause the first device, based on execution by the at least one processor: to obtain information related to a second sync raster; to receive a second synchronization signal block from the second device based on the information related to the second sync raster; and to obtain synchronization based on the second synchronization signal block. For example, the second synchronization signal block may be a simplified synchronization signal block compared to a first synchronization signal block on a first sync raster.

[0484] According to one embodiment of the present disclosure, a non-transient computer-readable storage medium recording instructions may be provided. For example, when the instructions are executed, the first device may: acquire information related to a second sync raster; receive a second synchronization signal block from a second device based on the information related to the second sync raster; and acquire synchronization based on the second synchronization signal block. For example, the second synchronization signal block may be a simplified synchronization signal block compared to a first synchronization signal block on a first sync raster.

[0485] FIG. 22 illustrates a procedure performed by a second device according to one embodiment of the present disclosure. The embodiment of FIG. 22 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, suggestions, methods, and / or operations of said embodiments may be omitted.

[0486] Referring to FIG. 22, in step S2210, the second device may transmit information related to the second sync raster to the first device. In step S2220, based on the information related to the second sync raster, the second device may transmit a second synchronization signal block to the first device. In step S2230, based on the second synchronization signal block, the second device may obtain synchronization. For example, the second synchronization signal block may be a simplified synchronization signal block compared to the first synchronization signal block on the first sync raster.

[0487] For example, the simplified synchronization signal block above includes only synchronization signals, method.

[0488] For example, the synchronization signal may include at least one of a primary synchronization signal and a secondary synchronization signal.

[0489] For example, the second device may transmit information related to the first sync raster to the first device. For example, based on the information related to the first sync raster, the first device may monitor the first sync signal block. For example, the first sync signal block may include a primary sync signal, a secondary sync signal, and a physical broadcast channel.

[0490] For example, the second synchronization signal block can be received independently of the first synchronization signal block.

[0491] For example, a second device may receive a signal from a first device to request the first synchronization signal block. For example, the information related to the first sync raster may be obtained based on the signal to request the first synchronization signal block. For example, the monitoring of the first synchronization signal block may be performed based on the signal to request the first synchronization signal block.

[0492] For example, the signal for requesting the first synchronization signal block may be a UL (uplink) WUS (wake-up signal).

[0493] For example, the first sink raster may be an on-demand sink raster based on the second sink raster. For example, the second sink raster may be an always-on sink raster.

[0494] For example, a method in which the support of the second synchronization signal block is provided based on the first synchronization signal block.

[0495] For example, the second device may receive a signal from the first device to request a resource for a random access channel based on the synchronization. For example, the second device may receive the random access channel on the resource for the random access channel from the first device.

[0496] For example, the transmission of a signal to request the resource for the random access channel can be triggered based on celestial information.

[0497] For example, a signal to request the resource for the random access channel may be UL WUS.

[0498] For example, the first device may be a terminal. For example, the second device may be at least one of a base station or a non-terrestrial network.

[0499] The proposed method above may be applied to a device according to various embodiments of the present disclosure. For example, the processor (202) of the second device (200) may transmit information related to a second sync raster from the second device to the first device (for example, the processor (202) of the second device (200) may control the transceiver (206) so that the second device transmits information related to a second sync raster to the first device). For example, the processor (202) of the second device (200) may transmit a second synchronization signal block from the second device to the first device based on the information related to the second sync raster (for example, the processor (202) of the second device (200) may control the transceiver (206) so that the second device transmits a second synchronization signal block to the first device based on the information related to the second sync raster). For example, the processor (202) of the second device (200) can enable the second device to acquire synchronization based on the second synchronization signal block (for example, the processor (202) of the second device (200) can control the transceiver (206) so that the second device acquires synchronization based on the second synchronization signal block). For example, the second synchronization signal block may be a simplified synchronization signal block compared to the first synchronization signal block on the first sync raster.

[0500] According to one embodiment of the present disclosure, a second device may be provided. For example, the second device may include at least one transceiver; at least one processor; and at least one memory connected to the at least one processor and storing instructions. For example, based on the instructions executed by the at least one processor, the second device may: transmit information related to a second sync raster to the first device; transmit a second synchronization signal block to the first device based on the information related to the second sync raster; and acquire synchronization based on the second synchronization signal block. For example, the second synchronization signal block may be a simplified synchronization signal block compared to a first synchronization signal block on a first sync raster.

[0501] For example, the simplified synchronization signal block above includes only synchronization signals, method.

[0502] For example, the synchronization signal may include at least one of a primary synchronization signal and a secondary synchronization signal.

[0503] For example, the second device may transmit information related to the first sync raster to the first device. For example, based on the information related to the first sync raster, the first device may monitor the first sync signal block. For example, the first sync signal block may include a primary sync signal, a secondary sync signal, and a physical broadcast channel.

[0504] For example, the second synchronization signal block can be received independently of the first synchronization signal block.

[0505] For example, a second device may receive a signal from a first device to request the first synchronization signal block. For example, the information related to the first sync raster may be obtained based on the signal to request the first synchronization signal block. For example, the monitoring of the first synchronization signal block may be performed based on the signal to request the first synchronization signal block.

[0506] For example, the signal for requesting the first synchronization signal block may be a UL (uplink) WUS (wake-up signal).

[0507] For example, the first sink raster may be an on-demand sink raster based on the second sink raster. For example, the second sink raster may be an always-on sink raster.

[0508] For example, a method in which the support of the second synchronization signal block is provided based on the first synchronization signal block.

[0509] For example, the second device may receive a signal from the first device to request a resource for a random access channel based on the synchronization. For example, the second device may receive the random access channel on the resource for the random access channel from the first device.

[0510] For example, the transmission of a signal to request the resource for the random access channel can be triggered based on celestial information.

[0511] For example, a signal to request the resource for the random access channel may be UL WUS.

[0512] For example, the first device may be a terminal. For example, the second device may be at least one of a base station or a non-terrestrial network.

[0513] According to one embodiment of the present disclosure, a processing device (configured to control a second device) may be provided. For example, the processing device may include at least one processor; and at least one memory connected to the at least one processor and storing instructions. For example, the instructions may cause the second device, based on execution by the at least one processor: to transmit information related to a second sync raster to the first device; to transmit a second synchronization signal block to the first device based on the information related to the second sync raster; and to obtain synchronization based on the second synchronization signal block. For example, the second synchronization signal block may be a simplified synchronization signal block compared to a first synchronization signal block on a first sync raster.

[0514] According to one embodiment of the present disclosure, a non-transient computer-readable storage medium recording instructions may be provided. For example, when the instructions are executed, the second device may cause: to transmit information related to a second sync raster to the first device; to transmit a second synchronization signal block to the first device based on the information related to the second sync raster; and to obtain synchronization based on the second synchronization signal block. For example, the second synchronization signal block may be a simplified synchronization signal block compared to a first synchronization signal block on a first sync raster.

[0515] According to the present disclosure, the following effects can be obtained.

[0516] - Reduction in terminal synchronous search complexity

[0517] Since the simplified synchronization signal block is searched only on the second sync raster, the terminal can acquire synchronization in an environment where the number of frequency candidates is significantly reduced without needing to search the entire dense first sync raster.

[0518] Accordingly, search complexity can be significantly reduced.

[0519] - Maintain synchronous performance even in long-cycle SSB environments

[0520] Even if the transmission period of the conventional SSB is extended, the terminal can maintain / reacquire synchronization more quickly and stably through a simplified second synchronization signal block.

[0521] - - It can be particularly effective in environments requiring an SSB cycle of 160 ms or more, such as NTN.

[0522] - Reduced terminal power consumption

[0523] By utilizing only a simplified synchronization signal block that does not include a PBCH, unnecessary demodulation and decoding operations are eliminated, thereby reducing terminal power consumption.

[0524] - Conventional synchronization signal block performance protection

[0525] By receiving the simplified synchronization signal block at a frequency position distinct from the first sync raster, interference with the detection performance and system information transmission performance of the conventional SSB can be avoided.

[0526] According to the present disclosure, the following effects can also be obtained.

[0527] - Establishment of a two-step synchronization structure for terminal operation

[0528] - - The terminal can (i) acquire primary synchronization with a simplified synchronization signal block based on a second sync raster, and (ii) request and monitor the first synchronization signal block only when necessary to perform precise synchronization and acquire system information.

[0529] Accordingly, unnecessary conventional SSB continuous monitoring has been eliminated.

[0530] - Further reduction in terminal power consumption and computational complexity

[0531] Since the reception of conventional SSB (including PBCH) is limited to a request-based system, the terminal may only need to process a minimum number of signals during the synchronization maintenance phase.

[0532] - - In particular, it can effectively mitigate power consumption issues caused by prolonged standby / monitoring in NTN environments.

[0533] - Ensuring scalability for future on-demand SSB / energy saving scenarios

[0534] It can provide foundational technology for energy-efficient synchronous structures in next-generation mobile communication environments.

[0535] The following describes an apparatus to which various embodiments of the present disclosure may be applied.

[0536] Although not limited to, the various descriptions, functions, procedures, proposals, methods, and / or flowcharts of operation disclosed in this document may be applied to various fields requiring wireless communication / connection (e.g., 5G, 6G, etc.) between devices.

[0537] Examples are provided in more detail below with reference to the drawings. In the following drawings and descriptions, the same reference numerals may represent the same or corresponding hardware blocks, software blocks, or function blocks unless otherwise described.

[0538] FIG. 23 shows a communication system (1) according to one embodiment of the present disclosure. The embodiment of FIG. 23 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, suggestions, methods and / or operations of the embodiments may be omitted.

[0539] Referring to FIG. 23, a communication system (1) to which various embodiments of the present disclosure are applied includes a wireless device, a base station, and a network. Here, the wireless device refers to a device that performs communication using wireless access technology (e.g., 5G NR (New RAT), LTE (Long Term Evolution), 6G) and may be referred to as a communication / wireless / 5G / 6G device. Although not limited thereto, the wireless device may include a robot (100a), a vehicle (100b-1, 100b-2), an XR (eXtended Reality) device (100c), a hand-held device (100d), a home appliance (100e), an IoT (Internet of Thing) device (100f), and an AI device / server (400). For example, the vehicle may include a vehicle equipped with wireless communication functions, an autonomous vehicle, a vehicle capable of performing inter-vehicle communication, etc. Here, the vehicle may include an Uncrewed Aerial Vehicle (UAV) (e.g., a drone) and / or an Aerial Vehicle (AV) (e.g., Advanced Air Mobility). The XR device includes an Augmented Reality (AR) / Virtual Reality (VR) / Mixed Reality (MR) device and may be implemented in the form of a Head-Mounted Device (HMD), a Head-Up Display (HUD) equipped in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance, digital signage, a vehicle, a robot, etc. The portable device may include a smartphone, a smartpad, a wearable device (e.g., a smartwatch, smart glasses), a computer (e.g., a laptop, etc.). The home appliance may include a TV, a refrigerator, a washing machine, etc. The IoT device may include a sensor, a smart meter, etc. For example, a base station and a network may be implemented as a wireless device, and a specific wireless device (200a) may operate as a base station / network node to other wireless devices.

[0540] Here, the wireless communication technology implemented in the wireless devices (100a to 100f) of the present disclosure may include LTE, NR, and 6G, as well as NB-IoT (Narrowband Internet of Things) for low-power communication. In this case, for example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology and may be implemented according to standards such as LTE Cat NB1 and / or LTE Cat NB2, but is not limited to the names mentioned above. Additionally, or generally, the wireless communication technology implemented in the wireless devices (100a to 100f) of the present disclosure may perform communication based on LTE-M technology. In this case, for example, LTE-M technology may be an example of LPWAN technology and may be referred to by various names such as eMTC (enhanced Machine Type Communication). For example, LTE-M technology may be implemented in at least one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-Bandwidth Limited), 5) LTE-MTC, 6) LTE Machine Type Communication, and / or 7) LTE M, and is not limited to the names mentioned above. Additionally or generally, wireless communication technology implemented in the wireless devices (100a to 100f) of the present disclosure may include at least one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN) for low-power communication, and is not limited to the names mentioned above. As an example, ZigBee technology can create personal area networks (PANs) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and may be referred to by various names.

[0541] Wireless devices (100a to 100f) can be connected to a network (300) through a base station (200). Artificial Intelligence (AI) technology may be applied to the wireless devices (100a to 100f), and wireless devices (100a to 100f) can be connected to an AI server (400) through the network (300). The network (300) can be configured using a 3G network, a 4G (e.g., LTE) network, a 5G (e.g., NR) network, or a 6G network. Wireless devices (100a to 100f) may communicate with each other through the base station (200) / network (300), but they may also communicate directly (e.g., sidelink communication) without going through the base station / network. For example, vehicles (100b-1, 100b-2) can communicate directly (e.g., V2V (Vehicle to Vehicle) / V2X (Vehicle to everything) communication). Also, IoT devices (e.g., sensors) can communicate directly with other IoT devices (e.g., sensors) or other wireless devices (100a to 100f).

[0542] Wireless communication / connection (150a, 150b, 150c) can be established between wireless devices (100a~100f) / base station (200) and base station (200) / base station (200). Here, wireless communication / connection can be achieved through various wireless access technologies (e.g., 5G NR, 6G, etc.), such as uplink / downlink communication (150a), sidelink communication (150b) (or D2D communication), and inter-base station communication (150c) (e.g., relay, IAB (Integrated Access Backhaul)). Through wireless communication / connection (150a, 150b, 150c), wireless devices and base stations / wireless devices, and base stations and base stations can transmit / receive wireless signals to / from each other. For example, wireless communication / connection (150a, 150b, 150c) can transmit / receive signals through various physical channels. To this end, based on the various proposals of the present disclosure, at least some of the following may be performed: various configuration information setting processes for transmitting / receiving wireless signals, various signal processing processes (e.g., channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.), resource allocation processes, etc.

[0543] FIG. 24 shows a wireless device according to one embodiment of the present disclosure. The embodiment of FIG. 24 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, suggestions, methods, and / or operations of the embodiments may be omitted.

[0544] Referring to FIG. 24, the first wireless device (100) and the second wireless device (200) can transmit and receive wireless signals through various wireless access technologies (e.g., LTE, NR). Here, {the first wireless device (100), the second wireless device (200)} may correspond to {wireless device (100x), base station (200)} and / or {wireless device (100x), wireless device (100x)} of FIG. 23.

[0545] The first wireless device (100) includes one or more processors (102) and one or more memories (104), and may additionally include one or more transceivers (106) and / or one or more antennas (108). The processor (102) controls the memory (104) and / or transceivers (106) and may be configured to implement the descriptions, functions, procedures, proposals, methods and / or sequences of operation disclosed in this document. For example, the processor (102) may process information within the memory (104) to generate a first information / signal and then transmit a wireless signal containing the first information / signal through the transceiver (106). Additionally, the processor (102) may receive a wireless signal containing a second information / signal through the transceiver (106) and then store information obtained from the signal processing of the second information / signal in the memory (104). The memory (104) may be connected to the processor (102) and may store various information related to the operation of the processor (102). For example, the memory (104) may store software code containing instructions for performing some or all of the processes controlled by the processor (102) or for performing the descriptions, functions, procedures, proposals, methods, and / or operation sequence diagrams disclosed in this document. Here, the processor (102) and the memory (104) may be part of a communication modem / circuit / chip designed to implement wireless communication technology (e.g., LTE, NR). The transceiver (106) may be connected to the processor (102) and may transmit and / or receive wireless signals through one or more antennas (108). The transceiver (106) may include a transmitter and / or receiver. The transceiver (106) may be combined with an RF (Radio Frequency) unit. In the present disclosure, a wireless device may refer to a communication modem / circuit / chip.

[0546] The second wireless device (200) includes one or more processors (202) and one or more memories (204), and may additionally include one or more transceivers (206) and / or one or more antennas (208). The processor (202) controls the memory (204) and / or transceivers (206) and may be configured to implement the descriptions, functions, procedures, proposals, methods and / or sequences of operation disclosed in this document. For example, the processor (202) may process information within the memory (204) to generate a third information / signal and then transmit a wireless signal containing the third information / signal through the transceiver (206). Additionally, the processor (202) may receive a wireless signal containing a fourth information / signal through the transceiver (206) and then store information obtained from the signal processing of the fourth information / signal in the memory (204). Memory (204) may be connected to the processor (202) and may store various information related to the operation of the processor (202). For example, memory (204) may store software code containing instructions for performing some or all of the processes controlled by the processor (202) or for performing the descriptions, functions, procedures, proposals, methods, and / or sequence diagrams of operation disclosed in this document. Here, the processor (202) and memory (204) may be part of a communication modem / circuit / chip designed to implement wireless communication technology (e.g., LTE, NR). A transceiver (206) may be connected to the processor (202) and may transmit and / or receive wireless signals through one or more antennas (208). The transceiver (206) may include a transmitter and / or receiver. The transceiver (206) may be interchangeable with an RF unit. In this disclosure, a wireless device may refer to a communication modem / circuit / chip.

[0547] Hereinafter, hardware elements of the wireless device (100, 200) will be described in more detail. Although not limited thereto, one or more protocol layers may be implemented by one or more processors (102, 202). For example, one or more processors (102, 202) may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, SDAP). One or more processors (102, 202) may generate one or more Protocol Data Units (PDUs) and / or Service Data Units (SDUs) according to the descriptions, functions, procedures, proposals, methods, and / or flowcharts of operation disclosed in this document. One or more processors (102, 202) may generate messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or flowcharts of operation disclosed in this document. One or more processors (102, 202) may generate a signal (e.g., baseband signal) containing a PDU, SDU, message, control information, data, or information according to the functions, procedures, proposals, and / or methods disclosed in this document and provide it to one or more transceivers (106, 206). One or more processors (102, 202) may receive a signal (e.g., baseband signal) from one or more transceivers (106, 206) and may obtain a PDU, SDU, message, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed in this document.

[0548] One or more processors (102, 202) may be referred to as a controller, microcontroller, microprocessor, or microcomputer. One or more processors (102, 202) may be implemented by hardware, firmware, software, or a combination thereof. For example, one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), one or more Digital Signal Processing Devices (DSPDs), one or more Programmable Logic Devices (PLDs), or one or more Field Programmable Gate Arrays (FPGAs) may be included in one or more processors (102, 202). The descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed in this document may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc. Firmware or software configured to perform the descriptions, functions, procedures, proposals, methods, and / or operation sequences disclosed in this document may be contained in one or more processors (102, 202) or stored in one or more memories (104, 204) and driven by one or more processors (102, 202). The descriptions, functions, procedures, proposals, methods, and / or operation sequences disclosed in this document may be implemented using firmware or software in the form of code, instructions, and / or sets of instructions.

[0549] One or more memories (104, 204) may be connected to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, code, instructions, and / or commands. One or more memories (104, 204) may be composed of ROM, RAM, EPROM, flash memory, hard drive, registers, cache memory, computer read storage media, and / or combinations thereof. One or more memories (104, 204) may be located inside and / or outside of one or more processors (102, 202). Additionally, one or more memories (104, 204) may be connected to one or more processors (102, 202) through various technologies such as wired or wireless connections.

[0550] One or more transceivers (106, 206) may transmit user data, control information, wireless signals / channels, etc., as mentioned in the methods and / or operation flowcharts, etc., of this document to one or more other devices. One or more transceivers (106, 206) may receive user data, control information, wireless signals / channels, etc., as mentioned in the descriptions, functions, procedures, proposals, methods and / or operation flowcharts, etc., disclosed in this document from one or more other devices. For example, one or more transceivers (106, 206) may be connected to one or more processors (102, 202) and may transmit and receive wireless signals. For example, one or more processors (102, 202) may control one or more transceivers (106, 206) to transmit user data, control information, or wireless signals to one or more other devices. Additionally, one or more processors (102, 202) may control one or more transceivers (106, 206) to receive user data, control information, or wireless signals from one or more other devices. Additionally, one or more transceivers (106, 206) may be connected to one or more antennas (108, 208), and one or more transceivers (106, 206) may be configured to transmit and receive user data, control information, wireless signals / channels, etc., as described in the descriptions, functions, procedures, proposals, methods, and / or flowcharts of operation disclosed in this document through one or more antennas (108, 208). In this document, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers (106, 206) can convert the received wireless signal / channel, etc. from an RF band signal to a baseband signal in order to process the received user data, control information, wireless signal / channel, etc. using one or more processors (102, 202).One or more transceivers (106, 206) can convert user data, control information, wireless signals / channels, etc. processed using one or more processors (102, 202) from baseband signals to RF band signals. To this end, one or more transceivers (106, 206) may include (analog) oscillators and / or filters.

[0551] FIG. 25 illustrates a signal processing circuit for a transmission signal according to one embodiment of the present disclosure. The embodiment of FIG. 25 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, suggestions, methods, and / or operations of the embodiments may be omitted.

[0552] Referring to FIG. 25, the signal processing circuit (1000) may include a scrambler (1010), a modulator (1020), a layer mapper (1030), a precoder (1040), a resource mapper (1050), and a signal generator (1060). Although not limited thereto, the operation / function of FIG. 25 may be performed in the processor (102, 202) and / or transceiver (106, 206) of FIG. 24. The hardware elements of FIG. 25 may be implemented in the processor (102, 202) and / or transceiver (106, 206) of FIG. 24. For example, blocks 1010 through 1060 may be implemented in the processor (102, 202) of FIG. 24. Additionally, blocks 1010 to 1050 may be implemented in the processor (102, 202) of FIG. 24, and block 1060 may be implemented in the transceiver (106, 206) of FIG. 24.

[0553] The codeword can be converted into a wireless signal through the signal processing circuit (1000) of FIG. 25. Here, the codeword is an encoded bit sequence of an information block. The information block may include a transmission block (e.g., UL-SCH transmission block, DL-SCH transmission block). The wireless signal can be transmitted through various physical channels (e.g., PUSCH, PDSCH).

[0554] Specifically, a codeword can be converted into a scrambled bit sequence by a scrambler (1010). The scrambled sequence used for scrambling is generated based on an initialization value, which may include ID information of a wireless device, etc. The scrambled bit sequence can be modulated into a modulation symbol sequence by a modulator (1020). The modulation method may include pi / 2-BPSK (pi / 2-Binary Phase Shift Keying), m-PSK (m-Phase Shift Keying), m-QAM (m-Quadrature Amplitude Modulation), etc. The complex modulation symbol sequence can be mapped to one or more transmission layers by a layer mapper (1030). The modulation symbols of each transmission layer can be mapped to the corresponding antenna port(s) by a precoder (1040) (precoding). The output z of the precoder (1040) can be obtained by multiplying the output y of the layer mapper (1030) by an N*M precoding matrix W. Here, N is the number of antenna ports and M is the number of transmission layers. Here, the precoder (1040) can perform precoding after performing transform precoding (e.g., DFT transform) on the complex modulation symbols. Additionally, the precoder (1040) can perform precoding without performing transform precoding.

[0555] A resource mapper (1050) can map the modulation symbols of each antenna port to a time-frequency resource. The time-frequency resource may include multiple symbols (e.g., CP-OFDMA symbols, DFT-s-OFDMA symbols) in the time domain and multiple subcarriers in the frequency domain. A signal generator (1060) generates a radio signal from the mapped modulation symbols, and the generated radio signal can be transmitted to another device through each antenna. To this end, the signal generator (1060) may include an Inverse Fast Fourier Transform (IFFT) module, a Cyclic Prefix (CP) inserter, a Digital-to-Analog Converter (DAC), a frequency uplink converter, etc.

[0556] The signal processing process for a received signal in a wireless device can be configured as the inverse of the signal processing process (1010–1060) of FIG. 25. For example, a wireless device (e.g., 100, 200 in FIG. 24) can receive a wireless signal from the outside through an antenna port / transceiver. The received wireless signal can be converted into a baseband signal through a signal restorer. To this end, the signal restorer may include a frequency downlink converter, an analog-to-digital converter (ADC), a CP remover, and a Fast Fourier Transform (FFT) module. Subsequently, the baseband signal can be restored into a codeword through a resource de-mapper process, a postcoding process, a demodulation process, and a de-scrambling process. The codeword can be restored into the original information block through decoding. Accordingly, a signal processing circuit (not shown) for a received signal may include a signal restorer, a resource de-mapper, a postcoder, a demodulator, a de-scrambler, and a decoder.

[0557] FIG. 26 illustrates a wireless device according to one embodiment of the present disclosure. The wireless device may be implemented in various forms depending on the use-example / service (see FIG. 23). The embodiment of FIG. 26 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.

[0558] Referring to FIG. 26, the wireless device (100, 200) corresponds to the wireless device (100, 200) of FIG. 24 and may be composed of various elements, components, units / parts, and / or modules. For example, the wireless device (100, 200) may include a communication unit (110), a control unit (120), a memory unit (130), and additional elements (140). The communication unit may include a communication circuit (112) and transceiver(s) (114). For example, the communication circuit (112) may include one or more processors (102, 202) and / or one or more memories (104, 204) of FIG. 24. For example, the transceiver(s) (114) may include one or more transceivers (106, 206) and / or one or more antennas (108, 208) of FIG. 24. The control unit (120) is electrically connected to the communication unit (110), the memory unit (130), and additional elements (140) and controls the general operation of the wireless device. For example, the control unit (120) may control the electrical / mechanical operation of the wireless device based on a program / code / command / information stored in the memory unit (130). Additionally, the control unit (120) may transmit information stored in the memory unit (130) to an external (e.g., another communication device) via a wireless / wired interface through the communication unit (110), or store information received from an external (e.g., another communication device) via a wireless / wired interface through the communication unit (110) in the memory unit (130).

[0559] The additional element (140) can be configured in various ways depending on the type of wireless device. For example, the additional element (140) may include at least one of a power unit / battery, an input / output unit (I / O unit), a driving unit, and a computing unit. Although not limited thereto, the wireless device may be implemented in the form of a robot (Fig. 23, 100a), a vehicle (Fig. 23, 100b-1, 100b-2), an XR device (Fig. 23, 100c), a portable device (Fig. 23, 100d), a home appliance (Fig. 23, 100e), an IoT device (Fig. 23, 100f), a digital broadcasting terminal, a hologram device, a public safety device, an MTC device, a medical device, a fintech device (or financial device), a security device, a climate / environment device, an AI server / device (Fig. 23, 400), a base station (Fig. 23, 200), a network node, etc. Wireless devices can be used in a movable or fixed location depending on the use—e.g., service.

[0560] In FIG. 26, various elements, components, units / parts, and / or modules within the wireless device (100, 200) may be entirely interconnected via a wired interface, or at least partially connected via a communication unit (110). For example, within the wireless device (100, 200), the control unit (120) and the communication unit (110) may be connected via a wire, and the control unit (120) and the first unit (e.g., 130, 140) may be connected wirelessly via the communication unit (110). Additionally, each element, component, unit / part, and / or module within the wireless device (100, 200) may include one or more additional elements. For example, the control unit (120) may be composed of one or more sets of processors. For example, the control unit (120) may be composed of a set of a communication control processor, an application processor, an Electronic Control Unit (ECU), a graphics processing processor, a memory control processor, etc. As another example, the memory unit (130) may be composed of RAM (Random Access Memory), DRAM (Dynamic RAM), ROM (Read Only Memory), flash memory, volatile memory, non-volatile memory and / or a combination thereof.

[0561] Hereinafter, an implementation example of FIG. 26 will be described in more detail with reference to the drawings.

[0562] FIG. 27 illustrates a portable device according to one embodiment of the present disclosure. The portable device may include a smartphone, a smartpad, a wearable device (e.g., a smartwatch, smart glasses), a portable computer (e.g., a laptop, etc.). The portable device may be referred to as a Mobile Station (MS), a User Terminal (UT), a Mobile Subscriber Station (MSS), a Subscriber Station (SS), an Advanced Mobile Station (AMS), or a Wireless Terminal (WT). The embodiment of FIG. 27 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.

[0563] Referring to FIG. 27, the portable device (100) may include an antenna unit (108), a communication unit (110), a control unit (120), a memory unit (130), a power supply unit (140a), an interface unit (140b), and an input / output unit (140c). The antenna unit (108) may be configured as part of the communication unit (110). Blocks 110 to 130 / 140a to 140c each correspond to blocks 110 to 130 / 140 of FIG. 26.

[0564] The communication unit (110) can transmit and receive signals (e.g., data, control signals, etc.) with other wireless devices and base stations. The control unit (120) can control the components of the portable device (100) to perform various operations. The control unit (120) may include an AP (Application Processor). The memory unit (130) can store data / parameters / programs / code / commands required for the operation of the portable device (100). Additionally, the memory unit (130) can store input / output data / information, etc. The power supply unit (140a) supplies power to the portable device (100) and may include wired / wireless charging circuits, batteries, etc. The interface unit (140b) can support the connection between the portable device (100) and other external devices. The interface unit (140b) may include various ports (e.g., audio input / output ports, video input / output ports) for connection with external devices. The input / output unit (140c) can receive or output video information / signals, audio information / signals, data, and / or information input by a user. The input / output unit (140c) may include a camera, a microphone, a user input unit, a display unit (140d), a speaker and / or a haptic module, etc.

[0565] For example, in the case of data communication, the input / output unit (140c) acquires information / signals (e.g., touch, text, voice, image, video) input from the user, and the acquired information / signals can be stored in the memory unit (130). The communication unit (110) converts the information / signals stored in the memory into wireless signals and can directly transmit the converted wireless signals to another wireless device or to a base station. Additionally, the communication unit (110) can receive wireless signals from another wireless device or base station and then restore the received wireless signals to their original information / signals. The restored information / signals can be stored in the memory unit (130) and then output in various forms (e.g., text, voice, image, video, haptic) through the input / output unit (140c).

[0566] The claims described in this specification may be combined in various ways. For example, the technical features of the method claims in this specification may be combined to be implemented as a device, and the technical features of the device claims in this specification may be combined to be implemented as a method. Furthermore, the technical features of the method claims and the technical features of the device claims in this specification may be combined to be implemented as a device, and the technical features of the method claims and the technical features of the device claims in this specification may be combined to be implemented as a method.

Claims

In terms of method, A first device acquires information related to a second sink raster; Based on the information related to the second sync raster, the first device receives a second synchronization signal block from the second device; and Based on the second synchronization signal block, the first device acquires synchronization; comprising, A method in which the second synchronization signal block is a simplified synchronization signal block compared to the first synchronization signal block on the first sync raster. In paragraph 1, The above simplified synchronization signal block includes only a synchronization signal, a method. In paragraph 2, A method in which the above synchronization signal comprises at least one of a primary synchronization signal and a secondary synchronization signal. In paragraph 1, The first device acquires information related to the first sink raster; Based on the information related to the first sync raster, the first device further includes the step of monitoring the first synchronization signal block; The above first synchronization signal block comprises a primary synchronization signal, a secondary synchronization signal, and a physical broadcast channel, method. In paragraph 4, A method in which the second synchronization signal block is received independently of the first synchronization signal block. In paragraph 4, The method further includes the step of the first device transmitting a signal to the second device to request the first synchronization signal block; The information related to the first sync raster is obtained based on the signal for requesting the first synchronization signal block, and A method in which the monitoring of the first synchronization signal block is performed based on the signal for requesting the first synchronization signal block. In paragraph 6, A method in which the signal for requesting the first synchronization signal block is a UL (uplink) WUS (wake-up signal). In paragraph 4, The first sink raster is an on-demand sink raster based on the second sink raster, and The above second sync raster is an always-on sync raster, method. In paragraph 1, A method in which the support of the second synchronization signal block is provided based on the first synchronization signal block. In paragraph 1, The first device transmits a signal to the second device to request a resource for a random access channel based on the synchronization; and A method further comprising the step of the first device transmitting the random access channel to the second device on the resource for the random access channel. In Paragraph 10, A method in which the transmission of a signal to request the resource for the above random access channel is triggered based on celestial information. In Paragraph 11, A method in which a signal for requesting the resource for the above random access channel is UL WUS. In paragraph 1, The above-mentioned first device is a terminal, and The method wherein the second device is at least one of a base station or a non-ground network. In the first device, At least one transmitter / receiver; At least one processor; and The first device comprises at least one memory connected to the at least one processor and storing instructions, wherein the instructions are executed by the at least one processor: To obtain information related to the second sync raster; Based on the information related to the second sync raster, to receive a second synchronization signal block from the second device; and Based on the above second synchronization signal block, synchronization is obtained, The first device, wherein the second synchronization signal block is a simplified synchronization signal block compared to the first synchronization signal block on the first sync raster. In a processing device, At least one processor; and The first device comprises at least one memory connected to the at least one processor and storing instructions, wherein the instructions are executed by the at least one processor: To obtain information related to the second sync raster; Based on the information related to the second sync raster, to receive a second synchronization signal block from the second device; and Based on the above second synchronization signal block, synchronization is obtained, A processing device in which the second synchronization signal block is a simplified synchronization signal block compared to the first synchronization signal block on the first sync raster. As a non-transient computer-readable storage medium recording instructions, When executed, the above instructions cause the first device: To obtain information related to the second sync raster; Based on the information related to the second sync raster, to receive a second synchronization signal block from the second device; and Based on the above second synchronization signal block, synchronization is obtained, A non-transient computer-readable storage medium in which the second synchronization signal block is a simplified synchronization signal block compared to the first synchronization signal block on the first sync raster. In terms of method, A step in which the second device transmits information related to the second sink raster to the first device; Based on the information related to the second sync raster, the second device transmits a second synchronization signal block to the first device; and Based on the second synchronization signal block, the second device acquires synchronization; comprising, A method in which the second synchronization signal block is a simplified synchronization signal block compared to the first synchronization signal block on the first sync raster. In the second device, At least one transmitter / receiver; At least one processor; and The second device comprises at least one memory connected to the at least one processor and storing instructions, wherein the instructions are executed by the at least one processor: To cause the first device to transmit information related to the second sink raster; Based on the information related to the second sync raster, the first device is made to transmit a second synchronization signal block; and Based on the above second synchronization signal block, synchronization is obtained, The second device, wherein the second synchronization signal block is a simplified synchronization signal block compared to the first synchronization signal block on the first sync raster. In a processing device, At least one processor; and A second device comprising at least one memory connected to the at least one processor and storing instructions, wherein the instructions are executed by the at least one processor: To cause the first device to transmit information related to the second sink raster; Based on the information related to the second sync raster, the first device is made to transmit a second synchronization signal block; and Based on the above second synchronization signal block, synchronization is obtained, A processing device in which the second synchronization signal block is a simplified synchronization signal block compared to the first synchronization signal block on the first sync raster. As a non-transient computer-readable storage medium recording instructions, When executed, the above commands cause the second device: To cause the first device to transmit information related to the second sink raster; Based on the information related to the second sync raster, the first device is made to transmit a second synchronization signal block; and Based on the above second synchronization signal block, synchronization is obtained, A non-transient computer-readable storage medium in which the second synchronization signal block is a simplified synchronization signal block compared to the first synchronization signal block on the first sync raster.

Images