WO2025234721A1 - Method and apparatus for selecting carrier of multi-carrier support terminal - Google Patents

Abstract

Provided are a method by which a first device performs wireless communication and an apparatus supporting same. The method may comprise the steps of: acquiring information related to a plurality of carriers including a first carrier; receiving, from a second device via a physical sidelink control channel (PSCCH), first sidelink control information (SCI) for scheduling a physical sidelink shared channel (PSSCH) and second SCI; receiving, from the second device via the PSSCH, the second SCI including information for a channel state information (CSI) request; and transmitting, to the second device, a medium access control (MAC) control element (CE) for CSI reporting. For example, the MAC CE for the CSI reporting may be transmitted on the first carrier on which the information for the CSI request has been received.

Description

Carrier selection method and device for a multi-carrier supporting terminal

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.

per device peak data rate 1 Tbps E2E latency 1 ms maximum spectral efficiency 100bps/Hz mobility support Up to 1000km/hr satellite integration Fully AI Fully autonomous vehicle Fully XR Fully haptic communication Fully

In one embodiment, a method for a first device to perform wireless communication is provided. The method may include: obtaining information related to a plurality of carriers including a first carrier; receiving, from a second device, a first SCI (sidelink control information) for scheduling a physical sidelink shared channel (PSSCH) and a second SCI (physical sidelink control channel) via a physical sidelink control channel (PSCCH); receiving, from the second device, a second SCI including information for a channel state information (CSI) request via the PSSCH; and transmitting, to the second device, a medium access control (MAC) control element (CE) for CSI reporting. For example, the MAC CE for CSI reporting may be transmitted on the first carrier on which information for the CSI request is received.

In one embodiment, a first device configured to perform wireless communication is provided. 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, may cause the first device to: obtain information related to a plurality of carriers including a first carrier; receive, from a second device, a first SCI (sidelink control information) for scheduling a physical sidelink shared channel (PSSCH) and a second SCI (sidelink control information) via a physical sidelink control channel (PSCCH); receive, from the second device, a second SCI including information for a channel state information (CSI) request via the PSSCH; and transmit a medium access control (MAC) control element (CE) for CSI reporting to the second device. For example, the MAC CE for the CSI report may be transmitted on the first carrier on which information for the CSI request is received.

In one embodiment, a processing device configured to control a first device is provided. The processing device includes at least one processor; and at least one memory coupled to the at least one processor and storing instructions, wherein the instructions, when executed by the at least one processor, cause the first device to: obtain information related to a plurality of carriers including a first carrier; receive, from a second device, a first SCI for scheduling a physical sidelink shared channel (PSSCH) and a second SCI (sidelink control information) via a physical sidelink control channel (PSCCH); receive, from the second device, a second SCI including information for a channel state information (CSI) request via the PSSCH; and transmit a medium access control (MAC) control element (CE) for CSI reporting to the second device. For example, the MAC CE for the CSI report may be transmitted on the first carrier on which information for the CSI request is received.

In one embodiment, a non-transitory computer-readable storage medium having instructions recorded thereon is provided. The instructions, when executed, may cause a first device to: obtain information related to a plurality of carriers including a first carrier; receive, from a second device, a first SCI (sidelink control information) for scheduling a physical sidelink shared channel (PSSCH) and a second SCI (sidelink control information) via a physical sidelink control channel (PSCCH); receive, from the second device, a second SCI (channel state information) including information for a CSI request via the PSSCH; and transmit a medium access control (MAC) control element (CE) for CSI reporting to the second device. For example, the MAC CE for CSI reporting may be transmitted on the first carrier on which information for the CSI request is received.

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 procedure for a terminal to perform V2X or SL communication according to a resource allocation mode, according to an embodiment of the present disclosure.

FIG. 7 illustrates three cast types according to one embodiment of the present disclosure.

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

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

FIG. 10 illustrates an example of a sensing operation according to one embodiment of the present disclosure.

FIG. 11 illustrates a carrier selection method according to one embodiment of the present disclosure.

FIG. 12 illustrates a carrier selection method for transmitting a CSI reporting MAC CE according to an embodiment of the present disclosure.

FIG. 13 illustrates a carrier selection method for transmitting IUC information MAC CE according to one embodiment of the present disclosure.

FIG. 14 illustrates a method for a first device to perform wireless communication according to one embodiment of the present disclosure.

FIG. 15 illustrates a method for a second device to perform wireless communication according to one embodiment of the present disclosure.

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

FIG. 17 illustrates a wireless device according to one embodiment of the present disclosure.

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

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

FIG. 20 illustrates a portable device according to one embodiment of the present disclosure.

FIG. 21 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 (i.e., 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’.

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) from a base station or a network. In the present disclosure, "setting or defining" may be interpreted as being preset to a device. 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 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, and some descriptions, functions, procedures, proposals, methods, and/or operations of the embodiments may be omitted.

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 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and/or operations of the embodiments may be omitted. 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 (e.g., between the physical layers of a first device and a second device) through a physical channel. For example, the physical channel can be modulated using an orthogonal frequency division multiplexing (OFDM) scheme, and time and frequency can be utilized as radio resources.

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 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and/or operations of the embodiments may be omitted.

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 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and/or operations of the embodiments may be omitted.

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.

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

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.

Meanwhile, in the present disclosure, the 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, etc. In the present disclosure, the 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, etc.

FIG. 6 illustrates a procedure for a terminal to perform V2X or SL communication according to a resource allocation mode, according to an embodiment of the present disclosure. The embodiment of FIG. 6 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and/or operations of the embodiments may be omitted.

Referring to (a) of FIG. 6, in resource allocation mode 1, the base station may schedule SL resources to be used by the terminal for SL transmission. For example, in step S600, the base station may transmit information related to SL resources and/or information related to UL resources to the first terminal. For example, the UL resources may include PUCCH resources and/or PUSCH resources. For example, the UL resources may be resources for reporting SL HARQ feedback to the base station.

For example, a first terminal may receive information related to a dynamic grant (DG) resource and/or information related to a configured grant (CG) resource from a base station. For example, a CG resource may include a CG type 1 resource or a CG type 2 resource. In this specification, a DG resource may be a resource that a base station configures/allocates to the first terminal via downlink control information (DCI). In this specification, a CG resource may be a (periodic) resource that a base station configures/allocates to the first terminal via DCI and/or an RRC message. For example, in the case of a CG type 1 resource, the base station may transmit an RRC message including information related to the CG resource to the first terminal. For example, in the case of a CG type 2 resource, the base station may transmit an RRC message including information related to the CG resource to the first terminal, and the base station may transmit a DCI related to activation or release of the CG resource to the first terminal.

In step S610, the first terminal may transmit a PSCCH (e.g., Sidelink Control Information (SCI) or 1st-stage SCI) to the second terminal based on the resource scheduling. In step S620, the first terminal may transmit a PSSCH (e.g., 2nd-stage SCI, MAC PDU, data, etc.) related to the PSCCH to the second terminal. In step S630, the first terminal may receive a PSFCH related to the PSCCH/PSSCH from the second terminal. For example, HARQ feedback information (e.g., NACK information or ACK information) may be received from the second terminal via the PSFCH. In step S640, the first terminal may transmit/report HARQ feedback information to the base station via a PUCCH or a PUSCH. For example, the HARQ feedback information reported to the base station may be information generated by the first terminal based on the HARQ feedback information received from the second terminal. For example, the HARQ feedback information reported to the base station may be information generated by the first terminal based on a rule set in advance. For example, the DCI may be DCI for scheduling SL.

Referring to (b) of FIG. 6, in resource allocation mode 2, the terminal can determine SL transmission resources within SL resources set by the base station/network or preset SL resources. For example, the set SL resources or preset SL resources may be a resource pool. For example, the terminal can autonomously select or schedule resources for SL transmission. For example, the terminal can perform SL communication by selecting resources by itself within the set resource pool. For example, the terminal can select resources by itself within a selection window by performing sensing and resource (re)selection procedures. For example, the sensing can be performed on a subchannel basis. For example, in step S610, the first terminal that has selected resources by itself within the resource pool can transmit a PSCCH (e.g., Sidelink Control Information (SCI) or 1 ^st -stage SCI) to the second terminal using the resources. In step S620, the first terminal may transmit a PSSCH (e.g., ^2nd- stage SCI, MAC PDU, data, etc.) related to the PSCCH to the second terminal. In step S630, the first terminal may receive a PSFCH related to the PSCCH/PSSCH from the second terminal.

Referring to (a) or (b) of FIG. 6, for example, a first terminal may transmit an SCI to a second terminal on a PSCCH. Or, for example, the first terminal may transmit two consecutive SCIs (e.g., 2-stage SCIs) to the second terminal on the PSCCH and/or the PSSCH. In this case, the second terminal may decode the two consecutive SCIs (e.g., 2-stage SCIs) to receive the PSSCH from the first terminal. In the present specification, an SCI transmitted on a PSCCH may be referred to as a 1 ^st SCI, a 1 ^st -stage SCI, or a 1 ^st -stage SCI format, and an SCI transmitted on a PSSCH may be referred to as a 2 ^nd SCI, a 2 nd SCI, a 2 ^nd -stage SCI, or a 2 ^nd -stage SCI format.

Referring to (a) or (b) of FIG. 6, in step S630, the first terminal may receive a PSFCH. For example, the first terminal and the second terminal may determine PSFCH resources, and the second terminal may use the PSFCH resources to transmit HARQ feedback to the first terminal.

Referring to (a) of FIG. 6, in step S640, the first terminal may transmit SL HARQ feedback to the base station via PUCCH and/or PUSCH.

FIG. 7 illustrates three cast types according to an embodiment of the present disclosure. The embodiment of FIG. 7 can be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and/or operations of the embodiments may be omitted. Specifically, (a) of FIG. 7 illustrates broadcast type SL communication, (b) of FIG. 7 illustrates unicast type SL communication, and (c) of FIG. 7 illustrates groupcast type SL communication. In the case of unicast type SL communication, a terminal can perform one-to-one communication with another terminal. In the case of groupcast type SL communication, a terminal can perform SL communication with one or more terminals within the group to which it belongs. In various embodiments of the present disclosure, SL groupcast communication can be replaced with SL multicast communication, SL one-to-many communication, etc.

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

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)

- 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. 9 illustrates an example of a communication scenario based on a 6G system, according to an embodiment of the present disclosure. The embodiment of FIG. 9 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and/or operations of the embodiments may be omitted.

Referring to FIG. 9, 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.

Below, the integrated sensing and communication (ISAC) mentioned above is described in detail.

Integrated Sensing and Communications (ISAC) 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 environment and/or the characteristics of objects within the environment. Because radio frequency sensing does not require a device to connect to the object through a network, it can provide services for object positioning without a device. The ability to obtain range, velocity, and angle information from radio frequency signals can enable a wide range of new capabilities, such as various object detection, object recognition (e.g., vehicles, humans, animals, UAVs), and high-precision localization, tracking, and activity recognition. Wireless sensing services can provide information to a variety of industries (e.g., unmanned aerial vehicles, smart homes, V2X, factories, railways, public safety, etc.), enabling applications such as intruder detection, assisted vehicle steering and navigation, trajectory tracking, collision avoidance, traffic management, and health and traffic management. In some cases, wireless sensing can utilize non-3GPP type sensors (e.g., radar, cameras) to further support 3GPP-based sensing. For example, the operation of a wireless sensing service (e.g., a sensing operation) may depend on the transmission, reflection, and scattering of wireless sensing signals. Therefore, wireless sensing may provide an opportunity to enhance existing communication systems from a communication network to a wireless communication and sensing network. FIG. 10 illustrates an example of a sensing operation according to an embodiment of the present disclosure. The embodiment of FIG. 10 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and/or operations of the embodiments may be omitted. Specifically, (a) of FIG. 10 illustrates an example of sensing using a sensing receiver and a sensing transmitter located at the same location (e.g., monostatic sensing), and (b) of FIG. 10 illustrates an example of sensing using a separated sensing receiver and a sensing transmitter (e.g., bistatic sensing).

Meanwhile, in conventional LTE V2X, a terminal supporting multi-channel operation (e.g., multi-carrier operation or carrier aggregation (CA)) can select a specific carrier for transmitting sidelink data, select available resources on the selected carrier, and transmit sidelink data through the selected resources and carrier.

In this disclosure, a carrier or resource reselection operation of a terminal supporting multi-carrier operation is proposed as follows.

[Proposal 1]

For example, when a transmitting terminal declares a sidelink RLF on a specific sidelink carrier (or one of the selected carriers, or all selected carriers, or all available carriers that have been configured) (e.g., when a discontinuous transmission (DTX) (e.g., an event in which a PSFCH for a PSCCH/PSSCH transmission is not received) occurs on a specific carrier for a preset threshold, the transmitting terminal may declare an RLF on that carrier), the transmitting terminal may trigger a carrier reselection procedure to replace the carrier on which the RLF occurred with another carrier. For example, when a sidelink RLF is declared on a specific sidelink carrier (or one of the selected carriers, or all selected carriers, or all available carriers that have been configured), a carrier reselection procedure may be triggered to reselect a new carrier. In addition, for example, resources being used or selected on the carrier on which the RLF occurred may be released and resources to be used on the new carrier may be reselected (e.g., the terminal may trigger resource reselection so that the newly reselected resources can be used on the newly selected carrier) so as to be mapped to the newly selected carrier. For example, a transmitting terminal can select a newly selected carrier and new resources to use on that carrier, and transmit sidelink data using the selected carrier and the selected resources.

[Proposal 2]

For example, when a transmitting terminal (e.g., a terminal supporting sidelink carrier aggregation (CA) operation and/or a terminal supporting sidelink unlicensed band operation) declares a (consistent or one shot) LBT failure on a specific sidelink carrier (or one of the selected carriers, or all selected carriers, or all configured available carriers), a carrier reselection procedure may be triggered to replace the carrier on which the (consistent or one shot) LBT failure occurred with another carrier. For example, when a transmitting terminal declares a sidelink (consistent or one shot) LBT failure on a specific sidelink carrier (or one of the selected carriers, or all selected carriers, or all configured available carriers), a carrier reselection procedure may be triggered to reselect a new carrier. Additionally, for example, resources being used or selected on a carrier where a (consistent or one-shot) LBT failure occurred can be released and resources to be used on a new carrier can be reselected (e.g., the UE can trigger resource reselection to use the newly reselected resources on the newly selected carrier) and mapped to the newly selected carrier. For example, the transmitting UE can select the newly selected carrier and new resources to be used on the newly selected carrier, and transmit sidelink data using the selected carrier and the selected resources.

[Proposal 3]

For example, when a terminal (e.g., a terminal supporting sidelink carrier aggregation (CA) operation and/or a terminal supporting sidelink FR2 operation) experiences a beam failure (e.g., when the MAC layer receives a beam failure instance from the PHY layer) on a specific sidelink carrier (or one of the selected carriers, or all selected carriers, or all configured available carriers) or a beam failure recovery procedure is triggered or the beam failure recovery procedure fails, the terminal may trigger a carrier reselection procedure to replace the carrier on which the beam failure occurred or the beam failure recovery procedure was triggered or the beam failure recovery procedure failed with another carrier. For example, if a beam failure occurs on a specific sidelink carrier (or on one of the selected carriers, or on all selected carriers, or on all available carriers that have been configured), or if a beam failure recovery procedure is triggered, or if the beam failure recovery procedure fails, a carrier reselection procedure may be triggered to reselect a new carrier. Additionally, for example, resources being used or selected on the carrier on which a beam failure occurs, or on which a beam failure recovery procedure is triggered, or on which a beam failure recovery procedure fails, may be released, and resources to be used on a new carrier may be reselected (e.g., the UE may trigger resource reselection to use the newly reselected resources on the newly selected carrier) and mapped to the newly selected carrier. For example, the UE may select the newly selected carrier and new resources to be used on the newly selected carrier, and may transmit and receive sidelink data using the selected carrier and the selected resources.

[Proposal 4]

For example, when a transmitting terminal declares a PC5 RRC reconfiguration failure on a specific sidelink carrier (or one of the selected carriers, or all selected carriers, or all available carriers that have been configured) (e.g., the terminal may declare a PC5 RRC Reconfiguration Failure if it transmits an RRCReconfigurationSidelink message on the corresponding sidelink carrier and does not receive an RRCReconfigurationCompleteSidelink message or an RRCReconfigurationFailureSidelink message until the T400 timer expires), it triggers a carrier reselection procedure to replace the carrier on which the PC5 RRC reconfiguration failure occurred with another carrier. For example, if a sidelink PC5 RRC reconfiguration failure is declared on a specific sidelink carrier (or on one of the selected carriers, or on all selected carriers, or on all available carriers that have been configured), a carrier reselection procedure may be triggered to reselect a new carrier. Additionally, for example, resources currently in use or selected on the carrier where the PC5 RRC reconfiguration failure occurred may be released, and resources to be used on the new carrier may be reselected (e.g., the UE may trigger resource reselection to use the newly reselected resources on the newly selected carrier) and mapped to the newly selected carrier. For example, a transmitting UE may select a newly selected carrier and new resources to be used on the newly selected carrier, and transmit sidelink data using the selected carrier and the selected resources.

[Proposal 5]

For example, when (re-)selection of a sidelink carrier/SL BWP/SL resource pool/SL HARQ entity is triggered during multi-carrier operation, a terminal (e.g., a transmitting terminal) may select a sidelink carrier/SL BWP/SL resource pool/SL HARQ entity in which sidelink data transmission is allowed, including a SL resource pool with a PSFCH configured, when HARQ feedback enabled data is available for a logical channel or when both HARQ feedback enabled data and HARQ feedback disabled data are available for a logical channel (e.g., where HARQ feedback enabled data and HARQ feedback disabled data can be mapped to the same sidelink unicast service or groupcast service or broadcast service), during sidelink data transmission and reception operation in multi-carrier. Only the (re-)selectable candidate sidelink carrier/SL BWP/SL resource pool/SL HARQ entity can be considered.

For example, if the CBR measurement value of all the sidelink data transmission-allowed sidelink carriers/SL BWPs/SL resource pools/SL HARQ entities that include the SL resource pools for which PSFCH is configured is higher than the CBR threshold for a pre-configured data-related priority (e.g., sidelink priority), the terminal may keep the existing selected sidelink carrier/SL BWP/SL resource pool/SL HARQ entity or (re-)select the sidelink carrier/SL BWP/SL resource pool/SL HARQ entity by converting the attribute of the data to HARQ feedback disabled.

In addition, for example, when the terminal transmits logical channel data or MAC CE or PC5 RRC message or PC5-S message or HARQ feedback enabled MAC PDU (or HARQ feedback enabled TB (transport block)) with HARQ feedback enabled, the terminal may (re-)select a sidelink carrier for transmitting logical channel data or MAC CE or PC5 RRC message or PC5-S message or HARQ feedback enabled MAC PDU (or HARQ feedback enabled TB (transport block)) with HARQ feedback enabled, as in the following procedure. For example, when the UE transmits HARQ feedback enabled logical channel data or MAC CE or PC5 RRC message or PC5-S message or HARQ feedback enabled MAC PDU (or HARQ feedback enabled transport block (TB)), if the CBR measurement value for the sidelink carrier(s) on which the PSFCH is configured (or the sidelink carrier(s) allowed to transmit the HARQ feedback enabled MAC PDU) or the sidelink carrier(s) associated with the sidelink resource pool(s) on which the PSFCH is configured is lower than the CBR threshold for the priority (e.g., sidelink priority) associated with the pre-configured data, the UE may (re-)select the sidelink carrier as the sidelink carrier for HARQ feedback enabled MAC PDU transmission. For example, if there are multiple sidelink carrier(s) with PSFCH configured (or sidelink carrier(s) allowed to transmit HARQ feedback enabled MAC PDUs) or sidelink resource pool(s) with PSFCH configured, among the sidelink carriers whose CBR measurements are lower than a CBR threshold for a predetermined data-related priority (e.g., sidelink priority), the sidelink carrier with the lowest measured CBR can be selected as the sidelink carrier for HARQ feedback enabled MAC PDU transmission. Alternatively, for example, if there are multiple sidelink carrier(s) with PSFCH configured (or sidelink carrier(s) allowed to transmit HARQ feedback enabled MAC PDUs) or sidelink resource pool(s) with PSFCH configured, it may be UE implementation-selectable which sidelink carrier among the sidelink carriers with CBR measurements lower than a CBR threshold for a pre-configured data-related priority (e.g., sidelink priority) is selected.

For example, a terminal may perform a carrier selection procedure in the following order to select a sidelink carrier for HARQ feedback enabled MAC PDU transmission.

1) Select sidelink carrier(s) that allow HARQ feedback enabled MAC PDU transmission.

2) Select the sidelink carrier(s) whose CBR measurement value is lower than the CBR threshold for the pre-configured data-related priority (e.g. sidelink priority).

3) If there are multiple sidelink carriers selected in the above-described processes 1) and 2), the sidelink carrier with the lowest measured CBR value is selected, or the UE selects the sidelink carrier through UE implementation.

[Proposal 6]

For example, in multi-carrier operation, if SL RLF is declared and sidelink carrier reselection is triggered, the terminal (e.g., transmitting terminal) may reselect sidelink carrier(s) to be used (preferentially) among the remaining sidelink carrier(s) excluding the sidelink carrier for which SL RLF is declared, and regenerate sidelink grants for the reselected sidelink carrier(s). However, for example, if the sidelink carrier for which SL RLF is declared is the only (remaining) sidelink carrier allowed to transmit the relevant packet/service, the terminal may not trigger both sidelink carrier reselection and sidelink grant regeneration. Alternatively, for example, if the sidelink carrier for which SL RLF is declared is the only (remaining) sidelink carrier allowed to transmit the relevant packet/service, the terminal may not trigger sidelink carrier reselection, but may trigger only sidelink grant regeneration to regenerate the sidelink grant.

[Proposal 7]

For example, when a multi-carrier capable terminal encounters an SL RLF in a unicast session or a PC5 RRC connection, the terminal may start a resource reuse timer and release resources being used by all sidelink carriers/SL BWPs/SL resource pools/SL HARQ entities associated with the PC5 RRC connection in which the SL RLF occurred. Additionally, for example, the terminal may stop (or cancel) the use of resources in use by all sidelink carriers/SL BWPs/SL resource pools/SL HARQ entities associated with the PC5 RRC connection in which the SL RLF occurred or resources reserved based on all sidelink carriers/SL BWPs/SL resource pools/SL HARQ entities associated with the PC5 RRC connection in which the SL RLF occurred while the resource reuse timer is running, or stop the resource selection operation based on all sidelink carriers/SL BWPs/SL resource pools/SL HARQ entities associated with the PC5 RRC connection in which the SL RLF occurred. For example, when the resource reuse timer expires, the UE may resume using resources that are in use by all sidelink carriers/SL BWPs/SL resource pools/SL HARQ entities associated with the PC5 RRC connection where the SL RLF occurred or reserved based on all sidelink carriers/SL BWPs/SL resource pools/SL HARQ entities associated with the PC5 RRC connection where the SL RLF occurred, or restart resource (re-)selection operations based on all sidelink carriers/SL BWPs/SL resource pools/SL HARQ entities associated with the PC5 RRC connection.

Alternatively, for example, when a SL RLF occurs in a unicast session or a PC5 RRC connection, a multi-carrier capable terminal may start a resource reuse timer and cancel (or exclude) the use of resources being used by a specific sidelink carrier/SL BWP/SL resource pool/SL HARQ entity associated with the PC5 RRC connection in which the SL RLF occurred (e.g., a specific sidelink carrier/SL BWP/SL resource pool/SL HARQ entity in which a threshold amount of DTX occurs among multiple sidelink carriers/SL BWP/SL resource pools/SL HARQ entities associated with the PC5 RRC connection). Additionally, for example, the UE may stop (or cancel, or exclude) the use of resources in use by a specific sidelink carrier/SL BWP/SL resource pool/SL HARQ entity associated with a PC5 RRC connection in which an SL RLF occurred while the resource reuse timer is running, or reserve resources based on a specific sidelink carrier/SL BWP/SL resource pool/SL HARQ entity associated with a PC5 RRC connection in which an SL RLF occurred, or stop resource selection operation based on a specific sidelink carrier/SL BWP/SL resource pool/SL HARQ entity associated with a PC5 RRC connection in which an SL RLF occurred. For example, when the resource reuse timer expires, the UE may resume using resources that are in use by a specific sidelink carrier/SL BWP/SL resource pool/SL HARQ entity associated with the PC5 RRC connection where the SL RLF occurred or reserved based on a specific sidelink carrier/SL BWP/SL resource pool/SL HARQ entity associated with the PC5 RRC connection where the SL RLF occurred, or may restart a resource (re-)selection operation based on a specific sidelink carrier/SL BWP/SL resource pool/SL HARQ entity associated with the PC5 RRC connection.

Or, for example, when a multi-carrier supporting terminal encounters an SL RLF in a unicast session or a PC5 RRC connection, the terminal may exclude resources being used by a specific sidelink carrier/SL BWP/SL resource pool/SL HARQ entity associated with the PC5 RRC connection where the SL RLF occurred (e.g., a specific sidelink carrier/SL BWP/SL resource pool/SL HARQ entity among multiple sidelink carriers/SL BWPs/SL resource pools/SL HARQ entities associated with the PC5 RRC connection where DTX occurred as many as the threshold amount) (or may exclude a resource (re-)selection operation based on a specific sidelink carrier/SL BWP/SL resource pool/SL HARQ entity where DTX occurred as many as the threshold amount), and may select a specific sidelink associated with the PC5 RRC connection (where the SL RLF occurred). Resources from a carrier/SL BWP/SL resource pool/SL HARQ entity (e.g., a specific sidelink carrier/SL BWP/SL resource pool/SL HARQ entity among multiple sidelink carriers/SL BWP/SL resource pools/SL HARQ entities associated with a PC5 RRC connection for which DTX has not occurred as much as a threshold) can be used (or a resource (re-)selection operation based on a specific sidelink carrier/SL BWP/SL resource pool/SL HARQ entity for which DTX has not occurred as much as a threshold) is performed.

For example, the number of DTX thresholds can be set differently depending on the sidelink priority or sidelink reliability or QoS profile or CBR or PQI or LCH or sidelink carrier/SL BWP/SL resource pool/SL HARQ entity.

Meanwhile, according to the prior art, in a multi-carrier (or, carrier aggregation (CA)) operation, when transmitting logical channel data, the Tx UE can measure the channel busy ratio (CBR) for one or more resource pools included in each of a plurality of carriers, determine a carrier with a CBR lower than a CBR threshold associated with the priority of the logical channel among the plurality of carriers as a candidate carrier, and select a carrier with the lowest CBR among one or more carriers included in the candidate carriers as a carrier for transmitting the logical channel data. However, a carrier selection procedure for transmitting MAC CE is not defined. For example, in the case of MAC CE, since there is no CBR threshold mapped to a priority associated with MAC CE, a carrier for transmitting MAC CE cannot be selected based on the carrier selection procedure for transmitting the above-described logical channel data (e.g., a carrier selection procedure based on CBR measurement and/or CBR check).

In addition, for example, in case of MAC CE related to CSI (channel state information) (or MAC CE related to IUC (inter-UE coordination)), a UE that receives a CSI request (or IUC request) transmitted by a UE that triggers CSI (or IUC information) must generate a CSI reporting MAC CE (or IUC information MAC CE) and transmit the CSI reporting MAC CE (or IUC information MAC CE) to the UE that triggered CSI (or IUC information) before a timer (e.g., sl-CSI-ReportTimer or sl-IUC-ReportTimer) expires. However, for example, when selecting a carrier for the CSI reporting MAC CE or a carrier for the IUC information MAC CE based on a carrier selection procedure for transmitting the above-described logical channel data (e.g., a carrier selection procedure based on CBR measurement and/or CBR check), the timer (e.g., sl-CSI-ReportTimer or sl-IUC-ReportTimer) may not be satisfied due to the performance of the CBR measurement procedure and the CBR check procedure for each of the plurality of carriers. For example, due to the CBR measurement and check procedures for each of the plurality of carriers, there may be a high possibility that the generation and transmission of the CSI reporting MAC CE or the IUC information MAC CE may not be completed before the timer (e.g., sl-CSI-ReportTimer or sl-IUC-ReportTimer) expires.

In addition, for example, if all CBR measurements for each of one or more resource pools included in a carrier exceed the CBR threshold, the carrier cannot be selected according to the prior art, and thus transmission of MAC CEs that should be transmitted preferentially (e.g., priority: 1 (highest priority) of CSI reporting MAC CE, or priority: 1 (highest priority) of IUC information MAC CE) may not be guaranteed.

In the present disclosure, a carrier selection method for MAC CE transmission of a multi-carrier supporting terminal and a device supporting the same are proposed as follows.

For example, Tx carrier (re)selection may be as follows:

For example, a MAC entity may consider the CBR (channel busy ratio) measured by a lower layer according to TS 38.215 as the carrier's CBR if the CBR measurement result is available, or may consider the corresponding sl-defaultTxConfigIndex set by the upper layer as the CBR if the CBR measurement result is not available.

For example, the SL-CSI (channel state information) reporting MAC CE can only be transmitted on the carrier on which the SL-CSI request was received.

For example, if Tx carrier (re)selection is triggered for a sidelink process according to clause 5.22.1.1, 5.22.1.2, or 5.22.1.3.3 of TS 38.321, the MAC entity may:

1> If there is no selected sidelink grant on any carrier for which data is available for the sidelink logical channel and MAC CE as indicated by the higher layers (TS 38.331 and TS 23.287):

2> For each carrier configured at the upper layer associated with the corresponding sidelink logical channel:

3> If the carrier's CBR is lower than sl-threshCBR-FreqReselection, which is related to the priority of the sidelink logical channel:

Note: When multiple resource pools are configured for a carrier, which resource pool is used to determine the CBR for that carrier can be determined by the UE implementation, taking into account sl-HARQ-FeedbackEnabled of the sidelink logical channel.

4> The carrier may be considered as a candidate carrier for Tx carrier (re)selection for the corresponding sidelink logical channel and/or MAC CE.

1> If not:

2> For each sidelink logical channel or MAC CE allowed on a carrier where data is available, or SL-CSI reporting is triggered, or SL DRX command indication is triggered, or SL inter-UE coordination (IUC) information reporting is triggered, or SL IUC request is triggered, and Tx carrier (re)selection is triggered according to clause 5.22.1.1, if the CBR of that carrier is lower than sl-threshCBR-FreqKeeping associated with the priority of the sidelink logical channel:

3> You can select the carrier and its associated pool of resources.

2> If not:

3> For each carrier configured by the upper layer that allows sidelink logical channels or MAC CEs, if the CBR of that carrier is lower than sl-threshCBR-FreqReselection associated with the priority of the sidelink logical channel:

4> For each carrier configured by the upper layer that allows sidelink logical channels or MAC CEs, that carrier can be considered a candidate carrier for Tx carrier (re)selection.

For example, a MAC entity can:

1> If more than one carrier is considered as a candidate carrier for Tx carrier (re)selection:

2> When Tx carrier (re)selection is triggered, for each logical channel on which data is allowed on the available carrier:

3> One or more carriers can be selected from among the candidate carriers in order of increasing CBR, starting with the lowest CBR, and an associated pool(s) of resources can be selected.

4> If sl-HARQ-FeedbackEnabled is set to enabled for the sidelink logical channel:

5> One resource pool with PSFCH resources set can be selected from among the resource pools excluding the pools in sl-BWP-DiscPoolConfig or sl-BWP-DiscPoolConfigCommon (if set).

4> If not:

5> You can select any pool of resources except the pools set in sl-BWP-DiscPoolConfig or sl-BWP-DiscPoolConfigCommon.

2> When Tx carrier (re)selection is triggered for SL-CSI reporting, or SL DRX command indication, or SL inter-UE coordination information reporting, or SL inter-UE coordination request:

3> One or more carriers can be selected in order of increasing CBR from the lowest CBR among the candidate carriers, and any pool of resources can be selected from the resource pools.

Note: How many carriers are selected based on UE capability depends on the UE implementation.

NOTE: It is up to the UE implementation to determine which sidelink logical channels are allowed on the carrier where data is available and Tx carrier (re)selection is triggered.

Note: It is up to the UE implementation whether the resource pool for CBR measurements is reused as the resource pool for SL grant creation.

Or, for example, Tx carrier (re)selection could be as follows:

For example, a MAC entity may consider the CBR (channel busy ratio) measured by a lower layer according to TS 38.215 as the carrier's CBR if the CBR measurement result is available, or may consider the corresponding sl-defaultTxConfigIndex set by the upper layer as the CBR if the CBR measurement result is not available.

For example, the SL-CSI (channel state information) reporting MAC CE can only be transmitted on the carrier on which the SL-CSI request was received.

For example, 1) for SL IUC (inter-UE coordination) request MAC CE transmission, the MAC entity can select a TX pool of resources that require an IUC resource set. And, for example, the MAC entity can determine a carrier to which the TX pool selected in 1) above belongs as a carrier for SL IUC (inter-UE coordination) request MAC CE transmission. For example, if there are multiple carriers to which the TX pool selected in 1) above belongs, the MAC entity can select a carrier with the best CBR measurement result (e.g., a carrier with the lowest CBR measurement value among carriers with CBR measurement values less than or equal to a CBR threshold) as a carrier for SL IUC (inter-UE coordination) request MAC CE transmission. Alternatively, for example, if there are multiple carriers to which the TX pool selected in 1) above belongs, the MAC entity may randomly select one carrier from among the multiple carriers as the carrier for SL IUC (inter-UE coordination) request MAC CE transmission. Alternatively, for example, if there are multiple carriers to which the TX pool selected in 1) above belongs, the MAC entity may leave the decision on the carrier for SL IUC (inter-UE coordination) request MAC CE transmission to the UE implementation.

For example, in order to transmit SL IUC (inter-UE coordination) information MAC CE, 2) the MAC entity can select a TX pool of resources where an IUC resource set is located. And, for example, the MAC entity can determine a carrier to which the TX pool selected in 2) belongs as a carrier for transmitting SL IUC (inter-UE coordination) information MAC CE. For example, if there are multiple carriers to which the TX pool selected in 2) belongs, the MAC entity can select a carrier with the best CBR measurement result (e.g., a carrier with the lowest CBR measurement value among carriers with CBR measurement values less than or equal to a CBR threshold) as a carrier for transmitting SL IUC (inter-UE coordination) information MAC CE. Or, for example, if there are multiple carriers to which the TX pool selected in 2) above belongs, the MAC entity may randomly select one carrier from among the multiple carriers as the carrier for transmitting the SL IUC (inter-UE coordination) information MAC CE. Or, for example, if there are multiple carriers to which the TX pool selected in 2) above belongs, the MAC entity may leave the determination of the carrier for transmitting the SL IUC (inter-UE coordination) information MAC CE to the UE implementation. Or, for example, the MAC entity may determine the carrier on which the SL IUC (inter-UE coordination) request MAC CE is received as the carrier for transmitting the SL IUC (inter-UE coordination) information MAC CE.

Or, for example, it could be:

For example, if Tx carrier (re)selection is triggered for a sidelink process according to clause 5.22.1.1, 5.22.1.2, or 5.22.1.3.3 of TS 38.321, the MAC entity may:

1> If there is no selected sidelink grant on any carrier for which data is available for the sidelink logical channel and MAC CE as indicated by the higher layers (TS 38.331 and TS 23.287):

2> For each carrier configured at the upper layer associated with the corresponding sidelink logical channel:

3> If the carrier's CBR is lower than sl-threshCBR-FreqReselection, which is related to the priority of the sidelink logical channel:

Note: When multiple resource pools are configured for a carrier, which resource pool is used to determine the CBR for that carrier can be determined by the UE implementation, taking into account sl-HARQ-FeedbackEnabled of the sidelink logical channel.

4> The carrier may be considered as a candidate carrier for Tx carrier (re)selection for the corresponding sidelink logical channel and/or MAC CE.

1> If not:

2> For each sidelink logical channel or MAC CE allowed on a carrier where data or MAC CE (e.g., SL-CSI reporting MAC CE, SL DRX command MAC CE, SL inter-UE coordination request MAC CE, SL inter-UE coordination information MAC CE) is available and Tx carrier (re)selection is triggered according to clause 5.22.1.1, if the CBR of that carrier is lower than sl-threshCBR-FreqKeeping associated with the priority of the sidelink logical channel:

3> You can select the carrier and its associated pool of resources.

2> If not:

3> For each carrier configured by the upper layer that allows sidelink logical channels or MAC CEs, if the CBR of that carrier is lower than sl-threshCBR-FreqReselection associated with the priority of the sidelink logical channel:

4> For each carrier configured by the upper layer that allows sidelink logical channels or MAC CEs, that carrier can be considered a candidate carrier for Tx carrier (re)selection.

For example, a MAC entity can:

1> If more than one carrier is considered as a candidate carrier for Tx carrier (re)selection:

2> When Tx carrier (re)selection is triggered, for each logical channel on which data is allowed on the available carrier:

3> One or more carriers can be selected from among the candidate carriers in order of increasing CBR, starting with the lowest CBR, and an associated pool(s) of resources can be selected.

4> If sl-HARQ-FeedbackEnabled is set to enabled for the sidelink logical channel:

5> One resource pool with PSFCH resources set can be selected from among the resource pools excluding the pools in sl-BWP-DiscPoolConfig or sl-BWP-DiscPoolConfigCommon (if set).

4> Otherwise:

5> You can select any pool of resources except the pools set in sl-BWP-DiscPoolConfig or sl-BWP-DiscPoolConfigCommon.

2> When Tx carrier (re)selection is triggered for SL MAC CE (e.g. SL DRX command indication):

3> One or more carriers can be selected in order of increasing CBR from the lowest CBR among the candidate carriers, and any pool of resources can be selected from the resource pools.

Note: How many carriers are selected based on UE capability depends on the UE implementation.

NOTE: It is up to the UE implementation to determine which sidelink logical channels are allowed on the carrier where data is available and Tx carrier (re)selection is triggered.

Note: It is up to the UE implementation whether the resource pool for CBR measurements is reused as the resource pool for SL grant creation.

Or, for example, Tx carrier (re)selection could be as follows:

For example, a MAC entity may consider the CBR (channel busy ratio) measured by a lower layer according to TS 38.215 as the carrier's CBR if the CBR measurement result is available, or may consider the corresponding sl-defaultTxConfigIndex set by the upper layer as the CBR if the CBR measurement result is not available.

For example, the SL-CSI (channel state information) reporting MAC CE can only be transmitted on the carrier on which the SL-CSI request was received.

For example, for SL IUC (inter-UE coordination) request MAC CE transmission, the MAC entity can select a TX pool of resources that require an IUC resource set. For example, for SL IUC (inter-UE coordination) information MAC CE transmission, the MAC entity can select a TX pool of resources that have an IUC resource set.

For example, if Tx carrier (re)selection is triggered for a sidelink process according to clause 5.22.1.1, 5.22.1.2, or 5.22.1.3.3 of TS 38.321, the MAC entity may:

1> If there is no selected sidelink grant on any carrier for which data is available for the sidelink logical channels and MAC CEs (e.g., SL-CSI reporting MAC CE, SL DRX command MAC CE, SL inter-UE coordination (IUC) request MAC CE, SL inter-UE coordination (IUC) information MAC CE) as indicated by higher layers (TS 38.331 and TS 23.287):

2> For each carrier configured at the upper layer associated with the corresponding sidelink logical channel:

3> If the carrier's CBR is lower than sl-threshCBR-FreqReselection, which is related to the priority of the sidelink logical channel:

Note: When multiple resource pools are configured for a carrier, which resource pool is used to determine the CBR for that carrier can be determined by the UE implementation, taking into account sl-HARQ-FeedbackEnabled of the sidelink logical channel.

4> The carrier may be considered as a candidate carrier for Tx carrier (re)selection for the corresponding sidelink logical channel and/or MAC CE.

1> If not:

2> For each sidelink logical channel or MAC CE allowed on a carrier where data or MAC CE (e.g., SL-CSI reporting MAC CE, SL DRX command MAC CE, SL inter-UE coordination request MAC CE, SL inter-UE coordination information MAC CE) is available and Tx carrier (re)selection is triggered according to clause 5.22.1.1, if the CBR of that carrier is lower than sl-threshCBR-FreqKeeping associated with the priority of the sidelink logical channel:

3> You can select the carrier and its associated pool of resources.

2> If not:

3> For each carrier configured by the upper layer that allows sidelink logical channels or MAC CEs, if the CBR of that carrier is lower than sl-threshCBR-FreqReselection associated with the priority of the sidelink logical channel:

4> For each carrier configured by the upper layer that allows sidelink logical channels or MAC CEs, that carrier can be considered a candidate carrier for Tx carrier (re)selection.

For example, a MAC entity can:

1> If more than one carrier is considered as a candidate carrier for Tx carrier (re)selection:

2> When Tx carrier (re)selection is triggered, for each logical channel on which data is allowed on the available carrier:

3> One or more carriers can be selected from among the candidate carriers in order of increasing CBR, starting with the lowest CBR, and an associated pool(s) of resources can be selected.

4> If sl-HARQ-FeedbackEnabled is set to enabled for the sidelink logical channel:

5> One resource pool with PSFCH resources set can be selected from among the resource pools excluding the pools in sl-BWP-DiscPoolConfig or sl-BWP-DiscPoolConfigCommon (if set).

4> If not:

5> You can select any pool of resources except the pools set in sl-BWP-DiscPoolConfig or sl-BWP-DiscPoolConfigCommon.

2> When Tx carrier (re)selection is triggered for SL MAC CE (e.g., SL-CSI reporting MAC CE, SL DRX command MAC CE, SL inter-UE coordination request MAC CE, SL inter-UE coordination information MAC CE):

3> One or more carriers can be selected from among the candidate carriers in order of increasing CBR, starting from the lowest CBR, and any pool of resources can be selected from among the resource pools.

3> The TX pool for SL IUC (inter-UE coordination) request MAC CE transmission can be selected as a resource pool (e.g., TX pool) that requires an IUC resource set among the resource pools belonging to the selected carrier.

3> The TX pool for transmitting SL IUC (inter-UE coordination) information MAC CE can be selected as a resource pool (e.g., TX pool) in which an IUC resource set (e.g., a preferred resource set recommended in IUC (inter-UE coordination) information MAC CE) is located among the resource pools belonging to the selected carrier.

Note: How many carriers are selected based on UE capability depends on the UE implementation.

NOTE: It is up to the UE implementation to determine which sidelink logical channels are allowed on the carrier where data is available and Tx carrier (re)selection is triggered.

Note: It is up to the UE implementation whether the resource pool for CBR measurements is reused as the resource pool for SL grant creation.

Meanwhile, in legacy single carrier operation, as shown below, the UE may generate an SL grant for SL CSI reporting MAC CE transmission when SL CSI reporting MAC CE transmission is triggered and there are no SL-SCH resources that can accommodate the SL CSI reporting MAC CE.

For example, SL grant reception and SCI transmission are as follows (Section 5.22.1.1 of TS 38.321).

1> When the MAC entity chooses to generate a selected sidelink grant corresponding to a single MAC PDU transmission, and SL data is available on the logical channel, or SL-CSI reporting is triggered, or SL DRX command indication is triggered, or SL IUC information reporting is triggered, or SL IUC request is triggered; or

1> If the MAC entity chooses to generate a selected sidelink grant corresponding to a single SL-PRS transmission triggered by the reception of SCI from an upper layer or a peer UE:

2> When a single carrier frequency is set:

3> When SL-CSI reporting, or SL DRX command, or SL IUC request, or SL IUC information is triggered:

4> You can select a resource pool from among the resource pools excluding the pools set in sl-BWP-DiscPoolConfig, sl-BWP-DiscPoolConfigCommon, sl-BWP-PoolConfigA2X or sl-BWP-PoolConfigCommonA2X or the SL-PRS dedicated resource pool (if set).

2> As specified in Section 5.22.1.2, a TX resource (re)selection check can be performed for the selected resource pool.

2> If TX resource (re)selection is triggered as a result of the TX resource (re)selection check

3> If the selected resource pool is not a SL-PRS dedicated resource pool:

4> The number of HARQ retransmissions may be selected from the allowed number in sl-MaxTxTransNumPSSCH contained in sl-PSSCH-TxConfigList (if configured by RRC), and from the values overlapping sl-MaxTxTransNumPSSCH indicated in sl-CBR-PriorityTxConfigList for the highest priority logical channel and pending SL-PRS transmissions (if configured by RRC), and may be selected according to the CBR measured at lower layers, if available and allowed by the carrier and if CBR measurement results are available according to clause 5.1.27 of TS 38.215, or if CBR measurement results are not available, the corresponding sl-defaultTxConfigIndex configured by RRC, or if partial sensing is selected and CBR measurement results are not available, the corresponding sl-DefaultCBR-PartialSensing configured by RRC. In case sl-TxPoolExceptional is not used, random selection is selected and if CBR measurement results are not available, the corresponding sl-DefaultCBR-RandomSelection set by RRC may be selected.

NOTE: As specified in clause 8.1.4 of TS 38.214, for multi-consecutive slots transmission, it is up to the UE implementation whether the number of HARQ retransmissions is counted from the allowed number based on the number of MCSt transmissions during resource (re)selection or based on the number of slots within the multi-consecutive slots transmission.

4> (if configured by the RRC) may select an amount of frequency resources within the range between sl-MinSubChannelNumPSSCH and sl-MaxSubChannelNumPSSCH contained in the sl-PSSCH-TxConfigList, and (if configured by the RRC) may select from overlapping values between sl-MinSubChannelNumPSSCH and sl-MaxSubChannelNumPSSCH indicated in the sl-CBR-PriorityTxConfigList for the highest priority logical channel and pending SL-PRS transmissions, and may select according to the CBR measured at the lower layer, if available and allowed by the carrier and if CBR measurement results are available according to clause 5.1.27 of TS 38.215, or may select the corresponding sl-defaultTxConfigIndex configured by the RRC if CBR measurement results are not available, or partial sensing is selected and If the CBR measurement result is not available, the corresponding sl-DefaultCBR-PartialSensing set by RRC can be selected, or if sl-TxPoolExceptional is not used, random selection can be selected and if the CBR measurement result is not available, the corresponding sl-DefaultCBR-RandomSelection set by RRC can be selected.

3> If sl-InterUE-CoordinationScheme1, which enables reception/transmission of preferred resource sets and non-preferred resource sets, is not configured by RRC:

4> If transmission based on random selection is set in the upper layer:

5> If the selected resource pool is not a SL-PRS dedicated resource pool:

6> (If configured) The time and frequency resources for a transmission opportunity may be randomly selected from the pool of resources that occurred within the SL DRX active time as specified in Section 5.28.2 of the selected destination UE to indicate the SL DRX active time to the physical layer, and from the pool in which sidelink consistent LBT failures were detected and not canceled in all RB sets (if configured), based on the amount of frequency resources selected, the remaining PDB of SL data available to the logical channel(s), and the remaining SL-PRS delay budget of SL-PRS transmissions (if available), whether allowed on the carrier, and the latency requirement of the triggered SL-CSI report (request).

However, as shown below, the MAC specification only specifies the carrier selection procedure for logical channel data.

For example, TX carrier (re)selection is as follows (clause 5.22.1.11 of TS 38.321):

For example, if a MAC entity has a CBR measurement result, it may consider the CBR measured by the lower layer according to TS 38.215 as the carrier's CBR, or if there is no CBR measurement result, it may consider the corresponding sl-defaultTxConfigIndex set by the upper layer as the carrier's CBR.

For example, if Tx carrier (re)selection is triggered for a sidelink process according to clause 5.22.1.1, 5.22.1.2, or 5.22.1.3.3 of TS 38.321, the MAC entity may:

1> If there is no selected sidelink grant on any carrier allowed on the data-available sidelink logical channel, as directed by the higher layers (TS 38.331 and TS 23.287):

2> For each carrier configured at the upper layer associated with the corresponding sidelink logical channel:

3> If the CBR of the carrier is lower than sl-threshCBR-FreqReselection, which is related to the priority of the sidelink logical channel:

Note: When multiple resource pools are configured for a carrier, which resource pool is used to determine the CBR for that carrier can be determined by the UE implementation, taking into account sl-HARQ-FeedbackEnabled of the sidelink logical channel.

4> The carrier may be considered as a candidate carrier for TX carrier (re)selection for the sidelink logical channel.

1> If not:

2> For each sidelink logical channel allowed on a carrier where data is available and Tx carrier (re)selection is triggered according to Section 5.22.1.1, if the carrier's CBR is lower than sl-threshCBR-FreqKeeping, which is related to the priority of the sidelink logical channel:

3> You can select a carrier and a pool of resources.

2> If not:

3> For each carrier configured by the upper layer that allows sidelink logical channels, if the CBR of that carrier is lower than sl-threshCBR-FreqReselection, which is associated with the priority of the sidelink logical channel:

4> For each carrier configured by the upper layer that allows sidelink logical channels, that carrier can be considered as a candidate carrier for TX carrier (re)selection.

For example, a MAC entity can:

1> If more than one carrier is considered as a candidate carrier for Tx carrier (re)selection:

2> When Tx carrier (re)selection is triggered, for each logical channel on which data is allowed on the available carrier:

3> One or more carriers can be selected from among the candidate carriers in order of increasing CBR, starting with the lowest CBR, and an associated pool(s) of resources can be selected.

4> If sl-HARQ-FeedbackEnabled is set to enabled for the sidelink logical channel:

5> One resource pool with PSFCH resources set can be selected from among the resource pools excluding the pools in sl-BWP-DiscPoolConfig or sl-BWP-DiscPoolConfigCommon (if set).

4> If not:

5> You can select a resource pool from among the resource pools excluding the pools set in sl-BWP-DiscPoolConfig or sl-BWP-DiscPoolConfigCommon.

Note: How many carriers are selected based on UE capability depends on the UE implementation.

NOTE: It is up to the UE implementation to determine which sidelink logical channels are allowed on the carrier where data is available and Tx carrier (re)selection is triggered.

Note: It is up to the UE implementation whether the resource pool for CBR measurements is reused as the resource pool for SL grant creation.

Meanwhile, the purpose of the procedure specified in Section 5.22.1.11 is to select a carrier for grant generation. However, since the UE procedure described in Section 5.22.1.11 only supports carrier selection for logical channel data, the UE does not perform a carrier selection procedure for grant generation for SL CSI reporting MAC CE transmission. Therefore, the operation for the UE to perform carrier selection for grant generation for SL CSI reporting MAC CE transmission must be specified in Section 5.22.1.11.

Additionally, as agreed upon in the previous #125bis meeting, CSI reporting can only be transmitted on the carrier on which the CSI reporting request (REQ) was received. For example, the procedure for a UE to select the carrier on which the SL CSI reporting request (REQ) was received as the carrier for SL CSI reporting MAC CE transmission should be specified in Section 5.22.1.11.

Therefore, considering the above, the following TP (text proposal) can be proposed.

For example, TX carrier (re)selection could be as follows (modification to section 5.22.1.11):

For example, a MAC entity may consider the CBR (channel busy ratio) measured by a lower layer according to TS 38.215 as the carrier's CBR if the CBR measurement result is available, or may consider the corresponding sl-defaultTxConfigIndex set by the upper layer as the CBR if the CBR measurement result is not available.

For example, if Tx carrier (re)selection is triggered for a sidelink process according to clause 5.22.1.1, 5.22.1.2, or 5.22.1.3.3 of TS 38.321, the MAC entity may:

1> If there is no selected sidelink grant on any carrier for which data is available for the sidelink logical channel and MAC CE as indicated by the higher layers (TS 38.331 and TS 23.287):

2> For each carrier configured at the upper layer associated with the corresponding sidelink logical channel:

3> If the carrier's CBR is lower than sl-threshCBR-FreqReselection, which is related to the priority of the sidelink logical channel:

Note: When multiple resource pools are configured for a carrier, which resource pool is used to determine the CBR for that carrier can be determined by the UE implementation, taking into account sl-HARQ-FeedbackEnabled of the sidelink logical channel.

4> The carrier may be considered as a candidate carrier for Tx carrier (re)selection for the corresponding sidelink logical channel and/or MAC CE.

1> If not:

2> For each sidelink logical channel allowed on a carrier where data is available and Tx carrier (re)selection is triggered according to Section 5.22.1.1, if the carrier's CBR is lower than sl-threshCBR-FreqKeeping, which is related to the priority of the sidelink logical channel:

3> You can select the carrier and its associated pool of resources.

2> If not:

3> For each carrier configured by the upper layer that allows sidelink logical channels or MAC CEs, if the CBR of that carrier is lower than sl-threshCBR-FreqReselection associated with the priority of the sidelink logical channel:

4> For each carrier configured by the upper layer that allows sidelink logical channels or MAC CEs, that carrier can be considered a candidate carrier for Tx carrier (re)selection.

For example, the MAC entity may select the carrier on which the SL-CSI request is received as the carrier for SL-CSI reporting MAC CE transmission.

For example, a MAC entity can:

1> If more than one carrier is considered as a candidate carrier for Tx carrier (re)selection:

2> When Tx carrier (re)selection is triggered, for each logical channel on which data is allowed on the available carrier:

3> One or more carriers can be selected from among the candidate carriers in order of increasing CBR, starting with the lowest CBR, and an associated pool(s) of resources can be selected.

4> If sl-HARQ-FeedbackEnabled is set to enabled for the sidelink logical channel:

5> One resource pool with PSFCH resources set can be selected from among the resource pools excluding the pools in sl-BWP-DiscPoolConfig or sl-BWP-DiscPoolConfigCommon (if set).

4> If not:

5> You can select a resource pool from among the resource pools excluding the pools set in sl-BWP-DiscPoolConfig or sl-BWP-DiscPoolConfigCommon.

Note: How many carriers are selected based on UE capability depends on the UE implementation.

NOTE: It is up to the UE implementation to determine which sidelink logical channels are allowed on the carrier where data is available and Tx carrier (re)selection is triggered.

Note: It is up to the UE implementation whether the resource pool for CBR measurements is reused as the resource pool for SL grant creation.

Additionally, for example, CSI reporting could be as follows (modification to section 5.22.1.7):

For example, the SL-CSI reporting procedure can be used to provide sidelink channel status information to a peer UE, as specified in clause 8.5 of TS 38.214.

For example, RRC can set the following parameters to control the SL-CSI reporting procedure:

- sl-LatencyBoundCSI-Report can be maintained for each PC5-RRC connection.

For example, the MAC entity may maintain an sl-CSI-ReportTimer for each pair of source layer 2 ID and destination layer 2 ID corresponding to a PC5-RRC connection. For example, the sl-CSI-ReportTimer may be used to ensure that the UE reporting SL-CSI complies with the latency requirement signaled from the UE triggering the CSI. For example, the value of sl-CSI-ReportTimer may be equal to the latency requirement of SL-CSI reporting in sl-LatencyBoundCSI-Report configured in RRC.

For example, the SL-CSI reporting MAC CE can only be transmitted on the carrier on which the SL-CSI request was received.

For example, a MAC entity could do the following for each pair of source layer 2 ID and destination layer 2 ID corresponding to a PC5-RRC connection established at a higher layer:

1> If SL-CSI reporting is triggered by SCI and not canceled:

2> If sl-CSI-ReportTimer for triggered SL-CSI reporting is not running:

3> You can start sl-CSI-ReportTimer.

2> When the sl-CSI-ReportTimer for triggered SL-CSI reporting expires:

3> Triggered SL-CSI reporting can be canceled.

2> If the MAC entity has SL resources allocated for a new transmission on the carrier on which the SL-CSI request was received, and the SL-SCH resources can accommodate the SL-CSI reporting MAC CE and its subheaders as a result of logical channel prioritization (LCP):

3> The multiplexing and assembly procedure can be instructed to generate a sidelink CSI reporting MAC CE as defined in Section 6.1.3.35.

3> You can stop the sl-CSI-ReportTimer for triggered SL-CSI reporting.

3> Triggered SL-CSI reporting can be canceled.

2> If the MAC entity is set to sidelink resource allocation mode 1:

3> It can trigger a scheduling request.

NOTE: A MAC entity configured with Sidelink Resource Allocation Mode 1 may trigger a scheduling request if the pending SL-CSI reporting transmission via the Sidelink Grant cannot meet the latency requirements associated with the SL-CSI reporting.

Meanwhile, in legacy single carrier operation as shown below, the UE can generate an SL grant for SL MAC CE transmission when SL CSI reporting/SL DRX command indication/SL IUC information reporting/SL IUC request is triggered and there are no SL-SCH resources that can accommodate the corresponding SL MAC CE.

For example, SL grant reception and SCI transmission are as follows (Section 5.22.1.1 of TS 38.321).

1> When the MAC entity chooses to generate a selected sidelink grant corresponding to a single MAC PDU transmission, and SL data is available on the logical channel, or SL-CSI reporting is triggered, or SL DRX command indication is triggered, or SL IUC information reporting is triggered, or SL IUC request is triggered; or

1> If the MAC entity chooses to generate a selected sidelink grant corresponding to a single SL-PRS transmission triggered by the reception of SCI from an upper layer or a peer UE:

2> When a single carrier frequency is set:

3> When SL-CSI reporting, or SL DRX command, or SL IUC request, or SL IUC information is triggered:

4> You can select a resource pool from among the resource pools excluding the pools set in sl-BWP-DiscPoolConfig, sl-BWP-DiscPoolConfigCommon, sl-BWP-PoolConfigA2X or sl-BWP-PoolConfigCommonA2X or the SL-PRS dedicated resource pool (if set).

2> As specified in Section 5.22.1.2, a TX resource (re)selection check can be performed for the selected resource pool.

2> If TX resource (re)selection is triggered as a result of the TX resource (re)selection check

3> If the selected resource pool is not a SL-PRS dedicated resource pool:

4> The number of HARQ retransmissions may be selected from the allowed number in sl-MaxTxTransNumPSSCH contained in sl-PSSCH-TxConfigList (if configured by RRC), and from the values overlapping sl-MaxTxTransNumPSSCH indicated in sl-CBR-PriorityTxConfigList for the highest priority logical channel and pending SL-PRS transmissions (if configured by RRC), and may be selected according to the CBR measured at lower layers, if available and allowed by the carrier and if CBR measurement results are available according to clause 5.1.27 of TS 38.215, or if CBR measurement results are not available, the corresponding sl-defaultTxConfigIndex configured by RRC, or if partial sensing is selected and CBR measurement results are not available, the corresponding sl-DefaultCBR-PartialSensing configured by RRC. In case sl-TxPoolExceptional is not used, random selection is selected and if CBR measurement results are not available, the corresponding sl-DefaultCBR-RandomSelection set by RRC may be selected.

NOTE: As specified in clause 8.1.4 of TS 38.214, for multi-consecutive slots transmission, it is up to the UE implementation whether the number of HARQ retransmissions is counted from the allowed number based on the number of MCSt transmissions during resource (re)selection or based on the number of slots within the multi-consecutive slots transmission.

4> (if configured by the RRC) may select an amount of frequency resources within the range between sl-MinSubChannelNumPSSCH and sl-MaxSubChannelNumPSSCH contained in the sl-PSSCH-TxConfigList, and (if configured by the RRC) may select from overlapping values between sl-MinSubChannelNumPSSCH and sl-MaxSubChannelNumPSSCH indicated in the sl-CBR-PriorityTxConfigList for the highest priority logical channel and pending SL-PRS transmissions, and may select according to the CBR measured at the lower layer, if available and allowed by the carrier and if CBR measurement results are available according to clause 5.1.27 of TS 38.215, or may select the corresponding sl-defaultTxConfigIndex configured by the RRC if CBR measurement results are not available, or partial sensing is selected and If the CBR measurement result is not available, the corresponding sl-DefaultCBR-PartialSensing set by RRC can be selected, or if sl-TxPoolExceptional is not used, random selection can be selected and if the CBR measurement result is not available, the corresponding sl-DefaultCBR-RandomSelection set by RRC can be selected.

3> If sl-InterUE-CoordinationScheme1, which enables reception/transmission of preferred resource sets and non-preferred resource sets, is not configured by RRC:

4> If transmission based on random selection is set in the upper layer:

5> If the selected resource pool is not a SL-PRS dedicated resource pool:

6> (If configured) The time and frequency resources for a transmission opportunity may be randomly selected from the pool of resources that occurred within the SL DRX active time as specified in Section 5.28.2 of the selected destination UE to indicate the SL DRX active time to the physical layer, and from the pool in which sidelink consistent LBT failures were detected and not canceled in all RB sets (if configured), based on the amount of frequency resources selected, the remaining PDB of SL data available to the logical channel(s), and the remaining SL-PRS delay budget of SL-PRS transmissions (if available), whether allowed on the carrier, and the latency requirement of the triggered SL-CSI report (request).

However, as shown below, the MAC specification only specifies the carrier selection procedure for logical channel data.

For example, TX carrier (re)selection is as follows (clause 5.22.1.11 of TS 38.321):

For example, if a MAC entity has a CBR measurement result, it may consider the CBR measured by the lower layer according to TS 38.215 as the carrier's CBR, or if there is no CBR measurement result, it may consider the corresponding sl-defaultTxConfigIndex set by the upper layer as the carrier's CBR.

For example, if Tx carrier (re)selection is triggered for a sidelink process according to clause 5.22.1.1, 5.22.1.2, or 5.22.1.3.3 of TS 38.321, the MAC entity may:

1> If there is no selected sidelink grant on any carrier allowed on the data-available sidelink logical channel, as directed by the higher layers (TS 38.331 and TS 23.287):

2> For each carrier configured at the upper layer associated with the corresponding sidelink logical channel:

3> If the CBR of the carrier is lower than sl-threshCBR-FreqReselection, which is related to the priority of the sidelink logical channel:

Note: When multiple resource pools are configured for a carrier, which resource pool is used to determine the CBR for that carrier can be determined by the UE implementation, taking into account sl-HARQ-FeedbackEnabled of the sidelink logical channel.

4> The carrier may be considered as a candidate carrier for TX carrier (re)selection for the sidelink logical channel.

1> If not:

2> For each sidelink logical channel allowed on a carrier where data is available and Tx carrier (re)selection is triggered according to Section 5.22.1.1, if the carrier's CBR is lower than sl-threshCBR-FreqKeeping, which is related to the priority of the sidelink logical channel:

3> You can select a carrier and a pool of resources.

2> If not:

3> For each carrier configured by the upper layer that allows sidelink logical channels, if the CBR of that carrier is lower than sl-threshCBR-FreqReselection, which is associated with the priority of the sidelink logical channel:

4> For each carrier configured by the upper layer that allows sidelink logical channels, that carrier can be considered as a candidate carrier for TX carrier (re)selection.

For example, a MAC entity can:

1> If more than one carrier is considered as a candidate carrier for Tx carrier (re)selection:

2> When Tx carrier (re)selection is triggered, for each logical channel on which data is allowed on the available carrier:

3> One or more carriers can be selected from among the candidate carriers in order of increasing CBR, starting with the lowest CBR, and an associated pool(s) of resources can be selected.

4> If sl-HARQ-FeedbackEnabled is set to enabled for the sidelink logical channel:

5> One resource pool with PSFCH resources set can be selected from among the resource pools excluding the pools in sl-BWP-DiscPoolConfig or sl-BWP-DiscPoolConfigCommon (if set).

4> Otherwise:

5> You can select a resource pool from among the resource pools excluding the pools set in sl-BWP-DiscPoolConfig or sl-BWP-DiscPoolConfigCommon.

Note: How many carriers are selected based on UE capability depends on the UE implementation.

NOTE: It is up to the UE implementation to determine which sidelink logical channels are allowed on the carrier where data is available and Tx carrier (re)selection is triggered.

Note: It is up to the UE implementation whether the resource pool for CBR measurements is reused as the resource pool for SL grant creation.

Meanwhile, the purpose of the procedure specified in Section 5.22.1.11 is to select a carrier for grant generation. However, since the UE procedure described in Section 5.22.1.11 only supports carrier selection for logical channel data, the UE does not perform a carrier selection procedure for grant generation for SL MAC CE transmission. Therefore, the operation by which the UE performs carrier selection for grant generation for SL MAC CE transmission must be specified in Section 5.22.1.11.

[Carrier Selection for SL CSI Reporting MAC CE]

As agreed upon in the previous #125bis meeting, CSI reporting can only be transmitted on the carrier on which the CSI reporting request (REQ) was received. For example, a UE may select the carrier on which the SL-CSI request was received as the carrier for SL CSI reporting MAC CE transmission.

Additionally, for example, with respect to pool selection, the UE may select any pool of resources from among the pools of resources, as in a single carrier procedure.

For example, a text proposal (TP) related to TX carrier (re)selection (section 5.22.1.11) could be proposed as follows (for SL CSI reporting MAC CE).

For example, a MAC entity may consider the CBR (channel busy ratio) measured by a lower layer according to TS 38.215 as the carrier's CBR if the CBR measurement result is available, or may consider the corresponding sl-defaultTxConfigIndex set by the upper layer as the CBR if the CBR measurement result is not available.

For example, if Tx carrier (re)selection is triggered for a sidelink process according to clause 5.22.1.1, 5.22.1.2, or 5.22.1.3.3 of TS 38.321, the MAC entity may:

1> If there is no selected sidelink grant on any carrier for which data is available for the sidelink logical channel and MAC CE as indicated by the higher layers (TS 38.331 and TS 23.287):

2> For each carrier configured at the upper layer associated with the corresponding sidelink logical channel:

3> If the carrier's CBR is lower than sl-threshCBR-FreqReselection, which is related to the priority of the sidelink logical channel:

Note: When multiple resource pools are configured for a carrier, which resource pool is used to determine the CBR for that carrier can be determined by the UE implementation, taking into account sl-HARQ-FeedbackEnabled of the sidelink logical channel.

4> The carrier may be considered as a candidate carrier for Tx carrier (re)selection for the corresponding sidelink logical channel and/or MAC CE.

1> If not:

2> For each sidelink logical channel allowed on a carrier where data is available and Tx carrier (re)selection is triggered according to Section 5.22.1.1, if the carrier's CBR is lower than sl-threshCBR-FreqKeeping, which is related to the priority of the sidelink logical channel:

3> You can select the carrier and its associated pool of resources.

2> If not:

3> For each carrier configured by the upper layer that allows sidelink logical channels or MAC CEs, if the CBR of that carrier is lower than sl-threshCBR-FreqReselection associated with the priority of the sidelink logical channel:

4> For each carrier configured by the upper layer that allows sidelink logical channels or MAC CEs, that carrier can be considered a candidate carrier for Tx carrier (re)selection.

For example, the MAC entity may select the carrier on which the SL-CSI request is received as the carrier for transmission of the sidelink CSI reporting MAC CE. For example, the MAC entity may select any pool of resources for the sidelink CSI reporting MAC CE, except for sl-BWP-DiscPoolConfig, sl-BWP-DiscPoolConfigCommon, sl-BWP-PoolConfigA2X, or sl-BWP-PoolConfigCommonA2X (if configured), or the SL-PRS dedicated resource pool (if configured).

For example, a MAC entity can:

1> If more than one carrier is considered as a candidate carrier for Tx carrier (re)selection:

2> When Tx carrier (re)selection is triggered, for each logical channel on which data is allowed on the available carrier:

3> One or more carriers can be selected from among the candidate carriers in order of increasing CBR, starting with the lowest CBR, and an associated pool(s) of resources can be selected.

4> If sl-HARQ-FeedbackEnabled is set to enabled for the sidelink logical channel:

5> One resource pool with PSFCH resources set can be selected from among the resource pools excluding the pools in sl-BWP-DiscPoolConfig or sl-BWP-DiscPoolConfigCommon (if set).

Note: How many carriers are selected based on UE capability depends on the UE implementation.

NOTE: It is up to the UE implementation to determine which sidelink logical channels are allowed on the carrier where data is available and Tx carrier (re)selection is triggered.

Note: It is up to the UE implementation whether the resource pool for CBR measurements is reused as the resource pool for SL grant creation.

[Carrier Selection for SL IUC Information MAC CE]

For example, the carrier selection procedure for the SL IUC information MAC CE can be defined similarly to the carrier selection procedure for the SL CSI reporting MAC CE. For example, the UE can select the carrier on which the SL IUC request is received as the carrier for transmitting the SL IUC information MAC CE. In addition, the single carrier procedure can be reused with respect to pool selection.

For example, a text proposal (TP) related to TX carrier (re)selection (section 5.22.1.11) could be proposed as follows (for SL IUC Information MAC CE):

For example, a MAC entity may consider the CBR (channel busy ratio) measured by a lower layer according to TS 38.215 as the CBR of the carrier if CBR measurements are available, or may consider the corresponding sl-defaultTxConfigIndex set by a higher layer as the CBR if CBR measurements are not available. For example, if Tx carrier (re)selection is triggered for a sidelink process according to clauses 5.22.1.1, 5.22.1.2, or 5.22.1.3.3 of TS 38.321, the MAC entity may:

1> If there is no selected sidelink grant on any carrier for which data is available for the sidelink logical channel and MAC CE as indicated by the higher layers (TS 38.331 and TS 23.287):

2> For each carrier configured at the upper layer associated with the corresponding sidelink logical channel:

3> If the carrier's CBR is lower than sl-threshCBR-FreqReselection, which is related to the priority of the sidelink logical channel:

Note: When multiple resource pools are configured for a carrier, which resource pool is used to determine the CBR for that carrier can be determined by the UE implementation, taking into account sl-HARQ-FeedbackEnabled of the sidelink logical channel.

4> The carrier may be considered as a candidate carrier for Tx carrier (re)selection for the corresponding sidelink logical channel and/or MAC CE.

1> If not:

2> For each sidelink logical channel allowed on a carrier where data is available and Tx carrier (re)selection is triggered according to Section 5.22.1.1, if the carrier's CBR is lower than sl-threshCBR-FreqKeeping, which is related to the priority of the sidelink logical channel:

3> You can select the carrier and its associated pool of resources.

2> If not:

3> For each carrier configured by the upper layer that allows sidelink logical channels or MAC CEs, if the CBR of that carrier is lower than sl-threshCBR-FreqReselection associated with the priority of the sidelink logical channel:

4> For each carrier configured by the upper layer that allows sidelink logical channels or MAC CEs, that carrier can be considered a candidate carrier for Tx carrier (re)selection.

For example, the MAC entity may select the carrier on which the sidelink inter-UE coordination request is received as the carrier for transmission of the sidelink inter-UE coordination information MAC CE. For example, the MAC entity may select any pool of resources for the sidelink inter-UE coordination information MAC CE, except for sl-BWP-DiscPoolConfig, sl-BWP-DiscPoolConfigCommon, sl-BWP-PoolConfigA2X, or sl-BWP-PoolConfigCommonA2X (if configured), or the SL-PRS dedicated resource pool (if configured).

For example, a MAC entity can:

1> If more than one carrier is considered as a candidate carrier for Tx carrier (re)selection:

2> When Tx carrier (re)selection is triggered, for each logical channel on which data is allowed on the available carrier:

3> One or more carriers can be selected from among the candidate carriers in order of increasing CBR, starting with the lowest CBR, and an associated pool(s) of resources can be selected.

4> If sl-HARQ-FeedbackEnabled is set to enabled for the sidelink logical channel:

5> One resource pool with PSFCH resources set can be selected from among the resource pools excluding the pools in sl-BWP-DiscPoolConfig or sl-BWP-DiscPoolConfigCommon (if set).

4> Otherwise:

5> You can select a resource pool from among the resource pools excluding the pools set in sl-BWP-DiscPoolConfig or sl-BWP-DiscPoolConfigCommon.

Note: How many carriers are selected based on UE capability depends on the UE implementation.

NOTE: It is up to the UE implementation to determine which sidelink logical channels are allowed on the carrier where data is available and Tx carrier (re)selection is triggered.

Note: It is up to the UE implementation whether the resource pool for CBR measurements is reused as the resource pool for SL grant creation.

Note: For sidelink IUC (inter-UE coordination) request MAC CE transmission, the MAC entity can select a TX pool of resources that require an IUC resource set. For sidelink IUC (inter-UE coordination) information MAC CE transmission, the MAC entity can select a TX pool of resources where an IUC resource set is located.

[Carrier Selection for SL IUC Request MAC CE]

For example, just as the behavior of logical channel data and MAC CE is not defined differently in the grant creation procedure of a single carrier, the carrier selection procedure for SL IUC request MAC CE in multi-carrier may use the same procedure as for logical channel data. For example, the single-carrier procedure may be reused for pool selection.

[Carrier Selection for SL DRX Command MAC CE]

For example, it could be the same as in the case of SL IUC request MAC CE.

For example, a text proposal (TP) related to TX carrier (re)selection (Section 5.22.1.11) could be proposed as follows (for SL IUC request MAC CE and/or SL DRX command MAC CE).

For example, a MAC entity may consider the CBR (channel busy ratio) measured by a lower layer according to TS 38.215 as the carrier's CBR if the CBR measurement result is available, or may consider the corresponding sl-defaultTxConfigIndex set by the upper layer as the CBR if the CBR measurement result is not available.

For example, if Tx carrier (re)selection is triggered for a sidelink process according to clause 5.22.1.1, 5.22.1.2, or 5.22.1.3.3 of TS 38.321, the MAC entity may:

1> If there is no selected sidelink grant on any carrier allowed for a data-available sidelink logical channel, or SL DRX command MAC CE, or SL IUC request MAC CE, as indicated by higher layers (TS 38.331 and TS 23.287):

2> For each carrier configured at the upper layer associated with the corresponding sidelink logical channel:

3> If the carrier's CBR is lower than sl-threshCBR-FreqReselection, which is related to the priority of the sidelink logical channel:

Note: When multiple resource pools are configured for a carrier, which resource pool is used to determine the CBR for that carrier can be determined by the UE implementation, taking into account sl-HARQ-FeedbackEnabled of the sidelink logical channel.

4> The carrier may be considered as a candidate carrier for Tx carrier (re)selection for the corresponding sidelink logical channel and/or MAC CE.

1> If not:

2> For each sidelink logical channel where data is available (if any), or for a SL DRX command MAC CE, or for a SL IUC request MAC CE, and if allowed on the carrier where Tx carrier (re)selection is triggered according to clause 5.22.1.1, if the carrier's CBR is lower than sl-threshCBR-FreqKeeping related to the priority of the sidelink logical channel:

3> You can select the carrier and its associated pool of resources.

2> If not:

3> For each carrier configured by upper layers that allows sidelink logical channels, or SL DRX command MAC CE, or SL IUC request MAC CE, if the CBR of that carrier is lower than sl-threshCBR-FreqReselection associated with the priority of the sidelink logical channel:

4> For each carrier configured by a higher layer that allows sidelink logical channels, or SL DRX command MAC CE, or SL IUC request MAC CE, that carrier may be considered a candidate carrier for Tx carrier (re)selection.

For example, a MAC entity can:

1> If more than one carrier is considered as a candidate carrier for Tx carrier (re)selection:

2> When Tx carrier (re)selection is triggered, for each logical channel on which data is allowed on the available carrier:

3> One or more carriers can be selected from among the candidate carriers in order of increasing CBR, starting with the lowest CBR, and an associated pool(s) of resources can be selected.

4> If sl-HARQ-FeedbackEnabled is set to enabled for the sidelink logical channel:

5> One resource pool with PSFCH resources set can be selected from among the resource pools excluding the pools in sl-BWP-DiscPoolConfig or sl-BWP-DiscPoolConfigCommon (if set).

4> Otherwise:

5> You can select a resource pool from among the resource pools excluding the pools set in sl-BWP-DiscPoolConfig or sl-BWP-DiscPoolConfigCommon.

2> When Tx carrier (re)selection is triggered, for SL DRX command MAC CE or SL IUC request MAC CE:

3> Any pool of resources can be selected, excluding sl-BWP-DiscPoolConfig, sl-BWP-DiscPoolConfigCommon, sl-BWP-PoolConfigA2X, or sl-BWP-PoolConfigCommonA2X (if set), or the SL-PRS dedicated resource pool (if set).

Note: How many carriers are selected based on UE capability depends on the UE implementation.

NOTE: It is up to the UE implementation to determine which sidelink logical channels are allowed on the carrier where data is available and Tx carrier (re)selection is triggered.

Note: It is up to the UE implementation whether the resource pool for CBR measurements is reused as the resource pool for SL grant creation.

Alternatively, for example, for transmitting SL MAC CE without QoS flow (e.g., SL CSI reporting MAC CE, SL inter-UE coordination (IUC) request MAC CE, SL inter-UE coordination (IUC) information MAC CE), the UE may generate an SL grant for SL MAC CE transmission using a legacy carrier (e.g., a carrier configured or allocated to the UE for single-carrier operation), and perform SL MAC CE transmission using the SL grant generated based on the legacy carrier.

Alternatively, for example, a default carrier (set) for transmitting SL MAC CEs (e.g., SL CSI reporting MAC CE, SL inter-UE coordination request MAC CE, SL inter-UE coordination information MAC CE) without QoS flows may be pre-configured or set by the base station or a higher layer (e.g., V2X layer) and then communicated to the UE (e.g., the access stratum (AS) layer of the UE, or the MAC entity).

FIG. 11 illustrates a carrier selection method according to an embodiment of the present disclosure. The embodiment of FIG. 11 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and/or operations of the embodiments may be omitted.

Referring to FIG. 11, a Tx UE supporting multi-carrier operation may obtain information related to multiple carriers (carrier #1, carrier #2, carrier #3, and carrier #4 in FIG. 11). For example, the Tx UE may perform a carrier selection procedure for transmitting available data of a logical channel. In this case, for example, the Tx UE may measure a CBR for each of the multiple carriers and compare the CBR measurements for each of the multiple carriers with a CBR threshold. For example, based on the CBR of carrier #1 (e.g., CBR measurement value: 5) being lower than a CBR threshold mapped to a priority associated with the logical channel, carrier #1 may be determined as a candidate carrier. And, for example, based on the CBR of carrier #2 (e.g., CBR measurement value: 20) exceeding a CBR threshold mapped to a priority associated with the logical channel, carrier #2 may be excluded as a candidate carrier. For example, logical channel data may be transmitted on carrier #1 based on the carrier #1 having the lowest CBR among one or more carriers included in the candidate carriers. The operations related to carrier #1 and carrier #2 described above may be limited to carrier selection operations for transmitting logical channel data.

Meanwhile, the carrier selection operation for MAC CE may be different from the conventional carrier selection operation as described below. For example, in the case of carrier #3 and/or carrier #4 among the plurality of carriers, the Tx UE may receive CSI request information based on carrier #3 from a peer UE, and/or may receive an IUC request MAC CE based on carrier #4. For example, unlike the above-described operation, CBR measurement may not be performed on carrier #3 on which CSI request information is received and/or carrier #4 on which IUC request MAC CE is received. Specifically, for example, the Tx UE may select carrier #3 on which the CSI request information is received as a carrier for CSI reporting MAC CE without performing CBR measurement on each of the plurality of carriers. Alternatively, for example, the Tx UE may select the carrier #4 on which the IUC request MAC CE is received as a carrier for the IUC information MAC CE without performing CBR measurement for each of the plurality of carriers. For example, the Tx UE may transmit the CSI reporting MAC CE to the peer UE based on the carrier #3 on which the CSI request information is received. Or, for example, the Tx UE may transmit the IUC information MAC CE to the peer UE based on the carrier #4 on which the IUC request MAC CE is received. For example, the CSI reporting MAC CE may be transmitted only on the carrier on which the CSI request information is received. Or, the IUC information MAC CE may be transmitted only on the carrier on which the IUC request MAC CE is received.

In the embodiment of FIG. 11, the carrier selection procedure for transmission of CSI reporting MAC CE and the carrier selection procedure for transmission of IUC information MAC CE are described together for comparison with the carrier selection procedure for transmission of existing logical channel data. However, the carrier selection procedure for transmission of CSI reporting MAC CE and the carrier selection procedure for transmission of IUC information MAC CE can be performed independently of each other. A specific description of each procedure is as follows (see the embodiment of FIG. 12 and/or the embodiment of FIG. 13).

FIG. 12 illustrates a carrier selection method for transmitting a CSI reporting MAC CE according to an embodiment of the present disclosure. The embodiment of FIG. 12 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and/or operations of the embodiments may be omitted.

Referring to FIG. 12, UE A and UE B are UEs that support multi-carrier operation. For example, UE A and UE B can obtain information related to multiple carriers. For example, a unicast connection (or PC5 RRC connection) can be established between UE A and UE B. In step S1210, UE A can receive a PSSCH from UE B. For example, the PSSCH can be transmitted and received on a first carrier among multiple carriers. For example, the SCI received through the PSSCH can include information related to a CSI (channel state information) request. And, for example, a CSI-RS (reference signal) can be transmitted and received through the PSSCH on the first carrier. For example, a procedure related to CSI reporting of UE A can be triggered based on information related to the CSI request received on the first carrier. For example, UE A may perform measurement for CSI reporting based on CSI-RS and generate CSI reporting MAC CE based thereon. For example, CSI reporting MAC CE may include information related to CQI and/or RI. In step S1220, UE A may perform carrier selection for transmitting the CSI reporting MAC CE. For example, when selecting a carrier for transmission of the CSI reporting MAC CE, UE A may not perform CBR measurement for each of the plurality of carriers. For example, UE A may select the first carrier, on which information related to the CSI request is received in step S1210 described above, as a carrier for transmission of the CSI reporting MAC CE, without performing a CBR measurement procedure for each of the plurality of carriers and a comparison procedure with a CBR threshold. In step S1230, UE A may transmit a CSI reporting MAC CE based on the first carrier selected in step S1220 described above. For example, the CSI reporting MAC CE may be transmitted only on the carrier (the first carrier) on which information related to the CSI request is received.

FIG. 13 illustrates a carrier selection method for transmitting an IUC information MAC CE according to an embodiment of the present disclosure. The embodiment of FIG. 13 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and/or operations of the embodiments may be omitted.

Referring to FIG. 13, UE A and UE B are UEs that support multi-carrier operation. For example, UE A and UE B can obtain information related to multiple carriers. For example, a unicast connection (or PC5 RRC connection) can be established between UE A and UE B. In step S1310, UE A can receive a PSSCH from UE B. For example, the PSSCH can be transmitted and received on a first carrier among multiple carriers. For example, an IUC (inter-UE coordination) request MAC CE can be transmitted and received through the PSSCH. For example, a procedure related to IUC reporting of UE A can be triggered based on the IUC request MAC CE received on the first carrier. For example, UE A can determine preferred/non-preferred resources for resource selection of UE B based on information included in an IUC request MAC CE, and generate an IUC information MAC CE based on the information. For example, the IUC information MAC CE can include information related to preferred/non-preferred resources (e.g., an IUC resource set). In step S1320, UE A can perform carrier selection for transmitting the IUC information MAC CE. For example, when selecting a carrier for transmitting the IUC information MAC CE, UE A may not perform CBR measurement for each of the plurality of carriers. For example, UE A may select the first carrier on which the IUC request MAC CE was received in step S1310 as a carrier for transmitting the IUC information MAC CE, without performing a CBR measurement and comparison procedure with a CBR threshold for each of the plurality of carriers. In step S1330, UE A may transmit the IUC information MAC CE based on the first carrier selected in step S1320. For example, the IUC information MAC CE may be transmitted only on the carrier (the first carrier) on which information related to the IUC request was received.

The wording of multi-carrier as specified in this disclosure may be extended to carrier aggregation (CA).

The CBR threshold associated with a sidelink carrier/SL sidelink bandwidth part (BWP)/SL HARQ entity specified in the present disclosure can be set per priority, per QoS profile (e.g., packet delay budget (PDB) or reliability), per SL radio bearer, or per logical channel.

The wording of the sidelink carrier specified in this disclosure may be extended to a sidelink BWP or a sidelink HARQ entity.

The unicast service specified in this disclosure may be interpreted as a pair of source layer-2 ID and destination layer-2 ID.

The groupcast service specified in this disclosure may be interpreted as a groupcast destination layer-2 ID.

The broadcast service specified in this disclosure may be interpreted as a broadcast destination layer-2 ID.

The term "carrier" as specified in the present disclosure may be replaced with "band" or "set of resource blocks (RBs) of a specific carrier" or "set of resource pools of a specific carrier" or "channel".

For example, whether (some) of the proposed methods/rules of the present disclosure are applicable and/or related parameters (e.g., thresholds) may be set specifically (or differently or independently) for SL-Channel Access Priority Class (CAPC). For example, whether (some) of the proposed methods/rules of the present disclosure are applicable and/or related parameters (e.g., thresholds) may be set specifically (or differently or independently) for SL-LBT types (e.g., Type 1 LBT, Type 2A LBT, Type 2B LTB, Type 2C LBT). For example, whether (some) of the proposed methods/rules of the present disclosure are applicable and/or related parameters (e.g., thresholds) may be set specifically (or differently or independently) depending on whether FBE (Frame Based LBT) is applied. For example, whether (some) of the proposed methods/rules of the present disclosure are applicable and/or the relevant parameters (e.g., thresholds) may be set specifically (or differently or independently) depending on whether LBE (Load Based LBT) is applied.

For example, whether (some) of the proposed methods/rules of the present disclosure are applicable and/or their associated parameters (e.g., thresholds) can be set resource pool-specifically (or differently or independently). For example, whether (some) of the proposed methods/rules of the present disclosure are applicable and/or their associated parameters (e.g., thresholds) can be set congestion level-specifically (or differently or independently). For example, whether (some) of the proposed methods/rules of the present disclosure are applicable and/or their associated parameters (e.g., thresholds) can be set service priority-specifically (or differently or independently). For example, whether (some) of the proposed methods/rules of the present disclosure are applicable and/or their associated parameters (e.g., thresholds) can be set service type-specifically (or differently or independently). For example, whether (some) of the proposed schemes/rules of the present disclosure are applicable and/or related parameters (e.g., thresholds) can be set specifically (or differently or independently) for QoS requirements (e.g., latency, reliability). For example, whether (some) of the proposed schemes/rules of the present disclosure are applicable and/or related parameters (e.g., thresholds) can be set specifically (or differently or independently) for PQI (5QI (5G QoS identifier) for PC5). For example, whether (some) of the proposed schemes/rules of the present disclosure are applicable and/or related parameters (e.g., thresholds) can be set specifically (or differently or independently) for traffic types (e.g., periodic generation or aperiodic generation). For example, whether (some) of the proposed schemes/rules of the present disclosure are applicable and/or related parameters (e.g., thresholds) can be set specifically (or differently or independently) for SL transmission resource allocation modes (e.g., mode 1 or mode 2). For example, whether (some) of the proposed methods/rules of the present disclosure are applicable and/or related parameters (e.g., thresholds) may be configured specifically (or differently or independently) for a Tx profile (e.g., a Tx profile indicating that the service supports sidelink DRX operation or a Tx profile indicating that the service does not need to support sidelink DRX operation).

For example, whether the proposed rule of the present disclosure applies and/or the related parameter setting values can be specifically (or differently or independently) set depending on whether PUCCH configuration is supported (e.g., when PUCCH resources are configured or when PUCCH resources are not configured). For example, whether the proposed rule of the present disclosure applies and/or the related parameter setting values can be specifically (or differently or independently) set for a resource pool (e.g., a resource pool where PSFCH is configured or a resource pool where PSFCH is not configured). For example, whether the proposed rule of the present disclosure applies and/or the related parameter setting values can be specifically (or differently or independently) set for a type of service/packet. For example, whether the proposed rule of the present disclosure applies and/or the related parameter setting values can be specifically (or differently or independently) set for a priority of a service/packet. For example, whether the proposed rule of the present disclosure applies and/or the related parameter setting values can be set specifically (or differently or independently) for a QoS profile or QoS requirement (e.g., URLLC/EMBB traffic, reliability, latency). For example, whether the proposed rule of the present disclosure applies and/or the related parameter setting values can be set specifically (or differently or independently) for a PQI. For example, whether the proposed rule of the present disclosure applies and/or the related parameter setting values can be set specifically (or differently or independently) for a PFI. For example, whether the proposed rule of the present disclosure applies and/or the related parameter setting values can be set specifically (or differently or independently) for a cast type (e.g., unicast, groupcast, broadcast). For example, whether the proposed rule of the present disclosure applies and/or the related parameter setting values can be set specifically (or differently or independently) for a (resource pool) congestion level (e.g., CBR). For example, whether the proposed rule of the present disclosure is applicable and/or the related parameter setting value can be set specifically (or differently or independently) for an SL HARQ feedback scheme (e.g., NACK-only feedback, ACK/NACK feedback). For example, whether the proposed rule of the present disclosure is applicable and/or the related parameter setting value can be set specifically (or differently or independently) for HARQ Feedback Enabled MAC PDU transmission. For example, whether the proposed rule of the present disclosure is applicable and/or the related parameter setting value can be set specifically (or differently or independently) for HARQ Feedback Disabled MAC PDU transmission. For example, whether the proposed rule of the present disclosure is applicable and/or the related parameter setting value can be set specifically (or differently or independently) depending on whether a PUCCH-based SL HARQ feedback reporting operation is set. For example, whether the proposed rule of the present disclosure applies and/or the related parameter setting values can be set specifically (or differently or independently) depending on whether pre-emption or pre-emption-based resource reselection is performed. For example, whether the proposed rule of the present disclosure applies and/or the related parameter setting values can be set specifically (or differently or independently) depending on whether re-evaluation or re-evaluation-based resource reselection is performed. For example, whether the proposed rule of the present disclosure applies and/or the related parameter setting values can be set specifically (or differently or independently) for (L2 or L1) (source and/or destination) identifiers. For example, whether the proposed rule of the present disclosure applies and/or the related parameter setting values can be set specifically (or differently or independently) for (L2 or L1) (a combination of source ID and destination ID) identifiers. For example, whether the proposed rule of the present disclosure applies and/or the related parameter setting values can be set specifically (or differently or independently) for an identifier (L2 or L1) (a combination of a pair of source ID and destination ID and a cast type). For example, whether the proposed rule of the present disclosure applies and/or the related parameter setting values can be set specifically (or differently or independently) for a direction of a pair of source layer ID and destination layer ID. For example, whether the proposed rule of the present disclosure applies and/or the related parameter setting values can be set specifically (or differently or independently) for a PC5 RRC connection/link. For example, whether the proposed rule of the present disclosure applies and/or the related parameter setting values can be set specifically (or differently or independently) depending on whether SL DRX is performed. For example, whether the proposed rule of the present disclosure applies and/or the related parameter setting values can be set specifically (or differently or independently) depending on whether SL DRX is supported. For example, whether the proposed rule of the present disclosure applies and/or the related parameter setting values can be set specifically (or differently or independently) for the SL mode type (e.g., resource allocation mode 1 or resource allocation mode 2). For example, whether the proposed rule of the present disclosure applies and/or the related parameter setting values can be set specifically (or differently or independently) for the case of performing (a)periodic resource reservation. For example, whether the proposed rule of the present disclosure applies and/or the related parameter setting values can be set specifically (or differently or independently) for a Tx profile (e.g., a Tx profile indicating that the service supports sidelink DRX operation or a Tx profile indicating that the service does not need to support sidelink DRX operation).

The applicability of the proposals and proposed rules of the present disclosure (and/or the associated parameter settings) may also be applied to mmWave SL operation.

FIG. 14 illustrates a method for a first device to perform wireless communication according to an embodiment of the present disclosure. The embodiment of FIG. 14 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and/or operations of the embodiments may be omitted.

Referring to FIG. 14, in step S1410, a first device may obtain information related to a plurality of carriers including a first carrier. In step S1420, the first device may receive, from a second device, a first SCI for scheduling a physical sidelink shared channel (PSSCH) and a second SCI (sidelink control information) through a physical sidelink control channel (PSCCH). In step S1430, the first device may receive, from the second device, a second SCI including information for a channel state information (CSI) request through the PSSCH. In step S1440, the first device may transmit a medium access control (MAC) control element (CE) for CSI reporting to the second device. For example, the MAC CE for the CSI report may be transmitted on the first carrier on which information for the CSI request is received.

For example, the MAC CE for the CSI report may be transmitted only on the first carrier on which information for the CSI request is received.

Additionally, for example, the first device may receive a CSI RS (reference signal) from the second device via the PSSCH. For example, the MAC CE for the CSI report may include a measurement value based on the CSI RS.

For example, the MAC CE for the CSI report may include at least one of information related to a channel quality indicator (CQI) or information related to a rank indicator (RI).

For example, the first carrier on which information for the CSI request is received may be selected as a carrier for transmission of the MAC CE for the CSI report.

For example, a resource pool related to the MAC CE for the CSI reporting may be selected from among multiple resource pools excluding a resource pool related to discovery, a resource pool related to aircraft-to-everything (A2X) service, and a dedicated resource pool related to sidelink (SL) positioning reference signal (PRS).

Additionally, for example, the first device can receive a MAC CE for an inter-UE coordination (IUC) request from the second device. And, for example, the first device can transmit a MAC CE including IUC information to the second device. For example, a second carrier on which the MAC CE for the IUC request is received can be selected as a carrier for transmitting the MAC CE including the IUC information. And, for example, the second carrier can be included in the plurality of carriers. For example, at least one of the resource pool associated with the MAC CE including the IUC information or the resource pool associated with the MAC CE for the IUC request can be selected from a plurality of resource pools excluding a resource pool associated with discovery, a resource pool associated with an aircraft-to-everything (A2X) service, and a dedicated resource pool associated with a sidelink (SL) positioning reference signal (PRS). For example, based on a CBR (channel busy ratio) for a carrier other than the first carrier and the second carrier among the plurality of carriers being lower than a threshold, the carrier may be included in a candidate carrier. For example, the candidate carrier may include one or more carriers for transmitting available data of a logical channel. For example, based on a CBR of a third carrier among the one or more carriers included in the candidate carriers being the lowest, the third carrier may be selected as a carrier for transmitting available data of a logical channel. For example, CBR measurement may not be performed for each of the first carrier associated with the MAC CE for the CSI reporting and the second carrier associated with the MAC CE including the IUC information.

For example, based on the establishment of a unicast connection between the first device and the second device, the MAC CE for the CSI report may be transmitted to the second device.

The proposed method can be applied to devices according to various embodiments of the present disclosure. First, the processor (102) of the first device (100) can control the transceiver (106) to obtain information related to a plurality of carriers including a first carrier. Then, the processor (102) of the first device (100) can control the transceiver (106) to receive, from a second device, a first SCI (sidelink control information) for scheduling a physical sidelink shared channel (PSSCH) and a second SCI (physical sidelink control channel) through a physical sidelink control channel (PSCCH). Then, the processor (102) of the first device (100) can control the transceiver (106) to receive, from the second device, the second SCI including information for a channel state information (CSI) request through the PSSCH. And, the processor (102) of the first device (100) can control the transceiver (106) to transmit a medium access control (MAC) CE (control element) for CSI reporting to the second device. For example, the MAC CE for the CSI reporting can be transmitted on the first carrier on which information for the CSI request is received.

According to one embodiment of the present disclosure, a first device configured to perform wireless communication may be provided. For example, the first device may include at least one transceiver; at least one processor; and at least one memory coupled to the at least one processor and storing instructions. For example, the instructions, based on being executed by the at least one processor, may cause the first device to: obtain information related to a plurality of carriers including a first carrier; receive, from a second device, a first SCI (sidelink control information) for scheduling a physical sidelink shared channel (PSSCH) and a second SCI (sidelink control information) via a physical sidelink control channel (PSCCH); receive, from the second device, a second SCI including information for a channel state information (CSI) request via the PSSCH; and transmit a medium access control (MAC) control element (CE) for CSI reporting to the second device. For example, the MAC CE for the CSI report may be transmitted on the first carrier on which information for the CSI request is received.

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 being executed by the at least one processor, may cause the first device to: obtain information related to a plurality of carriers including a first carrier; receive, from a second device, a first SCI (sidelink control information) for scheduling a physical sidelink shared channel (PSSCH) and a second SCI (physical sidelink control channel) via a physical sidelink control channel (PSCCH); receive, from the second device, a second SCI including information for a channel state information (CSI) request via the PSSCH; and transmit a medium access control (MAC) control element (CE) for CSI reporting to the second device. For example, the MAC CE for the CSI report may be transmitted on the first carrier on which information for the CSI request is received.

According to one embodiment of the present disclosure, a non-transitory computer-readable storage medium having instructions recorded thereon may be provided. For example, the instructions, when executed, may cause a first device to: obtain information related to a plurality of carriers including a first carrier; receive, from a second device, a first SCI (sidelink control information) for scheduling a physical sidelink shared channel (PSSCH) and a second SCI (physical sidelink control channel) via a physical sidelink control channel (PSCCH); receive, from the second device, a second SCI including information for a channel state information (CSI) request via the PSSCH; and transmit a medium access control (MAC) control element (CE) for CSI reporting to the second device. For example, the MAC CE for CSI reporting may be transmitted on the first carrier on which information for the CSI request is received.

FIG. 15 illustrates a method for a second device to perform wireless communication according to an embodiment of the present disclosure. The embodiment of FIG. 15 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and/or operations of the embodiments may be omitted.

Referring to FIG. 15, in step S1510, the second device may obtain information related to a plurality of carriers including a first carrier. In step S1520, the second device may transmit, to the first device, a first sidelink control channel (SCI) for scheduling a physical sidelink shared channel (PSSCH) and a second sidelink control information (SCI) through a physical sidelink control channel (PSCCH). In step S1530, the second device may transmit, to the first device, a second SCI including information for a channel state information (CSI) request through the PSSCH. In step S1540, the second device may receive, from the first device, a medium access control (MAC) control element (CE) for CSI reporting. For example, the MAC CE for the CSI report may be transmitted by the first device on the first carrier through which information for the CSI request is received by the first device.

The proposed method can be applied to devices according to various embodiments of the present disclosure. First, the processor (202) of the second device (200) can control the transceiver (206) to obtain information related to a plurality of carriers including a first carrier. Then, the processor (202) of the second device (200) can control the transceiver (206) to transmit, to the first device, a first SCI for scheduling a physical sidelink shared channel (PSSCH) and a second SCI (sidelink control information) through a physical sidelink control channel (PSCCH). Then, the processor (202) of the second device (200) can control the transceiver (206) to transmit, to the first device, the second SCI including information for a channel state information (CSI) request through the PSSCH. And, the processor (202) of the second device (200) can control the transceiver (206) to receive a medium access control (MAC) control element (CE) for CSI reporting from the first device. For example, the MAC CE for CSI reporting can be transmitted by the first device on the first carrier on which information for the CSI request is received by the first device.

According to one embodiment of the present disclosure, a second device configured to perform wireless communication 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, may cause the second device to: obtain information related to a plurality of carriers including a first carrier; transmit, to a first device, a first SCI for scheduling a physical sidelink shared channel (PSSCH) and a second SCI (sidelink control information) via a physical sidelink control channel (PSCCH); transmit, to the first device, the second SCI including information for a channel state information (CSI) request via the PSSCH; and receive, from the first device, a medium access control (MAC) control element (CE) for CSI reporting. For example, the MAC CE for the CSI report may be transmitted by the first device on the first carrier through which information for the CSI request is received by the first device.

According to one embodiment of the present disclosure, a processing device configured to control a second device may be provided. For example, the processing device may include at least one processor; and at least one memory coupled to the at least one processor and storing instructions. For example, the instructions, when executed by the at least one processor, may cause the second device to: obtain information related to a plurality of carriers including a first carrier; transmit, to the first device, a first SCI for scheduling a physical sidelink shared channel (PSSCH) and a second SCI (sidelink control information) via a physical sidelink control channel (PSCCH); transmit, to the first device, the second SCI including information for a channel state information (CSI) request via the PSSCH; and receive, from the first device, a medium access control (MAC) control element (CE) for CSI reporting. For example, the MAC CE for the CSI report may be transmitted by the first device on the first carrier through which information for the CSI request is received by the first device.

According to one embodiment of the present disclosure, a non-transitory computer-readable storage medium having instructions recorded thereon may be provided. For example, the instructions, when executed, may cause a second device to: obtain information related to a plurality of carriers including a first carrier; transmit, to the first device, a first SCI for scheduling a physical sidelink shared channel (PSSCH) and a second SCI (sidelink control information) via a physical sidelink control channel (PSCCH); transmit, to the first device, a second SCI including information for a channel state information (CSI) request via the PSSCH; and receive, from the first device, a medium access control (MAC) control element (CE) for CSI reporting. For example, the MAC CE for the CSI report may be transmitted by the first device on the first carrier through which information for the CSI request is received by the first device.

According to various embodiments of the present disclosure, when selecting a carrier for transmission of a MAC CE (e.g., a CSI reporting MAC CE or an IUC information MAC CE), a carrier on which an SCI including information triggering transmission of the MAC CE (e.g., an SCI including CSI request information) or a MAC CE (e.g., a MAC CE including IUC request information) is received may be selected as the carrier for transmission of the MAC CE (e.g., a CSI reporting MAC CE or an IUC information MAC CE). In this case, for example, a procedure for measuring a CBR for each of a plurality of carriers and a procedure for comparing the CBR with a CBR threshold may be omitted, and thus the carrier selection procedure for transmitting the MAC CE of the present disclosure may significantly reduce delay and overhead associated with existing carrier selection procedures. In addition, since the delay accompanying the existing carrier selection procedure as described above can be eliminated, for example, the transmission of the response MAC CE (e.g., CSI reporting MAC CE or IUC information MAC CE) can be stably completed before the timer (sl-CSI-ReportTimer or sl-IUC-ReportTimer) started when the transmission of the response MAC CE (e.g., CSI reporting MAC CE or IUC information MAC CE) is triggered expires. Alternatively, since the carrier on which the request information is received can be selected as the carrier for transmission of the response MAC CE regardless of the CBR measurement results for each of the plurality of carriers, the transmission of a high-priority MAC CE (e.g., CSI reporting MAC CE or IUC information MAC CE) can be more stably guaranteed. Alternatively, for example, as described above, by selecting a carrier for a response MAC CE transmission based on the carrier in which the request information is received, the delay associated with the transmission of the MAC CE can be reduced, and the transmission of the MAC CE can be guaranteed, thereby improving the reliability associated with the transmission of the MAC CE.

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. 16 illustrates a communication system (1) according to one embodiment of the present disclosure. The embodiment of Fig. 16 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and/or operations of the embodiments may be omitted.

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

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. 17 illustrates a wireless device according to an embodiment of the present disclosure. The embodiment of FIG. 17 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and/or operations of the embodiments may be omitted.

Referring to FIG. 17, 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. 16.

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. 18 illustrates a signal processing circuit for a transmission signal according to an embodiment of the present disclosure. The embodiment of FIG. 18 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and/or operations of the embodiments may be omitted.

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

The codeword can be converted into a wireless signal through the signal processing circuit (1000) of FIG. 18. Here, the codeword is an encoded bit sequence of an information block. The information block may include a transport block (e.g., an UL-SCH transport block, a DL-SCH transport block). The wireless signal may 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. 18. For example, a wireless device (e.g., 100, 200 of FIG. 17) 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 19 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 16). The embodiment of Figure 19 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and/or operations of the embodiments may be omitted.

Referring to FIG. 19, the wireless device (100, 200) corresponds to the wireless device (100, 200) of FIG. 17 and may be composed of various elements, components, units/units, and/or modules. For example, the wireless device (100, 200) may include a communication unit (110), a control unit (120), a memory unit (130), and an additional element (140). The communication unit may include a communication circuit (112) and a transceiver(s) (114). For example, the communication circuit (112) may include one or more processors (102, 202) and/or one or more memories (104, 204) of FIG. 17. For example, the transceiver(s) (114) may include one or more transceivers (106, 206) and/or one or more antennas (108, 208) of FIG. 17. 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. 16, 100a), a vehicle (Fig. 16, 100b-1, 100b-2), an XR device (Fig. 16, 100c), a portable device (Fig. 16, 100d), a home appliance (Fig. 16, 100e), an IoT device (Fig. 16, 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. 16, 400), a base station (Fig. 16, 200), a network node, etc. Wireless devices may be mobile or stationary depending on the use/service.

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

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

FIG. 20 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. 20 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and/or operations of the embodiments may be omitted.

Referring to FIG. 20, 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. 19, 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. 21 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/unmanned aerial vehicle (AV), a ship, etc. The embodiment of FIG. 21 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and/or operations of the embodiments may be omitted.

Referring to FIG. 21, 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. 19, 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 specification may be combined in various ways. For example, the technical features of the method claims of this specification may be combined and implemented as a device, and the technical features of the device claims of this specification may be combined and implemented as a method. Furthermore, the technical features of the method claims and the technical features of the device claims of this specification may be combined and implemented as a device, and the technical features of the method claims and the technical features of the device claims of this specification may be combined and implemented as a method.

Claims (20)

In terms of method, A step in which a first device acquires information related to a plurality of carriers including a first carrier; A step in which the first device receives, from the second device, a first SCI for scheduling a physical sidelink shared channel (PSSCH) and a second SCI (sidelink control information) through a physical sidelink control channel (PSCCH); A step of receiving the second SCI including information for a CSI (channel state information) request from the second device through the PSSCH; and A step of transmitting a MAC (medium access control) CE (control element) for CSI reporting to the second device; A method in which the MAC CE for the CSI report is transmitted on the first carrier on which information for the CSI request is received. In the first paragraph, A method in which the MAC CE for the CSI report is transmitted only on the first carrier on which information for the CSI request is received. In the first paragraph, Further comprising a step of receiving a CSI RS (reference signal) from the second device through the PSSCH; A method wherein the MAC CE for the above CSI reporting includes a measurement value based on the above CSI RS. In the first paragraph, A method in which the MAC CE for the above CSI report includes at least one of information related to a channel quality indicator (CQI) or information related to a rank indicator (RI). In the first paragraph, A method in which the first carrier, from which information for the CSI request is received, is selected as a carrier for transmission of the MAC CE for the CSI report. In the first paragraph, A method in which a resource pool related to MAC CE for the above CSI reporting is selected from among multiple resource pools excluding a resource pool related to discovery, a resource pool related to A2X (aircraft-to-everything) service, and a dedicated resource pool related to SL (sidelink) PRS (positioning reference signal). In the first paragraph, A step of receiving a MAC CE for an inter-UE coordination (IUC) request from the second device; and Further comprising a step of transmitting a MAC CE including IUC information to the second device; The second carrier from which the MAC CE for the IUC request is received is selected as a carrier for transmission of the MAC CE including the IUC information, and A method wherein the second carrier is included in the plurality of carriers. In paragraph 7, A method wherein at least one of the resource pools associated with the MAC CE including the IUC information or the resource pools associated with the MAC CE for the IUC request is selected from among a plurality of resource pools excluding a resource pool associated with discovery, a resource pool associated with an aircraft-to-everything (A2X) service, and a dedicated resource pool associated with a sidelink (SL) positioning reference signal (PRS). In paragraph 7, A method in which a carrier is included in a candidate carrier based on a CBR (channel busy ratio) for a carrier other than the first carrier and the second carrier among the plurality of carriers being lower than a threshold value. In paragraph 9, A method wherein the candidate carrier comprises one or more carriers for transmission of available data of a logical channel. In paragraph 9, A method in which a third carrier is selected as a carrier for transmission of available data of a logical channel based on the lowest CBR of one or more carriers included in the candidate carriers. In paragraph 7, A method in which CBR measurements are not performed for each of the first carrier associated with the MAC CE for the CSI reporting and the second carrier associated with the MAC CE including the IUC information. In the first paragraph, A method in which a MAC CE for CSI reporting is transmitted to the second device based on the establishment of a unicast connection between the first device and the second device. In the first device, At least one transmitter/receiver; at least one processor; and At least one memory connected to said at least one processor and storing instructions, said instructions being executed by said at least one processor, wherein said first device causes: Obtain information related to a plurality of carriers including a first carrier; From a second device, receive a first SCI for scheduling a physical sidelink shared channel (PSSCH) and a second SCI (sidelink control information) through a physical sidelink control channel (PSCCH); Receive the second SCI including information for a CSI (channel state information) request from the second device through the PSSCH; and Transmit the MAC (medium access control) CE (control element) for CSI reporting to the second device, The MAC CE for the CSI report is a first device, which is transmitted on the first carrier on which information for the CSI request is received. In a processing device set to control a first device, at least one processor; and At least one memory connected to said at least one processor and storing instructions, said instructions being executed by said at least one processor, wherein said first device causes: Obtain information related to a plurality of carriers including a first carrier; From a second device, receive a first SCI for scheduling a physical sidelink shared channel (PSSCH) and a second SCI (sidelink control information) through a physical sidelink control channel (PSCCH); Receive the second SCI including information for a CSI (channel state information) request from the second device through the PSSCH; and Transmit the MAC (medium access control) CE (control element) for CSI reporting to the second device, A processing device, wherein the MAC CE for the CSI report is transmitted on the first carrier on which information for the CSI request is received. A non-transitory computer-readable storage medium that records commands, The above commands, when executed, cause the first device to: Obtain information related to a plurality of carriers including a first carrier; From a second device, receive a first SCI for scheduling a physical sidelink shared channel (PSSCH) and a second SCI (sidelink control information) through a physical sidelink control channel (PSCCH); Receive the second SCI including information for a CSI (channel state information) request from the second device through the PSSCH; and Transmit the MAC (medium access control) CE (control element) for CSI reporting to the second device, A non-transitory computer-readable storage medium, wherein the MAC CE for the CSI report is transmitted on the first carrier on which information for the CSI request is received. In terms of method, A step of the second device obtaining information related to a plurality of carriers including the first carrier; A step of the second device transmitting, to the first device, a first SCI for scheduling a physical sidelink shared channel (PSSCH) and a second SCI (sidelink control information) through a physical sidelink control channel (PSCCH); A step of transmitting, to the first device, the second SCI including information for a CSI (channel state information) request through the PSSCH; and A step of receiving a MAC (medium access control) CE (control element) for CSI reporting from the first device; A method wherein the MAC CE for the CSI report is transmitted by the first device on the first carrier through which information for the CSI request is received by the first device. In the second device, At least one transmitter/receiver; at least one processor; and At least one memory connected to said at least one processor and storing instructions, said instructions being executed by said at least one processor, wherein said second device causes: Obtain information related to a plurality of carriers including a first carrier; As a first device, transmit a first SCI for scheduling a physical sidelink shared channel (PSSCH) and a second SCI (sidelink control information) through a physical sidelink control channel (PSCCH); To the first device, transmit the second SCI including information for a CSI (channel state information) request through the PSSCH; and To receive a MAC (medium access control) CE (control element) for CSI reporting from the first device, A second device, wherein the MAC CE for the CSI report is transmitted by the first device on the first carrier through which information for the CSI request is received by the first device. In a processing device set to control a second device, at least one processor; and At least one memory connected to said at least one processor and storing instructions, said instructions being executed by said at least one processor, wherein said second device causes: Obtain information related to a plurality of carriers including a first carrier; As a first device, transmit a first SCI for scheduling a physical sidelink shared channel (PSSCH) and a second SCI (sidelink control information) through a physical sidelink control channel (PSCCH); To the first device, transmit the second SCI including information for a CSI (channel state information) request through the PSSCH; and To receive a MAC (medium access control) CE (control element) for CSI reporting from the first device, A processing device, wherein the MAC CE for the CSI report is transmitted by the first device on the first carrier on which information for the CSI request is received by the first device. A non-transitory computer-readable storage medium that records commands, The above commands, when executed, cause the second device to: Obtain information related to a plurality of carriers including a first carrier; As a first device, transmit a first SCI for scheduling a physical sidelink shared channel (PSSCH) and a second SCI (sidelink control information) through a physical sidelink control channel (PSCCH); To the first device, transmit the second SCI including information for a CSI (channel state information) request through the PSSCH; and To receive a MAC (medium access control) CE (control element) for CSI reporting from the first device, A non-transitory computer-readable storage medium in which the MAC CE for the CSI report is transmitted by the first device on the first carrier through which information for the CSI request is received by the first device.