Orthogonal cover code-based transmission / reception method and device in non-terrestrial network

Abstract

Provided are a method by which a device performs wireless communication and a device for supporting same. The device may: acquire information related to a plurality of orthogonal cover code indices; determine an orthogonal cover code index among the plurality of orthogonal cover code indices; and perform transmission to a base station on the basis of an orthogonal cover code related to the orthogonal cover code index. For example, the orthogonal cover code index may be determined on the basis of whether the transmission is for initial access.

Description

Method and device for transmitting and receiving based on orthogonal cover code in 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 may be provided. For example, the method may include: obtaining information related to a plurality of orthogonal cover code indices; determining an orthogonal cover code index from among the plurality of orthogonal cover code indices; and performing a transmission to a base station based on an orthogonal cover code associated with the orthogonal cover code index. For example, the orthogonal cover code index may be determined based on whether the transmission is for initial access.

[0006] According to one embodiment of the present disclosure, a device may be provided. For example, the 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, when executed by the at least one processor, may cause the device to: obtain information related to a plurality of orthogonal cover code indices; determine an orthogonal cover code index from among the plurality of orthogonal cover code indices; and perform a transmission to a base station based on an orthogonal cover code associated with the orthogonal cover code index. For example, the orthogonal cover code index may be determined based on whether the transmission is a transmission for initial access.

[0007] According to one embodiment of the present disclosure, a processing device configured to control a 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, when executed by the at least one processor, may cause the device to: obtain information related to a plurality of orthogonal cover code indices; determine an orthogonal cover code index from among the plurality of orthogonal cover code indices; and perform a transmission to a base station based on an orthogonal cover code associated with the orthogonal cover code index. For example, the orthogonal cover code index may be determined based on whether the transmission is a transmission for initial access.

[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 device to: obtain information related to a plurality of orthogonal cover code indices; determine an orthogonal cover code index from among the plurality of orthogonal cover code indices; and perform a transmission to a base station based on an orthogonal cover code associated with the orthogonal cover code index. For example, the orthogonal cover code index may be determined based on whether the transmission is for an initial connection.

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

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

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

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

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

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

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

[0016] FIGS. 8A and 8B illustrate a non-terrestrial network scenario according to one embodiment of the present disclosure.

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

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

[0019] FIG. 11 illustrates a method by which a device performs wireless communication according to one embodiment of the present disclosure.

[0020] FIG. 12 illustrates a method for a base station to perform wireless communication according to one embodiment of the present disclosure.

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

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

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

[0024] FIG. 16 illustrates a wireless device according to one embodiment of the present disclosure.

[0025] FIG. 17 illustrates a mobile device according to one embodiment of the present disclosure.

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

[0027] 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."

[0028] 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."

[0029] 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.”

[0030] 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.”

[0031] 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 (i.e., PDCCH)", "PDCCH" may be proposed as an example of "control information."

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

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

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

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

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

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

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

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

[0040] 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).

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

[0042] 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).

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

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

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

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

[0047] 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 a 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.

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

[0049] 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).

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

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

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

[0053] 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).

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

[0055] 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).

[0056] 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).

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

[0058] 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

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

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

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

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

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

[0064] 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 the 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.

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

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

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

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

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

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

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

[0072] - Large-scale MIMO technology

[0073] - Hologram beamforming (HBF)

[0074] - Optical wireless technology

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

[0076] - Quantum communication

[0077] - Cell-free communication

[0078] - Integration of wireless information and power transmission

[0079] - Integration of wireless communication and sensing

[0080] - Integrated access and backhaul network

[0081] - Big data analysis

[0082] - Reconfigurable intelligent surface

[0083] - metaverse

[0084] - Blockchain

[0085] 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).

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

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

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

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

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

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

[0092] Figures 8a and 8b illustrate a non-terrestrial network scenario according to an embodiment of the present disclosure. The embodiments of Figures 8a and 8b may be combined with various embodiments of the present disclosure.

[0093] Figure 8a illustrates a non-terrestrial network scenario based on a transparent payload, and Figure 8b illustrates a non-terrestrial network scenario based on a regenerative payload. For example, a non-terrestrial network may typically include the following elements:

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

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

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

[0097] - A satellite (or UAS platform) capable of implementing transparent or regenerative (including onboard processing) payloads. For example, a satellite (or UAS platform) may generate multiple beams over a given service area, typically bounded by a field of view. For example, the beam footprint may be typically elliptical in shape. For example, the field of view of the satellite (or UAS platform) may vary depending on the onboard antenna diagram and minimum elevation angle. For example, for transparent payloads, radio frequency filtering, frequency conversion, and amplification may be performed. Therefore, the repetitive waveform signal in the payload may remain unchanged. For example, for regenerative payloads, radio frequency filtering, frequency conversion, and amplification, as well as demodulation / decoding, switching and / or routing, and coding / modulation may be performed. This may effectively be equivalent to onboarding all base station functions onto the satellite (or UAS platform).

[0098] - Optionally, inter-satellite link (ISL)

[0099] - User equipment can be serviced by satellites (or UAS platforms) within the target service area.

[0100] FIG. 9 illustrates a procedure for performing downlink transmission and reception according to an embodiment of the present disclosure. The embodiment of FIG. 9 may be combined with various embodiments of the present disclosure.

[0101] Referring to FIG. 9, in step S910, the base station may schedule downlink transmission, such as frequency / time resources, transmission layers, downlink precoder, modulation and coding scheme (MCS), etc. For example, the base station may determine a beam for PDSCH transmission to the terminal.

[0102] In step S920, the terminal can receive DCI for downlink scheduling (e.g., including scheduling information of PDSCH) from the base station on the PDCCH.

[0103] For example, DCI format 1_0 or 1_1 may be used for downlink scheduling. For example, DCI format 1_1 may include the following information: identifier for DCI formats, bandwidth part indicator, frequency domain resource assignment, time domain resource assignment, PRB bundling size indicator, rate matching indicator, zero power (ZP) CSI-RS trigger, antenna port(s), transmission configuration indication (TCI), sounding reference signal (SRS) request, demodulation reference signal (DMRS) sequence initialization.

[0104] For example, depending on each state indicated in the antenna port(s) field, a number of DMRS ports can be scheduled, and single-user (SU) / multi-user (MU) transmission scheduling can also be possible.

[0105] For example, the TCI field can consist of 3 bits, and quasi co-location (QCL) for DMRS can be dynamically indicated by indicating up to 8 TCI states depending on the TCI field value.

[0106] In step S930, the terminal can receive downlink data from the base station on the PDSCH.

[0107] For example, if a terminal detects a PDCCH including DCI format 1_0 or 1_1, the terminal can decode the PDSCH according to instructions by the corresponding DCI.

[0108] FIG. 10 illustrates a procedure for performing uplink transmission and reception according to an embodiment of the present disclosure. The embodiment of FIG. 10 may be combined with various embodiments of the present disclosure.

[0109] Referring to FIG. 10, in step S1010, the base station may schedule uplink transmission, such as frequency / time resources, transmission layers, uplink precoder, modulation and coding scheme (MCS), etc. For example, the base station may determine a beam for the terminal to transmit PUSCH.

[0110] In step S1020, the terminal can receive DCI for uplink scheduling (e.g., including scheduling information of PUSCH) from the base station on the PDCCH.

[0111] For example, DCI format 0_0 or 0_1 may be used for uplink scheduling. For example, DCI format 0_1 ​​may include the following information: identifier for DCI formats, supplementary uplink (UL / SUL) indicator, bandwidth part indicator, frequency domain resource assignment, time domain resource assignment, frequency hopping flag, modulation and coding scheme (MCS), SRS resource indicator (SRI), precoding information and number of layers, antenna port(s), SRS request, DMRS sequence initialization, and uplink shared channel (UL-SCH) indicator.

[0112] For example, the SRS resources configured within the SRS resource set associated with the upper layer parameter 'usage' can be indicated by the SRS resource indicator field. For example, 'spatialRelationInfo' can be configured for each SRS resource, and its value can be one of {CRI, SSB, SRI}.

[0113] In step S1030, the terminal can transmit uplink data to the base station on PUSCH.

[0114] For example, if a terminal detects a PDCCH including DCI format 0_0 or 0_1, the terminal can transmit the corresponding PUSCH according to the instructions of the corresponding DCI. For example, two transmission methods, codebook-based transmission and non-codebook-based transmission, can be supported for PUSCH transmission.

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

[0116] Recently, the telecommunications industry has been actively discussing the introduction of non-terrestrial networks (NTNs), which utilize satellites as network nodes. Satellites supporting NTNs can be categorized based on their flight orbits and characteristics, such as geostationary Earth orbit (GEO), medium Earth orbit (MEO), and low Earth orbit (LEO). These satellites typically operate at very high altitudes. Consequently, the satellites' service areas can have very wide coverage characteristics, and the number of target terminals within these service areas can be relatively large. Consequently, NTN services may require multiplexing support for multiple terminals. Since terrestrial terminals have transmission power constraints, coverage extension techniques can be applied to ensure that signals of sufficient size reach high-altitude NTNs during uplink transmission. For example, terminals can achieve coverage extension by repeating the physical uplink shared channel (PUSCH), an uplink data channel, on the time axis. Here, the terminal can transmit the PUSCH using the Discrete Fourier Transform Spread Orthogonal Frequency Division Multiplexing (DFT-s-OFDM) 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 OFDM modulation method. Meanwhile, the coverage expansion technology may have reduced resource utilization efficiency due to repeated transmission, and an uplink multiplexing method using an orthogonal cover code (OCC) may be effective.In the present disclosure, a method for setting and / or indicating an OCC when a terminal can apply the OCC to an uplink transmission signal and a device supporting the same are proposed.

[0117] In the following, the present disclosure mainly describes a method(s) for applying OCC to an uplink data channel, but the proposed method(s) of the present disclosure can also be extended to apply OCC to any uplink transmission signal.

[0118] [Proposal #01] When a terminal can apply OCC for a scheduled uplink data channel (and / or Msg3 PUSCH) (and / or its repeated transmission) based on a UL grant in a random access response (RAR), the terminal can report the support capability related to the application of the OCC by selecting and transmitting (pre-)configured and / or (pre-)defined (specific) initial access resources (e.g., RACH preamble, etc.) between the base station and the terminal. Here, for example, whether or not to apply the OCC can be configured / instructed by the base station. Here, for example, the OCC can be applied between repeated transmissions. Here, for example, the RAR (random access response) can mean a response signal of the base station to the initial access resources (e.g., RACH (random access channel) preamble, etc.) transmitted by the terminal. Here, for example, the RACH (random access channel) may mean a physical transmission channel / resource, etc. for supporting initial access and / or random access.

[0119] For example, in a next-generation mobile communication system based on a non-terrestrial network according to an embodiment of the present disclosure, assume that a terminal transmits an uplink data channel (e.g., PUSCH). For example, 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. Here, for example, the terminal may support transmission of an uplink data channel (e.g., PUSCH) to which OCC is applied for the purpose of increasing uplink capacity, etc.

[0120] Here, for example, in the case of an initial access process, the terminal can first transmit a RACH (random access channel) preamble as Msg1, the base station can transmit a RAR (random access response) as Msg2, and the terminal can again transmit an RRC connection request, etc. as Msg3. Here, for example, the Msg3 can be transmitted in the form of an uplink data channel (e.g., PUSCH), and repeated transmission for coverage improvement can be supported. Here, for example, when the Msg3 PUSCH is repeatedly transmitted, OCC application can be considered to increase uplink capacity. Here, for example, the terminal must be able to report (terminal) capability information that it can support OCC application when transmitting the Msg3 PUSCH. Here, for example, since the initial access process may be a previous step of the process of reporting the capabilities of the terminal, the support capability related to the OCC application for the Msg3 PUSCH may be reported by the terminal selecting and transmitting (pre-)configured and / or (pre-)defined (specific) initial access resources (e.g., RACH preamble, etc.) between the base station and the terminal. Here, for example, in general, the capability related to the OCC support may be reported by selecting and transmitting (pre-)configured and / or (pre-)defined (specific) initial access resources (e.g., RACH preamble, etc.) for the scheduled uplink data channel (and / or Msg3 PUSCH) (and / or its repeated transmissions) based on the UL grant in the RAR (random access response). According to the proposed method of the present disclosure, there is an advantage in that the OCC application can be supported even for the uplink data channel (e.g., PUSCH) (and / or its repeated transmissions) prior to the initial access process and / or the terminal capability reporting process.

[0121] The above [Proposal #01] can be applied in combination with other proposed methods(s) to the extent that the proposed actions do not conflict.

[0122] [Proposal #02] When a terminal can apply OCC to a scheduled uplink data channel (and / or Msg3 PUSCH) (and / or its repeated transmission) based on a UL grant in a random access response (RAR), the base station and / or the terminal can determine an OCC application (basic) unit and / or an OCC length in one or more of the following ways.

[0123] (1) The (basic) unit for applying OCC may be determined based on the repetitive transmission unit of the uplink data channel. For example, if PUSCH repetition type A is applied for repeated transmission when transmitting Msg3 PUSCH, the (basic) unit for applying OCC may be a slot.

[0124] (2) The OCC length may be determined based on the number of repeated transmissions of the uplink data channel. For example, if repeated transmission of PUSCH repetition type A is applied when transmitting Msg3 PUSCH, the OCC length may be the number of PUSCH repeated transmissions.

[0125] Here, for example, whether or not to apply the OCC can be set / instructed by the base station. Here, for example, the RAR (random access response) can mean a response signal of the base station to the initial access resource (e.g., a RACH (random access channel) preamble, etc.) transmitted by the terminal. Here, for example, the RACH (random access channel) can mean a physical transmission channel / resource, etc. for supporting initial access and / or random access.

[0126] For example, in a next-generation mobile communication system based on a non-terrestrial network according to an embodiment of the present disclosure, assume that a terminal transmits an uplink data channel (e.g., PUSCH). For example, 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. Here, for example, the terminal may support transmission of an uplink data channel (e.g., PUSCH) to which OCC is applied for the purpose of increasing uplink capacity, etc.

[0127] Here, for example, in the case of an initial access process, the terminal can first transmit a RACH (random access channel) preamble as Msg1, the base station can transmit a RAR (random access response) as Msg2, and the terminal can again transmit an RRC connection request, etc. as Msg3. Here, for example, the Msg3 can be transmitted in the form of an uplink data channel (e.g., PUSCH), and repeated transmission for coverage improvement can be supported. Here, for example, if the Msg3 PUSCH is repeatedly transmitted, application of OCC can be considered to increase uplink capacity. Here, for example, when applying OCC to an uplink data channel (and / or Msg3 PUSCH) (and / or its repeated transmission) scheduled based on an UL grant in the RAR (random access response), it may be desirable to implicitly set / indicate the OCC application (basic) unit and / or OCC length rather than explicitly set / indicate them, since it is difficult to convey terminal-specific / dedicated configuration information. Here, for example, the OCC application (basic) unit may be determined based on the repeated transmission unit of the uplink data channel. For example, when repeated transmission of PUSCH repetition type A is applied when transmitting Msg3 PUSCH, the OCC application (basic) unit may be a slot. Here, for example, the OCC length may be determined based on the number of repeated transmissions of the uplink data channel. For example, when repeated transmission of PUSCH repetition type A is applied when transmitting Msg3 PUSCH, the OCC length may be the number of PUSCH repeated transmissions. According to the proposed method of the present disclosure, there is an advantage in that OCC application can be supported (without additional signaling load) even for an uplink data channel (e.g., PUSCH) (and / or its repeated transmission) prior to the initial access process and / or terminal-specific / dedicated configuration.

[0128] The above [Proposal #02] can be applied in combination with other proposed methods(s) to the extent that the proposed actions do not conflict.

[0129] [Proposal #03] When a terminal can apply OCC for a scheduled uplink data channel (and / or Msg3 PUSCH) (and / or its repeated transmission) based on a UL grant in a random access response (RAR), the base station and / or the terminal can determine an OCC index based on one or more of the following items:

[0130] (1) RAPID (RACH preamble ID)

[0131] (2) PRACH OCC Index

[0132] (3) Location of UL grant (of the terminal) within RAR

[0133] Here, for example, whether or not to apply the OCC can be set / instructed by the base station. Here, for example, the OCC can be applied between repeated transmissions. Here, for example, the RAR (random access response) can mean a response signal of the base station to the initial access resource transmitted by the terminal (e.g., a RACH (random access channel) preamble, etc.). Here, for example, the RACH (random access channel) can mean a physical transmission channel / resource, etc. for supporting initial access and / or random access. Here, for example, the terminal can apply the OCC if there is another uplink data channel whose resource allocation (in the time axis and / or frequency axis) partially and / or fully overlaps with its own uplink data channel by referring to the UL grant(s) in the RAR, and if not, the OCC can not be applied.

[0134] For example, in a next-generation mobile communication system based on a non-terrestrial network according to an embodiment of the present disclosure, assume that a terminal transmits an uplink data channel (e.g., PUSCH). For example, 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. Here, for example, the terminal may support transmission of an uplink data channel (e.g., PUSCH) to which OCC is applied for the purpose of increasing uplink capacity, etc.

[0135] Here, for example, in the case of an initial access process, the terminal can first transmit a RACH (random access channel) preamble as Msg1, the base station can transmit a RAR (random access response) as Msg2, and the terminal can again transmit an RRC connection request, etc. as Msg3. Here, for example, the Msg3 can be transmitted in the form of an uplink data channel (e.g., PUSCH), and repeated transmission for coverage improvement can be supported. Here, for example, if the Msg3 PUSCH is repeatedly transmitted, application of OCC can be considered to increase uplink capacity. Here, for example, when applying OCC for an uplink data channel (and / or Msg3 PUSCH) (and / or repeated transmission thereof) scheduled based on an UL grant in the RAR (random access response), it may be preferable to implicitly set / indicate an OCC index rather than explicitly set / indicate it, since it is difficult to convey terminal-specific / dedicated configuration information. Therefore, in the present disclosure, when a terminal can apply OCC for an uplink data channel (and / or Msg3 PUSCH) (and / or repeated transmission thereof) scheduled based on an UL grant in the RAR (random access response), the base station and / or the terminal may determine an OCC index based on one or more of the following items.

[0136] (1) RAPID (RACH preamble ID)

[0137] (2) PRACH OCC Index

[0138] (3) Location of UL grant (of the terminal) within RAR

[0139] According to the proposed method of the present disclosure, there is an advantage in that OCC application can be supported (without additional signaling load) even for an uplink data channel (e.g., PUSCH) (and / or its repeated transmission) prior to the initial access process and / or terminal-specific / dedicated configuration.

[0140] The above [Proposal #03] can be applied in combination with other proposed methods(s) to the extent that the proposed actions do not conflict.

[0141] [Proposal #04] When a terminal can apply OCC to an uplink data channel (e.g., PUSCH) (and / or its repeated transmission), the terminal can determine that the OCC setting is invalid in one or more of the following cases.

[0142] (1) When the number of (configured / instructed) PUSCH repetition transmissions is small compared to the (configured / instructed) OCC length.

[0143] (2) When the (nominal) TDW (time domain window) is small compared to the (set / indicated) OCC length.

[0144] (3) When the (set / indicated) hopping interval is small compared to the (set / indicated) OCC length.

[0145] (4) When the resource group to which OCC is applied has a certain interval (on the time / frequency axis)

[0146] (5) When slot indexing is applied based on available slots.

[0147] (6) When PUSCH repetition type B is applied

[0148] Here, for example, whether or not to apply the OCC can be set / instructed by the base station. Here, for example, the OCC can be applied between repetitive transmissions. Here, for example, the OCC can be applied between repetitive transmissions (in the time domain and / or frequency domain) of an uplink data channel (e.g., PUSCH). Here, for example, the (nominal) TDW (time domain window) can mean a (nominal) time period during which the terminal is expected to maintain phase continuity and / or power consistency, and the base station can (pre-) set / define / instruct the terminal. Here, for example, the hopping interval can mean a (time / frequency) period during which a single hop is maintained when applying frequency hopping and / or OCC index hopping of an uplink data channel (e.g., PUSCH). Here, for example, the available slot can mean a slot during which the terminal can fully transmit the allocated PUSCH resource. For example, if some (OFDM) symbol(s) of the scheduled PUSCH resources within a slot are invalid symbol(s) (e.g., downlink transmission symbols and / or synchronization signal transmission symbols, etc.), the slot may not be an available slot. Here, for example, the PUSCH repetition type B may refer to a type for PUSCH repetitive transmission, and may refer to a type in which the terminal performs the next repetitive transmission immediately following the symbol at which the previous repetitive transmission ends. Here, for example, the (configured / defined / indicated) number of PUSCH repetitive transmissions may refer to the number of PUSCH repetitive transmissions within a (nominal) TDW and / or within a hop.

[0149] For example, in a next-generation mobile communication system based on a non-terrestrial network according to an embodiment of the present disclosure, assume that a terminal transmits an uplink data channel (e.g., PUSCH). For example, 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. Here, for example, the terminal may support transmission of an uplink data channel (e.g., PUSCH) to which OCC is applied for the purpose of increasing uplink capacity, etc.

[0150] Here, for example, if the base station configures / instructs the terminal to apply OCC for an uplink data channel (e.g., PUSCH) (and / or its repeated transmission), the terminal may go through a process of determining the validity of the OCC application configuration / instruction. Here, for example, if it is determined that the orthogonality of the OCC is not maintained or that it is difficult to guarantee the orthogonality of the OCC, the terminal may determine the corresponding OCC configuration to be invalid. For example, the terminal may determine the corresponding OCC configuration to be invalid in one or more of the following cases.

[0151] (1) When the number of (configured / instructed) PUSCH repetition transmissions is small compared to the (configured / instructed) OCC length.

[0152] (2) When the (set / indicated) (nominal) TDW is smaller than the (set / indicated) OCC length.

[0153] (3) When the (set / indicated) hopping interval is small compared to the (set / indicated) OCC length.

[0154] (4) When the resource group to which OCC is applied has a certain interval (on the time / frequency axis)

[0155] (5) When slot indexing is applied based on available slots.

[0156] (6) When PUSCH repetition type B is applied

[0157] According to the proposed method of the present disclosure, there is an advantage in that the implementation of the terminal can be facilitated and the operation between the base station and the terminal can be clarified by promising and / or defining that the terminal will determine the corresponding OCC application settings as invalid for a combination of settings in which OCC orthogonality and / or OCC validity is difficult to expect.

[0158] The above [Proposal #04] can be applied in combination with other proposed methods as long as the proposed actions do not conflict.

[0159] [Proposal #05] When a terminal can apply OCC to an uplink data channel (e.g., PUSCH) (and / or its repeated transmission), when the terminal can apply OCC between repeated transmissions of the uplink data channel (e.g., PUSCH), the application of OCC can be supported in one or more of the following ways within the repeated transmission period.

[0160] (1) OCC can be applied (repeatedly) from the start of repeated transmission.

[0161] (2) The base station may set and / or indicate section information (or start position and / or end position and / or length) related to OCC application (within a repetitive transmission section).

[0162] Here, for example, whether or not to apply the OCC can be set / indicated by the base station. Here, for example, the OCC can be applied between repetitive transmissions. Here, for example, the OCC can be applied between repetitive transmissions (in the time axis and / or frequency axis) of an uplink data channel (e.g., PUSCH). Here, for example, the (time / frequency axis) repetitive transmission interval for the uplink data channel can be set / indicated to be equal to or longer than the (time / frequency axis) OCC application interval (or OCC length).

[0163] For example, in a next-generation mobile communication system based on a non-terrestrial network according to an embodiment of the present disclosure, assume that a terminal transmits an uplink data channel (e.g., PUSCH). For example, 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. Here, for example, the terminal may support transmission of an uplink data channel (e.g., PUSCH) to which OCC is applied for the purpose of increasing uplink capacity, etc.

[0164] Here, for example, the terminal can apply OCC between repetitive transmissions of an uplink data channel (e.g., PUSCH). Here, for example, the OCC length (applied by the terminal) can be equal to or smaller than the repetitive transmission interval / number of times of the uplink data channel (e.g., PUSCH). Here, for example, if the OCC length is shorter than the repetitive transmission interval, an agreement between the base station and the terminal on the OCC application method may be required. For example, the base station and the terminal can (pre-) agree / define to (repeatedly) apply the OCC from the start time of the repetitive transmission. For example, if OCC = [+1 -1] and the number of repetitive transmissions is 4, the OCC can be applied from the transmission start point and [+1 -1] can be applied for the first two repetitive transmissions, or the OCC can be repeatedly applied from the transmission start point and [+1 -1 +1 -1] can be applied for the entire repetitive transmissions. Alternatively, for example, the base station may set and / or instruct the terminal regarding the interval information (or the start position and / or the end position and / or the length) related to the application of OCC (within the repetitive transmission interval). According to the proposed method of the present disclosure, when the terminal can apply OCC between repetitive transmissions of an uplink data channel (e.g., PUSCH), even if the OCC length (or the OCC application interval) and the number of repetitive transmissions (or the repetitive transmission interval) do not match, the base station and the terminal have the same understanding of the OCC application interval and can clearly operate.

[0165] The above [Proposal #05] can be applied in combination with other proposed methods as long as the proposed actions do not conflict.

[0166] [Proposal #06] When a terminal can apply OCC to an uplink data channel (e.g., PUSCH) (and / or its repeated transmission), the terminal can apply OCC according to one or more of the following slot indexing methods.

[0167] (1) In case of physical slot indexing, OCC can be applied to consecutive slot(s) based on the physical slot index.

[0168] (2) In case of available slot indexing, OCC can be applied to consecutive slot(s) based on the available slot index.

[0169] Here, for example, whether or not to apply the OCC can be set / instructed by the base station. Here, for example, the OCC can be applied between repeated transmissions. Here, for example, the OCC application period can be based on the OCC application unit and / or OCC length setting. Here, for example, the OCC can be applied in units of multiples of slots in the time axis. Here, for example, the physical slot can mean a physically defined (time axis) scheduling unit. Here, for example, the available slot can mean a slot in which the terminal can fully transmit the allocated PUSCH resource. For example, if some (OFDM) symbol(s) of the scheduled PUSCH resources within the slot are invalid symbol(s) (e.g., downlink transmission symbols and / or synchronization signal transmission symbols, etc.), the corresponding slot may not be an available slot. Here, for example, the slot indexing method to be referenced when applying the OCC may be information that is (pre-)defined and / or (pre-)set between the base station and the terminal.

[0170] For example, in a next-generation mobile communication system based on a non-terrestrial network according to an embodiment of the present disclosure, assume that a terminal transmits an uplink data channel (e.g., PUSCH). For example, 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. Here, for example, the terminal may support transmission of an uplink data channel (e.g., PUSCH) to which OCC is applied for the purpose of increasing uplink capacity, etc.

[0171] Here, for example, the OCC applied by the terminal to the uplink data channel (e.g., PUSCH) (and / or its repeated transmission) may be an OCC applied in the time axis. Here, for example, when applying the (time axis) OCC, the terminal may apply the OCC in units of multiples of slots in the time axis. Here, for example, the resource group to which the (time axis) OCC is applied may vary depending on the slot indexing method. For example, when based on physical slot indexing, a resource group to which the OCC is applied may be formed with consecutive slot(s) based on the physical slot index. For example, when based on available slot indexing, a resource group to which the OCC is applied may be formed with consecutive slot(s) based on the available slot index. Here, for example, the available slot may mean a slot in which the terminal can fully transmit the allocated PUSCH resource. For example, if some (OFDM) symbol(s) of the scheduled PUSCH resources within a slot are invalid symbol(s) (e.g., downlink transmission symbols and / or synchronization signal transmission symbols, etc.), the corresponding slot may not be an available slot. Here, for example, the slot indexing method to be referred to when applying OCC may be information that the base station sets to the terminal. According to the proposed method of the present disclosure, there is an advantage in that, corresponding to the fact that the uplink data channel (e.g., PUSCH) (and / or its repeated transmission) follows the physical slot indexing and / or the available slot indexing, the OCC application can also be applied according to the physical slot indexing and / or the available slot indexing.

[0172] The above [Proposal #06] can be applied in combination with other proposed methods(s) to the extent that the proposed actions do not conflict.

[0173] [Proposal #07] When a terminal can apply OCC to an uplink data channel (e.g., PUSCH) (and / or its repeated transmission), a base station can set / define / instruct multiple OCC lengths to the terminal with the OCC-related settings, and the terminal can select and apply one of the multiple OCC lengths according to a (time / frequency axis) transmission interval / length and / or the number of repeated transmissions and / or a channel environment of its uplink data channel. Here, for example, whether to apply the OCC can be set / instructed by the base station. Here, for example, the OCC application interval can be based on an OCC application unit and / or an OCC length setting.

[0174] For example, in a next-generation mobile communication system based on a non-terrestrial network according to an embodiment of the present disclosure, assume that a terminal transmits an uplink data channel (e.g., PUSCH). For example, 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. Here, for example, the terminal may support transmission of an uplink data channel (e.g., PUSCH) to which OCC is applied for the purpose of increasing uplink capacity, etc.

[0175] Here, for example, when the terminal attempts to apply OCC to an uplink data channel (e.g., PUSCH) (and / or its repeated transmissions), some transmissions of the uplink data channel (e.g., PUSCH) (and / or its repeated transmissions) may be omitted or canceled. Here, for example, when the terminal is configured with only a single OCC length, the OCC length may be in a form that is no longer suitable for the transmission interval of the reduced / changed uplink data channel (e.g., PUSCH) (and / or its repeated transmissions). Accordingly, in the present disclosure, when a terminal can apply OCC to an uplink data channel (e.g., PUSCH) (and / or its repeated transmission), a base station can set / define / instruct multiple OCC lengths to the terminal with the OCC-related settings, and the terminal can select and apply one of the multiple OCC lengths according to the (time / frequency axis) transmission interval / length and / or the number of repeated transmissions and / or the channel environment of its uplink data channel. According to the proposed method of the present disclosure, there is an advantage in that orthogonality can still be supported by allowing the terminal to apply another OCC length candidate when UL transmission is omitted and / or OCC application conditions are not met. For example, the terminal can select / apply OCC lengths by starting from applying a long OCC length, and then attempting to apply the next long OCC Length when UL transmission is omitted and / or OCC application conditions are not met.

[0176] The above [Proposal #07] can be applied in combination with other proposed methods(s) as long as the proposed actions do not conflict.

[0177] [Proposal #08] When a terminal can apply OCC to an uplink data channel (e.g., PUSCH) (and / or its repeated transmission), the base station and / or the terminal can (pre-)configure and / or (pre-)define OCC index hopping, and the hopping interval when applying the OCC index hopping can be (pre-)configured and / or (pre-)defined by one or more of the following methods.

[0178] (1) Set and / or define in units of symbols / slots (or their multiples);

[0179] (2) Set and / or define in units of OCC length (or its multiples);

[0180] (3) Set and / or define in units of (nominal) TDW (or its multiples);

[0181] Here, for example, whether or not to apply the OCC can be set / instructed by the base station. Here, for example, the OCC can be applied between repeated transmissions. Here, for example, the OCC application period can be based on the OCC application unit and / or the OCC length setting. Here, for example, the OCC can be applied in units of multiples of slots on the time axis. Here, for example, the (nominal) TDW (time domain window) can mean a (nominal) time period during which the terminal is expected to maintain phase continuity and / or power consistency, and the base station can (pre-) set / define / instruct the terminal. Here, for example, the hopping interval can mean a (time / frequency) period during which one hop is maintained when applying OCC index hopping. Here, for example, the hopping interval can be calculated based on physical slot indexing and / or available slot indexing. Here, for example, the base station can (pre-)configure and / or (pre-)define a slot indexing method to be referenced for the hopping interval. Here, for example, the physical slot can mean a physically defined (time axis) scheduling unit. Here, for example, the available slot can mean a slot in which the terminal can fully transmit the allocated PUSCH resource. For example, if some (OFDM) symbol(s) of the scheduled PUSCH resources within the slot are invalid symbol(s) (e.g., downlink transmission symbols and / or synchronization signal transmission symbols, etc.), the slot may not be an available slot. Here, for example, if the hopping interval is greater than the (nominal) TDW, the terminal can invalidate the application of the OCC index hopping and / or the application of the OCC. For example, the terminal can apply the OCC without OCC index hopping or can not apply the OCC.Here, for example, the base station can set and / or instruct the terminal to additionally apply an OCC index offset to the OCC index hopping.

[0182] For example, in a next-generation mobile communication system based on a non-terrestrial network according to an embodiment of the present disclosure, assume that a terminal transmits an uplink data channel (e.g., PUSCH). For example, 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. Here, for example, the terminal may support transmission of an uplink data channel (e.g., PUSCH) to which OCC is applied for the purpose of increasing uplink capacity, etc.

[0183] Here, for example, when the terminal applies OCC for an uplink data channel (e.g., PUSCH) (and / or its repeated transmission), the uplink data channel (e.g., PUSCH) (and / or its repeated transmission) may be an uplink data channel scheduled based on a TYPE1 CG (configured grant). Here, for example, when applying a fixed OCC index for the TYPE1 CG-based uplink data channel (e.g., PUSCH) (and / or its repeated transmission), it may continuously collide with a TYPE1 CG-based uplink data channel (e.g., PUSCH) (and / or its repeated transmission) scheduled for the same resource in an adjacent cell and / or an adjacent beam and / or an adjacent footprint. Here, for example, it may be considered that the terminal supports OCC index hopping for the OCC applied to the uplink data channel (e.g., PUSCH) (and / or its repeated transmission). Accordingly, in the present disclosure, when a terminal can apply OCC for an uplink data channel (e.g., PUSCH) (and / or its repeated transmission), the base station and / or the terminal can (pre-)configure and / or (pre-)define OCC index hopping, and the hopping interval when applying the OCC index hopping can be (pre-)configured and / or (pre-)defined in one or more of the following ways.

[0184] (1) Set and / or define in units of slots / symbols (or their multiples)

[0185] (2) Set and / or define in units of OCC length (or its multiples);

[0186] (3) Set and / or define in units of (nominal) TDW (or its multiples);

[0187] According to the proposed method of the present disclosure, when a terminal applies OCC to the uplink data channel (e.g., PUSCH) (and / or its repeated transmission), there is an advantage in that interference influences from adjacent cells and / or adjacent beams and / or adjacent footprints can be randomized and / or mitigated through OCC index hopping.

[0188] The above [Proposal #08] can be applied in combination with other proposed methods(s) to the extent that the proposed actions do not conflict.

[0189] [Proposal #09] When a terminal can apply OCC for an uplink data channel (e.g., PUSCH) (and / or its repeated transmission), the base station and / or the terminal can (pre-)configure and / or (pre-)define OCC index hopping, and the pattern of the OCC index hopping can be determined based on one or more of the following factors (or parameters).

[0190] (1) Scrambling ID (for PUSCH)

[0191] (2) PCDI (physical cell ID)

[0192] (3) SSB (synchronization signal block) index

[0193] (4) Beam reference signal index

[0194] Here, for example, whether or not the OCC is applied can be set / instructed by the base station. Here, for example, the OCC can be applied between repeated transmissions. Here, for example, the OCC application period can be determined by the OCC application unit and / or OCC length settings.

[0195] For example, in a next-generation mobile communication system based on a non-terrestrial network according to an embodiment of the present disclosure, assume that a terminal transmits an uplink data channel (e.g., PUSCH). For example, 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. Here, for example, the terminal may support transmission of an uplink data channel (e.g., PUSCH) to which OCC is applied for the purpose of increasing uplink capacity, etc.

[0196] Here, for example, when the terminal applies OCC for an uplink data channel (e.g., PUSCH) (and / or its repeated transmission), the uplink data channel (e.g., PUSCH) (and / or its repeated transmission) may be an uplink data channel scheduled based on a TYPE1 CG (configured grant). Here, for example, when applying a fixed OCC index for the TYPE1 CG-based uplink data channel (e.g., PUSCH) (and / or its repeated transmission), it may continuously collide with a TYPE1 CG-based uplink data channel (e.g., PUSCH) (and / or its repeated transmission) scheduled for the same resource in an adjacent cell and / or an adjacent beam and / or an adjacent footprint. Here, for example, it may be considered that the terminal supports OCC index hopping for the OCC applied to the uplink data channel (e.g., PUSCH) (and / or its repeated transmission). Accordingly, in the present disclosure, when a terminal can apply OCC for an uplink data channel (e.g., PUSCH) (and / or its repeated transmission), the base station and / or the terminal can (pre-)configure and / or (pre-)define OCC index hopping, and the pattern of the OCC index hopping can be determined based on one or more of the following factors (or parameters).

[0197] (1) Scrambling ID (for PUSCH)

[0198] (2) PCDI (physical cell ID)

[0199] (3) SSB (synchronization signal block) index

[0200] (4) Beam reference signal index

[0201] According to the proposed method of the present disclosure, when a terminal applies OCC to the uplink data channel (e.g., PUSCH) (and / or its repeated transmission), there is an advantage in that interference influences from adjacent cells and / or adjacent beams and / or adjacent footprints can be randomized and / or mitigated through OCC indexing hopping.

[0202] The above [Proposal #09] can be applied in combination with other proposed methods as long as the proposed actions do not conflict.

[0203] [Proposal #10] When a terminal can apply OCC to an uplink data channel (e.g., PUSCH) (and / or its repeated transmission), the terminal can determine the OCC length (according to an implicit rule) based on the transmission interval / length and / or the number of repeated transmissions of the uplink data channel (e.g., PUSCH). Here, for example, whether or not to apply the OCC can be set / instructed by the base station. Here, for example, the OCC can be applied between repeated transmissions. Here, for example, the OCC application interval can be based on the OCC application unit and / or OCC length setting. Here, for example, the implicit rule can be a (pre-)configured and / or (pre-)agreed rule between the base station and the terminal. Here, for example, the terminal can select a number that is appropriate for the transmission interval / length and / or the number of repeated transmissions of the uplink data channel (e.g., PUSCH) from among numbers that can be expressed as a power of 2 when determining the OCC length.

[0204] For example, in a next-generation mobile communication system based on a non-terrestrial network according to an embodiment of the present disclosure, assume that a terminal transmits an uplink data channel (e.g., PUSCH). For example, 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. Here, for example, the terminal may support transmission of an uplink data channel (e.g., PUSCH) to which OCC is applied for the purpose of increasing uplink capacity, etc.

[0205] Here, for example, the terminal can apply OCC between repeated transmissions of an uplink data channel (e.g., PUSCH). Here, for example, the OCC application unit can be defined as the repeated transmission unit (or a multiple thereof). Here, for example, the OCC length can be determined (according to an implicit rule) based on the transmission interval / length and / or the number of repeated transmissions of the uplink data channel (e.g., PUSCH) without a separate explicit setting / instruction. According to the proposed method of the present disclosure, there is an advantage in that the OCC length can be determined according to a method agreed upon between the base station and the terminal without causing a separate signaling load for indicating the OCC length.

[0206] The above [Proposal #10] can be applied in combination with other proposed methods as long as the proposed actions do not conflict.

[0207] [Proposal #11] When a terminal can apply OCC for an uplink data channel (e.g., PUSCH) (and / or its repeated transmissions), if the (actual) time domain window (TDW) is less than the (configured / instructed) OCC length, the terminal can perform one or more of the following actions:

[0208] (1) OCC not applied / (partially) applied

[0209] (2) Omit (all) PUSCH transmissions related to the resource group to which OCC applies.

[0210] Here, for example, whether or not to apply the OCC can be set / instructed by the base station. Here, for example, the OCC can be applied between repeated transmissions. Here, for example, the OCC application period can be based on the OCC application unit and / or OCC length setting. Here, for example, the (actual) TDW (time domain window) can mean an actual time period in which the terminal is expected to maintain phase continuity and / or power consistency, and can be a period occurring within the (nominal) TDW (pre-)configured / defined / instructed by the base station. For example, the (actual) TDW can be defined based on the time of event occurrence. Here, for example, the event can mean an event in which phase continuity and / or power consistency is not maintained, and can be divided into a dynamic event (e.g., an event triggered by DCI or MAC-CE) and a semi-static event (an event other than a dynamic event). Here, for example, the (nominal) TDW (time domain window) may mean a (nominal) time interval during which the terminal is expected to maintain phase continuity and / or power consistency, and may be (pre-)set / defined / instructed by the base station to the terminal.

[0211] For example, in a next-generation mobile communication system based on a non-terrestrial network according to an embodiment of the present disclosure, assume that a terminal transmits an uplink data channel (e.g., PUSCH). For example, 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. Here, for example, the terminal may support transmission of an uplink data channel (e.g., PUSCH) to which OCC is applied for the purpose of increasing uplink capacity, etc.

[0212] Here, for example, the terminal may not be able to guarantee to maintain phase continuity and / or power consistency for the transmission signal when a specific event occurs. Here, for example, the event may mean an event in which phase continuity and / or power consistency is not maintained, and may be divided into a dynamic event (e.g., an event triggered by DCI or MAC-CE) and a semi-static event (an event other than a dynamic event). Here, for example, an (actual) TDW may be determined based on the occurrence of the event. Here, for example, the (actual) TDW (time domain window) may mean an actual time period in which the terminal is expected to maintain phase continuity and / or power consistency, and may be a period occurring within a (nominal) TDW (pre-)configured / defined / instructed by the base station. For example, the (actual) TDW may be defined based on the time point of occurrence of the event. Here, for example, if the (actual) TDW is smaller than the OCC application period and / or OCC length to be applied by the terminal for an uplink data channel (e.g., PUSCH) (and / or its repeated transmission), orthogonality within the OCC application period and / or OCC length may not be guaranteed. Therefore, in the above case, the terminal may not apply the OCC or may omit (all) PUSCH transmissions related to the resource group to which the OCC is applied so as not to affect interference with other transmissions. According to the proposed method of the present disclosure, when orthogonality of the OCC within the OCC application period and / or OCC length for an uplink data channel (e.g., PUSCH) (and / or its repeated transmission) is not guaranteed, the terminal may not apply the OCC or may omit transmissions in the resource group to which the OCC is applied, thereby facilitating terminal operation or reducing interference effects.

[0213] The above [Proposal #11] can be applied in combination with other proposed methods as long as the proposed actions do not conflict.

[0214] [Proposal #12] When a terminal can apply OCC to an uplink data channel (e.g., PUSCH) (and / or its repeated transmission), the terminal may not apply a terminal action related to an event occurrence within the OCC application period and / or OCC length. For example, the terminal may not apply one or more of the following action(s) within the OCC application period and / or OCC length. For example, the terminal may apply the above action(s) at a time point after the OCC application period and / or OCC length.

[0215] (1) DL (downlink) reception and / or monitoring

[0216] (2) Other UL transmissions among the above PUSCH (and / or its repeated transmissions)

[0217] (3) UL transmission omission / cancellation

[0218] (4) Frequency hopping

[0219] (5) Application of UL TA (timing advance) (indicated by MAC CE)

[0220] (6) SRS resource set association

[0221] (7) Update of ephemeris (or orbital information of non-terrestrial base stations or satellites) information

[0222] (8) (Common) TA (timing advance) update

[0223] Here, for example, whether or not to apply the OCC can be set / instructed by the base station. Here, for example, the OCC can be applied between repeated transmissions. Here, for example, the OCC application period can be based on the OCC application unit and / or OCC length setting. Here, for example, the event can mean an incident in which phase continuity and / or power consistency is not maintained, and can be divided into a dynamic event (for example, an event triggered by DCI or MAC-CE) and a semi-static event (an event other than a dynamic event). Here, for example, the ephemeris information can mean information on the movement orbit of a non-terrestrial base station or satellite. Here, for example, the (common) TA (timing advanced) can mean a TA commonly applied to terminals in a non-terrestrial network, and can be a value applied by the terminal based on parameters set by the base station (or network) and a (pre-)defined / set formula.

[0224] For example, in a next-generation mobile communication system based on a non-terrestrial network according to an embodiment of the present disclosure, assume that a terminal transmits an uplink data channel (e.g., PUSCH). For example, 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. Here, for example, the terminal may support transmission of an uplink data channel (e.g., PUSCH) to which OCC is applied for the purpose of increasing uplink capacity, etc.

[0225] Here, for example, the terminal may not be able to guarantee to maintain phase continuity and / or power consistency for the transmission signal when a specific event occurs. Here, for example, the event may mean an event in which phase continuity and / or power consistency is not maintained, and may be divided into a dynamic event (e.g., an event triggered by DCI or MAC-CE) and a semi-static event (an event other than a dynamic event). Here, for example, if the event occurs within the OCC application period and / or OCC length to be applied by the terminal to an uplink data channel (e.g., PUSCH) (and / or its repeated transmission), orthogonality and / or validity may not be guaranteed. Therefore, in the present disclosure, when the terminal can apply the OCC to the uplink data channel (e.g., PUSCH) (and / or its repeated transmission), the terminal may not apply a terminal action related to the occurrence of an event within the OCC application period and / or OCC length. For example, the terminal may not apply one or more of the following operations within the OCC application period and / or OCC length.

[0226] (1) DL (downlink) reception and / or monitoring

[0227] (2) Other UL transmissions among the above PUSCH (and / or its repeated transmissions)

[0228] (3) UL transmission omission / cancellation

[0229] (4) Frequency hopping

[0230] (5) Application of UL TA (timing advance) (indicated by MAC CE)

[0231] (6) SRS resource set association

[0232] (7) Update of ephemeris (or orbital information of non-terrestrial base stations or satellites) information

[0233] (8) (Common) TA (timing advance) update

[0234] Here, for example, the terminal may apply the above operation(s) outside the OCC application period and / or OCC length. According to the proposed method of the present disclosure, there is an advantage in that the utilization of the OCC can be increased by ensuring that the terminal guarantees the orthogonality and / or validity of the OCC when applying the OCC to an uplink data channel (e.g., PUSCH) (and / or its repeated transmission).

[0235] The above [Proposal #12] can be applied in combination with other proposed methods as long as the proposed actions do not conflict.

[0236] [Proposal #13] When a terminal can apply OCC to a transmission resource (or its repeated transmission) of an uplink data channel (e.g., PUSCH), and when there exists a bit field (hereinafter, a first bit field) indicating an OCC parameter in a dynamic control channel (e.g., DCI) and a bit field (hereinafter, a second bit field) indicating a transmission parameter other than an OCC parameter, if a specific state of the first bit field (hereinafter, a first state) and / or a specific state of the second bit field (hereinafter, a second state) is indicated, the terminal can determine that the operation is not OCC-applied. Here, for example, the first bit field may be a bit field indicating an OCC index and / or an OCC length and / or an OCC type. Here, for example, the first bit field may be the same bit field as a bit field indicating an antenna port of a DM-RS or a bit field linked to a bit field. Here, for example, the second bit field may be a bit field indicating a redundancy version (RV) for a transport block (TB) and / or a bit field indicating frequency hopping. Here, for example, the interpretation of the second bit field may vary depending on the presence or absence of the first bit field. For example, when the first bit field exists, prior information and / or upper layer configuration information for interpreting the second bit field may be separately provided to the terminal. Here, for example, the first state may be a state indicating a state in which all OCC sequences have a value of '1' (for example,

[0011] when the OCC length is 2, [1 1 1 1] when the OCC length is 4, etc.). Here, for example, the second state may be a state corresponding to 'RV ID = 1' and / or a specific RV cycling pattern (for example, [1 0 2 3]).

[0237] For example, in a next-generation mobile communication system based on a non-terrestrial network according to an embodiment of the present disclosure, assume that a terminal transmits an uplink data channel (e.g., PUSCH). For example, 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. Here, for example, the terminal may support transmission of an uplink data channel (e.g., PUSCH) to which OCC is applied for the purpose of increasing uplink capacity, etc.

[0238] Here, for example, the base station (or network) may support transmitting OCC parameters to the UE via a dynamic control channel (e.g., DCI) for transmission of an uplink data channel (e.g., PUSCH) to which the OCC is applied. Here, for example, when there is no other UE that is multiplexed together during the PUSCH transmission, it may be desirable to disable the application of OCC. For example, when OCC is applied to repeated PUSCH transmission, when UCI is included in the PUSCH (e.g., UCI piggyback), since repeated UCI transmission must be guaranteed within the resource group to which OCC is applied in order to maintain OCC orthogonality, the signal load for UCI transmission may be large. On the other hand, for example, when OCC is not applied to repeated PUSCH transmission, since UCI can be transmitted only within PUSCH resources that overlap in the time axis, the signal load for UCI transmission may be small. Therefore, if the terminal is not multiplexed with other terminals, it may be desirable for the base station (or network node) to instruct the terminal to disable OCC. For example, the disablement of OCC may be indicated by a dedicated bit field within the dynamic control channel (hereinafter referred to as DCI (dynamic control information)), but the DCI size may change depending on the addition of a new bit field. This may result in the terminal having to support a highly complex reception operation that performs blind detection for multiple DCI formats / sizes.Accordingly, in the present disclosure, when a terminal can apply OCC to a transmission resource (or its repeated transmission) of an uplink data channel (e.g., PUSCH), when there exists a bit field (hereinafter, a first bit field) indicating an OCC parameter in a dynamic control channel (e.g., DCI) and a bit field (hereinafter, a second bit field) indicating a transmission parameter other than an OCC parameter, if a specific state of the first bit field (hereinafter, a first state) and / or a specific state of the second bit field (hereinafter, a second state) is indicated, the terminal can determine that the OCC is not applied. For example, the first bit field may be a bit field indicating an OCC index. For example, the second bit field may be a bit field indicating a redundancy version (RV) for a transport block (TB). For example, the first state may be a state in which all OCC sequences have the value '1' (e.g.,

[0011] when the OCC length is 2, [1 1 1 1] when the OCC length is 4, etc.). For example, the second state may be a state corresponding to 'RV ID = 1' and / or a specific RV cycling pattern (e.g., [1 0 2 3]).

[0239] According to the proposed method of the present disclosure, there is an advantage in that an OCC application / de-application operation for an uplink data channel (e.g., PUSCH) (and / or its repeated transmission) can be dynamically indicated without a separate dedicated bit field or increased control signal transmission load.

[0240] The above [Proposal #13] can be applied in combination with other proposed methods as long as the proposed actions do not conflict.

[0241] [Proposal #14] When a terminal can apply OCC to a transmission resource (or its repeated transmission) of an uplink data channel (e.g., PUSCH), and when the terminal can apply OCC between repeated transmissions of the uplink data channel (e.g., PUSCH), a base station (or a network node) can configure / instruct the terminal to omit PUSCH transmission in units of OCC groups within the repeated transmission interval. Here, for example, whether or not to apply the OCC can be configured / instructed by the base station. Here, for example, the OCC can be applied between repeated transmissions. Here, for example, the OCC group can mean a resource group to which the same OCC sequence is applied. Here, for example, the OCC can be applied between repeated transmissions (in time axis and / or frequency axis) of an uplink data channel (e.g., PUSCH). Here, for example, the (time / frequency axis) repetitive transmission interval for the above uplink data channel can be set / indicated to be equal to or longer than the (time / frequency axis) OCC application interval (or OCC length).

[0242] For example, in a next-generation mobile communication system based on a non-terrestrial network according to an embodiment of the present disclosure, assume that a terminal transmits an uplink data channel (e.g., PUSCH). For example, 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. Here, for example, the terminal may support transmission of an uplink data channel (e.g., PUSCH) to which OCC is applied for the purpose of increasing uplink capacity, etc.

[0243] Here, for example, the PUSCH (repetitive) transmission (hereinafter referred to as the first transmission) to which the OCC is applied may collide with another PUSCH transmission (e.g., a PUSCH transmission for a legacy UE) (hereinafter referred to as the second transmission) that does not support OCC on the same resource. Here, for example, transmission omission may be performed for resources that collide with the second transmission during the first transmission to reduce interference impact on the second transmission. Here, for example, the resources omitted in the first transmission may be resources in units of OCC groups. Here, for example, the OCC group may mean a group of resources to which the same OCC sequence is applied. For example, when the first transmission is divided into multiple OCC groups, the base station (or network node) may configure / instruct to omit transmission for OCC group(s) that include at least one resource that collides with the second transmission among the OCC group(s).

[0244] According to the proposed method of the present disclosure, when applying OCC to an uplink data channel (e.g., PUSCH) (and / or its repeated transmission), by instructing and / or setting the omission of OCC group unit transmission to which OCC is applied, an effect of blocking and / or preventing interference effects on channels that cannot be multiplexed with the PUSCH to which OCC is applied can be obtained.

[0245] The above [Proposal #14] can be applied in combination with other proposed methods as long as the proposed actions do not conflict.

[0246] [Proposal #15] When the terminal can apply OCC to the transmission resource (or its repeated transmission) of the uplink data channel (e.g., PUSCH) for Msg3, the terminal can apply the (RA-) RNTI ((random access) radio network temporary identifier) ​​for the Msg3 in one or more of the following ways.

[0247] (1) The terminal can select and apply a fixed (RA-) RNTI.

[0248] (2) The terminal can select and apply a (pre-)configured (RA-) RNTI.

[0249] (3) The terminal can (arbitrarily) select and apply (RA-) RNTI.

[0250] (4) The terminal can (randomly) select a (virtual) RACH resource, and the terminal can apply an (RA-) RNTI determined based on the RACH resource.

[0251] (5) The terminal can select and apply (RA-) RNTI based on the time resource / frequency resource / OCC resource of Msg3.

[0252] (6) The terminal may select and apply (RA-) RNTI based on terminal identification information and / or contention resolution ID.

[0253] Here, for example, the Msg3 may be a CB (contention based) Msg3 EDT (early data transmission). For example, the CB (contention based) Msg3 EDT (early data transmission) may mean Msg3 transmitted by the terminal while omitting transmission of Msg1 (RACH preamble) and Msg2 (random access response). Here, for example, the RACH resource may mean an NPRACH (NB-IoT PRACH) resource. Here, for example, the time resource of the Msg3 may be a resource at a start time and / or a resource at an end time and / or a number of repetitions and / or a number of slots in which one TB (transport block) is transmitted and / or a resource unit (e.g., N RU) may include a number of RNTIs. Here, for example, the (RA-) RNTI may be an RNTI utilized for determining a data scrambling sequence and / or a DM-RS sequence and / or a CRC mask sequence when transmitting Msg3.

[0254] For example, in a next-generation mobile communication system based on a non-terrestrial network according to an embodiment of the present disclosure, assume that a terminal transmits an uplink data channel (e.g., PUSCH). For example, 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. Here, for example, the terminal may support transmission of an uplink data channel (e.g., PUSCH) to which OCC is applied for the purpose of increasing uplink capacity, etc.

[0255] Here, for example, the OCC application for the PUSCH may also be applied to Msg3 during the initial access process. For example, the Msg3 may be repeatedly transmitted over multiple slots, and the OCC may be applied between the repeated transmissions. Here, the RA-RNTI determination method applied to the Msg3 needs to be defined. For example, if the Msg3 is a CB Msg3 EDT transmitted by omitting the transmission of Msg1 and / or Msg2, since there is no information of Msg1 and / or Msg2 that can be referenced, the RA-RNTI determination and / or application method for the CB Msg3 EDT may need to be newly defined.

[0256] Accordingly, in the present disclosure, when the terminal can apply OCC to transmission resources (or repetitive transmissions thereof) of an uplink data channel (e.g., PUSCH) for Msg3, the terminal can apply a random access radio network temporary identifier (RA-RNTI) for the Msg3 in one or more of the following ways.

[0257] (1) The terminal can select and apply a fixed (RA-) RNTI.

[0258] (2) The terminal can select and apply a (pre-)configured (RA-) RNTI.

[0259] (3) The terminal can (arbitrarily) select and apply (RA-) RNTI.

[0260] (4) The terminal can (randomly) select a (virtual) RACH resource, and the terminal can apply an (RA-) RNTI determined based on the RACH resource.

[0261] (5) The terminal can select and apply (RA-) RNTI based on the time resource / frequency resource / OCC resource of Msg3.

[0262] (6) The terminal may select and apply (RA-) RNTI based on terminal identification information and / or contention resolution ID.

[0263] According to the proposed method of the present disclosure, there is an advantage in that the terminal can clearly determine the RA-RNTI for the CB Msg3 EDT transmitted by omitting transmission of Msg1 and / or Msg2.

[0264] The above [Proposal #15] can be applied in combination with other proposed methods as long as the proposed actions do not conflict.

[0265] For example, the scrambling sequence generator can be initialized based on Equation 1.

[0266]

[0267] For example, n s may be the first slot of codeword transmission. For example, in case of NPUSCH repetition, every M NPUSCH identical After transmitting the codeword of the number n, the scrambling sequence can be reinitialized according to the above mathematical expression 1, at which time n s Wow n f can be set to the first slot and frame used for each repeated transmission. For example, M NPUSCH identical can be set for terminals and / or base stations.

[0268] For example, resource allocation information set by a higher layer for NPUSCH transmission using preset uplink resources or in uplink DCI format N0 for NPUSCH transmission may instruct the scheduled UE to:

[0269] - A set of consecutively allocated subcarriers of a resource unit (n) determined by the upper layer parameter npusch-SubCarrierSetIndex of PUR-Config-NB or by the subcarrier indication field. sc )

[0270] - The number of resource units (N) determined by the upper layer parameter npusch-NumRUsIndex of PUR-Config-NB or by the resource allocation fields according to Table 4 RU )

[0271] - The number of repetitions (N) determined by the repetition number field according to Table 5 Rep ), and for NPUSCH transmission using preset uplink resources, the UE shall use N Rep=1, except for NPUSCH using 16QAM, the repetition count set by the upper layer can be used.

[0272] For example, the subcarrier spacing △f of NPUSCH transmission can be determined by:

[0273] - For NPUSCH transmissions using preset uplink resources and subsequent NPUSCH transmissions until a narrowband random access response grant is received, the upper layer parameter npusch-SubCarrierSetIndex,

[0274] - Otherwise, the uplink subcarrier spacing field in the narrowband random access response grant.

[0275] For example, for NPUSCH transmission with subcarrier spacing △f=3.75kHz, n sc = I sc It can be. Here, for example, I sc may be a subcarrier indication field, and I sc = 48, 49, ..., 63 can be reserved, or n sc can be configured by the upper layer parameter npusch-SubCarrierSetIndex in PUR-Config-NB for NPUSCH transmission using preset uplink resources.

[0276] For example, for NPUSCH transmission with subcarrier spacing △f=15kHz, the subcarrier indication field (I) in the DCI or npusch-SubCarrierSetIndex in the PUR-Config-NB for NPUSCH transmission using preset uplink resources is sc ) is a set of subcarriers (n) that are consecutively allocated according to Table 3. sc ) can be determined.

[0277] Table 3 shows an example of allocated subcarriers for NPUSCH with △f=15kHz.

[0278] Subcarrier Indication Field (I sc ) set of assigned subcarriers (n sc )0-11I sc 12-153(I sc -12)+{0,1,2}16-176(I sc -16)+{0,1,2,3,4,5}18{0,1,2,3,4,5,6,7,8,9,10,11}19-63Reserved

[0279] Table 4 shows the number of resource units (N) for NPUSCH. RU ) is an example.

[0280] I RU N RU 01122334455668710

[0281] Table 5 shows the number of iterations (N) for NPUSCH Rep ) is an example of

[0282] I Rep N Rep 011224384165326647128

[0283] [Proposal #16] When a terminal can apply OCC to transmission resources (or its repeated transmissions) of an uplink data channel (e.g., PUSCH) for Msg3, the terminal can apply the OCC parameters for Msg3 in one or more of the following ways.

[0284] (1) The terminal can select and apply (pre-)set OCC parameters.

[0285] (2) The terminal can (arbitrarily) select and apply OCC parameters.

[0286] (3) The terminal can (randomly) select a (virtual) RACH resource, and the terminal can (randomly) select and apply an OCC parameter determined based on the RACH resource.

[0287] (4) The terminal can select and apply OCC parameters based on the time resources / frequency resources / OCC resources of Msg3.

[0288] (5) The terminal may select and apply OCC parameters based on terminal identification information and / or contention resolution ID.

[0289] Here, for example, the Msg3 may be a CB (contention based) Msg3 EDT (early data transmission). For example, the CB (contention based) Msg3 EDT (early data transmission) may mean Msg3 transmitted by the terminal while omitting transmission of Msg1 (RACH preamble) and Msg2 (random access response). Here, for example, the OCC parameter may include at least one of OCC enable / disable and / or OCC index and / or OCC type and / or OCC codeword and / or OCC length.

[0290] For example, in a next-generation mobile communication system based on a non-terrestrial network according to an embodiment of the present disclosure, assume that a terminal transmits an uplink data channel (e.g., PUSCH). For example, 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. Here, for example, the terminal may support transmission of an uplink data channel (e.g., PUSCH) to which OCC is applied for the purpose of increasing uplink capacity, etc.

[0291] Here, for example, the OCC application for the PUSCH may also be applied to Msg3 during the initial access process. For example, the Msg3 may be repeatedly transmitted across multiple slots, and the OCC may be applied between the repeated transmissions. Here, a method for determining the OCC parameters applied to the Msg3 needs to be defined. Therefore, in the present disclosure, when the terminal can apply the OCC to the transmission resources (or its repeated transmissions) of the uplink data channel (e.g., the PUSCH) for the Msg3, the terminal may apply the OCC parameters for the Msg3 in one or more of the following ways.

[0292] (1) The terminal can select and apply (pre-)set OCC parameters.

[0293] (2) The terminal can (arbitrarily) select and apply OCC parameters.

[0294] (3) The terminal can (randomly) select a (virtual) RACH resource, and the terminal can (randomly) select and apply an OCC parameter determined based on the RACH resource.

[0295] (4) The terminal can select and apply OCC parameters based on the time resources / frequency resources / OCC resources of Msg3.

[0296] (5) The terminal may select and apply OCC parameters based on terminal identification information and / or contention resolution ID.

[0297] According to the proposed method of the present disclosure, there is an advantage in that the terminal can clearly determine the OCC parameters for Msg3 to which OCC is applied.

[0298] The above [Proposal #16] can be applied in combination with other proposed methods as long as the proposed actions do not conflict.

[0299] [Proposal #17] When a terminal can apply OCC to transmission resources (or its repeated transmission) of an uplink data channel (e.g., PUSCH) for Msg3, the transmission start time of Msg3 to which the OCC is applied can be restricted. Here, for example, the Msg3 can be CB (contention based) Msg3 EDT (early data transmission). For example, the CB (contention based) Msg3 EDT (early data transmission) can mean Msg3 transmitted by the terminal omitting transmission of Msg1 (RACH preamble) and Msg2 (random access response). Here, for example, the transmission start time of the Msg3 can be given in the form of a resource grid determined in units of OCC length (or its multiple). For example, when slot-to-slot OCC is applied and the OCC length is 2, the terminal can determine the transmission start time in units of 2 slots. Here, for example, the transmission start time of the above Msg3 can be limited to units of OCC length (or its multiple).

[0300] For example, in a next-generation mobile communication system based on a non-terrestrial network according to an embodiment of the present disclosure, assume that a terminal transmits an uplink data channel (e.g., PUSCH). For example, 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. Here, for example, the terminal may support transmission of an uplink data channel (e.g., PUSCH) to which OCC is applied for the purpose of increasing uplink capacity, etc.

[0301] Here, for example, the application of OCC to the PUSCH may also be applied to Msg3 during the initial access process. For example, Msg3 may be repeatedly transmitted across multiple slots, and OCC may be applied between the repeated transmissions. Here, for example, when OCC is applied to Msg3, the transmission start positions of Msg3 transmitted between different terminals may need to be aligned. For example, the transmission timing for Msg3 may be restricted in the form of a resource grid with the OCC length as the basic unit. According to the proposed method of the present disclosure, there is an advantage in that the usability of OCC is guaranteed by aligning the transmission start positions between terminals for Msg3 to which OCC is applied.

[0302] The above [Proposal #17] can be applied in combination with other proposed methods as long as the proposed actions do not conflict.

[0303] FIG. 11 illustrates a method for a device to perform wireless communication according to an embodiment of the present disclosure. The embodiment of FIG. 11 may be combined with various embodiments of the present disclosure.

[0304] Referring to FIG. 11, in step S1110, the device may obtain information related to a plurality of orthogonal cover code indices. In step S1120, the device may determine an orthogonal cover code index from among the plurality of orthogonal cover code indices. In step S1130, the device may perform transmission to the base station based on the orthogonal cover code associated with the orthogonal cover code index. For example, the orthogonal cover code index may be determined based on whether the transmission is for initial access.

[0305] For example, based on the above transmission being a transmission for the initial access, the orthogonal cover code index may be determined based on at least one of a random access preamble identifier, an orthogonal cover code index associated with a random access channel, or a position of a grant within a random access response.

[0306] For example, based on the fact that the transmission is a transmission after the initial connection, the hopping of the orthogonal cover code index may be performed based on at least one of a scrambling ID, a physical cell ID, a synchronization signal block index, or a beam reference signal index. For example, the transmission may be performed based on a configured grant from a base station.

[0307] For example, the transmission may include uplink data channel repetition, and the orthogonal cover code may be applied to the uplink data channel repetition.

[0308] Additionally, for example, the device may report to the base station its capabilities related to applying the orthogonal cover code to the transmission based on the initial access resource. For example, a random access preamble transmitted on the initial access resource established between the base station and the device may indicate that the device has the capability to apply the orthogonal cover code to the transmission.

[0309] For example, the unit of application of the orthogonal cover code may be determined based on the unit of repetition of the transmission, and the length of the orthogonal cover code may be determined based on the number of repetitions of the transmission.

[0310] For example, in the procedure for the initial access, the orthogonal cover code index determined based on at least one of the random access preamble ID, the orthogonal cover code index associated with the random access channel, or the position of the grant in the random access response may be hopped based on at least one of the scrambling ID, the physical cell ID, the synchronization signal block index, or the beam reference signal index.

[0311] Additionally, for example, the device may receive information related to a section to which the orthogonal cover code is applied from the base station. For example, the information related to a section to which the orthogonal cover code is applied may include at least one of information related to a start position to which the orthogonal cover code is applied, information related to an end position to which the orthogonal cover code is applied, or information related to a length of a section to which the orthogonal cover code is applied.

[0312] For example, based on the fact that the transmission is an uplink data channel transmission without a random access preamble and a random access response for the initial connection, a radio network temporary identifier (RNTI) may be selected based on at least one of a time resource, a frequency resource, an orthogonal cover code resource, identification information of the device, or a contention resolution ID associated with the transmission.

[0313] For example, based on the above transmission being an uplink data channel transmission without a random access preamble and a random access response for the initial access, the orthogonal cover code index may be determined based on at least one of a time resource, a frequency resource, an orthogonal cover code resource, identification information of a device, or a contention resolution ID associated with the transmission.

[0314] For example, the transmission may be omitted based on whether at least one of phase continuity or power consistency is not maintained within the interval to which the orthogonal cover code is applied.

[0315] The proposed method can be applied to devices according to various embodiments of the present disclosure. First, the processor (102) of the device (100) can obtain information related to a plurality of orthogonal cover code indices. Then, the processor (102) of the device (100) can determine an orthogonal cover code index from among the plurality of orthogonal cover code indices. Then, the processor (102) of the device (100) can control the transceiver (106) to perform transmission to a base station based on the orthogonal cover code related to the orthogonal cover code index. For example, the orthogonal cover code index can be determined based on whether the transmission is for initial access.

[0316] According to one embodiment of the present disclosure, a device may be provided. For example, the 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, when executed by the at least one processor, may cause the device to: obtain information related to a plurality of orthogonal cover code indices; determine an orthogonal cover code index from among the plurality of orthogonal cover code indices; and perform a transmission to a base station based on an orthogonal cover code associated with the orthogonal cover code index. For example, the orthogonal cover code index may be determined based on whether the transmission is a transmission for initial access.

[0317] According to one embodiment of the present disclosure, a processing device configured to control a 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, when executed by the at least one processor, may cause the device to: obtain information related to a plurality of orthogonal cover code indices; determine an orthogonal cover code index from among the plurality of orthogonal cover code indices; and perform a transmission to a base station based on an orthogonal cover code associated with the orthogonal cover code index. For example, the orthogonal cover code index may be determined based on whether the transmission is a transmission for initial access.

[0318] 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 device to: obtain information related to a plurality of orthogonal cover code indices; determine an orthogonal cover code index from among the plurality of orthogonal cover code indices; and perform a transmission to a base station based on an orthogonal cover code associated with the orthogonal cover code index. For example, the orthogonal cover code index may be determined based on whether the transmission is for an initial connection.

[0319] FIG. 12 illustrates a method for a base station to perform wireless communication according to an embodiment of the present disclosure. The embodiment of FIG. 12 may be combined with various embodiments of the present disclosure.

[0320] Referring to FIG. 12, in step S1210, the base station may obtain information related to a plurality of orthogonal cover code indices. In step S1220, the base station may determine an orthogonal cover code index from among the plurality of orthogonal cover code indices. In step S1230, the base station may receive a transmission from a device based on an orthogonal cover code associated with the orthogonal cover code index. For example, the orthogonal cover code index may be determined based on whether the transmission is for initial access.

[0321] For example, based on the above transmission being a transmission for the initial access, the orthogonal cover code index may be determined based on at least one of a random access preamble identifier, an orthogonal cover code index associated with a random access channel, or a position of a grant within a random access response.

[0322] For example, based on the fact that the transmission is a transmission after the initial connection, the hopping of the orthogonal cover code index may be performed based on at least one of a scrambling ID, a physical cell ID, a synchronization signal block index, or a beam reference signal index. For example, the transmission may be performed based on a configured grant from a base station.

[0323] For example, the transmission may include uplink data channel repetition, and the orthogonal cover code may be applied to the uplink data channel repetition.

[0324] Additionally, for example, the base station may receive from the device a capability related to applying the orthogonal cover code to the transmission based on the initial access resource. For example, a random access preamble transmitted on the initial access resource established between the base station and the device may indicate that the device has the capability to apply the orthogonal cover code to the transmission.

[0325] For example, the unit of application of the orthogonal cover code may be determined based on the unit of repetition of the transmission, and the length of the orthogonal cover code may be determined based on the number of repetitions of the transmission.

[0326] For example, in the procedure for the initial access, the orthogonal cover code index determined based on at least one of the random access preamble ID, the orthogonal cover code index associated with the random access channel, or the position of the grant in the random access response may be hopped based on at least one of the scrambling ID, the physical cell ID, the synchronization signal block index, or the beam reference signal index.

[0327] Additionally, for example, the base station may transmit to the device information related to the section to which the orthogonal cover code is applied. For example, the information related to the section to which the orthogonal cover code is applied may include at least one of information related to the start position to which the orthogonal cover code is applied, information related to the end position to which the orthogonal cover code is applied, or information related to the length of the section to which the orthogonal cover code is applied.

[0328] For example, based on the fact that the transmission is an uplink data channel transmission without a random access preamble and a random access response for the initial connection, a radio network temporary identifier (RNTI) may be selected based on at least one of a time resource, a frequency resource, an orthogonal cover code resource, identification information of the device, or a contention resolution ID associated with the transmission.

[0329] For example, based on the above transmission being an uplink data channel transmission without a random access preamble and a random access response for the initial access, the orthogonal cover code index may be determined based on at least one of a time resource, a frequency resource, an orthogonal cover code resource, identification information of a device, or a contention resolution ID associated with the transmission.

[0330] For example, the transmission may be omitted based on whether at least one of phase continuity or power consistency is not maintained within the interval to which the orthogonal cover code is applied.

[0331] The proposed method can be applied to devices according to various embodiments of the present disclosure. First, the processor (202) of the base station (200) can obtain information related to a plurality of orthogonal cover code indices. Then, the processor (202) of the base station (200) can determine an orthogonal cover code index from among the plurality of orthogonal cover code indices. Then, the processor (202) of the base station (200) can control the transceiver (206) to receive a transmission of the device based on the orthogonal cover code associated with the orthogonal cover code index. For example, the orthogonal cover code index can be determined based on whether the transmission is a transmission for initial access.

[0332] According to one embodiment of the present disclosure, a base station may be provided. For example, the base station 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 base station to: obtain information related to a plurality of orthogonal cover code indices; determine an orthogonal cover code index from among the plurality of orthogonal cover code indices; and receive a transmission from a device based on an orthogonal cover code associated with the orthogonal cover code index. For example, the orthogonal cover code index may be determined based on whether the transmission is a transmission for initial access.

[0333] According to one embodiment of the present disclosure, a processing device configured to control a base station 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 base station to: obtain information related to a plurality of orthogonal cover code indices; determine an orthogonal cover code index from among the plurality of orthogonal cover code indices; and receive a transmission from a device based on an orthogonal cover code associated with the orthogonal cover code index. For example, the orthogonal cover code index may be determined based on whether the transmission is a transmission for initial access.

[0334] 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 base station to: obtain information related to a plurality of orthogonal cover code indices; determine an orthogonal cover code index from among the plurality of orthogonal cover code indices; and receive a transmission from a device based on an orthogonal cover code associated with the orthogonal cover code index. For example, the orthogonal cover code index may be determined based on whether the transmission is for an initial connection.

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

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

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

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

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

[0340] Referring to FIG. 13, 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.

[0341] Here, the wireless communication technology implemented in the wireless devices (100a to 100f) of the present specification 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 specification 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 specification 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.

[0342] 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).

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

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

[0345] Referring to FIG. 14, 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. 13.

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

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

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

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

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

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

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

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

[0354] The codeword can be converted into a wireless signal through the signal processing circuit (1000) of FIG. 15. 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).

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

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

[0357] 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. 15. For example, a wireless device (e.g., 100, 200 of FIG. 14) 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.

[0358] Figure 16 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 13). The embodiment of Figure 16 may be combined with various embodiments of the present disclosure.

[0359] Referring to FIG. 16, the wireless device (100, 200) corresponds to the wireless device (100, 200) of FIG. 14 and may be composed of various elements, components, units / 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. 14. For example, the transceiver(s) (114) may include one or more transceivers (106, 206) and / or one or more antennas (108, 208) of FIG. 14. 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).

[0360] 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. 13, 100a), a vehicle (Fig. 13, 100b-1, 100b-2), an XR device (Fig. 13, 100c), a portable device (Fig. 13, 100d), a home appliance (Fig. 13, 100e), an IoT device (Fig. 13, 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. 13, 400), a base station (Fig. 13, 200), a network node, etc. Wireless devices may be mobile or stationary depending on the use / service.

[0361] In FIG. 16, various elements, components, units / parts, and / or modules within the wireless device (100, 200) may be interconnected entirely 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.

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

[0363] FIG. 17 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. 17 may be combined with various embodiments of the present disclosure.

[0364] Referring to FIG. 17, 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. 16, respectively.

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

[0366] 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).

[0367] FIG. 18 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. 18 may be combined with various embodiments of the present disclosure.

[0368] Referring to FIG. 18, 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. 16, respectively.

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

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

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

Claims

1. In the method, A step of obtaining information related to a plurality of orthogonal cover code indices; A step of determining an orthogonal cover code index among the plurality of orthogonal cover code indices; and A step of performing transmission to a base station based on an orthogonal cover code associated with the above orthogonal cover code index; including, A method wherein the above orthogonal cover code index is determined based on whether the above transmission is a transmission for initial connection.

2. In paragraph 1, A method wherein the orthogonal cover code index is determined based on at least one of a random access preamble identifier (ID), an orthogonal cover code index associated with a random access channel, or a position of a grant in a random access response, based on the above transmission being a transmission for the initial access.

3. In paragraph 1, A method wherein, based on the above transmission being a transmission after the initial connection, hopping of the orthogonal cover code index is performed based on at least one of a scrambling ID, a physical cell ID, a synchronization signal block index, or a beam reference signal index.

4. In paragraph 3, A method in which the above transmission is performed based on a set grant from a base station.

5. In paragraph 1, The above transmission includes uplink data channel repetition, and A method in which the above orthogonal cover code is applied to the above uplink data channel repetition.

6. In paragraph 1, A method further comprising: reporting to a base station, based on initial access resources, capabilities related to application of the orthogonal cover code to the transmission; 7. In paragraph 6, A method wherein a random access preamble transmitted on the initial access resource established between the base station and the device indicates that the device has the capability to apply the orthogonal cover code to the transmission.

8. In paragraph 1, A method wherein the unit of application of the above orthogonal cover code is determined based on the unit of repetition of the above transmission, and the length of the above orthogonal cover code is determined based on the number of repetitions of the above transmission.

9. In paragraph 1, A method in which, in the procedure for the initial connection, the orthogonal cover code index determined based on at least one of the random access preamble ID, the orthogonal cover code index associated with the random access channel, or the position of the grant in the random access response is hopped based on at least one of the scrambling ID, the physical cell ID, the synchronization signal block index, or the beam reference signal index.

10. In paragraph 1, A step of receiving information related to a section to which the above orthogonal cover code is applied from the base station; further comprising: A method wherein information related to a section to which the orthogonal cover code is applied includes at least one of information related to a start position to which the orthogonal cover code is applied, information related to an end position to which the orthogonal cover code is applied, or information related to a length of a section to which the orthogonal cover code is applied.

11. In paragraph 1, A method in which a radio network temporary identifier (RNTI) is selected based on at least one of a time resource, a frequency resource, an orthogonal cover code resource, device identification information, or a contention resolution ID associated with the transmission, based on the above transmission being an uplink data channel transmission without a random access preamble and a random access response for the initial connection.

12. In paragraph 1, A method wherein the above transmission is an uplink data channel transmission without a random access preamble and a random access response for the initial access, wherein the orthogonal cover code index is determined based on at least one of a time resource, a frequency resource, an orthogonal cover code resource, device identification information, or a contention resolution ID related to the transmission.

13. In paragraph 1, A method in which the transmission is omitted based on the fact that at least one of phase continuity or power consistency is not maintained within the section to which the orthogonal cover code is applied.

14. In the device, At least one transmitter / receiver; at least one processor; and At least one memory connected to said at least one processor and storing instructions, said instructions being executed by said at least one processor, wherein said device causes: Obtain information related to multiple orthogonal cover code indices; Determine an orthogonal cover code index among the above plurality of orthogonal cover code indices; and To perform transmission to the base station based on the orthogonal cover code associated with the above orthogonal cover code index, The above orthogonal cover code index is determined based on whether the transmission is a transmission for initial connection.

15. In a processing device set to control a device, at least one processor; and At least one memory connected to said at least one processor and storing instructions, said instructions being executed by said at least one processor, wherein said device causes: Obtain information related to multiple orthogonal cover code indices; Determine an orthogonal cover code index among the above plurality of orthogonal cover code indices; and To perform transmission to the base station based on the orthogonal cover code associated with the above orthogonal cover code index, A processing device wherein the above orthogonal cover code index is determined based on whether the above transmission is a transmission for initial connection.

16. A non-transitory computer-readable storage medium that records commands, The above commands, when executed, cause the device to: Obtain information related to multiple orthogonal cover code indices; Determine an orthogonal cover code index among the above plurality of orthogonal cover code indices; and To perform transmission to the base station based on the orthogonal cover code associated with the above orthogonal cover code index, A non-transitory computer-readable storage medium, wherein the above orthogonal cover code index is determined based on whether the transmission is a transmission for an initial connection.

17. In the method, A step of obtaining information related to a plurality of orthogonal cover code indices; A step of determining an orthogonal cover code index among the plurality of orthogonal cover code indices; and A step of receiving a transmission of a device based on an orthogonal cover code associated with the orthogonal cover code index; comprising: A method wherein the above orthogonal cover code index is determined based on whether the above transmission is a transmission for initial connection.

18. At the base station, At least one transmitter / receiver; at least one processor; and At least one memory connected to said at least one processor and storing instructions, said instructions being executed by said at least one processor, wherein said base station: Obtain information related to multiple orthogonal cover code indices; Determine an orthogonal cover code index among the above plurality of orthogonal cover code indices; and Receiving a transmission from a device based on an orthogonal cover code associated with the above orthogonal cover code index, The above orthogonal cover code index is determined based on whether the transmission is a transmission for initial access, the base station.

19. In a processing device set to control a base station, at least one processor; and At least one memory connected to said at least one processor and storing instructions, said instructions being executed by said at least one processor, wherein said base station: Obtain information related to multiple orthogonal cover code indices; Determine an orthogonal cover code index among the above plurality of orthogonal cover code indices; and Receiving a transmission from a device based on an orthogonal cover code associated with the above orthogonal cover code index, A processing device wherein the above orthogonal cover code index is determined based on whether the above transmission is a transmission for initial connection.

20. A non-transitory computer-readable storage medium that records commands, The above commands, when executed, cause the base station to: Obtain information related to multiple orthogonal cover code indices; Determine an orthogonal cover code index among the above plurality of orthogonal cover code indices; and Receiving a transmission from a device based on an orthogonal cover code associated with the above orthogonal cover code index, A non-transitory computer-readable storage medium, wherein the above orthogonal cover code index is determined based on whether the transmission is a transmission for an initial connection.

Images