Terminal, base station, communication system, and communication method

Abstract

The terminal has a reception section that receives a downlink control channel and a plurality of downlink shared channels that are scheduled, and a control section that, when receiving the downlink shared channels, assumes a plurality of start positions in the time domain for the downlink shared channels in a time slot in which listen-before-talk (LBT) is required or a time slot in which a monitoring period of the downlink control channel can be one time slot or more among time slots in which the plurality of downlink shared channels are scheduled.

Description

Technical Field

[0001] This invention relates to terminals, base stations, and communication methods in wireless communication systems. Background Technology

[0002] In NR (New Radio) (also known as "5G"), which is the successor system to LTE (Long Term Evolution), technologies that meet requirements such as high-capacity systems, high-speed data transmission, low latency, simultaneous connection of multiple terminals, low cost, and power saving are being researched (e.g., Non-Patent Literature 1).

[0003] In NR version 17, higher frequency bands than previous versions (e.g., non-patent document 2) were investigated. For example, the applicable parameter set, including subcarrier spacing, channel bandwidth, etc., physical layer design, and obstacles envisioned in actual wireless communication were studied in the 52.6 GHz to 71 GHz frequency band.

[0004] Existing technical documents

[0005] Non-patent literature

[0006] Non-patent document 1: 3GPP TS 38.300 V16.2.0 (2020-07)

[0007] Non-patent document 2: 3GPP TS 38.306 V16.1.0 (2020-07) Summary of the Invention

[0008] The problem that the invention aims to solve

[0009] In newly applied frequency bands using higher frequencies than before, increasing the monitoring period is being studied to reduce the load required for monitoring the PDCCH (Physical Downlink Control Channel). On the other hand, to ensure scheduling flexibility even with longer PDCCH monitoring periods, research is underway to support scheduling of multiple PDSCH (Physical Downlink Shared Channel) or multiple PUSCH (Physical Uplink Shared Channel) channels.

[0010] However, for example, in an unauthorized band domain, if LBT (Listen before talk) is performed immediately before transmission, the transmission opportunity may be lost due to LBT failure.

[0011] The present invention was made in view of the above aspects, and in a wireless communication system, scheduling corresponding to the communication mode can be performed.

[0012] Methods for solving problems

[0013] According to the disclosed technology, a terminal is provided, comprising: a receiving unit that receives a downlink control channel and a plurality of scheduled downlink shared channels; and a control unit that, when receiving the downlink shared channels, envisions a plurality of start positions in the time domain for the downlink shared channels in a time slot in which listen-before-speak (LBT) is required or in a time slot in which the monitoring period of the downlink control channel can be one or more time slots.

[0014] The effects of the invention

[0015] According to publicly available technology, scheduling corresponding to the communication method can be performed in wireless communication systems. Attached Figure Description

[0016] Figure 1 This is a diagram illustrating a structural example of a wireless communication system according to an embodiment of the present invention.

[0017] Figure 2 This is a diagram illustrating an example of the frequency range in an embodiment of the present invention.

[0018] Figure 3 This is a diagram used to illustrate an example of LBT.

[0019] Figure 4 This is a flowchart illustrating an example of a receiving action in an embodiment of the present invention.

[0020] Figure 5 This is a diagram illustrating an example (1) of scheduling in an embodiment of the present invention.

[0021] Figure 6 This is a diagram illustrating example (2) of scheduling in an embodiment of the present invention.

[0022] Figure 7 This is a diagram illustrating an example (3) of scheduling in an embodiment of the present invention.

[0023] Figure 8 This is a diagram illustrating an example (4) of scheduling in an embodiment of the present invention.

[0024] Figure 9 This is a diagram illustrating an example (5) of scheduling in an embodiment of the present invention.

[0025] Figure 10 This is a diagram illustrating an example (6) of scheduling in an embodiment of the present invention.

[0026] Figure 11 This is a diagram illustrating an example (7) of scheduling in an embodiment of the present invention.

[0027] Figure 12 This is a diagram illustrating an example (8) of scheduling in an embodiment of the present invention.

[0028] Figure 13 This is a diagram illustrating an example of the functional structure of base station 10 in an embodiment of the present invention.

[0029] Figure 14 This is a diagram illustrating an example of the functional structure of terminal 20 in an embodiment of the present invention.

[0030] Figure 15 This is a diagram illustrating an example of the hardware structure of a base station 10 or a terminal 20 in an embodiment of the present invention. Detailed Implementation

[0031] Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings. Furthermore, the embodiments described below are merely examples, and the application of the present invention is not limited to the embodiments described below.

[0032] In the operation of the wireless communication system according to embodiments of the present invention, existing technologies are appropriately used. These existing technologies include, for example, existing LTE, but are not limited to, existing LTE. Furthermore, unless otherwise stated, the term "LTE" as used in this specification has a broad meaning that includes LTE-Advanced and subsequent methods (e.g., NR).

[0033] Furthermore, in the embodiments of the present invention described below, the terms SS (Synchronization Signal), PSS (Primary SS), SSS (Secondary SS), PBCH (Physical broadcast channel), PRACH (Physical random access channel), PDCCH (Physical Downlink Control Channel), PDSCH (Physical Downlink Shared Channel), PUCCH (Physical Uplink Control Channel), and PUSCH (Physical Uplink Shared Channel) used in conventional LTE are used. These are for ease of description, and the same signals and functions may also be referred to by other names. In addition, the above terms in NR correspond to NR-SS, NR-PSS, NR-SSS, NR-PBCH, NR-PRACH, etc. However, even signals used in NR are not necessarily designated as "NR-".

[0034] Furthermore, in embodiments of the present invention, the duplex mode can be TDD (Time Division Duplex), FDD (Frequency Division Duplex), or other modes (e.g., Flexible Duplex).

[0035] Furthermore, in embodiments of the present invention, the “configure” wireless parameters can be pre-configured predetermined values ​​or wireless parameters notified from the base station 10 or the terminal 20.

[0036] Figure 1 This is a diagram illustrating an example structure of a wireless communication system according to an embodiment of the present invention. For example... Figure 1 As shown, the wireless communication system in this embodiment of the invention includes a base station 10 and a terminal 20. Figure 1 The image shows one base station 10 and one terminal 20, but this is just one example; there can be multiple terminals.

[0037] Base station 10 is a communication device that provides one or more cells and wirelessly communicates with terminal 20. The physical resources of the wireless signal are defined in the time and frequency domains. The time domain can be defined by the number of OFDM (Orthogonal Frequency Division Multiplexing) symbols, and the frequency domain can be defined by the number of subcarriers or resource blocks. Base station 10 sends synchronization signals and system information to terminal 20. Synchronization signals are, for example, NR-PSS and NR-SSS. System information is transmitted, for example, via NR-PBCH, also known as broadcast information. Synchronization signals and system information can also be referred to as SSB (SS / PBCH block). Figure 1 As shown, base station 10 sends control signals or data to terminal 20 via DL (Downlink) and receives control signals or data from terminal 20 via UL (Uplink). Both base station 10 and terminal 20 are capable of beamforming for signal transmission and reception. Furthermore, both base station 10 and terminal 20 can apply MIMO (Multiple Input Multiple Output) based communication to DL or UL. Additionally, base station 10 and terminal 20 can also communicate via secondary cells (SCell) and primary cells (PCell) based on CA (Carrier Aggregation). Moreover, terminal 20 can also communicate via the primary cell of base station 10 and other primary / secondary SCG cells of base station 10 based on DC (Dual Connectivity).

[0038] Terminal 20 is a communication device with wireless communication capabilities, such as a smartphone, mobile phone, tablet computer, wearable terminal, or M2M (Machine-to-Machine) communication module. Figure 1 As shown, terminal 20 receives control signals or data from base station 10 via DL and transmits control signals or data to base station 10 via UL, thereby utilizing various communication services provided by the wireless communication system. Furthermore, terminal 20 receives various reference signals transmitted from base station 10 and performs propagation path quality measurements based on the reception results of these reference signals.

[0039] Figure 2 This is a diagram illustrating an example of the frequency range in an embodiment of the present invention. In the NR specifications of 3GPP Releases 15 and 16, the use of frequency bands, for example, above 52.6 GHz, was investigated. Additionally, as... Figure 2As shown, the currently used FR (Frequency Range) 1 is defined as the frequency band from 410MHz to 7.125GHz, with a Subcarrier Spacing (SCS) of 15, 30, or 60kHz and a bandwidth from 5MHz to 100MHz. FR2 is the frequency band from 24.25GHz to 52.6GHz, with an SCS of 60, 120, or 240kHz and a bandwidth from 50MHz to 400MHz. For example, a new frequency band from 52.6GHz to 71GHz could also be envisioned. Furthermore, support for frequency bands exceeding 71GHz could also be envisioned.

[0040] As mentioned above, the carrier frequency of the newly used frequency band is much higher than that of the past, so problems such as those described in 1) to 3) below are considered.

[0041] 1) Large phase noise

[0042] This issue necessitates, for example, the use of a larger SCS or a single-carrier waveform.

[0043] 2) Large propagation loss

[0044] This issue necessitates, for example, the requirement for narrower beams and a greater number of beams.

[0045] 3) The high sensitivity of PAPR (Peak to Average Power Ratio) and the nonlinearity of PA (Power Amplifier).

[0046] This issue has led to requirements such as larger SCS (i.e., smaller FFT points), mechanisms to reduce PAPR, and single-carrier waveforms.

[0047] Considering the issues mentioned above, the waveforms in the newly used frequency band could be envisioned as applying CP-OFDM (Cyclic Prefix Orthogonal Frequency Division Multiplexing) / DFT-S-OFDM (Discrete Fourier Transform Spread OFDM) with a larger SCS.

[0048] On the other hand, as shown in Table 1, which illustrates the relationship between SCS and symbol length, when 14 symbols are maintained as a time slot structure, the symbol / CP period and the time slot period become shorter due to the larger SCS.

[0049] [Table 1]

[0050] As shown in Table 1, the symbol length is 66.6 microseconds at an SCS of 15 kHz. The symbol length is 33.3 microseconds at an SCS of 30 kHz. The symbol length is 16.65 microseconds at an SCS of 60 kHz. The symbol length is 8.325 microseconds at an SCS of 120 kHz. The symbol length is 4.1625 microseconds at an SCS of 240 kHz. The symbol length is 2.08125 microseconds at an SCS of 480 kHz. The symbol length is 1.040625 microseconds at an SCS of 960 kHz.

[0051] Figure 3 This is a diagram used to illustrate examples of LBT (Listen before talk). For example, in the frequency band from 52.6 GHz to 71 GHz, such as... Figure 3 As shown, the CCA (Clear Channel Assessment) process defines the channel detection period as a period based on 8 microseconds + 5 microseconds × a random counter. Figure 3 This is an example where the random counter is 3 in the first LBT, and it represents a detection period of 8 + 5 × 3 = 23 microseconds during which the channel is active. The example also shows that the channel was detected as busy during the detection period from 14 to 18 microseconds. Furthermore, in... Figure 3 The following example is shown: The second LBT starts from the state where the random counter is 2 when the channel is busy was detected in the first LBT. 8 + 5 × 2 = 18 microseconds is the channel detection period. During this detection period, the channel is not detected to be busy, so transmission begins.

[0052] In newly applied frequency bands using higher frequencies than before, increasing the monitoring period is being studied to reduce the load required for PDCCH (Physical Downlink Control Channel) monitoring. On the other hand, to ensure scheduling flexibility and maintain resource utilization efficiency and communication speed even with longer PDCCH monitoring periods, support for scheduling multiple PDSCH (Physical Downlink Shared Channel) or multiple PUSCH (Physical Uplink Shared Channel) is being studied. However, for example, in unlicensed bands, if LBT is performed immediately before transmission, there is a possibility of losing a transmission opportunity due to LBT failure.

[0053] Therefore, in embodiments of the present invention, a DCI (Downlink Control Information) format for appropriately scheduling multiple PDSCHs or multiple PUSCHs is proposed. Furthermore, a TDRA (Time Domain Resource Allocation) format for appropriately scheduling multiple PDSCHs or multiple PUSCHs is proposed. Moreover, DCI fields other than TDRA are also proposed. Hereinafter, "PDSCH" can be replaced with "PUSCH", and "PUSCH" can be replaced with "PDSCH".

[0054] Figure 4 This is a flowchart illustrating an example of a receiving operation in an embodiment of the present invention. In step S1, terminal 20 receives a DCI. In the following step S2, terminal 20 receives multiple PDSCHs or sends multiple PUSCHs based on the DCI.

[0055] For example, DCI can schedule multiple PUSCH transmissions in consecutive time slots. Furthermore, DCI can also notify the start time slot or the TDRA field within each time slot. This TDRA can correspond to a mapping type that makes multiple start positions or multiple mini-time slots valid within a single time slot, as well as multiple sets of SLIVs (Start and Length Indicator Values).

[0056] For example, TDRA can be used to schedule multiple PDSCHs or multiple PUSCHs across multiple non-contiguous or contiguous time slots. Furthermore, a single TDRA field can notify multiple start locations or multiple mini-time slots without requiring changes to the TDRA table. Additionally, multiple PDSCHs or multiple PUSCHs can be scheduled based on mini-time slots or time slots.

[0057] Furthermore, the DCI format can also be an extension of the existing UE-specific DCI format. For example, some or all of DCI format 1_0, DCI format 1_1, and DCI format 1_2 can be used for scheduling multiple PDSCHs. Similarly, some or all of DCI format 0_0, DCI format 0_1, and DCI format 0_2 can be used for scheduling multiple PUSCHs.

[0058] Furthermore, the DCI format can also use a new format that performs scheduling of multiple PDSCHs and / or multiple PUSCHs. For example, the DCI can contain fields for both PDSCH and PUSCH. Additionally, the DCI can contain common fields for both PDSCH and PUSCH.

[0059] Furthermore, when only PDSCH is scheduled, a field for a specific PUSCH can indicate that the PUSCH is not scheduled. For example, if all FDRA (Frequency Domain Resource Allocation) values ​​for the PUSCH are "0", it indicates that the PUSCH is not scheduled.

[0060] The following describes the scheduling method for a TDRA index corresponding to a SLIV without expanding the TDRA table, and the method that enables non-contiguous scheduling.

[0061] DCI can schedule channels in multiple time slots using a single TDRA index. A TDRA index can correspond to a mapping type and each entry in the TDRA table for a single SLIV. By using a single TDRA index corresponding to a single SLIV, it is not necessary to expand the TDRA table. Furthermore, discontinuous scheduling is possible.

[0062] For example, SLIV can also notify multiple start positions in the scheduled time slots. Figure 5 This is a diagram illustrating an example (1) of scheduling in an embodiment of the present invention. For example... Figure 5 As shown, "S" represents the initially possible start position within the time slot being considered. For example, if LBT fails at the start position "S", the next possible start position is set to "S+L". That is, the start position is repeatedly delayed by L each time until LBT succeeds. In other words, the start position of PDSCH can also be specified by a period that is an integer multiple of S plus L. For example, if the start position immediately after a successful LBT in a time slot is "S1", the actual length of PDSCH or PUSCH in that time slot is "13-S1" or "12-S1". For example, time slots that do not require LBT can have their start position set to "S". Figure 5 As shown, multiple start positions can be specified based on a single SLIV in each scheduled time slot.

[0063] Furthermore, for example, SLIV can also notify multiple start positions for the starting time slot and the time slots that require LBT. Figure 6 This is a diagram illustrating example (2) of scheduling in an embodiment of the present invention. For example... Figure 6As shown, in the scheduled starting time slot and in the time slots of LBTs outside the starting time slot that require energy detection before the first symbol transmission, "S" represents the initially possible start position within the time slot being targeted. For example, if the LBT fails at the start position "S", the next possible start position is set to "S+L". That is, the start position is repeatedly delayed by L each time until the LBT succeeds. For example, if the start position immediately after a successful LBT in a time slot is "S1", the actual length of the PDSCH or PUSCH in that time slot is "13-S1" or "12-S1".

[0064] Additionally, the time slot of an LBT that is outside the initial time slot and requires power detection before the first symbol transmission can also be a time slot that is scheduled later in the time domain through discontinuous time slot scheduling.

[0065] Furthermore, if the PDCCH monitoring period may be longer than one time slot, the start position of the PDSCH can be changed according to the length of the monitoring period. For example, if the terminal 20 fails to monitor the PDCCH at the start position "S", it can set the next possible start position to "S+L". That is, the terminal 20 can also repeatedly perform the action of delaying the start position by L each time until the PDCCH monitoring is successful.

[0066] In LBT time slots outside the initial time slot and where power detection is not required before the first symbol transmission, SLIV can be ignored. The first symbol within the target time slot is used as the starting symbol for PDSCH / PUSCH within the target time slot. L can be 13 or 14 symbols. PDSCH / PUSCH is scheduled among all available symbols in the target time slot. Furthermore, PDSCH / PUSCH can refer to either PDSCH or PUSCH, or it can refer to both PDSCH and PUSCH.

[0067] Figure 7 This is a diagram illustrating example (3) of scheduling in an embodiment of the present invention. For example... Figure 7 As shown, LBT was successfully performed within the scheduled initial time slot, in an 8µs window and three 5µs windows. Therefore, transmission can begin from the starting position immediately following the successful LBT time point among multiple pre-defined start positions. Furthermore, as... Figure 7 As shown, LBT was successfully performed in an 8µs window and two 5µs windows during the time slot where LBT was required. Therefore, transmission can also begin from the start position immediately following the successful LBT time point among multiple start positions for transmission.

[0068] Figure 8This is a diagram illustrating an example (4) of scheduling in an embodiment of the present invention. For example... Figure 8 As shown, in the scheduled initial time slot, no transmission is performed because busy is detected in LBT. In the next time slot, LBT is performed successfully in an 8µs window and two 5µs windows. Therefore, transmission can also begin from the start position "S+2L", which is immediately after the successful LBT time point among the multiple start positions set for transmission. Furthermore, in the next time slot requiring LBT, LBT is performed successfully in an 8µs window and three 5µs windows. Therefore, transmission can also begin from the start position "S+L", which is immediately after the successful LBT time point among the multiple start positions set for transmission.

[0069] In addition, DCI can also notify a TDRA index to schedule channels in multiple time slots. A TDRA index can correspond to a mapping type and SLIV for each entry in the TDRA table.

[0070] Figure 9 This is a diagram illustrating example (5) of scheduling in an embodiment of the present invention. Figure 9 As shown, in each scheduled time slot, the TDRA for PDSCH / PUSCH scheduled in multiple mini-time slots is determined by the notified SLIV, which can be continuously and repeatedly applied within that time slot. The TDRA for PDSCH / PUSCH scheduled in the nth mini-time slot within a given time slot can be envisioned as "S n ′=S+(n-1)*L” and “L n The value of S is used to determine this. n ' is the starting position of the PDSCH / PUSCH scheduled in the nth mini-slot, L n ' is the length of the PDSCH / PUSCH scheduled in the nth mini-slot.

[0071] And for example, when TDRA does not exceed the time slot boundary, i.e., when S n '+L n When '<14, it can also be S' n =S n ', L n =L n '.

[0072] For example, when the final TDRA exceeds the time slot boundary, i.e., when S n '+L n When the time interval is greater than 14, the symbol length before the time slot boundary of the PDSCH / PUSCH scheduled in the last mini time slot can be less than L, S. n =S n ', L n=L n '.

[0073] For example, when the final TDRA exceeds the time slot boundary, i.e., when S n '+L n At time 14, the symbol length before the slot boundary of the PDSCH / PUSCH scheduled in the last mini-slot can be concatenated with the immediately preceding TDRA, S n-1 =S n-1 ′, L n =13-S n-1 ′.

[0074] For example, when the final TDRA exceeds the time slot boundary, i.e., when S n '+L n At time 14, symbols preceding the slot boundary of the PDSCH / PUSCH scheduled in the last mini slot can be discarded.

[0075] Figure 9 This is an example of linking the last TDRA to the immediately preceding TDRA when the last TDRA exceeds the slot boundary, and transmission begins upon successful LBT. Figure 9 The scheduling method shown reduces the impact on the TDRA table and enables discontinuous scheduling.

[0076] Figure 10 This is a diagram illustrating an example (6) of scheduling in an embodiment of the present invention. Figure 10 As shown, SLIV can also notify multiple start positions for the initial time slot and the time slots requiring LBT. In the scheduled initial time slot, and in the time slots outside the initial time slot that require LBT before the first symbol transmission, the TDRA corresponding to the PDSCH / PUSCH of multiple mini-time slots can also be determined based on the notified start position. Figure 9 The SLIV described in the document is used to determine this. In LBT time slots outside the start time slot that do not require power detection before the first symbol transmission, TDRA can also be determined based on the time slot passed. Figure 9 The process of setting S=0 in the SLIV specification determines this.

[0077] like Figure 10 As shown, after LBT succeeds, PDSCH can also be scheduled starting from S based on SLIV, setting S after the time slot boundary to 0, and then scheduling subsequent PDSCH. Figure 10 The scheduling method shown can reduce the impact on the TDRA table, reduce the DCI payload size, and perform discontinuous scheduling.

[0078] Here, whether to perform slot-based scheduling or mini-slot-based scheduling can be determined by any one of the following 1) to 3).

[0079] 1) It can be defined through specifications. For example, it can support only time slot-based, only mini-time slot-based, or both time slot-based and mini-time slot-based.

[0080] 2) This can be configured via RRC. For example, you can use the information elements contained in PDSCH-Config or PUSCH-Config to indicate whether only slot-based support is supported, whether only mini-slot-based support is supported, or whether both slot-based and mini-slot-based support are supported.

[0081] 3) Notification can be made via DCI. Notification can be made using 1 bit in the scheduled DCI, or only support for slot-based systems, or only support for mini-slot-based systems, or both slot-based and mini-slot-based systems can be provided using multiple bits in the scheduled DCI.

[0082] Here, whether to perform continuous time slot scheduling or non-continuous time slot scheduling can be determined by any one of the following 1) to 3).

[0083] 1) This can be configured via RRC. For example, RRC settings can be used to specify which of the continuous and non-continuous time slots to apply to multiple PDSCH / PUSCH scheduling.

[0084] 2) Notification can be made via DCI. For example, one bit in the DCI of the request or scheduler can be used to indicate which of the multiple PDSCH / PUSCH schedulers should apply a continuous or non-contiguous time slot.

[0085] 3) It can be defined through specifications. For example, it is also possible to predefine which of the continuous and non-continuous time slots to apply to multiple PDSCH / PUSCH scheduling.

[0086] For 1)-3) above, when setting, notifying or defining the scheduling of non-continuous time slots, it is also possible to set, notify or define the possible time slot modes for scheduling.

[0087] For example, time slot patterns can be mapped based on timing or repetition. For instance, if time slot N1 is scheduled, then time slot N2 is not scheduled; then time slot N1 is scheduled, then time slot N2 is not scheduled, and so on, until the desired number of time slots are reached.

[0088] The values ​​of N1 and N2 can be set via RRC, or the DCI can notify which value to use from a set of values ​​defined by the specification or RRC. The DCI can also notify an index representing any one of the bitmap sets defined by the specification or RRC. The bit field length of this index can be determined based on the set size. Furthermore, the DCI can directly notify the bitmap. The size of the field notifying this bitmap can be determined based on the maximum number of scheduled time slots.

[0089] Furthermore, the possible scheduling slot patterns can be determined based on the TDD mode. For example, in TDD mode, slots containing D symbols or D and F symbols can be skipped when scheduling multiple PUSCHs. Similarly, in TDD mode, slots containing U symbols or U and F symbols can be skipped when scheduling multiple PDSCHs.

[0090] In addition, DCI can also notify a TDRA index containing the mapping type and multiple sets of SLIVs. Multiple SLIVs can correspond to multiple consecutive time slots or multiple non-consecutive time slot ranges.

[0091] Multiple SLIVs can correspond to ranges of consecutive or non-consecutive time slots. Whether the scheduling is consecutive or non-consecutive can also be determined based on the values ​​of the multiple SLIVs notified. Non-consecutive scheduling can also be achieved through the configuration of the TDRA table.

[0092] Alternatively, multiple SLIVs can correspond to a range of consecutive time slots. Scheduling multiple non-consecutive PDSCH / PUSCHs can be achieved by representing the number of unscheduled time slots following the scheduled time slot (e.g., N1 time slots) and the number of repeated SLIV patterns (e.g., N2 times). N1 and N2 can be determined as shown in 1)-5) below.

[0093] 1) The values ​​of N1 and N2 can also be separately encoded as different columns in the TDRA table.

[0094] 2) The values ​​of N1 and N2 can also be jointly encoded as a column of the TDRA table (as in SLIV).

[0095] 3) The value of N1 is encoded as column 1 of the TDRA table, and the value of N2 can be determined by the RRC setting or by the DCI of the scheduler.

[0096] 4) The value of N2 is encoded as column 1 of the TDRA table. The value of N1 can be determined by RRC settings or by notification through the DCI of the scheduler.

[0097] 5) The values ​​of N1 and N2 can be determined by RRC settings or by notification through the scheduling DCI.

[0098] Table 2 below shows an example of applying the TDRA table described in 1) above.

[0099] [Table 2]

[0100] As shown in Table 2, N1 and N2 can be separated into different columns. Figure 11 This is a diagram illustrating an example (7) of scheduling in an embodiment of the present invention. Figure 11 This is the scheduling example corresponding to index #1 in Table 2. For example... Figure 11 As shown, three PDSCHs with a starting position of #0 and a length of 14 are scheduled via SLIV. Since N1 is 2, the next two time slots are scheduled. Since N2 is 3, the group of the three scheduled time slots and the two unscheduled time slots of the PDSCH is repeated three times.

[0101] Additionally, multiple SLIVs can also correspond to a range of consecutive time slots. Scheduling of multiple non-consecutive PDSCH / PUSCHs can be achieved through a scheduling mode that indicates which time slot among the multiple SLIVs is not scheduled. This scheduling mode can be defined by the specification, set by the RRC, notified by the DCI, or applied as shown in 1) or 2) below.

[0102] 1) The scheduling mode can also be applied only once.

[0103] 2) It can also notify the number of recurring scheduling patterns (e.g., N2).

[0104] Table 3 below shows an example of applying the TDRA table described in 2) above.

[0105] [Table 3]

[0106] Figure 12 This is a diagram illustrating an example (8) of scheduling in an embodiment of the present invention. Figure 12 This is the scheduling example corresponding to index #1 in Table 3. For example... Figure 12 The example shown is as follows: Five PDSCHs with a start position of #0 and a length of 14 are scheduled using SLIV, and these five time slots are notified of "10101" as the scheduling mode. Furthermore, in... Figure 12 In the example, the number of repetitions N2 is set to 3. Alternatively, N2 can also be encoded as a TDRA table.

[0107] like Figure 12 As shown, based on the scheduling mode, the time slots of PDSCH are scheduled three times repeatedly: time slots of PDSCH are scheduled, time slots of PDSCH are not scheduled, time slots of PDSCH are scheduled, time slots of PDSCH are not scheduled, and time slots of PDSCH are scheduled.

[0108] Here, the DCI field common to multiple or individual PDSCH / PUSCH schedules can be defined as follows.

[0109] MCS / NDI / RV can be publicly notified by the scheduler. For example, an MCS / NDI / RV field can also be publicly applied to all PDSCH / PUSCH schedulers. In addition, the MCS / NDI / RV record can be replaced with MCS, NDI, or RV, or any combination thereof, or even MCS, NDI, and RV.

[0110] MCS / NDI / RV can be notified by a field separated for each schedule. The number of fields for MCS / NDI / RV can be equal to the maximum number of schedulable PDSCH / PUSCH. Alternatively, it can be notified by bits separated for each schedule in a single field. The field length of MCS / NDI / RV can be N times the field length of a schedule used for PDSCH / PUSCH. N can be equal to the maximum number of schedulable PDSCH / PUSCH. The number of notification bits for a schedule used for PDSCH / PUSCH can be less than the existing MCS / NDI / RV field length.

[0111] When using a common MCS notification, the same MCS table or different MCS tables can be applied. When applying different MCS tables, the choice of which MCS table to apply can be indicated by bits contained in other fields of the DCI of the scheduled PDSCH / PUSCH. When this bit is 1, a low SE (Spectral efficiency) MCS table can be applied to the scheduled PDSCH / PUSCH; when this bit is not 1, another pre-defined MCS table can be used. These other fields can also be existing DCI fields; for example, in the case of separate notification, they can be fields indicating priority. Furthermore, these other fields can also be new DCI fields; for example, they can have a field length equal to the maximum number of schedulable PDSCH / PUSCHs.

[0112] When scheduling multiple PDSCHs, with maxNrofCodewordsScheduledByDCI set to 2, only one transport block (TB) can be allowed per PDSCH. For example, with separate notification, only the field corresponding to TB1 needs to be extended. Furthermore, with maxNrofCodewordsScheduledByDCI set to 2, similar to a single PDSCH, two TBs can be allowed per PDSCH. For example, with separate notification, the fields corresponding to TB1 and TB2 need to be extended.

[0113] FDRA can be publicly notified by the schedulers. For example, an FDRA field can be publicly applied to all PDSCH / PUSCH schedules. Alternatively, FDRA can also be notified by a field separate for each schedule. The number of FDRA fields can be equal to the maximum number of schedulable PDSCH / PUSCH. Alternatively, it can be notified by bits separate for each schedule within a single field. The length of the FDRA field can be N times the length of the field used by a schedule of PDSCH / PUSCH. N can be equal to the maximum number of schedulable PDSCH / PUSCH. The number of notification bits used for a schedule of PDSCH / PUSCH can be less than the length of the FDRA field in the prior art.

[0114] The priority indicator can also be communicated publicly or separately by each PDSCH / PUSCH scheduler, just like FDRA.

[0115] Regarding the HARQ process ID, the HPN field indicates the HARQ process ID corresponding to the initial PDSCH / PUSCH, and subsequent PDSCH / PUSCHs can increment the HAQ process ID sequentially.

[0116] Furthermore, HPN can also be notified via fields separated for each schedule. The number of HPN fields can be equal to the maximum number of schedulable PDSCH / PUSCH. Alternatively, it can be notified via bits separated for each schedule within a single field. The length of an HPN field can be N times the field length for a schedule of PDSCH / PUSCH. N can be equal to the maximum number of schedulable PDSCH / PUSCH. The number of notification bits used for a schedule of PDSCH / PUSCH can be less than the HPN field length in the prior art.

[0117] Regarding information related to CBG (Code Block Group) transmission and information indicating CBG completion, in the case of multiple PDSCH / PUSCH transmissions, CBG-based transmission is not considered. That is, in the case of multiple PDSCH / PUSCH transmissions, the corresponding field can be 0 bits. Furthermore, each TB of the scheduled PDSCH / PUSCH can be notified separately; for example, the bit length or number of fields can be determined based on the maximum number of schedulable PDSCH / PUSCHs.

[0118] The Transmission Configuration Indication (TCI) corresponding to multiple PDSCH schedules or the Resource Index (SRS) corresponding to multiple PUSCH schedules can be commonly notified by the schedules. For example, an FDRA field can be commonly applied to all PDSCH / PUSCH schedules. Alternatively, the TCI / SRI can be notified by fields separated for each schedule. The number of TCI / SRI fields can be equal to the maximum number of schedulable PDSCH / PUSCHs. Alternatively, it can be notified by bits separated for each schedule in a single field. The field length of the TCI / SRI can be N times the field length used for a single PDSCH / PUSCH schedule. N can be equal to the maximum number of schedulable PDSCH / PUSCHs. The number of notification bits for a single PDSCH / PUSCH schedule can be less than the existing TCI / SRI field length. The number of bits in the TCI / SRI field can be consistent with the number of beams contained in a subset. This subset can correspond to the available beams in the COT (Channel Occupancy Time) of unlicensed bandfield operations. Additionally, TCI / SRI can refer to both TCI and SRI, or either TCI or SRI.

[0119] The predetermined number of TCI / SRIs are notified, and the scheduled PDSCHs and TCI / SRIs can be mapped as follows.

[0120] For example, mapping can be performed using time slot-based repetition. For instance, two TCI states can be notified, applying the first TCI to the initial time slot, the second TCI to subsequent time slots, and repeating this process in later time slots. Alternatively, mapping can be performed using PDSCH / PUSCH repetition. For instance, two TCI states can be notified, applying the first TCI to the initial PDSCH, the second TCI to subsequent PDSCHs, and repeating this process in later PDSCHs.

[0121] Furthermore, mapping can also be performed according to time slot-based timing. For example, a TCI state can be associated with a time slot in which a PDSCH is scheduled, and the association between the time slot and the TCI state can be set by RRC. For example, two TCI states can be notified, and RRC settings can be used to associate the first two time slots with the first TCI state, the next two time slots with the second TCI state, and so on. Alternatively, mapping can be performed according to PDSCH / PUSCH-based timing. For example, a TCI state can be associated with the index of an object PDSCH among all scheduled PDSCHs, and the association between the PDSCH index and the TCI state can be set by RRC. For example, two TCI states can be notified, and RRC settings can be used to associate the first PDSCH with the first TCI state, the subsequent PDSCHs with the second TCI state, and so on.

[0122] The number of TCI / SRI states can be defined in the specification or set via RRC.

[0123] The TPMI (Transmitted Precoding Matrix Indicator) and RI (Rank Indicator) related to multiple PUSCH scheduling can be notified in the same way as the SRI described above, and which of the notification methods for the SRI described above is used can be determined independently of the SRI. Furthermore, the notification methods for TPMI and RI can also depend on the notification method for SRI. For example, in the case of common notification of SRI for all scheduled PDSCHs, common or separate TPMI and RI can also be notified. For example, in the case of separately notifying SRI for each scheduled PDSCH, separate TPMI and RI can be notified. When multiple SRI states are mapped to scheduled PDSCHs, the TPMI and RI corresponding to each SRI state can be notified.

[0124] The TPC (Transmit Power Control) command field related to multiple PUSCH scheduling can independently determine which of the aforementioned SRI notification methods to use. Furthermore, the TPC command notification method can also depend on the SRI notification method. For example, when publicly notifying the SRI for all scheduled PDSCHs, both public and separate TPC commands can be notified. Conversely, when separately notifying the SRI for each scheduled PDSCH, separate TPC commands can be notified. When multiple SRI states are mapped to scheduled PDSCHs, the TPC command corresponding to each SRI state can be notified.

[0125] Regarding the PUSCH transmit power control of terminal 20 based on TPC commands, it can also be operated as follows.

[0126] When terminal 20 is not configured with TPC-Accumulation, a TPC command is publicly notified to all PUSCHs, and this TPC command may be applied only once to the initial PUSCH. Alternatively, the TPC command may be separately notified to each PUSCH, and the TPC command may be applied to each PUSCH individually. For example, if no power adjustment is performed between two PUSCHs, the latter PUSCH may be notified with a TPC command value of 0. Furthermore, in the case of a mapping of multiple TPC commands, in each set of PUSCHs with the same power control state, the corresponding TPC command value may be applied only to the initial PUSCH within that set.

[0127] When tpc-Accumulation is set in terminal 20, the notified TPC command value can also be applied to the corresponding PUSCH.

[0128] Furthermore, which action can be performed in the above embodiments can be set by higher-level parameters, reported by the terminal 20 as a UE capability, defined by specifications, or determined by the setting of higher-level parameters and UE capabilities.

[0129] Alternatively, the following UE capability can be defined, which indicates whether the terminal 20 supports scheduling of multiple PDSCHs or multiple PUSCHs based on a single DCI, according to the existing UE-inherent DCI format.

[0130] Alternatively, the following UE capability can be defined, which indicates whether the terminal 20 supports scheduling of multiple PDSCHs or multiple PUSCHs based on a single DCI, according to the new UE-inherent DCI format.

[0131] Through the above embodiments, base station 10 can efficiently schedule multiple PDSCH / PUSCH of the envisioned LBT.

[0132] That is, in a wireless communication system, scheduling corresponding to the communication method can be performed.

[0133] (Device structure)

[0134] Next, an example of the functional structure of the base station 10 and terminal 20 performing the processes and actions described above will be explained. The base station 10 and terminal 20 include the functions implemented in the above embodiments. However, the base station 10 and terminal 20 may each have only a portion of the functions described in the embodiments.

[0135] <Base Station 10>

[0136] Figure 13 This is a diagram illustrating an example of the functional structure of base station 10 in an embodiment of the present invention. For example... Figure 13 As shown, the base station 10 has a transmitting unit 110, a receiving unit 120, a setting unit 130 and a control unit 140. Figure 13 The functional structure shown is only one example. As long as the actions involved in the embodiments of the present invention can be performed, the functional distinctions and names of the functional parts can be arbitrary.

[0137] The transmitting unit 110 includes the function of generating a signal to be transmitted to the terminal 20 and wirelessly transmitting the signal. Furthermore, the transmitting unit 110 transmits inter-network node messages to other network nodes. The receiving unit 120 includes the function of receiving various signals transmitted from the terminal 20 and obtaining, for example, higher-level information from the received signals. Furthermore, the transmitting unit 110 has the function of transmitting NR-PSS, NR-SSS, NR-PBCH, DL / UL control signals, etc., to the terminal 20. Furthermore, the receiving unit 120 receives inter-network node messages from other network nodes.

[0138] The setting unit 130 stores preset setting information and various setting information sent to the terminal 20. The content of the setting information includes, for example, information related to measurement settings.

[0139] As described in the embodiment, the control unit 140 performs control related to the setting of the measurement. Additionally, the control unit 140 performs scheduling. Alternatively, the signal transmission-related functions of the control unit 140 may be included in the transmitting unit 110, and the signal reception-related functions of the control unit 140 may be included in the receiving unit 120.

[0140] Terminal 20

[0141] Figure 14 This is a diagram illustrating an example of the functional structure of terminal 20 in an embodiment of the present invention. For example... Figure 14 As shown, the terminal 20 has a transmitting unit 210, a receiving unit 220, a setting unit 230, and a control unit 240. Figure 14 The functional structure shown is only one example. As long as the actions involved in the embodiments of the present invention can be performed, the functional distinctions and names of the functional parts can be arbitrary.

[0142] The transmitting unit 210 generates a transmission signal based on the transmission data and transmits the transmission signal wirelessly. The receiving unit 220 wirelessly receives various signals and obtains higher-layer signals from the received physical layer signals. Furthermore, the receiving unit 220 has the function of receiving NR-PSS, NR-SSS, NR-PBCH, DL / UL / SL control signals, etc., transmitted from the base station 10. For example, as D2D communication, the transmitting unit 210 transmits PSCCH (Physical Sidelink Control Channel), PSSCH (Physical Sidelink Shared Channel), PSDCH (Physical Sidelink Discovery Channel), PSBCH (Physical Sidelink Broadcast Channel), etc., to other terminals 20, and the receiving unit 220 receives PSCCH, PSSCH, PSDCH, or PSBCH from other terminals 20.

[0143] The setting unit 230 stores various setting information received from the base station 10 by the receiving unit 220. In addition, the setting unit 230 also stores preset setting information. The content of the setting information includes, for example, information related to measurement settings.

[0144] As described in the embodiment, the control unit 240 performs control related to the setting of the measurement. Alternatively, the signal transmission-related functions of the control unit 240 may be included in the transmitting unit 210, and the signal reception-related functions of the control unit 240 may be included in the receiving unit 220.

[0145] (Hardware structure)

[0146] The block diagram used in the description of the above embodiments ( Figure 13 and Figure 14 The diagram illustrates blocks organized by function. These functional blocks (structural units) are implemented through any combination of at least one of hardware and software. Furthermore, there are no particular limitations on the implementation method of each functional block. That is, each functional block can be implemented using a single device that is physically or logically combined, or by directly or indirectly (e.g., using wired, wireless, etc.) connecting two or more physically or logically separate devices. Functional blocks can also be implemented by combining software within the aforementioned single or multiple devices.

[0147] The functions include judgment, decision, determination, calculation, calculation, processing, derivation, investigation, search, confirmation, receiving, sending, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assigning, but are not limited to these. For example, the functional block (structural part) that enables sending is called the transmitting unit or transmitter. In short, as mentioned above, there are no particular limitations on the implementation method.

[0148] For example, in one embodiment of this disclosure, the base station 10, terminal 20, etc., can also function as a computer for processing the wireless communication method of this disclosure. Figure 15 This is a diagram illustrating an example of the hardware structure of a base station 10 and a terminal 20 according to an embodiment of the present disclosure. The base station 10 and the terminal 20 may also be configured as a computer device that physically includes a processor 1001, a storage device 1002, an auxiliary storage device 1003, a communication device 1004, an input device 1005, an output device 1006, and a bus 1007.

[0149] Additionally, in the following description, the term "device" can be replaced with "circuit," "device," "unit," etc. The hardware structure of base station 10 and terminal 20 can be configured to include one or more of the devices shown in the figures, or it can be configured to not include any of them.

[0150] The functions in base station 10 and terminal 20 are implemented by reading predetermined software (programs) into hardware such as processor 1001 and storage device 1002, so that processor 1001 performs calculations and controls the communication of communication device 1004 or controls at least one of reading and writing data in storage device 1002 and auxiliary storage device 1003.

[0151] The processor 1001 controls the computer as a whole by instructing the operating system to operate. The processor 1001 may also be a central processing unit (CPU) that includes interfaces with peripheral devices, control units, arithmetic units, registers, etc. For example, the aforementioned control unit 140, control unit 240, etc., can also be implemented using the processor 1001.

[0152] Furthermore, the processor 1001 reads programs (program code), software modules, or data from at least one of the auxiliary storage devices 1003 and communication devices 1004, and performs various processes accordingly. As a program, a program is used that causes the computer to perform at least a portion of the actions described in the above embodiments. For example, Figure 13 The control unit 140 of the base station 10 shown can also be implemented by a control program stored in the storage device 1002 and operated in the processor 1001. And, for example, Figure 14 The control unit 240 of the terminal 20 shown can also be implemented by a control program stored in the storage device 1002 and operated in the processor 1001. Although it has been described that the various processes described above are executed by one processor 1001, the various processes described above can also be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 can also be implemented by more than one chip. In addition, the program can also be sent from the network via a telecommunications line.

[0153] Storage device 1002 is a computer-readable recording medium, and may be composed of at least one of ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), etc. Storage device 1002 may also be referred to as a register, cache, main memory (main storage device), etc. Storage device 1002 can store programs (program code), software modules, etc., that are executable for implementing the communication method according to one embodiment of this disclosure.

[0154] The auxiliary storage device 1003 is a computer-readable recording medium, such as at least one of the following: CD-ROM (CompactDisc ROM) or other optical discs, hard disks, floppy disks, magneto-optical discs (e.g., compact discs, digital multifunction discs, Blu-ray discs, smart cards, flash memory (e.g., cards, sticks, key drives), floppy disks, magnetic stripes, etc. The aforementioned storage medium may, for example, be a database, server, or other suitable media that includes at least one of the storage device 1002 and the auxiliary storage device 1003.

[0155] The communication device 1004 is hardware (transceiver) used for communication between computers via at least one of a wired network and a wireless network. It may also be referred to as a network device, network controller, network interface card (NIC), communication module, etc. The communication device 1004 may, for example, be configured to include a high-frequency switch, duplexer, filter, frequency synthesizer, etc., to implement at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, transceiver antennas, amplifier sections, transceiver sections, transmission path interfaces, etc., can also be implemented using the communication device 1004. The transceiver section may also be physically or logically separated into a transmitting section and a receiving section.

[0156] Input device 1005 is an input device that accepts input from external sources (e.g., keyboard, mouse, microphone, switch, button, sensor, etc.). Output device 1006 is an output device that performs output to external sources (e.g., display, speaker, LED, etc.). Alternatively, input device 1005 and output device 1006 can also be integrated (e.g., a touch panel).

[0157] Furthermore, the processor 1001 and storage device 1002, among other devices, are connected via a bus 1007 for communicating information. The bus 1007 can be a single bus or can be composed of different buses between devices.

[0158] Furthermore, the base station 10 and the terminal 20 can be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), or a FPGA (Field Programmable Gate Array), and can also use this hardware to implement part or all of the functional blocks. For example, the processor 1001 can also be implemented using at least one of these hardware components.

[0159] (Summary of implementation methods)

[0160] As described above, according to an embodiment of the present invention, a terminal is provided, comprising: a receiving unit that receives a downlink control channel and a plurality of scheduled downlink shared channels; and a control unit that, when receiving the downlink shared channels, envisions a plurality of start positions in the time domain for the downlink shared channels in a time slot in which listen-before-speak (LBT) is required or in a time slot in which the monitoring period of the downlink control channel can be one or more time slots.

[0161] With the above structure, base station 10 can efficiently schedule multiple PDSCH / PUSCH of the envisioned LBT. That is, in the wireless communication system, scheduling corresponding to the communication mode can be performed.

[0162] Alternatively, when receiving the downlink shared channel, the control unit may, within the initial time slot of the scheduled timeslots of the plurality of downlink shared channels, assume multiple start positions of the downlink shared channel in the time domain. Through this structure, the base station 10 can efficiently schedule multiple PDSCH / PUSCHs of the assumed LBT.

[0163] The multiple start positions can also be determined by adding an integer multiple of a length L to a start position S. With this structure, base station 10 can efficiently schedule multiple PDSCH / PUSCH of the envisioned LBT.

[0164] Alternatively, when receiving the downlink shared channel, the control unit may designate the start position of the downlink shared channel in the time domain as the start of the time slot, excluding the starting time slot and the time slot requiring LBT, within the time slots where the multiple downlink shared channels are scheduled. With this structure, the base station 10 can efficiently schedule multiple PDSCH / PUSCHs with designed LBT.

[0165] Furthermore, according to an embodiment of the present invention, a terminal is provided, comprising: a receiving unit that receives a downlink control channel; a transmitting unit that transmits a plurality of scheduled uplink shared channels; and a control unit that, when transmitting the uplink shared channels, envisions a plurality of start positions in the time domain for the uplink shared channels in a time slot in which a listen-before-speak (LBT) time slot or a time slot in which the monitoring period of the downlink control channel can be one or more time slots.

[0166] With the above structure, base station 10 can efficiently schedule multiple PDSCH / PUSCH of the envisioned LBT. That is, in the wireless communication system, scheduling corresponding to the communication mode can be performed.

[0167] Furthermore, according to an embodiment of the present invention, a base station is provided, comprising: a transmitting unit that transmits a downlink control channel and a plurality of scheduled downlink shared channels; and a control unit that, when transmitting the downlink shared channels, envisions a plurality of start positions in the time domain for the downlink shared channels in a time slot in which the multiple downlink shared channels are scheduled, where a listen-before-tell (LBT) time slot or a time slot in which the monitoring period of the downlink control channel can be one or more time slots.

[0168] With the above structure, base station 10 can efficiently schedule multiple PDSCH / PUSCH of the envisioned LBT. That is, in the wireless communication system, scheduling corresponding to the communication mode can be performed.

[0169] In addition, according to an embodiment of the present invention, a communication method is provided, wherein a terminal performs the following steps: a receiving step, receiving a downlink control channel and a plurality of scheduled downlink shared channels; and a control step, when receiving the downlink shared channels, in the time slots in which the plurality of downlink shared channels are scheduled, in the time slots that require Listen-Before-Speak (LBT) or in the time slots in which the monitoring period of the downlink control channel can be more than one time slot, envisioning a plurality of start positions in the time domain for the downlink shared channels.

[0170] With the above structure, base station 10 can efficiently schedule multiple PDSCH / PUSCH of the envisioned LBT. That is, in the wireless communication system, scheduling corresponding to the communication mode can be performed.

[0171] (Supplement to the implementation method)

[0172] The embodiments of the present invention have been described above, but the disclosed invention is not limited to such embodiments. Those skilled in the art should understand various modifications, alterations, substitutions, and replacements. Specific numerical examples have been used to facilitate understanding of the invention, but unless otherwise specified, these values ​​are merely examples, and any appropriate values ​​may be used. The distinctions between items in the above description are not essential to the present invention; items described in two or more items may be combined as needed, and items described in one item may be applied to items described in another item (as long as there is no contradiction). The boundaries of functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries of physical components. Multiple functional units may be operated by a single physical component, or a single functional unit may be operated by multiple physical components. Regarding the processing described in the embodiments, the order of processing may be interchanged unless there is a contradiction. For ease of explanation, a functional block diagram has been used to illustrate the base station 10 and terminal 20, but such a device may also be implemented by hardware, software, or a combination thereof. Software operating according to embodiments of the present invention via the processor of base station 10 and software operating according to embodiments of the present invention via the processor of terminal 20 may also be stored in random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, registers, hard disk (HDD), removable disk, CD-ROM, database, server, and other suitable storage media, respectively.

[0173] Furthermore, the notification of information is not limited to the methods / implementations described in this disclosure, and other methods may also be used. For example, the notification of information may be implemented through physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), higher layer signaling (e.g., RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling, broadcast information (MIB (Master Information Block), SIB (System Information Block)), other signals, or combinations thereof. In addition, RRC signaling may be referred to as an RRC message, for example, it may also be an RRC Connection Setup message, an RRC Connection Reconfiguration message, etc.

[0174] The various methods / implementations described in this disclosure can also be applied to systems utilizing LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), FRA (Future Radio Access), NR (new Radio), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, UWB (Ultra-Wideband), Bluetooth (registered trademark), other suitable systems, and next-generation systems extended therefrom. Furthermore, multiple systems can be combined (e.g., a combination of at least one of LTE and LTE-A with 5G, etc.).

[0175] The processing procedures, timing, and flow of the various methods / implementations described in this specification may be rearranged in order, provided there is no contradiction. For example, the elements of various steps are indicated using an illustrative order for the methods described in this disclosure, but are not limited to the specific order indicated.

[0176] In this specification, certain actions performed by base station 10 may sometimes also be performed by its upper node, depending on the circumstances. In a network consisting of one or more network nodes having base station 10, it is obvious that various actions performed to communicate with terminal 20 can be performed by at least one of base station 10 and other network nodes besides base station 10 (e.g., considering MME or S-GW, but not limited to these). The above example illustrates the case where there is one other network node besides base station 10, but other network nodes can also be a combination of multiple other network nodes (e.g., MME and S-GW).

[0177] The information or signals described in this disclosure can be output from a higher (or lower) layer to a lower (or higher) layer. They can also be input or output via multiple network nodes.

[0178] Input or output information can be stored in a specific location (e.g., memory) or managed using a management table. Input or output information can be overwritten, updated, or appended. Output information can also be deleted. Input information can also be sent to other devices.

[0179] The determination in this disclosure can be made by a value represented by 1 bit (0 or 1), by a Boolean value (Boolean: true or false), or by a comparison of numerical values ​​(e.g., a comparison with a predetermined value).

[0180] Software, whether called software, firmware, middleware, microcode, hardware description language, or by other names, should be broadly interpreted as referring to commands, command sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc.

[0181] In addition, software, commands, and information can also be sent and received via transmission media. For example, when software is sent from a webpage, server, or other remote source using at least one of wired technologies (coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) etc.) and wireless technologies (infrared, microwave, etc.), at least one of these wired and wireless technologies is included within the definition of transmission media.

[0182] The information, signals, etc., described in this disclosure can also be represented using any of a variety of different technologies. For example, the data, commands, instructions, information, signals, bits, symbols, chips, etc., that may be involved in the above description as a whole can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any combination of these.

[0183] Furthermore, the terms used in this disclosure and those necessary for understanding this disclosure may be replaced with terms that have the same or similar meanings. For example, at least one of the channel and symbol may also be a signal (signaling). Additionally, a signal may also be a message. Furthermore, a component carrier (CC) may also be referred to as carrier frequency, cell, frequency carrier, etc.

[0184] The terms “system” and “network” as used in this disclosure are used interchangeably.

[0185] Furthermore, the information, parameters, etc., described in this disclosure may be represented using absolute values, relative values ​​to predetermined values, or other corresponding information. For example, wireless resources may be indicated using indexes.

[0186] The names used for the above parameters are non-limiting in any respect. Furthermore, the formulas, etc., using these parameters sometimes differ from those explicitly disclosed in this disclosure. Various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by all appropriate names, therefore the various names assigned to these channels and information elements are non-limiting in any respect.

[0187] In this disclosure, the terms "base station (BS)," "wireless base station," "base station device," "fixed station," "NodeB," "eNodeB (eNB)," "gNodeB (gNB)," "access point," "transmission point," "reception point," "transmission / reception point," "cell," "sector," "cell group," "carrier," and "component carrier" are used interchangeably. Sometimes, terms such as macro cell, small cell, femtocell, and picocell are also used to refer to base stations.

[0188] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, its coverage area can be divided into several smaller areas, each of which can provide communication services through a base station subsystem (e.g., a small indoor base station RRH: Remote Radio Head). Terms such as "cell" or "sector" refer to a portion or all of the coverage area of ​​at least one of the base station and base station subsystem providing communication services within that coverage area.

[0189] In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," and "terminal" can be used interchangeably.

[0190] For mobile stations, those skilled in the art sometimes also use the following terms: subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handheld device, user agent, mobile client, client, or some other appropriate terms.

[0191] At least one of the base station and mobile station can also be referred to as a transmitting device, receiving device, communication device, etc. Additionally, at least one of the base station and mobile station can also be a device mounted on a mobile body, the mobile body itself, etc. The mobile body can be a vehicle (e.g., a car, an airplane, etc.), a mobile body moving in an unmanned manner (e.g., a drone, an autonomous vehicle, etc.), or a robot (humanized or unmanned). Furthermore, at least one of the base station and mobile station also includes devices that do not necessarily move during communication. For example, at least one of the base station and mobile station can be an IoT (Internet of Things) device such as a sensor.

[0192] Furthermore, the base station in this disclosure can also be replaced by a user terminal. For example, the communication between the base station and the user terminal can be replaced by communication between multiple terminals 20 (e.g., D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.), and various methods / implementations of this disclosure can also be applied. In this case, the terminal 20 can also be configured to have the functions of the base station 10 described above. In addition, terms such as "uplink" and "downlink" can be replaced with terms corresponding to inter-terminal communication (e.g., "side"). For example, uplink channel, downlink channel, etc. can also be replaced with side channel.

[0193] Similarly, the user terminal in this disclosure can be replaced by a base station. In this case, the base station can also be configured to have the functions of the aforementioned user terminal.

[0194] The terms "determining" and "determining" as used in this disclosure sometimes encompass a variety of actions. For example, "determining" or "determining" may include actions such as judging, calculating, computing, processing, deriving, investigating, searching (e.g., searching in a table, database, or other data structure), and ascertaining, which are considered as actions of "determining" or "determining." Furthermore, "determining" or "determining" may include actions such as receiving (e.g., receiving information), transmitting (e.g., sending information), inputting, outputting, and accessing (e.g., accessing data in memory), which are considered as actions of "determining" or "determining." Additionally, "determining" or "determining" may include actions such as resolving, selecting, choosing, establishing, and comparing, which are considered as actions of "determining" or "determining." That is, "judgment" and "decision" can include matters that are considered as having been "judged" or "decided". In addition, "judgment (decision)" can also be replaced by "assuming", "expecting", "considering", etc.

[0195] The terms “connected,” “coupled,” or any variations thereof are intended to indicate any direct or indirect connection or combination between two or more elements, including cases where there is one or more intermediate elements between the two elements that are “connected” or “coupled.” The combination or connection between elements can be physical, logical, or a combination of these. For example, “access” can be used instead of “connected.” In the context of this disclosure, it can be understood that two elements are “connected” or “coupled” to each other using at least one of one or more wires, cables, and printed electrical connections, and, as some non-limiting and non-inclusive examples, using electromagnetic energy with wavelengths in the wireless frequency domain, microwave region, and light (including both visible and invisible regions) to “connect” or “couple” to each other.

[0196] The reference signal can be simply called RS (Reference Signal), or, depending on the standard applied, pilot.

[0197] As used in this disclosure, the word "based on" does not mean "based on only" unless otherwise expressly stated. In other words, the word "based on" means both "based on only" and "based on at least" both.

[0198] Any reference to an element using the designations “first,” “second,” etc., as used in this disclosure does not necessarily limit the number or order of these elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Therefore, references to “first element” and “second element” do not imply that only two elements can be taken, or that in any form the first element must precede the second element.

[0199] Alternatively, the "unit" in the structure of the above devices can be replaced with "section", "circuit", "equipment", etc.

[0200] When the terms "include," "including," and their variations are used in this disclosure, these terms, like the term "comprising," imply inclusion. Furthermore, the term "or" as used in this disclosure does not refer to XOR.

[0201] A radio frame can consist of one or more frames in the time domain. Each frame in the time domain is called a subframe. A subframe can also consist of one or more time slots in the time domain. A subframe can also be a fixed time length (e.g., 1 ms) independent of the parameter set (numerology).

[0202] A parameter set can be communication parameters applied to at least one of the transmission and reception of a signal or channel. For example, a parameter set can represent at least one of the following: Subcarrier Spacing (SCS), bandwidth, symbol length, cyclic prefix length, Transmission Time Interval (TTI), number of symbols per TTI, radio frame structure, specific filtering processing performed by the transceiver in the frequency domain, and specific windowing processing performed by the transceiver in the time domain.

[0203] In the time domain, a time slot can be composed of one or more symbols (OFDM (Orthogonal Frequency Division Multiplexing) symbols, SC-FDMA (Single Carrier Frequency Division Multiple Access) symbols, etc.). A time slot can be a time unit based on a set of parameters.

[0204] A time slot can contain multiple mini-time slots. Each mini-time slot can consist of one or more symbols in the time domain. Furthermore, a mini-time slot can also be called a sub-time slot. A mini-time slot can consist of fewer symbols than a time slot. PDSCH (or PUSCH) transmitted in time units larger than mini-time slots can be called PDSCH (or PUSCH) mapping type (type) A. PDSCH (or PUSCH) transmitted using mini-time slots can be called PDSCH (or PUSCH) mapping type (type) B.

[0205] Radio frames, subframes, time slots, mini-time slots, and symbols all represent time units for transmitting signals. Radio frames, subframes, time slots, mini-time slots, and symbols can each be referred to by other corresponding names.

[0206] For example, a subframe can be called a Transmission Time Interval (TTI), multiple consecutive subframes can also be called a TTI, and a time slot or a mini-time slot can also be called a TTI. That is, at least one of a subframe and a TTI can be a subframe (1ms) in existing LTE, a period shorter than 1ms (e.g., 1-13 symbols), or a period longer than 1ms. In addition, the unit representing TTI may not be called a subframe, but a time slot, mini-time slot, etc.

[0207] Here, TTI refers, for example, to the smallest unit of time for scheduling in wireless communication. For instance, in an LTE system, the base station schedules the allocation of radio resources (bandwidth, transmit power, etc., available to each terminal 20) in units of TTI. However, the definition of TTI is not limited to this.

[0208] The Time Interval (TTI) can be a unit of time for transmitting channel-coded data packets (transmission blocks), code blocks, codewords, etc., or it can be a processing unit such as scheduling or link adaptation. Furthermore, when a TTI is given, the actual time interval (e.g., the number of symbols) that the transmission block, code block, codeword, etc., are mapped to can be shorter than the TTI.

[0209] Furthermore, when one time slot or one mini-time slot is referred to as a TTI, more than one TTI (i.e., more than one time slot or more than one mini-time slot) can become the minimum time unit for scheduling. In addition, the number of time slots (mini-time slots) constituting the minimum time unit for scheduling can be controlled.

[0210] A TTI with a duration of 1ms is also called a normal TTI (TTI in LTE Rel.8-12), a long TTI, a normal subframe, a long subframe, or a time slot. A TTI shorter than a normal TTI can also be called a shortened TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a mini time slot, a sub-time slot, or a time slot.

[0211] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) can be understood as a TTI with a duration of more than 1ms, and a short TTI (e.g., a shortened TTI, etc.) can be understood as a TTI with a duration of less than a long TTI but more than 1ms.

[0212] A resource block (RB) is a unit of resource allocation in both the time and frequency domains. In the frequency domain, it can contain one or more consecutive subcarriers. The number of subcarriers contained in an RB can be the same regardless of the parameter set, for example, it can be 12. The number of subcarriers contained in an RB can also be determined based on the parameter set.

[0213] Furthermore, the temporal domain of an RB can contain one or more symbols, which can be a single time slot, a single mini-time slot, a single subframe, or the length of a single TTI. A single TTI, a single subframe, etc., can each be composed of one or more resource blocks.

[0214] In addition, one or more RBs can also be called Physical Resource Block (PRB), Sub-Carrier Group (SCG), Resource Element Group (REG), PRB pair, RB pair, etc.

[0215] Furthermore, a resource block can consist of one or more resource elements (REs). For example, one RE can be a radio resource area consisting of one subcarrier and one symbol.

[0216] The Bandwidth Part (BWP) (also known as partial bandwidth, etc.) can also represent a subset of contiguous common resource blocks (RBs) used for a certain parameter set in a certain carrier. Here, common RBs can be determined by indexing RBs based on a common reference point of that carrier. PRBs can be defined and numbered within a BWP.

[0217] A BWP can include a UL BWP and a DL BWP. One or more BWPs can be set for a UE within a single carrier.

[0218] At least one of the configured BWPs can be active, and it is not assumed that the UE will transmit or receive predetermined signals / channels outside of the active BWP. In addition, the terms "cell" and "carrier" in this disclosure can be replaced by "BWP".

[0219] The structures of radio frames, subframes, time slots, mini-time slots, and symbols described above are merely illustrative. For example, the number of subframes contained in a radio frame, the number of time slots in each subframe or radio frame, the number of mini-time slots contained in a time slot, the number of symbols and RBs contained in a time slot or mini-time slot, the number of subcarriers contained in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, and other structures can be varied in many ways.

[0220] In this disclosure, for example, in cases where articles are added through translation, such as in English (e.g., a, an, and the), this disclosure also includes cases where the noun following these articles is in a plural form.

[0221] In this disclosure, the phrase "A and B are different" can also mean "A and B are not the same." Furthermore, this phrase can also mean "A and B are each different from C." Terms such as "separate" and "combined" can also be interpreted in the same way as "different."

[0222] The various methods / implementations described in this disclosure can be used individually or in combination, and can be switched depending on the execution. Furthermore, the notification of predetermined information is not limited to explicit notification (e.g., a "Yes X" notification) but can also be implicit notification (e.g., not notifying the predetermined information).

[0223] Furthermore, the PDSCH in this disclosure is an example of a downlink shared channel. The PDCCH is an example of a downlink control channel.

[0224] The present disclosure has been described in detail above, but it will be clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented as modifications and variations without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the present disclosure is for illustrative purposes only and is not intended to be limiting.

[0225] Label Explanation

[0226] 10: Base station

[0227] 110: Sending Department

[0228] 120: Receiving Department

[0229] 130: Setting Department

[0230] 140: Control Department

[0231] 20: Terminal

[0232] 210: Sending Department

[0233] 220: Receiving Department

[0234] 230: Setting Department

[0235] 240: Control Department

[0236] 1001: Processor

[0237] 1002: Storage device

[0238] 1003: Auxiliary storage device

[0239] 1004: Communication device

[0240] 1005: Input device

[0241] 1006: Output device

Claims

1. A terminal having: The receiving unit receives PDCCHs in DCI format, wherein... DCI refers to Downlink Control Information, and PDCCH refers to Physical Downlink Control Channel; and The control unit, based on a TDRA index contained in the DCI format, determines multiple sets of mapping types and SLIVs, and applies each set contained in the multiple sets to the corresponding PDSCHs within multiple PDSCHs scheduled by the DCI format. Here, TDRA refers to Time domain resource allocation, SLIV refers to Start and Length Indicator Value, and PDSCH refers to Physical Downlink Shared Channel. For each PDSCH scheduled by the DCI format, the NDI field and RV field contained in the DCI format are applied separately. The HPN field contained in the DCI format is applied to the initial PDSCH scheduled by the DCI format, and for each subsequent PDSCH, the HARQ process ID is applied incrementally. The TCI field contained in the DCI format is applied to all PDSCHs scheduled by the DCI format, where TCI stands for Transmission Configuration Indication. The receiving unit receives multiple PDSCHs scheduled by the DCI format.

2. A base station, comprising: The transmitting unit transmits PDCCHs in DCI format, wherein... DCI refers to Downlink Control Information, and PDCCH refers to Physical Downlink Control Channel; and The control unit, based on a TDRA index contained in the DCI format, determines multiple sets of mapping types and SLIVs, and applies each set contained in the multiple sets to the corresponding PDSCHs within multiple PDSCHs scheduled by the DCI format. Here, TDRA refers to Time domain resource allocation, SLIV refers to Start and Length Indicator Value, and PDSCH refers to Physical Downlink Shared Channel. For each PDSCH scheduled by the DCI format, the NDI field and RV field contained in the DCI format are applied separately. The HPN field contained in the DCI format is applied to the initial PDSCH scheduled by the DCI format, and for each subsequent PDSCH, the HARQ process ID is applied incrementally. The TCI field contained in the DCI format is applied to all PDSCHs scheduled by the DCI format, where TCI stands for Transmission Configuration Indication. The transmitting unit transmits multiple PDSCHs scheduled by the DCI format.

3. A communication system comprising a terminal and a base station, wherein, The terminal has: The receiving unit receives a PDCCH carrying DCI format from the base station, where DCI refers to Downlink Control Information and PDCCH refers to Physical Downlink Control Channel; and The control unit, based on a TDRA index contained in the DCI format, determines multiple sets of mapping types and SLIVs, and applies each set contained in the multiple sets to the corresponding PDSCHs within multiple PDSCHs scheduled by the DCI format. Here, TDRA refers to Time domain resource allocation, SLIV refers to Start and Length Indicator Value, and PDSCH refers to Physical Downlink Shared Channel. For each PDSCH scheduled by the DCI format, the NDI field and RV field contained in the DCI format are applied separately. The HPN field contained in the DCI format is applied to the initial PDSCH scheduled by the DCI format, and for each subsequent PDSCH, the HARQ process ID is applied incrementally. The TCI field contained in the DCI format is applied to all PDSCHs scheduled by the DCI format, where TCI stands for Transmission Configuration Indication. The receiving unit receives multiple PDSCHs scheduled by the DCI format from the base station. The base station has: The transmitting unit transmits the PDCCH carrying the DCI format to the terminal; and The control unit, based on a TDRA index contained in the DCI format, determines multiple sets of mapping types and SLIVs, and applies each set contained in the multiple sets to the corresponding PDSCHs within the multiple PDSCHs scheduled by the DCI format. For each PDSCH scheduled by the DCI format, the NDI field and RV field contained in the DCI format are applied separately. The HPN field contained in the DCI format is applied to the initial PDSCH scheduled by the DCI format, and for each subsequent PDSCH, the HARQ process ID is applied incrementally. The TCI field contained in the DCI format is applied to all PDSCHs scheduled by the DCI format. The transmitting unit transmits multiple PDSCHs scheduled by the DCI format.

4. A communication method, wherein, The terminal performs the following steps: Receive PDCCH carrying DCI format, where DCI refers to Downlink Control Information and PDCCH refers to Physical Downlink Control Channel. Based on a TDRA index contained in the DCI format, multiple sets of mapping types and SLIVs are determined. Each set contained in these multiple sets is applied to the corresponding PDSCH within multiple PDSCHs scheduled by the DCI format. Here, TDRA refers to Time domain resource allocation, SLIV refers to Start and Length Indicator Value, and PDSCH refers to Physical Downlink Shared Channel. For each PDSCH scheduled by the DCI format, the NDI field and RV field contained in the DCI format are applied separately. The HPN field contained in the DCI format is applied to the initial PDSCH scheduled by the DCI format, and for each subsequent PDSCH, the HARQ process ID is applied incrementally. The TCI field contained in the DCI format is applied to all PDSCHs scheduled by the DCI format, where TCI stands for Transmission Configuration Indication; and Receive multiple PDSCHs scheduled by the DCI format.

Images