Patent Description:
Sidelink (SL) communication is a communication scheme in which a direct link is established between User Equipments (UEs) and the UEs exchange voice and data directly with each other without intervention of an evolved Node B (eNB). SL communication is under consideration as a solution to the overhead of an eNB caused by rapidly increasing data traffic.

Vehicle-to-everything (V2X) refers to a communication technology through which a vehicle exchanges information with another vehicle, a pedestrian, an object having an infrastructure (or infra) established therein, and so on. The V2X may be divided into <NUM> types, such as vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-network (V2N), and vehicle-to-pedestrian (V2P). The V2X communication may be provided via a PC5 interface and/or Uu interface.

Regarding V2X communication, a scheme of providing a safety service, based on a V2X message such as BSM(Basic Safety Message), CAM(Cooperative Awareness Message), and DENM(Decentralized Environmental Notification Message) is focused in the discussion on the RAT used before the NR. The V2X message may include position information, dynamic information, attribute information, or the like. For example, a UE may transmit a periodic message type CAM and/or an event triggered message type DENM to another UE.

For example, the CAM may include dynamic state information of the vehicle such as direction and speed, static data of the vehicle such as a size, and basic vehicle information such as an exterior illumination state, route details, or the like. For example, the UE may broadcast the CAM, and latency of the CAM may be less than <NUM>. For example, the UE may generate the DENM and transmit it to another UE in an unexpected situation such as a vehicle breakdown, accident, or the like. For example, all vehicles within a transmission range of the UE may receive the CAM and/or the DENM. In this case, the DENM may have a higher priority than the CAM.

Thereafter, regarding V2X communication, various V2X scenarios are proposed in NR. For example, the various V2X scenarios may include vehicle platooning, advanced driving, extended sensors, remote driving, or the like.

For example, based on the vehicle platooning, vehicles may move together by dynamically forming a group. For example, in order to perform platoon operations based on the vehicle platooning, the vehicles belonging to the group may receive periodic data from a leading vehicle. For example, the vehicles belonging to the group may decrease or increase an interval between the vehicles by using the periodic data.

For example, based on the advanced driving, the vehicle may be semi-automated or fully automated. For example, each vehicle may adjust trajectories or maneuvers, based on data obtained from a local sensor of a proximity vehicle and/or a proximity logical entity. In addition, for example, each vehicle may share driving intention with proximity vehicles.

For example, based on the extended sensors, raw data, processed data, or live video data obtained through the local sensors may be exchanged between a vehicle, a logical entity, a UE of pedestrians, and/or a V2X application server. Therefore, for example, the vehicle may recognize a more improved environment than an environment in which a self-sensor is used for detection.

For example, based on the remote driving, for a person who cannot drive or a remote vehicle in a dangerous environment, a remote driver or a V2X application may operate or control the remote vehicle. For example, if a route is predictable such as public transportation, cloud computing based driving may be used for the operation or control of the remote vehicle. In addition, for example, an access for a cloud-based back-end service platform may be considered for the remote driving.

Meanwhile, a scheme of specifying service requirements for various V2X scenarios such as vehicle platooning, advanced driving, extended sensors, remote driving, or the like is discussed in NR-based V2X communication. For example, the 3GPP article "<NPL>) discusses SL HARQ protocol aspects for NR- based V2X communication. According to a proposal, a SL grant received with a toggled New Data Indicator (NDI) value compared to the NDI value of a last received SL grant for the same HARQ process Identifier (ID) allocates SL resources for an initial HARQ transmission.

According to an embodiment, a method of operating a first apparatus <NUM> in a wireless communication system with the features of claim <NUM> is proposed. Also, a first apparatus <NUM> for performing wireless communication with the features of claim <NUM> is proposed.

The user equipment (UE) can efficiently perform SL communication.

In the present specification, "A or B" may mean "only A", "only B" or "both A and B. " In other words, in the present specification, "A or B" may be interpreted as "A and/or B". For example, in the present specification, "A, B, or C" may mean "only A", "only B", "only C", or "any combination of A, B, C".

A slash (/) or comma used in the present specification may mean "and/or". For example, "A, B, C" may mean "A, B, or C".

In the present specification, "at least one of A and B" may mean "only A", "only B", or "both A and B". In addition, in the present specification, the expression "at least one of A or B" or "at least one of A and/or B" may be interpreted as "at least one of A and B".

In addition, in the present specification, "at least one of A, B, and C" may mean "only A", "only B", "only C", or "any combination of A, B, and C". In addition, "at least one of A, B, or C" or "at least one of A, B, and/or C" may mean "at least one of A, B, and C".

In addition, a parenthesis used in the present specification may mean "for example". Specifically, when indicated as "control information (PDCCH)", it may mean that "PDCCH" is proposed as an example of the "control information". In other words, the "control information" of the present specification is not limited to "PDCCH" and "PDCCH" may be proposed as an example of the "control information". In addition, when indicated as "control information (i.e., PDCCH)", it may also mean that "PDCCH" is proposed as an example of the "control information".

A technical feature described individually in one figure in the present specification may be individually implemented, or may be simultaneously implemented.

Layers of a radio interface protocol between the UE and the network can be classified into a first layer (layer <NUM>, L1), a second layer (layer <NUM>, L2), and a third layer (layer <NUM>, L3) based on the lower three layers of the open system interconnection (OSI) model that is well-known in the communication system. Among them, a physical (PHY) layer belonging to the first layer provides an information transfer service by using a physical channel, and a radio resource control (RRC) layer belonging to the third layer serves to control a radio resource between the UE and the network. For this, the RRC layer exchanges an RRC message between the UE and the BS.

<FIG> shows a radio protocol architecture, based on an embodiment of the present disclosure. Specifically, (a) of <FIG> shows a radio protocol stack of a user plane for Uu communication, and (b) of <FIG> shows a radio protocol stack of a control plane for Uu communication. (c) of <FIG> shows a radio protocol stack of a user plane for SL communication, and (d) of <FIG> shows a radio protocol stack of a control plane for SL communication.

A radio resource control (RRC) layer is defined only in the control plane. The RRC layer serves to control the logical channel, the transport channel, and the physical channel in association with configuration, reconfiguration and release of RBs. The RB is a logical path provided by the first layer (i.e., the physical layer or the PHY layer) and the second layer (i.e., a MAC layer, an RLC layer, a packet data convergence protocol (PDCP) layer, and a service data adaptation protocol (SDAP) layer) for data delivery between the UE and the network.

<FIG> shows a structure of a radio frame of an NR, based on an embodiment of the present disclosure.

Table <NUM> shown below represents an example of a number of symbols per slot (Nslotsymb), a number slots per frame (Nframe,uslot), and a number of slots per subframe (Nsubframe,uslot) based on an SCS configuration (u), in a case where a normal CP is used.

The BWP may be a set of consecutive physical resource blocks (PRBs) in a given numerology. The PRB may be selected from consecutive sub-sets of common resource blocks (CRBs) for the given numerology on a given carrier.

Meanwhile, the BWP may be defined for SL. The same SL BWP may be used in transmission and reception. For example, a transmitting UE may transmit an SL channel or an SL signal on a specific BWP, and a receiving UE may receive the SL channel or the SL signal on the specific BWP. In a licensed carrier, the SL BWP may be defined separately from a Uu BWP, and the SL BWP may have configuration signaling separate from the Uu BWP. For example, the UE may receive a configuration for the SL BWP from the BS/network. For example, the UE may receive a configuration for the Uu BWP from the BS/network. The SL BWP may be (pre-)configured in a carrier with respect to an out-of-coverage NR V2X UE and an RRC_IDLE UE. For the UE in the RRC_CONNECTED mode, at least one SL BWP may be activated in the carrier.

A sidelink synchronization signal (SLSS) may include a primary sidelink synchronization signal (PSSS) and a secondary sidelink synchronization signal (SSSS), as an SL-specific sequence. The PSSS may be referred to as a sidelink primary synchronization signal (S-PSS), and the SSSS may be referred to as a sidelink secondary synchronization signal (S-SSS). For example, length-<NUM>-sequences may be used for the S-PSS, and length-<NUM> gold sequences may be used for the S-SSS. For example, a UE may use the S-PSS for initial signal detection and for synchronization acquisition. For example, the UE may use the S-PSS and the S-SSS for acquisition of detailed synchronization and for detection of a synchronization signal ID.

A physical sidelink broadcast channel (PSBCH) may be a (broadcast) channel for transmitting default (system) information which must be first known by the UE before SL signal transmission/reception. For example, the default information may be information related to SLSS, a duplex mode (DM), a time division duplex (TDD) uplink/downlink (UL/DL) configuration, information related to a resource pool, a type of an application related to the SLSS, a subframe offset, broadcast information, or the like. For example, for evaluation of PSBCH performance, in NR V2X, a payload size of the PSBCH may be <NUM> bits including <NUM>-bit cyclic redundancy check (CRC).

<FIG> shows a UE performing V2X or SL communication, based on an embodiment of the present disclosure.

Referring to <FIG>, in V2X or SL communication, the term 'UE' may generally imply a UE of a user. However, if a network equipment such as a BS transmits/receives a signal according to a communication scheme between UEs, the BS may also be regarded as a sort of the UE. For example, a UE <NUM> may be a first apparatus <NUM>, and a UE <NUM> may be a second apparatus <NUM>.

<FIG> shows a procedure of performing V2X or SL communication by a UE based on a transmission mode, based on an embodiment of the present disclosure. In various embodiments of the present disclosure, the transmission mode may be called a mode or a resource allocation mode. Hereinafter, for convenience of explanation, in LTE, the transmission mode may be called an LTE transmission mode. In NR, the transmission mode may be called an NR resource allocation mode.

For example, (a) of <FIG> shows a UE operation related to an LTE transmission mode <NUM> or an LTE transmission mode <NUM>. Alternatively, for example, (a) of <FIG> shows a UE operation related to an NR resource allocation mode <NUM>. For example, the LTE transmission mode <NUM> may be applied to general SL communication, and the LTE transmission mode <NUM> may be applied to V2X communication.

For example, (b) of <FIG> shows a UE operation related to an LTE transmission mode <NUM> or an LTE transmission mode <NUM>. Alternatively, for example, (b) of <FIG> shows a UE operation related to an NR resource allocation mode <NUM>.

Referring to (a) of <FIG>, in the LTE transmission mode <NUM>, the LTE transmission mode <NUM>, or the NR resource allocation mode <NUM>, a BS may schedule an SL resource to be used by the UE for SL transmission. For example, the BS may perform resource scheduling to a UE <NUM> through a PDCCH (e.g., downlink control information (DCI)) or RRC signaling (e.g., Configured Grant Type <NUM> or Configured Grant Type <NUM>), and the UE <NUM> may perform V2X or SL communication with respect to a UE <NUM> according to the resource scheduling. For example, the UE <NUM> may transmit a sidelink control information (SCI) to the UE <NUM> through a physical sidelink control channel (PSCCH), and thereafter transmit data based on the SCI to the UE <NUM> through a physical sidelink shared channel (PSSCH).

Referring to (b) of <FIG>, in the LTE transmission mode <NUM>, the LTE transmission mode <NUM>, or the NR resource allocation mode <NUM>, the UE may determine an SL transmission resource within an SL resource configured by a BS/network or a pre-configured SL resource. For example, the configured SL resource or the pre-configured SL resource may be a resource pool. For example, the UE may autonomously select or schedule a resource for SL transmission. For example, the UE may perform SL communication by autonomously selecting a resource within a configured resource pool. For example, the UE may autonomously select a resource within a selective window by performing a sensing and resource (re)selection procedure. For example, the sensing may be performed in unit of subchannels. In addition, the UE <NUM> which has autonomously selected the resource within the resource pool may transmit the SCI to the UE <NUM> through a PSCCH, and thereafter may transmit data based on the SCI to the UE <NUM> through a PSSCH.

<FIG> shows three cast types, based on an embodiment of the present disclosure. Specifically, (a) of <FIG> shows broadcast-type SL communication, (b) of <FIG> shows unicast type-SL communication, and (c) of <FIG> shows groupcast-type SL communication. In case of the unicast-type SL communication, a UE may perform one-to-one communication with respect to another UE. In case of the groupcast-type SL transmission, the UE may perform SL communication with respect to one or more UEs in a group to which the UE belongs. In various embodiments of the present disclosure, SL groupcast communication may be replaced with SL multicast communication, SL one-to-many communication, or the like.

Meanwhile, in various embodiments of the present disclosure, a transmitting UE (i.e., TX UE) may be a UE which transmits data to (target) receiving UE(s) (i.e., RX UE(s)). For example, the TX UE may be a UE which performs PSCCH transmission and/or PSSCH transmission. For example, the TX UE may be a UE which transmits SL CSI-RS(s) and/or a SL CSI report request indication to (target) RX UE(s). For example, the TX UE may be a UE which transmits a (pre-defined) reference signal(s) (e.g., PSSCH demodulation reference signal (DM-RS)) and/or SL (L1) RSRP report request indicator, which is/are used for SL (L1) RSRP measurement, to (target) to RX UE(s). For example, the TX UE may be a UE which transmits a (control) channel (e.g., PSCCH, PSSCH, etc.) and/or reference signal(s) (e.g., DM-RS(s), CSI-RS(s), etc.) through the (control) channel, which is/are used for SL radio link monitoring (RLM) operation(s) and/or SL radio link failure (RLF) operation(s) of (target) RX UE(s).

Meanwhile, in various embodiments of the present disclosure, a receiving UE (i.e., RX UE) may be a UE which transmits SL HARQ feedback to transmitting UE(s) (i.e., TX UE(s)), based on whether or not data transmitted by TX UE(s) is decoded successfully and/or whether or not a PSCCH (related to PSSCH scheduling) transmitted by TX UE(s) is detected/decoded successfully. For example, the RX UE may be a UE which performs SL CSI transmission to TX UE(s) based on SL CSI-RS(s) and/or a SL CSI report request indication received from TX UE(s). For example, the RX UE may be a UE which transmits, to TX UE(s), an SL (L1) RSRP measurement value measured based on (pre-defined) reference signal(s) and/or SL (L1) RSRP report request indication received from TX UE(s). For example, the RX UE may be a UE which transmits its own data to TX UE(s). For example, the RX UE may be a UE which performs SL RLM operation(s) and/or SL RLF operation(s) based on a (pre-configured) (control) channel and/or reference signal(s) through the (control) channel received from TX UE(s).

Meanwhile, in various embodiments of the present disclosure, when a receiving UE transmits SL HARQ feedback information for a PSSCH and/or a PSCCH received from a transmitting UE, the following method may be considered or partly considered. Here, for example, the corresponding scheme or some schemes may be limitedly applied only when a receiving UE successfully decodes/detects a PSCCH for scheduling a PSSCH.

Meanwhile, in various embodiments of the present disclosure, for example, a TX UE may transmit at least one of the following information to an RX UE through SCI. Here, for example, a TX UE may transmit at least one of the following information to an RX UE through first SCI and/or second SCI.

Meanwhile, in various embodiments of the present disclosure, for example, a PSCCH may be replaced/substituted with at least one of a SCI, a first SCI (<NUM>st-stage SCI), and/or a second SCI (<NUM>nd-stage SCI), or vice versa. For example, a SCI may be replaced/substituted with at least one of a PSCCH, a first SCI, and/or a second SCI, or vice versa. For example, a PSSCH may be replaced/substituted with a second SCI and/or a PSCCH, or vice versa, since a transmitting UE may transmit second SCI to a receiving UE through PSSCH. for example, if SCI configuration fields are divided into two groups in consideration of a (relatively) high SCI payload size, an SCI including a first SCI configuration field group may be referred to as a first SCI or a <NUM>st SCI, and an SCI including a second SCI configuration field group may be referred to as a second SCI or a <NUM>nd SCI. For example, the <NUM>st SCI and the <NUM>nd SCI may be transmitted through different channels. For example, the transmitting UE may transmit the first SCI to the receiving UE through the PSCCH. For example, the second SCI may be transmitted to the receiving UE through an (independent) PSCCH, or may be transmitted in a piggyback manner together with data through the PSSCH.

On the other hand, in various embodiments of the present disclosure, for example, "configuration" or "definition" may mean (resource pool specific) (pre-)configuration (through predefined signaling (e.g., SIB, MAC, RRC, etc.)) from a base station or a network. For example, "A is configured" may mean "a base station/network transmits information related to A to a UE". Or, for example, "A is configured" may mean "A is designated through pre-defined signaling (e.g., PC5 RRC) between UEs".

Meanwhile, in various embodiments of the present disclosure, for example, "RLF" may be interpreted as mutually extended to at least one of out of synch (OOS) and in synch (IS). Meanwhile, in various embodiments of the present disclosure, for example, a resource block (RB) may be replaced/substituted with a subcarrier, or vice versa. For example, a packet or a traffic may be replaced/substituted with a transport block (TB) or a medium access control protocol data unit (MAC PDU) according to a transmission layer, or vice versa. For example, a code block group (CBG) may be replaced/substituted with a TB, or vice versa. For example, a source ID may be replaced/substituted with a destination ID, or vice versa. For example, an L1 ID may be replaced/substituted with an L2 ID, or vice versa. For example, the L1 ID may be an L1 source ID or an L1 destination ID. For example, the L2 ID may be an L2 source ID or an L2 destination ID.

Meanwhile, in various embodiments of the present disclosure, for example, operation(s) of a TX UE to reserve/select/determine retransmission resource(s) may include operation(s) of the TX UE to reserve/select/determine potential retransmission resource(s) in which actual use is determined based on SL HARQ feedback information received from RX UE(s).

Meanwhile, in various embodiments of the present disclosure, a sub-selection window may be replaced/substituted with a selection window and/or a pre-configured number of resource sets within the selection window, or vice versa.

Meanwhile, in various embodiments of the present disclosure, SL MODE <NUM> may refer to a resource allocation method or a communication method in which a base station directly schedules SL transmission resource(s) for a TX UE through pre-defined signaling (e.g., DCI or RRC message). For example, SL MODE <NUM> may refer to a resource allocation method or a communication method in which a UE independently selects SL transmission resource(s) in a resource pool pre-configured or configured from a base station or a network. For example, a UE performing SL communication based on SL MODE <NUM> may be referred to as a MODE <NUM> UE or MODE <NUM> TX UE, and a UE performing SL communication based on SL MODE <NUM> may be referred to as a MODE <NUM> UE or MODE <NUM> TX UE.

Meanwhile, in the present disclosure, for example, a dynamic grant (DG) may be replaced/substituted with a configured grant (CG) and/or a semi-persistent scheduling (SPS) grant, or vice versa. For example, the DG may be replaced/substituted with a combination of the CG and the SPS grant, or vice versa. For example, the CG may include at least one of a configured grant (CG) type <NUM> and/or a configured grant (CG) type <NUM>. For example, in CG type <NUM>, the grant may be provided by RRC signaling and may be stored as a configured grant. For example, in CG type <NUM>, a grant may be provided by PDCCH, it may be stored or deleted as a configured grant based on L1 signaling indicating activation or deactivation of the grant. For example, in CG type <NUM>, a base station may allocate a periodic resource to a TX UE through an RRC message. For example, in CG type <NUM>, a base station may allocate a periodic resource to a TX UE through an RRC message, and a base station may dynamically activate or deactivate a periodic resource through DCI.

Meanwhile, in various embodiments of the present disclosure, a channel may be replaced/substituted with a signal, or vice versa. For example, transmission/reception of a channel may include transmission/reception of a signal. For example, transmission/reception of a signal may include transmission/reception of a channel. For example, cast may be replaced/substituted with at least one of unicast, groupcast, and/or broadcast, or vice versa. For example, a cast type may be replaced/substituted with at least one of unicast, groupcast, and/or broadcast, or vice versa.

Meanwhile, in various embodiments of the present disclosure, a resource may be replaced/substituted with a slot or a symbol, or vice versa. For example, the resource may include a slot and/or a symbol.

Meanwhile, in various embodiments of the present disclosure, a priority may be replaced/substituted with at least one of logical channel prioritization (LCP), latency, reliability, minimum required communication range, prose per-packet priority (PPPP), sidelink radio bearer (SLRB), a QoS profile, a QoS parameter, and/or requirement, or vice versa.

Meanwhile, in various embodiments of the present disclosure, for example, for convenience of description, a (physical) channel used when a RX UE transmits at least one of the following information to a TX UE may be referred to as a PSFCH.

Meanwhile, when performing sidelink communication, a method for a transmitting UE to reserve or pre-determine transmission resource(s) for receiving UE(s) may be representatively as follows.

For example, the transmitting UE may perform a reservation of transmission resource(s) based on a chain. Specifically, for example, if the transmitting UE reserves K transmission resources, the transmitting UE may transmit location information for less than K transmission resources to receiving UE(s) through a SCI transmitted to the receiving UE(s) at any (or specific) transmission time or a time resource. That is, for example, the SCI may include location information for less than the K transmission resources. Alternatively, for example, if the transmitting UE reserves K transmission resources related to a specific TB, the transmitting UE may transmit location information for less than K transmission resources to receiving UE(s) through a SCI transmitted to the receiving UE(s) at any (or specific) transmission time or a time resource. That is, the SCI may include location information for less than the K transmission resources. In this case, for example, it is possible to prevent performance degradation due to an excessive increase in payloads of the SCI, by signaling only the location information for less than K transmission resources to the receiving UE(s) through one SCI transmitted at any (or specific) transmission time or the time resource by the transmitting UE.

<FIG> shows a method in which a UE that has reserved transmission resource(s) informs another UE of the transmission resource(s), based on an embodiment of the present disclosure.

Specifically, for example, (a) of <FIG> shows a method for performing by a transmitting UE chain-based resource reservation by transmitting/signaling location information of (maximum) <NUM> transmission resources to receiving UE(s) through one SCI, in the case of a value of K = <NUM>. For example, (b) of <FIG> shows a method for performing by a transmitting UE chain-based resource reservation by transmitting/signaling location information of (maximum) <NUM> transmission resources to receiving UE(s) through one SCI, in the case of a value of K = <NUM>. For example, referring to (a) and (b) of <FIG>, the transmitting UE may transmit/signal only location information of the fourth transmission-related resource to the receiving UE(s) through the fourth (or last) transmission-related PSCCH. For example, referring to (a) of <FIG>, the transmitting UE may transmit/signal to the receiving UE(s) not only location information of the fourth transmission-related resource but also location information of the third transmission-related resource additionally through the fourth (or last) transmission-related PSCCH. For example, referring to (b) of <FIG>, the transmitting UE may transmit/signal to the receiving UE(s) not only location information of the fourth transmission-related resource but also location information of the second transmission-related resource and location information of the third transmission-related resource additionally through the fourth (or last) transmission-related PSCCH. In this case, for example, in (a) and (b) of <FIG>, if the transmitting UE may transmit/signal to the receiving UE(s) only location information of the fourth transmission-related resource through the fourth (or last) transmission-related PSCCH, the transmitting UE may configure or designate a field/bit of location information of unused or remaining transmission resource(s) to a pre-configured value (e.g., <NUM>). For example, in (a) and (b) of <FIG>, if the transmitting UE may transmit/signal to the receiving UE(s) only location information of the fourth transmission-related resource through the fourth (or last) transmission-related PSCCH, the transmitting UE may be configured or designate a field/bit of location information of unused or remaining transmission resource(s) to a pre-configured status/bit value indicating/representing the last transmission (among <NUM> transmissions).

Meanwhile, for example, the transmitting UE may perform a reservation of transmission resource(s) based on a block. Specifically, for example, if the transmitting UE reserves K transmission resources, the transmitting UE may transmit location information for K transmission resources to receiving UE(s) through a SCI transmitted to the receiving UE(s) at any (or specific) transmission time or a time resource. That is, the SCI may include location information for K transmission resources. For example, if the transmitting UE reserves K transmission resources related to a specific TB, the transmitting UE may transmit location information for K transmission resources to receiving UE(s) through a SCI transmitted to the receiving UE(s) at any (or specific) transmission time or a time resource. That is, the SCI may include location information for K transmission resources. For example, (c) of <FIG> shows a method for performing by the transmitting UE block-based resource reservation, by signaling location information of <NUM> transmission resources to receiving UE(s) through one SCI, in the case of a value of K = <NUM>.

According to an embodiment of the present disclosure, when a mode (MODE) <NUM> UE performs TB transmission using an SL resource within a specific CG period, and/or when it performs TB transmission using SL retransmission resources additionally allocated through mode <NUM> DG downlink control information (DCI), linked with SL resources within a specific CG period, whether to toggling a new data indicator (NDI) on the SCI related to TB transmission may be configured to be determined according to the (part of) following rules. For example, the TB transmission may be an initial transmission or a retransmission. And, for example, it may be determined whether to designate an NDI value and/or designate/change an SL HARQ PROCESS ID according to the (part of) following rules. For example, in the present disclosure, SL HARQ PROCESS ID may mean SL PROCESS ID.

According to an embodiment of the present disclosure, when a CG period is changed, an NDI value on TB-related SCI transmitted through a (changed) "SL resource interlocked with a CG period (REL_CGRSC)" may be toggled. For example, (option <NUM>-A) toggling an NDI value may be toggling compared to an NDI value on REL_CGRSC-related SCI of the previous CG period. Or, for example, (option <NUM>-B) toggling an NDI value may be toggling compared to an NDI value on the previous nearest REL_CGRSC related SCI where an actual TB transmission was performed. For example, in the present disclosure, "REL_CGRSC" may be interpreted (limitedly) as a CG resource configured within a CG period and/or an SL retransmission resource additionally allocated through mode <NUM> DG DCI linked with a CG resource configured within a CG period. For example, in the present disclosure, only one TB transmission is possible through REL_CGRSC, in addition, it may be assumed that different TB transmissions are performed between different REL_CGRSCs. For example, in the Option <NUM>-A scheme (and/or Option <NUM>-B scheme) above, a change of CG periods of the pre-configured number of times may be interpreted as a factor for toggling an NDI value on SCI. For example, when applying the rules of Option <NUM>-A and/or Option <NUM>-B above, if different TB transmissions are performed using REL_CGRSC with different HARQ PROCESS IDs (HPN_DCI), SL HARQ PROCESS ID (HPN_SCI) designated on REL_CGRSC-related SCI of different HPN_DCI may be mapped/specified differently (e.g., one-to-one mapping). For example, a HARQ PROCESS ID may be derived through a predefined formula. For example, the predefined formula may include Equation <NUM> below.

For example, HPN_DCI may be used to indicate linkage between a CG resource configured within a CG period and an SL retransmission resource additionally allocated through mode <NUM> DG DCI. For example, the HPN_DCI may be signaled through a predefined field on the mode <NUM> DG DCI.

According to an embodiment of the present disclosure, NDI values on different TB-related SCIs transmitted through REL_CGRSC related to different CG periods may be determined differently according to a mapping method between "REL_CGRSC-related HPN_DCI" and "HPN_SCI on TB-related SCI transmitted using (corresponding) REL_CGRSC". For example, whether the NDI values on the different TB-related SCIs are TOGGLED may also be determined differently according to a mapping method between the HPN_DCI and the HPN_SCI. For example, NDI values on different TB-related SCIs transmitted through REL_CGRSC having different HPN_DCI to which the same HPN_SCI value is mapped may be configured to be toggled. For example, NDI values on different TB-related SCIs transmitted through REL_CGRSC with different HPN_DCIs to which different HPN_SCI values are mapped may be configured not to be toggled, or to be untoggled. For example, a rule in which NDI values on different TB-related SCIs are determined according to the above-described mapping method between HPN_DCI and HPN_SCI may be limitedly applied only when a PUCCH resource is not configured (or configured) for a mode <NUM> CG resource. For example, the PUCCH resource may be for the purpose of requesting additional retransmission resources. For example, when the same HPN_SCI value is mapped to a plurality of REL_CGRSCs having different HPN_DCIs, a UE may not expect that a mode <NUM> CG resource related PUCCH resource is configured.

According to an embodiment of the present disclosure, depending on whether a PUCCH resource is configured for a mode <NUM> CG resource, the mapping method between allowed "REL_CGRSC-related HPN_DCI" and "HPN_SCI on TB-related SCI transmitted using (corresponding) REL_CGRSC" may be configured differently. Here, for example, when a PUCCH resource is configured, HPN_SCI designated on REL_CGRSC-related SCI of different HPN_DCI may be mapped/specified differently (e.g., one-to-one mapping). On the other hand, for example, if a PUCCH resource is not configured, on REL_CGRSC-related SCIs of different HPN_DCIs, HPN_SCI mapping/designation of the same value (e.g., many to one mapping) may be allowed.

According to an embodiment of the present disclosure, REL_CGRSC until REL_CGRSC of HPN_DCI#X reappears, for example, from REL_CGRSC related to CG period of HPN_DCI#X to REL_CGRSC related to CG period of HPN_DCI#(X + HPNDCI_NUM - <NUM>), all NDI values on the related SCI are configured to have the same toggling state (and/or value). Here, for example, X may be a pre-configured value (e.g., <NUM>). For example, from a REL_CGRSC related to a CG period of HPN_DCI#X that reappeared after a CG period of HPN_DCI#(X + HPNDCI_NUM - <NUM>), to a REL_CGRSC relative to a CG period of HPN_DCI#(X + HPNDCI_NUM - <NUM>), an NDI value on related SCI is toggled (vs. before). Here, for example, "HPNDCI_NUM" means the (maximum) number of (SL) HARQ PROCESS (IDs) configured for a mode <NUM> CG resource. For example, the (maximum) number of the (SL) HARQ PROCESS (ID) may mean the (maximum) number of HPN_SCIs or the (maximum) number of HPN_DCIs.

<FIG> shows an example in which an NDI value is toggled according to an embodiment of the present disclosure.

Referring to <FIG>, in the first CG period, HPN_DCI may be HPN_DCI#A. For example, in the first CG period, REL_CGRSC-related HPN_SCI of HPN_DCI#A may be HPN_SCI#a. For example, in <FIG>, HPN_DCI and HPN_SCI may have a one-to-one mapping relationship in each CG period. For example, an NDI value on REL_CGRSC related SCI of HPN_DCI#A in the first CG period may be <NUM> or <NUM>. For example, the HPN_DCI#A may be determined based on a first resource among three resources included in the REL_CGRSC of the first CG period. For example, a first TB may be initially transmitted to a receiving UE based on one of three resources included in the REL_CGRSC of the first CG period.

For example, HPN_DCI related to DCI-based DG resource related to retransmission of a first TB initially transmitted in the first CG period of <FIG> may be HPN_DCI#A. And, HPN_SCI related to the DG resource may be HPN_SCI#a. That is, even if a CG period is changed, HPN_DCI and HPN_SCI related to resources related to retransmission of the first TB are maintained the same. For example, HPN_DCI related to the DG resource may be indicated through the DCI. And, for example, an NDI value on the SCI related to the retransmission of the first TB may be the same as the NDI value on the SCI related to the initial transmission. That is, for example, since the NDI value on the REL_CGRSC related SCI of HPN_DCI#A in the first CG period is <NUM> or <NUM>, the NDI value on the SCI related to the retransmission of the initially transmitted first TB in <FIG> may be: <NUM> if the NDI value on the REL_CGRSC related SCI of HPN_DCI#A is <NUM>; Or, <NUM> if the NDI value on the REL_CGRSC related SCI of HPN_DCI#A is <NUM>.

For example, in the second CG period and/or the fourth CG period in <FIG>, HPN_DCI may be determined based on the first resource among three resources included in each REL_CGRSC. For example, HPN_DCI of the second CG period may be HPN_DCI#B, and HPN_DCI of the fourth CG period may be HPN_DCI#X. And, HPN_DCI#B, HPN_DCI#X REL_CGRSC-related HPN_SCI of each may be HPN_SCI#b, HPN_SCI#x, and as described above, HPN_SCI#b and HPN_SCI#x may have a one-to-one mapping relationship with HPN_DCI#B and HPN_DCI#X, respectively.

For example, in the fifth CG period of <FIG>, HPN_DCI determined based on the first resource among three resources included in REL_CGRSC is HPN_DCI#A, it is equal to HPN_DCI#A related to the first CG period. For example, in this case, in the fifth CG period due to the one-to-one mapping relationship, HPN_SCI related to HPN_DCI#A may be HPN_SCI#a. In this case, for example, retransmission of the first TB initially transmitted in the first CG period cannot be performed any more. In the fifth CG period, a second TB may be initially transmitted. Here, when the initial transmission of the second TB is transmitted to the same receiving UE that received the first TB, an NDI value on SCI related to the second TB is a value toggled from the NDI value on the SCI related to the retransmission of the first TB. For example, when the NDI value on the SCI related to the retransmission of the first TB is <NUM>, the NDI value on the SCI related to the second TB may be <NUM>, or when the NDI value on the SCI related to the retransmission of the first TB is <NUM>, the NDI value on the SCI related to the second TB may be <NUM>.

According to an embodiment of the present disclosure, an NDI value on REL_CGRSC related SCI of HPN_DCI#Y may be toggled (compared to the previous one) when REL_CGRSC of the same HPN_DCI#Y appears again. Here, for example, the NDI value may be toggled (compared to the previous one) when a REL_CGRSC of the same HPN_DCI#Y reappears a pre-configured number of times. For example, a rule related to the reappearance of REL_CGRSC of HPN_DCI#Y may be independently applied/operated for each REL_CGRSC of different HPN_DCI.

According to an embodiment of the present disclosure, when a (pre-configured) timer value related to HPN_DCI#Z expires, an NDI value on a REL_CGRSC related SCI of HPN_DCI#Z may be toggled (compared to the previous one). Here, for example, a timer value of HPN_DCI#Z may mean a time during which a UE can expect DG DCI reception for allocating additional retransmission resources related to HPN_DCI#Z from a base station. Also, for example, when a timer value related to HPN_DCI#Z expires, a new transport block (TB) (compared to the previous) transmission may be performed through an HPN_DCI#Z related REL_CGRSC. For example, when a new TB transmission is performed, a UE may perform a new TB transmission after flushing a HPN_DCI#Z related buffer/MAC PDU.

According to an embodiment of the present disclosure, when TB transmission is performed through REL_CGRSC related to a specific CG period, whether to toggle an NDI on relevant SCI, designation of an NDI value, designation of an HPN_SCI value, and/or designation of an L1 ID (e.g., source/destination ID) may be made to be determined by a UE implementation.

According to an embodiment of the present disclosure, when a mode <NUM> UE performs TB transmission through REL_CGRSC related to a specific CG period, whether to toggle an NDI on relevant SCI, designation of an NDI value, and/or designation of an HPN_SCI value may be determined according to (a part of) the rules below.

For example, when a TX UE performs different TB transmissions with respect to the same target RX UE (and/or an RX UE related to the same session, and/or an RX UE related to the same cast type), using different CG period-related REL_CGRSC (and/or when a TX UE uses the same L1 (or L2) source ID and L1 (or L2) destination ID to perform different TB transmissions through different CG period-related REL_CGRSC), on REL_CGRSC-related SCIs of different CG periods, different HPN_SCI values (and/or the same (or different) NDI values) may be designated.

For example, when a TX UE performs different TB transmissions for different target RX UEs (and/or an RX UE related to the same session, and/or an RX UE related to the same cast type) by using different CG period-related REL_CGRSC (and/or when a TX UE uses the same L1 (or L2) source ID and L1 (or L2) destination ID to perform different TB transmissions through different CG period-related REL_CGRSC), in REL_CGRSC-related SCI of different CG periods, an HPN_SCI value and an NDI value may be identically (or differently) designated (or an HPN_SCI value may be designated as the same (or different), and an NDI value may be designated as different (or the same)).

For example, when a TX UE performs (TB) retransmission for the same target RX UE (and/or an RX UE related to the same session, and/or an RX UE related to the same cast type) by using REL_CGRSC related to a specific CG period (and/or when a TX UE performs retransmission (e.g., retransmission of TB) using the same L1 (or L2) source ID and L1 (or L2) destination ID), an HPN_SCI value and an NDI value may be identically designated on SCI.

According to an embodiment of the present disclosure, during mode <NUM> CG operation, when TB transmission is performed through retransmission resources (ADD_RRSC) additionally allocated through DG DCI, an NDI value on related SCI may be designated according to the rule below. For example, during mode <NUM> CG operation, when TB transmission is performed through a retransmission resource (ADD_RRSC) additionally allocated through DG DCI, whether to toggle NDI may also be determined according to the rule below.

For example, an NDI value on REL_CGRSC (LINK_CGRSC) related SCI (e.g., of a specific CG period) linked with ADD_RRSC may be configured to be used/maintained in the same way in an NDI on the ADD_RRSC related SCI. Here, for example, LINK_CGRSC may be derived through information such as CG index and/or HPN_DCI on the DG DCI scheduling ADD_RRSC, etc..

According to an embodiment of the present disclosure, a mode <NUM> UE may be configured to report the (part of) following information to a (serving) base station through predefined signaling. For example, the predefined signaling may include an RRC message and/or a medium access control (MAC) control element (CE).

Table <NUM> shows a procedure for flushing a HARQ buffer of a sidelink process.

Referring to Table <NUM>, with respect to a sidelink grant occurring within a PSSCH period, when a configured sidelink grant is activated, and when a sidelink grant occurring within a PSSCH period corresponds to the first PSSCH transmission opportunity in a sidelink CG period of the configured sidelink grant, a MAC layer of a UE in each PSSCH duration: i) may configure a HARQ process ID as a HARQ process ID related to the PSSCH period, and if possible, may also configure HARQ process IDs related to all subsequent PSSCH sections occurring within the sidelink CG period for the configured sidelink grant as HARQ process IDs related to the PSSCH section, ii) may determine that the PSSCH period is used for initial transmission, iii) may flush a HARQ buffer of a sidelink process related to the HARQ process ID. For example, in the configured sidelink grant, a HARQ process ID related to the first slot of SL transmission may be determined based on the above equation.

Table <NUM> shows a procedure for toggling NDI.

Referring to <FIG>, for each sidelink grant, when a sidelink grant is a configured sidelink grant and a MAC PDU is not obtained within a sidelink CG period of the configured sidelink grant, a sidelink HARQ entity may associate a sidelink process with this grant. And, for the associated sidelink process, the sidelink HARQ entity may obtain a MAC PDU to be transmitted, and if a HARQ process ID for the sidelink grant is configured, it may associate the sidelink process with the HARQ process ID for the sidelink grant. In addition, the sidelink HARQ entity may determine sidelink transmission information of a TB for a source/destination pair of the MAC PDU, it may i) configure an L1 source ID to <NUM> LSB of an L2 source ID of a MAC PDU, ii) configure an L1 destination ID to <NUM> LSB of an L2 destination ID of a MAC PDU, iii) associate the sidelink process with a sidelink process ID, iv) compare the sidelink identification information with a value of the previous (same) transmission corresponding to a sidelink process ID of a MAC PDU, and considers it a toggled NDI, and may configure an NDI to the toggled value.

<FIG> shows a procedure in which a first apparatus performs wireless communication, according to an embodiment of the present disclosure.

Referring to <FIG>, in step S1210, a first apparatus receives a configured grant from a base station. In step S1220, the first apparatus obtains a first hybrid automatic repeat request, HARQ, process identifier, ID, related to a first period of the configured grant. In step, S1230, the first apparatus transmits a first physical sidelink shared channel, PSSCH, to a second apparatus, based on a first resource included in the first period. In step S1240, the first apparatus obtains a second HARQ process ID related to a second period of the configured grant. For example, the second HARQ process ID related to the second period may be the same as the first HARQ process ID. In step S1250, the first apparatus transmits a second PSSCH to the second apparatus, based on a second resource included in the second period. For example, a new data indicator, NDI, related to the second PSSCH is a value to which a NDI related to the first PSSCH is toggled, based on the second HARQ process ID which is the same as the first HARQ process ID.

For example, the first HARQ process ID may be mapped one-to-one with a first sidelink, SL, process ID related to the first PSSCH.

For example, the first HARQ process ID may be mapped one-to-one with the first SL process ID, based on that a resource related to a physical uplink control channel, PUCCH, related to the first PSSCH is configured.

For example, the first SL process ID may be included in first sidelink control information, SCI, related to the first PSSCH.

For example, SL identification information of the first apparatus related to the first PSSCH may be the same as SL identification information of the first apparatus related to the second PSSCH.

For example, a first SL process ID related to the first PSSCH may be the same as a second SL process ID related to the second PSSCH.

For example, additionally, the first apparatus may receive a dynamic grant including a third resource related to the first HARQ process ID from the base station; and retransmit the first PSSCH to the second apparatus, based on the third resource.

For example, an NDI related to the retransmitted first PSSCH may be the same as the NDI related to the first PSSCH.

For example, a third SL process ID related to the retransmitted first PSSCH may be the same as a first SL process ID related to the first PSSCH.

For example, additionally, the first apparatus may flush a buffer related to the second HARQ process ID, based on that the second HARQ process ID is the same as the first HARQ process ID.

For example, the buffer related to the second HARQ process ID may be flushed based on expiration of a timer related to the second HARQ process ID.

For example, additionally, the first apparatus may report a mapping relationship related to the first HARQ process ID and a first SL process ID related to the first PSSCH.

For example, the mapping relationship may be reported through a radio resource control, RRC, message or a medium access control, MAC, control element, CE.

The above-described embodiment may be applied to various devices to be described below. For example, a processor <NUM> of a first apparatus <NUM> may control a transceiver <NUM> to receive a configured grant from a base station. And, the processor <NUM> of the first apparatus <NUM> may obtain a first hybrid automatic repeat request, HARQ, process identifier, ID, related to a first period of the configured grant. And, the processor <NUM> of the first apparatus <NUM> may control the transceiver <NUM> to transmit a first physical sidelink shared channel, PSSCH, to a second apparatus, based on a first resource included in the first period. And, the processor <NUM> of the first apparatus <NUM> may obtain a second HARQ process ID related to a second period of the configured grant. And, the processor <NUM> of the first apparatus <NUM> may control the transceiver <NUM> to transmit a second PSSCH to the second apparatus, based on a second resource included in the second period.

According to the embodiment of the present disclosure, a first apparatus for performing wireless communication is proposed. For example, the first apparatus comprises: one or more memories storing instructions; one or more transceivers; and one or more processors connected to the one or more memories and the one or more transceivers. The one or more processors execute the instructions to: receive a configured grant from a base station; obtain a first hybrid automatic repeat request, HARQ, process identifier, ID, related to a first period of the configured grant; transmit a first physical sidelink shared channel, PSSCH, to a second apparatus, based on a first resource included in the first period; obtain a second HARQ process ID related to a second period of the configured grant, wherein the second HARQ process ID related to the second period is the same as the first HARQ process ID; and transmit a second PSSCH to the second apparatus, based on a second resource included in the second period, wherein a new data indicator, NDI, related to the second PSSCH is a value to which a NDI related to the first PSSCH is toggled, based on the second HARQ process ID which is the same as the first HARQ process ID when a CG period is changed.

According to an example of the present disclosure, an apparatus configured to control a first user equipment, UE, may be proposed. For example, the apparatus may comprise: one or more processors; and one or more memories operably connectable to the one or more processors and storing instructions. For example, the one or more processors may execute the instructions to: receive a configured grant from a base station; obtain a first hybrid automatic repeat request, HARQ, process identifier, ID, related to a first period of the configured grant; transmit a first physical sidelink shared channel, PSSCH, to a second UE, based on a first resource included in the first period; obtain a second HARQ process ID related to a second period of the configured grant, wherein the second HARQ process ID related to the second period is the same as the first HARQ process ID; and transmit a second PSSCH to the second UE, based on a second resource included in the second period, wherein a new data indicator, NDI, related to the second PSSCH is a value to which a NDI related to the first PSSCH is toggled, based on the second HARQ process ID which is the same as the first HARQ process ID.

According to a further example of the present disclosure, a non-transitory computer-readable storage medium storing instructions may be proposed. For example, the instructions, when executed, may cause a first apparatus to: receive a configured grant from a base station; obtain a first hybrid automatic repeat request, HARQ, process identifier, ID, related to a first period of the configured grant; transmit a first physical sidelink shared channel, PSSCH, to a second apparatus, based on a first resource included in the first period; obtain a second HARQ process ID related to a second period of the configured grant, wherein the second HARQ process ID related to the second period is the same as the first HARQ process ID; and transmit a second PSSCH to the second apparatus, based on a second resource included in the second period, wherein a new data indicator, NDI, related to the second PSSCH is a value to which a NDI related to the first PSSCH is toggled, based on the second HARQ process ID which is the same as the first HARQ process ID.

<FIG> shows a procedure in which a second apparatus performs wireless communication, according to an example of the present disclosure.

Referring to <FIG>, in step S1310, a second apparatus may receive a first physical sidelink shared channel, PSSCH, from a first apparatus, based on a first resource included in a first period of a configured grant. In step S1320, the second apparatus may receive a second PSSCH from the first apparatus, based on a second resource included in a second period of the configured grant. For example, a new data indicator, NDI, related to the second PSSCH may be a value to which a NDI related to the first PSSCH is toggled, based on a second hybrid automatic repeat request, HARQ, process identifier, ID, which is the same as a first HARQ process ID, the first HARQ process ID may be related to the first period, and the second HARQ process ID may be related to the second period.

The above-described embodiment may be applied to various devices to be described below. For example, a processor <NUM> of a second apparatus <NUM> may control a transceiver <NUM> to receive a first physical sidelink shared channel, PSSCH, from a first apparatus, based on a first resource included in a first period of a configured grant. And, the processor <NUM> of the second apparatus <NUM> may control the transceiver to receive a second PSSCH from the first apparatus, based on a second resource included in a second period of the configured grant.

According to a still further example of the present disclosure, a second apparatus for performing wireless communication may be proposed. For example, the second apparatus may comprise: one or more memories storing instructions; one or more transceivers; and one or more processors connected to the one or more memories and the one or more transceivers. For example, the one or more processors may execute the instructions to: receive a first physical sidelink shared channel, PSSCH, from a first apparatus, based on a first resource included in a first period of a configured grant; and receive a second PSSCH from the first apparatus, based on a second resource included in a second period of the configured grant, wherein a new data indicator, NDI, related to the second PSSCH is a value to which a NDI related to the first PSSCH is toggled, based on a second hybrid automatic repeat request, HARQ, process identifier, ID, which is the same as a first HARQ process ID, wherein the first HARQ process ID is related to the first period, and wherein the second HARQ process ID is related to the second period.

<FIG> shows a communication system <NUM>, based on an embodiment of the present disclosure.

Referring to <FIG>, a communication system <NUM> to which various embodiments of the present disclosure are applied includes wireless devices, Base Stations (BSs), and a network. Herein, the wireless devices represent devices performing communication using Radio Access Technology (RAT) (e.g., <NUM> New RAT (NR)) or Long-Term Evolution (LTE)) and may be referred to as communication/radio/<NUM> devices. The wireless devices may include, without being limited to, a robot 100a, vehicles 100b-<NUM> and 100b-<NUM>, an eXtended Reality (XR) device 100c, a hand-held device 100d, a home appliance 100e, an Internet of Things (IoT) device 100f, and an Artificial Intelligence (AI) device/server <NUM>. For example, the vehicles may include a vehicle having a wireless communication function, an autonomous vehicle, and a vehicle capable of performing communication between vehicles. Herein, the vehicles may include an Unmanned Aerial Vehicle (UAV) (e.g., a drone). 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) mounted in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance device, a digital signage, a vehicle, a robot, etc. The hand-held device may include a smartphone, a smartpad, a wearable device (e.g., a smartwatch or a smartglasses), and a computer (e.g., a notebook). For example, the BSs and the network may be implemented as wireless devices and a specific wireless device 200a may operate as a BS/network node with respect to other wireless devices.

Here, wireless communication technology implemented in wireless devices 100a to 100f of the present disclosure may include Narrowband Internet of Things for low-power communication in addition to LTE, NR, and <NUM>. In this case, for example, NB-IoT technology may be an example of Low Power Wide Area Network (LPWAN) technology and may be implemented as standards such as LTE Cat NB1, and/or LTE Cat NB2, and is not limited to the name described above. Additionally or alternatively, the wireless communication technology implemented in the wireless devices 100a to 100f of the present disclosure may perform communication based on LTE-M technology. In this case, as an example, the LTE-M technology may be an example of the LPWAN and may be called by various names including enhanced Machine Type Communication (eMTC), and the like. For example, the LTE-M technology may be implemented as at least any one of various standards such as <NUM>) LTE CAT <NUM>, <NUM>) LTE Cat M1, <NUM>) LTE Cat M2, <NUM>) LTE non-Bandwidth Limited (non-BL), <NUM>) LTE-MTC, <NUM>) LTE Machine Type Communication, and/or <NUM>) LTE M, and is not limited to the name described above. Additionally or alternatively, the wireless communication technology implemented in the wireless devices 100a to 100f of the present disclosure may include at least one of Bluetooth, Low Power Wide Area Network (LPWAN), and ZigBee considering the low-power communication, and is not limited to the name described above. As an example, the ZigBee technology may generate personal area networks (PAN) related to small/low-power digital communication based on various standards including IEEE <NUM>. <NUM>, and the like, and may be called by various names.

Wireless communication/connections 150a, 150b, or 150c may be established between the wireless devices 100a to 100f/BS <NUM>, or BS <NUM>/BS <NUM>. Herein, the wireless communication/connections may be established through various RATs (e.g., <NUM> NR) such as uplink/downlink communication 150a, sidelink communication 150b (or, D2D communication), or inter BS communication (e.g. relay, Integrated Access Backhaul (IAB)). The wireless devices and the BSs/the wireless devices may transmit/receive radio signals to/from each other through the wireless communication/connections 150a and 150b. For example, the wireless communication/connections 150a and 150b may transmit/receive signals through various physical channels. To this end, at least a part of various configuration information configuring processes, various signal processing processes (e.g., channel encoding/decoding, modulation/demodulation, and resource mapping/demapping), and resource allocating processes, for transmitting/receiving radio signals, may be performed based on the various proposals of the present disclosure.

<FIG> shows wireless devices, based on an embodiment of the present disclosure.

<FIG> shows a signal process circuit for a transmission signal, based on an embodiment of the present disclosure.

<FIG> shows another example of a wireless device, based on an embodiment of the present disclosure.

<FIG> shows a hand-held device, based on an embodiment of the present disclosure. The hand-held device may include a smartphone, a smartpad, a wearable device (e.g., a smartwatch or a smartglasses), or a portable computer (e.g., a notebook). The hand-held 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).

<FIG> shows a vehicle or an autonomous vehicle, based on an embodiment of the present disclosure. The vehicle or autonomous vehicle may be implemented by a mobile robot, a car, a train, a manned/unmanned Aerial Vehicle (AV), a ship, etc..

For example, the communication unit <NUM> may receive map data, traffic information data, etc. from an external server. The autonomous driving unit 140d may generate an autonomous driving path and a driving plan from the obtained data. The control unit <NUM> may control the driving unit 140a such that the vehicle or the autonomous vehicle <NUM> may move along the autonomous driving path according to the driving plan (e.g., speed/direction control). In the middle of autonomous driving, the communication unit <NUM> may aperiodically/periodically acquire recent traffic information data from the external server and acquire surrounding traffic information data from neighboring vehicles. In the middle of autonomous driving, the sensor unit 140c may obtain a vehicle state and/or surrounding environment information. The autonomous driving unit 140d may update the autonomous driving path and the driving plan based on the newly obtained data/information. The communication unit <NUM> may transfer information about a vehicle position, the autonomous driving path, and/or the driving plan to the external server. The external server may predict traffic information data using AI technology, etc., based on the information collected from vehicles or autonomous vehicles and provide the predicted traffic information data to the vehicles or the autonomous vehicles.

Claim 1:
A method for performing, by a first apparatus, wireless communication, the method comprising:
receiving (S1210) a configured grant, CG, from a base station;
obtaining (S1220) a first hybrid automatic repeat request, HARQ, process identifier, ID, related to a first period according to the CG;
transmitting (S1230) a first physical sidelink shared channel, PSSCH, to a second apparatus, based on a first resource included in the first period;
obtaining (S1240) a second HARQ process ID related to a second period according to the CG,
wherein the second HARQ process ID related to the second period is the same as the first HARQ process ID; and
transmitting (S1250) a second PSSCH to the second apparatus, based on a second resource included in the second period,
wherein a second new data indicator, NDI, related to the second PSSCH is a value to which a first NDI related to the first PSSCH is toggled,
characterized in that the second NDI is set to the toggled value, based on the second HARQ process ID being the same as the first HARQ process ID when a CG period is changed.