WO2025159547A1 - Method and apparatus for performing repetitive transmission and multiplexing of terminal-to-base station communication in non-terrestrial network - Google Patents

Abstract

Proposed is a method for operating a first device (100) in a wireless communication system. The method comprises the steps of: obtaining information regarding multiple resources related to device-to-base station channel repetition; and obtaining information related to an orthogonal cover code, wherein the multiple resources include at least one orthogonal cover code group to which the orthogonal cover code is applied. On the basis of an overlap between the first orthogonal cover code group among the at least one orthogonal cover code group and a device-to-base station physical control channel resource, all transmissions based on the first orthogonal cover code group may be dropped.

Description

Method and device for performing repeated transmission and multiplexing of terminal-to-base station communication in a non-terrestrial network

The present disclosure relates to a wireless communication system.

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.

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.

Maximum data rate per device 1 Tbps E2E delay 1 ms Maximum spectral efficiency 100bps/Hz Mobility support Up to 1000km/hr Satellite integration completely AI completely autonomous driving completely XR completely haptic communication completely

According to one embodiment of the present disclosure, a method that can be performed by a first device may be provided. For example, the method includes: obtaining information about a plurality of device-to-base station physical shared channel resources associated with a device-to-base station physical shared channel repetition; and obtaining information related to an orthogonal cover code, wherein the plurality of device-to-base station physical shared channel resources include at least one orthogonal cover code group to which the orthogonal cover code is applied, wherein based on an overlap between a first device-to-base station physical shared channel resource within a first orthogonal cover code group among the at least one orthogonal cover code group and a first device-to-base station physical control channel resource to which device-to-base station control information is to be transmitted, all device-to-base station physical shared channel transmissions based on the first orthogonal cover code group may be dropped.

According to one embodiment of the present disclosure, a first device may be provided. For example, the first device may include: at least one transceiver; at least one processor; and at least one memory coupled to the at least one processor and storing instructions. For example, the instructions, when executed by the at least one processor, cause the first device to: obtain information about a plurality of device-to-base station physical shared channel resources associated with a device-to-base station physical shared channel repetition; And obtain information related to orthogonal cover codes, wherein the plurality of device-to-base station physical shared channel resources include at least one orthogonal cover code group to which the orthogonal cover code is applied, and based on an overlap of a first device-to-base station physical shared channel resource in a first orthogonal cover code group among the at least one orthogonal cover code group and a first device-to-base station physical control channel resource to which device-to-base station control information is to be transmitted, all device-to-base station physical shared channel transmissions based on the first orthogonal cover code group can be dropped.

According to one embodiment of the present disclosure, a processing device configured to control a first device may be provided. For example, the processing device may include: at least one processor; and at least one memory coupled to the at least one processor and storing instructions. For example, the instructions, based on execution by the at least one processor, cause the first device to: obtain information about a plurality of device-to-base station physical shared channel resources associated with a device-to-base station physical shared channel repetition; And obtain information related to orthogonal cover codes, wherein the plurality of device-to-base station physical shared channel resources include at least one orthogonal cover code group to which the orthogonal cover code is applied, and based on an overlap of a first device-to-base station physical shared channel resource in a first orthogonal cover code group among the at least one orthogonal cover code group and a first device-to-base station physical control channel resource to which device-to-base station control information is to be transmitted, all device-to-base station physical shared channel transmissions based on the first orthogonal cover code group can be dropped.

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, cause a first device to: obtain information about a plurality of device-to-base station physical shared channel resources associated with a device-to-base station physical shared channel repetition; and obtain information associated with an orthogonal cover code, wherein the plurality of device-to-base station physical shared channel resources include at least one orthogonal cover code group to which the orthogonal cover code is applied, and based on an overlap between a first device-to-base station physical shared channel resource within a first orthogonal cover code group of the at least one orthogonal cover code group and a first device-to-base station physical control channel resource to which device-to-base station control information is to be transmitted, all device-to-base station physical shared channel transmissions based on the first orthogonal cover code group may be dropped.

According to one embodiment of the present disclosure, a method that can be performed by a second device may be provided. For example, the method includes: transmitting to a first device information about a plurality of device-to-base station physical shared channel resources associated with a device-to-base station physical shared channel repetition, wherein the plurality of device-to-base station physical shared channel resources include at least one orthogonal cover code group to which an orthogonal cover code is applied; and receiving from the first device device device control information based on a first device-to-base station physical control channel resource, wherein based on an overlap of a first device-to-base station physical shared channel resource within a first orthogonal cover code group among the at least one orthogonal cover code group and the first device-to-base station physical control channel resource, all device-to-base station physical shared channel transmissions based on the first orthogonal cover code group may be dropped.

According to one embodiment of the present disclosure, a second device may be provided. For example, the second device may include: at least one transceiver; at least one processor; and at least one memory coupled to the at least one processor and storing instructions. For example, the instructions, based on being executed by the at least one processor, cause the second device to: transmit to a first device information about a plurality of device-to-base station physical shared channel resources associated with a device-to-base station physical shared channel repetition, wherein the plurality of device-to-base station physical shared channel resources include at least one orthogonal cover code group to which an orthogonal cover code is applied; And receiving device-to-base station control information based on a first device-to-base station physical control channel resource from the first device, wherein based on an overlap of a first device-to-base station physical shared channel resource within a first orthogonal cover code group among the at least one orthogonal cover code group and the first device-to-base station physical control channel resource, all device-to-base station physical shared channel transmissions based on the first orthogonal cover code group can be dropped.

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

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

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

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

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

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

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

FIG. 8 illustrates transmission resources for terminal-to-base station physical shared channel repetition (e.g., PUSCH repetition) to which an orthogonal cover code (e.g., OCC) is applied, according to one embodiment of the present disclosure.

FIG. 9 illustrates a piggyback operation when resources for terminal-to-base station physical control channel transmission (e.g., PUCCH transmission) overlap with resources for terminal-to-base station physical shared channel repetition (e.g., PUSCH repetition) according to one embodiment of the present disclosure.

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

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

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

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

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

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

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

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

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."

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."

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.”

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.”

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

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

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

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

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.

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.

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.

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.

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.

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.

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).

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.

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).

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.

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.

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.

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.

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

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.

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).

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.

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.

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.

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).

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.

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).

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).

Table 2 below illustrates the number of symbols per slot (N ^slot _symb ), the number of slots per frame (N ^frame,u slot ), and the number of slots per subframe (N ^subframe,u _slot ) depending on the SCS setting ( _u ) when normal CP or extended CP is used.

CP type SCS (15*2 ^u ) N ^slot _symb N ^frame,u _slot N ^{subframes, u} _slots Normal CP 15kHz (u=0) 14 10 1 30kHz (u=1) 14 20 2 60kHz (u=2) 14 40 4 120kHz (u=3) 14 80 8 240kHz (u=4) 14 160 16 Extended CP 60kHz (u=2) 12 40 4

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.

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.

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.

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.

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.

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 example, for uplink, the initial BWP can be given by the system information block (SIB) for the random access procedure. For example, the default BWP can be set by a higher layer. For example, the initial value of the default BWP can be the initial DL BWP. For energy saving, if the UE does not detect downlink control information (DCI) for a certain period of time, the UE can switch its active BWP to the default BWP.

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

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

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

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.

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.

For example, the BWP can be set by a point A, an offset from point A (N ^start _BWP ), and a bandwidth (N ^size _BWP ). For example, point A can be an outer reference point of a 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.

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.

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.

- 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.

- 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.

- Large-scale MIMO technology

- Hologram beamforming (HBF)

- Optical wireless technology

- Free-space optical transmission backhaul network (FSO backhaul network)

- Quantum communication

- Cell-free communication

- Integration of wireless information and power transmission

- Integration of wireless communication and sensing

- Integrated access and backhaul network

- Big data analysis

- Reconfigurable intelligent surface

- metaverse

- Block chain

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).

- 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.

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.

- 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.

- 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.

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.

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.

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

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

Here, the terminal may transmit the terminal-to-base station physical shared channel (e.g., PUSCH) using the DFT-s-OFDM (Discrete Fourier Transform Spread Orthogonal Frequency Division Multiplexing) method for coverage gain. Here, the DFT-s-OFDM modulation method may refer to a modulation method in which DFT precoding (or DFT spreading) is applied as part of TF (Transform) precoding before the orthogonal frequency division multiplexing (e.g., OFDM) modulation method.

Meanwhile, when the above-mentioned coverage expansion technology is applied, resource utilization efficiency may decrease due to repetitive transmission, and to solve this problem, an uplink multiplexing method utilizing an orthogonal cover code (e.g., OCC) may be effective. In the present disclosure, a method is proposed to achieve capacity increase and/or multiplexing of a terminal-to-base station communication data channel (e.g., PUSCH) by utilizing an orthogonal cover code (e.g., OCC) when repetitive transmission of terminal-to-base station communication (e.g., UL communication) is performed.

For example, in the following, repeating a terminal-to-base station communication data channel transmission (e.g., PUSCH transmission) may be the same as performing transmissions related to terminal-to-base station communication data channel repetition (e.g., PUSCH repetition).

[Proposal #01]

According to one embodiment of the present disclosure, when a terminal can apply an orthogonal cover code (e.g., OCC) between transmissions of terminal-to-base station communication data channel repetitions (e.g., PUSCH repetitions) (in the time domain) during terminal-to-base station communication data channel transmissions (e.g., PUSCH transmissions), a method may be provided for determining a redundancy version (e.g., RV; Redundancy Version) and/or scrambling for the repeated transmission(s) through one or more of the following methods.

(1) A method to ensure that the same redundancy version (e.g., RV) and/or scrambling is applied to all repeat transmissions.

(2) A method in which the same redundancy version (e.g., RV) and/or scrambling is applied within a resource group to which an orthogonal cover code (e.g., OCC) is applied, and different redundancy versions (e.g., RV) and/or scrambling are applied between resource groups to which an orthogonal cover code (e.g., OCC) is applied.

Here, the application of an orthogonal cover code (e.g., OCC) between repetitions of a terminal-to-base station communication data channel (e.g., PUSCH repetitions) (in the time domain) may mean an operation of applying an orthogonal cover code (e.g., OCC) in units of repeated transmissions (or in units of multiples thereof, or in units of groups of orthogonal cover codes (e.g., OCC) according to the length of the orthogonal cover code (e.g., OCC).

Here, the resource group (e.g., orthogonal cover code (e.g., OCC) group) to which the above orthogonal cover code (e.g., OCC) is applied may mean (time domain) resource(s) to which one orthogonal cover code (e.g., OCC) is applied.

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

According to one embodiment of the present disclosure, assuming that a terminal performs terminal-to-base station communication data channel transmission (e.g., PUSCH transmission), a method may be provided in which the terminal repeatedly performs terminal-to-base station communication data channel transmission (e.g., PUSCH transmission) (in the time domain) and applies an orthogonal cover code (e.g., OCC) (in the time domain) between the repeated transmissions.

Here, the (time domain) orthogonal cover code (e.g., OCC) may be for the purpose of multiplexing one or more terminal-to-base station communication data channel transmissions (e.g., PUSCH transmissions) (within the same cell). Here, in order for the (time domain) orthogonal cover code (e.g., OCC) to be effective, the data (or modulated symbols) of the repeatedly transmitted terminal-to-base station communication data channel (e.g., PUSCH) may need to be identical.

For example, even if transmissions of terminal-to-base station communication data channel repetitions (e.g., PUSCH repetitions) are transmitted with an orthogonal cover code (e.g., OCC) (or by applying an orthogonal cover code (e.g., OCC)), if the redundant version (e.g., RV) and/or scrambling for each repetition is different, orthogonality by the orthogonal cover code (e.g., OCC) may not be guaranteed.

Accordingly, in the present disclosure, when a terminal can apply an orthogonal cover code (e.g., OCC) between transmissions of terminal-to-base station communication data channel repetition (e.g., PUSCH repetition) (in the time domain) during terminal-to-base station communication data channel transmission (e.g., PUSCH transmission), a method is proposed for determining a redundancy version (e.g., RV) and/or scrambling for the repeated transmission(s) through one or more of the following methods.

(1) A method to ensure that the same redundancy version (e.g., RV) and/or scrambling is applied to all repeat transmissions.

(2) A method in which the same redundancy version (e.g., RV) and/or scrambling is applied within a resource group to which an orthogonal cover code (e.g., OCC) is applied, and different redundancy versions (e.g., RV) and/or scrambling are applied between resource groups to which an orthogonal cover code (e.g., OCC) is applied.

According to the proposal of the present disclosure, when terminal-to-base station communication data channel transmissions (e.g., PUSCH transmissions) are performed repeatedly (in the time domain), there may be an advantage of supporting diversity operations for redundant versions (e.g., RV) and/or scrambling while supporting orthogonal cover code (e.g., OCC) based multiplexing.

As an additional operation to the above proposal, according to one embodiment of the present disclosure, a base station (or a network node) may (pre-)define, set and/or instruct a terminal (or a network node) on (time domain) unit information (hereinafter, redundancy version (e.g., RV) granularity) to which a (same) redundancy version (e.g., RV) is applied (for a terminal-to-base station physical shared channel (e.g., PUSCH) to which an orthogonal cover code (e.g., OCC) is applied). Here, the setting and/or instruction may be performed via radio resource control (e.g., RRC; radio resource control) signaling, base station-to-terminal control information (e.g., DCI) and/or MAC control element (e.g., CE; control element).

For example, the base station (or network node) may provide the redundancy version (e.g., RV) granularity to the terminal in units of slots or in units of resource groups (and/or orthogonal cover code (e.g., OCC) lengths) to which orthogonal cover codes (e.g., OCC) are applied. For example, the redundancy version (e.g., RV) granularity may be provided in the form of 2 slots and/or 4 slots.

For example, the granularity of the above duplicate version (e.g., RV) may be provided in the form of one unit (x1) and/or two units (x2) per resource group (and/or per orthogonal cover code (e.g., OCC) length) to which the orthogonal cover code (e.g., OCC) is applied.

For example, when transmissions of terminal-to-base station physical shared channel repetitions (e.g., PUSCH repetitions) to which an orthogonal cover code (e.g., OCC) of length 2 is applied (hereinafter, transmissions of the first terminal-to-base station physical shared channel repetitions (e.g., PUSCH repetitions)) and transmissions of terminal-to-base station physical shared channel repetitions (e.g., PUSCH repetitions) to which an orthogonal cover code (e.g., OCC) of length 4 is applied (hereinafter, transmissions of the second terminal-to-base station physical shared channel repetitions (e.g., PUSCH repetitions)) are multiplexed, the base station (or network node) may multiplex the transmissions of the first terminal-to-base station physical shared channel repetitions (e.g., PUSCH repetitions) to which an orthogonal cover code (e.g., OCC) of length 4 is applied, A redundancy version (e.g., RV) granularity that is doubled may be set and/or indicated, and a redundancy version (e.g., RV) granularity that is 1 time the length of the orthogonal cover code (e.g., OCC) may be set and/or indicated for transmissions of the second terminal-to-base station physical shared channel repetition (e.g., PUSCH repetition).

As another example, when transmissions of terminal-to-base station physical shared channel repetitions (e.g., PUSCH repetitions) with an orthogonal cover code (e.g., OCC) of length 2 (hereinafter, third terminal-to-base station physical shared channel repetitions (e.g., PUSCH repetitions)) and transmissions of terminal-to-base station physical shared channel repetitions (e.g., PUSCH repetitions) with an orthogonal cover code (e.g., OCC) of length 2 (hereinafter, fourth terminal-to-base station physical shared channel repetitions (e.g., PUSCH repetitions)) are multiplexed, the base station (or network node) may apply an orthogonal cover code (e.g., OCC) of length 2 to both the third and fourth terminal-to-base station physical shared channel repetitions (e.g., PUSCH repetitions) to the transmissions. You can set and/or indicate the granularity of the duplicate version (e.g., RV) to be 1x the length of the code (e.g., OCC).

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

[Proposal #02]

According to one embodiment of the present disclosure, when a terminal can apply an orthogonal cover code (e.g., OCC) between transmissions of terminal-to-base station communication data channel repetitions (e.g., PUSCH repetitions) (in the time domain) during terminal-to-base station communication data channel transmissions (e.g., PUSCH transmissions), when a terminal-to-base station control channel transmission (e.g., PUCCH transmission; physical uplink control channel transmission) occurs at the time of terminal-to-base station communication data channel transmission (e.g., PUSCH transmission) to which the orthogonal cover code (e.g., OCC) is applied (or, a time interval related to a resource on which the transmission is performed), a method for supporting multiplexing in one or more of the following ways may be provided.

(1) A method in which the terminal first performs the terminal-to-base station communication multiplexing rules (e.g., UL multiplexing rules) when the orthogonal cover code (e.g., OCC) is not applied, and then performs an additional exception handling process when the orthogonal cover code (e.g., OCC) is applied.

For example, according to the above method, when the terminal-to-base station communication multiplexing rule (e.g., UL multiplexing rule) is performed first when the orthogonal cover code (e.g., OCC) is not applied, and then when the terminal-to-base station control information (e.g., UCI; uplink control information) is included in (specific) repetitive transmission of the terminal-to-base station communication data channel (e.g., PUSCH), the suitability of the processing time for piggybacking the terminal-to-base station control information (e.g., UCI) is (re)confirmed based on the first transmission time point within the resource group to which the same orthogonal cover code (e.g., OCC) as the repetitive transmission is applied, and if the processing time is suitable (sufficient), the terminal-to-base station control information (e.g., UCI) is repeatedly transmitted within the resource group to which the orthogonal cover code (e.g., OCC) is applied, and otherwise, the corresponding Terminal-to-base station data transmissions (e.g., PUSCH transmissions) may be omitted.

(2) A method of defining terminal-to-base station communication multiplexing rules (e.g., UL Multiplexing Rule) when the terminal applies an orthogonal cover code (e.g., OCC) separately from when the terminal does not apply an orthogonal cover code (e.g., OCC).

For example, when applying an orthogonal cover code (e.g., OCC), a terminal-to-base station communication multiplexing rule (e.g., UL multiplexing rule) can be defined considering the processing time based on the first terminal-to-base station communication data channel (e.g., PUSCH) of the resource group to which the orthogonal cover code (e.g., OCC) is applied.

Here, the terminal-to-base station communication multiplexing rule (e.g., UL multiplexing rule) may mean an action performed by a terminal when transmission interval(s) of multiple different terminal-to-base station transmission channel(s) (e.g., PUCCH or PUSCH) (from the same terminal) overlap (in the time domain).

Here, the application of an orthogonal cover code (e.g., OCC) between terminal-to-base station communication data channel repetitions (e.g., PUSCH repetitions) (in the time domain) may mean an operation of applying an orthogonal cover code (e.g., OCC) in units of repeated transmissions.

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

According to one embodiment of the present disclosure, assuming that a terminal performs terminal-to-base station communication data channel transmission (e.g., PUSCH transmission), a method may be provided in which the terminal repeatedly performs terminal-to-base station communication data channel transmission (e.g., PUSCH transmission) (in the time domain) and applies an orthogonal cover code (e.g., OCC) (in the time domain) between the repeated transmissions.

Here, the (time domain) orthogonal cover code (e.g., OCC) may be for the purpose of multiplexing one or more terminal-to-base station communication data channel transmissions (e.g., PUSCH transmissions) (within the same cell).

Here, when an orthogonal cover code (e.g., OCC) is applied between transmissions of the terminal-to-base station communication data channel repetition (e.g., PUSCH repetition), a two-way terminal-to-base station communication multiplexing rule (e.g., UL multiplexing rule) may be considered. Here, the terminal-to-base station communication multiplexing rule (e.g., UL multiplexing rule) may include terminal operation when transmissions between terminal-to-base station communication data channels (e.g., PUSCH)(s) and terminal-to-base station control channels (e.g., PUCCH)(s) overlap (in the time domain).

According to one embodiment of the present disclosure, a method may be provided in which a terminal first performs a terminal-to-base station communication multiplexing rule (e.g., UL multiplexing rule) when an orthogonal cover code (e.g., OCC) is not applied, and then an additional exception handling process is performed when an orthogonal cover code (e.g., OCC) is applied.

For example, when the UE-to-base station communication multiplexing rule (e.g., UL multiplexing rule) is performed first when the orthogonal cover code (e.g., OCC) is not applied, and then UE-to-base station control information (e.g., UCI) is included in (specific) repetitive transmissions of the UE-to-base station communication data channel (e.g., PUSCH), the suitability of the processing time for piggybacking the UE-to-base station control information (e.g., UCI) is (re)confirmed based on the first transmission time point within the resource group to which the same orthogonal cover code (e.g., OCC) as the repetitive transmission is applied, and if the processing time is suitable (sufficient), the UE-to-base station control information (e.g., UCI) is repeatedly transmitted within the resource group to which the orthogonal cover code (e.g., OCC) is applied, otherwise, the corresponding UE-to-base station data transmissions (e.g., PUSCH transmissions) are omitted. Can be.

According to one embodiment of the present disclosure, a method may be provided for defining a terminal-to-base station communication multiplexing rule (e.g., UL multiplexing rule) when a terminal applies an orthogonal cover code (e.g., OCC) separately from when the orthogonal cover code (e.g., OCC) is not applied. For example, when an orthogonal cover code (e.g., OCC) is applied, a terminal-to-base station communication multiplexing rule (e.g., UL multiplexing rule) may be defined considering a processing time based on a first terminal-to-base station communication data channel (e.g., PUSCH) of a resource group to which the orthogonal cover code (e.g., OCC) is applied.

According to the above-described proposal of the present disclosure, there may be an advantage in that terminal-to-base station communication multiplexing rules (e.g., UL multiplexing rules) can be supported when the terminal can apply an orthogonal cover code (e.g., OCC) between transmissions of terminal-to-base station communication data channel repetitions (e.g., PUSCH repetitions) (in the time domain) during terminal-to-base station communication data channel transmissions (e.g., PUSCH transmissions).

As an additional operation for the above proposal, according to one embodiment of the present disclosure, a base station (or a network node) (in advance) defines, sets and/or instructs a time margin (hereinafter, a first time margin) to a terminal, and the terminal performs a terminal-to-base station control information (e.g., UCI) multiplexing (and/or terminal-to-base station control information (e.g., UCI) multiplexing and/or terminal-to-base station control information (e.g., UCI) and/or terminal-to-base station control information (e.g., UCI) piggybacking on a terminal-to-base station physical shared channel (e.g., PUSCH)), based on a required operation time (and/or processing time and/or timeline) condition (hereinafter, a first condition) plus the first time margin, (and/or processing time and/or timeline) condition (hereinafter, a second condition) A method for determining whether terminal-to-base station control information (e.g., UCI) is multiplexed is proposed.

Here, the first time margin may be positive or negative. For example, in a non-terrestrial network according to an embodiment of the present disclosure, there may be differences in understanding of relative timing (and/or time advance (e.g., TA; Timing Advance) between base station-to-terminal communication (e.g., DL communication) and terminal-to-base station communication (e.g., UL communication) between a base station (or network node) and a terminal.

In the above case, the terminal may perform unexpected terminal-to-base station control information (e.g., UCI) multiplexing from the base station (or network node). If the first time margin is sufficiently large to include the degree of time advance (e.g., TA) mismatch between the base station (or network node) and the terminal, and if the terminal determines whether to perform terminal-to-base station control information (e.g., UCI) multiplexing based on the second condition, the understanding and/or judgment of whether to perform terminal-to-base station control information (e.g., UCI) multiplexing between the base station (or network node) and the terminal may be consistent and/or aligned.

Here, the terminal may conservatively not perform terminal-to-base station control information (e.g., UCI) multiplexing even when terminal-to-base station control information (e.g., UCI) multiplexing is possible based on the actual required computation time (and/or, processing time, and/or, timeline) conditions for terminal-to-base station control information (e.g., UCI) multiplexing.

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

FIG. 8 illustrates transmission resources for UE-to-base station physical shared channel repetition (e.g., PUSCH repetition) using an orthogonal cover code (e.g., OCC) according to one embodiment of the present disclosure. The embodiment of FIG. 8 may be combined with various embodiments of the present disclosure.

Referring to FIG. 8, transmission resources for repetition of a terminal-to-base station physical shared channel to which an orthogonal cover code (e.g., OCC) having a length of 4 is applied are shown. For example, in the repetition of the terminal-to-base station physical shared channel (e.g., PUSCH repetition), the terminal-to-base station physical shared channel transmission can be performed 8 times. That is, since the length of the orthogonal cover code (e.g., OCC) is 4, there can be two orthogonal cover code (e.g., OCC) groups. In the present embodiment, the orthogonal cover code (e.g., OCC) group can include a first orthogonal cover code (e.g., OCC) group and a second orthogonal cover code (e.g., OCC) group.

In the present embodiment, it is assumed that some of the resources within the first orthogonal cover code (e.g., OCC) group temporally overlap with terminal-to-base station physical shared channel (e.g., PUCCH) resources. In this case, a terminal performing the terminal-to-base station physical shared channel repetition (e.g., PUSCH repetition) may omit (or drop) transmissions based on the first orthogonal cover code (e.g., OCC) group (e.g., according to various embodiments described in the present disclosure). This may be because information transmitted via terminal-to-base station physical control channel transmission (e.g., PUCCH transmission) may be more important than data to be transmitted via terminal-to-base station physical shared channel transmission (e.g., PUSCH transmission).

FIG. 9 illustrates a piggyback operation when resources for terminal-to-base station physical control channel transmission (e.g., PUCCH transmission) overlap with resources for terminal-to-base station physical shared channel repetition (e.g., PUSCH repetition), according to one embodiment of the present disclosure. The embodiment of FIG. 9 may be combined with various embodiments of the present disclosure.

Referring to FIG. 9, transmission resources for repetition of a terminal-to-base station physical shared channel to which an orthogonal cover code (e.g., OCC) having a length of 4 is applied are shown. For example, in the repetition of the terminal-to-base station physical shared channel (e.g., PUSCH repetition), the terminal-to-base station physical shared channel transmission can be performed 8 times. That is, since the length of the orthogonal cover code (e.g., OCC) is 4, there can be two orthogonal cover code (e.g., OCC) groups. In the present embodiment, the orthogonal cover code (e.g., OCC) group can include a first orthogonal cover code (e.g., OCC) group and a second orthogonal cover code (e.g., OCC) group.

Here, the terminal that performs the terminal-to-base station physical shared channel repetition (e.g., PUSCH repetition) can determine that the resources for terminal-to-base station physical control channel transmission (e.g., PUCCH transmission) at the first time point overlap with the resources for the terminal-to-base station physical shared channel repetition (e.g., PUSCH repetition) (in particular, the first orthogonal cover code (e.g., OCC) group).

Here, for example, if the time interval between the second time point, which is the start time of the first orthogonal cover code (e.g., OCC) group, and the first time point is greater than or equal to a processing time (pre-)configured for the terminal (in the present embodiment, it is assumed that the time interval is greater than or equal to the processing time (pre-)configured for the terminal), the terminal may transmit the terminal-to-base station physical control channel transmission (e.g., PUCCH transmission) together with the terminal-to-base station physical shared channel repetition (e.g., PUSCH repetition) by piggybacking it.

This can have the effect of improving the efficiency of radio resources by allowing both terminal-to-base station physical shared channel repetition (e.g., PUSCH repetition) and terminal-to-base station physical control channel transmission (e.g., PUCCH transmission) to be performed if the processing time required for piggybacking (or multiplexing) operation is secured.

[Proposal #03]

According to one embodiment of the present disclosure, when a terminal is capable of applying an orthogonal cover code (e.g., OCC) to a terminal-to-base station communication data channel (e.g., PUSCH) (and/or its repeated transmissions), or when the terminal is capable of applying an orthogonal cover code (e.g., OCC) between transmissions of a terminal-to-base station communication data channel repetition (e.g., PUSCH repetition), if some of the repeated transmission(s) include terminal-to-base station control information transmission (e.g., UCI transmission) (e.g., terminal-to-base station control information (e.g., UCI) on a terminal-to-base station physical shared channel (e.g., PUSCH), or terminal-to-base station control information (e.g., UCI) piggybacking) (or, some of the repeated transmission(s) and terminal-to-base station control information transmission (e.g., UCI transmission) in the time domain), (In case of overlapping), a method may be provided for the terminal to perform one or more of the following actions:

(1) Non-application or (partial) application of orthogonal cover code (e.g., OCC)

(2) Omission of transmissions of (all) UE-to-base station physical shared channel repetitions (e.g., PUSCH repetitions) associated with an orthogonal cover code (e.g., OCC) applied resource group (including transmissions of UE-to-base station physical shared channel repetitions (e.g., PUSCH repetitions) that are the target of UE-to-base station control information (e.g., UCI) transmission)

(3) Repeated transmission of the UE-to-base station control information (e.g., UCI) within transmissions of (all) UE-to-base station physical shared channel repetitions (e.g., PUSCH repetitions) associated with an orthogonal cover code (e.g., OCC) applied resource group (including transmissions of UE-to-base station physical shared channel repetitions (e.g., PUSCH repetitions) targeting UE-to-base station control information (e.g., UCI) transmission)

Here, the application of an orthogonal cover code (e.g., OCC) between repetitions of the terminal-to-base station communication data channel (e.g., repetitions of the terminal-to-base station physical shared channel (e.g., PUSCH)) (in the time domain) may mean an operation of applying an orthogonal cover code (e.g., OCC) in units of repetition transmission.

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

According to one embodiment of the present disclosure, assuming that a terminal performs terminal-to-base station communication data channel transmission (e.g., PUSCH transmission), a method may be provided in which the terminal repeatedly performs terminal-to-base station communication data channel transmission (e.g., PUSCH transmission) (in the time domain) and applies an orthogonal cover code (e.g., OCC) (in the time domain) between the repeated transmissions.

Here, the (time domain) orthogonal cover code (e.g., OCC) may be for the purpose of multiplexing one or more terminal-to-base station communication data channel transmissions (e.g., PUSCH transmissions) (within the same cell). Here, as one of the conditions for applying the orthogonal cover code (e.g., OCC), the terminal may be required to repeatedly generate and/or map the same signal for the unit to which the orthogonal cover code (e.g., OCC) is applied.

When a terminal repeatedly transmits a terminal-to-base station physical shared channel (e.g., PUSCH), the transmission time points of some of the repeated transmission(s) (or the time interval during which the transmission(s) are performed) may overlap with the terminal-to-base station control channel (e.g., PUCCH), and thus the repeated transmission(s) (or the time interval during which the transmission(s) are performed) may include transmission of terminal-to-base station control information (e.g., UCI).

Here, when a terminal applies an orthogonal cover code (e.g., OCC) between transmissions of terminal-to-base station communication data channel repetitions (e.g., PUSCH repetitions) (in the time domain) during terminal-to-base station communication data channel transmissions (e.g., PUSCH transmissions), if only some (repeated) transmissions within a resource group to which the orthogonal cover code (e.g., OCC) is applied include transmission of terminal-to-base station control information (e.g., UCI), the same signal repetition condition, which is one of the conditions for applying the orthogonal cover code (e.g., OCC), may be violated.

Accordingly, according to one embodiment of the present disclosure, when a terminal can apply an orthogonal cover code (e.g., OCC) between transmissions of terminal-to-base station communication data channel repetitions (e.g., PUSCH repetitions) (in the time domain) during terminal-to-base station communication data channel transmissions (e.g., PUSCH transmissions), and when some of the repeated transmission(s) include terminal-to-base station control information transmissions (e.g., UCI transmissions) (e.g., terminal-to-base station control information (e.g., UCI) on a terminal-to-base station physical shared channel (e.g., PUSCH) or terminal-to-base station control information (e.g., UCI) piggybacking), a method is proposed in which the terminal performs one or more of the following operations.

(1) Non-application or (partial) application of orthogonal cover code (e.g., OCC)

(2) Omission of transmissions of (all) UE-to-base station physical shared channel repetitions (e.g., PUSCH repetitions) associated with an orthogonal cover code (e.g., OCC) applied resource group (including transmissions of UE-to-base station physical shared channel repetitions (e.g., PUSCH repetitions) that are the target of UE-to-base station control information (e.g., UCI) transmission)

(3) Repeated transmission of the UE-to-base station control information (e.g., UCI) within transmissions of (all) UE-to-base station physical shared channel repetitions (e.g., PUSCH repetitions) associated with an orthogonal cover code (e.g., OCC) applied resource group (including transmissions of UE-to-base station physical shared channel repetitions (e.g., PUSCH repetitions) targeting UE-to-base station control information (e.g., UCI) transmission)

Here, when the UE performs UE-to-base station physical shared channel repetition (e.g., PUSCH repetition), if the condition for applying an orthogonal cover code (e.g., OCC) is violated due to transmission of UE-to-base station control information (e.g., UCI) within (some) transmissions (or, a time interval during which (some) transmissions are performed) of UE-to-base station physical shared channel repetition (e.g., PUSCH repetition), the UE may satisfy the condition for applying an orthogonal cover code (e.g., OCC) by canceling the application of the orthogonal cover code (e.g., OCC), omitting transmission(s) of the related UE-to-base station physical shared channel repetition (e.g., PUSCH repetition), or repeatedly transmitting UE-to-base station control information (e.g., UCI) within the orthogonal cover code (e.g., OCC) application resource group.

According to the above-described proposal of the present disclosure, there may be an advantage in clarifying the terminal operation by defining an exception handling operation in a situation where some of the conditions for applying an orthogonal cover code (e.g., OCC) are violated due to a terminal-to-base station control information (e.g., UCI) (or terminal-to-base station control information (e.g., UCI) piggybacking) process on a terminal-to-base station physical shared channel (e.g., PUSCH).

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

[Proposal #04]

According to one embodiment of the present disclosure, when a terminal can apply an orthogonal cover code (e.g., OCC) to a terminal-to-base station communication data channel (e.g., PUSCH) (and/or its repeated transmission), a method may be provided in which a base station utilizes a time domain resource allocation field (e.g., a Time Domain Resource Allocation (TDRA) field) in a dynamic control channel (e.g., a PDCCH and/or base station-to-terminal control information (e.g., DCI)) (for the terminal-to-base station communication data channel (e.g., PUSCH)) and/or a redundant field (e.g., some and/or all of a redundant version (e.g., RV) field) generated when applying the orthogonal cover code (e.g., OCC) to indicate one or more of the following information to the terminal.

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

(2) Orthogonal cover code (e.g., OCC) length

(3) Orthogonal cover code (e.g., OCC) index

For example, a specific state indicated by the time domain resource allocation field (e.g., TDRA field) may indicate a configuration combination including time domain resource allocation, and the configuration combination may be a combination including an orthogonal cover code (e.g., OCC) type, an orthogonal cover code (e.g., OCC) length, and/or an orthogonal cover code (e.g., OCC) index.

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

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

Here, the application section of the orthogonal cover code (e.g., OCC) may be determined by the orthogonal cover code (e.g., OCC) application unit and/or the orthogonal cover code (e.g., OCC) length setting.

Here, for example, when an orthogonal cover code (e.g., OCC) is applied to the terminal-to-base station communication data channel (e.g., PUSCH), the time domain resource allocation field (e.g., TDRA field) may be extended to include a redundant field (e.g., a redundant version (e.g., RV) field) that occurs when the orthogonal cover code (e.g., OCC) is applied.

Here, the redundant field generated when applying the orthogonal cover code (e.g., OCC) may refer to bit(s) generated when the purpose of an existing field is reduced or eliminated due to the application of the orthogonal cover code (e.g., OCC). For example, when applying the orthogonal cover code (e.g., OCC), since the redundant version (e.g., RV) value must be repeatedly applied, some and/or all of the redundant version (e.g., RV) field may not be used, and in this case, some and/or all of the redundant version (e.g., RV) field may be included in the redundant field.

Here, for example, to support dynamic scheduling for orthogonal cover code (e.g., OCC) index resources, the orthogonal cover code (e.g., OCC) type and/or the orthogonal cover code (e.g., OCC) length may be indicated via a time-domain resource allocation field (e.g., TDRA field), and the orthogonal cover code (e.g., OCC) index may be indicated using a separate field (e.g., a redundant version (e.g., RV) field) independent from the time-domain resource allocation (e.g., TDRA).

Here, the orthogonal cover code (e.g., OCC) type may include an orthogonal cover code (e.g., OCC) type applied within a single terminal-to-base station physical shared channel (e.g., PUSCH), an orthogonal cover code (e.g., OCC) type applied for terminal-to-base station physical shared channel (e.g., PUSCH) repetition type A, and/or an orthogonal cover code (e.g., OCC) type applied for terminal-to-base station physical shared channel (e.g., PUSCH) repetition type B.

Here, for example, the orthogonal cover code (e.g., OCC) type may be implicitly determined without separate settings and/or instructions depending on the terminal-to-base station physical shared channel (e.g., PUSCH) transmission type (e.g., single transmission and/or repetitive transmission) and whether the orthogonal cover code (e.g., OCC) is applied.

According to one embodiment of the present disclosure, assuming that a terminal performs terminal-to-base station communication data channel transmission (e.g., PUSCH transmission), a method may be provided in which the terminal repeatedly performs terminal-to-base station communication data channel transmission (e.g., PUSCH transmission) (in the time domain) and applies an orthogonal cover code (e.g., OCC) (in the time domain) between the repeated transmissions.

Here, the (time domain) orthogonal cover code (e.g., OCC) may be for the purpose of multiplexing one or more terminal-to-base station communication data channel transmissions (e.g., PUSCH transmissions) (within the same cell).

Here, when a terminal-to-base station communication data channel (e.g., PUSCH) to which the orthogonal cover code (e.g., OCC) is applied is scheduled through dynamic control information, components of the orthogonal cover code (e.g., OCC) applied to the terminal-to-base station communication data channel (e.g., PUSCH) (e.g., orthogonal cover code (e.g., OCC) type, orthogonal cover code (e.g., OCC) length, and/or orthogonal cover code (e.g., OCC) index) can be indicated through the corresponding dynamic control information.

Here, for example, the orthogonal cover code (e.g., OCC) may be associated with time-domain repetitive transmission of a terminal-to-base station communication data channel (e.g., PUSCH), and the repetitive transmission information may be indicated via a time-domain resource allocation field (e.g., time-domain resource allocation (e.g., TDRA)) in the dynamic control information (for the terminal-to-base station communication data channel (e.g., PUSCH)).

Here, for example, the base station may also indicate orthogonal cover code (e.g., OCC) information in the time domain resource allocation field (for a terminal-to-base station communication data channel (e.g., PUSCH)) within the dynamic control information.

For example, a specific state indicated by the time domain resource allocation field (e.g., TDRA field) may indicate a configuration combination including time domain resource allocation, and the configuration combination may be a combination including an orthogonal cover code (e.g., OCC) type, an orthogonal cover code (e.g., OCC) length, and/or an orthogonal cover code (e.g., OCC) index.

Here, for example, orthogonal cover code (e.g., OCC) information (e.g., orthogonal cover code (e.g., OCC) type, orthogonal cover code (e.g., OCC) length, and/or orthogonal cover code (e.g., OCC) index) for each state of the time domain resource allocation (e.g., TDRA) can be (pre-)set and/or (pre-)defined by the base station to the terminal.

Here, when indicating orthogonal cover code (e.g., OCC) components (e.g., orthogonal cover code (e.g., OCC) type, orthogonal cover code (e.g., OCC) length, and/or orthogonal cover code (e.g., OCC) index), redundant fields (e.g., some and/or all of the redundant version (e.g., RV) fields) generated when applying the orthogonal cover code (e.g., OCC) may be utilized.

For example, when applying an orthogonal cover code (e.g., OCC), since the redundant version (e.g., RV) value must be repeatedly applied, some and/or all of the redundant version (e.g., RV) field may not be used, and in such a case, some and/or all of the redundant version (e.g., RV) field may be included in the redundant field.

Here, for example, the base station can indicate orthogonal cover code (e.g., OCC) components (e.g., orthogonal cover code (e.g., OCC) type, orthogonal cover code (e.g., OCC) length, and/or orthogonal cover code (e.g., OCC) index) by utilizing a time domain resource allocation field (e.g., a time domain resource allocation (e.g., TDRA) field) and/or a redundant field (e.g., some and/or all of a redundant version (e.g., RV) field) generated when applying the orthogonal cover code (e.g., OCC).

For example, an extended time domain resource allocation field (e.g., TDRA field) can be formed by adding a redundant field (e.g., a redundant version (e.g., RV) field) to an existing time domain resource allocation field (e.g., TDRA field), and then an orthogonal cover code (e.g., OCC) component can be indicated through the extended time domain resource allocation field (e.g., TDRA field).

For example, the orthogonal cover code (e.g., OCC) type and/or the orthogonal cover code (e.g., OCC) length may be indicated via a time domain resource allocation field (e.g., TDRA field), and the orthogonal cover code (e.g., OCC) index may be indicated using a separate field (e.g., a redundant version (e.g., RV) field) independent of the time domain resource allocation (e.g., TDRA).

According to the proposal of the present disclosure, when a (time domain) orthogonal cover code (e.g., OCC) is applied to a terminal-to-base station communication data channel (e.g., PUSCH) (and/or its repeated transmission), there may be an advantage in that the orthogonal cover code (e.g., OCC) components (e.g., orthogonal cover code (e.g., OCC) type, orthogonal cover code (e.g., OCC) length, and/or orthogonal cover code (e.g., OCC) index) can be efficiently indicated by utilizing a time domain resource allocation field (e.g., time domain resource allocation (e.g., TDRA)) and/or a redundancy field (e.g., redundancy version (e.g., RV) field) (when applying the orthogonal cover code (e.g., OCC)).

The above [Proposal #04] can be applied in combination with other proposal(s) to the extent that the actions of the disclosure do not conflict.

[Proposal #05]

According to one embodiment of the present disclosure, when a terminal can apply an orthogonal cover code (e.g., OCC) to a terminal-to-base station communication data channel (e.g., PUSCH) (and/or its repeated transmission), a method may be provided for performing one or more of the following operations when the terminal-to-base station communication data channel (e.g., PUSCH) to which the orthogonal cover code (e.g., OCC) is applied overlaps and/or collides (in the time domain) with a terminal-to-base station control channel (e.g., PUCCH).

(1) Piggybacking operation of terminal-to-base station control information (e.g., UCI) within the terminal-to-base station physical shared channel (e.g., PUSCH).

(2) Omission of terminal-to-base station physical shared channel (e.g., PUSCH) transmission

(3) Omission of control information (terminal-to-base station control information (e.g., UCI)) transmission

Here, the base station can (pre-)promise with the terminal, (pre-)configure with the terminal, and/or (dynamically) instruct the terminal which of the above operation(s) to perform.

Here, the omission of transmission of the control information (e.g., terminal-to-base station control information (e.g., UCI)) may be determined and/or set differently and/or independently depending on the type of terminal-to-base station control information (e.g., UCI). For example, if the terminal-to-base station control information (e.g., UCI) is channel state information (e.g., CSI; channel state information), transmission omission may be allowed and/or set, and if it is feedback information (e.g., HARQ-ACK), omission may not be allowed and/or set.

According to one embodiment of the present disclosure, assuming that a terminal performs terminal-to-base station communication data channel transmission (e.g., PUSCH transmission), a method may be provided in which the terminal repeatedly performs terminal-to-base station communication data channel transmission (e.g., PUSCH transmission) (in the time domain) and applies an orthogonal cover code (e.g., OCC) (in the time domain) between the repeated transmissions.

Here, the (time domain) orthogonal cover code (e.g., OCC) may be for the purpose of multiplexing one or more terminal-to-base station communication data channel transmissions (e.g., PUSCH transmissions) (within the same cell).

Here, when the terminal needs to transmit a terminal-to-base station control channel (e.g., PUCCH) that collides with transmissions of terminal-to-base station physical shared channel repetitions (e.g., PUSCH repetitions) to which the above orthogonal cover code (e.g., OCC) is applied, the terminal may transmit terminal-to-base station control information (e.g., UCI), which is control information intended to be transmitted through the terminal-to-base station physical control channel (e.g., PUCCH), by including it in the terminal-to-base station physical shared channel (e.g., PUSCH) channel (e.g., terminal-to-base station control information (e.g., UCI) piggybacking).

Here, for example, if some of the repeated transmissions of the terminal-to-base station physical shared channel repetitions (e.g., PUSCH repetitions) to which the orthogonal cover code (e.g., OCC) is applied include terminal-to-base station control information (e.g., UCI), the orthogonality of the orthogonal cover code (e.g., OCC) may not be guaranteed because the data repetition transmissions are not maintained.

Therefore, the present disclosure proposes a method in which a base station prioritizes transmission of a terminal-to-base station physical shared channel (e.g., PUSCH) to which an orthogonal cover code (e.g., OCC) is applied as needed.

According to one embodiment of the present disclosure, when a specific terminal-to-base station control information (e.g., UCI) transmission collides with a terminal-to-base station physical shared channel (e.g., PUSCH) transmission to which an orthogonal cover code (e.g., OCC) is applied, the base station configures and/or instructs the terminal to skip the terminal-to-base station control information (e.g., UCI) transmission, and the terminal can skip the control information (e.g., terminal-to-base station control information (e.g., UCI)) transmission and transmit the terminal-to-base station physical shared channel (e.g., PUSCH) based on the orthogonal cover code (e.g., OCC) in its entirety according to the configuration and/or instruction of the base station.

According to the embodiment of the present disclosure, the overall system performance can be improved by allowing the base station to give priority to transmission of a terminal-to-base station communication data channel (e.g., PUSCH transmission) to which an orthogonal cover code (e.g., OCC) is applied over transmission of a specific type of terminal-to-base station control information (e.g., UCI).

The above [Proposal #05] can be applied in combination with other proposal(s) to the extent that the actions of the disclosure do not conflict.

[Proposal #06]

According to one embodiment of the present disclosure, when a terminal can apply an orthogonal cover code (e.g., OCC) between transmissions of terminal-to-base station communication data channel repetitions (e.g., PUSCH repetitions) (in the time domain) during terminal-to-base station communication data channel transmissions (e.g., PUSCH transmissions), a method may be provided in which the terminal supports one or more of the following operations when a resource group to which the orthogonal cover code (e.g., OCC) is applied overlaps and/or collides (in the time domain) with two or more terminal-to-base station control channels (e.g., PUCCH).

(1) An operation that does not expect overlap and/or collision between a (single) resource group to which an orthogonal cover code (e.g., OCC) is applied and two or more (different) terminal-to-base station control information (e.g., UCI) (for example, when the above case occurs, the terminal may treat it as an error case).

(2) When two or more (different) terminal-to-base station control information (e.g., UCI) overlap and/or collide with a (single) resource group to which an orthogonal cover code (e.g., OCC) is applied, an operation of selecting and multiplexing a single terminal-to-base station control information (e.g., UCI) according to one or more of the following terminal-to-base station control information (e.g., UCI) priority rules.

i) Terminal-to-base station control information (e.g., UCI) that is ahead in the time domain may have higher priority.

ii) Terminal-to-base station control information (e.g., UCI) with a large payload size may have a higher priority. Alternatively, terminal-to-base station control information (e.g., UCI) associated with more data transmission may have a higher priority.

iii) URLLC-related terminal-to-base station control information (e.g., UCI) may have a high priority. For example, terminal-to-base station control information (e.g., UCI) with a high priority index may have a high priority.

iv) Terminal-to-base station control information (e.g., UCI) related to a high number of retransmissions may have a high priority.

v) Terminal-to-base station control information (e.g., UCI) that has a scheduling point in time ahead of the relevant data may have a higher priority.

vi) Feedback transmission (e.g., HARQ-ACK transmission) may have a higher priority than channel state information (e.g., CSI) transmission.

vii) Beam reporting may have higher priority than channel quality information (e.g., CQI), precoding matrix indicator (e.g., PMI), and/or rank indicator (e.g., RI).

viii) The rank indicator (e.g., RI) may have higher priority than the channel quality information (e.g., CQI) and/or the precoding matrix indicator (e.g., PMI).

ix) Channel state information (e.g., CSI) related to process index with low (or high) channel state information (e.g., CSI) may have high priority.

x) Aperiodic terminal-to-base station control information (e.g., UCI) may have a higher priority than periodic terminal-to-base station control information (e.g., UCI).

xi) It can be implemented according to the terminal.

Here, for example, the terminal-to-base station communication multiplexing rule (e.g., UL multiplexing rule) may mean an action performed by a terminal when transmission interval(s) of multiple different terminal-to-base station transmission channel(s) (e.g., PUCCH or PUSCH) (from the same terminal) overlap (in the time domain).

Here, the priority rules described above can be extended for tie-breaking purposes even when two or more terminal-to-base station control information (e.g., UCI) of the same priority overlap and/or collide with a (single) resource group to which an orthogonal cover code (e.g., OCC) is applied.

Here, the application of an orthogonal cover code (e.g., OCC) between terminal-to-base station communication data channel repetitions (e.g., PUSCH repetitions) (in the time domain) may mean an operation of applying an orthogonal cover code (e.g., OCC) in units of repeated transmissions.

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

Here, the terminal can support multiplexing of one terminal-to-base station control information (e.g., UCI) within a resource group to which an orthogonal cover code (e.g., OCC) is applied.

Here, the terminal-to-base station control information (e.g., UCI) may be feedback information (e.g., HARQ-ACK), channel state information (e.g., CSI), and/or scheduling request (e.g., SR; scheduling request).

According to one embodiment of the present disclosure, assuming that a terminal performs terminal-to-base station communication data channel transmission (e.g., PUSCH transmission), a method may be provided in which the terminal repeatedly performs terminal-to-base station communication data channel transmission (e.g., PUSCH transmission) (in the time domain) and applies an orthogonal cover code (e.g., OCC) (in the time domain) between the repeated transmissions.

Here, the (time domain) orthogonal cover code (e.g., OCC) may be for the purpose of multiplexing one or more terminal-to-base station communication data channel transmissions (e.g., PUSCH transmissions) (within the same cell).

Here, if one or more repeated transmissions among the transmissions of the terminal-to-base station communication data channel repetition (e.g., PUSCH repetition) collide/overlap with the terminal-to-base station control channel (e.g., PUCCH) in the time domain, the terminal-to-base station control information (e.g., UCI) transmitted via the terminal-to-base station control channel (e.g., PUCCH) may be multiplexed within the terminal-to-base station physical shared channel (e.g., PUSCH). For example, the multiplexing may mean a piggybacking operation of the terminal-to-base station control information (e.g., UCI) on the terminal-to-base station physical shared channel (e.g., PUSCH) or the terminal-to-base station control information (e.g., UCI).

Here, when terminal-to-base station control information (e.g., UCI) is multiplexed within a resource group to which the orthogonal cover code (e.g., OCC) is applied, the terminal-to-base station control information (e.g., UCI) transmission may also be repeatedly transmitted within the group to which the orthogonal cover code (e.g., OCC) is applied.

Here, if the resource group to which the orthogonal cover code (e.g., OCC) is applied overlaps and/or collides (in the time domain) with two or more terminal-to-base station control channels (e.g., PUCCH) and/or terminal-to-base station control information (e.g., UCI), combining and repeatedly transmitting the multiple terminal-to-base station control information (e.g., UCI) may cause excessive feedback load from the perspective of terminal-to-base station control information (e.g., UCI) feedback.

Accordingly, in the present disclosure, when a terminal can apply an orthogonal cover code (e.g., OCC) between transmissions of terminal-to-base station communication data channel repetitions (e.g., PUSCH repetitions) (in the time domain) during terminal-to-base station communication data channel transmissions (e.g., PUSCH transmissions), a method is proposed in which a terminal supports one or more of the following operations when a resource group to which the orthogonal cover code (e.g., OCC) is applied overlaps and/or collides (in the time domain) with two or more terminal-to-base station control channels (e.g., PUCCH).

(1) Operations that do not expect overlap and/or collision between a (single) resource group to which an orthogonal cover code (e.g., OCC) is applied and two or more (different) terminal-to-base station control information (e.g., UCI) (e.g., the terminal may treat this as an error case when the above case occurs).

(2) When two or more (different) terminal-to-base station control information (e.g., UCI) overlap and/or collide with a (single) resource group to which an orthogonal cover code (e.g., OCC) is applied, an operation of selecting and multiplexing a single terminal-to-base station control information (e.g., UCI) according to one or more of the following terminal-to-base station control information (e.g., UCI) priority rules.

i) Terminal-to-base station control information (e.g., UCI) that is ahead in the time domain may have higher priority.

ii) Terminal-to-base station control information (e.g., UCI) with a large payload size may have a higher priority. Alternatively, terminal-to-base station control information (e.g., UCI) associated with more data transmission may have a higher priority.

iii) URLLC-related terminal-to-base station control information (e.g., UCI) may have a high priority. For example, terminal-to-base station control information (e.g., UCI) with a high priority index may have a high priority.

iv) Terminal-to-base station control information (e.g., UCI) related to a high number of retransmissions may have a high priority.

v) Terminal-to-base station control information (e.g., UCI) that has a scheduling point in time ahead of the relevant data may have a higher priority.

vi) Feedback transmission (e.g., HARQ-ACK transmission) may have a higher priority than channel state information (e.g., CSI) transmission.

vii) Beam reporting may have higher priority than channel quality information (e.g., CQI), precoding matrix indicator (e.g., PMI), and/or rank indicator (e.g., RI).

viii) The rank indicator (e.g., RI) may have higher priority than the channel quality information (e.g., CQI) and/or the precoding matrix indicator (e.g., PMI).

ix) Channel state information (e.g., CSI) related to process index with low (or high) channel state information (e.g., CSI) may have high priority.

x) Aperiodic terminal-to-base station control information (e.g., UCI) may have a higher priority than periodic terminal-to-base station control information (e.g., UCI).

xi) It can be implemented according to the terminal.

According to the above-described proposal of the present disclosure, there may be an advantage in that terminal-to-base station communication multiplexing rules (e.g., UL multiplexing rules) are supported when the terminal can apply an orthogonal cover code (e.g., OCC) between transmissions of terminal-to-base station communication data channel repetitions (e.g., PUSCH repetitions) (in the time domain) during terminal-to-base station communication data channel transmissions (e.g., PUSCH transmissions).

As a further proposal of the present disclosure, according to one embodiment of the present disclosure, when a terminal can apply an orthogonal cover code (e.g., OCC) between transmissions of terminal-to-base station communication data channel repetitions (e.g., PUSCH repetitions) (in time domain) during terminal-to-base station communication data channel transmissions (e.g., PUSCH transmissions), if a resource group to which the orthogonal cover code (e.g., OCC) is applied overlaps and/or collides (in time domain) with two or more terminal-to-base station control channels (e.g., PUCCH), a method is proposed in which the terminal supports terminal-to-base station control information (e.g., UCI) multiplexing in stages as follows.

(1) Step 1: Priority-based payload selection and/or payload multiplexing by terminal-to-base station control information (e.g., UCI) type.

(2) Step 2: Multiplexing coded symbols/bits for different terminal-to-base station control information (e.g., UCI) types within a resource group using an orthogonal cover code (e.g., OCC).

Here, the terminal-to-base station control information (e.g., UCI) type may include feedback information (e.g., HARQ-ACK), channel state information (e.g., CSI), and/or scheduling request (e.g., SR).

Here, multiplexing within a resource group to which the orthogonal cover code (e.g., OCC) is applied may include a process of repeatedly transmitting terminal-to-base station control information (e.g., UCI) within the resource group to which the orthogonal cover code (e.g., OCC) is applied.

Here, if there are two or more types of specific terminal-to-base station control information (e.g., UCI) (in case of collision), the terminal may skip transmission of (terminal-to-base station physical shared channel (e.g., PUSCH)) for the resource group to which the orthogonal cover code (e.g., OCC) is applied, and perform terminal-to-base station physical control channel transmission (e.g., PUCCH transmission). For example, the specific type of terminal-to-base station control information (e.g., UCI) may be feedback information (e.g., HARQ-ACK).

Here, whether to select a priority-based payload or perform payload multiplexing for each terminal-to-base station control information (e.g., UCI) type may depend on the settings of the base station (or network node).

The above [Proposal #06] may be applied in combination with other proposal(s) to the extent that the actions of the disclosure do not conflict.

[Proposal #07]

According to one embodiment of the present disclosure, when a terminal can apply an orthogonal cover code (e.g., OCC) between transmissions of terminal-to-base station communication data channel repetitions (e.g., PUSCH repetitions) (in the time domain) during terminal-to-base station communication data channel transmissions (e.g., PUSCH transmissions), a resource group to which the orthogonal cover code (e.g., OCC) is applied (hereinafter, a first orthogonal cover code (e.g., OCC) group) overlaps and/or collides (in the time domain) with one or more terminal-to-base station control channels (e.g., PUCCH), and a resource group to which the orthogonal cover code (e.g., OCC) is applied (hereinafter, a second orthogonal cover code (e.g., OCC) group) exists after the first orthogonal cover code (e.g., OCC) group, a method may be provided for the terminal to support one or more of the following operations.

(1) An operation of delaying transmission of some and/or all terminal-to-base station control information (e.g., UCI) within a terminal-to-base station physical control channel (e.g., PUCCH) and multiplexing it with a second orthogonal cover code (e.g., OCC) group (e.g., an operation of delaying transmission of some and/or all terminal-to-base station control information (e.g., UCI) so that it is multiplexed with the next orthogonal cover code (e.g., OCC) group rather than the overlapping orthogonal cover code (e.g., OCC) group).

Here, for example, the terminal operation may be applied when terminal-to-base station control information (e.g., UCI) multiplexing within the first orthogonal cover code (e.g., OCC) group is not supported. For example, the terminal operation may be applied when there is insufficient processing time for terminal-to-base station control information (e.g., UCI) multiplexing and/or terminal-to-base station control information (e.g., UCI) transmission must be skipped due to priority, etc.

Here, the second orthogonal cover code (e.g., OCC) group may be a resource group in which processing time (and/or timeline) for terminal-to-base station control information (e.g., UCI) multiplexing is guaranteed.

Here, the second orthogonal cover code (e.g., OCC) group may be a resource group that includes (at least) the delayed first terminal-to-base station control information (e.g., UCI) or includes only the delayed first terminal-to-base station control information (e.g., UCI).

Here, the terminal may delay transmission of the first terminal-to-base station control information (e.g., UCI) for a specific type of terminal-to-base station control information (e.g., UCI) (hereinafter, the first terminal-to-base station control information (e.g., UCI)), and select an orthogonal cover code (e.g., OCC) group that does not include (at least) the same type of terminal-to-base station control information (e.g., UCI) as the first terminal-to-base station control information (e.g., UCI) and/or does not include any terminal-to-base station control information (e.g., UCI) as a second orthogonal cover code (e.g., OCC) group, and multiplex the first terminal-to-base station control information (e.g., UCI) into the second orthogonal cover code (e.g., OCC) group.

Here, the terminal delays transmission of the first terminal-to-base station control information (e.g., UCI) for a specific type of terminal-to-base station control information (e.g., UCI) (hereinafter, the first terminal-to-base station control information (e.g., UCI)), and selects an orthogonal cover code (e.g., OCC) group that includes (at least) only terminal-to-base station control information (e.g., UCI) of the same type as the first terminal-to-base station control information (e.g., UCI) and/or includes (at least) only terminal-to-base station control information (e.g., UCI) of a type defined, set, and/or indicated in advance as a second orthogonal cover code (e.g., OCC) group, and transmits the first terminal-to-base station control information (e.g., UCI) to the second orthogonal cover code (e.g., OCC) group. It can be multiplexed (or multiplexed with a second orthogonal cover code (e.g., OCC) group).

Here, the terminal can selectively apply the operation according to the terminal-to-base station control information (e.g., UCI) type. For example, if the terminal-to-base station control information (e.g., UCI) includes feedback information (e.g., HARQ-ACK) and/or channel state information (e.g., CSI), the channel state information (e.g., CSI) can be multiplexed into a first orthogonal cover code (e.g., OCC) group, and the feedback information (e.g., HARQ-ACK) can be multiplexed into a first orthogonal cover code (e.g., OCC) group or a second orthogonal cover code (e.g., OCC) group depending on the processing time (and/or timeline).

Here, the terminal may omit the delayed terminal-to-base station control information (e.g., UCI) transmission if it fails to find a suitable second orthogonal cover code (e.g., OCC) group (for a certain period of time).

Here, when the terminal wants to multiplex the terminal-to-base station control information (e.g., UCI) to an orthogonal cover code (e.g., OCC) group (within an adjacent or predefined time interval) after delaying the terminal-to-base station control information (e.g., UCI), if the terminal-to-base station control information (e.g., UCI) is already included in the orthogonal cover code (e.g., OCC) group, the transmission of the delayed terminal-to-base station control information (e.g., UCI) can be omitted.

Here, when the terminal searches for the second orthogonal cover code (e.g., OCC) group, the terminal may utilize different grant and/or configuration-based terminal-to-base station physical shared channel (e.g., PUSCH) transmission resource(s). Alternatively, for example, when the terminal searches for the second orthogonal cover code (e.g., OCC) group, the search may be performed only within transmissions of the same terminal-to-base station physical shared channel repetition (e.g., PUSCH repetition) as the first orthogonal cover code (e.g., OCC) group.

Here, the above orthogonal cover code (e.g., OCC) group may mean a terminal-to-base station physical shared channel (e.g., PUSCH) resource group to which the orthogonal cover code (e.g., OCC) is applied.

The above [Proposal #07] may be applied in combination with other proposal(s) to the extent that the actions of the disclosure do not conflict.

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

The introduction of non-terrestrial networks (e.g., NTN) that utilize satellites as network nodes is being actively discussed. Satellites that support the above non-terrestrial networks (e.g., NTN) can be classified according to their flight orbits and characteristics, such as geostationary orbit satellites (e.g., GEO; geostationary orbit), medium Earth orbit (e.g., MEO; medium Earth orbit), and low Earth orbit (e.g., LEO; low Earth orbit), and generally have the characteristic of having very high satellite altitudes.

Accordingly, the service area of the satellite may have a very wide coverage characteristic, and the number of target terminals within the service area may be relatively large. Accordingly, the non-terrestrial network (e.g., NTN) service may require multiplexing support for multiple terminal(s).

Here, since terrestrial terminals have transmission power constraints, coverage extension techniques may need to be applied to ensure that signals of sufficient size reach high-altitude non-terrestrial networks (e.g., NTNs) during terminal-to-base station (e.g., UL) transmission. For example, terminals can achieve coverage extension by repeatedly transmitting the terminal-to-base station physical shared channel (e.g., PUSCH; Physical Uplink Shared Channel), which is a terminal-to-base station (e.g., UL) data channel, on the time axis.

Meanwhile, in the above coverage expansion technology, resource utilization efficiency may decrease due to repeated transmission, and to solve this, multiplexing of terminal-to-base station communication (e.g., UL communication) using an orthogonal cover code (e.g., OCC) may be effective.

According to one embodiment of the present disclosure, a method for achieving capacity increase and/or multiplexing of a base station-to-terminal physical shared channel (e.g., PUSCH) by applying an orthogonal cover code (e.g., OCC) during base station-to-terminal transmission (e.g., UL transmission) of a non-terrestrial network may be provided.

Here, in particular, the present disclosure may provide a method for omitting repetition of the entire base station-to-terminal physical shared channel (e.g., PUSCH) when applying an orthogonal cover code (e.g., OCC) between repeated transmissions of a base station-to-terminal physical shared channel (e.g., PUSCH), when transmission of terminal-to-base station control information (e.g., UCI) overlaps with transmission of some base station-to-terminal physical shared channel (e.g., PUSCH).

According to various embodiments of the present disclosure, in an environment where an orthogonal cover code is applied, transmission of important data can be protected by allowing terminal-to-base station control information, which may be more important than terminal-to-base station shared channel transmission, to be transmitted.

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

Referring to FIG. 10, in step S1010, a first device may obtain information on a plurality of device-to-base station physical shared channel resources related to device-to-base station physical shared channel repetition. In step S1020, the first device may obtain information related to an orthogonal cover code. For example, the plurality of device-to-base station physical shared channel resources may include at least one orthogonal cover code group to which the orthogonal cover code is applied. For example, based on an overlap between a first device-to-base station physical shared channel resource in a first orthogonal cover code group among the at least one orthogonal cover code group and a first device-to-base station physical control channel resource to which device-to-base station control information is to be transmitted, all device-to-base station physical shared channel transmissions based on the first orthogonal cover code group may be dropped.

For example, all device-to-base station physical shared channel transmissions based on the first orthogonal cover code group may be dropped based on a first time interval between the time at which the overlap is detected and the first start time of the earliest resource within the first orthogonal cover code group being less than the processing time.

For example, additionally, the first device may search for a second orthogonal cover code group in which a second time interval between the time at which the overlap is detected and the second start time of the earliest resource is greater than the processing time, based on the first time interval being less than the processing time. For example, all device-to-base station physical shared channel transmissions based on the first orthogonal cover code group may be dropped based on a failure in the search for the second orthogonal cover code group.

For example, additionally, the first device may determine the occurrence of an error case based on whether the first orthogonal cover code group overlaps with two or more device-to-base station physical control channel resources including the first device-to-base station physical control channel resource; and based on the determination of the occurrence of the error case, the first device-to-base station physical control channel resource may be selected from among the two or more device-to-base station physical control channel resources.

For example, additionally, the first device may transmit the device-to-base station control information to the base station via a device-to-base station physical control channel.

For example, transmissions on a device-to-base station physical control channel may not be repeated.

For example, information related to the orthogonal cover code can be received from a base station.

For example, the information related to the orthogonal cover code is information about a combination of orthogonal cover code-related parameters, and the information about the combination of orthogonal cover code-related parameters can be received through a state value of a time domain resource allocation field in base station-to-device control information.

For example, signals transmitted over the device-to-base station physical shared channel repetition may be identical.

For example, duplicate versions of signals transmitted over the device-to-base station physical shared channel repetition may be identical.

For example, the number of repetitions of the device-to-base station physical shared channel repetition may be an integer multiple of the length of the orthogonal cover code.

For example, the device-to-base station control information includes channel state information, and all device-to-base station physical shared channel transmissions based on the first orthogonal cover code group may be dropped based on the device-to-base station control information including channel state information and the overlap.

The above-described embodiment can be applied to various devices described below. First, the processor (102) of the first device (100) can obtain information on a plurality of device-to-base station physical shared channel resources related to device-to-base station physical shared channel repetition. In addition, the processor (102) of the first device (100) can obtain information related to an orthogonal cover code. For example, the plurality of device-to-base station physical shared channel resources can include at least one orthogonal cover code group to which the orthogonal cover code is applied. For example, based on an overlap between a first device-to-base station physical shared channel resource in a first orthogonal cover code group among the at least one orthogonal cover code group and a first device-to-base station physical control channel resource to which device-to-base station control information is to be transmitted, all device-to-base station physical shared channel transmissions based on the first orthogonal cover code group can be dropped.

According to one embodiment of the present disclosure, a first device may be provided. For example, the first device may include: at least one transceiver; at least one processor; and at least one memory coupled to the at least one processor and storing instructions. For example, the instructions, when executed by the at least one processor, cause the first device to: obtain information about a plurality of device-to-base station physical shared channel resources associated with a device-to-base station physical shared channel repetition; And obtain information related to orthogonal cover codes, wherein the plurality of device-to-base station physical shared channel resources include at least one orthogonal cover code group to which the orthogonal cover code is applied, and based on an overlap of a first device-to-base station physical shared channel resource in a first orthogonal cover code group among the at least one orthogonal cover code group and a first device-to-base station physical control channel resource to which device-to-base station control information is to be transmitted, all device-to-base station physical shared channel transmissions based on the first orthogonal cover code group can be dropped.

For example, all device-to-base station physical shared channel transmissions based on the first orthogonal cover code group may be dropped based on a first time interval between the time at which the overlap is detected and the first start time of the earliest resource within the first orthogonal cover code group being less than the processing time.

For example, additionally, the instructions may cause the first device to: search for a second orthogonal cover code group in which a second time interval between the time at which the overlap is detected and the second start time of the earliest resource is greater than the processing time, based on the first time interval being less than the processing time. For example, all device-to-base station physical shared channel transmissions based on the first orthogonal cover code group may be dropped based on a failure to search for the second orthogonal cover code group.

For example, additionally, the commands may cause the first device to: determine the occurrence of an error case based on whether the first orthogonal cover code group overlaps with two or more device-to-base station physical control channel resources including the first device-to-base station physical control channel resource; and select the first device-to-base station physical control channel resource from among the two or more device-to-base station physical control channel resources based on the determination of the occurrence of the error case.

For example, additionally, the commands may cause the first device to: transmit the device-to-base station control information to the base station via a device-to-base station physical control channel.

For example, transmissions on a device-to-base station physical control channel may not be repeated.

For example, information related to the orthogonal cover code can be received from a base station.

For example, the information related to the orthogonal cover code is information about a combination of orthogonal cover code-related parameters, and the information about the combination of orthogonal cover code-related parameters can be received through a state value of a time domain resource allocation field in base station-to-device control information.

For example, signals transmitted over the device-to-base station physical shared channel repetition may be identical.

For example, duplicate versions of signals transmitted over the device-to-base station physical shared channel repetition may be identical.

For example, the number of repetitions of the device-to-base station physical shared channel repetition may be an integer multiple of the length of the orthogonal cover code.

For example, the device-to-base station control information includes channel state information, and all device-to-base station physical shared channel transmissions based on the first orthogonal cover code group may be dropped based on the device-to-base station control information including channel state information and the overlap.

According to one embodiment of the present disclosure, a processing device configured to control a first device may be provided. For example, the processing device may include: at least one processor; and at least one memory coupled to the at least one processor and storing instructions. For example, the instructions, based on execution by the at least one processor, cause the first device to: obtain information about a plurality of device-to-base station physical shared channel resources associated with a device-to-base station physical shared channel repetition; And obtain information related to orthogonal cover codes, wherein the plurality of device-to-base station physical shared channel resources include at least one orthogonal cover code group to which the orthogonal cover code is applied, and based on an overlap of a first device-to-base station physical shared channel resource in a first orthogonal cover code group among the at least one orthogonal cover code group and a first device-to-base station physical control channel resource to which device-to-base station control information is to be transmitted, all device-to-base station physical shared channel transmissions based on the first orthogonal cover code group can be dropped.

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, cause a first device to: obtain information about a plurality of device-to-base station physical shared channel resources associated with a device-to-base station physical shared channel repetition; and obtain information associated with an orthogonal cover code, wherein the plurality of device-to-base station physical shared channel resources include at least one orthogonal cover code group to which the orthogonal cover code is applied, and based on an overlap between a first device-to-base station physical shared channel resource within a first orthogonal cover code group of the at least one orthogonal cover code group and a first device-to-base station physical control channel resource to which device-to-base station control information is to be transmitted, all device-to-base station physical shared channel transmissions based on the first orthogonal cover code group may be dropped.

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

Referring to FIG. 11, in step S1110, a second device may transmit to a first device information about a plurality of device-to-base station physical shared channel resources related to device-to-base station physical shared channel repetition. For example, the plurality of device-to-base station physical shared channel resources may include at least one orthogonal cover code group to which an orthogonal cover code is applied. In step S1120, the second device may receive device-to-base station control information from the first device based on a first device-to-base station physical control channel resource. For example, based on an overlap between a first device-to-base station physical shared channel resource within a first orthogonal cover code group among the at least one orthogonal cover code group and the first device-to-base station physical control channel resource, all device-to-base station physical shared channel transmissions based on the first orthogonal cover code group may be dropped.

For example, additionally, the second device may transmit information related to the orthogonal cover code to the first device.

The above-described embodiment can be applied to various devices described below. First, the processor (202) of the second device (200) can control the transceiver (206) to transmit information about a plurality of device-to-base station physical shared channel resources related to device-to-base station physical shared channel repetition to the first device (100). For example, the plurality of device-to-base station physical shared channel resources can include at least one orthogonal cover code group to which an orthogonal cover code is applied. In addition, the processor (202) of the second device (200) can control the transceiver (206) to receive device-to-base station control information based on the first device-to-base station physical control channel resource from the first device (100). For example, based on an overlap of a first device-to-base station physical shared channel resource within a first orthogonal cover code group among the at least one orthogonal cover code group and the first device-to-base station physical control channel resource, all device-to-base station physical shared channel transmissions based on the first orthogonal cover code group may be dropped.

According to one embodiment of the present disclosure, a second device may be provided. For example, the second device may include: at least one transceiver; at least one processor; and at least one memory coupled to the at least one processor and storing instructions. For example, the instructions, based on being executed by the at least one processor, cause the second device to: transmit to a first device information about a plurality of device-to-base station physical shared channel resources associated with a device-to-base station physical shared channel repetition, wherein the plurality of device-to-base station physical shared channel resources include at least one orthogonal cover code group to which an orthogonal cover code is applied; And receiving device-to-base station control information based on a first device-to-base station physical control channel resource from the first device, wherein based on an overlap of a first device-to-base station physical shared channel resource within a first orthogonal cover code group among the at least one orthogonal cover code group and the first device-to-base station physical control channel resource, all device-to-base station physical shared channel transmissions based on the first orthogonal cover code group can be dropped.

For example, the instructions, based on being executed by the at least one processor, may cause the second device to: transmit, to the first device, information related to the orthogonal cover code.

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

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

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.

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.

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

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

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

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).

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 base station-to-base station communication (150c) (e.g., relay, IAB (Integrated Access Backhaul). Through wireless communication/connection (150a, 150b, 150c), wireless devices and base stations/wireless devices, and base stations and base stations can transmit/receive wireless signals to 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.

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

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

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

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.

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.

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.

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.

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.

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) may 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 processed user data, control information, wireless signals/channels, etc. from baseband signals to RF band signals using one or more processors (102, 202). For this purpose, one or more transceivers (106, 206) may include an (analog) oscillator and/or a filter.

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

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

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

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.

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.

The signal processing process for receiving signals in a wireless device can be configured in reverse order of the signal processing process (1010 to 1060) of FIG. 14. For example, a wireless device (e.g., 100, 200 of FIG. 13) can receive wireless signals from the outside through an antenna port/transceiver. The received wireless signals can be converted into baseband signals through a signal restorer. For this purpose, the signal restorer can include a frequency downlink converter, an analog-to-digital converter (ADC), a CP remover, and a fast Fourier transform (FFT) module. Thereafter, the baseband signal can be restored to a codeword through a resource demapper process, a postcoding process, a demodulation process, and a descrambling process. The codewords can be restored to the original information blocks through decoding. Accordingly, a signal processing circuit (not shown) for a received signal may include a signal restorer, a resource de-mapper, a postcoder, a demodulator, a de-scrambler, and a decoder.

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

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

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

In FIG. 15, various elements, components, units/parts, and/or modules within the wireless device (100, 200) may be entirely interconnected via a wired interface, or at least some may be wirelessly connected via a communication unit (110). For example, within the wireless device (100, 200), the control unit (120) and the communication unit (110) may be wired, and the control unit (120) and the first unit (e.g., 130, 140) may be wirelessly connected via the communication unit (110). In addition, each element, component, unit/part, and/or module within the wireless device (100, 200) may further include one or more elements. For example, the control unit (120) may be composed of one or more processor sets. For example, the control unit (120) may be composed of a set of a communication control processor, an application processor, an electronic control unit (ECU), a graphics processing processor, a memory control processor, etc. As another example, the memory unit (130) may be composed of a random access memory (RAM), a dynamic RAM (DRAM), a read only memory (ROM), a flash memory, a volatile memory, a non-volatile memory, and/or a combination thereof.

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

FIG. 16 illustrates a mobile device according to an embodiment of the present disclosure. The mobile device may include a smartphone, a smart pad, a wearable device (e.g., a smartwatch, smartglasses), or a portable computer (e.g., a laptop, etc.). The mobile device may be referred to as a Mobile Station (MS), a User Terminal (UT), a Mobile Subscriber Station (MSS), a Subscriber Station (SS), an Advanced Mobile Station (AMS), or a Wireless Terminal (WT). The embodiment of FIG. 16 may be combined with various embodiments of the present disclosure.

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

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.

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).

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

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

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.

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.

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

Claims (20)

In terms of method, A step of obtaining information about a plurality of device-to-base station physical shared channel resources related to device-to-base station physical shared channel repetition; and Obtain information related to the orthogonal cover code, The step of comprising: wherein the plurality of device-to-base station physical shared channel resources include at least one orthogonal cover code group to which the orthogonal cover code is applied; A method wherein all device-to-base station physical shared channel transmissions based on the first orthogonal cover code group are dropped based on an overlap of a first device-to-base station physical shared channel resource and a first device-to-base station physical control channel resource on which device-to-base station control information is to be transmitted within a first orthogonal cover code group among at least one orthogonal cover code group. In the first paragraph, A method wherein all device-to-base station physical shared channel transmissions based on the first orthogonal cover code group are dropped based on a first time interval between the time at which the overlap is detected and the first start time of the earliest resource within the first orthogonal cover code group being less than the processing time. In the second paragraph, Further comprising a step of searching for a second orthogonal cover code group in which a second time interval between the time at which the overlap is detected and the second start time of the earliest resource is greater than the processing time, based on the first time interval being less than the processing time, A method wherein all device-to-base station physical shared channel transmissions based on the first orthogonal cover code group are dropped based on a failure in searching for the second orthogonal cover code group. In the first paragraph, A step of determining the occurrence of an error case based on the first orthogonal cover code group overlapping with two or more device-to-base station physical control channel resources including the first device-to-base station physical control channel resource; and A method further comprising the step of selecting the first device-to-base station physical control channel resource among the two or more device-to-base station physical control channel resources based on a determination of the occurrence of the above error case. In the first paragraph, A method further comprising the step of transmitting the device-to-base station control information to the base station via a device-to-base station physical control channel. In paragraph 5, A method in which transmission of a device-to-base station physical control channel is non-repetitive. In the first paragraph, A method in which information related to the above orthogonal cover code is received from a base station. In paragraph 7, The information related to the above orthogonal cover code is information about the combination of parameters related to the orthogonal cover code, and A method in which information on a combination of the above orthogonal cover code related parameters is received through a state value of a time domain resource allocation field in base station-to-device control information. In the first paragraph, The signals transmitted through the above device-to-base station physical shared channel repetition are the same, method. In the first paragraph, The duplicate versions of the signals transmitted via the above device-to-base station physical shared channel repetition are identical, method. In the first paragraph, A method wherein the number of repetitions of the above device-to-base station physical shared channel repetition is an integer multiple of the length of the above orthogonal cover code. In the first paragraph, The above device-to-base station control information includes channel state information, and A method wherein all device-to-base station physical shared channel transmissions based on the first orthogonal cover code group are dropped based on the device-to-base station control information including channel state information and the overlap. In the first paragraph, A method, wherein the above method is performed by a first device. In the first device, At least one transmitter/receiver; at least one processor; and At least one memory connected to the at least one processor and storing instructions, The above instructions, based on being executed by the at least one processor, cause the first device to: Obtain information about multiple device-to-base station physical shared channel resources associated with device-to-base station physical shared channel repetition; and Obtain information related to the orthogonal cover code, The above plurality of device-to-base station physical shared channel resources include at least one orthogonal cover code group to which the orthogonal cover code is applied, and A first device, wherein all device-to-base station physical shared channel transmissions based on the first orthogonal cover code group are dropped based on an overlap of a first device-to-base station physical shared channel resource and a first device-to-base station physical control channel resource on which device-to-base station control information is to be transmitted within a first orthogonal cover code group among at least one orthogonal cover code group. In a processing device set to control a first device, at least one processor; and At least one memory connected to the at least one processor and storing instructions, The above instructions, based on being executed by the at least one processor, cause the first device to: Obtain information about multiple device-to-base station physical shared channel resources associated with device-to-base station physical shared channel repetition; and Obtain information related to the orthogonal cover code, The above plurality of device-to-base station physical shared channel resources include at least one orthogonal cover code group to which the orthogonal cover code is applied, and A processing device, wherein all device-to-base station physical shared channel transmissions based on the first orthogonal cover code group are dropped based on an overlap of a first device-to-base station physical shared channel resource and a first device-to-base station physical control channel resource on which device-to-base station control information is to be transmitted within a first orthogonal cover code group among at least one orthogonal cover code group. A non-transitory computer-readable storage medium that records commands, The above commands, when executed, cause the first device to: Obtain information about multiple device-to-base station physical shared channel resources associated with device-to-base station physical shared channel repetition; and Obtain information related to the orthogonal cover code, The above plurality of device-to-base station physical shared channel resources include at least one orthogonal cover code group to which the orthogonal cover code is applied, and A non-transitory computer-readable storage medium, wherein all device-to-base station physical shared channel transmissions based on the first orthogonal cover code group are dropped based on an overlap of a first device-to-base station physical shared channel resource and a first device-to-base station physical control channel resource on which device-to-base station control information is to be transmitted within a first orthogonal cover code group among at least one orthogonal cover code group. In terms of method, Transmitting information about a plurality of device-to-base station physical shared channel resources related to device-to-base station physical shared channel repetition to the first device, A step in which the plurality of device-to-base station physical shared channel resources include at least one orthogonal cover code group to which an orthogonal cover code is applied; and A step of receiving device-to-base station control information based on a first device-to-base station physical control channel resource from the first device, A method wherein all device-to-base station physical shared channel transmissions based on the first orthogonal cover code group are dropped based on an overlap between a first device-to-base station physical shared channel resource and the first device-to-base station physical control channel resource within the first orthogonal cover code group among the at least one orthogonal cover code group. In paragraph 17, A method further comprising the step of transmitting information related to the orthogonal cover code to the first device. In the second device, At least one transmitter/receiver; at least one processor; and At least one memory connected to the at least one processor and storing instructions, The above instructions, based on being executed by the at least one processor, cause the second device to: Transmit information about a plurality of device-to-base station physical shared channel resources associated with a device-to-base station physical shared channel repetition to the first device, A step in which the plurality of device-to-base station physical shared channel resources include at least one orthogonal cover code group to which an orthogonal cover code is applied; and Receive device-to-base station control information based on the first device-to-base station physical control channel resource from the first device, A second device, wherein all device-to-base station physical shared channel transmissions based on the first orthogonal cover code group are dropped based on an overlap of a first device-to-base station physical shared channel resource and the first device-to-base station physical control channel resource within the first orthogonal cover code group among the at least one orthogonal cover code group. In paragraph 19, The above instructions, based on being executed by the at least one processor, cause the second device to: A second device that transmits information related to the orthogonal cover code to the first device.