Method and apparatus for performing terminal-to-base station transmission on basis of pre-compensation operation in non-terrestrial network

Abstract

Proposed is a method for operation of a first device (100) in a wireless communication system. The method may comprise the steps of: acquiring information related to requirements related to a synchronization offset; performing a pre-compensation operation; and on the basis of a synchronization offset value after performing the pre-compensation operation and the requirements, performing a plurality of slot-based transmissions.

Description

Method and device for performing terminal-to-base station transmission based on pre-compensation operation in a non-terrestrial network

[0001] The present disclosure relates to a wireless communication system.

[0002] 5G NR, the successor to LTE (long-term evolution), is a new clean-slate mobile communications system characterized by high performance, low latency, and high availability. 5G NR can utilize all available spectrum resources, from low-frequency bands below 1 GHz, mid-frequency bands between 1 GHz and 10 GHz, and high-frequency (millimeter wave) bands above 24 GHz.

[0003] The 6G (wireless communication) system aims to achieve (i) very high data rates per device, (ii) a very large number of connected devices, (iii) global connectivity, (iv) very low latency, (v) low energy consumption for battery-free Internet of Things (IoT) devices, (vi) ultra-reliable connectivity, and (vii) connected intelligence with machine learning capabilities. The vision of the 6G system can be divided into four aspects: intelligent connectivity, deep connectivity, holographic connectivity, and ubiquitous connectivity, and the 6G system can satisfy the requirements as shown in Table 1 below. For example, Table 1 can represent an example of the requirements of 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

[0005] According to one embodiment of the present disclosure, a method that can be performed by a first device may be provided. For example, the method may include: obtaining information related to requirements related to synchronization offset; performing a pre-compensation operation; and performing multiple slot-based transmissions based on a synchronization offset value and the requirements after performing the pre-compensation operation.

[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 coupled to the at least one processor and storing instructions. For example, the instructions, based on execution by the at least one processor, may cause the first device to: obtain information related to a requirement related to a synchronization offset; perform a pre-compensation operation; and, based on a synchronization offset value and the requirement after performing the pre-compensation operation, perform multiple slot-based transmissions.

[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 coupled to the at least one processor and storing instructions. For example, the instructions, based on execution by the at least one processor, may cause the first device to: obtain information related to a requirement related to a synchronization offset; perform a pre-compensation operation; and, based on a synchronization offset value and the requirement after performing the pre-compensation operation, perform multiple slot-based transmissions.

[0008] According to one embodiment of the present disclosure, a non-transitory computer-readable storage medium having instructions recorded thereon may be provided. For example, the instructions, when executed, may cause a first device to: obtain information related to requirements related to synchronization offset; perform a pre-compensation operation; and, based on a synchronization offset value and the requirements after performing the pre-compensation operation, perform multiple slot-based transmissions.

[0009] According to one embodiment of the present disclosure, a method that can be performed by a second device can be provided. For example, the method includes: transmitting information related to a requirement related to a synchronization offset to a first device; and receiving a plurality of slot-based transmissions from the first device, wherein the plurality of slot-based transmissions can be performed based on a synchronization offset value of the first device and the requirement after a pre-compensation operation is performed.

[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 coupled to the at least one processor and storing instructions. For example, the instructions, based on execution by the at least one processor, cause the second device to: transmit information related to a requirement related to a synchronization offset to a first device; and receive a plurality of slot-based transmissions from the first device, wherein the plurality of slot-based transmissions may be performed based on a synchronization offset value of the first device and the requirement after a pre-compensation operation is performed.

[0011] Figure 1 illustrates a device-to-device communication procedure according to one embodiment of the present disclosure.

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

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

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

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

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

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

[0018] FIG. 8 illustrates a pre-compensation operation for time synchronization error according to one embodiment of the present disclosure.

[0019] FIG. 9 illustrates different timing error related requirements depending on a specific transmission type, according to one embodiment of the present disclosure.

[0020] FIG. 10 illustrates a procedure of a method that can be performed by a first device according to one embodiment of the present disclosure.

[0021] FIG. 11 illustrates a procedure of a method that can be performed by a second device according to one embodiment of the present disclosure.

[0022] FIG. 12 illustrates a communication system (1) according to one embodiment of the present disclosure.

[0023] FIG. 13 illustrates a wireless device according to an embodiment of the present disclosure.

[0024] FIG. 14 illustrates a signal processing circuit for a transmission signal according to one embodiment of the present disclosure.

[0025] FIG. 15 illustrates a wireless device according to an embodiment of the present disclosure.

[0026] FIG. 16 illustrates a mobile device according to an embodiment of the present disclosure.

[0027] FIG. 17 illustrates a vehicle or autonomous vehicle according to one embodiment of the present disclosure.

[0028] In this disclosure, "A or B" can mean "only A," "only B," or "both A and B." In other words, "A or B" in this disclosure can be interpreted as "A and / or B." For example, "A, B or C" in this disclosure can mean "only A," "only B," "only C," or "any combination of A, B and C."

[0029] As used herein, a slash ( / ) or a comma 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."

[0030] 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 identically to “at least one of A and B.”

[0031] Additionally, in the present disclosure, “at least one of A, B and C” can 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” can mean “at least one of A, B and C.”

[0032] 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, "control information" in 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."

[0033] In the following explanation, ‘when, if, in case of’ can be replaced with ‘based on’.

[0034] In the present disclosure, the device obtaining information may include the information being (pre-)set to the device, the information being received from another entity to the device, or the device generating the information.

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

[0036] In the present disclosure, higher layer parameters may be parameters set for the terminal, preset, or predefined. For example, a base station or network may transmit higher layer parameters to the terminal. For example, the higher layer parameters may be transmitted via radio resource control (RRC) signaling or medium access control (MAC) signaling.

[0037] In the present disclosure, "setting or defining" may be interpreted as being set or preset to a device through predefined signaling (e.g., SIB, MAC, RRC, DCI (downlink control information), etc.) from a base station or a network. In the present disclosure, "setting or defining" may be interpreted as being set or preset to a device through predefined signaling (e.g., MAC, RRC, SCI (sidelink control information), device-to-device signaling control information, etc.) from another device. In the present disclosure, "setting or defining" may be interpreted as being set or preset to a device.

[0038] In the present disclosure, a 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.

[0039] The technology proposed in the present 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) / 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.

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

[0041] FIG. 1 illustrates a device-to-device communication procedure according to one embodiment of the present disclosure. The embodiment of FIG. 1 may be combined with various embodiments of the present disclosure.

[0042] Referring to FIG. 1, in step S101, a first device and a second device can perform synchronization. For example, the first device can be a terminal and / or at least one of the devices proposed in the present disclosure. For example, the second device can 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 can perform an initial cell search operation. For example, the first device can detect at least one synchronization signal transmitted by the second device according to a predefined rule. Here, for example, the synchronization signal can include a plurality of synchronization signals classified according to a structure or purpose (e.g., a primary synchronization signal, a secondary synchronization signal, etc.). 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., a cell identifier).

[0043] In step S103, the first device can obtain system information transmitted by the second device. For example, the system information may include information related to the properties, characteristics, and / or capabilities of the second device required 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 system information before receiving the system information. For example, the request and provision of system information may be performed after a random access procedure described below.

[0044] In step S105, the first device and the second device can perform a random access procedure. For example, the first device can transmit and / or receive at least one message (e.g., a random access preamble, a random access response message, etc.) for the random access procedure based on information related to a 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 can transmit a preamble (e.g., Msg1) through the random access channel, the first device can receive a random access response message (e.g., Msg2), the first device can transmit a message (e.g., Msg3) including 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 can receive a message (e.g., Msg4) for contention resolution and / or connection establishment. For example, Msg1 and Msg3 can be sent and received as one message (e.g., MsgA), and / or Msg2 and Msg4 can be sent and received as one message (e.g., MsgB).

[0045] 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 that controls a connection (e.g., a radio resource control (RRC) layer), a layer that handles mapping between logical channels and transport channels (e.g., a media access control (MAC) layer), a layer that handles physical channels (e.g., a physical (PHY) layer), etc. For example, the first device and the second device may perform at least one of signaling for establishing a connection, signaling for determining settings related to communication, and / or signaling for indicating allocated resources. For example, the control information may be signaled / transmitted via 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.

[0046] 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, transmit, and / or receive data based on signaling of control information. 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, waveform demodulation for each antenna, signal arrangement considering layer mapping, constellation demapping, descrambling, and / or channel decoding.

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

[0048] FIG. 2 illustrates a radio protocol architecture according to an embodiment of the present disclosure. The embodiment of FIG. 2 can be combined with various embodiments of the present disclosure. For example, (a) of FIG. 2 may illustrate a radio protocol stack of a user plane for uplink communication or downlink communication, and (b) of FIG. 2 may illustrate a radio protocol stack of a control plane for uplink communication or downlink communication. For example, (c) of FIG. 2 may illustrate a radio protocol stack of a user plane for device-to-device communication, and (d) of FIG. 2 may illustrate a radio protocol stack of a control plane for device-to-device communication.

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

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

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

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

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

[0054] For example, establishing an RB can refer to the process of defining the characteristics of the radio protocol layer and channel to provide a specific service, and setting specific parameters and operating methods for each. For example, RBs can be divided into two types: signaling radio bearers (SRBs) and data radio bearers (DRBs). For example, SRBs can be used as a channel to transmit RRC messages in the control plane, while DRBs can be used as a channel to transmit user data in the user plane.

[0055] For example, a downlink transmission channel may include at least one of a broadcast channel (BCH) for transmitting system information, and / or a downlink shared channel (SCH) for transmitting user traffic or control messages. For example, traffic or control messages of a downlink multicast or broadcast service may be transmitted through the downlink SCH, or may be transmitted through a separate downlink multicast channel (MCH). Meanwhile, an uplink transmission channel may include at least one of a random access channel (RACH) for transmitting initial control messages, and / or an uplink shared channel (SCH) for transmitting user traffic or control messages. For example, a logical channel located above a 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).

[0056] FIG. 3 illustrates the structure of a wireless frame according to an embodiment of the present disclosure. The embodiment of FIG. 3 can be combined with various embodiments of the present disclosure.

[0057] Referring to FIG. 3, for example, a radio frame may be used 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 include 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 according to a subcarrier spacing (SCS). For example, each slot may include 12 or 14 OFDM (A) symbols, depending on a cyclic prefix (CP).

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

[0059] Table 2 below shows the number of symbols per slot (N) depending on 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 ) is an example.

[0060] CP type SCS (15*2u )N slot symb N frame,u slot N subframe,u slot Normal CP15kHz (u=0)1410130kHz (u=1)1420260kHz (u=2)14404120kHz (u=3)14808240kHz (u=4)1416016Extended CP60kHz (u=2)12404

[0061] For example, OFDM(A) numerology (e.g., SCS, CP length, etc.) may be set differently between multiple cells that are merged into a single terminal. Accordingly, the (absolute time) interval of time resources (e.g., subframes, slots, or transmit time intervals (TTIs)) composed of the same number of symbols may be set differently between the merged cells. For example, in the present disclosure, time resources such as subframes, slots, TTIs, etc. may be referred to as time units.

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

[0063] FIG. 4 illustrates a slot structure of a frame according to an embodiment of the present disclosure. The embodiment of FIG. 4 can be combined with various embodiments of the present disclosure.

[0064] 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 one numerology (e.g., SCS, CP length, etc.). For example, a carrier may include at most N BWPs (where N is a positive integer). For example, data communication may be performed through an activated BWP. For example, each element may be referred to as a resource element (RE) in the resource grid, and one complex symbol may be mapped to it.

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

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

[0067] In the present disclosure, PSCCH may be replaced by a control channel, a physical control channel, a control channel associated with a sidelink, a physical control channel associated with a sidelink, a device-to-device physical control channel, etc. In the present disclosure, PSSCH may be replaced by a shared channel, a physical shared channel, a shared channel associated with a sidelink, a physical shared channel associated with a sidelink, a device-to-device physical shared channel, etc. For example, SL communication may be replaced by device-to-device communication. For example, in terms referring to various channels and / or signals associated with SL communication, the SL part may be replaced by "device-to-device."

[0068] In the present disclosure, PUCCH may be replaced by a control channel, a physical control channel, a control channel associated with uplink, a physical control channel associated with uplink, a device-to-base station physical control channel, a terminal-to-base station physical control channel, etc. In the present disclosure, PUSCH may be replaced by a shared channel, a physical shared channel, a shared channel associated with uplink, a physical shared channel associated with uplink, a device-to-base station physical shared channel, a terminal-to-base station physical shared channel, etc. For example, UL communication may be replaced by terminal-to-base station communication or device-to-base station communication. For example, in terms referring to various channels and / or signals associated with UL communication, the UL part may be replaced by "device-to-base station" or "terminal-to-base station."

[0069] In the present disclosure, PDCCH may be replaced by a control channel, a physical control channel, a downlink-related control channel, a downlink-related physical control channel, a base station-to-device physical control channel, a base station-to-terminal physical control channel, etc. In the present disclosure, PDSCH may be replaced by a shared channel, a physical shared channel, a downlink-related shared channel, a downlink-related physical shared channel, a base station-to-device physical shared channel, a base station-to-terminal physical shared channel, etc. For example, DL communication may be replaced by base station-to-device communication or base station-to-terminal communication. For example, the DL part in terms referring to various channels and / or signals related to DL communication may be replaced by "base station-to-device" or "base station-to-terminal."

[0070] FIG. 5 illustrates an example of a BWP according to an embodiment of the present disclosure. The embodiment of FIG. 5 can be combined with various embodiments of the present disclosure. In the embodiment of FIG. 5, it is assumed that there are three BWPs.

[0071] Referring to FIG. 5, for example, a common resource block (CRB) may be a carrier resource block numbered from one end of a 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 a resource block grid.

[0072] For example, BWP is point A, offset from point A (N start BWP ) and bandwidth (N size BWP) can be set by. For example, point A can be an outer reference point of the PRB of a carrier where subcarrier 0 of all numerologies (e.g., all numerologies supported by the network on that carrier) aligns. For example, the offset can be the PRB spacing between the lowest subcarrier in a given numerology and point A. For example, the bandwidth can be the number of PRBs in a given numerology.

[0073] FIG. 6 illustrates a communication structure that can be provided in a 6G system according to an embodiment of the present disclosure. The embodiment of FIG. 6 can be combined with various embodiments of the present disclosure.

[0074] As core implementation technologies of the 6G system, 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.

[0075] - Artificial Intelligence: Incorporating AI into communications can streamline and improve real-time data transmission. AI can use numerous analytics to determine how complex target tasks should be performed. For example, AI can increase efficiency and reduce processing delays. Time-consuming tasks such as handovers, network selection, and resource scheduling can be performed instantly using AI. AI can also play a crucial role in machine-to-machine (M2M), machine-to-human, and human-to-machine communications. AI can also facilitate rapid communication in brain-computer interfaces (BCIs). 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.

[0076] - THz communication (terahertz communication): Data rates can be increased by increasing the bandwidth. This can be achieved by using sub-THz communication with wide bandwidths and applying advanced massive MIMO technology. THz waves, also known as sub-millimeter waves, typically refer to the frequency range between 0.1 THz and 10 THz, with corresponding wavelengths ranging from 0.03 mm to 3 mm. The 100 GHz to 300 GHz band (sub-THz band) is considered a key part of the THz spectrum for cellular communications. Adding the sub-THz band to the mmWave band will increase the capacity of 6G cellular communications. Among the defined THz bands, 300 GHz to 3 THz lies in the far infrared (IR) frequency band. While part of the optical band, the 300 GHz to 3 THz band lies at the boundary of the optical band, immediately following the RF band. Therefore, this 300 GHz to 3 THz band exhibits similarities to RF. Key characteristics of THz communications include (i) the widely available bandwidth to support very high data rates and (ii) the high path loss that occurs at high frequencies (requiring highly directional antennas). The narrow beamwidths generated by highly directional antennas reduce interference. The small wavelength of THz signals allows for a significantly larger number of antenna elements to be integrated into devices and base stations operating in this band. This enables the use of advanced adaptive array technologies to overcome range limitations.

[0077] - Large-scale MIMO technology

[0078] - Hologram beamforming (HBF)

[0079] - Optical wireless technology

[0080] - Free-space optical transmission backhaul network (FSO backhaul network)

[0081] - Quantum communication

[0082] - Cell-free communication

[0083] - Integration of wireless information and power transmission

[0084] - Integration of wireless communication and sensing

[0085] - Integrated access and backhaul network

[0086] - Big data analysis

[0087] - Reconfigurable intelligent surface

[0088] - metaverse

[0089] - Block chain

[0090] 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 can include UAM, RAM, UAS, and uncrewed aerial vehicles (UAVs).

[0091] - Autonomous driving (self-driving): V2X (vehicle to everything), a key element in building autonomous driving infrastructure, can be a technology that allows cars to communicate and share with various elements on the road for autonomous driving, such as vehicle to vehicle (V2V) wireless communication and vehicle to infrastructure (V2I) wireless communication.

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

[0093] - 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.

[0094] - Reconfigurable intelligent surface (RIS): RIS can be used to manipulate and enhance signal propagation in wireless communication environments. For example, a 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 example, a RIS can improve signal reception by controlling the path, phase, and / or intensity of the propagating signal. For example, in the case of a RIS, power consumption can be very low because power is consumed only for controlling the phase and amplitude of the small antennas. For example, because a RIS can be reconfigured to suit different environments, it can meet diverse communication requirements and operate effectively in dynamic network environments.

[0095] 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.

[0096] Referring to FIG. 7, NTN communication can be performed based on satellite networks, high-altitude platform stations (HAPS) as international mobile telecommunications (IMT) base stations (BS), and terminals capable of aerial communication (e.g., AAMs). For example, to improve coverage, etc., devices such as satellite networks, HIBS, and terminals capable of aerial communication (e.g., AAMs) 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.

[0097] Recently, in the field of communications, the introduction of non-terrestrial networks (NTNs) that utilize satellites as network nodes is being actively discussed. Satellites that support the above non-terrestrial networks (e.g., NTNs) can be classified according to their flight orbits and characteristics, such as geostationary orbit (GEO), medium Earth orbit (MEO), and low Earth orbit (LEO). In general, the satellites can have very high altitudes. Therefore, the service area of ​​the satellite can have very wide coverage characteristics, and the number of target terminals within the service area can be relatively large. Accordingly, the above non-terrestrial network (e.g., NTN) service may require multiplexing support for multiple terminal(s).

[0098] Here, for example, since terrestrial terminals have transmission power constraints, coverage extension techniques can be applied to ensure that a sufficiently large signal reaches a high-altitude non-terrestrial network (e.g., NTN) during terminal-to-base station transmission (e.g., UL transmission). For example, the terminal can achieve coverage extension by repeating the terminal-to-base station physical shared channel (e.g., PUSCH; Physical Uplink Shared Channel), which is a terminal-to-base station communication data channel (e.g., UL link data channel) in the time domain (or by repeatedly performing terminal-to-base station physical shared channel (e.g., PUSCH) transmission).

[0099] Here, the terminal may transmit the terminal-to-base station physical shared channel (e.g., 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 before the orthogonal frequency division multiplexing (e.g., OFDM; orthogonal frequency division multiplexing) modulation method.

[0100] Meanwhile, the above-described coverage extension technology may have reduced resource utilization efficiency due to repeated transmissions, and to improve the reduced efficiency, a terminal-to-base station communication link (e.g., UL link) multiplexing method utilizing an orthogonal cover code (e.g., OCC) may be effective. Here, the orthogonal cover code (e.g., OCC) may refer to an orthogonal cover code (e.g., OCC) applied in the time domain and / or frequency domain for terminal-to-base station transmission (e.g., UL transmission).

[0101] Here, in order to maintain orthogonality between different orthogonal cover codes (e.g., OCC), it may be assumed that the channel variation is small within the time and / or frequency interval to which the orthogonal cover code (e.g., OCC) is applied.

[0102] Here, from the perspective of a terminal receiving a non-terrestrial network (e.g., NTN)-based service, problems such as Doppler shift due to high relative speed between the satellite and the terminal and / or time delay due to long communication distance between the satellite and the terminal may be aggravated compared to conventional terrestrial network (hereinafter referred to as TN)-based communication.

[0103] Therefore, in order to achieve multiplexing and / or capacity enhancement of the terminal-to-base station communication link (e.g., UL link) based on the orthogonal cover code (e.g., OCC) in the above-described non-terrestrial network (e.g., NTN), it may be necessary to verify whether the terminal-to-base station transmission (e.g., UL transmission) between the base station and / or terminals is suitable for applying the orthogonal cover code (e.g., OCC).

[0104] For example, a base station may require a terminal to achieve time-domain and / or frequency-domain synchronization accuracy within a certain level during terminal-to-base station transmission (e.g., UL transmission) based on an orthogonal cover code (e.g., OCC). For example, the base station may apply an orthogonal cover code (e.g., OCC) only when the terminal can pre-compensate for Doppler shift, etc. within a certain offset level by utilizing satellite orbit information, etc. In the present disclosure, a method and device for terminal-to-base station transmission (e.g., UL transmission) based on a pre-compensation operation in a non-terrestrial network (e.g., NTN) are proposed.

[0105] [Proposal #01]

[0106] According to one embodiment of the present disclosure, when there are (pre-)requirements(s) for supporting (a specific type of) terminal-to-base station transmission (e.g., UL transmission) between a base station and a terminal, a method may be provided in which, as one type of the (pre-)requirements(s), (pre-)requirements(s) for time synchronization error and / or Doppler shift pre-compensation (at the terminal end) are defined in a form including one or more of the following:

[0107] (1) Allowable (maximum) time-domain and / or frequency-domain synchronization error (range) (per slot / symbol)

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

[0109] (3) Allowable (maximum) time-domain and / or frequency-domain synchronization error change rate (e.g., Time Drift Rate and / or Doppler Drift Rate) between transmissions;

[0110] Here, the terminal-to-base station transmission (e.g., UL transmission) (of a specific type) may mean a terminal-to-base station transmission (e.g., UL transmission) to which an orthogonal cover code (e.g., OCC) is applied (in the time domain and / or frequency domain). For example, when the terminal-to-base station transmission (e.g., UL transmission) to which the orthogonal cover code (e.g., OCC) is applied between the base station and the terminal, (pre) requirements for time delay and / or Doppler shift pre-compensation (at the terminal) may need to be met.

[0111] Here, the above (pre) requirement(s) may be (pre) requirement(s) for a specific type of terminal. For example, the above (pre) requirement(s) may be (pre) requirement(s) for a non-terrestrial network (e.g., NTN) service terminal.

[0112] In a next-generation mobile communication system based on a non-terrestrial network according to an embodiment of the present disclosure, when a terminal transmits a terminal-to-base station communication data channel (e.g., UL link data channel) (e.g., terminal-to-base station physical shared channel (e.g., PUSCH)), the non-terrestrial network may be composed of a terminal, a satellite, and a base station, and the terminal and the satellite may be connected through a service link, and the satellite and the base station may be connected through a feeder link.

[0113] Here, due to the long distance and high relative velocity between the terminal and the satellite, time domain and / or frequency domain synchronization errors may occur in the service link, etc. For example, the time domain and / or frequency domain synchronization errors may include time synchronization errors and / or Doppler shifts. Here, time domain and / or frequency domain synchronization errors (within a certain level) may be required during (a specific type of) terminal-to-base station transmission (e.g., UL transmission) between the base station and the terminal. For example, requirements related to time domain and / or frequency domain synchronization errors may be (pre-)set during (a specific type of) terminal-to-base station transmission (e.g., UL transmission) between the base station and the terminal.

[0114] Here, for example, in order to achieve time domain and / or frequency domain synchronization error (within a certain level) during (a specific type of) terminal-to-base station transmission (e.g., UL transmission), requirement(s) for time synchronization error and / or Doppler shift pre-compensation (at the terminal) may be defined. For example, when a base station wants to configure and / or instruct a terminal to perform terminal-to-base station transmission (e.g., UL transmission) to which (time domain and / or frequency domain) orthogonal cover codes (e.g., OCC) are applied for the purpose of multiplexing and / or increasing capacity of the terminal-to-base station communication link (e.g., UL link), requirement(s) for time synchronization error and / or Doppler shift pre-compensation (at the terminal) for maintaining orthogonality between the orthogonal cover codes (e.g., OCC)(s) may be defined. Here, for example, the requirement(s) may be defined in a form including one or more of the following:

[0115] (1) Allowable (maximum) time-domain and / or frequency-domain synchronization error (range) (per slot or symbol);

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

[0117] (3) Allowable (maximum) time-domain and / or frequency-domain synchronization error change rate (e.g., time drift rate and / or Doppler drift rate, etc.) (between transmissions);

[0118] According to the above proposed method, there may be an advantage that the time synchronization error and / or Doppler shift pre-compensation requirement(s) (at the terminal) during a (specific type) terminal-to-base station transmission (e.g., UL transmission) between the base station and the terminal can be defined identically, and based on this, the base station can expect to receive a signal of a promised and / or defined form for the (specific type) terminal-to-base station transmission (e.g., UL transmission).

[0119] The above [Proposal #01] can be applied in combination with other proposed method(s) as long as the operation of the disclosure does not conflict.

[0120] FIG. 8 illustrates a pre-compensation operation for time synchronization error according to an embodiment of the present disclosure. The embodiment of FIG. 8 can be combined with various embodiments of the present disclosure.

[0121] Referring to FIG. 8, a specific resource start time according to the synchronization criteria of the base station and a resource start time from the perspective of the first device are shown. For example, a synchronization offset (specifically, a timing offset) may exist for the start time of the same resource, and in this example, a first timing offset may exist between the synchronization criteria of the base station and the synchronization criteria from the perspective of the first device.

[0122] At this time, the first device can perform a pre-compensation operation to reduce the timing error, and after the pre-compensation operation, the timing error between the synchronization reference of the base station and the synchronization reference from the first device's perspective can be reduced.

[0123] For example, in this example, after the above pre-compensation operation, the timing error between the synchronization reference of the base station and the synchronization reference from the first device perspective can be reduced to a second timing error.

[0124] FIG. 9 illustrates different timing error-related requirements depending on a specific transmission type, according to an embodiment of the present disclosure. The embodiment of FIG. 9 may be combined with various embodiments of the present disclosure.

[0125] Referring to FIG. 9, a case is shown where a terminal performs a single slot-based transmission (is to perform) and a case is shown where a terminal performs multiple slot-based transmissions (is to perform).

[0126] Here, for example, the terminal corresponding to each case can perform each transmission operation only when the requirement for synchronization error with the base station is satisfied.

[0127] Here, for example, the requirement may be a requirement related to timing error. For example, the requirement may be a requirement applied to the timing error after a pre-compensation operation to reduce the timing error. For example, the requirement may be satisfied if the timing error after the pre-compensation operation is performed is less than a threshold value associated with each requirement.

[0128] For example, when a terminal is to perform single-slot based transmission, the terminal may perform a pre-compensation operation related to a timing error, and the timing error after the pre-compensation operation may be less than a first threshold value related to a first requirement related to performing the single-slot based transmission. Therefore, the requirement is satisfied, and the terminal may perform the single-slot based transmission.

[0129] On the other hand, for example, when a terminal is to perform multiple slot-based transmissions, the terminal may perform a pre-compensation operation related to a timing error, and the timing error after the pre-compensation operation may be greater than a second threshold value related to a second requirement related to the multiple slot-based transmissions. Therefore, since the requirement is not met, the terminal may drop the multiple slot-based transmissions.

[0130] For example, in the above embodiment, the plurality of slot-based transmissions (or, a specific type of transmission in the present disclosure) may include repetitive transmissions according to terminal-to-base station channel repetition or repetitive transmissions according to terminal-to-terminal channel repetition. For example, in the above embodiment, the plurality of slot-based transmissions (or, a specific type of transmission in the present disclosure) may include repetitive transmissions according to terminal-to-base station channel repetition to which an orthogonal cover code (e.g., OCC) is applied or repetitive transmissions according to terminal-to-terminal channel repetition to which an orthogonal cover code (e.g., OCC) is applied.

[0131] [Proposal #02]

[0132] According to one embodiment of the present disclosure, when there are (pre-)requirements(s) to support (a specific type of) terminal-to-base station transmission (e.g., UL transmission) between a base station and a terminal, a method may be provided for making the base station and / or the terminal recognize (pre-)requirements(s) for time synchronization error and / or Doppler shift pre-compensation (at the terminal end) in one or more of the following ways, as one type of said (pre-)requirements(s).

[0133] (1) Preliminary agreement and / or definition between the base station and the terminal

[0134] (2) What the base station sets and / or instructs the terminal to do

[0135] (3) The terminal reports information about the time synchronization error and / or Doppler shift pre-compensation level and / or capability that can be supported by the base station.

[0136] Here, for example, the (specific type of) terminal-to-base station transmission (e.g., UL transmission) may mean terminal-to-base station transmission (e.g., UL transmission) to which an orthogonal cover code (e.g., OCC) is applied (in the time domain and / or frequency domain). For example, when the terminal-to-base station transmission (e.g., UL transmission) to which the orthogonal cover code (e.g., OCC) is applied between the base station and the terminal, (pre)requirements for time delay and / or Doppler shift pre-compensation (at the terminal end) may need to be met.

[0137] Here, the above (pre) requirement(s) may be (pre) requirement(s) for a specific type of terminal. For example, the above (pre) requirement(s) may be (pre) requirement(s) for a non-terrestrial network (e.g., NTN) service terminal.

[0138] In a next-generation mobile communication system based on a non-terrestrial network according to an embodiment of the present disclosure, when a terminal transmits a terminal-to-base station communication data channel (e.g., UL link data channel) (e.g., a terminal-to-base station physical shared channel (e.g., PUSCH)), the non-terrestrial network may be composed 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.

[0139] Here, due to the long distance and high relative velocity between the terminal and the satellite, time-domain and / or frequency-domain synchronization errors may occur in the service link, etc. For example, the time-domain and / or frequency-domain synchronization errors may include time synchronization errors and / or Doppler shifts. Here, time-domain and / or frequency-domain synchronization errors (within a certain level) may be required during (a specific type of) terminal-to-base station transmission (e.g., UL transmission) between the base station and the terminal.

[0140] Here, the (pre)requirements for the time domain and / or frequency domain synchronization errors (within a certain level) may be defined as (pre)requirements(s) for time synchronization errors and / or Doppler shift pre-compensation (at the terminal). Here, the base station and / or the terminal may recognize the (pre)requirements(s) for the pre-compensation through one or more of the following methods.

[0141] (1) Preliminary agreement and / or definition between the base station and the terminal

[0142] (2) What the base station sets and / or instructs the terminal to do

[0143] (3) The terminal reports information about the time synchronization error and / or Doppler shift pre-compensation level and / or capability that can be supported by the base station.

[0144] For example, when a base station wants to set and / or instruct a terminal to perform terminal-to-base station transmission (e.g., UL transmission) to which an orthogonal cover code (e.g., OCC) (in the time domain and / or frequency domain) is applied for the purpose of multiplexing and / or increasing the capacity of a terminal-to-base station communication link (e.g., UL link), time synchronization error and / or Doppler shift pre-compensation requirement(s) (at the terminal) for maintaining orthogonality between the orthogonal cover code(s) (e.g., OCC)(s) can be defined.

[0145] For example, the (pre)requirement(s) for the above pre-compensation may be pre-arranged and / or defined, or may be set and / or instructed by the base station to the terminal. For example, the terminal may report its (terminal-side) time synchronization error and / or Doppler shift pre-compensation capabilities to the base station, and the base station may refer to the capabilities of the terminal to determine whether to apply an orthogonal cover code (e.g., OCC) in terminal-to-base station transmission (e.g., UL transmission).

[0146] According to the above proposal, there may be an advantage that the awareness of time synchronization error and / or Doppler shift pre-compensation requirement(s) (at the terminal end) during (a specific type of) terminal-to-base station transmission (e.g., UL transmission) between the base station and the terminal may be the same, and based on this, the base station may expect to receive a signal of a promised and / or defined form for said (specific type of) terminal-to-base station transmission (e.g., UL transmission).

[0147] The above [Proposal #02] can be applied in combination with other proposed method(s) as long as the operation of the disclosure does not conflict.

[0148] [Proposal #03]

[0149] According to one embodiment of the present disclosure, when there are (pre-)requirements(s) for supporting (a specific type of) terminal-to-base station transmission (e.g., UL transmission) between a base station and a terminal, a method may be provided for defining, setting, indicating, and / or reporting (pre-)requirements(s) for supporting terminal-to-base station transmission (e.g., UL transmission) to which an orthogonal cover code (e.g., OCC) is applied, by distinguishing them according to one or more of the following criteria.

[0150] (1) Orthogonal cover code (e.g., OCC) type

[0151] For example, the orthogonal cover code (eg, OCC) type can be distinguished depending on the area to which the orthogonal cover code (eg, OCC) is applied. For example, the orthogonal cover code (eg, OCC) type can be distinguished into a type in which the orthogonal cover code (eg, OCC) is applied within a symbol (in orthogonal frequency division multiplexing (eg, OFDM)), a type in which the orthogonal cover code (eg, OCC) is applied between symbol groups (in orthogonal frequency division multiplexing (eg, OFDM)), a type in which the orthogonal cover code (eg, OCC) is applied between slot groups (in orthogonal frequency division multiplexing (eg, OFDM)), etc.

[0152] And / or, for example, the orthogonal cover code (e.g., OCC) type can be distinguished according to the code of the orthogonal cover code (e.g., OCC). For example, the orthogonal cover code (e.g., OCC) type can be distinguished into a type to which the Walsh-Hadamard code is applied, a type to which the DFT code is applied, etc.

[0153] (2) The orthogonal cover code (e.g., OCC) application unit may mean, for example, a time domain and / or frequency domain resource unit to which the orthogonal cover code (e.g., OCC) is applied.

[0154] (3) The orthogonal cover code (eg, OCC) length may mean, for example, the orthogonal cover code (eg, OCC) code length.

[0155] (4) The orthogonal cover code (eg, OCC) identifier may mean, for example, an index for an orthogonal cover code (eg, OCC) code.

[0156] (5) Orthogonal frequency division multiplexing (e.g., OFDM) numerology may refer to, for example, subcarrier spacing, symbol duration, and cyclic prefix length in an orthogonal frequency division multiplexing (e.g., OFDM) transmission method.

[0157] Here, the above (pre)requirement(s) may be pre-arranged and / or defined between the base station and the terminal, or may be set and / or instructed by the base station to the terminal.

[0158] Here, the terminal-to-base station transmission (e.g., UL transmission) (of a specific type) may mean a terminal-to-base station transmission (e.g., UL transmission) to which an orthogonal cover code (e.g., OCC) (in the time domain and / or frequency domain) is applied. For example, when the terminal-to-base station transmission (e.g., UL transmission) to which the orthogonal cover code (e.g., OCC) is applied between a base station and a terminal, (pre) requirements for time delay and / or Doppler shift pre-compensation (at the terminal) may need to be met.

[0159] Here, the (pre) requirement(s) for supporting terminal-to-base station transmission (e.g., UL transmission) to which the above orthogonal cover code (e.g., OCC) is applied may be (pre) requirement(s) for time synchronization error and / or Doppler shift pre-compensation (at the terminal end).

[0160] Here, the above (pre) requirement(s) may be (pre) requirement(s) for a specific type of terminal. For example, the above (pre) requirement(s) may be (pre) requirement(s) for a non-terrestrial network (e.g., NTN) service terminal.

[0161] In a next-generation mobile communication system based on a non-terrestrial network according to an embodiment of the present disclosure, when a terminal transmits a terminal-to-base station communication data channel (e.g., UL link data channel) (e.g., a terminal-to-base station physical shared channel (e.g., PUSCH)), the non-terrestrial network may be composed of a terminal, a satellite, and a base station, and the terminal and the satellite may be connected via a service link, and the satellite and the base station may be connected via a feeder link.

[0162] Here, due to the long distance and high relative velocity between the terminal and the satellite, time-domain and / or frequency-domain synchronization errors may occur in the service link, etc. For example, the time-domain and / or frequency-domain synchronization errors may include time synchronization errors and / or Doppler shifts. Here, time-domain and / or frequency-domain synchronization errors (within a certain level) may be required during (a specific type of) terminal-to-base station transmission (e.g., UL transmission) between the base station and the terminal.

[0163] Here, for example, the terminal-to-base station transmission (e.g., UL transmission) (of a specific type) may mean a terminal-to-base station transmission (e.g., UL transmission) to which a (time domain and / or frequency domain) orthogonal cover code (e.g., OCC) is applied.

[0164] Here, for example, (pre)requirements for time delay and / or Doppler shift pre-compensation (at the terminal end) can be defined to achieve the above-mentioned (within a certain level) time domain and / or frequency domain synchronization errors.

[0165] For example, in a non-terrestrial network according to an embodiment of the present disclosure, when a terminal-to-base station transmission (e.g., UL transmission) using the orthogonal cover code (e.g., OCC) between a base station and a terminal is performed, (prior) requirements for time delay and / or Doppler shift pre-compensation (at the terminal) may need to be satisfied. Here, the (prior) requirement(s) may be (pre-)defined, or set and / or instructed by the base station to the terminal, or reported by the terminal to the base station.

[0166] Here, for example, the above (pre)requirement(s) may be defined, set, indicated, and / or reported based on at least one of an orthogonal cover code (e.g., OCC) type, an orthogonal cover code (e.g., OCC) application unit, an orthogonal cover code (e.g., OCC) length, an orthogonal cover code (e.g., OCC) identification information, an orthogonal frequency division multiplexing (e.g., OFDM) numerology, etc.

[0167] For example, (pre)requirement(s) per orthogonal cover code (e.g., OCC) application unit and orthogonal cover code (e.g., OCC) length combination may be defined, set, directed, and / or reported.

[0168] Here, the proposed method of the present disclosure may include a method of reporting the support / capability level by classifying it based on at least one of an orthogonal cover code (e.g., OCC) type, an orthogonal cover code (e.g., OCC) application unit, an orthogonal cover code (e.g., OCC) length, an orthogonal cover code (e.g., OCC) identification information, an orthogonal frequency division multiplexing (e.g., OFDM) numerology, etc. when the terminal reports the support / capability level for time synchronization error and / or Doppler shift pre-compensation (at the terminal end) to the base station.

[0169] For example, when a terminal reports support(s) for time delay and / or Doppler shift pre-compensation (at the terminal end) to a base station (or network), the support(s) may be reported based on at least one of orthogonal cover code (e.g., OCC) type, orthogonal cover code (e.g., OCC) application unit, orthogonal cover code (e.g., OCC) length, orthogonal cover code (e.g., OCC) identification information, orthogonal frequency division multiplexing (e.g., OFDM) numerology, etc.

[0170] For example, a terminal may report to a base station (or network) pre-compensation support items(s) for each orthogonal cover code (e.g., OCC) application unit and orthogonal cover code (e.g., OCC) length combination.

[0171] According to the above proposal, when performing terminal-to-base station transmission (e.g., UL transmission) based on orthogonal cover code (e.g., OCC) between a base station and a terminal, there may be an advantage in that suitable (pre)requirement(s) can be shared for each detailed setting of the orthogonal cover code (e.g., OCC).

[0172] The above [Proposal #03] can be applied in combination with other proposed method(s) as long as the operation of the disclosure does not conflict.

[0173] [Proposal #04]

[0174] According to one embodiment of the present disclosure, when there are (pre-)requirement(s) to support (a specific type of) terminal-to-base station transmission (e.g., UL transmission) between a base station and a terminal, a method may be provided for a terminal to report to the base station whether the (pre-)requirement(s) are met and / or not met.

[0175] Here, the terminal-to-base station transmission (e.g., UL transmission) (of a specific type) may mean a terminal-to-base station transmission (e.g., UL transmission) to which an orthogonal cover code (e.g., OCC) (in the time domain and / or frequency domain) is applied. For example, when the terminal-to-base station transmission (e.g., UL transmission) to which the orthogonal cover code (e.g., OCC) is applied between a base station and a terminal, (pre) requirements for time delay and / or Doppler shift pre-compensation (at the terminal) may need to be met.

[0176] Here, the above (pre)requirement(s) may be pre-arranged and / or defined between the base station and the terminal, or may be set and / or instructed by the base station to the terminal.

[0177] Here, the above (pre) requirement(s) may be (pre) requirement(s) (hereinafter, first requirement(s)) for time synchronization error and / or Doppler shift pre-compensation (at the terminal) during terminal-to-base station transmission (e.g., UL transmission) to which an orthogonal cover code (e.g., OCC) is applied.

[0178] Here, for example, the first requirement(s) may be requirements for time domain and / or frequency domain synchronization error levels / ranges.

[0179] Here, the above (pre) requirement(s) may be (pre) requirement(s) for a specific type of terminal. For example, the above (pre) requirement(s) may be (pre) requirement(s) for a non-terrestrial network (e.g., NTN) service terminal.

[0180] In a next-generation mobile communication system based on a non-terrestrial network according to an embodiment of the present disclosure, when a terminal transmits a terminal-to-base station communication data channel (e.g., UL link data channel) (e.g., a terminal-to-base station physical shared channel (e.g., PUSCH)), the non-terrestrial network may be composed of a terminal, a satellite, and a base station, and the terminal and the satellite may be connected via a service link, and the satellite and the base station may be connected via a feeder link.

[0181] Here, due to the long distance and high relative velocity between the terminal and the satellite, time-domain and / or frequency-domain synchronization errors may occur in the service link, etc. For example, the time-domain and / or frequency-domain synchronization errors may include time synchronization errors and / or Doppler shifts. Here, time-domain and / or frequency-domain synchronization errors (within a certain level) may be required during (a specific type of) terminal-to-base station transmission (e.g., UL transmission) between the base station and the terminal.

[0182] Here, the terminal-to-base station transmission (e.g., UL transmission) (of a specific type) may mean a terminal-to-base station transmission (e.g., UL transmission) to which an orthogonal cover code (e.g., OCC) (in the time domain and / or frequency domain) is applied. Here, in order to achieve the time domain and / or frequency domain synchronization error (within a certain level), a (pre) requirement for time delay and / or Doppler shift pre-compensation (at the terminal) may be defined.

[0183] For example, in a non-terrestrial network according to one embodiment of the present disclosure, when the terminal-to-base station transmission (e.g., UL transmission) using the orthogonal cover code (e.g., OCC) between the base station and the terminal may require (prior) time delay and / or Doppler shift pre-compensation (at the terminal) to be satisfied. Here, the (prior) requirement(s) may be (prior) defined or may be set and / or instructed by the base station to the terminal.

[0184] Here, the base station may configure and / or instruct terminal-to-base station transmission (e.g., UL transmission) based on an orthogonal cover code (e.g., OCC) only if the terminal satisfies the (pre-) requirement(s) for the above pre-compensation. Accordingly, the terminal may need to be able to report to the base station whether the (pre-) requirement(s) are met or not.

[0185] For example, time synchronization error and / or Doppler shift pre-compensation (at the terminal) (in advance) requirement(s) for orthogonal cover code (e.g., OCC) type, orthogonal cover code (e.g., OCC) application unit, and / or orthogonal cover code (e.g., OCC) length between a base station and a terminal are (in advance) defined, and the terminal can report to the base station whether the (in advance) requirement(s) for orthogonal cover code (e.g., OCC) type, orthogonal cover code (e.g., OCC) application unit, and / or orthogonal cover code (e.g., OCC) length are met and / or not met.

[0186] Here, the above-mentioned reporting format may be a terminal capability reporting format. According to the above proposal, when performing terminal-to-base station transmission (e.g., UL transmission) based on an orthogonal cover code (e.g., OCC) between a base station and a terminal, there may be an advantage in that the base station can identify the orthogonal cover code (e.g., OCC) configuration(s) that the terminal can support, and apply the orthogonal cover code (e.g., OCC) that the terminal can support at a valid time.

[0187] The above [Proposal #04] can be applied in combination with other proposed method(s) as long as the operation of the disclosure does not conflict.

[0188] [Proposal #05]

[0189] According to one embodiment of the present disclosure, when there are (pre) requirement(s) (hereinafter referred to as first requirement(s)) in a terminal-to-base station transmission (e.g., UL transmission) to which an orthogonal cover code (e.g., OCC) is applied between a base station and a terminal, a method may be provided for performing one or more of the following exception handling operations when a terminal does not satisfy the first requirement(s) for a terminal-to-base station transmission (e.g., UL transmission) based on an orthogonal cover code (e.g., OCC) set and / or instructed by a base station.

[0190] (1) Omission of terminal-to-base station transmission (e.g., UL transmission) based on (configured and / or directed) orthogonal cover code (e.g., OCC).

[0191] (2) Non-application of orthogonal cover code (e.g., OCC) during terminal-to-base station transmission (e.g., UL transmission) based on (set and / or indicated) orthogonal cover code (e.g., OCC)

[0192] (3) Application of (default) orthogonal cover code (e.g., OCC) when terminal-to-base station transmission (e.g., UL transmission) based on (set and / or indicated) orthogonal cover code (e.g., OCC)

[0193] Here, the first requirement(s) may be pre-arranged and / or defined between the base station and the terminal, or may be set and / or instructed by the base station to the terminal.

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

[0195] Here, the first requirement(s) may be (pre)requirement(s) for time domain and / or frequency domain synchronization error level / range.

[0196] Here, the above (basic) orthogonal cover code (eg, OCC) may mean an orthogonal cover code (eg, OCC) agreed upon (in advance) between the base station and the terminal or an orthogonal cover code (eg, OCC) set by the base station.

[0197] Here, the above (pre) requirement(s) may be (pre) requirement(s) for a specific type of terminal. For example, the above (pre) requirement(s) may be (pre) requirement(s) for a non-terrestrial network (e.g., NTN) service terminal.

[0198] In a next-generation mobile communication system based on a non-terrestrial network according to an embodiment of the present disclosure, when a terminal transmits a terminal-to-base station communication data channel (e.g., UL link data channel) (e.g., a terminal-to-base station physical shared channel (e.g., PUSCH)), the non-terrestrial network may be composed of a terminal, a satellite, and a base station, and the terminal and the satellite may be connected via a service link, and the satellite and the base station may be connected via a feeder link.

[0199] Here, due to the long distance and high relative velocity between the terminal and the satellite, time-domain and / or frequency-domain synchronization errors may occur in the service link, etc. For example, the time-domain and / or frequency-domain synchronization errors may include time synchronization errors and / or Doppler shifts. Here, time-domain and / or frequency-domain synchronization errors (within a certain level) may be required during (a specific type of) terminal-to-base station transmission (e.g., UL transmission) between the base station and the terminal.

[0200] The above (specific type of) terminal-to-base station transmission (e.g., UL transmission) may mean a terminal-to-base station transmission (e.g., UL transmission) to which a (time domain and / or frequency domain) orthogonal cover code (e.g., OCC) is applied. Here, in order to achieve the above (within a certain level) time domain and / or frequency domain synchronization error, (pre)requirements for time delay and / or Doppler shift pre-compensation (at the terminal) may be defined.

[0201] For example, in a non-terrestrial network according to an embodiment of the present disclosure, when the terminal-to-base station transmission (e.g., UL transmission) is performed using the orthogonal cover code (e.g., OCC) between the base station and the terminal, (pre)requirements for time delay and / or Doppler shift pre-compensation (at the terminal end) may need to be met.

[0202] Here, if the base station sets up and / or instructs the terminal to perform a terminal-to-base station transmission (e.g., UL transmission) with a (specific) orthogonal cover code (e.g., OCC) applied to the terminal, but the terminal does not meet the (pre-)requirement(s) for applying the (specific) orthogonal cover code (e.g., OCC), an exception handling operation may be required for the transmission.

[0203] For example, if the above (pre-)requirement(s) are not met for a terminal-to-base station transmission (e.g., UL transmission) based on an orthogonal cover code (e.g., OCC) configured and / or instructed by the base station, the terminal may perform one or more of the following exception handling actions.

[0204] (1) Omission of terminal-to-base station transmission (e.g., UL transmission) based on (configured and / or directed) orthogonal cover code (e.g., OCC).

[0205] (2) Non-application of orthogonal cover code (e.g., OCC) during terminal-to-base station transmission (e.g., UL transmission) based on (set and / or indicated) orthogonal cover code (e.g., OCC)

[0206] (3) Application of (default) orthogonal cover code (e.g., OCC) during terminal-to-base station transmission (e.g., UL transmission) based on (set and / or indicated) orthogonal cover code (e.g., OCC)

[0207] According to the above proposal, an exception handling operation may be supported when a terminal does not meet (pre-)requirement(s) for a (specific type of) terminal-to-base station transmission (e.g., UL transmission) between a base station and a terminal, and this may have the advantage that the terminal-to-base station transmission (e.g., UL transmission) operation between the base station and the terminal can be performed clearly.

[0208] The above [Proposal #05] can be applied in combination with other proposed method(s) as long as the operation of the disclosure does not conflict.

[0209] [Proposal #06]

[0210] According to one embodiment of the present disclosure, when there are (pre) requirement(s) (hereinafter referred to as first requirement(s)) in a terminal-to-base station transmission (e.g., UL transmission) to which an orthogonal cover code (e.g., OCC) is applied between a base station and a terminal, a method may be provided in which a terminal reports to a base station information on a supportable orthogonal cover code (e.g., OCC) by including one or more of the following information.

[0211] (1) (Supportable) orthogonal cover code (e.g., OCC) type

[0212] (2) (Supportable) Orthogonal Cover Code (e.g., OCC) application unit

[0213] (3) (supportable) orthogonal cover code (e.g., OCC) length

[0214] (4) (supportable) orthogonal cover code (e.g., OCC) identifier (e.g., orthogonal cover code (e.g., OCC) index)

[0215] Here, the first requirement(s) may be pre-arranged and / or defined between the base station and the terminal, or may be set and / or instructed by the base station to the terminal.

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

[0217] Here, the above (pre) requirement(s) may be (pre) requirement(s) for a specific type of terminal. For example, the above (pre) requirement(s) may be (pre) requirement(s) for a non-terrestrial network (e.g., NTN) service terminal.

[0218] In a next-generation mobile communication system based on a non-terrestrial network according to an embodiment of the present disclosure, when a terminal transmits a terminal-to-base station communication data channel (e.g., UL link data channel) (e.g., a terminal-to-base station physical shared channel (e.g., PUSCH)), the non-terrestrial network may be composed of a terminal, a satellite, and a base station, and the terminal and the satellite may be connected via a service link, and the satellite and the base station may be connected via a feeder link.

[0219] Here, due to the long distance and high relative velocity between the terminal and the satellite, time-domain and / or frequency-domain synchronization errors may occur in the service link, etc. For example, the time-domain and / or frequency-domain synchronization errors may include time synchronization errors and / or Doppler shifts. Here, time-domain and / or frequency-domain synchronization errors (within a certain level) may be required during (a specific type of) terminal-to-base station transmission (e.g., UL transmission) between the base station and the terminal.

[0220] The above (specific type of) terminal-to-base station transmission (e.g., UL transmission) may mean a terminal-to-base station transmission (e.g., UL transmission) to which a (time domain and / or frequency domain) orthogonal cover code (e.g., OCC) is applied. Here, in order to achieve the above (within a certain level) time domain and / or frequency domain synchronization error, (pre)requirements for time delay and / or Doppler shift pre-compensation (at the terminal) may be defined.

[0221] For example, in a non-terrestrial network according to an embodiment of the present disclosure, when the terminal-to-base station transmission (e.g., UL transmission) using the orthogonal cover code (e.g., OCC) between the base station and the terminal may require (prior) time delay and / or Doppler shift pre-compensation (at the terminal) to be satisfied. Here, the (prior) requirement(s) may be (prior) agreed upon and / or defined between the base station and the terminal.

[0222] Here, the terminal can report to the base station (or network) the orthogonal cover code (e.g., OCC) information that it can support (by itself) based on the above (pre-)requirement(s).

[0223] For example, the terminal may report information such as (supportable) orthogonal cover code (e.g., OCC) type, (supportable) orthogonal cover code (e.g., OCC) application unit, (supportable) orthogonal cover code (e.g., OCC) length, (supportable) orthogonal cover code (e.g., OCC) identifier (e.g., orthogonal cover code (e.g., OCC) index) to the base station.

[0224] According to the above proposal, there may be an advantage in that the base station can obtain information on orthogonal cover codes (e.g., OCC) that the terminal can support in advance, and set and / or indicate a valid orthogonal cover code (e.g., OCC) during terminal-to-base station transmission (e.g., UL transmission).

[0225] The above [Proposal #06] can be applied in combination with other proposed method(s) as long as the operation of the disclosure does not conflict.

[0226] [Proposal #07]

[0227] According to one embodiment of the present disclosure, when a terminal can apply an orthogonal cover code (e.g., OCC) for a terminal-to-base station transmission (e.g., UL transmission) signal (and / or its repeated transmission), a method may be provided in which the terminal reports (terminal) capability information for the (supportable) orthogonal cover code (e.g., OCC) to a base station, and the base station assumes that one or more of the following condition(s) are satisfied for the (supportable) orthogonal cover code (e.g., OCC).

[0228] (1) Maintaining phase continuity (of terminal signal) (within the orthogonal cover code (e.g., OCC) application section)

[0229] (2) Maintaining power consistency (of terminal signals) (within the orthogonal cover code (e.g., OCC) application range)

[0230] (3) (When transmitting resources using orthogonal cover codes (e.g., OCC)) Pre-compensation for time differences (or timing errors (offsets)) (within a certain level)

[0231] (4) (When transmitting resources using orthogonal cover codes (e.g., OCC)) (within a certain level) Doppler shift pre-compensation

[0232] (5) Repeated generation and / or mapping of the same signal (by orthogonal cover code (e.g., OCC) application unit)

[0233] (6) Support for application of orthogonal cover code (e.g., OCC) (for terminal-to-base station transmission (e.g., UL transmission) signals)

[0234] Here, whether or not to apply the orthogonal cover code (e.g., OCC) can be set and / or indicated by the base station.

[0235] Here, the orthogonal cover code (e.g., OCC) may be applied between repeated transmissions.

[0236] Here, the terminal-to-base station transmission (e.g., UL transmission) signal may be a terminal-to-base station communication data channel (e.g., UL link data channel) (e.g., terminal-to-base station physical shared channel (e.g., PUSCH)).

[0237] Here, 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.

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

[0239] Here, when reporting (terminal) capability information for (supportable) orthogonal cover codes (e.g., OCC), the terminal may include information on the orthogonal cover code (e.g., OCC) length and / or the orthogonal cover code (e.g., OCC) application unit in the report. For example, if the orthogonal cover code (e.g., OCC) length is 4 and the orthogonal cover code (e.g., OCC) application unit is 1 slot, an orthogonal cover code (e.g., OCC) of length 4 may be applied to 4 slot(s).

[0240] In a next-generation mobile communication system based on a non-terrestrial network according to an embodiment of the present disclosure, when a terminal transmits a terminal-to-base station communication data channel (e.g., UL link data channel) (e.g., a terminal-to-base station physical shared channel (e.g., PUSCH)), the non-terrestrial network may be composed of a terminal, a satellite, and a base station, and the terminal and the satellite may be connected via a service link, and the satellite and the base station may be connected via a feeder link.

[0241] Here, the area served by the non-terrestrial network, for example, a satellite, may be relatively wide compared to conventional cell coverage, and the terminal may need to perform repeated transmissions, etc. on the terminal-to-base station communication link (e.g., UL link) to support coverage.

[0242] Here, the efficiency of resource utilization may be reduced during the above-described repeated transmission, and a method of increasing the terminal-to-base station transmission (e.g., UL transmission) capacity by supporting orthogonal cover code (e.g., OCC)-based multiplexing between repeated transmissions of the terminal-to-base station communication link (e.g., UL link) may be considered.

[0243] Here, the base station must be able to determine whether the terminal can apply an orthogonal cover code (e.g., OCC) during terminal-to-base station transmission (e.g., UL transmission), and the terminal can report (terminal) capability information for the orthogonal cover code (e.g., OCC) to the base station.

[0244] Here, the terminal can convey its orthogonal cover code (e.g., OCC) application capability to the base station by reporting (supportable) orthogonal cover code (e.g., OCC) information. Here, the base station can expect that the following condition(s) are satisfied for the (supportable) orthogonal cover code (e.g., OCC) reported by the terminal.

[0245] (1) Maintaining phase continuity (of terminal signal) (within the orthogonal cover code (e.g., OCC) application section)

[0246] (2) Maintaining power consistency (of terminal signals) (within the orthogonal cover code (e.g., OCC) application range)

[0247] (3) (When transmitting resources using orthogonal cover codes (e.g., OCC)) Pre-compensation for time differences (or timing errors) (within a certain level)

[0248] (4) (When transmitting resources using orthogonal cover codes (e.g., OCC)) (within a certain level) Doppler shift pre-compensation

[0249] (5) Repeated generation and / or mapping of the same signal (by orthogonal cover code (e.g., OCC) application unit)

[0250] (6) Support for application of orthogonal cover code (e.g., OCC) (for terminal-to-base station transmission (e.g., UL transmission) signals)

[0251] Here, in the case of a terminal that supports communication with a non-terrestrial network, if the terminal reports support for a (specific) orthogonal cover code (e.g., OCC), the base station may assume that the terminal can support time difference (or timing error) and / or Doppler shift pre-compensation (within a certain level) within the section to which the orthogonal cover code (e.g., OCC) is applied.

[0252] Here, the requirements for the time difference (or timing error) and / or Doppler shift pre-compensation accuracy may be (pre-)configured and / or defined between the base station and the terminal. Here, the supportability (or the fact that support is possible) for the (specific) orthogonal cover code (e.g., OCC) may imply the maintenance of phase continuity and / or power consistency within the section to which the orthogonal cover code (e.g., OCC) is applied.

[0253] Here, the orthogonal cover code (eg, OCC) may be an orthogonal cover code (eg, OCC) applied between repeated transmissions of a terminal-to-base station communication data channel (eg, UL link data channel) (e.g., a terminal-to-base station physical shared channel (eg, PUSCH)), and in the above case, support for (or support being possible) a (specific) orthogonal cover code (eg, OCC) may imply that support for repeated transmissions of a terminal-to-base station physical shared channel (eg, PUSCH) is possible.

[0254] According to the above proposal, when a terminal reports its orthogonal cover code (e.g., OCC) support capability to a base station, the base station can naturally identify the relevant detailed capabilities, thereby providing an advantage in enabling the base station to accurately identify the terminal capabilities.

[0255] The above [Proposal #07] can be applied in combination with other proposed method(s) as long as the operation of the disclosure does not conflict.

[0256] [Proposal #08]

[0257] According to one embodiment of the present disclosure, when a terminal can apply an orthogonal cover code (e.g., OCC) (hereinafter, orthogonal cover code (e.g., OCC)) to a terminal-to-base station transmission (e.g., UL transmission) signal (and / or its repeated transmission), a method may be provided in which the terminal reports one or more of the following (terminal) capability information to a base station, and the base station determines that the terminal has the orthogonal cover code (e.g., OCC) support capability if a (specific) combination of (terminal) capabilities is supported (or, if the supported capabilities satisfy the specific combination).

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

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

[0260] (3) Time difference (or timing error) pre-compensation capability (within a certain time interval and / or frequency interval)

[0261] (4) Doppler shift pre-compensation capability (within a certain time interval and / or frequency interval)

[0262] (5) Capability for repeated generation and / or mapping of the same signal (or repeated transmission capability on a terminal-to-base station physical shared channel (e.g., PUSCH))

[0263] (6) Signal generation capability with applied orthogonal cover code (e.g., OCC) (for terminal-to-base station transmission (e.g., UL transmission) signal)

[0264] Here, whether or not to apply the orthogonal cover code (e.g., OCC) can be set and / or indicated by the base station.

[0265] Here, the orthogonal cover code (e.g., OCC) may be applied between repeated transmissions.

[0266] Here, the terminal-to-base station transmission (e.g., UL transmission) signal may be a terminal-to-base station communication data channel (e.g., UL link data channel) (e.g., terminal-to-base station physical shared channel (e.g., PUSCH)).

[0267] Here, maintaining the phase continuity and / or establishing power consistency may mean that the phase and / or power change (of the terminal signal) is within a certain (error) range (e.g., during a specific time interval).

[0268] Here, the time difference (or timing error) pre-compensation and / or Doppler shift pre-compensation may mean that the time domain and / or frequency domain synchronization is within a certain (error) range (e.g., after the pre-compensation operation). Here, the requirements and / or error ranges for the time difference (or timing error) pre-compensation and / or Doppler shift pre-compensation may be (pre-)set and / or (pre-)defined between the base station and the terminal.

[0269] Here, the terminal may report terminal capabilities related to phase continuity and / or power consistency in the form of terminal capabilities related to bundling of demodulation reference signals (e.g., DM-RS; demodulation reference signal) (e.g., maxDMRS-BundlingDuration). Here, maxDMRS-BundlingDuration may mean the maximum time period during which the terminal can maintain phase continuity and / or power consistency, etc.

[0270] In a next-generation mobile communication system based on a non-terrestrial network according to an embodiment of the present disclosure, when a terminal transmits a terminal-to-base station communication data channel (e.g., UL link data channel) (e.g., a terminal-to-base station physical shared channel (e.g., PUSCH)), the non-terrestrial network may be composed of a terminal, a satellite, and a base station, and the terminal and the satellite may be connected via a service link, and the satellite and the base station may be connected via a feeder link.

[0271] Here, the area served by the non-terrestrial network, for example, a satellite, may be relatively wide compared to conventional cell coverage, and the terminal may need to perform repeated transmissions, etc. on the terminal-to-base station communication link (e.g., UL link) to support coverage.

[0272] Here, the efficiency of resource utilization may be reduced during the above-described repeated transmission, and a method of increasing the terminal-to-base station transmission (e.g., UL transmission) capacity by supporting orthogonal cover code (e.g., OCC)-based multiplexing between repeated transmissions of the terminal-to-base station communication link (e.g., UL link) may be considered.

[0273] Here, the base station must be able to determine whether the terminal can apply an orthogonal cover code (e.g., OCC) during terminal-to-base station transmission (e.g., UL transmission), and the terminal can report (terminal) capability information for the orthogonal cover code (e.g., OCC) to the base station.

[0274] Here, the terminal can communicate its orthogonal cover code (e.g., OCC) application capability to the base station by reporting one or more terminal capability(s) related to the application of orthogonal cover codes (e.g., OCC). For example, the terminal may report one or more of the following capability(s), and the base station may recognize that the terminal has orthogonal cover code (e.g., OCC) application capability based on the combination of capabilities.

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

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

[0277] (3) Time difference (or timing error) pre-compensation capability (within a certain time interval and / or frequency interval)

[0278] (4) Doppler shift pre-compensation capability (within a certain time interval and / or frequency interval)

[0279] (5) Capability for repeated generation and / or mapping of the same signal (or repeated transmission capability on a terminal-to-base station physical shared channel (e.g., PUSCH))

[0280] (6) Signal generation capability with applied orthogonal cover code (e.g., OCC) (for terminal-to-base station transmission (e.g., UL transmission) signal)

[0281] Here, the signal generation capability with an orthogonal cover code (e.g., OCC) applied (for a terminal-to-base station transmission (e.g., UL transmission) signal) may simply mean that the terminal can generate a signal with an orthogonal cover code (e.g., OCC), and may not guarantee orthogonality between orthogonal cover codes (e.g., OCC). For example, even if the terminal reports the signal generation capability with an orthogonal cover code (e.g., OCC) applied, if the terminal reports that it does not have the capability to maintain phase continuity and / or power consistency, or that the phase continuity and / or power consistency maintenance time interval is shorter than the orthogonal cover code (e.g., OCC) length and / or the orthogonal cover code (e.g., OCC) application interval, the base station may determine that it is difficult for the terminal to support an orthogonal cover code (e.g., OCC) that guarantees orthogonality, and may not set the application of the orthogonal cover code (e.g., OCC) for terminal-to-base station transmission (e.g., UL transmission). In other words, in order for a base station to configure an orthogonal cover code (e.g., OCC) for terminal-to-base station transmission (e.g., UL transmission), one or more terminal capabilities related to the orthogonal cover code (e.g., OCC) may need to be supported. According to the above proposal, when a terminal reports its orthogonal cover code (e.g., OCC) support capability to the base station, the base station may have the advantage of being able to accurately identify the terminal capabilities by naturally enabling the base station to identify the related detailed capabilities.

[0282] The above [Proposal #08] can be applied in combination with other proposed method(s) as long as the operation of the disclosure does not conflict.

[0283] [Proposal #09]

[0284] According to one embodiment of the present disclosure, when a terminal can apply an orthogonal cover code (e.g., OCC) (hereinafter, orthogonal cover code (e.g., OCC)) to a terminal-to-base station transmission (e.g., UL transmission) signal (and / or its repeated transmission), a method may be provided in which the terminal reports (terminal) capability information related to the orthogonal cover code (e.g., OCC) to a base station through a first process, and reports information related to the validity (within a certain time interval and / or frequency interval) of the orthogonal cover code (e.g., OCC) (or whether an orthogonal cover code (e.g., OCC) application condition is satisfied) to the base station through a second process (different from the first process).

[0285] Here, the second process may include one or more of the following method(s).

[0286] (1) A method in which a base station sends a trigger signal and a terminal reports upon receiving the trigger signal.

[0287] (2) A method in which a base station sets an event and a terminal reports when an event occurs.

[0288] (3) Terminal-led reporting method

[0289] Here, whether or not to apply the orthogonal cover code (e.g., OCC) can be set and / or indicated by the base station.

[0290] Here, the orthogonal cover code (e.g., OCC) may be applied between repeated transmissions.

[0291] Here, the terminal-to-base station transmission (e.g., UL transmission) signal may be a terminal-to-base station communication data channel (e.g., UL link data channel) (e.g., terminal-to-base station physical shared channel (e.g., PUSCH)).

[0292] Here, the base station can transmit to the terminal event settings and / or report (resource) settings for reporting information related to the validity of the orthogonal cover code (e.g., OCC) (or conditions for applying the orthogonal cover code (e.g., OCC)).

[0293] Here, the terminal can report information related to the validity of the orthogonal cover code (e.g., OCC) (or conditions for applying the orthogonal cover code (e.g., OCC)) to the base station in the form of UE Assistance Information, etc.

[0294] Here, the validity of the orthogonal cover code (e.g., OCC) (or the application condition of the orthogonal cover code (e.g., OCC)) may refer to information related to conditions for maintaining orthogonality based on the orthogonal cover code (e.g., OCC). For example, it may refer to whether time and / or frequency domain synchronization conditions for applying the orthogonal cover code (e.g., OCC) are met.

[0295] In a next-generation mobile communication system based on a non-terrestrial network according to an embodiment of the present disclosure, when a terminal transmits a terminal-to-base station communication data channel (e.g., UL link data channel) (e.g., a terminal-to-base station physical shared channel (e.g., PUSCH)), the non-terrestrial network may be composed of a terminal, a satellite, and a base station, and the terminal and the satellite may be connected via a service link, and the satellite and the base station may be connected via a feeder link.

[0296] Here, the area served by the non-terrestrial network, for example, a satellite, may be relatively much wider than the conventional cell coverage, and to support coverage, the terminal may need to perform repeated transmissions, etc., on the terminal-to-base station communication link (e.g., UL link). Here, the efficiency of resource utilization may be reduced during the repeated transmissions, and a method of increasing the terminal-to-base station transmission (e.g., UL transmission) capacity by supporting orthogonal cover code (e.g., OCC)-based multiplexing between repeated transmissions on the terminal-to-base station communication link (e.g., UL link) may be considered.

[0297] Here, the base station must be able to determine whether the terminal can apply an orthogonal cover code (e.g., OCC) during terminal-to-base station transmission (e.g., UL transmission), and the terminal can report (terminal) capability information for the orthogonal cover code (e.g., OCC) to the base station.

[0298] Here, the conditions for applying an orthogonal cover code (e.g., OCC) when the terminal transmits from terminal to base station (e.g., UL transmission) can be broadly divided into terminal internal conditions and terminal external conditions.

[0299] Here, the terminal internal conditions for applying the orthogonal cover code (e.g., OCC) are included in the terminal's orthogonal cover code (e.g., OCC) support capability and are reported as a first process, and the terminal external conditions for applying the orthogonal cover code (e.g., OCC) can be reported as a second process that is separate from the first process.

[0300] For example, a terminal may report phase continuity and / or power consistency maintenance capabilities, terminal-to-base station physical shared channel (e.g., PUSCH) repetition transmission capabilities, and orthogonal cover code (e.g., OCC) applied signal generation capabilities as terminal capabilities, while time difference (or timing error) and / or Doppler shift pre-compensation capabilities may be reported in a separate process. For example, time difference (or timing error) and / or Doppler shift pre-compensation capabilities may be reported in one or more of the following methods(s):

[0301] (1) A method in which a base station sends a trigger signal and a terminal reports upon receiving the trigger signal.

[0302] (2) A method in which a base station sets an event and a terminal reports when an event occurs.

[0303] (3) Terminal-led reporting method

[0304] Here, when reporting the orthogonal cover code (e.g., OCC) validity-related information to the base station, the terminal may report in a manner that utilizes an explicit reporting resource and / or modifies / utilizes existing resources, such as including it in the demodulation reference signal (e.g., DM-RS) scrambling information.

[0305] According to the above proposal, among the conditions for applying an orthogonal cover code (e.g., OCC), (dynamic) factors depending on the external environment, such as the channel environment, are reported in a separate process other than the terminal capability reporting process that is statically reported, thereby helping the base station and / or terminal to dynamically identify the conditions for applying an orthogonal cover code (e.g., OCC).

[0306] The above [Proposal #09] can be applied in combination with other proposed method(s) as long as the operation of the disclosure does not conflict.

[0307] The above proposed method can be applied to the device described below. First, the processor (202) of the receiving terminal can set at least one partial bandwidth (e.g., BWP; bandwidth part). Then, the processor (202) of the receiving terminal can control the transceiver (206) of the receiving terminal to receive a physical channel related to terminal-to-terminal communication (e.g., SL communication) and / or a reference signal related to terminal-to-terminal communication (e.g., SL communication) from the transmitting terminal on at least one partial bandwidth (e.g., BWP).

[0308] In non-terrestrial networks (e.g., NTN) that utilize satellites and other network nodes, the satellite's service area may have very wide coverage characteristics, and the number of target terminals within that service area may be relatively large. Therefore, the non-terrestrial network (e.g., NTN) service may require multiplexing support for multiple terminal(s).

[0309] Here, since terrestrial terminals have transmission power constraints, coverage extension techniques may be applied to ensure that signals of sufficient size reach high-altitude non-terrestrial networks (e.g., NTNs) during terminal-to-base station (e.g., UL) transmission. For example, terminals can achieve coverage extension by repeatedly transmitting a terminal-to-base station physical shared channel (e.g., PUSCH; Physical Uplink Shared Channel), which is a terminal-to-base station (e.g., UL) data channel, on the time axis. However, the coverage extension technique may reduce the efficiency of resource utilization due to repeated transmissions, and to solve this, a terminal-to-base station communication (e.g., UL communication) multiplexing operation utilizing an orthogonal cover code (e.g., OCC; Orthogonal Cover Code) may be effective.

[0310] Here, in order to maintain orthogonality between different orthogonal cover codes (e.g., OCC), it may be assumed that the channel variation is small within the time and / or frequency interval to which the orthogonal cover code (e.g., OCC) is applied. Here, from the perspective of a terminal receiving a non-terrestrial network (e.g., NTN)-based service, problems such as Doppler shift due to high relative speed between the satellite and the terminal and / or time delay due to long communication distance between the satellite and the terminal may be aggravated compared to conventional terrestrial network (e.g., TN; terrestrial network)-based communication. Therefore, in the non-terrestrial network (e.g., NTN), in order to achieve multiplexing and / or capacity increase of the orthogonal cover code (e.g., OCC)-based terminal-to-base station link (e.g., UL link), it may be necessary to confirm whether terminal-to-base station transmission (e.g., UL transmission) between base stations and / or terminals is suitable for applying the orthogonal cover code (e.g., OCC).

[0311] According to various embodiments of the present disclosure, a method and apparatus for pre-compensation-based terminal-to-base station transmission (e.g., UL transmission) in a non-terrestrial network (e.g., NTN) may be provided. For example, according to various embodiments of the present disclosure, a method for defining (pre-)requirements of a terminal for applying an orthogonal cover code (e.g., OCC), a method for a base station to set the (pre-)requirements, a method for a terminal to report information related to its capabilities related to the (pre-)requirements, a method for differentiating (or setting differently) the (pre-)requirements according to the type / length of an orthogonal cover code (e.g., OCC), a method related to exception handling (or subsequent actions) when the (pre-)requirements are not met, a method for reporting capabilities of a terminal related to an orthogonal cover code (e.g., OCC), a method for defining (pre-)requirements linked to capabilities for supporting an orthogonal cover code (e.g., OCC), a method for reporting validity related to an orthogonal cover code (e.g., OCC), and a separate method for setting parameters of an orthogonal cover code (e.g., OCC) based on fallback base station-to-terminal control information (e.g., DCI) may be provided.

[0312] In particular, according to one embodiment of the present disclosure, a method may be provided in which the requirements after pre-compensation operations related to time delay and / or Doppler shift in a non-terrestrial network (e.g., NTN) are set (or determined) differently (or more strictly) depending on the type of multiple slot-based transmissions (e.g., terminal-to-base station physical shared channel (e.g., PUSCH) repetitions, orthogonal cover code (e.g., OCC) group-based transmissions, etc.).

[0313] According to various embodiments of the present disclosure, from the perspective of a terminal receiving a non-terrestrial network (e.g., NTN)-based service, which may be aggravated by problems such as Doppler shift due to high relative speed between a satellite and a terminal and / or time delay due to long communication distance between a satellite and a terminal, multiplexing and / or capacity increase of a terminal-to-base station link (e.g., UL link) based on an orthogonal cover code (e.g., OCC) can be achieved in the non-terrestrial network (e.g., NTN) by performing transmission only when terminal-to-base station transmission (e.g., UL transmission) between a base station and / or a terminal is suitable for applying an orthogonal cover code (e.g., OCC).

[0314] FIG. 10 illustrates a procedure of a method that may be performed by a first device according to an embodiment of the present disclosure. The embodiment of FIG. 10 may be combined with various embodiments of the present disclosure.

[0315] Referring to FIG. 10, in step S1010, the first device may obtain information related to requirements related to synchronization offset. In step S1020, the first device may perform a pre-compensation operation. In step S1030, the first device may perform multiple slot-based transmissions based on the synchronization offset value and the requirements after performing the pre-compensation operation.

[0316] For example, the plurality of slot-based transmissions may be terminal-to-base station transmissions transmitted to a base station, and the terminal-to-base station transmissions may include transmissions transmitted via terminal-to-base station physical shared channel repetition.

[0317] For example, the base station may be associated with a non-terrestrial network.

[0318] For example, an orthogonal cover code may be applied between transmissions transmitted over the terminal-to-base station physical shared channel repetition.

[0319] For example, the above requirements may vary depending on parameters associated with the orthogonal cover code.

[0320] For example, additionally, the first device may transmit information to the base station regarding the capabilities of the first device associated with the orthogonal cover code. For example, the capabilities of the first device associated with the orthogonal cover code may vary depending on the length of the orthogonal cover code.

[0321] For example, additionally, the first device may transmit information to the base station regarding the capabilities of the first device associated with the orthogonal cover code. For example, the capabilities of the first device associated with the orthogonal cover code may include at least one of capabilities associated with phase continuity and capabilities associated with power consistency.

[0322] For example, additionally, the first device may transmit information to the base station regarding capabilities related to the pre-compensation operation that may be supported by the first device. For example, the pre-compensation operation may be related to timing offset or Doppler shift.

[0323] For example, the above requirements may vary depending on the type of transmission being performed, and the type of transmission may include multiple slot-based transmission or single slot-based transmission.

[0324] For example, the synchronization error may be an error relative to a synchronization reference of a base station, and the requirement may be related to a timing error between a second resource of the first device and the first resource after performing the pre-compensation operation corresponding to the first resource according to the synchronization reference.

[0325] For example, the synchronization error may be a timing error or a frequency offset.

[0326] For example, the above requirement may relate to the rate of change in synchronization error between transmissions performed by the first device.

[0327] The above-described embodiment can be applied to various devices described below. First, the processor (102) of the first device (100) can obtain information related to requirements related to synchronization offset. Then, the processor (102) of the first device (100) can perform a pre-compensation operation. Then, the processor (102) of the first device (100) can control the transceiver (106) to perform multiple slot-based transmissions based on the synchronization offset value and the requirements after performing the pre-compensation operation. For example, the requirements may vary depending on the type of transmission being performed.

[0328] 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 coupled to the at least one processor and storing instructions. For example, the instructions, based on execution by the at least one processor, may cause the first device to: obtain information related to a requirement related to a synchronization offset; perform a pre-compensation operation; and, based on a synchronization offset value and the requirement after performing the pre-compensation operation, perform multiple slot-based transmissions.

[0329] For example, the plurality of slot-based transmissions may be terminal-to-base station transmissions transmitted to a base station, and the terminal-to-base station transmissions may include transmissions transmitted via terminal-to-base station physical shared channel repetition.

[0330] For example, the base station may be associated with a non-terrestrial network.

[0331] For example, an orthogonal cover code may be applied between transmissions transmitted over the terminal-to-base station physical shared channel repetition.

[0332] For example, the above requirements may vary depending on parameters associated with the orthogonal cover code.

[0333] For example, additionally, the instructions, based on being executed by the at least one processor, may cause the first device to: transmit information about the capabilities of the first device associated with the orthogonal cover code to the base station. For example, the capabilities of the first device associated with the orthogonal cover code may vary depending on the length of the orthogonal cover code.

[0334] For example, additionally, the instructions, based on being executed by the at least one processor, may cause the first device to: transmit information about capabilities of the first device related to the orthogonal cover code to the base station. For example, the capabilities of the first device related to the orthogonal cover code may include at least one of capabilities related to phase continuity or capabilities related to power consistency.

[0335] For example, additionally, the instructions, based on being executed by the at least one processor, may cause the first device to: transmit to the base station information about capabilities related to the pre-compensation operation that may be supported by the first device. For example, the pre-compensation operation may be related to a timing offset or a Doppler shift.

[0336] For example, the above requirements may vary depending on the type of transmission being performed, and the type of transmission may include multiple slot-based transmission or single slot-based transmission.

[0337] For example, the synchronization error may be an error relative to a synchronization reference of a base station, and the requirement may be related to a timing error between a second resource of the first device and the first resource after performing the pre-compensation operation corresponding to the first resource according to the synchronization reference.

[0338] For example, the synchronization error may be a timing error or a frequency offset.

[0339] For example, the above requirement may relate to the rate of change in synchronization error between transmissions performed by the first device.

[0340] 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 coupled to the at least one processor and storing instructions. For example, the instructions, based on execution by the at least one processor, may cause the first device to: obtain information related to a requirement related to a synchronization offset; perform a pre-compensation operation; and, based on a synchronization offset value and the requirement after performing the pre-compensation operation, perform multiple slot-based transmissions.

[0341] According to one embodiment of the present disclosure, a non-transitory computer-readable storage medium having instructions recorded thereon may be provided. For example, the instructions, when executed, may cause a first device to: obtain information related to requirements related to synchronization offset; perform a pre-compensation operation; and, based on a synchronization offset value and the requirements after performing the pre-compensation operation, perform multiple slot-based transmissions.

[0342] FIG. 11 illustrates a procedure of a method that may be performed by a second device according to an embodiment of the present disclosure. The embodiment of FIG. 11 may be combined with various embodiments of the present disclosure.

[0343] Referring to FIG. 11, in step S1110, the second device may transmit information related to requirements related to synchronization offset to the first device. In step S1120, the second device may receive multiple slot-based transmissions from the first device. For example, the multiple slot-based transmissions may be performed based on the synchronization offset value of the first device and the requirements after a pre-compensation operation is performed.

[0344] For example, the above requirements may vary depending on the type of transmission being performed.

[0345] For example, the plurality of slot-based transmissions may be transmissions transmitted via terminal-to-base station physical shared channel repetition.

[0346] The above-described embodiment can be applied to various devices described below. First, the processor (202) of the second device (200) can control the transceiver (206) to transmit information related to requirements related to synchronization offset to the first device (100). Then, the processor (202) of the second device (200) can control the transceiver (206) to receive multiple slot-based transmissions from the first device (100). For example, the multiple slot-based transmissions can be performed based on the synchronization offset value of the first device (100) and the requirements after a pre-compensation operation is performed.

[0347] 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 coupled to the at least one processor and storing instructions. For example, the instructions, based on execution by the at least one processor, cause the second device to: transmit information related to a requirement related to a synchronization offset to a first device; and receive a plurality of slot-based transmissions from the first device, wherein the plurality of slot-based transmissions may be performed based on a synchronization offset value of the first device and the requirement after a pre-compensation operation is performed.

[0348] For example, the above requirements may vary depending on the type of transmission being performed.

[0349] For example, the plurality of slot-based transmissions may be transmissions transmitted via terminal-to-base station physical shared channel repetition.

[0350] The various embodiments of the present disclosure may be combined with each other.

[0351] Below, a description is given of devices to which various embodiments of the present disclosure can be applied.

[0352] Although not limited thereto, the various descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed in this document may be applied to various fields requiring wireless communication / connectivity (e.g., 5G) between devices.

[0353] Hereinafter, more specific examples will be provided with reference to the drawings. In the drawings / descriptions below, the same drawing reference numerals may represent identical or corresponding hardware blocks, software blocks, or functional blocks, unless otherwise described.

[0354] FIG. 12 illustrates a communication system (1) according to one embodiment of the present disclosure. The embodiment of FIG. 12 can be combined with various embodiments of the present disclosure.

[0355] Referring to FIG. 12, 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 a wireless access technology (e.g., 5G NR (New RAT), LTE (Long Term Evolution)) and may be referred to as a communication / wireless / 5G 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 Things) device (100f), and an AI device / server (400). For example, the vehicle may include a vehicle equipped with a wireless communication function, an autonomous vehicle, a vehicle capable of performing vehicle-to-vehicle communication, etc. Here, the vehicle may include an Unmanned Aerial Vehicle (UAV) (e.g., a drone) and / or an Aerial Vehicle (AV) (e.g., an Advanced Air Mobility (AAM)). The XR device may include 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, a digital signage, a vehicle, a robot, etc. The portable device may include a smartphone, a smart pad, a wearable device (e.g., a smart watch, smart glasses), a computer (e.g., a laptop, etc.), 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 also be implemented as a wireless device, and a specific wireless device (200a) may operate as a base station / network node to other wireless devices.

[0356] Here, the wireless communication technology implemented in the wireless devices (100a to 100f) of the present disclosure may include not only LTE, NR, and 6G, but also Narrowband Internet of Things for low-power communication. At this time, for example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology, and may be implemented with standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the above-described names. Additionally or alternatively, the wireless communication technology implemented in the wireless devices (100a to 100f) of the present disclosure may perform communication based on LTE-M technology. At this time, for example, LTE-M technology may be an example of LPWAN technology, and may be called by various names such as eMTC (enhanced Machine Type Communication). For example, LTE-M technology can be implemented by 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 above-described names. Additionally or alternatively, the wireless communication technology implemented in the wireless devices (100a to 100f) of the present disclosure can include at least one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN) considering low-power communication, and is not limited to the above-described names. For example, ZigBee technology can create personal area networks (PAN) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and can be called by various names.

[0357] Wireless devices (100a to 100f) can be connected to a network (300) via a base station (200). Artificial Intelligence (AI) technology can be applied to the wireless devices (100a to 100f), and the wireless devices (100a to 100f) can be connected to an AI server (400) via 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, etc. The wireless devices (100a to 100f) can communicate with each other via the base station (200) / network (300), but can 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). In addition, IoT devices (e.g., sensors) can communicate directly with other IoT devices (e.g., sensors) or other wireless devices (100a to 100f).

[0358] Wireless communication / connection (150a, 150b, 150c) can be established between wireless devices (100a~100f) / base stations (200), and base stations (200) / base stations (200). Here, wireless communication / connection can be achieved through various wireless access technologies (e.g., 5G NR) such as uplink / downlink communication (150a), sidelink communication (150b) (or, D2D communication), and communication between base stations (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 each other. For example, wireless communication / connection (150a, 150b, 150c) can transmit / receive signals through various physical channels. To this end, at least some of 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.), and resource allocation processes can be performed based on various proposals of the present disclosure.

[0359] FIG. 13 illustrates a wireless device according to an embodiment of the present disclosure. The embodiment of FIG. 13 may be combined with various embodiments of the present disclosure.

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

[0361] For example, the description of the first wireless device (or device) and the second wireless device (or device) below may be extended to the third wireless device (300) (or device) or a wireless device (or device) corresponding to a subsequent reference number. For example, the reference number of the processor of the third wireless device (300) may be 302, and the reference number of the transceiver may be 306.

[0362] A first wireless device (100) includes one or more processors (102) and one or more memories (104), and may further include one or more transceivers (106) and / or one or more antennas (108). The processor (102) controls the memories (104) and / or the transceivers (106), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document. For example, the processor (102) may process information in the memory (104) to generate first information / signal, and then transmit a wireless signal including the first information / signal via the transceiver (106). Furthermore, the processor (102) may receive a wireless signal including second information / signal via the transceiver (106), and then store information obtained from 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 perform some or all of the processes controlled by the processor (102), or may store software code including commands for performing the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. Here, the processor (102) and the memory (104) may be part of a communication modem / circuit / chip designed to implement a 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 via one or more antennas (108). The transceiver (106) may include a transmitter and / or a receiver. The transceiver (106) may be used interchangeably with an RF (Radio Frequency) unit. In the present disclosure, a wireless device may also mean a communication modem / circuit / chip.

[0363] A second wireless device (200) includes one or more processors (202), one or more memories (204), and may further include one or more transceivers (206) and / or one or more antennas (208). The processor (202) controls the memories (204) and / or the transceivers (206), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document. For example, the processor (202) may process information in the memory (204) to generate third information / signals, and then transmit a wireless signal including the third information / signals via the transceivers (206). In addition, the processor (202) may receive a wireless signal including fourth information / signals via the transceivers (206), and then store information obtained from signal processing of the fourth information / signals in the memory (204). The memory (204) may be connected to the processor (202) and may store various information related to the operation of the processor (202). For example, the memory (204) may perform some or all of the processes controlled by the processor (202), or may store software code including commands for performing the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. Here, the processor (202) and the memory (204) may be part of a communication modem / circuit / chip designed to implement wireless communication technology (e.g., LTE, NR). The transceiver (206) may be connected to the processor (202) and may transmit and / or receive wireless signals via one or more antennas (208). The transceiver (206) may include a transmitter and / or a receiver. The transceiver (206) may be used interchangeably with an RF unit. In the present disclosure, a wireless device may also mean a communication modem / circuit / chip.

[0364] Hereinafter, the 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 one or more Service Data Units (SDUs) according to the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts 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 operation flowcharts disclosed in this document. One or more processors (102, 202) can generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data or information according to the functions, procedures, proposals and / or methods disclosed herein, and provide the signals to one or more transceivers (106, 206). One or more processors (102, 202) can receive signals (e.g., baseband signals) from one or more transceivers (106, 206) and obtain PDUs, SDUs, messages, control information, data or information according to the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed herein.

[0365] One or more processors (102, 202) may be referred to as a controller, a microcontroller, a microprocessor, or a 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 operational 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. The descriptions, functions, procedures, suggestions, methods and / or operation flowcharts disclosed in this document may be implemented using firmware or software configured to perform one or more processors (102, 202) or stored in one or more memories (104, 204) and executed by one or more processors (102, 202). The descriptions, functions, procedures, suggestions, methods and / or operation flowcharts disclosed in this document may be implemented using firmware or software in the form of codes, instructions and / or sets of instructions.

[0366] One or more memories (104, 204) may be coupled to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, codes, instructions, and / or commands. The one or more memories (104, 204) may be configured as ROM, RAM, EPROM, flash memory, hard drives, registers, cache memory, computer-readable storage media, and / or combinations thereof. The one or more memories (104, 204) may be located internally and / or externally to the one or more processors (102, 202). Additionally, the one or more memories (104, 204) may be coupled to the one or more processors (102, 202) via various technologies, such as wired or wireless connections.

[0367] One or more transceivers (106, 206) can transmit user data, control information, wireless signals / channels, etc., as mentioned in the methods and / or flowcharts of this document, to one or more other devices. One or more transceivers (106, 206) can receive user data, control information, wireless signals / channels, etc., as mentioned in the descriptions, functions, procedures, proposals, methods and / or flowcharts of this document, from one or more other devices. For example, one or more transceivers (106, 206) can be connected to one or more processors (102, 202) and can transmit and receive wireless signals. For example, one or more processors (102, 202) can 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 coupled 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, or the like, as referred to in the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed herein, via 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 received user data, control information, wireless signals / channels, etc. from RF band signals to baseband signals in order to process the received user data, control information, wireless signals / channels, etc. using one or more processors (102, 202).One or more transceivers (106, 206) may convert user data, control information, wireless signals / channels, etc. processed by one or more processors (102, 202) from baseband signals to RF band signals. For this purpose, one or more transceivers (106, 206) may include an (analog) oscillator and / or filter.

[0368] FIG. 14 illustrates a signal processing circuit for a transmission signal according to an embodiment of the present disclosure. The embodiment of FIG. 14 may be combined with various embodiments of the present disclosure.

[0369] Referring to FIG. 14, 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 operations / functions of FIG. 14 may be performed in the processor (102, 202) and / or the transceiver (106, 206) of FIG. 13. The hardware elements of FIG. 14 may be implemented in the processor (102, 202) and / or the transceiver (106, 206) of FIG. 13. For example, blocks 1010 to 1060 may be implemented in the processor (102, 202) of FIG. 13. Additionally, blocks 1010 to 1050 may be implemented in the processor (102, 202) of FIG. 13, and block 1060 may be implemented in the transceiver (106, 206) of FIG. 13.

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

[0371] Specifically, the codeword can be converted into a bit sequence scrambled by a scrambler (1010). The scramble sequence used for scrambling is generated based on an initialization value, and the initialization value may include ID information of the 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 a precoding matrix W of N*M. 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 complex modulation symbols. In addition, the precoder (1040) can perform precoding without performing transform precoding.

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

[0373] The signal processing process for receiving signals in a wireless device can be configured in reverse order of the signal processing process (1010 to 1060) of FIG. 14. For example, a wireless device (e.g., 100, 200 of FIG. 13) can receive wireless signals from the outside through an antenna port / transceiver. The received wireless signals can be converted into baseband signals through a signal restorer. For this purpose, the signal restorer can include a frequency downlink converter, an analog-to-digital converter (ADC), a CP remover, and a fast Fourier transform (FFT) module. Thereafter, the baseband signal can be restored to a codeword through a resource demapper process, a postcoding process, a demodulation process, and a descrambling process. The codewords can be restored to the original information blocks 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.

[0374] Figure 15 illustrates a wireless device according to an embodiment of the present disclosure. The wireless device may be implemented in various forms depending on the use case / service (see Figure 12). The embodiment of Figure 15 may be combined with various embodiments of the present disclosure.

[0375] Referring to FIG. 15, the wireless device (100, 200) corresponds to the wireless device (100, 200) of FIG. 13 and may be composed of various elements, components, units, 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 an additional element (140). The communication unit may include a communication circuit (112) and a 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. 13. For example, the transceiver(s) (114) may include one or more transceivers (106, 206) and / or one or more antennas (108, 208) of FIG. 13. The control unit (120) is electrically connected to the communication unit (110), the memory unit (130), and the additional elements (140) and controls the overall operation of the wireless device. For example, the control unit (120) may control the electrical / mechanical operation of the wireless device based on the program / code / command / information stored in the memory unit (130). In addition, the control unit (120) may transmit information stored in the memory unit (130) to an external device (e.g., another communication device) via a wireless / wired interface through the communication unit (110), or store information received from an external device (e.g., another communication device) via a wireless / wired interface in the memory unit (130).

[0376] The additional element (140) may be configured in various ways depending on the type of the 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. 12, 100a), a vehicle (Fig. 12, 100b-1, 100b-2), an XR device (Fig. 12, 100c), a portable device (Fig. 12, 100d), a home appliance (Fig. 12, 100e), an IoT device (Fig. 12, 100f), a digital broadcasting terminal, a hologram device, a public safety device, an MTC device, a medical device, a fintech device (or a financial device), a security device, a climate / environmental device, an AI server / device (Fig. 12, 400), a base station (Fig. 12, 200), a network node, etc. Wireless devices may be mobile or stationary depending on the use / service.

[0377] In FIG. 15, 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 some may be wirelessly 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 wired, and the control unit (120) and the first unit (e.g., 130, 140) may be wirelessly connected via the communication unit (110). In addition, each element, component, unit / part, and / or module within the wireless device (100, 200) may further include one or more elements. For example, the control unit (120) may be composed of one or more processor sets. 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 a random access memory (RAM), a dynamic RAM (DRAM), a read only memory (ROM), a flash memory, a volatile memory, a non-volatile memory, and / or a combination thereof.

[0378] Below, the implementation example of Fig. 15 is described in more detail with reference to the drawings.

[0379] FIG. 16 illustrates a mobile device according to an embodiment of the present disclosure. The mobile device may include a smartphone, a smart pad, a wearable device (e.g., a smartwatch, smartglasses), or a portable computer (e.g., a laptop, etc.). The mobile 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. 16 may be combined with various embodiments of the present disclosure.

[0380] Referring to FIG. 16, 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 a part of the communication unit (110). Blocks 110 to 130 / 140a to 140c correspond to blocks 110 to 130 / 140 of FIG. 15, respectively.

[0381] 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 components of the mobile device (100) to perform various operations. The control unit (120) can include an AP (Application Processor). The memory unit (130) can store data / parameters / programs / codes / commands required for operating the mobile device (100). In addition, the memory unit (130) can store input / output data / information, etc. The power supply unit (140a) supplies power to the mobile device (100) and can include a wired / wireless charging circuit, a battery, etc. The interface unit (140b) can support connection between the mobile device (100) and other external devices. The interface unit (140b) can include various ports (e.g., audio input / output ports, video input / output ports) for connection with external devices. The input / output unit (140c) can input or output video information / signals, audio information / signals, data, and / or information input from 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.

[0382] For example, in the case of data communication, the input / output unit (140c) obtains information / signals (e.g., touch, text, voice, image, video) input by the user, and the obtained 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 other wireless devices or to a base station. In addition, the communication unit (110) can receive wireless signals from other wireless devices or base stations, and then restore the received wireless signals to the 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).

[0383] FIG. 17 illustrates a vehicle or autonomous vehicle according to one embodiment of the present disclosure. The vehicle or autonomous vehicle may be implemented as a mobile robot, a car, a train, a manned or unmanned aerial vehicle (AV), a ship, or the like. The embodiment of FIG. 17 may be combined with various embodiments of the present disclosure.

[0384] Referring to FIG. 17, a vehicle or autonomous vehicle (100) may include an antenna unit (108), a communication unit (110), a control unit (120), a driving unit (140a), a power supply unit (140b), a sensor unit (140c), and an autonomous driving unit (140d). The antenna unit (108) may be configured as a part of the communication unit (110). Blocks 110 / 130 / 140a to 140d correspond to blocks 110 / 130 / 140 of FIG. 15, respectively.

[0385] The communication unit (110) can transmit and receive signals (e.g., data, control signals, etc.) with external devices such as other vehicles, base stations (e.g., base stations, road side units, etc.), and servers. The control unit (120) can control elements of the vehicle or autonomous vehicle (100) to perform various operations. The control unit (120) can include an ECU (Electronic Control Unit). The drive unit (140a) can drive the vehicle or autonomous vehicle (100) on the ground. The drive unit (140a) can include an engine, a motor, a power train, wheels, brakes, a steering device, etc. The power supply unit (140b) supplies power to the vehicle or autonomous vehicle (100) and can include a wired / wireless charging circuit, a battery, etc. The sensor unit (140c) can obtain vehicle status, surrounding environment information, user information, etc. The sensor unit (140c) may include an IMU (inertial measurement unit) sensor, a collision sensor, a wheel sensor, a speed sensor, an incline sensor, a weight detection sensor, a heading sensor, a position module, a vehicle forward / backward sensor, a battery sensor, a fuel sensor, a tire sensor, a steering sensor, a temperature sensor, a humidity sensor, an ultrasonic sensor, an illuminance sensor, a pedal position sensor, etc. The autonomous driving unit (140d) may implement a technology for maintaining a driving lane, a technology for automatically controlling speed such as adaptive cruise control, a technology for automatically driving along a set path, a technology for automatically setting a path and driving when a destination is set, etc.

[0386] For example, the communication unit (110) can receive map data, traffic information data, etc. from an external server. The autonomous driving unit (140d) can generate an autonomous driving route and driving plan based on the acquired data. The control unit (120) can control the drive unit (140a) so that the vehicle or autonomous vehicle (100) moves along the autonomous driving route according to the driving plan (e.g., speed / direction control). During autonomous driving, the communication unit (110) can irregularly / periodically acquire the latest traffic information data from an external server and can acquire surrounding traffic information data from surrounding vehicles. In addition, during autonomous driving, the sensor unit (140c) can acquire vehicle status and surrounding environment information. The autonomous driving unit (140d) can update the autonomous driving route and driving plan based on newly acquired data / information. The communication unit (110) can transmit information regarding the vehicle location, autonomous driving route, driving plan, etc. to the external server. External servers can predict traffic information data in advance using AI technology or other technologies based on information collected from vehicles or autonomous vehicles, and provide the predicted traffic information data to the vehicles or autonomous vehicles.

[0387] The claims set forth in this disclosure may be combined in various ways. For example, the technical features of the method claims of this disclosure may be combined and implemented as a device, and the technical features of the device claims of this disclosure may be combined and implemented as a method. Furthermore, the technical features of the method claims of this disclosure and the technical features of the device claims of this disclosure may be combined and implemented as a device, and the technical features of the method claims of this disclosure and the technical features of the device claims of this disclosure may be combined and implemented as a method.

Claims

1. In terms of method, A step of obtaining information related to requirements related to synchronization offset; a step of performing a pre-compensation action; and A method comprising the step of performing multiple slot-based transmissions based on the synchronization error value and the requirements after performing the above pre-compensation operation.

2. In paragraph 1, The above multiple slot-based transmissions are terminal-to-base station transmissions transmitted to the base station, and A method wherein the terminal-to-base station transmissions include transmissions transmitted over terminal-to-base station physical shared channel repetitions.

3. In paragraph 2, The above base station is related to a non-terrestrial network, method.

4. In paragraph 2, A method in which an orthogonal cover code is applied between transmissions transmitted over the terminal-to-base station physical shared channel repetition.

5. In paragraph 4, The above requirements are different depending on the parameters associated with the orthogonal cover code.

6. In paragraph 4, Further comprising the step of transmitting information about the capabilities of the first device associated with the orthogonal cover code to the base station, A method wherein the capacity of the first device associated with the orthogonal cover code varies depending on the length of the orthogonal cover code.

7. In paragraph 4, Further comprising the step of transmitting information about the capabilities of the first device associated with the orthogonal cover code to the base station, A method wherein the capability of the first device associated with the orthogonal cover code comprises at least one of a capability associated with phase continuity and a capability associated with power consistency.

8. In paragraph 1, Further comprising the step of transmitting information about the capabilities related to the pre-compensation operation that can be supported by the first device to the base station, The above pre-compensation operation is related to timing offset or Doppler shift.

9. In paragraph 1, The above requirements vary depending on the type of transmission being performed, and A method wherein the type of said transmission comprises multiple slot-based transmission or single slot-based transmission.

10. In paragraph 1, The above synchronization error is the error compared to the synchronization standard of the base station, and The above requirement relates to a method in which a timing error between a second resource of a first device and the first resource after performing the pre-compensation operation corresponding to the first resource according to the synchronization criterion is related to the timing error.

11. In paragraph 1, A method in which the above synchronization error is a timing error or a frequency offset.

12. In paragraph 1, The above requirements relate to the rate of change in synchronization error between transmissions performed by the first device.

13. In paragraph 1, A method, wherein the above method is performed by a first device.

14. In the first device, At least one transceiver; at least one processor; and At least one memory coupled to said at least one processor and storing instructions, The above instructions, based on being executed by the at least one processor, cause the first device to: Obtain information related to requirements related to synchronization offset; to perform pre-compensation actions; and A first device, which performs multiple slot-based transmissions based on the synchronization error value and the above requirements after performing the above pre-compensation operation.

15. In a processing device set to control the first device, at least one processor; and At least one memory coupled to said at least one processor and storing instructions, The above instructions, based on being executed by the at least one processor, cause the first device to: Obtain information related to requirements related to synchronization offset; to perform pre-compensation actions; and A processing device that performs multiple slot-based transmissions based on the synchronization error value and the above requirements after performing the above pre-compensation operation.

16. A non-transitory computer-readable storage medium that records commands, The above commands, when executed, cause the first device to: Obtain information related to requirements related to synchronization offset; to perform pre-compensation actions; and A non-transitory computer-readable storage medium, which causes multiple slot-based transmissions to be performed based on the synchronization error value and the requirements after performing the above pre-compensation operation.

17. In the method, A step of transmitting information related to requirements related to synchronization offset to a first device; and A method comprising: receiving a plurality of slot-based transmissions from the first device; A method wherein the above multiple slot-based transmissions are performed based on a synchronization error value of the first device and the above requirements after a pre-compensation operation is performed.

18. In paragraph 17, A method wherein the above multiple slot-based transmissions are transmissions transmitted via terminal-to-base station physical shared channel repetition.

19. In the second device, At least one transceiver; at least one processor; and At least one memory coupled to said at least one processor and storing instructions, The above instructions, based on being executed by the at least one processor, cause the second device to: Transmitting information related to requirements relating to synchronization offset to the first device; and To receive multiple slot-based transmissions from the first device, A second device, wherein the above multiple slot-based transmissions are performed based on the synchronization error value of the first device and the above requirements after the pre-compensation operation is performed.

20. In paragraph 19, A second device wherein the above multiple slot-based transmissions are transmissions transmitted via terminal-to-base station physical shared channel repetitions.

Images