KR102710271B1 - Method and apparatus for uplink transmission in sidelink gap in wireless communication system - Google Patents

Abstract

A method and device for uplink transmission in a sidelink gap in a wireless communication system are provided. A method for a terminal to perform uplink (UL) SPS (Semi-Persistent Scheduling) transmission according to one aspect of the present invention may include the steps of: receiving UL SPS configuration information and sidelink (SL) gap configuration information from a base station; and, when an SL gap is configured in a UL SPS subframe indicated by the UL SPS configuration information, determining, based on at least one of a type of the UL SPS subframe or a type of the SL gap, whether to process a UL grant received from the base station or whether to perform UL SPS transmission based on the UL grant.

Description

{METHOD AND APPARATUS FOR UPLINK TRANSMISSION IN SIDELINK GAP IN WIRELESS COMMUNICATION SYSTEM}

The present invention relates to a wireless communication system, and more particularly, to a method, device, software, or a recording medium storing the software for uplink transmission in a sidelink gap.

Sidelink corresponds to a UE-to-UE interface that supports discovery and communication for direct communication between terminals. Sidelink uses uplink resources and can use a physical channel structure similar to uplink transmission.

Meanwhile, the base station can pre-allocate resources for uplink transmission and potential retransmissions. This is called uplink semi-persistent scheduling (SPS).

Due to the introduction of sidelink, there may be cases where the subframes in which the sidelink gap is established overlap (or overlap) with the subframes in which the uplink SPS transmission is established, but the specific behavior of the terminal in this case has not been determined yet.

The present invention provides a method and device for processing an uplink grant that sets up an uplink SPS transmission in a subframe overlapping a sidelink gap.

The present invention provides a method and device for processing uplink SPS HARQ (Hybrid Automatic Repeat Request) retransmission in a subframe overlapping a sidelink gap.

The technical problems to be achieved in the present invention are not limited to the technical problems mentioned above, and other technical problems not mentioned will be clearly understood by a person having ordinary skill in the technical field to which the present invention belongs from the description below.

According to one aspect of the present invention, a method for a terminal to perform uplink (UL) SPS (Semi-Persistent Scheduling) transmission in a wireless communication system can be provided. The method can include the steps of: receiving UL SPS configuration information and sidelink (SL) gap configuration information from a base station; and, when an SL gap is configured in a UL SPS subframe indicated by the UL SPS configuration information, determining, based on at least one of a type of the UL SPS subframe or a type of the SL gap, whether to process a UL grant received from the base station or whether to perform UL SPS transmission based on the UL grant.

The features briefly summarized above regarding the present invention are merely exemplary aspects of the detailed description of the present invention that follows and do not limit the scope of the present invention.

According to the present invention, a method for processing uplink SPS transmission and HARQ retransmission in a subframe overlapping with a sidelink gap can be provided.

The effects obtainable from the present invention are not limited to the effects mentioned above, and other effects not mentioned will be clearly understood by those skilled in the art to which the present invention belongs from the description below.

The drawings appended hereto are included to provide an understanding of the present invention and to illustrate various embodiments of the present invention and, together with the description of the specification, serve to explain the principles of the present invention.
FIG. 1 is a diagram for explaining a UL grant reception operation during an SL gap according to an example of the present invention.
FIG. 2 is a diagram for explaining the operation of a UL HARQ process during an SL gap according to an example of the present invention.
FIG. 3 is a drawing for explaining the operation of a terminal according to an example of the present invention.
Figure 4 is a drawing for explaining the configuration of a wireless device according to the present invention.

Hereinafter, the present specification will describe in detail the contents related to the present invention through exemplary drawings and embodiments. When adding reference signs to components of each drawing, it should be noted that the same components are given the same signs as much as possible even if they are shown in different drawings. In addition, when describing the embodiments of this specification, if it is determined that a specific description of a related known configuration or function may obscure the gist of this specification, the detailed description will be omitted.

In addition, this specification describes a wireless communication network, and operations performed in the wireless communication network may be performed in a process of controlling the network and transmitting or receiving a signal in a system (e.g., a base station) that manages the wireless communication network, or in a process of transmitting or receiving a signal in a terminal connected to the wireless network.

That is, it is obvious that various operations performed for communication with a terminal in a network consisting of a plurality of network nodes including a base station can be performed by the base station or other network nodes other than the base station. 'Base station (BS)' can be replaced by terms such as fixed station, Node B, eNode B (eNB), access point (AP). In addition, 'terminal' can be replaced by terms such as UE (User Equipment), MS (Mobile Station), MSS (Mobile Subscriber Station), SS (Subscriber Station), non-AP station (non-AP STA).

The terms used to describe the embodiments of the present invention can be described by the 3GPP LTE or LTE-A (LTE-Advanced) standard documents, except where explicitly stated to be used with a different meaning. However, it should be noted that this is only for the sake of economy and clarity of explanation, and that the embodiments of the present invention are not limited to being applied only to systems conforming to 3GPP LTE or LTE-A or successor standards.

First, we will explain the SPS and SL (SideLink) gap settings.

Table 1 shows some of the SPS configuration (SPS-Config) information elements provided through upper layer (e.g., RRC layer) signaling that are related to uplink SPS configuration.

Among the fields included in SPS-ConfigUL in Table 1, the semiPersistSchedIntervalUL parameter is defined as in Table 2 below. That is, subframes for uplink SPS transmission or retransmission can be preset according to the period indicated by the semiPersistSchedIntervalUL parameter.

Table 3 below shows the SL gap configuration (SL-GapConfig) information element provided via higher layer (e.g., RRC layer) signaling. An SL gap is a time period allocated by a base station for a UE to receive (or monitor) or transmit a sidelink discovery signal on another carrier or PLMN. In addition, an SL gap can be divided into a receive gap (Rx gap) and a transmit gap (Tx gap). The receive gap corresponds to a period for monitoring a neighboring Public Land Mobile Network (PLMN) or inter-carrier/cell discovery signal. The transmit gap corresponds to a period for transmitting a neighboring PLMN or inter-carrier/cell discovery signal.

Among the fields included in SL-GapConfig in Table 3, gapSubframeBitmap is defined as in Table 4 below. That is, a subframe in which an SL gap exists can be indicated in the form of a bitmap.

Next, we will explain uplink grant (UL Grant) reception.

In order to transmit the UL-SCH (Uplink-Shared Channel), which is a transport channel corresponding to the PUSCH (Physical Uplink Shared Channel) in the physical layer, the MAC entity must have a valid UL grant. However, in the case of non-adaptive HARQ retransmission, the UL-SCH can be retransmitted using the transmission parameters of the previous transmission without the UL grant.

A valid UL grant may be dynamically provided to a UE by a base station through a Physical Downlink Control Channel (PDCCH), through a Random Access Response (RAR), or may be configured semi-persistently. In order to perform a requested transmission, the MAC layer receives HARQ information from a lower layer (e.g., the physical (PHY) layer). When UL spatial multiplexing is configured in the PHY layer (i.e., when UL MIMO TM is configured), the MAC layer can receive up to two UL grants, and each UL grant can receive its own HARQ process from the PHY during the same Transmission Time Interval (TTI).

Table 5 below shows the behavior of how a MAC entity processes a UL grant received for a certain TTI.

In the above Table 5, if the serving cell is SpCell (Special Cell), and one UL grant for this TTI is received on the PDCCH of SpCell for the SPS C-RNTI (Cell-Radio Network Temporary Identifier) of the MAC entity, and if the value of NDI (New Data Indicator) of the received HARQ information is 1, it means that adaptive retransmission for the previous UL-SCH transmission is performed, not considering the new SPS allocation PDCCH. Here, SpCell generally includes PCell (Primary Cell) or PSCell (Primary SCell), and means PCell of MCG or PSCell (Primary Secondary Cell) of SCG in the dual connectivity operation mode in which MCG (Master Cell Group) and SCG (Secondary Cell Group) are established.

In the above Table 5, if the value of NDI of the received HARQ information is 0, it means that the UE considers the corresponding SPS allocation PDCCH as valid for SPS transmission, as in Table 6 below.

In Table 5 above, in cases other than when the PDCCH content indicates SPS release, the operation of storing the UL grant and related HARQ information as a configured UL grant means that when the PDCCH content indicates SPS activation, the UL grant information for UL SPS transmission is stored and considered as a configured UL grant.

In the above Table 5, it means the case where SPS activation is indicated by PDCCH, or re-initializing in an already activated state. Therefore, the operation of applying the set UL grant can be performed from the TTI for UL-SCH transmission indicated by the corresponding UL grant. For example, if the corresponding UL grant is received when SPS is already activated, it means re-initializing, and if the corresponding UL grant activates SPS transmission and also indicates control information for UL-SCH transmission, it can be considered as initializing.

In the above Table 5, the action of considering the NDI bit of the corresponding HARQ process as toggled means that it is considered as a new SPS transmission.

The action of transmitting the UL grant and related HARQ information set in Table 5 above to the HARQ entity of this TTI means that the set UL grant and the HARQ information associated with it are transmitted to the HARQ entity for the corresponding TTI.

In the above Table 5, if the serving cell is SpCell and the UL grant for this TTI has already been set for the SpCell, this means that the SPS allocation PDCCH has been previously received and that UL-SCH transmission (if any) can be performed based on the set UL grant information.

Table 6 below shows the validation operation of PDCCH or EPDCCH (Enhanced PDCCH) for SPS.

When all specific fields in DCI (Downlink Control Information) transmitted through a PDCCH/EPDCCH are set according to Table 7 or Table 8 below, the validation of the corresponding PDCCH/EPDCCH can be performed. Table 7 shows specific fields for SPS activation PDCCH/EPDCCH validation, and Table 8 shows specific fields for SPS release PDCCH/EPDCCH validation. When validation is performed, the UE can consider the received DCI information as valid SPS activation or release. If validation is not performed, the received DCI format can be considered as having a non-matching CRC (Cyclic Redundancy Check).

Table 9 below shows the UL SPS operation.

In the above Table 9, when twoIntervalsConfig is enabled by a higher layer, it means that eIMTA (enhanced Interference Management and Traffic Adaptation) is set. In a TDD network, terminals with eIMTA set can set two subframe sets, and the above twoIntervalsConfig corresponds to each subframe set. Here, the technology for Subframe_Offset is to be explained in Table 10.

FIG. 1 is a diagram for explaining a UL grant reception operation during an SL gap according to an example of the present invention.

SPS subframes can be set with a certain period and offset by SPS-ConfigUL as shown in Table 1 above.

Meanwhile, subframes corresponding to the SL gap can be set by bitmap signaling corresponding to a specific radio frame length through SL-GapConfig as shown in Table 3 above.

As illustrated in Fig. 1, a UL grant can be received through a PDCCH/EPDCCH scrambled with an SPS C-RNTI in a downlink subframe (DL SF) that is k-th earlier than an SPS subframe (SPS SF#0) of index 0 in a SpCell. Here, k is 4 in an FDD (Frequency Division Duplex) serving cell, a TDD (frame structure type 2) scheduling serving cell (i.e., a serving cell where an (E)PDCCH carrying a UL grant is transmitted) that is configured and operates with cross-carrier scheduling (i.e., scheduling in which the (E)PDCCH carrying the UL grant and the data transmission channel (e.g., PDSCH/PUSCH) are performed in different serving cells) in TDD-FDD CA, and in a TDD serving cell, k can have a value according to the TDD UL-DL configuration. Additionally, an FDD serving cell having a scheduling cell with a TDD frame structure type 2 structure in an interband TDD CA TDD serving cell or a TDD-FDD CA configuration may have a value according to a reference UL-DL configuration. In the example of Fig. 1, it is assumed that the received UL grant provides information about SPS PUSCH transmission in SPS SF#0, and the NDI field value in the received HARQ information is 0 (i.e., reception of UL grant with NDI=0 in Fig. 1).

As described above, SpCell (special cell) is a special secondary serving cell (pSCell, primary secondary serving cell) set in PCell or SeNB (secondary eNB) in a dual-connectivity configuration, and in the present invention, it is assumed to be a serving cell where SPS transmission is performed.

Case 1

In this Case 1, we define the behavior when this TTI (e.g., SPS SF#0 in the example of Fig. 1) overlaps (or overlaps) with an SL gap, where one UL grant is received on the PDCCH of SpCell for the SPS C-RNTI of the MAC entity for this TTI and indicates a UL-SCH transmission.

Here, if the SL gap overlapping with the SPS SF is an Rx gap, the UL grant processing operation has a higher priority than the Rx gap operation, and the Rx gap operation can be ignored. That is, the operation of monitoring a neighboring PLMN or carrier/cell-to-cell discovery signal defined to be performed in the Rx gap may not be performed if the Rx gap overlaps with the SPS SF.

In addition, in the Rx gap, the monitoring operation for the DL channel in the DL carrier for LTE DL reception is not performed. If the Rx gap overlaps with an SPS SF and the operation defined in the Rx gap (i.e., neighboring PLMN or carrier/cell-to-cell discovery signal monitoring) is not performed, it is unclear whether the LTE DL carrier monitoring operation is performed. According to the present invention, if the Rx gap overlaps with an SPS SF, it is defined that the LTE DL carrier monitoring operation is not performed.

More specifically, if a UL grant is received on the PDCCH of SpCell for an SPS C-RNTI of the MAC entity for this TTI and indicates UL-SCH transmission, and if this TTI (e.g., SPS SF#0 in the example of FIG. 1) overlaps with an SL gap configured as an Rx gap, the MAC entity may process the configured UL grant for this TTI and perform UL-SCH transmission simultaneously, but does not monitor neighboring PLMNs or inter-carrier/cell-to-cell discovery signals in the corresponding Rx gap, and does not perform monitoring for any DL channel on the DL carrier for LTE DL reception.

Here, the operation of processing the UL grant may include the following operations.

- If the PDCCH content does not correspond to SPS release, the terminal stores the HARQ information associated with the UL grant information as the configured UL grant.

- If SPS is not activated, the UL grant set to start from this TTI is initialized by activating SPS transmission from this TTI by the UL grant for received SPS transmission, or if SPS was already activated before, the UL grant set to start from this TTI is re-initialized. That is, the previously set UL grant is re-initialized with the received UL grant.

- Consider the NDI bit as toggled (i.e. consider it a new transmission).

- During this TTI, the above-mentioned UL grant and its associated HARQ information are delivered to the corresponding HARQ entity.

If the SPS SF overlapping SL gap is a Tx gap, the UL grant processing operation can be ignored during the Tx gap. That is, the operation of transmitting a discovery signal between neighboring PLMNs or carriers/cells, which is defined to be performed in the Tx gap, can be performed during the Tx gap without being affected by the UL grant processing operation and UL-SCH transmission. On the other hand, from the perspective of LTE UL HARQ operation, the configured UL grant is processed by the MAC entity but does not instruct UL-SCH transmission. That is, the PHY should not perform PUSCH transmission during the corresponding Tx gap.

In addition, in the Tx gap, the monitoring operation for DL channels/signals (e.g. (E)PDCCH, PDSCH, PMCH, PHICH, CRS, DRS, CSI-RS, PRS, etc.) in the DL carrier for LTE DL reception is not performed. If the Tx gap overlaps with an SPS SF and the operation defined in the Tx gap (i.e., transmission of discovery signals between neighboring PLMNs or carriers/cells) is performed as mentioned above, it is unclear whether the LTE DL carrier monitoring operation is performed. According to the present invention, if the Tx gap overlaps with an SPS SF, it is defined that the LTE DL carrier monitoring operation is not performed.

More specifically, if a UL grant is received on the PDCCH of SpCell for the SPS C-RNTI of the MAC entity for this TTI and indicates UL-SCH transmission, and if this TTI (e.g., SPS SF#0 in the example of FIG. 1) overlaps with an SL gap configured as a Tx gap, the MAC entity processes the configured UL grant but does not perform the UL-SCH transmission, transmits a neighboring PLMN or inter-carrier/cell-to-cell discovery signal in the Tx gap, and does not monitor any DL channel on the DL carrier for LTE DL reception.

Case 2

In this Case 2, we define the behavior when this TTI (e.g., SPS SF#1 in the example of Fig. 1) overlaps with an SL gap, in which case one UL grant is set in SpCell for this TTI, but there is no UL-SCH transmission (i.e., there is no UL-SCH data to transmit).

If the SL gap overlapping with an SPS SF (e.g., SPS SF#1) is an Rx gap, the MAC entity may process the UL grant configured for this TTI. However, no UL-SCH transmission is performed since there is no uplink data to transmit. Additionally, the Rx gap does not monitor neighboring PLMNs or inter-carrier/cell-to-cell discovery signals, whereas the DL carrier for LTE DL reception may or may not monitor any DL channel.

Alternatively, if the SL gap overlapping with an SPS SF (e.g., SPS SF#1) is an Rx gap, the MAC entity may not process the UL grant configured for this TTI. Accordingly, no UL-SCH transmission is performed. Additionally, the Rx gap may not be monitored for neighboring PLMNs or inter-carrier/cell-to-cell discovery signals, while the DL carrier for LTE DL reception may or may not perform monitoring for any DL channel.

Meanwhile, if the SL gap overlapping with an SPS SF (e.g., SPS SF#1) is a Tx gap, the MAC entity may not process the UL grant configured for this TTI. Accordingly, UL-SCH transmission is not performed. Therefore, if the SL gap is a Tx gap, the MAC entity does not perform any operation for the UL grant for this TTI and only performs neighboring PLMN or inter-carrier/cell-to-cell discovery signal transmission. Additionally, while transmitting neighboring PLMN or inter-carrier/cell-to-cell discovery signal in the Tx gap, no monitoring is performed on any DL channel in the DL carrier for LTE DL reception.

Case 3

In this Case 3, we define the behavior when a UL grant is set for this TTI in SpCell and UL-SCH transmission is instructed, and this TTI (e.g., SPS SF#2 in the example of Fig. 1) overlaps with an SL gap.

If the SL gap overlapping with an SPS SF (e.g., SPS SF#2) is an Rx gap, the MAC entity can process the corresponding configured UL grant for this TTI and perform UL-SCH transmission simultaneously, but does not monitor neighboring PLMN or inter-carrier/cell-to-cell discovery signals in the corresponding Rx gap, and does not perform monitoring for any DL channel on the DL carrier for LTE DL reception.

Meanwhile, if the SL gap overlapping with an SPS SF (e.g., SPS SF#2) is a Tx gap, the MAC entity processes the configured UL grant but does not perform UL-SCH transmission, transmits neighboring PLMN or inter-carrier/cell-to-cell discovery signal in the Tx gap, and does not monitor any DL channel in the DL carrier for LTE DL reception.

Alternatively, if the SL gap overlapping with an SPS SF (e.g., SPS SF#2) is a Tx gap, the MAC entity does not process the configured UL grant and does not perform UL-SCH transmission accordingly, transmits a neighboring PLMN or inter-carrier/cell-to-cell discovery signal in the Tx gap, and does not monitor any DL channel in the DL carrier for LTE DL reception.

FIG. 2 is a diagram for explaining the operation of a UL HARQ process during an SL gap according to an example of the present invention.

Unlike the measurement gap configuration, the SL gap configuration can overlap multiple times with the subframes corresponding to a single HARQ process. This is because the measurement gap has a period of 5 ms and a Measurement Gap Repetition Period (MGRP) of 40 ms or 80 ms, but the SL gap (Tx gap or Rx gap) is set as a bitmap of a size corresponding to 4*10 SF with a minimum size of 4 radio frames, so there is a possibility that the SL gap can overlap multiple times in a single HARQ process. This problem can be more severe in the case of TDD where the subframes available for UL transmission are limited. Therefore, when the HARQ process associated with the UL SPS and the SL gaps overlap, it is required to define a more specific terminal operation.

Case 4

This case 4 is for the case where both SL gap#0 and SL gap#1 in Fig. 2 are Rx gaps (or no SL gap).

In this case, if a UL grant is set in SL gap#0 for UL SPS transmission and PUSCH (or UL-SCH) transmission is instructed in SL gap#0, the UL grant can be processed and PUSCH (or UL-SCH) transmission can be performed according to the UL grant instruction.

In the example of Fig. 2, the PHICH (Physical HARQ Indicator Channel) indicates transmission of HARQ ACK/NACK information for a previous SPS (PUSCH) transmission, and the terminal can perform UL data transmission/retransmission on a subsequent SPS (PUSCH) based on the received HARQ-ACK feedback information.

Case 5

This case 5 is for the case where SL gap#0 is the Rx gap (or no SL gap) and SL gap#1 is the Tx gap.

In this case, if a UL grant is set in SL gap#0 for UL SPS transmission and PUSCH (or UL-SCH) transmission is instructed in SL gap#0, the UL grant can be processed and PUSCH (or UL-SCH) transmission can be performed according to the UL grant instruction.

Here, if the HARQ-ACK feedback for the previous PUSCH transmission provided to the UE through the PHICH indicates NACK, and if the associated PUSCH retransmission overlaps with the Tx gap which is SL gap#1, the associated PUSCH retransmission may not be performed (or may be delayed). In this case, the PUSCH retransmission that was not performed in response to the PHICH (NACK) may be performed again at the next PUSCH HARQ timing corresponding to the same HARQ process.

If the PUSCH transmission/retransmission indicated in this way cannot be performed due to a Tx gap, the value of CURRENT_TX_NB (i.e., the number of transmissions of data currently existing in the buffer) can be increased by 1. When the increased CURRENT_TX_NB value becomes equal to the maximum number of transmissions - 1, the HARQ buffer corresponding to the associated HARQ process can be flushed.

Case 6

This case 6 is for the case where SL gap#0 is the Tx gap and SL gap#1 is the Rx gap (or no SL gap).

In this case, if a UL grant is set in SL gap#0 for UL SPS transmission and PUSCH (or UL-SCH) transmission is instructed in SL gap#0, the UL grant is processed, but PUSCH (or UL-SCH) transmission according to the UL grant instruction may not be performed.

Here, if the subframe corresponding to the next PUSCH HARQ timing overlaps with SL gap#1 or no SL gap for PUSCH retransmission, the indicated PUSCH retransmission can be performed.

Case 7

This case 7 is for the case where both SL gap#0 and SL gap#1 are Tx gaps.

In this case, if a UL grant is set in SL gap#0 for UL SPS transmission and PUSCH (or UL-SCH) transmission is instructed in SL gap#0, the UL grant is processed, but PUSCH (or UL-SCH) transmission according to the UL grant instruction may not be performed.

Here, if the subframe corresponding to the next PUSCH HARQ timing corresponding to the same HARQ process for PUSCH retransmission overlaps consecutively with SL gap#1 (i.e., Tx gap), the indicated PUSCH transmission may not be performed.

If the PUSCH transmission/retransmission indicated in this way cannot be performed due to a Tx gap, the value of CURRENT_TX_NB (i.e., the number of transmissions of data currently existing in the buffer) can be increased by 1. When the increased CURRENT_TX_NB value becomes equal to the maximum number of transmissions - 1, the HARQ buffer corresponding to the associated HARQ process can be flushed.

Figure 3 is a drawing for explaining operation according to an example of the present invention.

In step S310, the terminal can receive UL SPS setting information and SL gap setting information from the base station.

In step S320, the terminal can determine whether an SL gap is set in a UL SPS subframe indicated by the UL SPS configuration information. If the UL SPS subframe and the SL gap overlap, the terminal can proceed to step S330.

In step S330, the terminal may determine at least one of whether to process a UL grant or whether to perform UL SPS transmission based on at least one of the types of the corresponding UL SPS subframe and the types of the SL gap. Here, the type of the UL SPS subframe may include a subframe immediately after UL grant initialization or re-initialization for the corresponding subframe (or TTI) (e.g., SPS SF#0 in FIG. 1), a subframe in which UL-SCH transmission is not indicated (e.g., SPS SF#1 in FIG. 1) or is indicated (e.g., SPS SF#2 in FIG. 1) while the UL grant is activated, a subframe related to initial transmission or retransmission while the UL grant is set (e.g., SPS (PUSCH) after the first SPS (PUSCH) or PHICH in FIG. 2), etc. The type of the SL gap may include Rx gap and Tx gap. A specific example may operate according to Cases 1 to 7 described above. For example, if the UL grant is not processed in step S330, UL SPS transmission is not performed in the corresponding UL SPS subframe, but even if the UL grant is processed, UL SPS transmission may not be performed. If it is determined to process the UL grant and perform UL SPS transmission in step S330, UL SPS transmission may be performed in step S340 based on the UL grant information.

If an SL gap is not set in a UL SPS subframe in step S320, UL SPS transmission can be performed in the corresponding UL SPS subframe in step S340.

Although the exemplary methods described above are presented as a series of operations for the sake of simplicity of explanation, this is not intended to limit the order in which the steps are performed, and each step may be performed simultaneously or in a different order, if desired. Furthermore, not all of the steps illustrated are necessarily required to implement the method according to the present invention.

The above-described embodiments include examples of various aspects of the present invention. Although not all possible combinations can be described to illustrate the various aspects, those skilled in the art will recognize that other combinations are possible. Accordingly, it is intended that the present invention include all other alterations, modifications, and variations that fall within the scope of the following claims.

The scope of the present invention includes a device (e.g., a wireless device and components thereof described with reference to FIG. 4) that processes or implements operations according to various embodiments of the present invention.

Figure 4 is a drawing for explaining the configuration of a wireless device according to the present invention.

FIG. 3 illustrates a terminal device (100) corresponding to an example of a downlink receiving device or an uplink transmitting device, and a base station device (200) corresponding to an example of a downlink transmitting device or an uplink receiving device.

The terminal device (100) may include a processor (110), an antenna unit (120), a transceiver (130), and a memory (140).

The processor (110) performs baseband-related signal processing and may include a first module (111) and a second module (112). The first module (111) may correspond to a higher layer processing unit and may process operations of a MAC (Medium Access Control) layer, an RRC (Radio Resource Control) layer, or a higher layer. The second module (112) may correspond to a physical layer processing unit (112) and may process operations of a physical (PHY) layer (e.g., uplink transmission signal processing, downlink reception signal processing). However, the present invention is not limited thereto, and the first and second modules may be integrated and configured as one module, or may be configured separately as three or more modules. In addition to performing baseband-related signal processing, the processor (110) may also control operations of the entire terminal device (100).

The antenna unit (120) may include one or more physical antennas, and when it includes multiple antennas, it may support MIMO transmission and reception. The transceiver (130) may include a radio frequency (RF) transmitter and an RF receiver. The memory (140) may store information processed by the processor (110), software related to the operation of the terminal device (100), an operating system, applications, etc., and may also include components such as a buffer.

The base station device (200) may include a processor (210), an antenna unit (220), a transceiver (230), and a memory (240).

The processor (210) performs baseband-related signal processing and may include a first module (211) and a second module (212). The first module (211) may correspond to a higher layer processing unit and may process operations of a MAC (Medium Access Control) layer, an RRC (Radio Resource Control) layer, or a higher layer. The second module (212) may correspond to a physical layer processing unit and may process operations of a physical (PHY) layer (e.g., uplink reception signal processing, downlink transmission signal processing). However, the present invention is not limited thereto, and the first and second modules may be integrated and configured as one module, or may be configured separately as three or more modules. In addition to performing baseband-related signal processing, the processor (210) may also control operations of the entire base station device (200).

The antenna unit (220) may include one or more physical antennas, and when it includes multiple antennas, it may support MIMO transmission and reception. The transceiver (230) may include an RF transmitter and an RF receiver. The memory (240) may store information processed by the processor (210), software related to the operation of the base station device (200), an operating system, applications, etc., and may also include components such as a buffer.

The first module (111) of the processor (110) of the terminal (100) may perform, for example, an operation related to RRC signaling of the terminal of the present invention. For example, the first module (111) may receive from a base station information including UL SPS configuration information, SL gap configuration information, etc., and transmit necessary information to a lower layer. The second module (112) may perform, for example, an operation related to a MAC entity of the terminal of the present invention. For example, the second module (112) may perform an operation of processing a UL grant received from the base station. For example, it may determine whether an SL gap is set in a UL SPS subframe indicated by the UL SPS configuration information. If the UL SPS subframe and the SL gap overlap, it may determine whether to process the UL grant or whether to perform UL SPS transmission based on at least one of the types of the UL SPS subframe and the SL gap. If it is decided to perform UL SPS transmission, the information required for UL-SCH transmission can be conveyed to the lower layer (e.g., PHY layer).

The first module (211) of the processor (210) of the base station (200) can perform, for example, an RRC signaling related operation of the base station of the present invention. For example, the first module (211) can generate UL SPS configuration information, SL gap configuration information, etc. and transmit them to the terminal. The second module (212) can perform, for example, an operation related to the MAC entity of the base station of the present invention. For example, the second module (212) can generate DCI information including a UL grant to be transmitted to the terminal and transmit it to a lower layer (e.g., a PHY layer) so that it is transmitted through a PDCCH/EPDCCH.

The operation of the processor (110) of the terminal (100) or the processor (210) of the base station (200) described above may be implemented by software processing or hardware processing, or may be implemented by software and hardware processing.

The scope of the present invention includes software (or an operating system, an application, firmware, a program, etc.) that allows operations according to various embodiments of the present invention to be executed on a device or a computer, and a medium storing such software and being executable on the device or the computer.

Although various embodiments of the present invention have been described with a focus on 3GPP LTE or LTE-A systems, they can be applied to various mobile communication systems.

Claims (10)

A method for a terminal to perform uplink (UL) semi-persistent scheduling (SPS) transmission in a wireless communication system,
A step of receiving UL SPS setting information and sidelink (SL) gap setting information from a base station;
A step for checking whether the SL gap overlaps in the UL SPS subframe indicated by the above UL SPS setting information; and
Including a step of determining whether to transmit UL SPS according to a UL grant received from the base station based on at least one of a UL SPS subframe type and an SL gap type, when the SL gap overlaps in the UL SPS subframe indicated by the UL SPS configuration information;
If the UL SPS subframe type is a subframe in which uplink-shared channel (UL-SCH) transmission is indicated after the UL grant is activated, and the SL gap type is an SL reception gap (Rx gap), the UL-SCH transmission is performed by storing related HARQ (hybrid automatic repeat and request) information based on the UL grant in the UL SPS subframe, and monitoring based on the SL reception gap is not performed.
A method for performing UL SPS transmission, wherein if the UL SPS subframe type is a subframe in which the UL-SCH transmission is not indicated after the UL grant is activated and the SL gap type is the SL reception gap (Rx gap), the UL grant is ignored in the UL SPS subframe, the UL-SCH transmission is not performed, and monitoring based on the SL reception gap is not performed.
In the first paragraph,
A method for performing UL SPS transmission, wherein the UL SPS subframe type is set to any one of a subframe immediately after the UL grant is initialized or re-initialized, a subframe in which the UL-SCH transmission is not indicated after the UL grant is activated, a subframe in which the UL-SCH transmission is indicated after the UL grant is activated, and a subframe related to initial transmission or retransmission in a state in which the UL grant is set.
In the second paragraph,
A method for performing UL SPS transmission, wherein the above SL gap type is set to one of the SL reception gap (Rx gap) and the SL transmission gap (Tx gap).
In the third paragraph,
A method for performing UL SPS transmission, wherein if the SL gap type of the overlapping SL gap is the SL transmission gap, the UL grant is ignored and the UL SPS transmission is not performed.
delete In a terminal performing UL SPS transmission in a wireless communication system,
transceiver; and
Processor; including,
The above processor,
Receive UL SPS setting information and SL gap setting information from the base station through the above transceiver,
Check whether the SL gap overlaps in the UL SPS subframe indicated by the above UL SPS configuration information, and
In the case where the SL gap overlaps in the UL SPS subframe indicated by the UL SPS configuration information, whether to transmit UL SPS is determined according to the UL grant received from the base station based on at least one of the UL SPS subframe type and the SL gap type.
If the UL SPS subframe type is a subframe in which uplink-shared channel (UL-SCH) transmission is indicated after the UL grant is activated, and the SL gap type is an SL reception gap (Rx gap), the UL-SCH transmission is performed by storing related HARQ (hybrid automatic repeat and request) information based on the UL grant in the UL SPS subframe, and monitoring based on the SL reception gap is not performed.
A terminal performing UL SPS transmission, wherein the UL SPS subframe type is a subframe in which the UL-SCH transmission is not indicated after the UL grant is activated, and the SL gap type is the SL reception gap (Rx gap), the UL grant is ignored in the UL SPS subframe, the UL-SCH transmission is not performed, and monitoring based on the SL reception gap is not performed.
In Article 6,
A terminal performing UL SPS transmission, wherein the above UL SPS subframe type is set to any one of a subframe immediately after the UL grant is initialized or re-initialized, a subframe in which the UL-SCH transmission is not indicated after the UL grant is activated, a subframe in which the UL-SCH transmission is indicated after the UL grant is activated, and a subframe related to initial transmission or retransmission in a state in which the UL grant is set.
In Article 7,
A terminal performing UL SPS transmission, wherein the above SL gap type is set to one of the SL reception gap (Rx gap) and the SL transmission gap (Tx gap).
In Article 8,
A terminal performing UL SPS transmission, in which the SL gap type of the overlapping SL gap is the SL transmission gap, the UL grant is ignored and the UL SPS transmission is not performed.
delete

Images