Terminal equipment, base station equipment, and communication methods

Abstract

This terminal device (40) has a transceiver (41) and a hardware processor (45). The hardware processor (45) receives one physical downlink control channel (PDCCH) via the transceiver (41). The one PDCCH schedules a plurality of physical shared channels in one or more carriers or in one or more slots. The one PDCCH and the plurality of physical shared channels are what is transmitted to the address of the terminal device (40). The plurality of physical shared channels are a plurality of physical downlink shared channels (PDSCH) or a plurality of physical uplink shared channels (PUSCH).

Description

Technical Field

[0001] The present disclosure relates to a terminal device, a base station device, and a communication method.

Background Art

[0002] Wireless access methods and wireless networks for cellular mobile communications (hereinafter also referred to as "Long Term Evolution (LTE)", "LTE-Advanced (LTE-A)", "LTE-Advanced Pro (LTE-A Pro)", "New Radio (NR)", "New Radio Access Technology (NRAT)", "Evolved Universal Terrestrial Radio Access (EUTRA)", or "Further EUTRA (FEUTRA)") are being studied in the Third Generation Partnership Project (3GPP). In the following description, LTE includes LTE-A, LTE-A Pro, and EUTRA, and NR includes NRAT and FEUTRA. In LTE and NR, a base station device (base station) is also referred to as an eNodeB (evolved NodeB), and a terminal device (mobile station, mobile station device, terminal) is also referred to as a UE (User Equipment). However, the base station device may sometimes be referred to as a gNodeB or gNB. LTE and NR are cellular communication systems in which a plurality of areas covered by a base station device are arranged in a cell shape. A single base station device may manage a plurality of cells.

[0003] NR is a Radio Access Technology (RAT) distinct from LTE, serving as a next-generation wireless access method. NR is an access technology capable of supporting various use cases, including eMBB (Enhanced Mobile Broadband), mMTC (Massive Machine Type Communications), and URLLC (Ultra Reliable and Low Latency Communications). 3GPP is working on standardizing NR to support these use cases.

[0004] Here, eMBB is an important use case for realizing high-speed, high-capacity communication such as high-definition video streaming transmission, AR (augmented reality), and VR (virtual reality). Furthermore, URLLC is an important use case for 5G, as it requires highly reliable and low-latency communication in use cases such as autonomous driving and automated factories. [Prior art documents] [Non-patent literature]

[0005] [Non-Patent Document 1] "3GPP TS38.214 version 16.6.0 Release 16", [online], [searched July 7, 2021], Internet<https: / / www.3gpp.org / ftp / / Specs / archive / 38_series / 38.214 / 38214-g60.zip> [Overview of the project] [Problems that the invention aims to solve]

[0006] However, in previous 5G technologies, the standards for the functions and technologies necessary to realize each use case were developed separately. Specifically, for technologies to realize eMBB, standards were developed with the aim of realizing broadband transmission and improving frequency utilization efficiency. On the other hand, for technologies to realize URLLC, standards were developed with the aim of improving reliability and transmission delay at the expense of frequency utilization efficiency.

[0007] In next-generation wireless communication systems, referred to as Beyond 5G and 6G, areas where these use cases overlap are being explored as new use cases. For example, use cases such as digital twin and tactile communication require the realization of both high-speed, high-capacity communication and high-quality, low-latency communication. In other words, realizing such use cases requires broadband transmission, improved frequency utilization efficiency, and improved reliability and transmission delay simultaneously.

[0008] Therefore, this disclosure provides a mechanism that can achieve both broadband transmission, improved frequency utilization efficiency, and improved reliability and transmission delay.

[0009] It should be noted that the above-mentioned problems or objectives are merely one of several problems or objectives that can be solved or achieved by the multiple embodiments disclosed herein. [Means for solving the problem]

[0010] The present disclosure provides a terminal device. The terminal device comprises a transceiver and a hardware processor. The hardware processor receives one PDCCH (Physical Downlink Control Channel) via the transceiver. The one PDCCH schedules multiple physical shared channels in one or more carriers or one or more slots. The one PDCCH and the multiple physical shared channels are transmitted to the terminal device. The multiple physical shared channels are multiple PDSCHs (Physical Downlink Shared Channels) or multiple PUSCHs (Physical Uplink Shared Channels). [Brief explanation of the drawing]

[0011] [Figure 1] This figure shows an example of the overall configuration of a communication system according to the embodiment of this disclosure. [Figure 2] This figure shows an example configuration of a base station device according to the present disclosure. [Figure 3] This figure shows an example configuration of a terminal device according to the embodiments of this disclosure. [Figure 4] This figure shows an example of a sequence diagram between a base station device and a terminal device according to an embodiment of this disclosure. [Figure 5] This figure shows an example of a sequence diagram between a base station device and a terminal device according to an embodiment of this disclosure. [Figure 6] This figure illustrates an example of a scheduling method according to the embodiments of this disclosure. [Figure 7] This figure illustrates an example of a scheduling method according to the embodiments of this disclosure. [Figure 8] This is a diagram illustrating an example of a DMRS configuration according to the embodiments of this disclosure. [Figure 9] This figure illustrates another example of a DMRS configuration according to the embodiments of this disclosure. [Figure 10]A diagram for explaining another example of the scheduling method according to an embodiment of the present disclosure. [Figure 11] A diagram for explaining another example of the scheduling method according to an embodiment of the present disclosure. [Figure 12] A diagram for explaining an example of the scheduling method in the case of a multi-slot according to an embodiment of the present disclosure. [Figure 13] A diagram for explaining an example of the scheduling method in the case of a multi-slot according to an embodiment of the present disclosure. [Figure 14] A diagram for explaining an example of the scheduling method in the case of a multi-carrier according to an embodiment of the present disclosure. [Figure 15] A diagram for explaining another example of the scheduling method in the case of a multi-carrier according to an embodiment of the present disclosure. [Figure 16] A diagram for explaining another example of the scheduling method in the case of a multi-carrier according to an embodiment of the present disclosure. <L [Figure 17] A diagram for explaining an example of the scheduling method in the case of TDD according to an embodiment of the present disclosure. [Figure 18] A diagram for explaining an example of the scheduling method by dual DCI according to an embodiment of the present disclosure. [Figure 19] A diagram for explaining an example of the scheduling method in which dual DCI according to an embodiment of the present disclosure is applied to a multi-slot. [Figure 20] A diagram for explaining an example of the scheduling method in which dual DCI according to an embodiment of the present disclosure is applied to a multi-carrier. [Figure 21] A diagram for explaining another example of the scheduling method in which dual DCI according to an embodiment of the present disclosure is applied to a multi-carrier. [Figure 22] A diagram for explaining an example of the multi-scheduling method according to an embodiment of the present disclosure.

MODE FOR CARRYING OUT THE INVENTION

[0012] Embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings. In the present specification and the drawings, components having substantially the same functional configuration are denoted by the same reference numerals, and redundant descriptions are omitted.

[0013] Also, in the present specification and the drawings, similar components of the embodiments may be distinguished by attaching different letters or numbers after the same reference numeral. However, when it is not necessary to particularly distinguish each of the similar components, only the same reference numeral is attached.

[0014] One or more of the embodiments (including examples and variations) described below can each be implemented independently. On the other hand, at least a part of the plurality of embodiments described below may be implemented in appropriate combination with at least a part of other embodiments. These plurality of embodiments may include different novel features from each other. Therefore, these plurality of embodiments can contribute to solving different purposes or problems from each other and can exhibit different effects from each other. <00,00106>

[0015] <<1. Introduction>> <1.1. PDSCH / PUSCH mapping type> First, the conventional PDSCH / PUSCH mapping types will be described. In both PDSCH and PUSCH, two different mapping types (mapping methods) called type A and type B are defined. These types are defined by the DMRS type (PDSCH DMRS type and PUSCH DMRS type) and the SLIV tables shown in Table 1 and Table 2. The SLIV tables shown in Table 1 and Table 2 are described in TS38.214. [[ID=,20]]<00,00111>

[0016]

Table 1

[0017]

Table 2

[0018] The SLIV table is used to map a PDSCH or PUSCH to a time resource in a given slot (a time-domain resource consisting of 14 OFDM symbols). S is information indicating the starting symbol in the given slot. For example, S=0 indicates the first symbol in the slot. L is the symbol length (time length) of the PDSCH or PUSCH mapped to the resource. For example, L=4 indicates a PDSCH or PUSCH with 4 symbols.

[0019] Mapping type A is suitable for use cases involving high-speed and high-capacity communication, such as eMBB. Mapping type B is suitable for use cases involving low-latency and high-reliability communication, such as URLLC.

[0020] [PDSCH] The following section provides details about PDSCH mapping types.

[0021] (Type A) The PDSCH DMRS is of type A. The position of the DMRS is fixed at either the 3rd (pos2) or 4th (pos3) position. That is, the DMRS symbol maps to symbol 2 or 3 regardless of the start and length of the PDSCH.

[0022] The start symbol for PDSCH can be any symbol from 0 to 3. The symbol length for PDSCH is set to 3 to 14 in the case of a normal CP, and to 3 to 12 in the case of an extended CP.

[0023] (Type B) The PDSCH DMRS is of type B. The position of the DMRS is fixed to the first symbol of the assigned PDSCH. That is, the DMRS symbol is mapped to the first PDSCH symbol, regardless of the start of the PDSCH.

[0024] The start symbol for PDSCH is one of symbols from 3 to 14 in the case of a standard CP. In the case of an extended CP, the start symbol for PDSCH is one of symbols from 0 to 10.

[0025] The symbol length of PDSCH is set to one of 2, 4, or 7 in the case of a normal CP, and one of 2, 4, or 6 in the case of an extended CP.

[0026] [PUSCH] The following section provides details about the PUSCH mapping types.

[0027] (Type A) The PUSCH DMRS is of type A. The DMRS position is fixed at the 3rd (pos2) or 4th (pos3) position. The start symbol for PUSCH is always 0.

[0028] The symbol length of PUSCH is normally set to 4-14 for CP and 4-12 for extended CP.

[0029] (Type B) The PUSCH DMRS is of type B. The position of the DMRS is fixed to the first symbol of the assigned PUSCH.

[0030] The start symbol for PUSCH is one of the symbols 0 through 13 in the case of a standard CP. In the case of an extended CP, the start symbol for PDSCH is one of the symbols 0 through 12.

[0031] The symbol length of PUSCH is normally set to 1-14 for CP and 1-12 for extended CP.

[0032] <1.2. Challenges> Broadband transmission, improved frequency utilization efficiency, and reduced reliability and transmission delay are all requirements for different purposes. Therefore, there are trade-offs between them in some respects.

[0033] Furthermore, even in use cases where high-speed, high-capacity communication and high-quality, low-latency communication overlap, the emphasis may be placed on one of these aspects depending on the specific use case.

[0034] Previous communication methods did not take such use cases into consideration and did not support efficient data transmission that could support both high-speed, high-capacity communication and high-quality, low-latency communication.

[0035] In particular, until now, one control information (DCI, PDCCH) scheduled one transmission data (PDSCH, PUSCH). URLLC transmission assumes that the data size (payload size) of the transmission data is small. Therefore, there were no particular problems with the conventional technology that scheduled one transmission data with one control information.

[0036] However, when URLLC transmission requires even higher speed and larger capacity communication, the size of the transmitted data increases. In this case, if the duration of a single transmitted data is shortened to achieve low-latency transmission, that is, if large data is divided into multiple transmissions, the overhead related to control information increases. Thus, improving frequency utilization efficiency becomes a challenge when achieving high-speed, large-capacity communication in URLLC transmission.

[0037] <1.3. Overview of the proposed technology> Therefore, in the proposed technology of this disclosure, a terminal device receives one PDCCH transmitted from a base station. One PDCCH schedules one or more carriers or multiple physical shared channels in one or more slots. The one PDCCH and the multiple physical shared channels scheduled by that one PDCCH are transmitted to one terminal device. The multiple physical shared channels include multiple PDSCHs or multiple PUSCHs.

[0038] Furthermore, of the communication parameters applied to multiple physical shared channels scheduled by the aforementioned single PDCCH, some communication parameters are applied in common to all physical shared channels. The remaining communication parameters are applied individually to each of the multiple physical shared channels.

[0039] Thus, in the proposed technology of this disclosure, the base station equipment schedules one or more carriers or multiple physical shared channels in one or more slots using one PDCCH. This allows the base station equipment to reduce the overhead related to control information even when large data transmission data is divided into multiple parts for transmission. In other words, when realizing high-speed, high-capacity communication in URLLC transmission, the base station equipment can further improve frequency utilization efficiency.

[0040] <<2. Communication System Configuration>> <2.1. Overall Configuration of the Communication System> Figure 1 is a diagram showing an example of the overall configuration of a communication system 1 according to an embodiment of this disclosure. As shown in Figure 1, the communication system 1 includes a plurality of base station devices 20 (20A and 20B), a plurality of terminal devices 40 (40A and 40B), a core network 120, and a PDN (Packet Data Network) 130. The number of each device is not limited to this; for example, there may be one base station device 20 and one terminal device 40.

[0041] The base station device 20 is a communication device that operates a cell 110 and provides wireless communication services to one or more terminal devices 40 located within the coverage of the cell 110. The cell 110 operates according to any wireless communication method, such as LTE or NR. The base station device 20 is connected to a core network 120. The core network 120 is connected to a packet data network (PDN) 130 via a gateway device (not shown). The base station device 20 may consist of a collection of multiple physical or logical devices. For example, in embodiments of this disclosure, the base station device 20 may be distinguished into multiple devices of BBU (Baseband Unit) and RU (Radio Unit), and may be interpreted as a collection of these multiple devices. Furthermore or alternatively, in embodiments of this disclosure, the base station device 20 may be either or both of the BBU and RU. The BBU and RU may be connected by a predetermined interface (e.g., eCPRI). Furthermore or alternatively, the RU may be referred to as a Remote Radio Unit (RRU) or Radio DoT (RD). Furthermore, or alternatively, the RU may correspond to the gNB-DU described later. Furthermore, or alternatively, the BBU may correspond to the gNB-CU described later. Alternatively, a part of the BBU may correspond to the gNB-DU described later, and the remainder may correspond to the GNB-CU described later. Furthermore, or alternatively, the RU may be a device formed integrally with the antenna. The antenna of the base station device 20 (for example, an antenna formed integrally with the RU) may employ an Advanced Antenna System and support MIMO (for example, FD-MIMO) and beamforming. The Advanced Antenna System may include, for example, 64 transmitting antenna ports and 64 receiving antenna ports in the antenna of the base station device 20 (for example, an antenna formed integrally with the RU).

[0042] Furthermore, multiple base station devices 20 may be connected to each other. One or more base station devices 20 may be included in a Radio Access Network (RAN). That is, base station devices 20 may simply be referred to as RAN, RAN node, AN (Access Network), or AN node. In LTE, the RAN is called EUTRAN (Enhanced Universal Terrestrial RAN). In NR, the RAN is called NGRAN. In W-CDMA® (UMTS), the RAN is called UTRAN. In LTE, the base station device 20 is referred to as eNodeB (Evolved Node B) or eNB. That is, EUTRAN includes one or more eNodeBs (eNBs). Also, in NR, the base station device 20 is referred to as gNodeB or gNB. That is, NGRAN includes one or more gNBs. Furthermore, EUTRAN may include gNBs (en-gNBs) connected to the core network (EPC) in the LTE communication system (EPS). Similarly, NGRAN may include ng-eNB connected to the core network 5GC in a 5G communication system (5GS). Furthermore, or alternatively, if the base station equipment 20 is an eNB, gNB, etc., it may be referred to as 3GPP Access. Furthermore, or alternatively, if the base station equipment 20 is an Access Point, it may be referred to as Non-3GPP Access. Furthermore, or alternatively, the base station equipment 20 may be an optical extension device called an RRH (Remote Radio Head). Furthermore, or alternatively, if the base station equipment 20 is a gNB, the base station equipment 20 may be referred to as a combination of the gNB CU (Central Unit) and gNB DU (Distributed Unit) described above, or either of these. The gNB CU (Central Unit) hosts multiple upper layers (e.g., RRC, SDAP, PDCP) of the Access Stratum for communication with the UE. On the other hand, the gNB-DU hosts multiple lower layers (e.g., RLC, MAC, PHY) of the Access Stratum.In other words, among the messages and information described later, RRC signalling (e.g., MIB, various SIBs including SIB1, RRCSetup message, RRCReconfiguration message) may be generated by the gNB CU, while DCI and various Physical Channels (e.g., PDCCH, PBCH) described later may be generated by the gNB-DU. Alternatively, among the RRC signalling, some configurations, such as IE:cellGroupConfig, may be generated by the gNB-DU, and the remaining configurations may be generated by the gNB-CU. These configurations may be transmitted and received via the F1 interface described later. The base station device 20 may be configured to communicate with other base station devices 20. For example, if multiple base station devices 20 are eNBs or a combination of eNB and en-gNB, the base station devices 20 may be connected via the X2 interface. Furthermore, or alternatively, if multiple base station devices 20 are gNBs or a combination of gn-eNB and gNB, the devices may be connected via the Xn interface. Furthermore, or alternatively, if the multiple base station devices 20 are a combination of gNB CU (Central Unit) and gNB DU (Distributed Unit), the devices may be connected to each other via the F1 interface described above. The messages and information described later (RRC signalling or DCI information, Physical Channel) may be communicated between the multiple base station devices 20 (for example, via the X2, Xn, and F1 interfaces).

[0043] Furthermore, as mentioned above, the base station device 20 may be configured to manage multiple cells 110. The cells 110 provided by the base station device 20 are called Serving cells. A Serving cell includes PCells (Primary Cells) and SCells (Secondary Cells). When Dual Connectivity (e.g., EUTRA-EUTRA Dual Connectivity, EUTRA-NR Dual Connectivity (ENDC), EUTRA-NR Dual Connectivity with 5GC, NR-EUTRA Dual Connectivity (NEDC), NR-NR Dual Connectivity) is provided to a UE (e.g., terminal device 40), the PCells and zero or more SCell(s) provided by the MN (Master Node) are called a Master Cell Group. Furthermore, a Serving cell may also include PSCells (Primary Secondary Cells or Primary SCG Cells). That is, when Dual Connectivity is provided to a UE, the PSCells and zero or more SCell(s) provided by the SN (Secondary Node) are called a Secondary Cell Group (SCG). Unless otherwise specified (e.g., PUCCH on SCell), the Physical Uplink Control Channel (PUCCH) is transmitted by PCell and PSCell, but not by SCell. Similarly, Radio Link Failure is detected by PCell and PSCell, but not by SCell (and does not need to be detected). Because PCell and PSCell have special roles within the Serving Cell(s), they are also called Special Cells (SpCell). A single cell 110 may be associated with one Downlink Component Carrier and one Uplink Component Carrier. Furthermore, the system bandwidth corresponding to a single cell 110 may be divided into multiple Bandwidth Parts.In this case, one or more Bandwidth Parts (BWPs) may be configured for the UE, and one Bandwidth Part may be used by the UE as the Active BWP. Furthermore, the radio resources (e.g., frequency band, numerology (subcarrier spacing), slot format) available to the terminal device 40 may differ for each cell 110, each component carrier, or each BWP.

[0044] If the core network 120 is the NR core network (5G Core (5GC)), the core network 120 may include AMF (Access and Mobility Management Function), SMF (Session Management Function), UPF (User Plane Function), PCF (Policy Control Function), and UDM (Unified Data Management).

[0045] If the core network 120 is an LTE core network (Evolved Packet Core (EPC)), the core network 120 may include an MME (Mobility Management Entity), S-GW (Serving Gateway), P-GW (PDN Gateway), PCRF (Policy and Charging Rule Function), and HSS (Home Subscriber Server). The AMF and MME are control nodes that handle control plane signals and manage the mobility of the terminal device 40. The UPF and S-GW / P-GW are nodes that handle user plane signals. The PCF / PCRF are control nodes that perform policies and billing control, such as QoS (Quality of Service), for PDU sessions or bearers. The UDM / HSS are control nodes that handle subscriber data and perform service control.

[0046] Terminal device 40 is a communication device that communicates wirelessly with base station device 20 based on control by base station device 20. Terminal device 40 may be, for example, a sensor or camera device with communication capabilities, a mobile phone, a smart device (smartphone or tablet), a PDA (Personal Digital Assistant), or a personal computer. Terminal device 40 may also be a head-mounted display or VR goggles, etc., that have the function of sending and receiving data wirelessly.

[0047] For example, terminal device 40 communicates wirelessly with other terminal devices 40 based on control by base station device 20, or autonomously. In this case, terminal device 40 transmits a sidelink signal to other terminal devices 40 and receives a sidelink signal from other terminal devices 40 over the PC5 link. Hereinafter, the transmission and reception of sidelink signals by terminal device 40 will be collectively referred to as sidelink communication. When performing sidelink communication, terminal device 40 may use automatic retransmission technology such as HARQ (Hybrid Automatic Repeat reQuest).

[0048] Terminal device 40 may be capable of NOMA (Non Orthogonal Multiple Access) communication with base station device 20. Terminal device 40 may also be capable of NOMA communication in communication with other terminal devices 40 (sidelink). Furthermore, terminal device 40 may be capable of LPWA (Low Power Wide Area) communication with other communication devices (for example, base station device 20 and other terminal devices 40). In addition, the wireless communication used by terminal device 40 may be millimeter-wave wireless communication. The wireless communication used by terminal device 40 (including sidelink communication) may be radio wave wireless communication, or infrared or visible light wireless communication (optical wireless).

[0049] The base station devices 20 can send and receive information from each other using the inter-base station interface. If the core network is 5GC, the inter-base station interface may be an Xn interface. If the core network is EPC, the inter-base station interface may be an X2 interface.

[0050] Although not shown in Figure 1, communication devices that provide wireless communication services other than cellular communication, such as Wi-Fi® or MultiFire®, operated by other RATs, may exist around the communication system 1. Such communication devices are typically connected to the PDN130.

[0051] <2.2. Base Station Equipment Configuration> Figure 2 shows an example configuration of a base station device 20 according to the embodiment of this disclosure. The base station device 20 is a communication device (wireless system) that communicates wirelessly with a terminal device 40. The base station device 20 is a type of information processing device.

[0052] The base station device 20 comprises a signal processing unit 21, a storage unit 22, a network communication unit 23, and a control unit 24. Note that the configuration shown in Figure 2 is a functional configuration, and the hardware configuration may differ. Furthermore, the functions of the base station device 20 may be distributed and implemented across multiple physically separated devices.

[0053] The signal processing unit 21 is a wireless communication interface that communicates wirelessly with other communication devices (e.g., terminal device 40 and other base station devices 20). The signal processing unit 21 is a wireless transceiver that operates according to the control of the control unit 24. The signal processing unit 21 may support multiple wireless access methods. For example, the signal processing unit 21 may support both NR and LTE. The signal processing unit 21 may also support other cellular communication methods such as W-CDMA and cdma2000. In addition to cellular communication methods, the signal processing unit 21 may also support wireless LAN communication methods. Of course, the signal processing unit 21 may support only one wireless access method.

[0054] The signal processing unit 21 comprises a receiving unit 211, a transmitting unit 212, and an antenna 413. The signal processing unit 21 may have multiple receiving unit 211s, transmitting unit 212s, and antennas 413. If the signal processing unit 21 supports multiple wireless access methods, each part of the signal processing unit 21 may be configured separately for each wireless access method. For example, if the base station device 20 supports NR and LTE, the receiving unit 211 and the transmitting unit 212 may be configured separately for NR and LTE.

[0055] The receiving processing unit 211 processes the uplink signal received via the antenna 413. The receiving processing unit 211 comprises a wireless receiving unit 211a, a multiplexing / decoupling unit 211b, a demodulation unit 211c, and a decoding unit 211d.

[0056] The wireless receiver 211a performs down-conversion, removal of unwanted frequency components, amplification level control, quadrature demodulation, conversion to a digital signal, removal of guard intervals, and extraction of frequency domain signals by fast Fourier transform on the uplink signal. For example, suppose the wireless access method of the base station device 20 is a cellular communication method such as LTE. In this case, the multiplexing / decoupling unit 211b separates the uplink channel and uplink reference signal, such as PUSCH (Physical Uplink Shared Channel) and PUCCH (Physical Uplink Control Channel), from the signal output from the wireless receiver 211a. The demodulation unit 211c demodulates the received signal using a modulation scheme such as BPSK (Binary Phase Shift Keying) or QPSK (Quadrature Phase Shift Keying) for the modulation symbols of the uplink channel. The modulation scheme used by the demodulation unit 211c may be a multi-level QAM such as 16QAM (Quadrature Amplitude Modulation), 64QAM, or 256QAM. The decoding unit 211d performs decoding on the encoded bits of the demodulated uplink channel. The decoded uplink data and uplink control information are output to the control unit 24.

[0057] The transmission processing unit 212 performs the transmission processing of downlink control information and downlink data. The transmission processing unit 212 comprises an encoding unit 212a, a modulation unit 212b, a multiplexing unit 212c, and a wireless transmission unit 212d.

[0058] The encoding unit 212a encodes the downlink control information and downlink data input from the control unit 24 using encoding methods such as block encoding, convolutional encoding, and turbo encoding. The modulation unit 212b modulates the encoded bits output from the encoding unit 212a using predetermined modulation methods such as BPSK, QPSK, 16QAM, 64QAM, and 256QAM. The multiplexing unit 212c multiplexes the modulation symbols and downlink reference signals for each channel and places them in predetermined resource elements. The wireless transmission unit 212d performs various signal processing on the signals from the multiplexing unit 212c. For example, the wireless transmission unit 212d performs processing such as time-domain conversion using the Fast Fourier Transform, addition of guard intervals, generation of baseband digital signals, conversion to analog signals, quadrature modulation, upconversion, removal of extraneous frequency components, and power amplification. The signals generated by the transmission processing unit 212 are transmitted from the antenna 413.

[0059] The memory unit 22 is a data read / write storage device such as DRAM, SRAM, flash memory, or hard disk. The memory unit 22 functions as a storage means for the base station device 20.

[0060] The network communication unit 23 is a communication interface for communicating with other devices (for example, other base station devices 20). For example, the network communication unit 23 is a LAN (Local Area Network) interface such as a NIC (Network Interface Card). The network communication unit 23 may also be a USB interface consisting of a USB (Universal Serial Bus) host controller, a USB port, etc. Furthermore, the network communication unit 23 may be a wired interface or a wireless interface. The network communication unit 23 functions as a network communication means for the base station device 20. The network communication unit 23 communicates with other devices according to the control of the control unit 24.

[0061] The control unit 24 is a controller that controls various parts of the base station device 20. The control unit 24 is a hardware processor that controls various parts of the base station device 20. The control unit 24 is implemented by a processor such as a CPU (Central Processing Unit) or an MPU (Micro Processing Unit). For example, the control unit 24 is implemented by the processor executing various programs stored in the memory device inside the base station device 20 using RAM (Random Access Memory) or the like as a working area. The control unit 24 may also be implemented by an integrated circuit such as an ASIC (Application Specific Integrated Circuit) or an FPGA (Field Programmable Gate Array). CPUs, MPUs, ASICs, and FPGAs can all be considered controllers.

[0062] <2.3. Terminal Device Configuration> Figure 3 shows an example configuration of a terminal device 40 according to the embodiment of this disclosure. The terminal device 40 is a communication device (wireless system) that communicates wirelessly with the base station device 20. The terminal device 40 is a type of information processing device.

[0063] The terminal device 40 comprises a signal processing unit 41, a storage unit 42, an input / output unit 44, and a control unit 45. Note that the configuration shown in Figure 3 is a functional configuration, and the hardware configuration may differ. Furthermore, the functions of the terminal device 40 may be implemented in a distributed manner across multiple physically separated configurations.

[0064] The signal processing unit 41 is a wireless communication interface that communicates wirelessly with other communication devices (e.g., the base station device 20 and other terminal devices 40). The signal processing unit 41 is a wireless transceiver that operates according to the control of the control unit 45. The signal processing unit 41 supports one or more wireless access schemes. For example, the signal processing unit 41 supports both NR and LTE. The signal processing unit 41 may also support other wireless access schemes such as W-CDMA and cdma2000.

[0065] The signal processing unit 41 comprises a receiving processing unit 411, a transmitting processing unit 412, and an antenna 313. The signal processing unit 41 may have multiple receiving processing units 411, transmitting processing units 412, and antennas 313. If the signal processing unit 41 supports multiple wireless access methods, each part of the signal processing unit 41 may be configured separately for each wireless access method. For example, the receiving processing unit 411 and the transmitting processing unit 412 may be configured separately for LTE and NR. The configuration of the receiving processing unit 411 and the transmitting processing unit 412 is the same as that of the receiving processing unit 211 and the transmitting processing unit 212 of the base station device 20.

[0066] The memory unit 42 is a data read / write storage device such as DRAM, SRAM, flash memory, or hard disk. The memory unit 42 functions as a storage means for the terminal device 40.

[0067] The input / output unit 44 is a user interface for exchanging information with the user. For example, the input / output unit 44 is an operating device for the user to perform various operations, such as a keyboard, mouse, operation keys, or touch panel. Alternatively, the input / output unit 44 is a display device such as a liquid crystal display or an organic electroluminescence display. The input / output unit 44 may also be an audio device such as a speaker or buzzer. Furthermore, the input / output unit 44 may also be a lighting device such as an LED (light-emitting diode) lamp. The input / output unit 44 functions as an input / output means (input means, output means, operation means, or notification means) of the terminal device 40.

[0068] The control unit 45 is a controller that controls each part of the terminal device 40. The control unit 24 is a hardware processor that controls each part of the terminal device 40. The control unit 45 is implemented by a processor such as a CPU or MPU. For example, the control unit 45 is implemented by the processor executing various programs stored in the memory device inside the terminal device 40 using RAM or the like as a working area. The control unit 45 may also be implemented by an integrated circuit such as an ASIC or FPGA. A CPU, MPU, ASIC, and FPGA can all be considered as controllers.

[0069] <<3. Technical Features>> <3.1. Scheduling Method> Next, an example of a PDSCH / PUSCH scheduling method implemented in the communication system 1 according to the embodiment of this disclosure will be described. Figures 4 and 5 show an example of a sequence diagram between the base station device 20 and the terminal device 40 according to the embodiment of this disclosure.

[0070] Figure 4 shows a case where the base station device 20 schedules multiple PDSCHs using one PDCCH.

[0071] When the base station device 20 schedules a PDSCH for the terminal device 40, the base station device 20 transmits a PDCCH including DCI (downlink control information) to the terminal device 40 that is the target of the scheduling.

[0072] The terminal device 40 sequentially demodulates and decodes a predetermined number of PDCCH candidates from a time-frequency resource called CORESET (control resource set), which has been set in advance by RRC signaling (e.g., transmission of RRCReconfiguration message, RRCSetup message, etc.), in a predetermined manner, and detects the PDCCH addressed to itself (blind detection).

[0073] The terminal device 40 recognizes whether a PDCCH is addressed to itself based on a parameter called RNTI (Radio Network Temporary Identifier). When the terminal device 40 detects a PDCCH addressed to itself, it performs reception processing on a PDSCH scheduled based on the DCI included in that PDCCH.

[0074] In Figure 4, the base station device 20 schedules six PDSCH#0 to #6 using one PDCCH. When the terminal device 40 detects a PDCCH addressed to itself, it then performs reception processing using PDSCH#0 to #6.

[0075] Figure 5 shows a case where the base station device 20 schedules multiple PUSCHs using one PDCCH.

[0076] In the same manner as in Figure 4, the terminal device 40 detects a PDCCH addressed to itself. Upon detecting a PDCCH addressed to itself, the terminal device 40 performs transmission processing using a PUSCH scheduled based on the DCI contained in that PDCCH.

[0077] In Figure 5, the base station device 20 schedules six PUSCH#0 to #4 using one PDCCH. When the terminal device 40 detects a PDCCH addressed to itself, it then performs transmission processing using PUSCH#0 to #4.

[0078] Thus, the communication method according to the embodiments of this disclosure is a method for scheduling PDSCH and / or PUSCH in one or more carriers and / or slots on one PDCCH (or one DCI).

[0079] In the communication method according to the embodiments of this disclosure, when one PDCCH schedules multiple PDSCHs and / or PUSCHs, the transmission parameters (receive parameters) of the multiple PDSCHs and / or PUSCHs may be partially common. Alternatively, the transmission parameters (receive parameters) of the multiple PDSCHs and / or PUSCHs may be individually notified. Whether the transmission parameters (receive parameters) are partially common or individually notified may be predetermined. Alternatively, whether the transmission parameters (receive parameters) are partially common or individually notified may be set specifically for cell 110 or specifically for terminal device 40 through RRC signaling or the like. Hereinafter, unless otherwise distinguished, transmission parameters and receive parameters will be referred to as communication parameters or transmission parameters.

[0080] <3.2. Transmission Parameters> As described above, the PDSCH / PUSCH transmission parameters can be transmitted from the base station device 20 to the terminal device 40 by RRC signaling (e.g., by including them in an RRCReconfiguration message, RRCSetup message, etc.). Alternatively, the PDSCH / PUSCH transmission parameters may be transmitted from the base station device 20 to the terminal device 40 by PDCCH (e.g., DCI), or by a combination of RRC signaling and PDCCH. Hereinafter, the PDSCH / PUSCH transmission parameters according to the embodiment of this disclosure are as follows. That is, the PDSCH / PUSCH transmission parameters according to the embodiment of this disclosure may include at least one of the following multiple parameters.

[0081] [Parameters related to resource mapping in the time domain] The PDSCH / PUSCH transmission parameters may include the following parameters as time-domain resource mapping parameters: • Number of symbols (duration) for PDSCH / PUSCH • Starting position End position • Information indicating the slots • Number of PDSCH / PUSCH units

[0082] The parameter indicating the start position includes, for example, information indicating the first symbol number and / or slot number of the PDSCH / PUSCH. The parameter indicating the end position includes, for example, information indicating the last symbol number and / or slot number of the PDSCH / PUSCH.

[0083] The information indicating a slot includes a slot number (or symbol number) specific to cell 110, or offset information relative to the slot (or symbol) to which PDCCH is mapped.

[0084] The information indicating the number of PDSCH / PUSCH units includes, for example, information indicating the number of PDSCH / PUSCH units to be scheduled consecutively in the time direction. This reduces the overhead of control information by notifying the number of PDSCH / PUSCH units, especially when parameters such as the number of symbols of the scheduled PDSCH / PUSCH units are common.

[0085] [Parameters related to resource mapping in the frequency domain] The PDSCH / PUSCH transmission parameters may include the following parameters as parameters related to frequency domain resource mapping: • Number of PDSCH / PUSCH resource blocks (frequency bandwidth) • Starting position End position • Information indicating whether or not frequency hopping will occur (frequency hopping flag) • Information indicating the BWP (Bandwidth part) and / or component carrier (cell).

[0086] The parameter indicating the start position includes, for example, information indicating the first resource block number and / or subcarrier number of the PDSCH / PUSCH. The parameter indicating the end position includes, for example, information indicating the last resource block number and / or subcarrier number of the PDSCH / PUSCH.

[0087] [Parameters related to MIMO (multi-input multi-output), etc.] The PDSCH / PUSCH transmission parameters may include the following parameters as MIMO, pre-coating, and / or beam-related parameters: • Parameters related to transmission mode • Parameters indicating the number of MIMO layers (number of ranks, number of spatial multiplexings) • Parameters showing the matrix used for pre-coating • A parameter indicating the antenna port used for transmission. • Parameters related to QCL (Quasi Co-Location)

[0088] Parameters related to the transmission mode include, for example, information about codebook-based or non-codebook-based transmission modes. Parameters indicating the antenna port used for transmission are also used to identify the corresponding demodulation reference signal (DMRS). Parameters related to QCL are used to indicate whether the given propagation path characteristics are the same.

[0089] [Parameters related to retransmission control] The transmission parameters for PDSCH / PUSCH may include the following parameters as parameters related to HARQ (hybrid automatic repeat request) control (retransmission control): • HARQ process number • New data indicator • Redundancy version

[0090] The HARQ process number is an identifier that manages the retransmission control process for data (codewords, transport blocks). The New data indicator indicates whether the data corresponding to the HARQ process number is a first transmission or a retransmission. The Redundancy version indicates the encoded bits transmitted in the data corresponding to the HARQ process number.

[0091] [Other parameters] In addition to the parameters mentioned above, the PDSCH / PUSCH transmission parameters may include the following parameters: • Parameters related to modulation scheme and / or coding rate • Parameters related to scramble codes used in PDSCH / PUSCH • Parameters related to transmit power control for PDSCH / PUSCH • A parameter indicating whether the scheduled data is PDSCH or PUSCH. • Especially when transmitting and receiving on unlicensed frequencies or shared frequencies, parameters related to the channel access method. • Parameters related to priority • Information indicating the PDSCH / PUSCH mapping type • Information indicating PDSCH or PUSCH

[0092] The information indicating the PDSCH / PUSCH mapping type includes types A, B, or C. That is, one PDCCH can schedule multiple PDSCH / PUSCHs with different mapping types.

[0093] The information indicating PDSCH or PUSCH is necessary when a single PDCCH, as described later, schedules both PDSCH and PUSCH. Note that PSSCH may be included in addition to, or by replacing either PDSCH or PUSCH.

[0094] The transmission parameters described above are examples only and are not limited to them. PDSCH / PUSCH transmission parameters can include a variety of information.

[0095] <3.3. Mapping Types> As mentioned above, conventional scheduling methods define two different mapping types for PDSCH / PUSCH, called Type A and Type B.

[0096] In the scheduling method according to the embodiments of this disclosure, in addition to the above-described types A and B, a new PDSCH / PUSCH mapping type C (hereinafter also referred to as type C) may be defined. Type C is a suitable type for use cases of eMBB and URLLC. For example, the possible values ​​of SLIV in type C may include all the possible values ​​of SLIV in types A and B. Also, for example, if scheduling can be performed across multiple slots in the scheduling method according to the embodiments of this disclosure, the possible values ​​of S in SLIV in type C may be 14 or more.

[0097] A terminal device 40 that supports transmission or reception of PDSCH / PUSCH mapping type C may also be configured to support transmission or reception of PDSCH / PUSCH mapping type B.

[0098] In the scheduling method according to the embodiments of this disclosure, if type C is not defined, the scheduling method may be applied to types A and B. Alternatively, the scheduling method may be applied to type B and not to type A. That is, the terminal device 40 supporting the scheduling method according to the embodiments of this disclosure shall support PDSCH / PUSCH mapping type B. In other words, the terminal device 40 supporting the scheduling method according to the embodiments of this disclosure shall support high reliability, low latency (URLLC) communication.

[0099] Furthermore, in the scheduling method according to the embodiments of this disclosure, a new DCI format (DCI format) used for scheduling may be defined. The DCI format is located within at least one slot (or symbol). The DCI format may include transmission parameters for scheduling one or more PDSCHs and / or PUSCHs.

[0100] The following describes some specific examples of scheduling methods according to the embodiments of this disclosure, some or all of these examples may be implemented in combination with each other.

[0101] <3.4. In the case of a single carrier and single slot> <3.4.1.PDSCH> This section describes an example in which one PDCCH schedules multiple PDSCHs within a predetermined slot (or symbol) in the case of a single carrier, single slot. Figures 6 and 7 illustrate an example of a scheduling method according to the embodiment of this disclosure. Although this example shows scheduling to a predetermined slot, the scheduling method according to the embodiment of this disclosure can also be applied to scheduling for any time length (e.g., a predetermined number of symbols, subframes, radio frames, etc.).

[0102] Figure 6 shows the case where the number of symbols (duration) of scheduled PDSCHs is the same in the single-carrier, single-slot scenario. In other words, in the example in Figure 6, some of the transmission parameters (in this case, the number of symbols) are common to multiple PDSCHs scheduled by a single PDCCH.

[0103] In Figure 6, PDCCH is included in a portion of PDSCH#0 during transmission. The number of symbols for the multiple PDSCH#0 to #6 scheduled by this PDCCH is "2", and they all have the same duration.

[0104] Figure 7 illustrates the case where, in a single-carrier, single-slot configuration, the number of symbols (duration) for each scheduled PDSCH is notified individually. In other words, in the example in Figure 7, for multiple PDSCHs scheduled by a single PDCCH, some of the transmission parameters (in this case, the number of symbols) are notified individually for each.

[0105] In Figure 7, PDCCH is included in a portion of PDSCH#0 when transmitted. The multiple PDSCH#0 to #3 scheduled by this PDCCH each have their own individually set number of symbols. For example, PDSCH#0 has 3 symbols, PDSCH#1 has 4 symbols, PDSCH#2 has 2 symbols, and PDSCH#3 has 3 symbols. In this way, multiple PDSCH#0 to #3 may each have different symbol lengths.

[0106] Furthermore, whether some transmission parameters (e.g., the number of symbols) are common or individually notified can be predetermined. Alternatively, the base station device 20 may configure the parameters to be specific to cell 110 or specific to terminal device 40 through RRC signaling or the like.

[0107] The following describes specific examples of transmission parameters in multiple PDSCHs scheduled by a single PDCCH. At least one of the following transmission parameters can be transmitted from the base station device 20 to the terminal device 40 via RRC signaling (e.g., by including it in an RRCReconfiguration message, RRCSetup message, etc.), PDCCH (e.g., DCI), or a combination thereof. Note that the scheduling method according to the embodiments of this disclosure only needs to include at least one of the following specific examples of transmission parameters, and does not necessarily need to include all of them.

[0108] [Number of symbols] The number of symbols (duration) of multiple scheduled PDSCHs are the same.

[0109] As a result, even when scheduling multiple PDSCHs, the base station device 20 does not need to individually notify the symbol length of each PDSCH, thereby further reducing the overhead of control information.

[0110] The base station device 20 may notify a single value as the common number of symbols. The base station device 20 may notify the number of symbols using DCI. Alternatively, the base station device 20 may pre-set the number of symbols using RRC signaling or the like.

[0111] The base station device 20 may also individually notify the number of PDSCHs scheduled within a predetermined slot, the start symbol, or the frequency resources via PDCCH.

[0112] [Frequency Resources] The frequency resources (resource block numbers) of multiple scheduled PDSCHs are the same.

[0113] As a result, even when scheduling multiple PDSCHs, the base station device 20 does not need to individually notify the frequency resources of each PDSCH, thereby further reducing the overhead of control information.

[0114] The base station device 20 may notify a single value as a common frequency resource. The base station device 20 may notify the frequency resource using DCI. Alternatively, the base station device 20 may pre-set the frequency resource using RRC signaling or the like.

[0115] The frequency bandwidth (i.e., the number of resource blocks) of the frequency resources of the multiple scheduled PDSCHs is the same. On the other hand, the location of the mapped frequency resources (e.g., the start resource block number, the start subcarrier number) may be different for each of the multiple PDSCHs.

[0116] For example, the base station device 20 may perform frequency hopping for each PDSCH for the purpose of frequency diversity. In this case, the base station device 20 notifies the frequency resources of the first PDSCH. The terminal device 40 determines the frequency resources of subsequent PDSCHs based on a predetermined method. Alternatively, the terminal device 40 may determine the frequency resources of subsequent (second and later) PDSCHs in a manner set by RRC signaling.

[0117] [Start Symbol] The start symbols for multiple scheduled PDSCHs are notified in bitmap format.

[0118] For example, DCI notifies the system of 14 bits of bitmap information (hereinafter also referred to as bitmap information) corresponding to each of the 14 symbols in a single slot. For instance, a "1" in this bitmap information indicates the start symbol from which the PDSCH is scheduled. In other words, the number of "1s" contained in this bitmap information represents the number of PDSCHs that will be scheduled.

[0119] Specifically, if this bitmap information is "01000100100000", three PDSCHs will be scheduled with the 2nd, 6th, and 9th symbols in the slot as the starting symbols.

[0120] The number of symbols for the scheduled PDSCH may be notified (or set) separately from the bitmap information. In this case, the base station device 20 schedules the PDSCH so that multiple PDSCHs do not overlap, and generates information (bitmap information) indicating the start symbol based on that schedule.

[0121] If the terminal device 40 receives bitmap information in which multiple PDSCHs are scheduled in overlapping order, it recognizes that no such schedule exists. In this case, the terminal device 40 recognizes that multiple PDSCHs are scheduled according to a predetermined method.

[0122] For example, suppose that multiple PDSCHs have the same symbol count of "4," but the terminal device 40 receives bitmap information of "01000100100000." In this bitmap information, the second and third PDSCHs overlap at the ninth symbol. In this case, the terminal device 40 recognizes that no PDSCHs have been scheduled based on the bitmap information and performs reception processing using multiple PDSCHs scheduled according to a predetermined method.

[0123] [TDRA(Time Domain Resource Assignment) table] The start symbol and number of symbols for each of the multiple scheduled PDSCHs are communicated through a single TDRA table.

[0124] For example, the combination of start symbol and symbol count values ​​for each scheduled PDSCH is defined as a single TDRA table. The start symbol and symbol count for each PDSCH are specified by the Time Domain Resource Assignment value included in the DCI. The start symbol and symbol count values ​​for each PDSCH may be defined by default or set by RRC signaling.

[0125] As a concrete example, Table 3 shows the TDRA table when four PDSCHs are scheduled. The Time Domain Resource Assignment included in DCI corresponds to the row index. For each row index, a combination of the start symbol (S) and the number of symbols (L) for each PDSCH is defined.

[0126] [Table 3]

[0127] Furthermore, a K0 (offset between the PDCCH slot and the PDSCH slot) may be set for each PDSCH. This allows the base station device 20 to allocate multiple PDSCHs scheduled in a single DCI across slots.

[0128] Furthermore, the duration (duration, number of slots, number of symbols) for which a combination is valid as notified by DCI may be notified by DCI or RRC signaling.

[0129] Note that while Table 3 shows examples where multiple combinations are defined or set, only one combination may be defined or set. In that case, the base station device 20 does not need to notify the Row index in DCI. Furthermore, a Periodicity indicating a period (duration, number of slots, number of symbols) may also be defined or set and applied repeatedly for each period.

[0130] Furthermore, the S and L values ​​that can be set for each PDSCH can be the same as those for mapping type B.

[0131] [DMRS(DeModulation Reference Signal)] Multiple PDSCHs scheduled by a single PDCCH may be associated with a common DMRS.

[0132] Figure 8 is a diagram illustrating an example of the arrangement of a DMRS according to the present disclosure. In the example in Figure 8, the DMRS is included only in the first PDSCH (PDSCH#0) of the multiple PDSCHs scheduled by one PDCCH, and the subsequent PDSCHs (PDSCH#1 to #6) do not include the DMRS. In this case, the terminal device 40 performs demodulation using the DMRS included in the first PDSCH for the subsequent PDSCHs. In this case, it is preferable that all of the multiple PDSCHs have the same QCL.

[0133] Figure 9 is a diagram illustrating another example of a DMRS configuration according to the embodiment of this disclosure. Here, a PDSCH group, which includes at least one of several PDSCHs, is assigned as a group to which a common DMRS applies.

[0134] In the example in Figure 9, two PDSCH groups are set up: a first group containing PDSCH#0 to #3 and a second group containing PDSCH#4 to #6. The first PDSCH in each group (PDSCH#0 and PDSCH#4) contains DMRS, while the other PDSCHs do not.

[0135] In this case, for PDSCH#1 to #3, the terminal device 40 performs demodulation using the DMRS included in PDSCH#0, which is the first of the first group. Also, for PDSCH#5 and #6, the terminal device 40 performs demodulation using the DMRS included in PDSCH#4, which is the first of the second group.

[0136] The PDSCH group settings (number of PDSCHs in a group, number of groups), DMRS placement symbols, etc., may be set by RRC signaling or specified by DCI.

[0137] Different PDSCH groups may have different QCLs. Transmission Configuration Indicators (TCIs) corresponding to each PDSCH group may be notified individually. Furthermore, a common antenna port may be notified for each DMRS, or individual antenna ports may be notified.

[0138] Thus, by using a common DMRS among multiple PDSCHs, communication system 1 can reduce the overhead of the DMRS in the time domain.

[0139] <3.4.2.PUSCH> Here, we describe an example in which, in the case of a single carrier, single slot, one PDCCH schedules multiple PUSCHs within a predetermined slot (or symbol). Although this is an example of scheduling to a predetermined slot, the scheduling method according to the embodiment of this disclosure can also be applied to scheduling to any time length (e.g., a predetermined number of symbols, subframes, radio frames, etc.).

[0140] Figures 10 and 11 illustrate other examples of scheduling methods according to the embodiments of this disclosure.

[0141] Figure 10 shows the case where the number of symbols (duration) of scheduled PUSCHs are the same in the single-carrier, single-slot scenario. In other words, in the example in Figure 10, some of the transmission parameters (in this case, the number of symbols) are common to multiple PUSCHs scheduled by a single PDCCH.

[0142] In Figure 10, PDCCH is placed on the first and second symbols of the downlink BWP (Bandwidth Part). These PDCCHs schedule PUSCH#0 to #4 on the fifth through fourteenth symbols of the uplink BWP. Each of PUSCH#0 to #4 has two symbols and the same duration.

[0143] Figure 11 illustrates the case where, in a single-carrier, single-slot configuration, the number of symbols (duration) for each scheduled PUSCH is notified individually. In other words, in the example in Figure 11, for multiple PDSCHs scheduled by a single PDCCH, some of the transmission parameters (in this case, the number of symbols) are notified individually for each.

[0144] In Figure 11, PDCCH is placed on the first and second symbols of the downlink BWP (Bandwidth Part). This PDCCH schedules PUSCH#0 to #2 on the fifth through seventh and ninth through fourteenth symbols of the uplink BWP. For example, PDSCH#0 has 3 symbols, PDSCH#1 has 2 symbols, and PDSCH#2 has 4 symbols. Thus, multiple PDSCH#0 to #2 can each be assigned different symbol lengths.

[0145] Thus, multiple PUSCHs are scheduled using a single PDCCH, just like multiple PDSCHs. The specific examples of transmission parameters applied to multiple PDSCHs described above can also be applied to multiple PUSCHs.

[0146] <3.5. In the case of multiple slots> In the case of a multi-slot system, an example is described in which one PDCCH schedules multiple PDSCHs or PUSCHs within a predetermined number of slots.

[0147] Figure 12 is a diagram illustrating an example of a scheduling method in the case of a multi-slot according to the embodiment of this disclosure. Figure 12 shows a case in the multi-slot case where one PDCCH schedules multiple PDSCHs within a predetermined number of slots.

[0148] In Figure 12, the base station device 20 uses one PDCCH to schedule multiple PDSCHs (PDSCH#n_1~#n_6, #n+1_1~#n+1_6) within two slots (Slot#n, #n+1).

[0149] As mentioned above, in the case of a single slot, whether some of the transmission parameters are common or individually notified can be predetermined. Alternatively, whether some of the transmission parameters are common or individually notified can be set specifically for cell 110 or specific for terminal device 40 through RRC signaling or the like.

[0150] Similarly, in the case of multi-slot systems, whether some transmission parameters are common or individually notified can be predetermined or configured through RRC signaling or similar means.

[0151] Furthermore, in the case of a multi-slot system, transmission parameters can be communicated individually between slots. For example, in the example shown in Figure 12, frequency resources are communicated individually between slots. Therefore, while the PDSCH frequency resources are common within each slot, they differ between slots.

[0152] Figure 13 is a diagram illustrating an example of a scheduling method in the case of a multi-slot according to the embodiment of this disclosure. Figure 13 shows a case in the multi-slot case where one PDCCH schedules multiple PUSCHs within a predetermined number of slots.

[0153] In Figure 13, the base station equipment 20 uses one PDCCH to schedule multiple PUSCHs (PUSCH#n_1~#n_4, #n+1_1~#n+1_6) within two slots (Slot#n, #n+1) of the uplink BWP.

[0154] Furthermore, when scheduling multiple PUSCHs, similar to PDSCHs, whether some transmission parameters are common or whether they are notified individually can be predetermined or configured through RRC signaling, etc.

[0155] Furthermore, when scheduling multiple PUSCHs, similar to PDSCHs, transmission parameters can be communicated individually between slots. For example, in the example in Figure 13, frequency resources are communicated individually between slots. Therefore, while the frequency resources for PDSCHs are common within each slot, they differ between slots.

[0156] Thus, the communication system 1 according to the embodiment of this disclosure can determine at predetermined time intervals whether the transmission parameters of multiple PDSCHs (or PUSCHs) scheduled by one PDCCH are common.

[0157] The predetermined time length may be a predefined time length such as one or more OFDM symbols, a slot consisting of 14 OFDM symbols, a subframe (1 ms), a half frame (5 ms), or a system frame (10 ms). Alternatively, the predetermined time length may be set specifically for cell 110 or specifically for terminal device 40 through RRC signaling or the like.

[0158] <3.6. In the case of multiple carriers> As an example of multi-carrier operation, we will describe a case where carrier aggregation is configured on a terminal device 40, and one PDCCH schedules multiple PDSCHs or PUSCHs within a predetermined set of component carriers (cells, BWPs, arbitrary frequency domains). The following section will focus on the case where one PDCCH schedules multiple PDSCHs. The case where one PDCCH schedules multiple PUSCHs can be scheduled in the same way as a PDSCH, so the explanation will be omitted here.

[0159] Figure 14 is a diagram illustrating an example of a scheduling method in the case of multi-carrier transmission according to the embodiment of this disclosure. Figure 14 shows an example of multi-carrier transmission in which multiple BWPs are set on the terminal device 40.

[0160] In Figure 14, one PDCCH schedules all PDSCHs in two BWPs (downlink BWP#A, #B) within a given slot.

[0161] As mentioned above, in the case of a single slot, whether some of the transmission parameters are common or individually notified can be predetermined. Alternatively, whether some of the transmission parameters are common or individually notified can be set specifically for cell 110 or specific for terminal device 40 through RRC signaling or the like.

[0162] Similarly, in the case of multi-carrier transmissions, whether some transmission parameters are common or individually notified can be predetermined or configured through RRC signaling or other means.

[0163] Furthermore, in the case of multi-carrier transmissions, transmission parameters can be communicated individually (specifically) between BWPs. For example, in the example in Figure 14, the PDSCH's frequency domain resource mapping (e.g., frequency bandwidth) is communicated individually between BWPs. Therefore, while the PDSCH's frequency bandwidth is common within each BWP, it differs between BWPs.

[0164] As described above, in the example in Figure 14, the transmission parameters for the PDSCH's frequency domain resource mapping (e.g., frequency bandwidth) are individually notified or set among multiple BWPs. On the other hand, the transmission parameters for the PDSCH's time domain resource mapping (e.g., number of symbols) are commonly notified or set among multiple BWPs.

[0165] Thus, in the example shown in Figure 14, the communication system 1 can determine, for each predetermined frequency bandwidth, whether the transmission parameters of multiple PDSCHs (or PUSCHs) scheduled by a single PDCCH are common.

[0166] Examples of the predetermined frequency bandwidth include component carriers, BWPs, one or a predetermined resource block, and one or a predetermined number of subcarriers.

[0167] Furthermore, even if the PDSCH transmission parameters are notified individually for each BWP, the values ​​of the transmission parameters may be associated between the BWPs. This allows the communication system 1 to reduce the number of bits required for notifying the transmission parameters.

[0168] A concrete example is MCS. Even at different frequencies, the same level of SINR can be expected. Therefore, the base station device 20 notifies the MCS at BWP#1 as 5 bits of information, and notifies the MCS at BWP#2 as the difference from the MCS at BWP#1. This allows the base station device 20 to reduce the number of bits in the MCS from BWP#2 onwards.

[0169] Figure 15 illustrates another example of a scheduling method in the case of multi-carrier according to the embodiment of this disclosure. Figure 15 shows an example of multi-carrier transmission in which multiple BWPs are set on the terminal device 40.

[0170] Here, one PDCCH schedules one PDSCH for each of the two BWPs (downlink BWP#A, #B) within a given slot.

[0171] In the example shown in Figure 15, the base station device 20 transmits scheduling information for PDSCH#A_0 and PDSCH#B_0 via PDCCH#0. The base station device 20 also transmits scheduling information for PDSCH#A_1 and PDSCH#B_1 via PDCCH#1.

[0172] In the example in Figure 15, the number of symbols and the start symbol position of the scheduled PDSCH are common to both BWP#A and #B. For example, PDSCH#A_0 and PDSCH#B_0 scheduled by PDCCH#0 have the same number of symbols. Also, the start symbol positions of PDSCH#A_0 and PDSCH#B_0 are the same.

[0173] In this way, by making the number of symbols and the start symbol position of the scheduled PDSCH common between BWP#A and #B, the base station device 20 no longer needs to notify the terminal device 40 of the number of symbols and the start symbol position. As a result, the base station device 20 can further improve frequency utilization efficiency.

[0174] The number of symbols and the start symbol position of the PDSCH to be scheduled may be notified separately by BWP#A and #B, respectively. Figure 16 is a diagram illustrating another example of the scheduling method in the case of multi-carrier according to the embodiment of this disclosure. Figure 16 shows an example of multi-carrier transmission in which multiple BWPs are set on the terminal device 40.

[0175] In the example in Figure 16, the number of symbols and the start symbol position of the scheduled PDSCH are notified separately by BWP#A and #B, respectively. For example, the number of symbols for PDSCH#A_2 scheduled by PDCCH#2 is "4", and the number of symbols for PDSCH#B_2 is "2". Also, the start symbol position for PDSCH#A_2 scheduled by PDCCH#2 is the 8th position, and the start symbol position for PDSCH#B_2 is the 9th position.

[0176] In this case, the start symbol position of the PDSCH may be restricted to being at or after the start symbol position of the PDCCH that is scheduling the PDSCH. In other words, the terminal device 40 assumes that the start symbol position of the PDSCH is not scheduled before the start symbol position of the PDCCH that is scheduling the PDSCH.

[0177] Furthermore, the start symbol position of a PDSCH may be notified by information indicating its relative position (offset) to the position of a predetermined symbol (e.g., the start symbol position) of the PDCCH that is scheduling that PDSCH.

[0178] For example, position information indicating relative position consists of 2 bits. This position information indicates an offset value (e.g., one of symbols 0, 1, 2, or 3). The number of bits (e.g., 2 bits) and / or possible offset values ​​(e.g., symbols 0, 1, 2, or 3) can be set by RRC signaling or the like.

[0179] Although the above example described the case of a single slot, the same applies to the case of multiple slots; the communication system 1 can schedule multiple PDSCHs (PUSCHs) using one PDCCH in a multi-carrier environment.

[0180] <3.7. In the case of TDD (Time Division Duplex)> When one PDCCH schedules multiple PDSCHs or PUSCHs as described above, those PDSCHs or PUSCHs are further scheduled based on the slot format.

[0181] Here, the slot format can be set as either a downlink symbol, an uplink symbol, or a flexible symbol for each OFDM symbol. A flexible symbol is a symbol that can become a downlink symbol or an uplink symbol through other signaling.

[0182] The slot format may include sidelink symbols used in direct inter-device communication. The slot format is communicated via RRC signaling specific to cell 110, RRC signaling specific to terminal device 40, and physical layer signaling (e.g., PDCCH or DCI carried by PDCCH).

[0183] Figure 17 is a diagram illustrating an example of a scheduling method in the case of TDD according to the embodiment of this disclosure. In the scheduling method shown in Figure 17, the base station device 20 notifies the second PDCCH 142 in addition to the first PDCCH 141.

[0184] The first PDCCH141 is the same as the one PDCCH described above and is used to send to one terminal device 40. Multiple PDSCHs or PUSCHs are scheduled by the first PDCCH141.

[0185] Furthermore, the second PDCCH142 is used to notify information indicating the slot format (SFI: slot format indicator). The second PDCCH142 may be used to notify multiple terminal devices 40.

[0186] Whether a PDSCH or PUSCH scheduled by the first PDCCH141 is ultimately used for transmission is determined based on the slot format notified (or set) by the second PDCCH142.

[0187] For example, a PDSCH scheduled by the first PDCCH141 is used for signal transmission when the slot format notified (or set) by another signaling (second PDCCH142) is a downlink symbol.

[0188] Furthermore, if some of the symbols to which the PDSCH can be mapped are not downlink symbols (for example, uplink symbols), the PDSCH may not be used for signal transmission. If the symbols to which the PDSCH can be mapped are downlink symbols or flexible symbols (for example, not uplink symbols), the PDSCH may be used for signal transmission.

[0189] For example, a PUSCH scheduled on the first PDCCH141 is used to transmit a signal when the slot format notified (or set) by another signaling (second PDCCH142) is an uplink symbol.

[0190] Furthermore, if some of the symbols to which the pusher can be mapped are not uplink symbols (for example, downlink symbols), the pusher may not be used for signal transmission. If the symbols to which the pusher can be mapped are uplink symbols or flexible symbols (for example, not downlink symbols), the pusher may be used for signal transmission.

[0191] Furthermore, the slot format notified by SFI after receiving the first PDCCH141 may be such that it does not contradict the PDSCH or PUSCH scheduled by the first PDCCH141. That is, if a PDSCH is scheduled by the first PDCCH141, the terminal device 40 assumes that the symbol to which that PDSCH is mapped will not be notified by SFI as an uplink. Also, if a PUSCH is scheduled by a PDCCH, the terminal device 40 assumes that the symbol to which that PUSCH is mapped will not be notified by SFI as a downlink.

[0192] <3.8. Scheduling with Dual DCI> In the example described above, we assumed that one DCI is included in one PDCCH, but this is not limited to this. For example, to schedule multiple PDSCHs, a DCI transmitted in a PDCCH is split into two. One part of the DCI (the first DCI) is advertised in the PDCCH as described above, and the other part (at least the remaining part) of the DCI (the second DCI) is mapped within each PDSCH. By receiving these two DCIs, the terminal device 40 can receive signals in the multiple scheduled PDSCHs.

[0193] Figure 18 is a diagram illustrating an example of a scheduling method using dual DCI according to an embodiment of this disclosure.

[0194] The first DCI is communicated by the PDCCH shown in Figure 18. The first DCI may include transmit parameters commonly used by the scheduled PDSCH, as well as time-domain and / or frequency-domain resource mapping information for the scheduled PDSCH.

[0195] The second DCI is mapped to a predetermined resource within each PDSCH. The second DCI may include PDSCH-specific transmission parameters to which the second DCI is mapped.

[0196] The given resource to which the second DCI is mapped is its relative position within the PDSCH. For example, the time domain of a given resource is the first symbol in the PDSCH. Alternatively, the frequency domain of a given resource is mapped from the first resource block in the PDSCH.

[0197] In this way, by dividing the DCI into a first DCI and a second DCI and transmitting them separately, the base station device 20 can reduce the overhead of the PDCCH transmitting the first DCI. Furthermore, the base station device 20 can use the second DCI to flexibly set the transmission parameters specific to each PDSCH.

[0198] Dual DCI (first and second DCI) can be applied in the multi-slot and / or multi-carrier cases described above.

[0199] Figure 19 illustrates an example of a scheduling method applying a dual DCI to multiple slots according to the embodiment of this disclosure.

[0200] The first DCI is notified by the PDCCH shown in Figure 19. Note that in Figure 19, the PDCCH is located in a different resource block from PDSCH#0, but it may be located in a part of PDSCH#0, as in Figure 12. The first DCI notifies the transmission parameters of all PDSCH#n_0~#n_6 and #n+1_0~#n+1_6 in multiple slots.

[0201] The second DCI is mapped to a predetermined resource within the leading PDSCH (PDSCH#n_0, #n+1_0) of each slot. The second DCI mapped to PDSCH#n_0 notifies the transmission parameters of multiple PDSCH#n_0 to #n_6 within slot #n. The second DCI mapped to PDSCH#n+1_0 notifies the transmission parameters of multiple PDSCH#n+1_0 to #n+1_6 within slot #n+1.

[0202] The first DCI notifies the transmission parameters of multiple PDSCHs in multiple slots, while the second DCI notifies the transmission parameters of multiple PDSCHs within each slot. In other words, the first and second DCIs differ in the time-direction granularity (transmission frequency) of the scheduled PDSCHs.

[0203] Figure 20 illustrates an example of a scheduling method that applies dual DCI to multiple carriers according to the embodiment of this disclosure.

[0204] The first DCI is notified by the PDCCH shown in Figure 20. The first DCI notifies the transmission parameters of all PDSCH#A_0~#A_6 and #B_0~#B_6 in multiple BWP#A and #B.

[0205] The second DCI is mapped to a predetermined resource within the leading PDSCH(PDSCH#A_0, #B_0) of each BWP#A and #B. The second DCI mapped to PDSCH#A_0 notifies the transmission parameters of multiple PDSCH#A_0 to #A_6 within BWP#A. The second DCI mapped to PDSCH#B_0 notifies the transmission parameters of multiple PDSCH#B_0 to #B_6 within BWP#B.

[0206] The first DCI notifies the transmission parameters of multiple PDSCHs across multiple BWPs, while the second DCI notifies the transmission parameters of multiple PDSCHs within each BWP. In other words, the first and second DCIs differ in the frequency granularity of the scheduled PDSCHs.

[0207] Figure 21 illustrates another example of a scheduling method applying dual DCI to multiple carriers according to the embodiments of this disclosure.

[0208] The first DCI is notified by the PDCCH shown in Figure 21. The first DCI notifies the transmission parameters of all PDSCH#A_0~#A_6 and #B_0~#B_6 in multiple BWP#A and #B.

[0209] The second DCI is mapped to a predetermined resource within each PDSCH (PDSCH#A_0 to #A_6) in BWP#A. The second DCI mapped to PDSCH#A_0 notifies the transmission parameters of PDSCH#A_0 and the corresponding PDSCH#B_0 in BWP#B. In this case, the multiple PDSCHs scheduled by the second DCI may be restricted so that at least one OFDM symbol overlaps.

[0210] Thus, the second DCI is mapped to a PDSCH in at least one frequency band (e.g., BWP#A) of multiple frequency bands (e.g., BWP#A, #B). The second DCI notifies the transmission parameters of one or more PDSCHs corresponding to that PDSCH, which are located in multiple frequency bands.

[0211] Specific examples of the first and second DCIs will be explained.

[0212] The first DCI notifies the start symbol position of each PDSCH. The second DCI notifies the number of symbols or the end symbol position of that PDSCH.

[0213] The first DCI notifies multiple PDSCHs of the MIMO layer count (spatial multiplexing count, rank count) and / or beam information as common transmission parameters. The second DCI notifies the PDSCH of information indicating its modulation scheme and / or coding rate (such as MCS number and Redundancy version number).

[0214] The first DCI notifies multiple PDSCHs of frequency domain resource mapping information as a common transmission parameter.

[0215] In particular, in the case of a multi-slot configuration (see, for example, Figure 19), the first DCI may notify transmit parameters for multiple PDSCHs in multiple slots. For example, the first DCI may notify transmit parameters common to each slot. For example, the first DCI may include frequency domain resource mapping information for each PDSCH in each slot.

[0216] In particular, in the case of a multi-slot configuration (see, for example, Figure 19), the second DCI may notify the transmission parameters for multiple PDSCHs within each slot. For example, the second DCI may notify the transmission parameters specific to each PDSCH in each slot. The second DCI includes time-domain resource mapping information for each PDSCH in each slot.

[0217] In particular, in the case of multi-carrier transmissions (see, for example, Figure 20), the first DCI may notify transmit parameters for multiple PDSCHs in multiple BWPs. For example, the first DCI may notify transmit parameters common to each BWP. For example, the first DCI may include frequency domain resource mapping information for the PDSCH in each slot.

[0218] In particular, in the case of multi-carrier systems (see, for example, Figure 20), the second DCI may notify the transmission parameters for multiple PDSCHs within each BWP. For example, the second DCI notifies the transmission parameters specific to each PDSCH in each BWP. The second DCI includes frequency domain resource mapping information for the PDSCHs in each BWP.

[0219] In particular, in the case of multi-carrier transmissions (see, for example, Figure 21), the first DCI may notify transmit parameters for multiple PDSCHs in multiple BWPs. For example, the first DCI may notify transmit parameters common to each BWP. For example, the first DCI may include frequency domain resource mapping information for the PDSCH in each slot.

[0220] In particular, in the case of multi-carrier transmissions (see, for example, Figure 21), the second DCI may notify transmit parameters for multiple PDSCHs corresponding across multiple BWPs. For example, the second DCI notifies transmit parameters specific to each PDSCH corresponding across multiple BWPs. The second DCI includes frequency domain resource mapping information for the PDSCHs corresponding across multiple BWPs.

[0221] <3.9. Multi-scheduling for PDSCH and PUSCH> This section describes an example where, in the case of a single carrier and single slot, one PDCCH schedules one or more PDSCHs and one or more PUSCHs within a given slot.

[0222] Figure 22 is a diagram illustrating an example of a multi-scheduling method according to the present disclosure. In the example of Figure 22, the base station device 20 schedules four PDSCH#0 to #2, #5 and three PUSCH#3, #4, #6 with one PDCCH.

[0223] In this case, the DCIs that schedule these PDSCH and PUSCH can be classified into the following types. These types may be predetermined or configured through RRC signaling to be cell 110 specific or terminal device 40 specific. • Transmission parameters common to all scheduled PDSCH and PUSCH • Common transmission parameters that apply only to all scheduled PDSCHs • Common transmission parameters that apply only to all scheduled pushes. • Specific transmission parameters for each scheduled PDSCH or PUSCH.

[0224] Common transmission parameters for all scheduled PDSCHs and PUSCHs include, for example, information regarding frequency domain resource mapping.

[0225] Common transmission parameters that apply only to all scheduled PDSCHs include, for example, information about the beam on the downlink and MCS.

[0226] Common transmit parameters that apply only to all scheduled pushes include, for example, information about the uplink beam, MCS, and transmit power control.

[0227] Examples of transmission parameters specific to each scheduled PDSCH or PUSCH include information about the HARQ process, information about retransmission control, and information about time-domain resource mapping.

[0228] The multi-scheduling method described here can be implemented in combination with the other scheduling methods mentioned above.

[0229] <3.10. Multi-PSSCH scheduling method for high-speed URLLC communication> The scheduling methods for multiple PDSCHs and / or PUSCHs described above can also be applied to scheduling multiple PSSCHs (Physical sidelink shared channels). A PSSCH is a data channel used in device-to-device communication (D2D communication, sidelink communication, PC5 communication).

[0230] The PDSCH and PUSCH described above can be interpreted as PSSCH. Similarly, the PDCCH described above can be interpreted as PSCCH (Physical sidelink control channel). In particular, the DCI described in the dual DCI scheduling section can be interpreted as SCI (Sidelink control information).

[0231] Multiple scheduling modes are defined for inter-terminal communication, such as a first mode and a second mode.

[0232] In the first mode, the base station device 20 determines the resources to be used for sidelink communication and notifies the transmitting terminal (Tx UE) of control information indicating those resources via PDCCH. The Tx UE uses those resources to transmit PSCCH and PSSCH to the receiving terminal (Rx UE). PSCCH contains scheduling information from the Tx UE to the Rx UE.

[0233] For example, base station equipment 20 notifies Tx UE of a large resource. Tx UE divides that resource and transmits multiple PSSCHs. At this time, Tx UE transmits scheduling information for multiple PSSCHs in a single PSCCH, similar to the scheduling method described above.

[0234] In the second mode, the Tx UE selects resources from some or all of a predetermined time-frequency resource (resource pool) set in advance by the base station equipment 20. The Tx UE uses the selected resources to transmit PSCCH and PSSCH to the Rx UE.

[0235] In the second mode as well, the Tx UE transmits scheduling information for multiple PSSCHs using a single PSCCH, similar to the scheduling method described above.

[0236] Furthermore, in the second mode, when the Tx UE selects a resource, it pre-senses the usage status within the given resource to reduce collisions with data transmitted from other Tx UEs.

[0237] This sensing is typically performed in units of slots (14 OFDM symbols). In this embodiment, the Tx UE may perform sensing based on a time length corresponding to the symbol length of the PSSCH, or it may perform it in units of slots as usual. When sensing is performed in units of slots, resource selection is on a slot-by-slot basis, but the Tx UE can transmit multiple PSSCHs using a portion of the selected slot.

[0238] <<4. Other Embodiments>> The embodiments and variations described above are merely examples, and various modifications and applications are possible.

[0239] For example, the control device that controls the base station device 20 and terminal device 40 in the above-described embodiment may be implemented by a dedicated computer system or by a general-purpose computer system.

[0240] For example, a communication program for performing the above-described operations is stored in a computer-readable recording medium such as an optical disc, semiconductor memory, magnetic tape, or flexible disk and distributed. Then, for example, the control device is configured by installing the program on a computer and executing the above-described process. In this case, the control device may be an external device to the transmitting device and receiving device (e.g., a personal computer). Alternatively, the control device may be an internal device to the transmitting device and receiving device (e.g., a control unit).

[0241] Alternatively, the above communication program may be stored on a disk device provided by a server on a network such as the Internet, and made available for download to a computer. Furthermore, the above functions may be realized through the cooperation of an OS (Operating System) and application software. In this case, the parts other than the OS may be stored on a medium and distributed, or the parts other than the OS may be stored on a server device and made available for download to a computer.

[0242] Furthermore, among the processes described in the above embodiments, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically by known methods. In addition, the processing procedures, specific names, and information including various data and parameters shown in the above document and drawings can be arbitrarily changed unless otherwise specified. For example, the various information shown in each figure is not limited to the information shown.

[0243] Furthermore, the components of each illustrated device are functionally conceptual and do not necessarily need to be physically configured as shown. In other words, the specific forms of distribution and integration of each device are not limited to those shown, and all or part of them can be functionally or physically distributed and integrated in any unit according to various loads and usage conditions. This distribution and integration configuration may also be performed dynamically.

[0244] Furthermore, the above-described embodiments can be combined as appropriate in areas where the processing content is not contradictory. Also, the order of each step shown in the sequence diagram of the above-described embodiments can be changed as appropriate.

[0245] Furthermore, for example, this embodiment can also be implemented as any configuration that constitutes a device or system, such as a processor as a system LSI (Large Scale Integration), a module using multiple processors, a unit using multiple modules, or a set with additional functions added to a unit (i.e., a configuration of a part of a device).

[0246] Furthermore, while some of the embodiments described above primarily described cases where the target radio access technology is LTE, NR, or a combination thereof, it is not limited to these cases. For example, it may also be applied to radio access technology in 6G communication, the next generation after 5G NR. For example, the terminal equipment and base station equipment described above may be 6G UE and 6G base station. The proper nouns for functions, entities, standards, and information (parameters) of LTE and 5G NR in some of the embodiments described above may be the same names used in 6G, or 6G-specific names may be used. In other words, the various proper nouns in some of the embodiments described above may be replaced by generalized names or descriptions.

[0247] In addition, in the present embodiment, the system means a collection of a plurality of components (devices, modules (parts), etc.), and it does not matter whether all the components are in the same housing. Therefore, a plurality of devices housed in separate housings and connected via a network, and one device in which a plurality of modules are housed in one housing are both systems.

[0248] Also, for example, the present embodiment can take a configuration of cloud computing in which one function is shared and jointly processed by a plurality of devices via a network.

[0249] <<5. Conclusion>> As described above, the embodiments of the present disclosure have been described. However, the technical scope of the present disclosure is not limited to the above-described embodiments as they are, and various changes can be made without departing from the gist of the present disclosure. Also, components across different embodiments and variations may be appropriately combined.

[0250] Also, the effects in each of the embodiments described in this specification are merely examples and are not limiting, and there may be other effects.

[0251] Note that the present technology can also take the following configuration. (1) A terminal device, a transceiver, and a hardware processor, and the hardware processor receives one PDCCH (Physical Downlink Control Channel) via the transceiver, the one PDCCH schedules a plurality of physical shared channels in one or more carriers or one or more slots, the one PDCCH and the plurality of physical shared channels are transmitted to the terminal device, The plurality of physical shared channels are a plurality of PDSCHs (Physical Downlink Shared Channels) or a plurality of PUSCHs (Physical Uplink Shared Channels). Terminal device. (2) Among the communication parameters applied to the plurality of physical shared channels scheduled by the one PDCCH, some of the communication parameters are commonly applied to the plurality of physical shared channels, and the remaining communication parameters are individually applied to each of the plurality of physical shared channels. The terminal device according to (1). (3) Some of the communication parameters are commonly applied to the plurality of physical shared channels at least in one of a predetermined time duration and a predetermined frequency band. The terminal device according to (2). (4) The communication parameters include parameters related to resource mapping in at least one of the time domain and the frequency domain. The terminal device according to (2) or (3). (5) The transceiver supports communication in which the mapping type of the physical shared channel is type B. The terminal device according to any one of (1) to (4). (6) The start symbols of the plurality of physical shared channels are notified in bitmap format. The terminal device according to any one of (1) to (5). (7) The start symbols of the plurality of physical shared channels are notified as information indicating the relative position with respect to a predetermined symbol position of the one PDCCH. The terminal device according to any one of (1) to (5). (8) The plurality of physical shared channels are scheduled based on a slot format. The terminal device according to any one of (1) to (7). (9) The one PDCCH includes a part of control information. The physical shared channel includes at least a part of the remaining control information. A terminal device as described in any one of (1) to (8). (10) The control information contained in the single PDCCH includes information regarding the communication parameters of multiple physical shared channels in multiple slots, The control information included in the physical shared channel includes information regarding the communication parameters of a plurality of physical shared channels within the slot where the physical shared channel is located. (9) The terminal device described above. (11) The control information included in the single PDCCH includes information regarding the communication parameters of multiple physical shared channels in multiple frequency bands, The control information included in the physical shared channel includes information regarding the communication parameters of a plurality of physical shared channels within the frequency band in which the physical shared channel is located. (9) The terminal device described above. (12) The control information included in the single PDCCH includes information regarding the communication parameters of multiple physical shared channels in multiple frequency bands, The control information included in the physical shared channel includes information regarding the communication parameters of the physical shared channel, which corresponds to the physical shared channel to which the control information is mapped, and which is arranged in a plurality of frequency bands. (9) The terminal device described above. (13) The terminal device according to any one of (1) to (12), wherein the multiple physical shared channels are one or more PDSCHs and one or more PUSCHs. (14) Base station equipment, Transceiver and, It has a hardware processor, The hardware processor transmits one PDCCH (Physical Downlink Control Channel) to the terminal device via the transceiver. The aforementioned PDCCH schedules multiple physical shared channels in one or more carriers or one or more slots, The aforementioned one PDCCH and the plurality of the aforementioned physical shared channels were transmitted to the terminal device. The multiple physical shared channels are multiple PDSCHs (Physical Downlink Shared Channels) or multiple PUSCHs (Physical Uplink Shared Channels). Base station equipment. (15) The base station apparatus according to (14), wherein, of the communication parameters applied to a plurality of physical shared channels scheduled by the single PDCCH, some of the communication parameters are applied in common to the plurality of physical shared channels, and the remaining communication parameters are applied individually to each of the plurality of physical shared channels. (16) The base station apparatus according to (15), wherein some of the aforementioned communication parameters are applied in common to a plurality of physical shared channels within a predetermined time length and at least one of a predetermined frequency band. (17) The base station apparatus according to (15) or (16), wherein the communication parameters include parameters relating to resource mapping in at least one of the time domain and the frequency domain. (18) The transceiver supports communication where the mapping type of the physical shared channel is type B, as described in any one of (14) to (17). (19) The base station equipment described in any one of (14) to (18) is provided with start symbols for multiple physical shared channels in bitmap format. (20) The base station device according to any one of (14) to (18), wherein the start symbols of the multiple physical shared channels are notified as information indicating their relative position to a predetermined symbol position of one PDCCH. (twenty one) The plurality of the physical shared channels are scheduled based on a slot format, and the base station apparatus according to any one of (14) to (20). (22) The one PDCCH includes a part of control information, The physical shared channel includes at least a part of the remaining control information. (14) to (21) of the base station apparatus according to any one of the above. (23) The control information included in the one PDCCH includes information regarding communication parameters of the plurality of the physical shared channels in a plurality of slots. The control information included in the physical shared channel includes information regarding the communication parameters of the plurality of the physical shared channels within the slot in which the physical shared channel is arranged. (22) of the base station apparatus according to the above. (24) The control information included in the one PDCCH includes information regarding communication parameters of the plurality of the physical shared channels in a plurality of frequency bands. The control information included in the physical shared channel includes information regarding the communication parameters of the plurality of the physical shared channels within the frequency band in which the physical shared channel is arranged. (22) of the base station apparatus according to the above. (25) The control information included in the one PDCCH includes information regarding communication parameters of the plurality of the physical shared channels in a plurality of frequency bands. The control information included in the physical shared channel includes information regarding the communication parameters of the physical shared channels corresponding to the physical shared channel to which the control information is mapped and arranged in a plurality of the frequency bands. (22) of the base station apparatus according to the above. (26) The plurality of the physical shared channels are one or more PDSCHs and one or more PUSCHs, and the base station apparatus according to any one of (14) to (25). (27) A communication method for terminal devices, This includes receiving one PDCCH (Physical Downlink Control Channel), The aforementioned PDCCH schedules multiple physical shared channels in one or more carriers or one or more slots, The aforementioned one PDCCH and the plurality of the aforementioned physical shared channels were transmitted to the terminal device. The multiple physical shared channels are multiple PDSCHs (Physical Downlink Shared Channels) or multiple PUSCHs (Physical Uplink Shared Channels). Communication method. (28) A communication method for base station equipment, This includes transmitting one PDCCH (Physical Downlink Control Channel) to a terminal device. The aforementioned PDCCH schedules multiple physical shared channels in one or more carriers or one or more slots, The aforementioned one PDCCH and the plurality of the aforementioned physical shared channels were transmitted to the terminal device. The multiple physical shared channels are multiple PDSCHs (Physical Downlink Shared Channels) or multiple PUSCHs (Physical Uplink Shared Channels). Communication method. [Explanation of Symbols]

[0252] 1. Communication System 20 Base station equipment 21, 41 Signal Processing Unit 22, 42 Storage section 23 Network Communications Department 24, 45 Control Unit 40 Terminal devices 44 Input / output section

Claims

1. A terminal device, Transceiver and, It has a hardware processor, The hardware processor receives one PDCCH (Physical Downlink Control Channel) via the transceiver, The aforementioned PDCCH schedules multiple physical shared channels in one or more carriers or one or more slots, The aforementioned one PDCCH and the plurality of the aforementioned physical shared channels were transmitted to the terminal device. The multiple physical shared channels are multiple PDSCHs (Physical Downlink Shared Channels), The aforementioned PDCCH includes a portion of the control information, The physical shared channel includes at least a portion of the remaining control information. Terminal device.

2. The terminal device according to claim 1, wherein, of the communication parameters applied to the multiple physical shared channels scheduled by the one PDCCH, some of the communication parameters are applied in common to the multiple physical shared channels, and the remaining communication parameters are applied individually to each of the multiple physical shared channels.

3. The terminal device according to claim 2, wherein some of the communication parameters are applied in common to a plurality of physical shared channels within a predetermined time length and / or within a predetermined frequency band, at least one of the above.

4. The terminal device according to claim 1, wherein the transceiver supports communication where the mapping type of the physical shared channel is type B.

5. The terminal device according to claim 1, wherein the start symbols of the multiple physical shared channels are notified in bitmap format.

6. The terminal device according to claim 1, wherein the start symbols of the multiple physical shared channels are notified as information indicating their relative position to a predetermined symbol position of one PDCCH.

7. The terminal device according to claim 1, wherein the multiple physical shared channels are scheduled based on a slot format.

8. Base station equipment, Transceiver and, It has a hardware processor, The hardware processor transmits one PDCCH (Physical Downlink Control Channel) to the terminal device via the transceiver. The aforementioned PDCCH schedules multiple physical shared channels in one or more carriers or one or more slots, The aforementioned one PDCCH and the plurality of the aforementioned physical shared channels were transmitted to the terminal device. The multiple physical shared channels are multiple PDSCHs (Physical Downlink Shared Channels), The aforementioned PDCCH includes a portion of the control information, The physical shared channel includes at least a portion of the remaining control information. Base station equipment.

9. The base station device according to claim 8, wherein, of the communication parameters applied to the multiple physical shared channels scheduled by the one PDCCH, some of the communication parameters are applied in common to the multiple physical shared channels, and the remaining communication parameters are applied individually to each of the multiple physical shared channels.

10. The base station apparatus according to claim 9, wherein some of the communication parameters are applied in common to a plurality of physical shared channels within a predetermined time length and / or within a predetermined frequency band, at least one of the above.

11. The base station apparatus according to claim 8, wherein the transceiver supports communication where the mapping type of the physical shared channel is type B.

12. The base station apparatus according to claim 8, wherein the start symbols of the multiple physical shared channels are notified in bitmap format.

13. The base station device according to claim 8, wherein the start symbols of the multiple physical shared channels are notified as information indicating their relative position to a predetermined symbol position of one PDCCH.

14. The base station apparatus according to claim 8, wherein the multiple physical shared channels are scheduled based on a slot format.

15. A communication method for terminal devices, This includes receiving one PDCCH (Physical Downlink Control Channel), The aforementioned PDCCH schedules multiple physical shared channels in one or more carriers or one or more slots, The aforementioned one PDCCH and the plurality of the aforementioned physical shared channels were transmitted to the terminal device. The multiple physical shared channels are multiple PDSCHs (Physical Downlink Shared Channels), The aforementioned PDCCH includes a portion of the control information, The physical shared channel includes at least a portion of the remaining control information. Communication method.

16. A communication method for base station equipment, This includes transmitting one PDCCH (Physical Downlink Control Channel) to a terminal device. The aforementioned PDCCH schedules multiple physical shared channels in one or more carriers or one or more slots, The aforementioned one PDCCH and the plurality of the aforementioned physical shared channels were transmitted to the terminal device. The multiple physical shared channels are multiple PDSCHs (Physical Downlink Shared Channels), The aforementioned PDCCH includes a portion of the control information, The physical shared channel includes at least a portion of the remaining control information. Communication method.

Images