Base station and communication system

Abstract

A base station is capable of performing periodic communication for transmitting and receiving data to and from a communication terminal at a predetermined cycle, and when transmitting downlink data, allocates a physical downlink control channel and a physical downlink shared channel to be used in a first cycle, which is the transmission cycle of the downlink data. When uplink data is received, a physical downlink shared channel used in a first period is changed in accordance with a change in the amount of downlink data, and the result of the change is notified to the communication terminal via a physical downlink control channel allocated to the first period, and when uplink data is received, the physical downlink shared channel used in the first period is changed in accordance with the change in the amount of downlink data. A physical downlink control channel and a physical uplink shared channel used in a second period, which is a transmission period of uplink data, are allocated, and the physical uplink shared channel used in the second period is changed in accordance with a change in the amount of uplink data. And notifying the communication terminal of the change result through the physical downlink control channel allocated to the second period.

Description

Technical Field

[0001] The present disclosure relates to wireless communication technology. Background Art

[0002] In 3GPP (3rd Generation Partnership Project), a standardization organization for mobile communication systems, the fifth generation (sometimes referred to as "5G") wireless access system is being discussed as a successor to Long Term Evolution (LTE) and Long Term Evolution Advanced (LTE-A), one of the fourth generation wireless access systems (see Non-Patent Document 1) (for example, Non-Patent Document 2). The technology for the wireless section of 5G is called "New Radio Access Technology" ("New Radio" is abbreviated as "NR"). The NR system is discussed based on the LTE system and the LTE-A system.

[0003] For example, in Europe, the METIS organization is summarizing the requirements for 5G (see non-patent document 3). In the 5G wireless access system, the system capacity is 1000 times that of the LTE system, the data transmission speed is 100 times, the data processing delay is 1 / 5, and the number of simultaneous connections of communication terminals is 100 times. The conditions for achieving further low power consumption and low cost of the device can be listed as requirements (see non-patent document 3).

[0004] In order to meet such requirements, discussions on 5G standards are progressing in 3GPP (see non-patent documents 4 to 23).

[0005] As the access method of NR, OFDM (Orthogonal Frequency Division Multiplexing) is used in the downlink direction, and OFDM and DFT-s-OFDM (Discrete Fourier Transform-spread-OFDM) are used in the uplink direction. In addition, like LTE and LTE-A, the 5G system does not include line switching, but only packet communication.

[0006] In NR, higher frequencies can be used compared to LTE to increase transmission speeds and reduce processing delays.

[0007] In NR, which sometimes uses higher frequencies than LTE, a narrower beam-shaped transmission and reception range is formed (beamforming) and the direction of the beam is changed (beam scanning), thereby attempting to ensure cell coverage.

[0008] use Figure 1 This article explains the decisions made by 3GPP regarding the frame structure of the NR system as described in Non-Patent Document 1 (Chapter 5). Figure 1 This is an explanatory diagram showing the structure of a wireless frame used in a communication system using the NR method. Figure 1 In NR, one radio frame is 10ms. The radio frame is divided into 10 subframes of equal size. The frame structure of NR supports one or more parameter sets (Numerology), that is, one or more subcarrier spacings (Subcarrier spacing: SCS). In NR, one subframe is 1ms, and one time slot consists of 14 code elements, regardless of the subcarrier spacing. In addition, the number of time slots contained in one subframe is one when the subcarrier spacing is 15kHz, and the number of time slots in other subcarrier spacings increases in proportion to the subcarrier spacing (refer to non-patent document 11 (3GPP TS38.211)).

[0009] Non-Patent Document 2 (Chapter 5) and Non-Patent Document 11 record the decisions made by 3GPP regarding the channel structure in the NR system.

[0010] The Physical Broadcast Channel (PBCH) is a channel used for downlink transmission from a base station device (hereinafter sometimes referred to as "base station") to a communication terminal device (hereinafter sometimes referred to as "communication terminal" or "terminal") such as a mobile terminal device (hereinafter sometimes referred to as "mobile terminal"). The PBCH is transmitted together with a downlink synchronization signal.

[0011] The downlink synchronization signal in NR has a first synchronization signal (Primary Synchronization Signal: P-SS) and a second synchronization signal (Secondary Synchronization Signal: S-SS). The synchronization signal is sent from the base station as a synchronization signal burst (Synchronization Signal Burst: sometimes referred to as SS burst below) at a specified period for a specified duration. The SS burst consists of a synchronization signal block (Synchronization Signal Block; sometimes referred to as SS block below) for each beam of the base station.

[0012] The base station changes the beam during the duration of the SS burst to transmit the SS block of each beam. The SS block consists of P-SS, S-SS and PBCH.

[0013] The Physical Downlink Control Channel (PDCCH) is a channel for downlink transmission from the base station to the communication terminal. PDCCH transmits downlink control information (DCI). DCI includes resource allocation information for the downlink shared channel (DL-SCH), which is one of the transmission channels described later, resource allocation information for the paging channel (PCH), which is one of the transmission channels described later, and HARQ (Hybrid Automatic Repeat reQuest) information related to DL-SCH. In addition, DCI sometimes includes an uplink scheduling grant. DCI sometimes includes a response signal for uplink transmission, namely Ack (Acknowledgement) / Nack (Negative Acknowledgement). In addition, in order to flexibly switch DL / UL within a time slot, DCI sometimes includes a time slot format indication (Slot Format Indication: SFI). PDCCH or DCI is also called L1 / L2 control signal.

[0014] In NR, a time domain and a frequency domain are provided as candidates for including PDCCH. This area is called a control resource set (CORESET). The communication terminal monitors CORESET and acquires PDCCH.

[0015] The Physical Downlink Shared Channel (PDSCH) is a channel for downlink transmission from a base station to a communication terminal. A downlink shared channel (DL-SCH) as a transport channel and a PCH as a transport channel are mapped to the PDSCH.

[0016] The Physical Uplink Control Channel (PUCCH) is a channel for uplink transmission from the communication terminal to the base station. PUCCH transmits uplink control information (UCI). UCI includes response information (response signal) for downlink transmission, namely Ack / Nack, CSI (Channel State Information), scheduling request (SR), etc. CSI is composed of RI (Rank Indicator), PMI (Precoding Matrix Indicator), and CQI (Channel Quality Indicator) reports. RI refers to the rank information of the channel matrix in MIMO (Multiple Input Multiple Output). PMI refers to the information of the precoding waiting matrix used in MIMO. CQI is quality information indicating the quality of the received data or the quality of the communication line. UCI is sometimes transmitted through the PUSCH described later. PUCCH or UCI is also called L1 / L2 control signal.

[0017] The physical uplink shared channel (Physical Uplink Shared Channel: PUSCH) is a channel for uplink transmission from a communication terminal to a base station. An uplink shared channel (Uplink Shared Channel: UL-SCH), which is one of the transport channels, is mapped to the PUSCH.

[0018] The Physical Random Access Channel (PRACH) is a channel for uplink transmission from a communication terminal to a base station. The PRACH transmits a random access preamble.

[0019] The downlink reference signal (Reference Signal: RS) is a codeword known as a communication system of the NR mode. The following four downlink reference signals are defined. The UE-specific Reference Signal (UE-specific Reference Signal) is the data demodulation reference signal (Demodulation Reference Signal: DM-RS), the phase tracking reference signal (Phase Tracking Reference Signal: PT-RS), the positioning reference signal (Positioning Reference Signal: PRS), and the channel state information reference signal (Channel State Information Reference Signal: CSI-RS). As a measurement of the physical layer of the communication terminal, there are reference signal received power (Reference Signal Received Power: RSRP) measurement and reference signal received quality (Reference Signal Received Quality: RSRQ) measurement.

[0020] The uplink reference signal is also a symbol known as a communication system of the NR method. The following three types of uplink reference signals are defined: data demodulation reference signal (Demodulation Reference Signal: DM-RS), phase tracking reference signal (Phase Tracking Reference Signal: PT-RS), and sounding reference signal (Sounding Reference Signal: SRS).

[0021] The transport channel described in Non-Patent Document 2 (Chapter 5) is described below. The broadcast channel (BCH) in the downlink transport channel is broadcast to the entire coverage area of ​​its base station (cell). The BCH is mapped to the physical broadcast channel (PBCH).

[0022] HARQ-based retransmission control is applied to the downlink shared channel (DL-SCH). DL-SCH can broadcast to the entire coverage area of ​​the base station (cell). DL-SCH supports dynamic or quasi-static resource allocation. Quasi-static resource allocation is also called semi-persistent scheduling. DL-SCH supports discontinuous reception (DRX) of communication terminals in order to reduce power consumption of communication terminals. DL-SCH is mapped to the physical downlink shared channel (PDSCH).

[0023] The Paging Channel (PCH) supports DRX of the communication terminal in order to reduce the power consumption of the communication terminal. The PCH is requested to be broadcast to the entire coverage area of ​​the base station (cell). The PCH is mapped to a physical resource such as the Physical Downlink Shared Channel (PDSCH) that can be dynamically used for traffic.

[0024] Retransmission control using HARQ is applied to the uplink shared channel (UL-SCH) in the uplink transmission channel. UL-SCH supports dynamic or quasi-static resource allocation. Quasi-static resource allocation is also called configured grant. UL-SCH is mapped to the physical uplink shared channel (PUSCH).

[0025] The Random Access Channel (RACH) is limited to control information. There is a risk of collision in the RACH. The RACH is mapped to the Physical Random Access Channel (PRACH).

[0026] The following is an explanation of HARQ. HARQ is a technology that improves the communication quality of a transmission line by combining Automatic RepeatreQuest (ARQ) and Forward Error Correction (Forward Error Correction). HARQ has the following advantages: even for a transmission line with changed communication quality, error correction can be effectively used by retransmission. In particular, when retransmission is performed, the quality can be further improved by synthesizing the reception result of the first transmission and the reception result of the retransmission.

[0027] An example of the retransmission method is described below. When the receiving side cannot correctly decode the received data, in other words, when a CRC (Cyclic Redundancy Check) error occurs (CRC=NG), "Nack" is sent from the receiving side to the sending side. The sending side that receives "Nack" retransmits the data. When the receiving side can correctly decode the received data, in other words, when no CRC error occurs (CRC=OK), "Ack" is sent from the receiving side to the sending side. The sending side that receives "Ack" sends the next data.

[0028] Other examples of the retransmission method are described. When a CRC error occurs on the receiving side, a retransmission request is made from the receiving side to the sending side. The retransmission request is made by switching the NDI (New Data Indicator). The sending side that receives the retransmission request retransmits the data. When no CRC error occurs on the receiving side, no retransmission request is made. When the sending side does not receive a retransmission request within a specified time, it is deemed that no CRC error is sent on the receiving side.

[0029] The logical channel described in Non-Patent Document 1 (Chapter 6) is described below. The Broadcast Control Channel (BCCH) is a downlink channel for broadcasting system control information. The BCCH as a logical channel is mapped to the Broadcast Channel (BCH) as a transport channel or the Downlink Shared Channel (DL-SCH).

[0030] The Paging Control Channel (PCCH) is a downlink channel for transmitting changes in paging information (PagingInformation) and system information (SystemInformation). The PCCH, which is a logical channel, is mapped to the Paging Channel (PCH), which is a transport channel.

[0031] The Common Control Channel (CCCH) is a channel used to send control information between a communication terminal and a base station. The CCCH is used when there is no RRC connection between the communication terminal and the network. In the downlink direction, the CCCH is mapped to the downlink shared channel (DL-SCH) as a transport channel. In the uplink direction, the CCCH is mapped to the uplink shared channel (UL-SCH) as a transport channel.

[0032] Dedicated Control Channel (DCCH) is a channel used to send dedicated control information between a communication terminal and a network in a point-to-point manner. DCCH is used when there is an RRC connection between a communication terminal and a network. DCCH is mapped to the uplink shared channel (UL-SCH) in the uplink and to the downlink shared channel (DL-SCH) in the downlink.

[0033] Dedicated Traffic Channel (DTCH) is a channel used to send user information and perform point-to-point communication with communication terminals. DTCH exists in both uplink and downlink. DTCH is mapped to the uplink shared channel (UL-SCH) in the uplink and to the downlink shared channel (DL-SCH) in the downlink.

[0034] The location tracking of the communication terminal is performed in units of an area consisting of one or more cells. The location tracking is performed to track the location of the communication terminal even in the standby state, so as to call the communication terminal. In other words, it is performed to call the communication terminal. The area used for the location tracking of the communication terminal is called a tracking area (TA).

[0035] NR supports calling of communication terminals within a range smaller than the tracking area. This range is called RAN Notification Area (RNA). Paging of communication terminals in the RRC_INACTIVE state described later is performed within this range.

[0036] In order to support wider frequency bandwidths (transmission bandwidths), carrier aggregation (CA) of aggregating (also called "aggregation") two or more component carriers (CC) is being studied in NR. CA is described in Non-Patent Document 1.

[0037] In the case of CA, the UE as a communication terminal has a unique RRC connection (RRC connection) with the network (Network: NW). In the RRC connection, one service cell provides NAS mobility information and security input. This cell is called the primary cell (Primary Cell: PCell). According to the capabilities (capability) of the UE, a secondary service cell (Secondary Cell: SCell) is formed to form a group of service cells together with the PCell. For one UE, a group of service cells consisting of one PCell and one or more SCells is formed.

[0038] In addition, in 3GPP, there is a dual connectivity (DC) in which a UE connects to two base stations for communication, in order to further increase the communication capacity. DC is described in Non-Patent Documents 1 and 22.

[0039] Sometimes one of the base stations performing dual connectivity (DC) is called the "master base station (Master Node: MN)", and the other is called the "secondary base station (Secondary Node: SN)". The service cells formed by the master base station are sometimes collectively referred to as the master cell group (Master Cell Group: MCG), and the service cells formed by the secondary base stations are sometimes collectively referred to as the secondary cell group (Secondary Cell Group: SCG). In DC, the main cell in the MCG or SCG is called a special cell (Special Cell: SpCell or SPCell). The special cell in the MCG is called PCell, and the special cell in the SCG is called the primary SCG cell (PSCell).

[0040] In addition, in NR, the base station pre-sets a part of the carrier frequency band for the UE (hereinafter sometimes referred to as Bandwidth Part: bandwidth part (BWP)), and the UE transmits and receives between itself and the base station in the BWP, thereby being able to reduce power consumption in the UE.

[0041] In addition, in 3GPP, the use of side link (SL) communication (also called PC5 communication) is supported in both the EPS (Evolved Packet System) and the 5G core system described later (see non-patent documents 1, 2, 26 to 28). In SL communication, communication is performed between terminals. As services using SL communication, there are, for example, V2X (Vehicle-to-everything) services and proxy services. In SL communication, not only direct communication between terminals, but also communication between UE and NW via relay is proposed (see non-patent documents 26 and 28).

[0042] The physical channels used for SL are described below (see Non-Patent Documents 2 and 11). The physical sidelink broadcast channel (PSBCH) transmits information related to system synchronization and is sent from the UE.

[0043] The physical sidelink control channel (PSCCH) transmits control information from the UE for sidelink communication and V2X sidelink communication.

[0044] The physical sidelink shared channel (PSSCH) transmits data from the UE for sidelink communication and V2X sidelink communication.

[0045] The physical sidelink feedback channel (PSFCH) transmits HARQ feedback on the sidelink from the UE that receives the PSSCH transmission to the UE that sends the PSSCH.

[0046] The transport channel used for SL will be described below (see Non-Patent Document 1). The sidelink broadcast channel (SL-BCH) has a predetermined transport channel format and is mapped to the PSBCH which is a physical channel.

[0047] The sidelink shared channel (SL-SCH) supports broadcast transmission. SL-SCH supports both UE autonomous resource selection and resource allocation scheduled by the base station. There is a risk of conflict in UE autonomous resource selection, but there is no conflict when the UE is allocated dedicated resources by the base station. In addition, SL-SCH supports dynamic link adaptation by changing the transmission power, modulation, and coding. SL-SCH is mapped to PSSCH, which is a physical channel.

[0048] The logical channels used for SL are described below (see Non-Patent Document 2). The Sidelink Broadcast Control Channel (SBCCH) is a sidelink channel used to broadcast sidelink system information from one UE to other UEs. The SBCCH is mapped to the SL-BCH which is a transport channel.

[0049] Sidelink Traffic Channel (STCH) is a one-to-many sidelink traffic channel used to send user information from one UE to other UEs. STCH is only used by UEs with sidelink communication capabilities and UEs with V2X sidelink communication capabilities. One-to-one communication between two UEs with sidelink communication capabilities is also achieved through STCH. STCH is mapped to SL-SCH, which is a transport channel.

[0050] A sidelink control channel (SCCH) is a sidelink control channel for transmitting control information from one UE to other UEs. The SCCH is mapped to the SL-SCH which is a transport channel.

[0051] In LTE, SL communication is only broadcast. In NR, in addition to broadcast, support for unicast and groupcast is also being studied as SL communication (see Non-Patent Document 27 (3GPP TS23.287)).

[0052] In SL's unicast and multicast communications, HARQ feedback (Ack / Nack), CSI reporting, etc. are supported.

[0053] In addition, 3GPP is studying Integrated Access and Backhaul (IAB) in which both an access link as a link between a UE and a base station and a backhaul link as a link between base stations are wirelessly performed (see Non-Patent Documents 2, 20, and 29).

[0054] In 3GPP, some new technologies have been proposed. For example, a communication method suitable for XR (eXtended Reality) or cloud gaming services has been discussed (non-patent document 30), and an XR identification method that takes into account the characteristics of XR traffic (such as non-integer periodicity, data generation time variation (jitter) characteristics, data volume variation characteristics, low latency characteristics, etc.), an XR-specific low power consumption method, and an XR-specific capacity improvement method have been proposed (non-patent documents 31, 32, 33). Prior art literature Non-patent literature

[0055] Non-patent document 1: 3GPP TS36.300 V16.7.0 Non-patent document 2: 3GPP TS38.300 V16.8.0 Non-patent document 3: “Scenarios, requirements and KPIs for 5G mobile and wireless system: ICT-317669-METIS / D1.1 Non-patent document 4: 3GPP TR23.799 V14.0.0 Non-patent document 5: 3GPP TR38.801 V14.0.0 Non-patent document 6: 3GPP TR38.802 V14.2.0 Non-patent document 7: 3GPP TR38.804 V14.0.0 Non-patent document 8: 3GPP TR38.912 V16.0.0 Non-patent document 9: 3GPP RP-172115 Non-patent document 10: 3GPP TS23.501 V17.3.0 Non-patent document 11: 3GPP TS38.211 V17.0.0 Non-patent document 12: 3GPP TS38.212 V17.0.0 Non-patent document 13: 3GPP TS38.213 V17.0.0 Non-patent document 14: 3GPP TS38.214 V17.0.0 Non-patent document 15: 3GPP TS38.321 V16.7.0 Non-patent document 16: 3GPP TS38.322 V16.2.0 Non-patent document 17: 3GPP TS38.323 V16.6.0 Non-patent document 18: 3GPP TS37.324 V16.3.0 Non-patent document 19: 3GPP TS38.331 V16.7.0 Non-patent document 20: 3GPP TS38.401 V16.8.0 Non-patent document 21: 3GPP TS38.413 V16.8.0 Non-patent document 22: 3GPP TS37.340 V16.8.0 Non-patent document 23: 3GPP TS38.423 V16.8.0 Non-patent document 24: 3GPP TS38.305 V16.7.0 Non-patent document 25: 3GPP TS23.273 V17.3.0 Non-patent document 26: 3GPP TR23.703 V12.0.0 Non-patent document 27: 3GPP TS23.287 V17.2.0 Non-patent document 28: 3GPP TS23.303 V17.0.0 Non-patent document 29: 3GPP TS38.340 V16.5.0 Non-patent document 30: 3GPP RP-213587 Non-patent document 31: 3GPP R1-2204656 Non-patent document 32: 3GPP R1-2203132 Non-patent document 33: 3GPP R1-2205056 Non-patent document 34: 3GPP TR38.838 V17.0.0 Summary of the invention Technical problem to be solved by the invention

[0056] In the 5G wireless access system, communications are performed for a variety of services. It is also an important issue to be able to achieve communications suitable for XR and cloud gaming services. In order to enable such communications, a communication method that takes into account the characteristics of XR traffic (such as non-integer periodicity, data generation time variation (jitter) characteristics, data volume variation characteristics, low latency characteristics, etc.) is required (non-patent document 30). In the existing communication method, the period in the periodic sending and receiving method is N milliseconds (N is a positive integer), and the periodically allocated resources are fixed. Therefore, there is the following problem: the existing communication method is not suitable for the characteristics of XR traffic, resulting in an increase in delay time and a deterioration in communication quality.

[0057] In view of the above problems, one of the objectives of the present disclosure is to obtain a base station capable of realizing a communication system suitable for communications having characteristics such as XR traffic. Technical solutions to technical problems

[0058] The base station involved in the present disclosure is a base station that can perform periodic communication to send and receive data with a communication terminal at a predetermined period. When sending downlink data to a communication terminal in periodic communication, a physical downlink control channel and a physical downlink shared channel used in a first period as a transmission period of downlink data are allocated, and the physical downlink shared channel used in the first period is changed according to the change in the amount of downlink data sent to the communication terminal, and the result of the change is notified to the communication terminal through the physical downlink control channel allocated to the first period. In addition, when receiving uplink data from a communication terminal in periodic communication, a physical downlink control channel and a physical uplink shared channel used in a second period as a transmission period of uplink data are allocated, and the physical uplink shared channel used in the second period is changed according to the change in the amount of uplink data sent by the communication terminal, and the result of the change is notified to the communication terminal through the physical downlink control channel allocated to the second period. Effects of the Invention

[0059] According to the present disclosure, it is possible to realize a communication system suitable for communications having characteristics such as XR traffic.

[0060] The objects, features, aspects and advantages of the present disclosure will become more apparent from the following detailed description and accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0061] Figure 1 This is an explanatory diagram showing the structure of a wireless frame used in a communication system using the NR method. Figure 2 This is a block diagram showing the overall structure of the NR-based communication system 210 discussed in 3GPP. Figure 3 This is a structural diagram of the DC based on the base station connected to the NG core. Figure 4 It is shown Figure 2 A block diagram of the structure of the mobile terminal 202 is shown. Figure 5 It is shown Figure 2 A block diagram of the structure of the base station 213 is shown. Figure 6 It is a block diagram showing the structure of the 5GC unit. Figure 7 This is a flowchart showing an overview of the cell search and standby actions performed by a communication terminal (UE) in a communication system using the NR mode. Figure 8 is a diagram showing an example of the structure of a cell in an NR system. Fig. 9 The following is a connection structure diagram showing an example of the connection structure of terminals in SL communication. Fig.10 The figure is a connection structure diagram showing an example of the connection structure of a base station supporting integrated access and backhaul. Fig.11 This is a diagram showing a resource allocation example when a plurality of PDSCHs and a plurality of PDCCHs are configured in one SPS period, regarding Embodiment 1. Fig.12 This is a diagram showing a resource allocation example when the number of PDCCHs and the number of PDSCHs are independently set in the SPS setting, regarding the first modification of the first embodiment. Fig.13 This is a diagram showing another resource allocation example when the number of PDCCHs and the number of PDSCHs are independently set in the SPS setting, regarding the first variant of the first embodiment. Fig.14 This is a diagram showing an example of releasing PDSCH resources set by SPS using PDCCH in Modification 2 of Implementation 1. Fig.15 This is a diagram showing another example of releasing PDSCH resources set by SPS using PDCCH, regarding Modification 2 of Embodiment 1. Fig.16 This is a diagram showing a resource allocation example when only one or more PDCCHs are configured in the SPS configuration, regarding the third modification of the first embodiment. Fig.17 This is a diagram of implementation mode 2, showing an example of resource allocation when multiple PUSCHs and multiple PDCCHs are set in the CG setting. Fig.18This is a diagram of a resource allocation example when the number of PDCCHs and the number of PUSCHs are set separately in the setting of the CG, regarding variant example 1 of implementation example 2. Fig.19 This is a diagram of other resource allocation examples when the number of PDCCHs and the number of PUSCHs are set separately in the setting of CG, regarding variant example 1 of implementation example 2. Fig. 20 This is a diagram showing an example of using PDCCH to release PUSCH resources set by CG, regarding variant example 2 of implementation example 2. Fig.21 This is a diagram of another example of using PDCCH to release PUSCH resources set by CG, regarding variant example 2 of implementation example 2. Fig. 22 This is a diagram of variant example 3 of implementation mode 2, showing an example of resource allocation when two PDCCHs are set in the CG setting. Fig.23 This is a diagram showing a resource allocation example when one or more PDSCHs are configured using the PDSCH configured in the SPS configuration, regarding Embodiment 3. Fig.24 This is a diagram showing a resource allocation example when one or more PDSCHs are configured using a plurality of PDSCHs configured in the SPS configuration, regarding the first variant of the third embodiment. Fig.25 This is a diagram showing a resource allocation example when one or more PDSCHs are released using a plurality of PDSCHs configured in the SPS configuration, regarding variant example 2 of embodiment 3. Fig.26 This is a diagram, regarding implementation mode 4, showing an example of resource allocation when using the PUSCH configured in the CG configuration to notify a scheduling request for one or more PUSCHs. Fig. 27 This is a diagram of variant example 1 of implementation mode 4, showing an example of resource allocation when a PUSCH scheduling request is notified using multiple PUSCHs set in the CG setting. Fig.28 This is a diagram of variant example 2 of implementation mode 4, showing an example of resource allocation when using multiple PUSCHs set in the CG setting to send information related to the PUSCH used by the UE for transmission. Fig.29 This is a diagram of variant example 3 of implementation mode 4, showing an example of resource allocation when using multiple PUSCHs set in the CG setting to send PUSCH release information. Fig.30This is a diagram of variation 4 of implementation mode 4, showing an example of resource allocation when sending an additional request for PUSCH using multiple PUSCHs set in the CG setting. Fig.31 This is a diagram showing an example of resource allocation in the case where an offset value is added to an SPS period every n periods set by the SPS, in relation to Embodiment 5. Fig.32 This is a diagram showing an example of resource allocation when an offset value is added to the period set by SPS in accordance with variant example 1 of implementation example 5. Fig.33 This is a diagram showing an example of resource allocation when using PDCCH to notify an offset value added to a period set by SPS, regarding variant example 2 of implementation example 5. Fig.34 This is a diagram showing another example of resource allocation when using PDCCH to notify an offset value added to the period set by SPS, regarding variant example 2 of implementation example 5. Fig.35 This is a diagram of implementation mode 6, showing an example of resource allocation when an offset value is added to the CG period every n periods set by the CG. Fig.36 This is a diagram of variant example 1 of implementation mode 6, showing an example of resource allocation when notifying a request to add an offset value to a period set by the CG. Fig.37 This is a diagram of variant example 2 of implementation example 6, showing an example of resource allocation when using PDCCH notification to add an offset value to the period set by the CG. Fig.38 This is a diagram of a sequence example of mobile processing for sending correction information for setting SPS and / or CG in RA processing, regarding embodiment 7. DETAILED DESCRIPTION

[0062] Implementation method 1. Figure 2 2 is a block diagram showing the overall structure of a communication system 210 using the NR method discussed in 3GPP. Figure 2 For explanation. The radio access network is called NG-RAN (Next Generation Radio Access Network: Next Generation Radio Access Network) 211. The communication terminal device, namely the mobile terminal device (hereinafter referred to as "mobile terminal (User Equipment: UE)") 202 can wirelessly communicate with the base station device (hereinafter referred to as "NR base station (NG-RAN NodeB: gNB)") 213, and use wireless communication to send and receive signals. NG-RAN211 is composed of one or more NR base stations 213.

[0063] Here, the "communication terminal device" includes not only mobile terminal devices such as mobile phone terminal devices that can be moved, but also non-mobile devices such as sensors. In the following description, the "communication terminal device" may be simply referred to as a "communication terminal".

[0064] The AS (Access Stratum) protocol is terminated between UE 202 and NG-RAN 211. As the AS protocol, for example, RRC (Radio Resource Control), SDAP (Service Data Adaptation Protocol), PDCP (Packet Data Convergence Protocol), RLC (Radio Link Control), MAC (Medium Access Control), and PHY (Physical layer) are used. RRC is used for the control layer (hereinafter, sometimes also referred to as C layer or C-Plane), SDAP is used for the user layer (hereinafter, sometimes also referred to as U layer or U-Plane), and PDCP, MAC, RLC, and PHY are used for both the C layer and the U layer.

[0065] The control protocol RRC (Radio Resource Control) between UE202 and NR base station 213 performs broadcast, paging, RRC connection management, etc. The states between NR base station 213 and UE202 in RRC include RRC_IDLE, RRC_CONNECTED, and RRC_INACTIVE.

[0066] In RRC_IDLE, PLMN (Public Land Mobile Network) selection, system information (System Information: SI) broadcasting, paging, cell reselection, movement, etc. are performed. In RRC_CONNECTED, the mobile terminal has an RRC connection and can send and receive data with the network. In addition, in RRC_CONNECTED, handover (Handover: HO), measurement of neighbor cells, etc. are performed. RRC_INACTIVE maintains the connection between the 5G core unit 214 and the NR base station 213, while broadcasting system information (System Information: SI), paging, cell reselection, movement, etc.

[0067] The gNB213 is connected to the 5G core unit (hereinafter sometimes referred to as the "5GC unit") 214 including the Access and Mobility Management Function (AMF), the Session Management Function (SMF), or the User Plane Function (UPF) through the NG interface. Communication of control information and / or user data is performed between the gNB213 and the 5GC unit 214. The NG interface is a general term for the N2 interface between the gNB213 and the AMF220, the N3 interface between the gNB213 and the UPF221, the N11 interface between the AMF220 and the SMF222, and the N4 interface between the UPF221 and the SMF222. One gNB213 can be connected to multiple 5GC units 214. The gNB213s are connected to each other through the Xn interface, and communication of control information and / or user data is performed between the gNB213s.

[0068] The 5GC unit 214 is an upper device, specifically, an upper node, and controls the connection between the NR base station 213 and the mobile terminal (UE) 202, allocates paging signals to one or more NR base stations (gNB) 213 and / or LTE base stations (E-UTRAN NodeB: eNB), etc. In addition, the 5GC unit 214 performs mobility control (Mobility Control) in the idle state (Idle State). The 5GC unit 214 manages the tracking area (Tracking Area) list when the mobile terminal 202 is in the idle state and in the inactive state (Inactive State) and active state (Active State). The 5GC unit 214 starts the paging protocol by sending a paging message to the cell belonging to the tracking area (Tracking Area) where the mobile terminal 202 is registered (registered).

[0069] gNB 213 can constitute one or more cells. When one gNB 213 constitutes multiple cells, each cell is configured to be able to communicate with UE 202.

[0070] gNB213 can be divided into a central unit (Central Unit: sometimes referred to as CU below) 215 and a distributed unit (Distributed Unit: sometimes referred to as DU below) 216. CU215 is configured as one in gNB213. DU216 is configured as one or more in gNB213. One DU216 constitutes one or more cells. CU215 is connected to DU216 via the F1 interface, and control information and / or user data are communicated between CU215 and DU216. The F1 interface is composed of an F1-C interface and an F1-U interface. CU215 assumes the functions of each protocol of RRC, SDAP, and PDCP, and DU216 assumes the functions of each protocol of RLC, MAC, and PHY. One or more TRPs (Transmission Reception Point: sending and receiving points) 219 are sometimes connected to DCU216. TRP219 sends and receives wireless signals with the UE.

[0071] CU215 can be divided into a C-layer CU (CU-C) 217 ​​and a U-layer CU (CU-U) 218. CU-C217 is configured as one in CU215. CU-U218 is configured as one or more in CU215. CU-C217 is connected to CU-U218 via an E1 interface, and control information is communicated between CU-C217 and CU-U218. CU-C217 is connected to DU216 via an F1-C interface, and control information is communicated between CU-C217 and DU216. CU-U218 is connected to DU216 via an F1-U interface, and user data is communicated between CU-U218 and DU216.

[0072] The 5G communication system may include the Unified Data Management (UDM) function and the Policy Control Function (PCF) described in Non-Patent Document 10 (3GPP TS23.501). UDM and / or PCF may be included in Figure 2 In the 5GC section 214.

[0073] In a 5G communication system, a location management function (LMF) described in non-patent document 24 (3GPP TS38.305) may be provided. As disclosed in non-patent document 25 (3GPP TS23.273), the LMF may be connected to a base station via an AMF.

[0074] The 5G communication system may include a non-3GPP interworking function (N3IWF) described in non-patent document 10 (3GPP TS23.501). N3IWF can use an access network (AN) as a terminal between the UE and the UE in non-3GPP access.

[0075] Figure 3 This is a diagram showing a structure based on DC (dual connection) connected to the NG core. Figure 3 In the figure, the solid line represents the connection of U-Plane, and the dotted line represents the connection of C-Plane. Figure 3 In the example, the primary base station 240-1 can be a gNB or an eNB. In addition, the secondary base station 240-2 can be a gNB or an eNB. Figure 3 In the present invention, the DC structure in which the primary base station 240-1 is a gNB and the secondary base station 240-2 is an eNB is sometimes referred to as NG-EN-DC. Figure 3In the example, the U-Plane connection between the 5GC unit 214 and the auxiliary base station 240-2 is performed via the main base station 240-1, but it can also be performed directly between the 5GC unit 214 and the auxiliary base station 240-2. Figure 3 In the present invention, the core network connected to the LTE system and the LTE-A system, namely the EPC (Evolved Packet Core), can be connected to the main base station 240-1 instead of the 5GC unit 214. The U-Plane connection between the EPC and the auxiliary base station 240-2 can be performed directly.

[0076] Figure 4 Yes means Figure 2 The structure of the mobile terminal 202 is shown in FIG. Figure 4 1 and 2. The transmission processing of the mobile terminal 202 shown in FIG. 1 is described. First, the control data from the control unit 310 and the user data from the application unit 302 are sent to the protocol processing unit 301. The control data and the user data can be buffered. The buffering of the control data and the user data can be set in the control unit 310, the application unit 302, or the protocol processing unit 301. The protocol processing unit 301 performs protocol processing such as SDAP, PDCP, RLC, MAC, etc., for example, it performs actions such as determining the transmission target base station in DC, etc., and assigning headers in each protocol. The data that has undergone protocol processing is transmitted to the encoding unit 304, and coding processing such as error correction is performed. There may also be data that is directly output from the protocol processing unit 301 to the modulation unit 305 without performing coding processing. The data encoded by the encoding unit 304 is modulated in the modulation unit 305. Precoding in MIMO can also be performed in the modulation unit 305. After the modulated data is converted into a baseband signal, it is output to the frequency conversion unit 306 and converted into a wireless transmission frequency. After that, the transmission signal is transmitted from antennas 307-1 to 307-4 to base station 213. Figure 4 , the example shows a case where the number of antennas is 4, but the number of antennas is not limited to 4.

[0077] In addition, the receiving process of the mobile terminal 202 is performed as follows. The wireless signal from the base station 213 is received through the antennas 307-1 to 307-4. The received signal is converted from the wireless receiving frequency to a baseband signal by the frequency conversion unit 306, and demodulated in the demodulation unit 308. In the demodulation unit 308, waiting calculation and multiplication processing can be performed. The demodulated data is transmitted to the decoding unit 309, and decoding processing such as error correction is performed. The decoded data is transmitted to the protocol processing unit 301, and protocol processing such as MAC, RLC, PDCP, SDAP, etc., such as removal of headers in each protocol, etc., is performed. Among the data after protocol processing, control data is transmitted to the control unit 310, and user data is transmitted to the application unit 302.

[0078] A series of processes of the mobile terminal 202 are controlled by the control unit 310. Figure 4 Although omitted in FIG. 3 , the control unit 310 is also connected to each unit 302 and 304 to 309 .

[0079] Each part of the mobile terminal 202, such as the control unit 310, the protocol processing unit 301, the encoding unit 304, and the decoding unit 309, is implemented by a processing circuit including a processor and a memory. For example, the control unit 310 is implemented by the processor executing a program that describes a series of processes of the mobile terminal 202. The program that describes a series of processes of the mobile terminal 202 is stored in the memory. Examples of memories are non-volatile or volatile semiconductor memories such as RAM (Random Access Memory), ROM (Read Only Memory), and flash memory. Each part of the mobile terminal 202, such as the control unit 310, the protocol processing unit 301, the encoding unit 304, and the decoding unit 309 can be implemented by a dedicated processing circuit such as FPGA (Field Programmable Gate Array), ASIC (Application Specific Integrated Circuit), DSP (Digital Signal Processor). In Figure 4 In the present invention, the number of antennas used by the mobile terminal 202 for sending may be the same as or different from the number of antennas used for receiving.

[0080] Figure 5 Yes means Figure 2 The structure of the base station 213 is shown in FIG. Figure 5 The sending process of the base station 213 shown is explained. The EPC communication unit 401 sends and receives data between the base station 213 and the EPC. The 5GC communication unit 412 sends and receives data between the base station 213 and the 5GC (5GC unit 214, etc.). The other base station communication units 402 send and receive data with other base stations. The EPC communication unit 401, the 5GC communication unit 412, and the other base station communication units 402 exchange information with the protocol processing unit 403 respectively. The control data from the control unit 411, and the user data and control data from the EPC communication unit 401, the 5GC communication unit 412, and the other base station communication units 402 are sent to the protocol processing unit 403. Buffering of control data and user data can be performed. The buffering of control data and user data can be set in the control unit 411, can be set in the EPC communication unit 401, can be set in the 5GC communication unit 412, and can also be set in the other base station communication units 402.

[0081] The protocol processing unit 403 performs protocol processing such as SDAP, PDCP, RLC, and MAC, for example, performs routing of transmission data in DC, assigning headers in each protocol, and other operations. The data that has undergone protocol processing is transmitted to the encoding unit 405, and coding processing such as error correction is performed. There may also be data that is directly output from the protocol processing unit 403 to the modulation unit 406 without performing coding processing. In addition, data can be sent from the protocol processing unit 403 to other base station communication units 402. For example, in DC, data sent from the 5GC communication unit 412 or the EPC communication unit 401 can be sent to other base stations, such as auxiliary base stations, via other base station communication units 402. The encoded data is modulated in the modulation unit 406. Precoding in MIMO can also be performed in the modulation unit 406. After the modulated data is converted into a baseband signal, it is output to the frequency conversion unit 407 and converted into a wireless transmission frequency. Thereafter, the transmission signal is sent to one or more mobile terminals 202 using antennas 408-1 to 408-4. In Figure 5 , the example shows a case where the number of antennas is 4, but the number of antennas is not limited to 4.

[0082] In addition, the receiving process of the base station 213 is performed as follows. The wireless signal from one or more mobile terminals 202 is received by the antennas 408-1 to 408-4. The received signal is converted from the wireless receiving frequency to a baseband signal by the frequency conversion unit 407, and demodulated in the demodulation unit 409. The demodulated data is transmitted to the decoding unit 410, and decoding processing such as error correction is performed. The decoded data is transmitted to the protocol processing unit 403, and protocol processing such as MAC, RLC, PDCP, SDAP, etc., such as the removal of headers in each protocol, etc., is performed. Among the data after the protocol processing, the control data is transmitted to the control unit 411 or the 5GC communication unit 412 or the EPC communication unit 401 or other base station communication units 402, and the user data is transmitted to the 5GC communication unit 412 or the EPC communication unit 401 or other base station communication units 402. Data sent from other base station communication units 402 can be sent to the 5GC communication unit 412 or the EPC communication unit 401. The data may be, for example, uplink data sent to the 5GC communication unit 412 or the EPC communication unit 401 via other base stations in DC.

[0083] A series of processing of the base station 213 is controlled by the control unit 411. Figure 5 Although omitted in the figure, the control unit 411 is also connected to each of the parts 401, 402, 405 to 410, and 412.

[0084] Each part of the base station 213, such as the control unit 411, the protocol processing unit 403, the 5GC communication unit 412, the EPC communication unit 401, the other base station communication unit 402, the encoding unit 405, and the decoding unit 410 are implemented by a processing circuit including a processor and a memory, or a dedicated processing circuit such as an FPGA, an ASIC, or a DSP, similar to the mobile terminal 202. Figure 5 In the present invention, the number of antennas used by the base station 213 for sending may be the same as or different from the number of antennas used for receiving.

[0085] As Figure 2 The example of the structure of CU 215 is shown, except that Figure 5 In addition to the coding unit 405, modulation unit 406, frequency conversion unit 407, antennas 408-1 to 408-4, demodulation unit 409, and decoding unit 410 shown, a configuration with a DU communication unit may be used. The DU communication unit is connected to the protocol processing unit 403. The protocol processing unit 403 in the CU 215 performs protocol processing such as PDCP and SDAP.

[0086] As Figure 2 The structure of the DU216 is shown as an example, except Figure 5 In addition to the EPC communication unit 401, other base station communication unit 402, and 5GC communication unit 412 shown, a configuration with a CU communication unit is sometimes used. The CU communication unit is connected to the protocol processing unit 403. The protocol processing unit 403 in the DU 216 performs protocol processing such as PHY, MAC, and RLC.

[0087] Figure 6 It is a block diagram showing the structure of the 5GC unit. Figure 6 The above Figure 2 The structure of the 5GC unit 214 is shown. Figure 6 Shown in Figure 2 The 5GC unit 214 shown includes the structure of AMF, the structure of SMF, and the structure of UPF. Figure 6In the example shown, the AMF may have the function of a control layer control unit 525, the SMF may have the function of a session management unit 527, and the UPF may have the functions of a user layer communication unit 523 and a data network communication unit 521. The data network communication unit 521 performs data transmission and reception between the 5GC unit 214 and the data network. The base station communication unit 522 performs data transmission and reception between the 5GC unit 214 and the base station 21 via the NG interface. User data sent from the data network is transmitted from the data network communication unit 521 to the base station communication unit 522 via the user layer communication unit 523, and is sent to one or more base stations 213. User data sent from the base station 213 is transmitted from the base station communication unit 522 to the data network communication unit 521 via the user layer communication unit 523, and is sent to the data network.

[0088] The control data transmitted from the base station 21 is transmitted from the base station communication unit 522 to the control layer control unit 525. The control layer control unit 525 may transmit the control data to the session management unit 527. The control data may be transmitted from the data network. The control data transmitted from the data network may be transmitted from the data network communication unit 521 to the session management unit 527 via the user layer communication unit 523. The session management unit 527 may transmit the control data to the control layer control unit 525.

[0089] The user plane control unit 523 includes a PDU processing unit 523-1, a mobile anchor unit 523-2, etc., and performs overall processing for the user plane (hereinafter sometimes referred to as U-Plane). The PDU processing unit 523-1 processes data packets, such as the transmission and reception of packets between the data network communication unit 521 and the transmission and reception of packets between the base station communication unit 522. The mobile anchor unit 523-2 is responsible for the connection of the data path when the UE moves.

[0090] The session management unit 527 manages the PDU session set between the UE and the UPF. The session management unit 527 includes a PDU session control unit 527-1, a UE IP address allocation unit 527-2, etc. The PDU session control unit 527-1 manages the PDU session between the mobile terminal 202 and the 5GC unit 214. The UE IP address allocation unit 527-2 allocates an IP address to the mobile terminal 202, etc.

[0091] The control layer control unit 525 includes a NAS security unit 525-1, an idle state mobility management unit 525-2, etc., and performs overall processing for the control layer (hereinafter, sometimes also referred to as C-Plane). The NAS security unit 525-1 performs security protection for NAS (Non-Access Stratum) messages, etc. The idle state mobility management unit 525-2 performs mobility management in the idle state (idle state: RRC_IDLE state, or simply called idle), generation and control of paging signals in the idle state, addition, deletion, update, retrieval, and tracking area list management of one or more mobile terminals 202 under coverage, etc.

[0092] A series of processing of the 5GC unit 214 is controlled by the control unit 526. Figure 6 Although omitted in the figure, the control unit 526 is connected to each unit 521 to 523, 525, and 527. Each part of the 5GC unit 214 is similar to the control unit 310 of the mobile terminal 202, and is implemented by, for example, a processing circuit including a processor and a memory, or a dedicated processing circuit such as an FPGA, ASIC, or DSP.

[0093] Next, an example of a cell search method in a communication system is shown. Figure 7 This is a flowchart showing an overview of the cell search and standby operation performed by a communication terminal (UE) in a communication system of the NR mode. If the communication terminal starts the cell search, in step ST601, the first synchronization signal (P-SS) and the second synchronization signal (S-SS) sent from the surrounding base stations are used to synchronize the time slot timing and the frame timing.

[0094] P-SS and S-SS are collectively referred to as synchronization signals (SS). The synchronization signal (SS) is assigned a synchronization code that corresponds to the PCI (Physical Cell Identifier) ​​assigned to each cell. Consider setting the number of PCIs to 1008. The communication terminal uses the 1008 PCIs to achieve synchronization and detects (determines) the PCI of the synchronized cell.

[0095] In step ST602, the communication terminal receives the PBCH for the next cell to acquire synchronization. The MIB (Master Information Block) containing the cell structure information is mapped to the BCCH on the PBCH. Therefore, by receiving the PBCH and obtaining the BCCH, the MIB can be obtained. The MIB information includes, for example, SFN (System Frame Number), scheduling information of SIB (System Information Block) 1, subcarrier spacing of SIB1, etc., information on DM-RS positions, etc.

[0096] In addition, the communication terminal obtains the SS block identifier through the PBCH. A portion of the bit column of the SS block identifier is included in the MIB. The remaining bit column is included in the identifier of the sequence used to generate the DM-RS attached to the PBCH. The communication terminal uses the MIB included in the PBCH and the sequence of the DM-RS attached to the PBCH to obtain the SS block identifier.

[0097] Next, in step ST603, the communication terminal measures the reception power of the SS block.

[0098] Next, in step ST604, the communication terminal selects a cell with the best reception quality from the one or more cells detected up to step ST603, for example, a cell with the highest reception power, i.e., the best cell. In addition, the communication terminal selects a beam with the best reception quality, for example, a beam with the highest reception power of an SS block, i.e., the best beam. The best beam is selected, for example, using the reception power of the SS block identified by each SS block.

[0099] Next, in step ST605, the communication terminal receives DL-SCH based on the scheduling information of SIB1 included in the MIB, and obtains SIB (System Information Block) 1 in the broadcast information BCCH. SIB1 includes information related to access to the cell, cell structure information, and scheduling information of other SIBs (SIBk: an integer of k ≥ 2). In addition, SIB1 also includes a tracking area code (Tracking Area Code: TAC).

[0100] Then in step ST606, the communication terminal compares the TAC of SIB1 received in step ST605 with the TAC part of the tracking area identity (TAI) in the tracking area list already held by the communication terminal. The tracking area list is also called the TAI list. TAI is identification information used to identify the tracking area, and is composed of MCC (Mobile Country Code), MNC (Mobile Network Code), and TAC (Tracking Area Code). MCC is the country code. MNC is the network code. TAC is the code number of the tracking area.

[0101] If the result of the comparison in step ST606 is that the TAC received in step ST605 is the same as the TAC included in the tracking area list, the communication terminal enters the standby action in the cell. If the TAC received in step ST605 is not included in the tracking area list, the communication terminal passes through the cell and requests the core network (CoreNetwork, EPC) including MME, etc. to change the tracking area to perform TAU (Tracking Area Update).

[0102] The device constituting the core network (hereinafter sometimes referred to as the "core network side device") updates the tracking area list based on the TAU request signal and the identification number (UE-ID, etc.) of the communication terminal sent from the communication terminal. The core network side device sends the updated tracking area list to the communication terminal. The communication terminal rewrites (updates) the TAC list held by the communication terminal based on the received tracking area list. Thereafter, the communication terminal enters standby action in the cell.

[0103] Next, an example of a random access method in a communication system is shown. In random access, 4-step random access and 2-step random access are used. In addition, for 4-step random access and 2-step random access, there are contention-based random access, that is, random access that may cause timing contention with other mobile terminals, and contention-free random access.

[0104] An example of a contention-based 4-step random access method is shown. As step 1, the mobile terminal sends a random access preamble to the base station. The random access preamble may be selected by the mobile terminal from a predetermined range, or may be individually allocated to the mobile terminal and notified by the base station.

[0105] As step 2, the base station sends a random access response to the mobile terminal. The random access response includes the uplink scheduling information used in step 3, the terminal identity used in the uplink transmission in step 3, and the like.

[0106] As step 3, the mobile terminal performs uplink transmission to the base station. The mobile terminal uses the information obtained in step 2 in uplink transmission. As step 4, the base station notifies the mobile terminal whether there is contention resolution. The mobile terminal notified of no conflict ends the random access process. The mobile terminal notified of a conflict starts the process again from step 1.

[0107] The contention-free 4-step random access method is different from the contention-based 4-step random access method in the following points: That is, the base station pre-allocates a random access preamble and uplink scheduling to the mobile terminal before step 1. In addition, the notification of whether or not a contention is resolved in step 4 is not required.

[0108] An example of a conflict-based 2-step random access method is shown. As step 1, the mobile terminal transmits a random access preamble and an uplink transmission to the base station. As step 2, the base station notifies the mobile terminal whether there is a conflict. The mobile terminal notified of no conflict ends the random access process. The mobile terminal notified of a conflict starts the process again from step 1.

[0109] The contention-free 2-step random access method is different from the contention-based 2-step random access method in the following respects: That is, before step 1, the base station pre-allocates a random access preamble and uplink scheduling to the mobile terminal. In addition, in step 2, the base station sends a random access response to the mobile terminal.

[0110] Figure 8 This shows an example of the structure of a cell in NR. In a cell in NR, a narrow beam is formed and its direction is changed for transmission. Figure 8 In the example shown, the base station 750 uses beam 751-1 at a certain time to transmit and receive with the mobile terminal. At other times, the base station 750 uses beam 751-2 to transmit and receive with the mobile terminal. Similarly, the base station 750 uses one or more of beams 751-3 to 751-8 to transmit and receive with the mobile terminal. Thus, the base station 750 forms a wide range of cells 752.

[0111] exist Figure 8 In FIG. 1 , an example is shown in which the number of beams used by the base station 750 is set to 8, but the number of beams may be different from 8. Figure 8 In the example shown, the number of beams used simultaneously by the base station 750 is set to one, but it can also be multiple.

[0112] The identification of beams uses the concept of QCL (Quasi-CoLocation) (refer to non-patent document 14 (3GPP TS 38.214)). That is, the beam is identified by information indicating which reference signal (e.g., SS block, CSI-RS) the beam can be considered to be the same as. This information sometimes includes the type of information about the viewpoints that can be considered to be the same beam, such as information about Doppler shift, Doppler shift spread, average delay, average delay spread, and spatial Rx parameters (refer to non-patent document 14 (3GPP TS38.214)).

[0113] In 3GPP, D2D (Device to Device) communication and V2V (Vehicle to Vehicle) communication support side links (SL) (see Non-Patent Documents 1 and 16). SL is defined by the PC5 interface.

[0114] In SL communication, in addition to broadcast, in order to support unicast and groupcast, the support of PC5-S signaling is studied (refer to non-patent document 27 (3GPP TS23.287)). For example, PC5-S signaling is implemented to establish SL, that is, a link for implementing PC5 communication. This link is implemented in the V2X layer and is also called a layer 2 link.

[0115] In addition, in SL communication, support for RRC signaling is being studied (see non-patent document 27 (3GPP TS23.287)). RRC signaling in SL communication is also called PC5 RRC signaling. For example, it is proposed to notify the capabilities of UEs between UEs performing PC5 communication, or to notify the settings of the AS layer for V2X communication using PC5 communication.

[0116] Fig. 9 An example of the connection structure of a mobile terminal in SL communication is shown in FIG. Fig. 9 In the example shown, UE 805 and UE 806 exist within the coverage area 803 of base station 801. UL / DL communication 807 is performed between base station 801 and UE 805. UL / DL communication 808 is performed between base station 801 and UE 806. SL communication 810 is performed between UE 805 and UE 806. UE 811 and UE 812 exist outside the coverage area 803. SL communication 814 is performed between UE 805 and UE 811. In addition, SL communication 816 is performed between UE 811 and UE 812.

[0117] As an example of communication between UE and NW via relay in SL communication, Fig. 9 UE 805 is shown relaying communications between UE 811 and base station 801 .

[0118] A UE that performs relaying sometimes uses Figure 4 Same structure. Use Figure 4 The relay processing in the UE is described. The relay processing of UE 805 in the communication from UE 811 to base station 801 is described. The wireless signal from UE 811 is received through antennas 307-1 to 307-4. The received signal is converted from the wireless reception frequency to a baseband signal by the frequency conversion unit 306, and demodulated in the demodulation unit 308. In the demodulation unit 308, waiting calculation and multiplication processing can be performed. The demodulated data is transmitted to the decoding unit 309, and decoding processing such as error correction is performed. The decoded data is transmitted to the protocol processing unit 301, and protocol processing such as MAC, RLC, etc. for communication with UE 811, such as removal of headers in each protocol, etc. is performed. In addition, protocol processing such as RLC, MAC, etc. for communication with base station 801, such as the addition of headers in each protocol, etc. is performed. In the protocol processing unit 301 of UE 811, protocol processing of PDCP and SDAP is sometimes performed. The data that has been processed by the protocol is transmitted to the coding unit 304, and coding processing such as error correction is performed. There may also be data that is directly output from the protocol processing unit 301 to the modulation unit 305 without being subjected to coding processing. The data that has been coded by the coding unit 304 is modulated in the modulation unit 305. Precoding in MIMO may also be performed in the modulation unit 305. After the modulated data is converted into a baseband signal, it is output to the frequency conversion unit 306 and converted into a wireless transmission frequency. Thereafter, the transmission signal is transmitted from the antennas 307-1 to 307-4 to the base station 801.

[0119] In the above content, an example of relaying of UE 805 in communication from UE 811 to base station 801 is shown, but the same processing is also used in relaying of communication from base station 801 to UE 811.

[0120] 5G base stations can support integrated access and backhaul (Integrated Access and Backhaul: IAB) (see non-patent literature 2, 20). A base station that supports IAB (hereinafter sometimes referred to as an IAB base station) is composed of a CU of a base station that acts as an IAB host providing IAB functions, namely, an IAB host CU, a DU of a base station that acts as an IAB host, namely, an IAB host DU, and an IAB node that uses a wireless interface to connect to the IAB host DU and to the UE. An F1 interface is set between the IAB node and the IAB host CU (see non-patent literature 2).

[0121] Fig.10 901 is a block diagram showing an example of the connection of an IAB base station. An IAB host CU 901 is connected to an IAB host DU 902. An IAB node 903 is connected to an IAB host DU 902 using a wireless interface. An IAB node 903 is connected to an IAB node 904 using a wireless interface. That is, multi-level connections of IAB nodes are sometimes made. A UE 905 is connected to an IAB node 904 using a wireless interface. A UE 906 is sometimes connected to an IAB node 903 using a wireless interface, and a UE 907 is sometimes connected to an IAB host 902 using a wireless interface. Multiple IAB host DUs 902 can be connected to an IAB host CU 901, multiple IAB nodes 903 can be connected to an IAB host DU 902, and multiple IAB nodes 904 can be connected to an IAB node 903.

[0122] In the connection between the IAB host DU and the IAB node and the connection between the IAB nodes, a BAP (Backhaul Adaptation Protocol) layer is set (see non-patent document 29). The BAP layer performs operations such as routing received data to the IAB host DU and / or IAB node, mapping to the RLC channel, etc. (see non-patent document 29).

[0123] As an example of the structure of the IAB host CU, the same structure as that of the CU 215 is used.

[0124] As an example of the structure of the IAB host DU, the same structure as that of DU 216 is used. In the protocol processing unit of the IAB host DU, BAP layer processing is performed, such as the addition of a BAP header in downlink data, routing to an IAB node, and removal of a BAP header in uplink data.

[0125] As an example of the structure of an IAB node, sometimes in addition to Figure 5 The structure other than the EPC communication unit 401, other base station communication unit 402, and 5GC communication unit 412 shown.

[0126] use Figure 5 , Fig.10 To illustrate the transceiver processing in the IAB node. The transceiver processing of the IAB node 903 in the communication between the IAB host CU 901 and the UE 905 is explained. In the uplink communication from the UE 905 to the IAB host CU 901, the wireless signal from the IAB node 904 is received through the antenna 408 (part or all of the antennas 408-1 to 408-4). The received signal is converted from the wireless reception frequency to a baseband signal by the frequency conversion unit 407, and demodulated in the demodulation unit 409. The demodulated data is transmitted to the decoding unit 410, and decoding processing such as error correction is performed. The decoded data is transmitted to the protocol processing unit 403, and protocol processing such as MAC, RLC, etc. for communication with the IAB node 904, such as removal of headers in each protocol, etc., is performed. In addition, routing to the IAB host DU 902 is performed using a BAP header, and protocol processing such as RLC, MAC, etc. for communication with the IAB host DU902, such as the assignment of headers in each protocol, is performed. The data that has undergone protocol processing is transmitted to the encoding unit 405, and coding processing such as error correction is performed. There may also be data that is directly output from the protocol processing unit 403 to the modulation unit 406 without performing coding processing. The encoded data is modulated in the modulation unit 406. Precoding in MIMO may also be performed in the modulation unit 406. After the modulated data is converted into a baseband signal, it is output to the frequency conversion unit 407 and converted into a wireless transmission frequency. Thereafter, the transmission signal is sent to the IAB host DU902 using antennas 408-1 to 408-4. The same processing is performed in the downlink communication from the IAB host CU901 to the UE905.

[0127] The IAB node 904 also performs the same transmission and reception processing as the IAB node 903. In the protocol processing unit 403 of the IAB node 903, as BAP layer processing, for example, the addition of a BAP header in uplink communication and routing to the IAB node 904, and the removal of a BAP header in downlink communication are performed.

[0128] In 5G wireless access systems, achieving communications suitable for XR and cloud gaming services has become an important issue. The characteristics of XR traffic in 3GPP have been studied (see non-patent document 34). As characteristics of XR traffic, for example, non-integer periodicity, data generation time variation (jitter) characteristics, data volume variation characteristics, low latency characteristics, etc. can be cited. In order to achieve communications suitable for XR or cloud gaming services, a communication method that takes into account the characteristics of such XR traffic is required.

[0129] As existing periodic communication methods, there are SPS (Semi-Persistent Scheduling) or CG (Configured Grant). They pre-allocate resources for transmission and reception, so they have the advantages of being able to obtain low latency characteristics and low power consumption characteristics. However, in SPS and CG, the period is N milliseconds (N is a positive integer). Therefore, there is a deviation between the data generation timing and the resource allocation timing, and it is necessary to wait for the transmission and reception of data until the next period. In addition, in SPS or CG, the timing of periodically allocating resources is fixed. Therefore, when the data generation time varies, transmission and reception cannot be performed at the resource allocation timing set by SPS or CG, and it is necessary to wait for the transmission and reception of data until the next period. In addition, in SPS or CG, the periodically allocated resources are fixed. Therefore, when the amount of data increases, data transmission and reception cannot be completed only by the resources allocated by SPS or CG for each period, and it is necessary to wait for the transmission and reception of data until the next period.

[0130] Therefore, simply applying the existing periodic communication method to XR traffic will increase the delay time and is not suitable for the characteristics of XR traffic. In addition, if the delay in data exceeds the required delay amount, the data is discarded, resulting in deterioration of communication quality.

[0131] In the first embodiment, a method for solving such a problem is disclosed.

[0132] In this method, one or more PDSCHs are set in the setting of SPS. However, how to set multiple PDSCHs in the setting of SPS becomes a problem. A solution to this problem is disclosed. The SPS setting performed in the existing RRC (refer to non-patent document 19) is set to correspond to the number of PDSCHs set in one cycle. The setting of SPS may also include information related to the number of PDSCHs set in one cycle. Different SPS setting identifiers can be assigned to each SPS setting. In the SPS setting, a reference SPS setting may also be determined. For example, the SPS setting of the first PDSCH set in the SPS cycle, which is the cycle when the gNB periodically sends downlink data (hereinafter referred to as DL data), may be used as a reference. Information representing the reference SPS may be included in the SPS setting. SPS setting information that is the same as the reference SPS setting information in other SPS setting information may also be omitted. The capability diagram realizes a reduction in the amount of information required to notify the UE from the gNB. As a result, multiple PDSCHs can be set in one SPS cycle.

[0133] Public activation / deactivation of SPS. The gNB notifies the UE of the activation / deactivation of SPS for each SPS setting set in the RRC. The activation / deactivation of SPS can be included in the DCI and notified using the PDCCH. As another notification method for the activation / deactivation of SPS, MAC signaling can be used for notification. A MAC CE for the activation / deactivation information of SPS can be set. The activation / deactivation information of SPS can also be set for each SPS setting set in the RRC. As information related to the activation / deactivation of SPS, there is existing information such as frequency domain resource allocation, time domain resource allocation, information indicating whether it is the first transmission or retransmission (NDI), etc. (refer to non-patent documents 12 and 13). As information related to the activation / deactivation of SPS, an SPS setting identifier set in the RRC can be included. The SPS setting identifier can be used to indicate which PDSCH's SPS setting is activated or deactivated.

[0134] As information related to the activation / deactivation of SPS, an offset can be set. The offset can span time slots. It can also span multiple time slots. The offset can be the period from the PDCCH that notifies the activation / deactivation of SPS. The offset can be set in a continuous manner in multiple PDSCHs, or in a discontinuous manner. Thus, the resource allocation of the time domain of multiple PDSCHs can be flexibly set.

[0135] Thus, multiple PDSCHs can be set in the SPS setting. Multiple PDSCHs can be used to send data from the gNB to the UE in each SPS period. In addition, since SPS can be activated / deactivated for each PDSCH, the number of PDSCHs can be flexibly set according to the amount of DL data generated in the service, for example.

[0136] Other methods of disclosing activation / deactivation of an SPS. Notifying the activation / deactivation of an SPS to activate / deactivate one or more SPS settings set in the RRC. The activation / deactivation of an SPS may be included in the DCI to be notified using the PDCCH. The activation / deactivation of an SPS may include information about the activation / deactivation of the SPS corresponding to the number of SPS settings. The SPS setting identifier set in the RRC may be associated with the information about the activation / deactivation of the SPS. The above method may be appropriately applied with respect to information related to the activation / deactivation of the SPS.

[0137] In the SPS setting, a reference SPS setting can be determined. For example, the SPS setting of the first PDSCH set in the SPS period can be used as a reference. Which SPS is used as a reference can be statically determined in advance based on standards, etc. As another method, information indicating the reference SPS can be included in the information about the activation / deactivation of the SPS. In the information related to the activation / deactivation of the SPS set by other SPS, the information that is the same as the information about the activation / deactivation of the SPS set by the reference SPS can be omitted. The capability diagram realizes a reduction in the amount of information required to notify the UE from the gNB.

[0138] A new RNTI (Radio Network Temporary Identifier) ​​can be set for receiving the PDCCH containing activation / deactivation of SPS when multiple PDSCHs are set in the SPS setting. The UE uses this RNTI to receive the PDCCH. As another method, CS-RNTI (Configured Scheduling RNTI) can also be used. The CS-RNTI can be notified to the UE in advance from the gNB. By using CS-RNTI, the existing RNTI can be used, so the flow chart can be simplified.

[0139] Thus, multiple PDSCHs can be set by activating / deactivating one SPS. Multiple PDSCHs can be used to send data from the gNB to the UE in each SPS period. Since only one SPS needs to be activated / deactivated, the processing of the gNB and the UE can be simplified. Misoperation can be reduced.

[0140] Other setting methods for multiple PDSCHs are disclosed. The gNB uses RRC to set one or more PDSCHs in one SPS setting for the UE. In one SPS setting, SPS setting information corresponding to the number of PDSCHs set in one period is set. As SPS setting information set in the RRC, in addition to the SPS setting information set in the existing RRC, information related to the setting of the PDSCH may also be included. One or more PDSCHs set by the SPS may be numbered. As information related to the setting of the PDSCH, the number of PDSCHs and / or the number of the PDSCH may be included in the SPS setting information. The number of the PDSCH may be associated with the SPS setting information corresponding to the PDSCH.

[0141] A reference PDSCH can be determined. For example, the first PDSCH set in the SPS period can be used as the reference. Which PDSCH is used as the reference can be statically determined in advance based on standards, etc. As another method, information indicating the reference PDSCH can be included in the SPS setting. SPS setting information that is the same as the SPS setting information of the reference PDSCH in the SPS setting information of other PDSCHs can also be omitted. The capability diagram realizes a reduction in the amount of information required to notify the UE from the gNB. As a result, multiple PDSCHs can be set within one SPS period.

[0142] An activation / deactivation method of an SPS is disclosed. The activation / deactivation of an SPS is notified to activate / deactivate an SPS set in the RRC. The activation / deactivation of the SPS may be included in the DCI for notification using the PDCCH. As another notification method of the activation / deactivation of the SPS, MAC signaling may be used for notification. A MAC CE of the activation / deactivation information of the SPS may be set. The activation / deactivation of an SPS may include information on the activation / deactivation of the SPS corresponding to the number of PDSCHs. The PDSCH number set in the RRC may be associated with the activation / deactivation information of the SPS of the PDSCH. The above method may be appropriately applied to information related to the activation / deactivation of the SPS.

[0143] A reference PDSCH in the PDSCH may be determined. For example, the first PDSCH set in the SPS period may be used as a reference. Information indicating the reference PDSCH may be included in information related to activation / deactivation of the SPS. In the information about activation / deactivation of the SPS of other PDSCHs, information that is the same as the information about activation / deactivation of the SPS of the reference PDSCH may be omitted. The capability diagram enables reduction in the amount of information required to notify the UE from the gNB.

[0144] As information about the activation / deactivation of SPS for PDSCH, an offset can be set. The offset can span time slots. It can also span multiple time slots. The offset can be the period from the PDCCH that notifies the activation / deactivation of SPS. The offset can be set in a continuous manner in multiple PDSCHs, or in a discontinuous manner. Thus, the resource allocation of the time domain of multiple PDSCHs can be flexibly set.

[0145] A new RNTI can be set for receiving a PDCCH containing activation / deactivation of an SPS for multiple PDSCHs. The UE uses this RNTI to receive the PDCCH. As another method, CS-RNTI can also be used. The CS-RNTI can be notified to the UE in advance from the gNB. By using CS-RNTI, the existing RNTI can be used, thereby simplifying the processing.

[0146] Thus, multiple PDSCHs can be set by activating / deactivating one SPS. Multiple PDSCHs can be used to send data from the gNB to the UE in each SPS period. Since only one SPS needs to be activated / deactivated, the processing of the gNB and the UE can be simplified. This can reduce malfunctions.

[0147] Other methods for disclosing the activation / deactivation of SPS. The gNB notifies the UE of the activation / deactivation of SPS for each PDSCH set in the SPS period. The activation / deactivation of SPS can be included in the DCI and notified using the PDCCH. Information about the activation / deactivation of SPS can be notified for each PDSCH.

[0148] As a result, multiple PDSCHs can be used in each SPS period to send data from the gNB to the UE. In addition, since SPS activation / deactivation can be performed at different timings for each PDSCH, the number of PDSCHs for SPS settings can be flexibly set according to the generation timing of DL data, for example.

[0149] A HARQ process number is assigned to each PDSCH. The HARQ process number can be derived using the SPS setting identifier. The HARQ process number can be set as a function of the SPS setting identifier. The HARQ process number can be derived using the PDSCH number. The HARQ process number can be set as a function of the PDSCH number. The HARQ process number can be derived using the time slot number to which the PDSCH is allocated. The HARQ process number can be set as a function of the time slot number to which the PDSCH is allocated. By adopting such a method, HARQ can be performed on each PDSCH.

[0150] Other methods of disclosing HARQ process numbers. A HARQ process number can be assigned to one or more PDSCHs in an SPS period. The HARQ process number can be derived using a benchmark SPS setting identifier. The HARQ process number can be set as a function of the benchmark SPS setting identifier. The HARQ process number can be derived using the time slot number set by the allocation benchmark SPS. The HARQ process number can be set as a function of the time slot number set by the allocation benchmark SPS. The HARQ process number can be derived using the PDSCH number. The HARQ process number can be set as a function of the PDSCH number. The HARQ process number can be derived using the time slot number of the allocation benchmark PDSCH. The HARQ process number can be set as a function of the time slot number of the allocation benchmark PDSCH. By adopting this method, HARQ can be performed on one or more PDSCHs in an SPS period. There is no need to perform multiple HARQ processes as for each PDSCH. In addition, the HARQ processing can be simplified.

[0151] Ack / Nack PUCCH can also be set for each PDSCH. Set the Ack / Nack PUCCH corresponding to the number of PDSCHs. Information related to the Ack / Nack PUCCH can also be included in the SPS setting information. Thus, Ack / Nack for each PDSCH can be set. In addition, Ack / Nack can be sent as early as possible from the received PDSCH without waiting for the reception of multiple PDSCHs.

[0152] Another configuration method of the PUCCH for Ack / Nack is disclosed. For one or more PDSCHs configured in the SPS period, one PUCCH for Ack / Nack may be configured. Information related to the PUCCH for Ack / Nack may also be included in the SPS configuration information.

[0153] The one PUCCH may include the Ack / Nack information of each PDSCH set in the SPS period. Ack / Nack information of one or more PDSCHs is sent using one PUCCH. In this way, the resources of PUCCH can be reduced. The resource utilization efficiency of UL can be improved. As another method, the one PUCCH may be used to send information of one or more PDSCHs that become Ack. The Ack information of one or more PDSCHs that become Ack may be included and sent using the one PUCCH. As another method, the one PUCCH may be used to send information of one or more PDSCHs that become Nack. The Nack information of one or more PDSCHs that become Nack may be included and sent using the one PUCCH. In this way, the resources of PUCCH can be further reduced. The resource utilization efficiency of UL can be improved.

[0154] A priority can be set for which PDSCH's Ack / Nack information is included. Alternatively, the amount of information can be reduced through a codebook. In this way, the amount of information sent using the PUCCH can be reduced.

[0155] An Ack / Nack message can be derived according to the reception status of one or more PDSCHs set in the SPS period. For example, when all PDSCHs are received, it is set to Ack, otherwise it is set to Nack. A PUCCH can contain an derived Ack / Nack message. A PUCCH is used to send an Ack / Nack message. In this way, the resources of PUCCH can be reduced. The resource utilization efficiency of UL can be improved.

[0156] One or more PDCCHs are set in the SPS period. In the SPS period, a PDCCH is set for each PDSCH. The number of PDSCHs and the number of PDCCHs can be made the same. One or more PDSCHs are set in the SPS period, and the same number of PDCCHs are set.

[0157] One or more CORESETs and search spaces (SS: Search Space) can be set as the settings of one or more PDCCHs. One or more CORESETs and search spaces can be a group of CORESETs and a group of search spaces. A list of CORESETs set in an SPS period can be set. A list of search spaces set in an SPS period can be set. The setting information of CORESET includes the CORESET identifier, frequency domain resources, symbol period, mapping information between CCE (Control Channel Element: control channel element) and REG (Resource Element Group: resource element group), TCI (Transmission Configuration Indication: transmission configuration indication) status related information, etc. It can also be a combination of these information. The setting information of the search space includes the search space identifier, the corresponding CORESET identifier, the search space period, the offset, the time slot period for the search space, the number of monitor symbols, the number of candidates, the DCI format information, etc. It can also be a combination of them.

[0158] In the configuration of one or more PDCCHs, part or all of the configuration information of the CORESET of each PDCCH may be the same. Similarly, part or all of the configuration information of the search space of each PDCCH may be the same. For example, the identifier of the CORESET may be different, but the other configuration information may be the same. For example, the identifier and start timing (offset) of the search space may be different, but the other configuration information may be the same. The same configuration information may also be omitted.

[0159] A reference PDCCH can be determined. For example, the first PDCCH set in the SPS period can be used as the reference. Which PDCCH is used as the reference can be statically determined in advance based on standards, etc. As another method, information indicating the reference PDCCH can be included in the SPS setting. Information that is the same as the reference PDCCH setting information in the setting information of other PDCCHs, such as the setting information of CORESET or the setting information of the search space, can be omitted. The capability diagram realizes a reduction in the amount of information required to notify the UE from the gNB.

[0160] The gNB notifies the UE of the setting of one or more PDCCHs in the SPS period. RRC signaling can be used. A new RRC message can also be set for the setting. Misidentification with other PDCCH settings can be reduced. Alternatively, an existing RRC message can be used. For example, the PDCCH-config can include the setting. For example, the period of the search space can be set to the period of the SPS. The PDCCH-config can set one or more search spaces in the SPS period.

[0161] As another notification method for one or more PDCCH settings in the SPS period, the setting can be included in the SPS-config of the RRC message. By including it in the SPS-config, it can be set simultaneously with other SPS settings, such as the PDSCH setting. By receiving the SPS-config, the UE can receive the PDSCH and PDCCH settings in the SPS period, which can reduce malfunctions.

[0162] A part of the setting information of one or more PDCCHs can be set using PDCCH-config, and the remaining part can be notified through SPS setting. Flexible setting is possible.

[0163] In the setting of one or more PDCCHs, the period of the search space can be set to the period of the search space set in one SPS period. For example, in the case of setting it to 1 time slot period, the search space is set in 1 time slot period for each SPS period. In the setting of one or more PDCCHs, the number of search spaces set in one SPS period can be set. It can also be set to be the same as the number of PDCCHs set in the SPS period. Thus, the number of search spaces set in one SPS period can be limited.

[0164] The SPS setting may also include setting information for setting the search space period to the search space period set in one SPS period. The gNB sends the information included in the SPS setting to the UE. For example, it may be sent in the SPS-config of the RRC message. The UE receives the search space setting information such as the search space period information set in one SPS period, the number of search spaces, etc., so that it can monitor the PDCCH set in one SPS period.

[0165] In the setting of one or more PDCCHs, the CORESET and / or search space may be set for each PDSCH set in the SPS period. The PDCCH may be used to implement scheduling corrections for the PDSCH. The CORESET and / or search space may be set before the resources of the PDSCH. The CORESET and / or search space may be set before the resources of the PDSCH. The CORESET and / or search space may be set continuously with the PDSCH. After receiving the PDCCH, the PDSCH may be received immediately.

[0166] The gNB can include the settings of one or more PDCCHs set in the SPS in the DCI and send it to the UE. For example, it can be included in the DCI for activation / deactivation of the SPS. PDCCH can be used to send the DCI. Dynamic notification can be performed. The settings of one or more PDCCHs set in the SPS can be notified using MAC signaling. A MAC CE including the settings of one or more PDCCHs set in the SPS can be set. It can be sent using PDSCH. Even if the PDCCH is not sent, the settings of one or more PDCCHs set in the SPS can be notified. Offset information can be set from the PDCCH that sends the settings of one or more PDCCHs set in the SPS to the one or more PDCCHs set in the SPS. The offset information can be included in the settings of the SPS. RRC signaling and PDCCH can be combined to notify the setting information of one or more PDCCHs. As a result, settings can be made more dynamically and flexibly.

[0167] A new RNTI can be set for receiving one or more PDCCHs set in the SPS period. The UE uses the RNTI to receive the PDCCH. As another method, C-RNTI (Cell RNTI: cell RNTI) can also be used. CS-RNTI (Configured Scheduling RNTI: configured scheduling RNTI) can be used. By using CS-RNTI or CS-RNTI, the existing RNTI can be used, thereby simplifying the processing.

[0168] The scheduling modification information of the PDSCH is notified by using one or more PDCCHs configured in the SPS period. The configuration information of the PDSCH other than the configuration information transmitted by RRC or DCI can be notified by using each PDCCH.

[0169] Fig.11 This figure shows an example of resource allocation when multiple PDSCHs and multiple PDCCHs are set in one SPS period. PDCCH shows the situation set for each PDSCH. The shaded quadrilateral represents the PDCCH, and the white quadrilateral represents the PDSCH. The horizontal axis represents the time domain, and the vertical axis represents the frequency domain. The SPS is set from the gNB to the UE using RRC signaling, and the activation / deactivation of the SPS is notified using the PDCCH. Multiple PDCCHs are set in each SPS period, and scheduling correction information for the PDSCH is sent using each PDCCH.

[0170] exist Fig.11 In the IEEE 802.11a / b / s protocol, multiple PDSCHs are allocated continuously, but can also be allocated non-contiguously.

[0171] Thus, multiple PDSCHs can be set in the SPS setting, and the PDCCH corresponding to each PDSCH can be set. Therefore, the scheduling of each PDSCH can be dynamically corrected. By using the PDCCH to correct the scheduling of each PDSCH, the timing and amount of data generation can be changed, and the settings of the resources allocated to each PDSCH, the MSC (Mobile Switching Centre), etc. can be corrected to more appropriate settings. The ability diagram can achieve a reduction in delay time and an improvement in resource utilization efficiency.

[0172] In the above, the case of using one or more PDSCHs to send data is shown. As another method, the amount of resources of PDSCH can be increased. For example, multiple time slots can be allocated to one PDSCH. The amount of resources of PDSCH can be set. Thus, one PDSCH can be used to send data. In the setting of SPS, a PDSCH setting can be made. The amount of resources of PDSCH can be set. The amount of resources of PDSCH can be set in RRC. Alternatively, it can also be set using MAC signaling. Alternatively, it can be included in DCI and set using PDCCH. Thus, the PDSCH set by SPS can be set to 1, which can simplify the processing.

[0173] Embodiment 1 Variation 1 Disclosed is another method for solving the problem disclosed in Embodiment 1. In the setting of SPS, one or more PDSCHs are set, and one or more PDCCHs are set. The number of PDSCHs and the number of PDCCHs can be set separately.

[0174] The method of setting one or more PDSCHs in the SPS period can appropriately apply the method disclosed in Embodiment 1. The method of setting one or more PDCCHs in the SPS period can appropriately apply the method disclosed in Embodiment 1. Using these methods, the number of PDSCHs and the number of PDCCHs can be set separately.

[0175] Scheduling modification information of one or more PDSCHs is notified by each PDCCH configured in one SPS cycle. Configuration information of PDSCH other than configuration information transmitted by RRC or DCI may be notified by each PDCCH.

[0176] A method for notifying scheduling correction information of multiple PDSCHs using one PDCCH is disclosed. Multiple search spaces corresponding to each PDSCH are set. A UE receives each search space corresponding to each PDSCH to receive DCI including scheduling correction information of each PDSCH. In this way, by setting multiple search spaces corresponding to each PDSCH, an existing search space setting method can be used. The complication of SPS processing can be avoided.

[0177] Disclosed is another method for notifying scheduling correction information of multiple PDSCHs using one PDCCH. A search space corresponding to multiple PDSCHs is set. The UE receives each search space corresponding to each PDSCH to receive DCI including scheduling correction information of each PDSCH. In this way, by setting a search space corresponding to each PDSCH, the existing search space setting method can be used. The complication of SPS processing can be avoided.

[0178] The search space setting information may also be included in the SPS setting information. It may also be included in the PDCCH setting information set in the SPS period. The search space setting information may be sent from the gNB to the UE using RRC signaling. The search space setting information may be included in the DCI including the activation / deactivation of the SPS and sent from the gNB to the UE using the PDCCH. As these methods, the method disclosed in Implementation 1 may be appropriately applied.

[0179] The PDSCH may be numbered to identify one or more PDSCHs configured by the SPS. In the configuration of one or more PDSCHs, the configuration information of the PDSCH may be associated with the number of the PDSCH. The method disclosed in Embodiment 1 may be appropriately applied.

[0180] In the method of notifying the scheduling correction information of multiple PDSCHs using one PDCCH, in order to determine which PDSCH the scheduling correction information is for, the PDSCH number disclosed above can be used. In this way, it is possible to clearly indicate which PDSCH the scheduling correction information is for. This can reduce erroneous operations between the gNB and the UE.

[0181] Fig.12 This is a diagram showing an example of resource allocation when the number of PDCCHs and the number of PDSCHs are set separately in the SPS setting. One PDCCH is set in the SPS setting, and five PDSCHs are set. One PDCCH is set in each SPS period, and the scheduling correction information of the corresponding PDSCH is sent using the PDCCH.

[0182] exist Fig.12 In the IEEE 802.11a / b / s protocol, multiple PDSCHs are allocated continuously, but can also be allocated non-contiguously.

[0183] The number of PDCCHs set in one SPS cycle may be multiple. The setting information of the PDCCH set in one SPS cycle may include the number of PDCCHs. The number of PDCCHs may be set within the range of the number of PDSCHs set in one SPS cycle. As a setting method for multiple PDCCHs, the PDCCH may be set periodically. The setting method of the CORESET or search space disclosed in Implementation Example 1 may be appropriately applied. Multiple PDCCHs can be set, and the scheduling of the PDSCH can be modified using the PDCCH suitable for the timing of DL data generation and the number of data amounts.

[0184] As another method for setting the PDCCH set in one SPS period, the PDCCH set in one SPS period can be set using bit mapping. It can also be set as a bit mapping of the number of bits corresponding to the number of PDSCHs set by the SPS. As the setting information of the PDCCH, the search space can also be set using bit mapping. The search space set in one SPS period may not be periodic, and flexible PDCCH setting can be performed.

[0185] Fig.13 This is a diagram showing an example of resource allocation when the number of PDCCHs and the number of PDSCHs are set separately in the SPS setting. Two PDCCHs are set in the SPS setting, and five PDSCHs are set. Two PDCCHs are set in each SPS cycle, and the first PDCCH is used to send scheduling correction information for the first to third PDSCHs, and the second PDCCH is used to send scheduling correction information for the fourth to fifth PDSCHs.

[0186] exist Fig.13 In the IEEE 802.11a / b / s protocol, multiple PDSCHs are allocated continuously, but can also be allocated non-contiguously.

[0187] Thus, multiple PDSCHs can be set in the setting of SPS, and the PDCCH corresponding to each PDSCH can be set. By setting the number of PDSCHs and the number of PDCCHs separately, flexible PDCCH settings can be performed. In addition, since the resources of PDCCH can be reduced, the efficiency of resource use can be improved. In addition, since the PDCCH reception processing of the UE can be reduced, low power consumption can be achieved. In addition, similar to the effect of implementation mode 1, the scheduling of each PDSCH can be dynamically corrected. By using PDCCH to correct the scheduling of each PDSCH, the timing and amount of data generation can be changed, and the settings of resources allocated to each PDSCH, MSC, etc. can be corrected to more suitable settings. The delay time is reduced and the efficiency of resource use is improved.

[0188] Embodiment 1 Variation 2 Other methods for solving the problem disclosed in Implementation 1 are disclosed. In the setting of SPS, one or more PDSCHs are set, and one or more PDCCHs are set. The number of PDSCHs and the number of PDCCHs can be set separately. The release information of the PDSCH set by the SPS is included in the PDCCH set for each SPS period. The gNB can use the PDCCH to notify the UE of the release information of one or more PDSCHs set by the SPS.

[0189] In the DCI sent using one or more PDCCHs set for each SPS period, release information of one or more PDSCHs set by the SPS may be included. In the case where the release information is included in the DCI, a new DCI format may also be set. As another method, an existing DCI format may be used. For example, DCI format 2_1 (see non-patent document 12) may be used. By using an existing DCI format, processing complexity may be avoided.

[0190] In order to receive DCI including release information, a new RNTI can be set. For example, it can be set to the RNTI for receiving the PDCCH disclosed in Implementation Example 1 or Implementation Example 1 Variation 1. By setting it to an RNTI specific to the PDCCH in the SPS setting, malfunctions can be reduced. As another method, an existing RNTI can be used (refer to non-patent document 15). For example, it can also be set to C-RNTI or CS-RNTI. For example, INT-RNTI (Interruption RNTI) can be used. When using DCI format 2_1, INT-RNTI can be used. By using an existing RNTI, processing complications can be avoided.

[0191] One PDCCH may be used to notify the release information of one or more PDSCHs. Information for determining which PDSCH to release may be set for notification. The PDSCH set by the SPS is assigned a number as information for determining the PDSCH to release the PDSCH number. As a method for notifying the release information of the PDSCH, the method of notifying the scheduling correction information of one or more PDSCHs using one PDCCH disclosed in variant 1 of implementation example 1 may be appropriately applied. Instead of the scheduling correction information of the PDSCH, or as the scheduling correction information of the PDSCH, it may be used as the release information of the PDSCH. The UE can identify the PDSCH to be released by receiving one or more PDCCHs in each SPS period sent from the gNB. The UE can release one or more PDSCHs set by the SPS.

[0192] The gNB does not use the PDSCH notified by the release information to send data to the UE. The UE may not receive the PDSCH notified by the release information. Both the gNB and the UE can simplify the processing. For example, the gNB releases the PDSCH according to the generation timing or data volume of the DL data, so that the PDSCH suitable for the generation timing or data volume of the DL data can be used. The gNB can use the resources of the released PDSCH for other communications. For example, resources can be allocated to the PDSCH of other UEs. In this way, the efficiency of wireless resource utilization can be improved.

[0193] As a release method, the PDSCH of the SPS period notifying the PDCCH including the release information is released. Thus, for example, it is possible to set the PDSCH to be released for each SPS period. The PDSCH can be released for each SPS period according to the generation timing and data amount of DL data.

[0194] As another release method, the PDSCH after the SPS period in which the PDCCH including the release information is notified is released. For example, the release information of the fourth and fifth PDSCHs is sent using the PDCCH of the second SPS period. In this case, the fourth and fifth PDSCHs of the SPS periods after the second are released. Thus, for example, it is not necessary to release the PDSCH in each SPS period, so the amount of information required for the notification can be reduced.

[0195] As another release method, the PDSCH of the specified period starting from the SPS period notifying the PDCCH including the release information is released. The unit of the period may be time, time slot, subframe, radio frame, etc. It may also be the number of SPS periods instead of a period. The gNB may send the release period information to the UE. It may also be sent together with the release information. For example, the release information and release period information of the fourth and fifth PDSCHs are sent using the PDCCH of the second SPS period. For example, the release period information is set to 5SPS periods. In this case, the fourth and fifth PDSCHs from the second to the sixth SPS periods are released. Thus, for example, the release of the PDSCH can be limited to a specified period. For example, a flexible setting can be made that takes into account the generation trend of DL data.

[0196] The release can be set only for the SPS period sent using PDCCH, after that, or for a specified period. The gNB can send information about which one it is to the UE. It can also be sent together with the release information. For example, it can also be set using the release period information. For example, in the case of the SPS period sent only using PDCCH, 1 is set as the release period information. In the case of a specified period, the number of SPS periods is set as the release period information. In the case of all after the SPS period sent using PDCCH, the release period information is set to a predetermined value. For example, it can be set to 0. In this way, it is possible to set what kind of release method is set. Flexible settings suitable for communication modes for DL ​​data can be made.

[0197] Fig.141 is a diagram showing an example of releasing resources of a PDSCH set by an SPS using a PDCCH. In the setting of the SPS, the number of PDCCHs and the number of PDSCHs are set separately. In the setting of the SPS, one PDCCH is set, and multiple PDSCHs are set. One PDCCH is set for each SPS period. Information on releasing the PDSCH using the PDCCH and information indicating which PDSCH is released are sent. The UE can identify which PDSCH is released by receiving the PDCCH. The UE does not receive the released PDSCH.

[0198] The number of PDCCHs may be multiple. As a setting method for multiple PDCCHs, PDCCHs may be set periodically. The setting may be performed within the range of setting PDSCH. Alternatively, the PDCCH may be sent within the range of setting PDSCH. As another setting method, PDCCH may be set by bit mapping. The setting may be performed within the range of setting PDSCH.

[0199] Fig.15 1 is a diagram showing another example of using PDCCH to release resources of PDSCH set by SPS. In the setting of SPS, two PDCCHs are set for each SPS period. Information on releasing multiple PDSCHs set by SPS and information indicating which PDSCH is released are sent using PDCCH. Information on releasing the PDSCH before the (n+1)th PDCCH is sent and information indicating which PDSCH is released are sent using the nth PDCCH. Fig.15 In the example, the first PDCCH is used to send the release information of the first to third PDSCHs and the information indicating which PDSCH is released. The second PDCCH is used to send the scheduling correction information of the fourth to fifth PDSCHs. The UE can identify which PDSCH is released by receiving the PDCCH. The UE does not receive the released PDSCH.

[0200] The release information of one or more PDSCHs set by the SPS may be included in the scheduling correction information of one or more PDSCHs set by the SPS disclosed in variant 1 of implementation mode 1. The scheduling correction information of one or more PDSCHs set by the SPS may include information for releasing the scheduling of one or more PDSCHs set by the SPS. The scheduling correction information of one or more PDSCHs set by the SPS may include information for canceling the scheduling of one or more PDSCHs set by the SPS.

[0201] As another method, the scheduling correction information of one or more PDSCHs set by the SPS disclosed in variant 1 of implementation mode 1 can be used to release (or cancel) other PDSCHs except the PDSCH to be scheduled. As scheduling correction information, information indicating the execution of the PDSCH allocation set in the SPS setting can be set. As scheduling correction information, information indicating whether to execute the PDSCH allocation set in the SPS setting can be set. Scheduling correction information of one or more PDSCHs set by the SPS can be used to release (or cancel) a PDSCH that does not show the information for executing the PDSCH allocation. As a result, the UE only needs to receive the scheduling correction information, which can simplify the processing at the UE.

[0202] Thus, multiple PDSCHs can be set in the setting of SPS, and the PDCCH corresponding to each PDSCH can be set. By setting the number of PDSCHs and the number of PDCCHs separately, flexible PDCCH settings can be performed. In addition, since PDCCH resources can be reduced, resource utilization efficiency can be improved. In addition, since the PDCCH reception processing of the UE can be reduced, low power consumption can be achieved. In addition, since each PDSCH can be released dynamically, even if multiple PDSCH settings are performed in the setting of SPS, it can be corrected to a setting suitable for changes in data generation timing and data volume. The ability to achieve a reduction in delay time and an improvement in resource utilization efficiency.

[0203] Embodiment 1 Variation 3 Disclosed is another method for solving the problem disclosed in Implementation Example 1. One or more PDCCHs are set in the SPS setting. In the SPS setting, the PDSCH is not set. The method for setting one or more PDCCHs in the SPS period can appropriately apply the above-disclosed method. The notification method of the setting of the PDCCH from the gNB to the UE can appropriately apply the above-disclosed method.

[0204] The PDSCH is scheduled using one or more PDCCHs set for each SPS period. The PDCCH is used to notify the scheduling information of the PDSCH. One PDCCH can be used to notify the scheduling information of one or more PDSCHs. The notification method can appropriately apply the method disclosed in Implementation Example 1, Variation Example 1, of notifying the scheduling correction information of one or more PDSCHs using one PDCCH. The scheduling information can be set to replace the scheduling correction information.

[0205] Fig.16This is a diagram showing an example of resource allocation when only one or more PDCCHs are set in the SPS setting. Two PDCCHs are set for each SPS period. PDSCH is not set in the SPS setting. SPS is set from the gNB to the UE using RRC signaling, and the activation / deactivation of SPS is notified using PDCCH. The scheduling information of PDSCH is notified using the PDCCH set for each SPS period. The scheduling information of PDSCH before sending the n+1th PDCCH can be sent using the nth PDCCH. Fig.16 In the example of , in the initial period, one PDSCH is scheduled using the first PDCCH, and two PDSCHs are scheduled using the second PDCCH. In the second period, two PDSCHs are scheduled using the first PDCCH, and one PDSCH is scheduled using the second PDCCH. The UE can receive the scheduling information of the PDSCH by receiving the PDCCH.

[0206] In this way, one or more PDCCHs can be set in the SPS setting. Since PDCCH is used to schedule PDSCH in each SPS period, the number of PDSCHs to be scheduled can be set according to the data generation timing and data volume changes. Therefore, the delay time can be reduced and the resource utilization efficiency can be improved.

[0207] Implementation method 2. Other methods for solving the problem disclosed in Implementation Example 1 are disclosed. One or more PUSCHs are set in the setting of the CG. One or more PDCCHs are set in the setting of the CG. In the CG period, the PDCCH can be set according to each PUSCH. The number of PDSCHs and the number of PDCCHs can be made the same. One or more PUSCHs are set in the CG period, and the same number of PDCCHs are set, and the above-mentioned CG period is a period when the UE periodically allocates resources for sending uplink data (hereinafter referred to as UL data).

[0208] One or more PUSCHs are set in the CG setting. However, how to set multiple PUSCHs in the CG setting becomes a problem. A solution to this problem is disclosed. The CG setting set in the existing RRC (refer to non-patent document 19) is set to correspond to the number of PUSCHs set in one cycle. Different CG setting identifiers can be assigned in each setting. In the CG setting, a benchmark CG setting can be determined. For example, the CG setting of the first PUSCH set in the CG cycle can be used as a benchmark. Information representing the benchmark CG can be included in the CG setting. CG setting information that is the same as the benchmark CG setting information in other CG setting information can also be omitted. The capability diagram realizes a reduction in the amount of information required to notify the UE from the gNB. As a result, multiple PUSCHs can be set in one CG cycle.

[0209] Public activation / deactivation of CG. gNB can use RRC signaling to notify UE of the activation / deactivation of CG. gNB can activate and deactivate CG by setting and releasing the CG settings made to UE using RRC signaling. Activate / deactivate CG for each CG setting set in RRC.

[0210] As another method, the gNB can notify the UE of the activation / deactivation of the CG for each CG setting set in the RRC. The activation / deactivation of the CG can be included in the DCI and notified using the PDCCH. As information related to the activation / deactivation of the CG, there is existing information such as frequency domain resource allocation, time domain resource allocation, information indicating whether it is the first transmission or retransmission (NDI), etc. (refer to non-patent documents 12 and 13). As information related to the activation / deactivation of the CG, a CG setting identifier set in the RRC may also be included. The CG setting identifier can be used to indicate which PUSCH CG setting is activated or deactivated.

[0211] Regarding the method of activating / deactivating CG, the method of activating / deactivating SPS disclosed in Implementation 1 can be appropriately applied. CG can be set to replace SPS. PUSCH set by CG can be set to replace PDSCH set by SPS. The same effect can be obtained in CG.

[0212] Other configuration methods for multiple PUSCHs are disclosed. The gNB uses RRC to configure one or more PUSCHs for the UE in one CG configuration. In one CG configuration, the number of configurations corresponds to the PUSCHs configured in the CG cycle. In addition to the CG configuration information configured in the existing RRC, information related to the configuration of the PUSCH may be included as CG configuration information configured in the RRC. One or more PUSCHs configured in the CG may be numbered. As information related to the configuration of the PUSCH, the number of PUSCHs and / or the number of the PUSCHs may be included in the CG configuration information. The PUSCH number may be associated with the CG configuration information corresponding to the PUSCH.

[0213] A reference PUSCH can be determined. For example, the first PUSCH set in the CG cycle can be used as the reference. Which PUSCH is used as the reference can be statically determined in advance based on standards, etc. As another method, information indicating the reference PUSCH can be included in the CG setting. CG setting information that is the same as the CG setting information of the reference PUSCH in the CG setting information of other PUSCHs can also be omitted. The capability diagram realizes a reduction in the amount of information required to notify the UE from the gNB. As a result, multiple PUSCHs can be set within one CG cycle.

[0214] The activation / deactivation of CG can appropriately apply the above-disclosed method. The gNB can use the CG setting and release performed on the UE by RRC signaling as the activation and deactivation of CG. Alternatively, for each CG setting set in RRC, the gNB can include the activation / deactivation of CG in the DCI and notify the UE using PDCCH.

[0215] Regarding the method of activating / deactivating CG, the method of activating / deactivating SPS disclosed in Implementation 1 can be appropriately applied. In this method, CG can be set to replace SPS. PUSCH set by CG can be set to replace PDSCH set by SPS. The same effect can be obtained in CG.

[0216] A HARQ process number is assigned to each PUSCH. The HARQ process number can be derived using a CG setting identifier. The HARQ process number can be set as a function of a CG setting identifier. The HARQ process number can be derived using a PUSCH number. The HARQ process number can be set as a function of a PUSCH number. The HARQ process number can be derived using a time slot number to which the PUSCH is allocated. The HARQ process number can be set as a function of a time slot number to which the PUSCH is allocated. By adopting such a method, HARQ can be performed on each PUSCH.

[0217] Other methods of disclosing HARQ process numbers. One or more PUSCHs in a CG period can be used to assign a HARQ process number. The HARQ process number can be derived using a benchmark CG setting identifier. The HARQ process number can be set as a function of the benchmark CG setting identifier. The HARQ process number can be derived using the time slot number set by the allocation benchmark CG. The HARQ process number can be set as a function of the time slot number set by the allocation benchmark CG. The HARQ process number can be derived using the PUSCH number. The HARQ process number can be set as a function of the PUSCH number. The HARQ process number can be derived using the time slot number of the allocation benchmark PUSCH. The HARQ process number can be set as a function of the time slot number of the allocation benchmark PUSCH. By adopting this method, HARQ can be performed on one or more PUSCHs in a CG period. There is no need to perform multiple HARQ processes as for each PUSCH. In addition, the HARQ processing can be simplified.

[0218] One or more PDCCHs are set in the CG period. In the CG period, a PDCCH is set for each PUSCH. The number of PUSCHs and the number of PDCCHs can be made the same. One or more PUSCHs are set in the CG period, and the same number of PDCCHs are set.

[0219] The method for setting the PDCCH may appropriately apply the method for setting one or more PDCCHs in the SPS period disclosed in Implementation 1. In this method, the SPS may be replaced by the CG.

[0220] Fig.17 This is a diagram showing an example of resource allocation when multiple PUSCHs and multiple PDCCHs are set in the setting of CG. Multiple PUSCHs are set in the setting of CG, and PDCCH is set according to each PUSCH. The shaded quadrilateral represents PDCCH, and the white quadrilateral represents PUSCH. The horizontal axis represents the time domain, and the vertical axis represents the frequency domain. The CG is set from the gNB to the UE using RRC signaling, and the activation / deactivation of the CG is notified using PDCCH. Multiple PDCCHs are set in each CG period, and scheduling correction information for the corresponding PUSCH is sent using each PDCCH.

[0221] exist Fig.17 In the IEEE 802.11a / b / s protocol, multiple PUSCHs are allocated continuously, but can also be allocated non-contiguously.

[0222] In UL communication, changes in data generation timing and data amount sometimes occur. The UE can use the PUSCH appropriately set by the CG to send information related to the UL data amount and data generation timing. This information can be included in the MAC CE. This information can be sent together with the UL data. BSR (Buffer Status Report) can be used to send UL data amount information. The gNB that receives this information can correct the scheduling of the PUSCH set by the CG. The PDCCH can be used to notify the UE of the scheduling correction information of the PUSCH to be corrected. The UE can obtain the scheduling correction information of the PUSCH by receiving the PDCCH. The UE can use the scheduled and corrected PUSCH to send UL data.

[0223] Thus, multiple PUSCHs can be set in the CG setting, and the PDCCH corresponding to each PUSCH can be set. Therefore, the scheduling of each PUSCH can be dynamically modified. By using the PDCCH to modify the scheduling of each PUSCH, the timing and amount of data are changed, and the settings of the resources allocated to each PUSCH, MSC, etc. can be modified to more appropriate settings. The ability diagram can achieve a reduction in delay time and an improvement in resource utilization efficiency.

[0224] In the above, the case of using one or more PUSCHs to send data is shown. As another method, the amount of PUSCH resources can be increased. For example, multiple time slots can be allocated to one PUSCH. The amount of PUSCH resources can be set. Thus, one PUSCH can be used to send data. In the setting of the CG, a PUSCH setting can be made. The amount of PUSCH resources can be set. The amount of PUSCH resources can be set in the RRC. Alternatively, it can also be set using MAC signaling. Alternatively, it can be included in the DCI and set using PDCCH. Thus, the PUSCH set by the CG can be set to 1, which can simplify the processing.

[0225] Implementation Example 2 Variation 1 Disclosed is another method for solving the problem disclosed in Implementation Example 1. In the setting of CG, one or more PUSCHs are set, and one or more PDCCHs are set. The number of PUSCHs and the number of PDCCHs can be set separately.

[0226] The method of setting one or more PUSCHs in the CG period can appropriately apply the method disclosed in Embodiment 2. The method of setting one or more PDCCHs in the CG period can appropriately apply the method disclosed in Embodiment 2. Using these methods, the number of PUSCHs and the number of PDCCHs can be set separately.

[0227] Scheduling modification information of one or more PUSCHs is notified by each PDCCH configured in one CG cycle. Configuration information of PUSCH other than configuration information transmitted by RRC or DCI can be notified by each PDCCH.

[0228] A method for notifying scheduling correction information of multiple PUSCHs using one PDCCH is disclosed. Multiple search spaces corresponding to each PUSCH are set. The UE receives each search space corresponding to each PUSCH to receive DCI including scheduling correction information of each PUSCH. In this way, by setting multiple search spaces corresponding to each PUSCH, the existing search space setting method can be used. The complication of SPS processing can be avoided.

[0229] Disclosed is another method for notifying scheduling correction information of multiple PUSCHs using one PDCCH. A search space corresponding to multiple PUSCHs is set. The UE receives each search space corresponding to each PUSCH to receive DCI including scheduling correction information of each PUSCH. In this way, by setting a search space corresponding to each PUSCH, the existing search space setting method can be used. The complication of SPS processing can be avoided.

[0230] The setting information of the search space may also be included in the setting information of the CG. It may also be included in the setting information of the PDCCH set in the CG period. The setting information of the search space may be sent from the gNB to the UE using RRC signaling. The setting information of the search space may be included in the DCI including CG activation / deactivation and sent from the gNB to the UE using the PDCCH. As these methods, the method disclosed in Implementation 2 may be appropriately applied.

[0231] The PUSCH may be numbered to identify one or more PUSCHs configured by the CG. In the configuration of one or more PUSCHs, the configuration information of the PUSCH may be associated with the number of the PUSCH. The method disclosed in Embodiment 2 may be appropriately applied.

[0232] In the method of notifying the scheduling correction information of multiple PUSCHs using one PDCCH, in order to determine which PUSCH the scheduling correction information is for, the above-disclosed PUSCH number can be used. In this way, it is possible to clearly indicate which PUSCH the scheduling correction information is for. This can reduce erroneous operations between the gNB and the UE.

[0233] Fig.18This is a diagram showing an example of resource allocation when the number of PDCCHs and the number of PUSCHs are set separately in the CG setting. One PDCCH is set in the CG setting, and five PUSCHs are set. One PDCCH is set in each CG cycle, and the scheduling correction information of the corresponding PUSCH is sent using the PDCCH.

[0234] exist Fig.18 In the IEEE 802.11a / b / s 4000-bit RTS / MS / MS, multiple PUSCHs are allocated continuously, but can also be allocated non-continuously.

[0235] The number of PDCCHs set in one CG cycle may be multiple. The setting information of the PDCCH set in one CG cycle may include the number of PDCCHs. The number of PDCCHs may be set within the range of the number of PDSCHs set in one CG cycle. As a setting method for multiple PDCCHs, the PDCCH may be set periodically. The setting method of CORESET or search space disclosed in Implementation Method 2 may be appropriately applied. Multiple PDCCHs can be set, and PUSCH scheduling correction can be performed using PDCCHs suitable for the timing of UL data generation and the number of data volumes.

[0236] As another setting method for the PDCCH set in a CG cycle, the PDCCH set in a CG cycle can be set using bit mapping. It can also be set to a bit map of the number of bits corresponding to the number of PUSCHs set by the CG. As the setting information of the PDCCH, the search space can also be set using bit mapping. The search space set in a CG cycle may not be periodic, and flexible PDCCH settings can be performed.

[0237] Fig.19 This is a diagram showing other resource allocation examples when the number of PDCCHs and the number of PUSCHs are set separately in the CG setting. In the CG setting, two PDCCHs are set in each CG period, and five PUSCHs are set. The scheduling correction information of the PUSCH before the (n+1)th PDCCH can be sent using the nth PDCCH. Fig.19 In the example, the first PDCCH is used to send scheduling correction information of the first to third PUSCHs, and the second PDCCH is used to send scheduling correction information of the fourth to fifth PUSCHs.

[0238] exist Fig.19 In the IEEE 802.11a / b / s protocol, multiple PUSCHs are allocated continuously, but can also be allocated non-contiguously.

[0239] Thus, multiple PUSCHs can be set in the setting of the CG, and the PDCCH corresponding to each PUSCH can be set. By setting the number of PUSCHs and the number of PDCCHs separately, flexible PDCCH settings can be performed. In addition, since the PDCCH resources can be reduced, the resource utilization efficiency can be improved. In addition, since the PDCCH reception processing of the UE can be reduced, low power consumption can be achieved. In addition, similar to the effect of Implementation 2, the scheduling of each PUSCH can be dynamically corrected. By using the PDCCH to correct the scheduling of each PUSCH, the timing and amount of data generation can be changed, and the settings of the resources allocated to each PUSCH, MSC, etc. can be corrected to more appropriate settings. The ability diagram achieves a reduction in delay time and an improvement in resource utilization efficiency.

[0240] Implementation Example 2 Variation 2 Other methods for solving the problem disclosed in Implementation Example 1 are disclosed. In the setting of the CG, one or more PUSCHs are set, and one or more PDCCHs are set. The number of PUSCHs and the number of PDCCHs can be set separately. The PDCCH includes release information of the PUSCH set by the CG. The gNB can use the PDCCH to notify the UE of the release information of one or more PUSCHs set by the CG.

[0241] In the DCI sent using one or more PDCCHs set in each CG period, release information of one or more PUSCHs set by the CG may be included. In the case where the release information is included in the DCI, a new DCI format may also be set. As another method, an existing DCI format may be used (see non-patent document 12). For example, DCI format 2_4 may be used. By using an existing DCI format, processing complications may be avoided.

[0242] In order to receive the PDCCH that sends the DCI including the release information, a new RNTI can be set. For example, it can be set to the RNTI for receiving the PDCCH disclosed in Implementation 2 or Implementation 2 Variation 1. By setting it to an RNTI specific to the PDCCH in the CG setting, it is possible to reduce malfunctions. As another method, an existing RNTI can be used (see non-patent document 15). For example, CI-RNTI (Cancellation RNTI: Cancellation indication RNTI) can be used. When using DCI format 2_4, CI-RNTI can be used. By using an existing RNTI, processing complications can be avoided.

[0243] The method or release method of notifying the release information of one or more PUSCHs using one PDCCH can appropriately apply the method or release method of notifying the release information of one or more PDSCHs using one PDCCH disclosed in Implementation 1. In this method, CG can be set to replace SPS. PUSCH can be set to replace PDSCH. The same effect as Implementation 1 is obtained.

[0244] Fig. 20 This is a diagram showing an example of releasing resources of a PUSCH set by a CG using PDCCH. In the setting of the CG, the number of PDCCHs and the number of PUSCHs are set separately. In the setting of the CG, one PDCCH is set, and multiple PUSCHs are set. One PDCCH is set for each CG period. Information on releasing the PUSCH using the PDCCH and information indicating which PUSCH is released are sent. The UE can identify which PUSCH is released by receiving the PDCCH. The UE does not send the released PUSCH.

[0245] The number of PDCCHs may be multiple. As a method for setting multiple PDCCHs, PDCCHs may be set periodically. The setting may be performed within the range of setting PUSCH. Alternatively, the transmission may be performed within the range of setting PUSCH. As another setting method, PDCCH may be set using bit mapping. The setting may be performed within the range of setting PUSCH.

[0246] Fig.21 : is a diagram showing another example of using PDCCH to release the resources of PUSCH set by CG. In the setting of CG, two PDCCHs are set for each CG period. Information on releasing one or more PUSCHs set by CG and information indicating which PUSCH is released are sent using PDCCH. Using the nth PDCCH, information on releasing the PUSCH before the n+1th PDCCH is sent and information indicating which PUSCH is released are sent. Fig.21 In the example, the first PDCCH is used to send the release information of the first to third PUSCHs and the information indicating which PUSCH is released. The second PDCCH is used to send the scheduling correction information of the fourth to fifth PUSCHs. The UE can identify which PUSCH is released by receiving the PDCCH. The UE does not send the released PUSCH.

[0247] The release information of one or more PUSCHs set by the CG may be included in the scheduling correction information of one or more PUSCHs set by the CG disclosed in variant example 1 of implementation mode 2. The scheduling correction information of one or more PUSCHs set by the CG may include information for releasing the scheduling of one or more PUSCHs set by the CG. The scheduling correction information of one or more PUSCHs set by the CG may include information for canceling the scheduling of one or more PUSCHs set by the CG.

[0248] As another method, the scheduling correction information of one or more PUSCHs set by the CG disclosed in variant example 1 of implementation mode 2 can be used to release (or cancel) other PUSCHs except the PUSCH to be scheduled. As scheduling correction information, information indicating the execution of PUSCH allocation set in the CG setting can be set. As scheduling correction information, information indicating the execution of PUSCH allocation set in the CG setting can be set. Scheduling correction information of one or more PUSCHs set by the CG can be used to release (or cancel) a PUSCH that does not show information on the execution of PUSCH allocation. As a result, the UE only needs to receive the scheduling correction information, which can simplify the processing at the UE.

[0249] Therefore, multiple PUSCHs can be set in the setting of the CG, and the PDCCH corresponding to each PUSCH can be set. By setting the number of PUSCHs and the number of PDCCHs separately, flexible PDCCH settings can be performed. In addition, since the PDCCH resources can be reduced, the resource utilization efficiency can be improved. In addition, since the PDCCH reception processing of the UE can be reduced, low power consumption can be achieved. In addition, since each PUSCH can be released dynamically, even if multiple PUSCH settings are performed in the CG setting, it can be corrected to a setting suitable for changes in data generation timing and data volume. The ability to achieve a reduction in delay time and an improvement in resource utilization efficiency.

[0250] Embodiment 2 Variation 3 Disclosed is another method for solving the problem disclosed in Implementation Example 1. One or more PDCCHs are set in the setting of the CG. In the setting of the CG, the setting of the PUSCH is not performed. Regarding the setting method of the PDCCH, the above-disclosed method can be appropriately applied. The notification method of the setting of the PDCCH from the gNB to the UE can appropriately apply the above-disclosed method.

[0251] PUSCH is scheduled using one or more PDCCHs set for each CG period. The PDCCH is used to notify the scheduling information of PUSCH. One PDCCH can be used to notify the scheduling information of multiple PUSCHs. The notification method can appropriately apply the above-disclosed method of notifying the scheduling correction information of multiple PUSCHs using one PDCCH.

[0252] Fig. 22 This is a diagram showing an example of resource allocation when two PDCCHs are set in the CG setting. PUSCH is not set in the CG setting. Two PDCCHs are set for each CG period. The CG is set from the gNB to the UE using RRC signaling, and the activation / deactivation of the CG is notified using the PDCCH. The scheduling information of the PUSCH is notified using the PDCCH set for each CG period. The scheduling information of the PUSCH before sending the n+1th PDCCH can be sent using the nth PDCCH. Fig. 22 In the example of , in the initial period, one PUSCH is scheduled using the first PDCCH, and two PUSCHs are scheduled using the second PDCCH. In the second period, two PUSCHs are scheduled using the first PDCCH, and one PUSCH is scheduled using the second PDCCH. The UE can receive the scheduling information of the PUSCH by receiving the PDCCH.

[0253] In this way, one or more PDCCHs can be set in the CG setting. Since PDCCH is used to schedule PUSCH in each CG period, the number of PUSCHs to be scheduled can be set according to the data generation timing and data volume changes. Therefore, the ability to achieve delay time reduction and improve resource utilization efficiency.

[0254] Implementation method 3. Another method for solving the problem disclosed in the first embodiment is disclosed.

[0255] One PDSCH is configured in the SPS configuration. One or more PDSCHs are configured using the PDSCH configured in the SPS configuration. MAC signaling may be used for the configuration of the one or more PDSCHs. The MAC CE may include scheduling information for the one or more PDSCHs.

[0256] The method of setting a PDSCH in the setting of SPS can apply the existing setting method of SPS. As a setting method for one or more PDSCHs, the method disclosed in Implementation 1 can be appropriately applied. In the case where DL data is sent by the PDSCH set in the setting of SPS, DL data and setting information of one or more PDSCHs can be multiplexed. This multiplexing can be performed by MAC. In the case where DL data is not sent using the PDSCH set in the setting of SPS, only the setting information of one or more PDSCHs can be sent.

[0257] In the case where one or more PDSCHs are not configured, the configuration information may include information indicating that there is no PDSCH configuration. As another method, padding may be included in the MAC PDU. The UE can recognize the case where there is no PDSCH configuration by receiving this information.

[0258] Fig.23 This is a diagram showing an example of resource allocation when one or more PDSCHs are configured using the PDSCH configured in the SPS configuration. The shaded rectangles represent PDCCHs, and the white rectangles represent PDSCHs. The horizontal axis represents the time domain, and the vertical axis represents the frequency domain. The SPS is configured from the gNB to the UE using RRC signaling, and the activation / deactivation of the SPS is notified using the PDCCH. One PDSCH is configured for each SPS period. The PDSCH configured in the SPS configuration is used to send DL data and configuration information for one or more PDSCHs. Using MAC, the MAC SDU containing DL data and the MAC CE containing configuration information for one or more PDSCHs are multiplexed. Fig.23 In the SPS configuration, two PDSCHs are configured using the PDSCH configured in the SPS configuration. DL data can be transmitted using the configured PDSCH.

[0259] In this way, one or more PDSCHs can be set for each SPS period. In addition, since one or more PDSCHs are set using the PDSCH set in the SPS setting, the number of PDSCHs in each SPS period can be flexibly changed. By dynamically changing the setting information of one or more PDSCHs using the PDSCH set in the SPS setting, resource allocation that is more suitable for changes in data generation timing and data volume can be achieved. The ability to achieve a reduction in delay time and an improvement in resource utilization efficiency.

[0260] Implementation 3 Variation 1 Disclosed is another method for solving the problem disclosed in Implementation Example 1. Multiple PDSCHs are set in the setting of SPS. One or more PDSCHs are set using the PDSCH set in the setting of SPS. In other words, multiple PDSCHs are set in the setting of SPS, and one or more PDSCHs are additionally set using the PDSCH. MAC signaling can be used to set one or more PDSCHs set using the PDSCH set in the setting of SPS. MAC CE can include setting information of the one or more PDSCHs.

[0261] The method for setting multiple PDSCHs in the setting of SPS can appropriately apply the setting method disclosed in Implementation 1. In the case of sending DL data using the PDSCH set in the setting of SPS, the DL data and the setting information of one or more PDSCHs can be multiplexed. The multiplexing can be performed by MAC. In the case of not sending DL data using the PDSCH set in the setting of SPS, only the setting information of one or more PDSCHs can be sent.

[0262] In the case where there is no configuration for one or more PDSCHs, the configuration information may include information indicating that there is no configuration for the PDSCH. As another method, padding may be included in the MAC PDU. The UE may recognize the case where there is no configuration for the PDSCH by receiving this information.

[0263] Fig.24 This is a diagram showing an example of resource allocation when one or more PDSCHs are set using multiple PDSCHs set in the SPS setting. The shaded rectangle represents the PDCCH, and the white rectangle represents the PDSCH. The horizontal axis represents the time domain, and the vertical axis represents the frequency domain. The SPS is set from the gNB to the UE using RRC signaling, and the activation / deactivation of the SPS is notified using the PDCCH. Two PDSCHs are set for each SPS period. The PDSCH set in the SPS setting is used to send DL data and setting information for one or more PDSCHs. Using MAC, the MAC SDU containing DL data and the MAC CE containing setting information for one or more PDSCHs are multiplexed.

[0264] exist Fig.24In the first cycle of SPS, the first PDSCH set in the setting of SPS is not used to set the PDSCH, but the second PDSCH is used to set (add) two PDSCHs. DL data can be sent using the set PDSCH. In the second cycle of SPS, one PDSCH is set (added) using the first PDSCH set in the setting of SPS, and one PDSCH is set (added) using the second PDSCH. DL data can be sent using the set PDSCH.

[0265] In this way, one or more PDSCHs can be set for each SPS period. By setting multiple PDSCHs in the SPS setting, the number and timing of PDSCHs in each SPS period can be flexibly changed. By dynamically changing the setting information of one or more PDSCHs using each of the multiple PDSCHs set in the SPS setting, resource allocation that is more suitable for changes in data generation timing and data volume can be achieved. The ability to achieve delay time reduction and improved resource utilization efficiency.

[0266] Implementation 3 Variation 2 Disclosed is another method for solving the problem disclosed in Implementation Example 1. One or more PDSCHs are set in the setting of the SPS. The PDSCH set in the setting of the SPS is used to notify the release information of one or more PDSCHs. MAC signaling can be used for notification of the release information of the one or more PDSCHs. The MAC CE can include the release information of the one or more PDSCHs.

[0267] The method of setting multiple PDSCHs in the SPS setting can appropriately apply the setting method disclosed in Implementation Example 1. For the release information of one or more PDSCHs, the release information of one or more PDSCHs set in the SPS disclosed in Modification Example 2 of Implementation Example 1 can be appropriately applied.

[0268] In the case of sending DL data using the PDSCH set in the setting of the SPS, the DL data and the release information of one or more PDSCHs may be multiplexed. The multiplexing may be performed by the MAC. In the case of not sending DL data using the PDSCH set in the setting of the SPS, only the release information of one or more PDSCHs may be sent. In the case of no release of one or more PDSCHs, the release information may include information indicating that there is no release information of the PDSCH.

[0269] In addition to the release information of the PDSCH, or in place of the PDSCH release information, information indicating which PDSCH is released may be set and sent. The UE may identify which PDSCH is released by receiving the PDSCH containing the information. The UE does not receive the released PDSCH.

[0270] Fig.25 This is a diagram showing an example of resource allocation when one or more PDSCHs are released using multiple PDSCHs set in the SPS setting. The shaded rectangles represent PDCCHs, and the white rectangles represent PDSCHs. The horizontal axis represents the time domain, and the vertical axis represents the frequency domain. The SPS is set from the gNB to the UE using RRC signaling, and the activation / deactivation of the SPS is notified using the PDCCH. Five PDSCHs are set for each SPS cycle. The PDSCH set in the SPS setting is used to send DL data and release information of one or more PDSCHs. Using MAC, the MAC SDU containing DL data and the MAC CE containing release information of one or more PDSCHs are multiplexed. Any PDSCH set in the SPS setting can be used to send the release information of the PDSCH. Fig.25 In the first cycle of SPS, five PDSCHs are set in the SPS settings. In the first cycle, the third PDSCH set in the SPS settings is used to send PDSCH release information. Release information for the fourth and fifth PDSCHs is sent. The released resources can be allocated to other UEs by the gNB. The UE does not receive the released PDSCH. In the second cycle of SPS, the first PDSCH set in the SPS settings is used to send PDSCH release information. Release information for the fourth and fifth PDSCH is sent. The released resources can be allocated to other UEs by the gNB. The UE does not receive the released PDSCH.

[0271] Thus, for each SPS period, one or more PDSCHs of the multiple PDSCHs set in the SPS setting can be released. The number of PDSCHs in each SPS period can be flexibly changed. By dynamically changing the release information of the PDSCH, for example, even if multiple PDSCHs are set in the SPS setting, resource allocation that is more suitable for changes in data generation timing and data volume can be performed. The ability to achieve a reduction in delay time and an improvement in resource utilization efficiency. In addition, since the UE's PDSCH reception processing can be reduced, low power consumption can be achieved.

[0272] Implementation method 4. Another method for solving the problem disclosed in the first embodiment is disclosed.

[0273] A PUSCH is configured in the CG configuration. The PUSCH configured in the CG configuration is used to notify the PUSCH scheduling request. One or more PUSCHs are scheduled using the PDCCH.

[0274] The method of setting a PUSCH in the setting of the CG can apply the existing setting method of the CG. In the case of sending UL data using the PUSCH set in the setting of the CG, the scheduling request of the UL data and the PUSCH can be multiplexed. The multiplexing can be performed by the MAC. In the case of not sending UL data using the PUSCH set in the setting of the CG, only the scheduling request of the PUSCH can be sent. The gNB can identify the scheduling request of the PUSCH by receiving this information from the UE.

[0275] In the case where there is no scheduling request for PUSCH, information indicating that there is no scheduling for PUSCH can be notified. As another method, padding can be included in the MAC PDU. The gNB can recognize the case where there is no scheduling request for PUSCH by receiving this information from the UE.

[0276] The gNB sends a PDCCH to the UE and schedules one or more PUSCHs. The gNB may schedule the one or more PUSCHs using a scheduling request for the PUSCH received from the UE. The UE receives the PDCCH and receives scheduling information for one or more PUSCHs. The UE may use the scheduled PUSCH to send UL data.

[0277] In the existing CG, there is no need to receive PDCCH in the CG period. The UE does not need to monitor PDCCH. However, in the method disclosed in this embodiment, the UE needs to receive PDCCH to receive scheduling information of one or more PUSCHs. The method is disclosed. When the UE sends a scheduling request for PUSCH, PDCCH monitoring starts. The UE can stop monitoring after receiving PDCCH.

[0278] Other methods are disclosed. The monitoring period of PDCCH can be set. After sending a scheduling request for PUSCH, the UE monitors PDCCH during the PDCCH monitoring period. When the UE receives PDCCH, it can continue to monitor PDCCH during the PDCCH monitoring period. Multiple PDCCHs can be sent during the PDCCH monitoring period so that the UE can receive the multiple PDCCHs. As another method when receiving PDCCH, the UE can stop monitoring PDCCH. Capability diagram realizes low power consumption of UE. One PDCCH can be sent during the PDCCH monitoring period. By scheduling one or more PUSCHs using PDCCH, resource allocation of PUSCH suitable for the UL data amount can be achieved.

[0279] The method for setting the PDCCH monitoring period is disclosed. The PDCCH monitoring period may be included in the setting information of the CG. The gNB may use RRC signaling to send the PDCCH monitoring period to the UE. It may be included in the setting information of the CG and sent using RRC signaling. The gNB may use PDCCH to send the PDCCH monitoring period to the UE. The PDCCH monitoring period may be included in the DCI together with the activation / deactivation information of the CG and sent using PDCCH. As another method, the PDCCH monitoring period may be included in the activation / deactivation information of the CG.

[0280] The PDCCH that schedules one or more PUSCHs can be used to notify whether there is a subsequent PDCCH or whether the subsequent PDCCH needs to be monitored. The PDCCH monitoring period can be reset. The PDCCH can be used to notify the PDCCH monitoring period for monitoring subsequent PDCCHs. As another method, the PDCCH monitoring period can be restarted when the UE receives the PDCCH. As a result, the gNB can perform flexible PUSCH scheduling for the UE.

[0281] As a method of scheduling one or more PUSCHs using PDCCH, the method of scheduling one or more PUSCHs using PDCCH disclosed in variation 3 of implementation mode 2 can be appropriately applied.

[0282] Fig.26 It shows an example of resource allocation when using the PUSCH set in the CG setting to notify the scheduling request of one or more PUSCHs. The shaded rectangle represents the PDCCH, and the white rectangle represents the PUSCH. The horizontal axis represents the time domain, and the vertical axis represents the frequency domain. The CG is set from the gNB to the UE using RRC signaling, and the activation / deactivation of the CG is notified using the PDCCH. A PUSCH is set for each CG period. The PUSCH set in the CG setting is used to send a scheduling request for one or more PUSCHs. Using MAC, the MAC SDU containing UL data and the MAC CE containing the scheduling request for one or more PUSCHs are multiplexed.

[0283] The gNB that receives the PUSCH scheduling request from the UE uses the PDCCH to schedule one or more PUSCHs. The PDCCH contains the scheduling information of one or more PUSCHs. Fig.26In the first cycle of the CG, two consecutive PUSCHs are scheduled and two non-consecutive PUSCHs are scheduled in the second cycle. After the UE notifies the gNB of the scheduling request for PUSCH, it monitors the PDCCH during the PDCCH monitoring period. The UE that receives the PDCCH during the PDCCH monitoring period receives the scheduling information of one or PUSCH. The UE can use the scheduling information of the received PUSCH to send UL data. The PDCCH including the scheduling information of the PUSCH and the PUSCH scheduled by the PDCCH can be discontinuous or non-continuous in time. There can also be a gap in time.

[0284] In this way, one or more PUSCHs can be set for each CG period. In addition, since the PUSCH set in the CG setting is used to make a scheduling request for the PUSCH, there is no need to send an SR (Scheduling Request). Since there is no need to wait for the SR period, it is possible to strive to reduce delay time. In addition, since the UE does not need to send an SR, it is possible to strive to achieve low power consumption. In addition, the gNB that receives the scheduling request from the UE can flexibly schedule the number of PUSCHs suitable for the amount of UL data generated in the UE. Therefore, resource allocation that is more suitable for changes in data generation timing and data volume can be performed. The ability to achieve delay time reduction and improve resource utilization efficiency.

[0285] Implementation 4 Variation 1 Disclosed are other methods for solving the problem disclosed in Implementation Example 1. Multiple PUSCHs are set in the setting of the CG. The scheduling request of the PUSCH is notified using the PUSCH set in the setting of the CG. In other words, the additional request of the PUSCH is notified using the PUSCH set in the setting of the CG. MAC signaling can be used to notify the additional request of the PUSCH. The MAC CE can include the additional request of the PUSCH. One or more PUSCHs are scheduled using the PDCCH.

[0286] The method of setting multiple PUSCHs in the setting of CG can appropriately apply the method disclosed in variant example 1 of implementation mode 2. In the case of sending UL data using the PUSCH set in the setting of CG, the scheduling request of UL data and PUSCH can be multiplexed. This multiplexing can be performed by MAC. In the case of not sending UL data using the PUSCH set in the setting of CG, only the scheduling request of PUSCH can be sent. The gNB can identify the scheduling request of PUSCH by receiving this information from the UE.

[0287] In the case where there is no scheduling request for PUSCH, information indicating that there is no scheduling request for PUSCH may be notified. As another method, padding may be included in the MAC PDU. The gNB can recognize the case where there is no scheduling request for PUSCH by receiving this information.

[0288] The gNB sends a PDCCH to the UE and schedules one or more PUSCHs. The gNB may schedule the one or more PUSCHs using a scheduling request for the PUSCH received from the UE. The UE receives the PDCCH and receives scheduling information for one or more PUSCHs. The method by which the UE can receive the PDCCH may appropriately apply the method disclosed in Implementation 4. The UE may use the PUSCH scheduled by the PDCCH to send UL data.

[0289] Fig. 27 This is a diagram showing an example of resource allocation when multiple PUSCHs set in the CG setting are used to notify a PUSCH scheduling request. The shaded rectangles represent PDCCHs, and the white rectangles represent PUSCHs. The horizontal axis represents the time domain, and the vertical axis represents the frequency domain. The CG is set from the gNB to the UE using RRC signaling, and the activation / deactivation of the CG is notified using the PDCCH. Two PUSCHs are set for each CG cycle. The PUSCH set in the CG setting is used to send UL data and PUSCH scheduling requests. Using MAC, the MAC SDU containing UL data and the MAC CE containing PUSCH scheduling information are multiplexed.

[0290] exist Fig. 27 In the first cycle of CG, only UL data is sent using the first PUSCH set in the setting of CG, and UL data and PUSCH scheduling requests are multiplexed and sent using the second PUSCH. In the second cycle of CG, the first PUSCH set in the setting of CG is used to multiplex and send UL data and PUSCH scheduling requests, and similarly, the second PUSCH is used to multiplex and send UL data and PUSCH scheduling requests.

[0291] The gNB that receives the PUSCH scheduling request from the UE uses the PDCCH to schedule one or more PUSCHs. Fig. 27In the first period of the CG, two consecutive PUSCHs are scheduled (added) using the PDCCH according to the PUSCH scheduling request included in the second PUSCH, and in the second period, one PUSCH is scheduled (added) using each PDCCH according to the PUSCH scheduling request included in the first PUSCH and the second PUSCH. After the UE notifies the gNB of the scheduling request for the PUSCH, it monitors the PDCCH during the PDCCH monitoring period. A UE that receives the PDCCH during the PDCCH monitoring period receives scheduling information for one or PUSCH. The UE can use the scheduling information of the received PUSCH to send UL data. The PDCCH including the scheduling information for the PUSCH and the PUSCH scheduled by the PDCCH may be discontinuous or non-continuous in time. An interval may also be set in time.

[0292] In this way, one or more PUSCHs can be set for each CG period. In addition, since the PUSCH set in the CG setting is used to make a scheduling request for the PUSCH, there is no need to send the SR. Since there is no need to wait until the SR sending period, it is possible to strive to reduce the delay time. In addition, since the UE does not need to send the SR, it is possible to strive to achieve low power consumption. In addition, the gNB that receives the scheduling request from the UE can flexibly schedule the number of PUSCHs suitable for the amount of UL data generated in the UE. By being able to set multiple PUSCHs in the CG setting, the gNB can more flexibly schedule the number of PUSCHs suitable for the amount of UL data generated in the UE in real time. Therefore, resource allocation that is more suitable for data generation timing and changes in data volume can be performed. The ability to achieve delay time reduction and improve resource utilization efficiency.

[0293] Implementation 4 Variation 2 Other methods for solving the problem disclosed in Implementation Example 1 are disclosed. One or more PUSCHs are set in the setting of the CG. Information related to the PUSCH used for transmission is notified using the PUSCH set in the setting of the CG. MAC signaling can be used to notify information related to the PUSCH used for transmission. MAC CE can include information related to the PUSCH used for transmission.

[0294] The method of setting multiple PUSCHs in the setting of CG can apply the setting method disclosed in variant example 1 of implementation mode 2. In the case of sending UL data using the PUSCH set in the setting of CG, UL data and information related to the PUSCH used for sending can be multiplexed. This multiplexing can be performed by MAC. In the case of not sending UL data using the PUSCH set in the setting of CG, only information related to the PUSCH used for sending can be sent. The gNB receives this information from the UE, thereby being able to identify which PUSCH the UE uses for sending.

[0295] In the case where there is no information related to the PUSCH for transmission, information indicating that there is no such information may be included. As another method, padding may be included in the MAC PDU. By receiving this information, the gNB is able to recognize that the UE does not have a PUSCH for transmission.

[0296] The information related to the PUSCH used for transmission may be information indicating which PUSCH is used for transmission. By receiving this information, the gNB can determine the PUSCH used by the UE for transmission. In addition, the gNB can determine the PUSCH that the UE does not use for transmission among multiple PUSCHs set by the CG. The gNB can allocate resources of the PUSCH that the UE does not use for transmission to other UEs. The UE uses the PUSCH used for transmission notified to the gNB to transmit UL data. The UE does not use a PUSCH other than the PUSCH used for transmission notified to the gNB to transmit UL data.

[0297] Fig.28 This is a diagram showing an example of resource allocation when multiple PUSCHs set in the CG setting are used to send information related to the PUSCH used by the UE for transmission. The shaded quadrilateral represents the PDCCH, and the white quadrilateral represents the PUSCH. The horizontal axis represents the time domain, and the vertical axis represents the frequency domain. The CG is set from the gNB to the UE using RRC signaling, and the activation / deactivation of the CG is notified using the PDCCH.

[0298] Fig.28 In , five PUSCHs are set for each CG period. The PUSCH set in the CG setting is used to send information related to the PUSCH used by the UE for transmission. Using MAC, the MAC SDU containing UL data and the MAC CE containing information related to the PUSC used by the UE for transmission are multiplexed. The UE can use any PUSCH set in the CG setting to send information related to the PUSCH used by the UE for transmission. Fig.28 In the first PUSCH, information related to the PUSCH used by the UE for transmission is sent.

[0299] exist Fig.28 In the first cycle of CG, information of the fourth and fifth PUSCHs is sent as information related to the PUSCH used by the UE for transmission. In the second cycle of CG, information of the third to fifth PUSCHs is sent as information related to the PUSCH used by the UE for transmission. Among the PUSCHs set by CG, in the first cycle of CG, the UE does not use the second and third PUSCHs to send UL data, but uses the fourth and fifth PUSCHs to send UL data. In the second cycle of CG, UL data is not sent using the second PUSCH, but uses the third to fifth PUSCHs to send UL data.

[0300] By receiving information related to the PUSCH used by the UE for transmission from the UE, the gNB can identify which PUSCH is used for transmission and which PUSCH is not used for transmission by the UE among the PUSCHs set by the CG. Fig.28 In the first period of CG, the gNB may not receive the second and third PUSCHs from the UE, but may receive the fourth and fifth PUSCHs. In the second period of CG, the gNB may not receive the second PUSCH from the UE, but may receive the third to fifth PUSCHs.

[0301] The gNB can allocate PUSCH resources that the UE does not use for transmission to other UEs.

[0302] In this way, one or more PUSCHs can be set for each CG period. In addition, since the PUSCH set in the CG setting is used to send information related to the PUSCH used by the UE for transmission, the gNB only needs to receive the PUSCH used by the UE for transmission in the PUSCH set by the CG. The processing of the gNB can be simplified and low power consumption can be achieved. In addition, the gNB can allocate the resources of the PUSCH that the UE does not use for transmission in the PUSCH set by the CG to other UEs. The ability diagram improves resource utilization efficiency. Even if multiple PUSCH settings are performed in the CG setting, more appropriate resource allocation can be made for changes in data generation timing and data volume. The ability diagram achieves a reduction in delay time and an improvement in resource utilization efficiency.

[0303] Implementation 4 Variation 3 Disclosed are other methods for solving the problem disclosed in Implementation 1. One or more PUSCHs are set in the CG setting. The PUSCH set in the CG setting is used to notify the release information of the PUSCH. MAC signaling can be used to notify the release request of the PUSCH. The MAC CE can include the release request of the PUSCH.

[0304] The method of setting multiple PUSCHs in the setting of CG can appropriately apply the method disclosed in variant example 1 of implementation mode 2. In the case of sending UL data using the PUSCH set in the setting of CG, the release information of UL data and PUSCH can be multiplexed. This multiplexing can be performed by MAC. In the case of not sending UL data using the PUSCH set in the setting of CG, only the release information of PUSCH can be sent. The gNB can identify the releasable PUSCH by receiving this information from the UE.

[0305] In the case where there is no PUSCH release information, information indicating that there is no such information may be included. As another method, padding may be included in the MAC PDU. The gNB can recognize the situation where there is no PUSCH to be released by receiving this information.

[0306] The PUSCH release information may include information for determining the PUSCH to be released. For example, it may be the number of the PUSCH to be released. The gNB is able to determine the releasable PUSCH by receiving the information. In addition, the gNB is able to determine the releasable PUSCH among multiple PUSCHs set by the CG. The gNB may allocate the releasable PUSCH resources to other UEs. The UE does not send UL data using the PUSCH to be released notified to the gNB. UL data is sent using a PUSCH other than the PUSCH to be released.

[0307] Fig.29 This figure shows an example of resource allocation when multiple PUSCHs set in the CG setting are used to send PUSCH release information. The shaded quadrilateral represents PDCCH, and the white quadrilateral represents PUSCH. The horizontal axis represents the time domain, and the vertical axis represents the frequency domain. The CG is set from the gNB to the UE using RRC signaling, and the activation / deactivation of the CG is notified using PDCCH.

[0308] Fig.29 In , five PUSCHs are set for each CG cycle. The PUSCH set in the CG setting is used to send UL data and PUSCH release information. Using MAC, the MAC SDU containing UL data and the MACCE containing PUSCH release information are multiplexed. Any PUSCH set in the CG setting can be used to send PUSCH release information. Fig.29 The release information of PUSCH is sent in the third PUSCH in the first cycle of CG and in the first PUSCH in the second cycle of CG.

[0309] exist Fig.29In the first cycle of CG, the information of the fourth and fifth PUSCHs is sent as PUSCH release information. In the second cycle of CG, the information of the fourth and fifth PUSCHs is sent as PUSCH release information. Among the PUSCHs set by CG, in the first cycle of CG, the UE does not use the fourth and fifth PUSCHs to send UL data, but uses the first to third PUSCHs to send UL data. In the second cycle of CG, the UE does not use the fourth and fifth PUSCHs to send UL data, but uses the first to third PUSCHs to send UL data.

[0310] The gNB is able to identify which PUSCH among the PUSCHs set by the CG can be released by receiving information about the release of the PUSCH from the UE. Fig.29 In the first cycle of CG, the gNB does not receive the fourth and fifth PUSCHs from the UE, but receives the first to third PUSCHs. In the second cycle of CG, the gNB does not receive the fourth and fifth PUSCHs from the UE, but receives the first to third PUSCHs.

[0311] The gNB can allocate the PUSCH resources indicated by the UE using the release information to other UEs.

[0312] Thus, for each CG cycle, one or more PUSCHs of the multiple PUSCHs set in the CG setting can be released. The number of PUSCHs for each CG cycle can be flexibly changed. By dynamically changing the release information of PUSCH, for example, even if multiple PUSCHs are set in the CG setting, resource allocation that is more suitable for changes in data generation timing and data volume can be performed. The ability to achieve reduction in delay time and improvement in resource utilization efficiency. In addition, since the PUSCH reception processing of the gNB can be reduced, low power consumption can be achieved.

[0313] Implementation 4 Variation 4 Disclosed is another method for solving the problem disclosed in Implementation Example 1. One or more PUSCHs are set in the setting of the CG. The PUSCH set in the setting of the CG is used to notify the request for adding the PUSCH. MAC signaling can be used to notify the request for adding the PUSCH. The MAC CE can include the request for adding the PUSCH.

[0314] The method of setting multiple PUSCHs in the setting of CG can apply the setting method disclosed in variant example 1 of implementation mode 2. In the case of sending UL data using the PUSCH set in the setting of CG, the UL data and the request for adding PUSCH can be multiplexed. The multiplexing can be performed by MAC. In the case of not sending UL data using the PUSCH set in the setting of CG, only the request for adding PUSCH can be sent. The gNB can identify the situation where PUSCH needs to be added to the UE by receiving this information from the UE.

[0315] In the case where there is no PUSCH addition request, it is sufficient to include information indicating that there is no such request. As another method, padding can be included in the MAC PDU. The gNB can recognize that there is no need to add PUSCH by receiving this information.

[0316] The PUSCH addition request information may include the number of additional PUSCHs. After the PUSCH set by the CG, the gNB continuously allocates PUSCH resources corresponding to the number of PUSCHs requested by the UE. The gNB does not allocate the allocated resources to other UEs. The UE may use the additional requested PUSCH to send UL.

[0317] A method for setting the time domain of additional PUSCH resources is disclosed. The time domain of additional PUSCH resources can be determined using time information from the PDCCH used for activation / deactivation of the CG. Since the time domains of the PUSCH set by the CG and the additional PUSCH resources can be set together, processing becomes easy. Other methods are disclosed. It can also be determined using time information from the transmission timing of the last PUSCH set by the CG. Since it can be set regardless of the number of PUSCHs set by the CG, malfunctions when adding PUSCHs can be reduced.

[0318] The time domain resources of the PUSCH allocated additionally after the PUSCH set by the CG may not be continuous. A deviation may also be set.

[0319] The time domain setting information of the additional PUSCH resources can also be statically determined in advance according to standards, etc. It can reduce malfunctions in gNB and UE. As another method, the gNB can use RRC signaling to notify the UE of the setting information. It can also be sent in the RRC information used for CG setting. As another method, the gNB can use PDCCH to notify the UE. For example, it can be included in the DCI used for activation / deactivation of the CG and use PDCCH for notification. As a result, the UE can identify the transmission timing of the added PUSCH.

[0320] The UE can notify the gNB of the time domain information of the additional PUSCH. For example, the offset from the last PUSCH set by the CG can be notified. Thus, for example, the UE can request the allocation of additional resources for the PUSCH suitable for UL data generation timing. As a notification method from the UE to the gNB, for example, MAC signaling can also be used for notification. It can be included in the additional request for the PUSCH notified from the UE to the gNB.

[0321] The method for setting the frequency domain of the resources of the additional PUSCH is disclosed. The setting method can be statically determined in advance according to standards, etc. It can reduce malfunctions in gNB and UE. As another method, it can be set to be the same as the frequency domain information of the PUSCH resources set by the CG. For example, it can be set to be the same as the frequency domain of the resources of the last PUSCH set by the CG. The PUSCH set by the CG can be numbered. It can be set to be the same as the frequency domain of the resources of the nth PUSCH set by the CG. The gNB can notify the UE of the same PUSCH number. The gNB can use RRC signaling to notify the UE. It can also be included in the RRC information used for CG setting. As another method, the gNB can use PDCCH to notify the UE. For example, it can be included in the DCI for activation / deactivation of the CG and use PDCCH for notification. In this way, the UE can identify the transmission frequency of the added PUSCH.

[0322] The UE can notify the gNB of the number of the PUSCH that has the same frequency domain information. For example, MAC signaling can be used for notification. It can be included in the additional request for the PUSCH notified from the UE to the gNB. Thus, for example, the UE can request the gNB to have the same frequency domain as the PUSCH with good reception quality.

[0323] The method of configuring the frequency domain of the additional PUSCH resources may be appropriately applied to other configurations of the additional PUSCH. The UE can configure the additional PUSCH. The UE can transmit the additional PUSCH.

[0324] Fig.30 This figure shows an example of resource allocation when sending an additional request for PUSCH using multiple PUSCHs set in the CG setting. The shaded rectangles represent PDCCHs, and the white rectangles represent PUSCHs. The horizontal axis represents the time domain, and the vertical axis represents the frequency domain. The CG is set from the gNB to the UE using RRC signaling, and the activation / deactivation of the CG is notified using PDCCH.

[0325] The gNB can send the scheduling information of the pre-added PUSCH resources to the UE. Part or all of the scheduling information of the added PUSCH resources can be notified by RRC signaling together with the setting of the CG, or can be notified by PDCCH together with the activation / deactivation of the CG. For example, part of the scheduling information of the added PUSCH resources can be notified by RRC signaling together with the setting of the CG, and the remaining information can be notified by PDCCH together with the activation / deactivation of the CG. As a result, the UE can obtain the scheduling information of the added PUSCH.

[0326] Fig.30 In the CG settings, five PUSCHs are set for each CG cycle. The PUSCH set in the CG settings is used to send UL data and PUSCH additional request information. Using MAC, the MAC SDU containing UL data and the MAC CE containing PUSCH additional request information are multiplexed. Any PUSCH set in the CG settings can be used to send PUSCH additional request information. Fig.30 In the first PUSCH in the first cycle of CG, additional request information for PUSCH is sent in the fourth PUSCH in the second cycle of CG.

[0327] exist Fig.30 In the first cycle of CG, additional request information for two PUSCHs is sent. In the second cycle of CG, additional request information for one PUSCH is sent. The additional request information for PUSCH may include, for example, offset information. In the first cycle of CG, the first PUSCH includes information indicating no offset, such as an offset value of 0, together with additional request information for two PUSCHs. In the second cycle of CG, the fourth PUSCH includes information indicating offset information, such as information of k time slots, together with additional request information for one PUSCH. Fig.30 In the example, k=1.

[0328] The gNB can identify whether to receive scheduled PUSCH in addition to the PUSCH set by the CG by receiving information about the additional request for PUSCH from the UE. Fig.30 In the first period of CG, the gNB receives two PUSCHs in addition to the PUSCH set by the CG. In the second period of CG, the gNB receives one PUSCH in addition to the PUSCH set by the CG. At this time, the offset value is considered.

[0329] When receiving a request for adding PUSCH from a UE, the gNB does not allocate the additional PUSCH resources to other UEs.

[0330] Therefore, for each CG period, in addition to the multiple PUSCHs set in the CG settings, one or more PUSCHs can be added. PUSCHs can be added based on the request of the UE. Therefore, the number of PUSCHs in each period of the CG can be added. Resource allocation that is more suitable for changes in UL data generation timing and data volume can be performed. The ability to achieve delay time reduction and improved resource utilization efficiency.

[0331] Implementation method 5. As disclosed in Implementation 1, as a characteristic of XR traffic, for example, it has non-integer periodicity, but in the previous SPS or CG, since the period is N milliseconds (N is a positive integer), the data generation timing and the resource allocation timing deviate, and it is necessary to wait for the data to be sent and received until the next period. Therefore, it is not suitable for the characteristics of XR traffic and will cause an increase in delay time. In addition, when a delay occurs in the data and exceeds the required delay amount, the data is discarded, resulting in deterioration of communication quality. In this Implementation 5, a method for solving this problem is disclosed.

[0332] In this method, an offset value is applied to the SPS period every n periods (n is a positive integer) set by the SPS. The gNB sends information about the offset value added to the SPS period to the UE. As the information, a combination of n, an offset value, information determining the period to which the offset value is added in every n periods, such as number (k), and information determining the PDSCH to which the resource allocation timing is staggered by applying the offset value in every n periods, such as number (m) can be used. k and / or m are not limited to one, and can also be multiple. RRC signaling can be used as a method for sending the information from the gNB to the UE. For example, it can be included in the RRC reconfiguration and sent. For example, the information can be included in the setting of the SPS and sent. As another method, the information can be included in the DCI and sent. The information can be included in the DCI for activation / deactivation indication of the SPS and sent. The PDCCH can be used to send the DCI. The UE receives the information from the gNB. It is good that the UE can recognize the setting of the SPS and add the offset value every few SPS periods. The UE can receive the PDSCH in the SPS period to which the offset value is added. This makes it possible to flexibly set the SPS period according to the type of service and the generation status of DL data.

[0333] Although it is disclosed that information about the offset value added to the SPS period is sent from the gNB to the UE, it can also be statically determined in advance by standards, etc. as another method. It is possible to strive to simplify the processing and reduce malfunctions.

[0334] Fig.31: is a diagram showing an example of resource allocation when an offset value is added to the SPS period every n periods set by the SPS. The shaded quadrilaterals represent the PDCCH, and the white quadrilaterals represent the PDSCH. The horizontal axis represents the time domain, and the vertical axis represents the frequency domain. Fig.31 In the SPS setting, one PDSCH is set. Multiple PDSCHs can be set. The SPS is set from the gNB to the UE using RRC signaling, and the activation / deactivation of the SPS is notified using the PDCCH. Fig.31 In the example, an offset is set to represent the case where n=3 and k=1. For example, instead of k=1, m=2 may be set. The unit of the offset value may be a time unit, a symbol unit, a time slot unit, a subframe unit, a radio frame unit, a TTI (Transmission Timing Interval) unit, or a combination thereof.

[0335] Fig.31 The time interval between the first and second PDSCHs set by the SPS is the interval in which the offset value is added to the SPS period. The time interval between the second and third PDSCHs is the SPS period, and the time interval between the third and fourth PDSCHs is the SPS period. Similarly, the time interval between the fourth and fifth PDSCHs set by the SPS is the interval in which the offset value is added to the SPS period. The time interval between the fifth and sixth (not shown) PDSCHs is the SPS period, and the time interval between the sixth and seventh PDSCHs is the SPS period. Repeat this setting of applying an offset value to the kth period every n. The gNB sends the PDSCH at the timing of adding the offset value every n SPS periods. The UE receives the PDSCH using the information received from the gNB about the offset value added to the SPS period.

[0336] In this way, by adding an offset value every n periods, the gNB can make adjustments suitable for the generation timing of DL data. Even if the generation timing of DL data is non-integer periodicity, for example, the transmission delay time of DL data can be reduced by adding an appropriate offset value every n periods. Therefore, it is possible to reduce the situation where DL data is discarded due to the transmission delay time of DL data exceeding the requested delay amount. It is possible to reduce the degradation of communication quality.

[0337] Embodiment 5 Variation 1 Other methods for solving the problem disclosed in Implementation Example 5 are disclosed. The gNB notifies the UE of the offset value added to the period set by the SPS. The offset value can be notified every n SPS periods. MAC signaling can be used to send the offset value from the gNB to the UE. For example, it can be included in the MAC CE for transmission. The MAC CE can be sent using the PDSCH set in the SPS setting. In the case of sending DL data using the PDSCH set in the SPS setting, the DL data and the offset value can be multiplexed. The multiplexing can be performed by the MAC. In the case of not sending DL data using the PDSCH set in the SPS setting, only the offset value can be sent.

[0338] Although it is disclosed that the offset value added to the period set by the SPS is sent from the gNB to the UE, as another method, the offset value may be pre-set and information on whether the offset value is added may be sent. The method of pre-setting the offset value from the gNB to the UE may appropriately apply the method for sending information about the offset value disclosed in Implementation Example 5. The method for sending information on whether the offset value is added may appropriately apply the method for sending the offset value disclosed above. In this way, the amount of information sent at regular intervals can be reduced.

[0339] Fig.32 : is a diagram showing an example of resource allocation when notifying an offset value added to a period set by SPS. The shaded quadrilaterals represent PDCCHs, and the white quadrilaterals represent PDSCHs. The horizontal axis represents the time domain, and the vertical axis represents the frequency domain. Fig.32 In the SPS setting, a PDSCH is set. The SPS is set from the gNB to the UE using RRC signaling, and the activation / deactivation of the SPS is notified using PDCCH.

[0340] exist Fig.32 In the embodiment, the offset value is sent from the gNB to the UE using the first PDSCH set by the SPS. The MAC SDU containing the DL data and the MAC CE containing the offset value are multiplexed and sent. As a result, the transmission timing of the second PDSCH becomes the timing with the offset value added to the SPS period. The offset value is not sent in the second PDSCH. As a result, the transmission timing of the third PDSCH becomes the timing of the SPS period. The offset value is not sent in the third PDSCH. As a result, the transmission timing of the fourth PDSCH becomes the timing of the SPS period. The offset value is sent using the fourth PDSCH. As a result, the transmission timing of the fifth PDSCH becomes the timing with the offset value added to the SPS period. In this way, when the offset value is added to the SPS period, the offset value is notified from the gNB to the UE.

[0341] The gNB transmits the PDSCH at the SPS period or at the timing of the SPS period plus an offset value. The UE receives the PDSCH at the SPS period without receiving the offset value from the gNB, and receives the PDSCH at the timing of the SPS period plus the offset value when receiving the offset value from the gNB. Thus, the gNB can dynamically add an offset value to the SPS period, and the UE can derive the PDSCH timing by receiving the offset value from the gNB. The UE can receive the PDSCH.

[0342] The gNB can use MAC signaling to notify the UE of a combination of information such as information determining the period to which the offset value is added every n periods, such as number (k), and information determining the PDSCH to which the resource allocation timing is staggered by applying the offset value every n periods, such as number (m). This information can be included in the MAC CE together with the offset value for notification.

[0343] In this way, by dynamically adding an offset value, the gNB can make adjustments suitable for the generation timing of DL data. Even if, for example, the generation timing of DL data is non-integer periodicity, the transmission delay time of DL data can be reduced by setting an appropriate offset value. In addition, even if the generation period of DL data varies in time, the transmission delay time of DL data can be reduced by dynamically setting an appropriate offset. Therefore, it is possible to reduce the situation where DL data is discarded because the transmission delay time of DL data exceeds the requested delay amount. The degradation of communication quality can be reduced.

[0344] Implementation 5 Variation 2 Disclosed are other methods for solving the problem disclosed in Implementation Example 5. In the setting of SPS, PDCCH is set every n SPS periods. The gNB sends information about the setting of PDCCH to the UE. As the information, n, the number (k) of the period in which the PDCCH is sent every n periods, and a combination of these information are used. k is not limited to one, but may be multiple. As the information about the setting of PDCCH, the setting information of PDCCH disclosed in Implementation Example 1 can be used. The method for sending this information from the gNB to the UE can appropriately apply the method for sending information about the offset value added to the SPS period disclosed in Implementation Example 5. As a result, the UE can receive the PDCCH set every n SPS periods.

[0345] The gNB notifies the UE of the offset value added to the period set by the SPS. The offset value may be notified every n SPS periods. As a method for sending the offset value from the gNB to the UE, the PDCCH disclosed above is used. For example, it may be included in the DCI for transmission. The DCI is transmitted using the PDCCH disclosed above.

[0346] Although it is disclosed that the offset value added to the period set by the SPS is sent from the gNB to the UE, as another method, the offset value may be pre-set and information on whether the offset value is added may be sent. The method of pre-setting the offset value from the gNB to the UE may appropriately apply the method for sending information about the offset value disclosed in Implementation Example 5. The method for sending information on whether the offset value is added may appropriately apply the method for sending the offset value disclosed above. In this way, the amount of information sent at regular intervals can be reduced.

[0347] Fig.33 : is a diagram showing an example of resource allocation when using PDCCH to notify the offset value added to the period set by SPS. The shaded quadrilateral represents PDCCH, and the white quadrilateral represents PDSCH. The horizontal axis represents the time domain, and the vertical axis represents the frequency domain. Fig.33 In the SPS setting, PDCCH is set for every n SPS periods. PDCCH is sent from gNB to UE every n SPS periods. Fig.33 , the case where n=3 and k=2 is shown. The PDCCH is transmitted in the second period of every three SPS periods. The offset value applied to the SPS period is transmitted by the PDCCH.

[0348] exist Fig.33 In the second period set by the SPS, the PDCCH is sent, and the offset value is sent. Thus, the sending timing of the second PDSCH becomes the timing with the offset value added to the first SPS period. The sending timing of the first and third PDSCHs is the timing set by the SPS. Similarly, the PDCCH is sent in the fifth period set by the SPS, and the offset value is sent. Thus, the sending timing of the fifth PDSCH becomes the timing with the offset value added to the fourth SPS period. The sending timing of the fourth and sixth (not shown) PDSCHs is the timing set by the SPS.

[0349] The gNB transmits the offset value using the configured PDCCH. The UE receives the PDSCH in the SPS period without receiving the offset value from the gNB, and receives the PDSCH at the timing of adding the offset value to the SPS period when receiving the offset value from the gNB. Thus, the gNB can dynamically add the offset value to the SPS period, and the UE can derive the PDSCH timing by receiving the offset value from the gNB. The UE can receive the PDSCH.

[0350] Fig.34 : is a diagram showing another resource allocation example when using PDCCH to notify the offset value added to the period set by SPS. The shaded quadrilateral represents PDCCH, and the white quadrilateral represents PDSCH. The horizontal axis represents the time domain, and the vertical axis represents the frequency domain. Fig.34In the SPS setting, PDCCH is set every n SPS periods. PDCCH is sent from gNB to UE every n SPS periods. Fig.34 , the case where n=3 and k=1 is shown. The PDCCH is transmitted in the first cycle of every three SPS cycles. The offset value applied to the SPS cycle is transmitted by the PDCCH.

[0351] The number (k) of the period for notifying the offset value may be different from the number of the PDSCH for which the offset value is applied to stagger the resource allocation timing. The information for determining the PDSCH for which the offset value is applied to stagger the resource allocation timing may be the number of the PDSCH for which the offset value is applied to stagger the resource allocation timing, or may be an offset from the number of the period for sending the offset value. The information is sent from the gNB to the UE. The method for sending the information for determining the PDSCH for which the offset value is applied to stagger the resource allocation timing may appropriately apply the method for notifying the offset value. The information for determining the PDSCH for which the offset value is applied to stagger the resource allocation timing may be notified together with the offset value.

[0352] exist Fig.34 In the method, the notified offset value is applied to the PDSCH allocated in the next SPS period. The period for notifying the offset value is numbered 1, and the PDSCH for which the resource allocation timing is staggered by applying the offset value is numbered 2. Fig.34 In the first cycle set by the SPS, the PDCCH is sent, and the offset value is sent using the PDCCH. As a result, the sending timing of the second PDSCH becomes the timing with the offset value added to the SPS cycle. The sending timing of the first and third PDSCHs is the timing set by the SPS. Similarly, the PDCCH is sent in the fourth cycle set by the SPS, and the offset value is sent using the PDCCH. As a result, the sending timing of the fifth PDSCH becomes the timing with the offset value added to the SPS cycle. The sending timing of the fourth and sixth (not shown) PDSCHs is the timing set by the SPS.

[0353] In this way, by setting PDCCH every n times and notifying the offset value using PDCCH, the gNB can make adjustments suitable for the generation timing of DL data. In addition, by sending the offset value using PDCCH, the UE can obtain the offset value as early as possible. Even if, for example, the generation timing of DL data is non-integer periodicity, the transmission delay time of DL data can be reduced by setting an appropriate offset value every n periods. Therefore, it is possible to reduce the situation where DL data is discarded because the transmission delay time of DL data exceeds the requested delay amount. The degradation of communication quality can be reduced.

[0354] In the figures shown in Implementation 5 to Implementation 5 Variation 2, examples of positive offset values ​​are disclosed. The offset value may not be a positive value. It may also be a negative value. In the case of a negative value, the resource allocation timing of the PDSCH to which the offset value is applied is offset before the offset value.

[0355] In Implementation Example 5 to Implementation Example 5 Variation 2, it is shown that the resource allocation timing of the PDSCH when the offset value is not applied is after the SPS period from the resource allocation timing of the previous PDSCH. As another method, an offset value based on the timing assigned from the SPS setting period can also be set. In other words, only the resource allocation timing of the PDSCH to which the offset value is applied is staggered by the offset value, and the resource allocation timing of other PDSCHs is set to the resource allocation timing based on the period assigned by the SPS setting. For example, in Implementation Example 5, the SPS period set in the SPS setting is set to 8ms, and the offset value is set to 1ms. In addition, the resource allocation timing of the first PDSCH is set to 0ms. When n=3 and k=2, the first PDSCH resource allocation timing is 0ms, the second PDSCH resource allocation timing is 7ms, and the third PDSCH resource allocation timing is 16ms. As a result, only the second PDSCH resource allocation timing can be staggered. It is possible to appropriately schedule a variety of DL data generation modes.

[0356] Implementation method 6. Disclosed is another method for solving the problem disclosed in Implementation Example 5. An offset value is added to the CG period every n periods set by the CG. The gNB sends information about the offset value added to the SPS period to the UE. As the information, a combination of n, an offset value, information determining the period to which the offset value is added in every n periods, such as a number (k), and information determining the PUSCH to which the resource allocation timing is staggered by applying the offset value in every n periods, such as a number (m) can be used. k and / or m are not limited to one and can also be multiple. RRC signaling can be used as a method for sending the information from the gNB to the UE. For example, it can be included in the RRC reconfiguration for transmission. For example, the information can be included in the CG setting for transmission. As another method, the information can be included in the DCI for transmission. The information can be included in the DCI for activation / deactivation indication of the CG for transmission. PDCCH can be used for sending the DCI. The UE receives information from the gNB. The UE can recognize the CG setting and can add the offset value every few CG periods. The UE can send the PUSCH in the CG period to which the offset value is added. Therefore, the CG period can be flexibly set according to the service type and the generation status of UL data.

[0357] Although it is disclosed that information about the offset value added to the CG period is sent from the gNB to the UE, it can also be statically determined in advance by standards, etc. as another method. It is possible to strive to simplify the processing and reduce malfunctions.

[0358] Fig.35 This is a diagram showing an example of resource allocation when an offset value is added to the CG period every n periods set by the CG. The shaded rectangles represent PDCCH, and the white rectangles represent PUSCH. The horizontal axis represents the time domain, and the vertical axis represents the frequency domain. Fig.35 In the CG setting, one PUSCH is set. Multiple PUSCHs can be set. The CG is set from the gNB to the UE using RRC signaling, and the activation / deactivation of the CG is notified using PDCCH. Fig.35 In the example, an offset is set to represent the case where n=3 and k=1. For example, instead of k=1, m=2 may be set. The unit of the offset value may be a time unit, a symbol unit, a time slot unit, a subframe unit, a radio frame unit, a TTI (Transmission Timing Interval) unit, or a combination thereof.

[0359] Fig.35 The time interval between the first and second PUSCHs set by the CG is the interval in which the offset value is added to the CG period. The time interval between the second and third PUSCHs is the CG period, and the time interval between the third and fourth PUSCHs is the CG period. Similarly, the time interval between the fourth and fifth PUSCHs set by the CG is the interval in which the offset value is added to the CG period. The time interval between the fifth and sixth (not shown) PUSCHs is the CG period, and the time interval between the sixth and seventh (not shown) PUSCHs is the CG period. Repeat this setting of applying an offset value to the kth period every n periods. The UE sends PUSCH at a timing in which the offset value is added to every n CG periods. The gNB receives PUSCH at a timing in which the offset value is added to every n CG periods.

[0360] In this way, by adding an offset value every n periods, the gNB can make an adjustment suitable for the generation timing of UL data. Even if the generation timing of UL data is non-integer periodicity, for example, the transmission delay time of UL data can be reduced by adding an appropriate offset value every n periods. Therefore, it is possible to reduce the situation where UL data is discarded due to the transmission delay time of UL data exceeding the requested delay amount. It is possible to reduce the degradation of communication quality.

[0361] Embodiment 6 Variation 1 Other methods for solving the problem disclosed in Implementation Example 5 are disclosed. The UE requests the gNB to add an offset value to the period set by the CG. Information about the offset request may also be notified every n CG periods. The information about the offset request may be information indicating a request to add an offset value to the CG period, an offset value, or a combination thereof. MAC signaling may be used to send information about the offset request from the UE to the gNB. For example, it may be included in a MAC CE for sending. The MAC CE may be sent using the PUSCH set in the CG setting. In the case of sending UL data using the PUSCH set in the CG setting, the UL data and the information about the offset request may be multiplexed. The multiplexing may be performed by the MAC. In the case of not sending UL data using the PUSCH set in the CG setting, only the information about the offset request may be sent.

[0362] Although it is disclosed that information is sent from the UE to the gNB regarding a request for an offset value to be added to the period set by the CG, as another method, the offset value may be pre-set and information on whether to add the offset value may be sent. The method of pre-setting the offset value from the gNB to the UE may appropriately apply the method for sending information on the offset value disclosed in Implementation Example 6. The method for sending information on whether to add the offset value may appropriately apply the method for sending information on the offset value request disclosed above. In this way, the amount of information sent at regular intervals can be reduced.

[0363] Fig.36 : is a diagram showing an example of resource allocation when notifying a request to add an offset value to a period set by the CG. The shaded rectangle represents the PDCCH, and the white rectangle represents the PUSCH. The horizontal axis represents the time domain, and the vertical axis represents the frequency domain. Fig.36 In the CG setting, a PUSCH is set. The CG is set from the gNB to the UE using RRC signaling, and the activation / deactivation of the CG is notified using PDCCH.

[0364] Information about the offset request is sent from the UE to the gNB using the first PUSCH set by the CG. The MAC SDU containing the UL data and the MAC CE containing the offset value are multiplexed and sent. As a result, the transmission timing of the second PUSCH becomes the timing with the offset value added to the CG cycle. The offset value is not sent in the second PUSCH. As a result, the transmission timing of the third PUSCH becomes the timing of the CG cycle. The offset value is not sent in the third PUSCH. As a result, the transmission timing of the fourth PUSCH becomes the timing of the CG cycle. The offset value is sent using the fourth PUSCH. As a result, the transmission timing of the fifth PUSCH becomes the timing with the offset value added to the CG cycle. In this way, when the offset value is notified from the UE to the gNB, the offset value is added to the CG cycle.

[0365] The UE receives PUSCH in the CG period without sending information about the offset request to the gNB, and receives PUSCH at the timing with the offset value added to the CG period when the information about the offset request is sent to the gNB. The gNB receives PUSCH in the CG period without receiving information about the offset request from the UE, and receives PUSCH at the timing with the offset value added to the CG period when the information about the offset request is received from the UE. Thus, the offset value can be dynamically added to the CG period according to the offset request of the UE. The gNB can derive the PUSCH timing by sending information about the offset request to the gNB by the UE. The gNB can receive the PUSCH sent by the UE after adding the offset value to the CG period.

[0366] The UE may notify the gNB of a combination of information such as a number (k) etc., which determines the period to which the offset value is added every n periods, and information such as a number (m) etc., which determines the PDSCH to which the resource allocation timing is staggered by applying the offset value every n periods. This information may be included in the MAC CE together with the offset value for notification.

[0367] In this way, the UE dynamically notifies the gNB of the offset request, so that the UE can make adjustments suitable for the generation timing of the UL data. Even if, for example, the generation timing of the UL data is non-integer periodicity, the transmission delay time of the UL data can be reduced by requesting an appropriate offset and adjusting the CG period. In addition, even if the generation period of the UL data varies in time, the transmission delay time of the UL data can be reduced by dynamically requesting an appropriate offset and adjusting the CG period. Therefore, the situation in which the UL data is discarded due to the transmission delay time of the UL data exceeding the requested delay amount can be reduced. The degradation of communication quality can be reduced.

[0368] Implementation 6 Variation 2 Disclosed are other methods for solving the problem disclosed in Implementation Example 5. In the setting of the CG, the PDCCH is set every n CG cycles. The gNB sends information about the setting of the PDCCH to the UE. As the information, n, the number (k) of the period for sending the PDCCH in every n periods, and a combination of these information are used. k is not limited to one, but can be multiple. The number (k) of the period for sending the PDCCH is set to the number of the PUSCH that staggers the resource allocation timing by applying an offset value. As information about the setting of the PDCCH, the setting information of the PDCCH disclosed in Implementation Example 1 can be used. The method for sending this information from the gNB to the UE can appropriately apply the method for sending information about the offset value added to the CG period disclosed in Implementation Example 6. Thereby, the UE can receive the PDCCH set every n SPS periods.

[0369] The gNB notifies the UE of the offset value added to the period set by the CG. The offset value can be notified every n CG periods. As a method for sending the offset value from the gNB to the UE, the PDCCH disclosed above is used. For example, it can be included in the DCI for transmission. The DCI is sent using the PDCCH disclosed above.

[0370] Although it is disclosed that an offset value added to the period set by the CG is sent from the gNB to the UE, as another method, the offset value may be pre-set and information on whether the offset value is added may be sent. The method of pre-setting the offset value from the gNB to the UE may appropriately apply the method for sending information about the offset value disclosed in Implementation Example 6. The method for sending information on whether the offset value is added may appropriately apply the method for sending the offset value disclosed above. In this way, the amount of information sent at regular intervals can be reduced.

[0371] Fig.37 This is a diagram showing an example of resource allocation when using PDCCH to notify an offset value added to the period set by the CG. The shaded rectangles represent PDCCH, and the white rectangles represent PUSCH. The horizontal axis represents the time domain, and the vertical axis represents the frequency domain. Fig.37 In the CG setting, PDCCH is set every n CG cycles. PDCCH is sent from gNB to UE every n CG cycles. Fig.37 In FIG. 1 , the case where n=3 and k=2 is shown. PDCCH is transmitted in the second cycle every three CG cycles. The offset value applied to the CG cycle is transmitted by PDCCH.

[0372] The UE can set the period for monitoring the PDCCH. For example, it can be a specified period before the PUSCH transmission timing of the CG period. The gNB can send the PDCCH monitoring period to the UE. The method for sending the PDCCH monitoring period from the gNB to the UE can appropriately apply the above-mentioned PDCCH setting information sending method. It can be included in the PDCCH setting and sent. Fig.37 In the CG period in which PDCCH is set, the PDCCH monitoring period is set.

[0373] exist Fig.37In the second period set by the CG, the PDCCH is sent, and the offset value is sent using the PDCCH. Since the UE receives the PDCCH, it monitors the PDCCH during the PDCCH monitoring period. The UE can receive the offset value by receiving the PDCCH. As a result, the transmission timing of the second PUSCH becomes the timing with the offset value added to the first CG period. The transmission timing of the first and third PUSCHs is the CG period. Similarly, the PDCCH is sent in the fifth period set by the CG, and the offset value is sent using the PDCCH. Since the UE receives the PDCCH, it monitors the PDCCH during the PDCCH monitoring period. The UE can receive the offset value by receiving the PDCCH. As a result, the transmission timing of the fifth PUSCH becomes the timing with the offset value added to the fourth CG period. The transmission timing of the fourth and sixth (not shown) PUSCHs is the CG period.

[0374] The gNB uses the configured PDCCH to send the offset value. The UE receives the PUSCH in the CG period when the offset value is not received from the gNB, and receives the PUSCH at the timing of the CG period plus the offset value when the offset value is received from the gNB. The gNB receives the PUSCH in the CG period when the offset value is not sent, and receives the PUSCH at the timing of the CG period plus the offset value when the offset value is sent. As a result, the gNB can receive the PUSCH sent by the UE at the timing with the offset value added.

[0375] The number (k) of the period for notifying the PDCCH can be made different from the number of the PUSCH for which the offset value is applied to stagger the resource allocation timing. The information for determining the PDSCH for which the offset value is applied to stagger the resource allocation timing can be the number of the PUSCH for which the offset value is applied to stagger the resource allocation timing, or it can be the offset from the number of the period for sending the PDCCH. The information is sent from the gNB to the UE. The method for sending the information for determining the PUSCH for which the offset value is applied to stagger the resource allocation timing can appropriately apply the notification method for the setting of the PDCCH. Other methods for sending the information for determining the PDSCH for which the offset value is applied to stagger the resource allocation timing can appropriately apply the method for sending the offset value. It can be sent using the PDCCH. The information for determining the PDSCH for which the offset value is applied to stagger the resource allocation timing can be notified together with the offset value.

[0376] For example, let n=3, k=1. Therefore, PDCCH is sent in the first period set by CG, and the offset value and the offset of PDSCH that staggers the resource allocation timing by applying the offset value are sent using the PDCCH. For example, if the offset of PDSCH that staggers the resource allocation timing by applying the offset value is set to 1, the sending timing of the second PUSCH is the timing with the offset value added to the first CG period. The sending timing of the first and third PUSCHs is the CG period. Similarly, PDCCH is sent in the fourth period set by CG, and the offset value and the offset of PDSCH that staggers the resource allocation timing by applying the offset value are sent using the PDCCH. Similarly, if the offset of PDSCH that staggers the resource allocation timing by applying the offset value is set to 1, the sending timing of the fifth PUSCH is the timing with the offset value added to the fourth CG period. The sending timing of the fourth and sixth PUSCHs is the CG period.

[0377] In this way, by setting the PDCCH every n times and notifying the offset using the PDCCH, the gNB can make adjustments suitable for the generation timing of the UL data. In addition, by sending the offset value using the PDCCH, the UE can obtain the offset value as early as possible. Even if, for example, the generation timing of the UL data is non-integer periodicity, the transmission delay time of the UL data can be reduced by setting an appropriate offset value every n periods. Therefore, the situation in which the UL data is discarded due to the transmission delay time of the UL data exceeding the requested delay amount can be reduced. The degradation of communication quality can be reduced.

[0378] In the figures shown in Implementation 6 to Implementation 6 Variation 2, examples of positive offset values ​​are disclosed. The offset value may not be a positive value. It may also be a negative value. In the case of a negative value, the resource allocation timing of the PUSCH to which the offset value is applied is offset before the offset value.

[0379] In Embodiment 6 to Embodiment 6 Variation 2, it is shown that the resource allocation timing of the PUSCH when the offset value is not applied is from the resource allocation timing of the previous PUSCH to after the CG period. As another method, an offset value based on the timing assigned from the CG setting period may also be set. In other words, only the resource allocation timing of the PUSCH to which the offset value is applied is shifted by an amount corresponding to the offset value, and the resource allocation timing of other PUSCHs is set to the resource allocation timing based on the period assigned by the CG setting. For example, in Embodiment 6, the CG period set in the CG setting is set to 8ms, and the offset value is set to 1ms. In addition, the resource allocation timing of the first PUSCH is set to 0ms. When n=3 and k=2, the first PUSCH resource allocation timing is 0ms, the second PUSCH resource allocation timing is 7ms, and the third PUSCH resource allocation timing is 16ms. Thus, only the second PUSCH resource allocation timing can be staggered. It is possible to appropriately schedule a variety of UL data generation modes.

[0380] Implementation method 7. Sometimes, mobility processing is performed between cells through the movement of UE. In the mobility processing from the mobile source cell to the mobile target cell, the UE implements RA (Random Access) processing in order to synchronize the mobile target cell. In addition, for example, in the case where the gNB with the mobile source cell (source gNB (S-gNB)) and the gNB with the mobile target cell (target gNB (T-gNB)) are different, in the mobility processing, DL data is transmitted from the S-gNB to the T-gNB. The DL data after the transmission processing is buffered in the T-gNB until the UE and the gNB complete the RA processing and resume data communication. In this way, in the inter-cell mobility, due to the RA processing and transmission processing, the DL data transmission timing in the T-gNB is different from the DL data transmission timing in the S-gNB. Therefore, even if the SPS setting is set to a setting suitable for the DL data transmission timing in the S-gNB, it may sometimes be different from the DL data transmission timing in the T-gNB, resulting in a delay in the transmission of DL data.

[0381] In addition, UL data is also buffered in the UE until RA processing is performed in the UE and gNB and data communication is resumed. In this way, in inter-cell mobility, the UL data transmission timing to the T-gNB is different from the UL data transmission timing to the S-gNB due to RA processing. Therefore, there is a problem that even if the CG setting is set to a setting suitable for the UL data transmission timing of the S-gNB, it may sometimes be different from the UL data transmission timing to the T-gNB, resulting in a delay in the transmission of UL data.

[0382] In this seventh embodiment, a method for solving such a problem is disclosed.

[0383] In this method, T-gNB sends DL data in the buffer to UE using dynamic scheduling. T-gNB performs dynamic scheduling on the UE after RA processing with the UE of the mobile object. T-gNB schedules PDSCH for DL ​​data transmission through PDCCH. UE receives dynamic grant after RA processing with T-gNB. UE monitors PDCCH after RA processing with T-gNB and receives PDCCH including scheduling information for this UE. UE receives scheduling information included in PDCCH and receives DL data using PDSCH indicated by the scheduling information.

[0384] Therefore, during mobile processing, the DL data in the buffer of T-gNB can be sent to the UE as early as possible.

[0385] T-gNB uses dynamic scheduling to send UL data in the UE's buffer to the UE. T-gNB performs dynamic scheduling on the UE after RA processing with the UE of the mobile object. T-gNB schedules PUSCH for UL data transmission through PDCCH. UE receives dynamic grant after RA processing with T-gNB. UE monitors PDCCH after RA processing with T-gNB and receives PDCCH including scheduling information for this UE. UE receives scheduling information contained in PDCCH and sends UL data on PUSCH.

[0386] Therefore, during mobile processing, the UE's UL data in the buffer can be sent to the T-gNB as early as possible.

[0387] SR can be sent from UE to T-gNB. For example, UE can send SR during or after RA processing. T-gNB that receives SR performs dynamic scheduling on UE.

[0388] The SR from the UE to the T-gNB may not be required. For example, in the case where a bearer such as XR that periodically generates UL data is set, the SR from the UE to the T-gNB may not be required in the mobile processing. The SR from the UE to the T-gNB may not be required in the RA processing in the mobile processing or after the RA processing. In the case where a bearer that periodically generates UL data is set, in the mobile processing, the T-gNB dynamically schedules the UE without receiving the SR. Even in the case where the SR is not sent to the T-gNB when a bearer such as one that periodically generates UL data is set, the UE only needs to monitor the PDCCH from the T-gNB. As a result, the T-gNB can schedule the PUSCH for the UE as early as possible.

[0389] Although it is disclosed that a case where SR is not required in mobile processing is a case where a bearer such as UL data is periodically generated is set, other methods are disclosed. Information indicating whether SR is required in mobile processing is sent from the T-gNB to the UE. For example, in mobile processing, the message is included in the HO REQUEST ACK message sent from the T-gNB to the S-gNB, and the message is included in the RRC re-configuration message sent from the S-gNB to the UE. Thus, the T-gNB can set whether SR is required.

[0390] T-gNB may also continue dynamic scheduling after RA processing until CORESET is set for UE from T-gNB. Alternatively, it may continue until SPS is set for UE from T-gNB. Alternatively, T-gNB may continue dynamic scheduling until CG is set for UE. Alternatively, dynamic scheduling may continue until the transmission of DL data stored in the buffer in the mobile processing in T-gNB is completed. It is possible to avoid UE from continuing to monitor PDCCH for dynamic scheduling after RA processing. The capability diagram realizes low power consumption of UE.

[0391] Other methods for solving the problems disclosed in Implementation Example 7 are disclosed. During mobile processing, the S-gNB deactivates the set SPS and / or CG. The S-gNB sends the deactivation of SPS and / or CG to the UE. The UE that receives the deactivation of SPS and / or CG from the S-gNB stops the processing of SPS and / or CG. The UE does not release the settings of SPS and / or CG. The T-gNB activates the settings of the deactivated SPS and / or CG during or after RA processing. The T-gNB sends the deactivation of SPS and / or CG to the UE. The UE that receives the deactivation of SPS and / or CG from the T-gNB performs the processing of SPS and / or CG again.

[0392] A notification method for deactivation of SPS and / or CG from S-gNB to UE is disclosed. The notification may use RRC signaling. For example, in mobile processing, the notification may be included in the RRC reconfiguration sent from S-gNB to UE. It is possible to notify together with the indication of mobile processing. As another method, PDCCH may be used for the notification. The deactivation of SPS and / or CG may be included in DCI for notification. It may be dynamically notified according to the timing of deactivation. As another method, the notification may use MAC signaling. For example, the deactivation of SPS and / or CG may be included in MAC CE and sent using PDSCH set by SPS. The UE does not need to receive PDCCH, and processing becomes easy.

[0393] Thus, the deactivation of SPS and / or CG from the S-gNB to the UE can be notified. The UE can receive the deactivation of SPS and / or CG from the S-gNB to the UE. In mobile processing, the deactivation of SPS and / or CG becomes possible.

[0394] A notification method for deactivation of SPS and / or CG from T-gNB to UE is disclosed. The notification may use RRC signaling. For example, RRC reconfiguration is sent from T-gNB to UE after RA processing. The notification may be sent by including it in the RRC reconfiguration. T-gNB can reliably notify after connecting with the UE. As another method, the notification may use PDCCH. Deactivation of SPS and / or CG may be included in DCI for notification. It may be dynamically notified according to the timing of deactivation.

[0395] Thus, the deactivation of SPS and / or CG can be notified from T-gNB to UE. UE can receive the deactivation of SPS and / or CG from T-gNB. In mobile processing, the deactivation of SPS and / or CG becomes possible.

[0396] Although it is set to notify the UE of the deactivation and activation of SPS and / or CG, as another method, it can be set to automatically implement the deactivation and / or activation without notification. In the case of mobile processing, it can also be set to automatically deactivate and activate SPS and / or CG for the UE that is the object of mobile processing. For example, the conditions for implementing deactivation and activation can also be statically determined in advance based on standards, etc. As a result, there is no need to notify the UE. The ability to reduce the signaling load.

[0397] As a result, SPS and / or CG can be performed by T-gNB without releasing the SPS and / or CG set by S-gNB. Therefore, SPS and / or CG can be performed by T-gNB for UE as early as possible. In mobile processing, DL data or UL data in the buffer of T-gNB or UE can be sent as early as possible.

[0398] Disclosed are other methods for solving the problem disclosed in this embodiment 7. During mobile processing, the set SPS and / or CG settings are released. The S-gNB can send a release of the SPS and / or CG settings to the UE. The UE that receives the release of the SPS and / or CG settings from the S-gNB releases the SPS and / or CG settings. The release can be performed even without a notification from the S-gNB. For example, the conditions for releasing the settings can also be statically determined in advance based on a standard, etc.

[0399] T-gNB sets SPS and / or CG in RA processing based on mobile processing or after RA processing. T-gNB notifies UE of the setting of SPS and / or CG. In addition, T-gNB notifies UE of the activation of SPS and / or CG. The UE that receives the SPS and / or CG setting and activation from T-gNB performs SPS and / or CG processing.

[0400] A method for setting SPS and / or CG for a UE by a T-gNB through mobile processing is disclosed. In the mobile processing, the T-gNB sends the setting of SPS and / or CG to the UE via the S-gNB. The T-gNB includes the setting in the HO REQUEST ACK and sends it to the S-gNB. The S-gNB includes the setting received from the T-gNB in ​​the RRC re-setting and sends it to the UE. The UE receives the setting of SPS and / or CG from the T-gNB from the S-gNB. In the case where activation / deactivation of SPS and / or CG is required, the T-gNB can use the PDCCH to send the activation / deactivation of SPS and / or CG to the UE after the RA processing based on the mobile processing. The UE monitors the PDCCH after the RA processing with the T-gNB and receives the activation / deactivation of SPS and / or CG using the PDCCH. As a result, the UE can perform the processing of SPS and / or CG using the T-gNB.

[0401] A method for setting SPS and / or CG for a UE by a T-gNB through mobile processing is disclosed. In the mobile processing, the T-gNB sends the setting of SPS and / or CG to the UE via the S-gNB. The T-gNB includes the setting in the HO REQUEST ACK and sends it to the S-gNB. The S-gNB includes the setting received from the T-gNB in ​​the RRC re-setting and sends it to the UE. The UE receives the setting of SPS and / or CG from the T-gNB from the S-gNB. In the case where activation / deactivation of SPS and / or CG is required, the T-gNB can use the PDCCH to send the activation / deactivation of SPS and / or CG to the UE after the RA processing based on the mobile processing. The UE monitors the PDCCH after the RA processing with the T-gNB and receives the activation / deactivation of SPS and / or CG using the PDCCH. As a result, the UE can perform the processing of SPS and / or CG using the T-gNB.

[0402] In the method in which T-gNB sends the settings of SPS and / or CG to UE via S-gNB in ​​mobile processing, since the settings are performed before the feedforward processing and RA processing in mobile processing, there is a problem of timing offset in the transmission of DL data or UL data. In order to solve such problems, other methods in which T-gNB sets SPS and / or CG for UE through mobile processing are disclosed. In mobile processing, T-gNB sends the settings of SPS and / or CG to UE. After RA processing with the UE, T-gNB sends RRC resetting to the UE. The setting can be included in the RRC resetting and sent. T-gNB can reliably notify after connecting with the UE.

[0403] When activation / deactivation of SPS and / or CG is required, T-gNB sends SPS and / or CG settings to UE using RRC signaling, and then uses PDCCH to send activation / deactivation of SPS and / or CG. After receiving SPS and / or CG settings from T-gNB, UE monitors PDCCH and receives activation / deactivation of SPS and / or CG using PDCCH. As a result, UE can use T-gNB to perform SPS and / or CG processing.

[0404] In a method in which the T-gNB sends the setting of SPS and / or CG to the UE after RA processing in mobile processing, a problem occurs that the SPS and / or CG cannot be used before the setting is performed. In order to solve such a problem, another method in which the T-gNB sets the SPS and / or CG to the UE through mobile processing is disclosed.

[0405] In other methods, in mobile processing, T-gNB sends the settings of SPS and / or CG to UE in RA processing. In this transmission, MSG2 in RA processing can also be used. In MSG2, MAC signaling can be used. For example, T-gNB includes the settings of SPS and / or CG in MAC CE and sends it to UE using MSG2. It is sufficient to send the activation / deactivation of the settings together with the settings of SPS and / or CG. Alternatively, the transmission of the settings of SPS and / or CG can serve as the activation of the settings. The UE receives the settings of SPS and / or CG in the RA processing with T-gNB. Thus, in the RA processing, SPS and / or CG can be set between T-gNB and UE. The gNB can use the SPS and / or CG set by T-gNB for DL ​​data transmission and reception or UL data transmission and reception with the UE.

[0406] In the setting of SPS and / or CG, T-gNB can take into account the deviation of the transmission timing of DL data or UL data caused by the feedforward processing and RA processing in the mobile processing. In addition, since SPS and / or CG are set in the RA processing, the UE of the mobile processing object can receive the setting of SPS and / or CG as early as possible. By using MSG2 processed by RA, the setting of SPS and / or CG can be received at the earliest timing when the UE can communicate with T-gNB. As a result, SPS and / or CG can be used when sending and receiving DL data or UL data between the UE and T-gNB. Therefore, the delay caused by the deviation of the transmission timing of DL data or UL data in the mobile processing can be reduced.

[0407] As another method, in mobile processing, T-gNB can send SPS and / or CG settings to UE via S-gNB, and T-gNB can send correction information of SPS and / or CG settings to UE in RA processing. The sending method can apply the above-disclosed method. Use MSG2 to send.

[0408] An offset value may also be set as correction information. The T-gNB adds the offset value to the start timing of the SPS set via the S-gNB. The UE that receives the offset value from the T-gNB adds the offset value to the start timing of the SPS and / or CG received via the S-gNB. Alternatively, the offset value may be added to the resource allocation timing of the SPS and / or CG just after the offset value is received instead of the start timing.

[0409] Thus, T-gNB can correct the settings of SPS and / or CG by taking into account the deviation of the transmission timing of DL data or UL data caused by the feedforward processing and RA processing in the mobile processing. T-gNB sends the correction information of SPS and / or CG settings to the UE in the RA processing, so that the UE can receive the correction information of SPS and / or CG settings as early as possible. By using MSG2 processed by RA, the correction information of SPS and / or CG settings can be received at the earliest timing when the UE can communicate with T-gNB. Thus, the correction information of SPS and / or CG settings can be used when sending and receiving DL data or UL data between the UE and T-gNB. Therefore, the delay caused by the deviation of the transmission timing of DL data or UL data in the mobile processing can be reduced. In addition, only the correction information of SPS and / or CG settings needs to be sent in MSG2, which can reduce the amount of information sent. In addition, the processing time of MSG2 can be shortened.

[0410] Fig.38This is a diagram showing a sequence example of mobile processing in which correction information for setting SPS and / or CG is sent in RA processing. In step ST3801, data communication is performed between UPF, S-gNB, and UE. SPS and / or CG may also be set between S-gNB and UE. Data communication may also be performed using this setting. In step ST3802, the UE performs measurement and reports the measurement result to the S-gNB in ​​step ST3803. In step ST3804, the S-gNB determines the switching (HO: Hand Over) of the UE as a mobile processing to the T-gNB. In step ST3805, the S-gNB sends a HO REQUEST to the T-gNB. The HO REQUEST may include the setting of SPS and / or CG. The setting may also include the setting information disclosed in Embodiment 1 to Embodiment 6 Variation 2. Thus, the T-gNB can recognize the setting of SPS and / or CG performed in the S-gNB. In step ST3806, the T-gNB performs admission control. The T-gNB sets the SPS and / or CG for the UE of the mobile object. When making this setting, the setting of the SPS and / or CG based on the S-gNB received from the S-gNB can also be considered. In step ST3807, the T-gNB sends a HO REQUEST ACK to the S-gNB. The HOREQUEST ACK includes the setting of the SPS and / or CG performed by the T-gNB. In step ST3808, the S-gNB notifies the UE of the mobile processing setting indication. This notification can be made using RRC resetting. The RRC resetting includes the setting of the SPS and / or CG performed by the T-gNB received from the T-gNB. The UE can use the setting of the SPS and / or CG in the communication with the T-gNB. The S-gNB that sent the mobile processing setting indication to the UE in step ST3808 sends the data transmission status to the T-gNB in ​​step ST3809. It is sent using SN STATUS TRANSFER. In step ST3810, the S-gNB starts transmitting the DL data received from the UPF to the T-gNB. The T-gNB that receives the DL data transmitted from the S-gNB buffers the DL data in step ST3811. The T-gNB buffers the DL data until data communication with the UE is possible. The UE that received the mobile processing setting indication in step ST3808 starts mobile processing to the T-gNB. In step ST3812, the UE sends PRACH to start T-gNB and RA processing. In step ST3813, the T-gNB that received the PRACH sends MSG2 to the UE. The T-gNB may include correction information for the settings of the SPS and / or CG in MSG2. The correction information for the settings may also include correction information for the settings disclosed in Embodiments 1 to 6, Variation 2.When the T-gNB receives PRACH from the UE, it derives the time required until the RA processing is completed. In order to adjust the time, the correction information of the SPS and / or CG settings can also be derived. The correction information can also be, for example, an offset value added to the start timing of the SPS and / or CG received via the above-mentioned S-gNB. Thus, considering the deviation in the transmission timing of the transmission processing based on the mobile processing and the RA processing, the settings of the SPS and / or CG in the T-gNB are adjusted to the SPS and / or CG suitable for the transmission timing in the T-gNB. The UE that receives the correction information of the SPS and / or CG settings in step ST3813 applies the correction to start the SPS and / or CG.

[0411] In step ST3814, the UE sends RRC reconfiguration completion to the T-gNB. In step ST3815, the UE performs data communication with the T-gNB, and the SPS and / or CG to which the correction information received in step ST3813 is applied are used in the data communication. In step ST3816, the T-gNB sends UL data to the UPF. In steps ST3817 and ST3818, a path switch is performed between the T-gNB, the AMF, and the UPF. In step ST3819, an end marker is sent from the UPF to the T-gNB via the S-gNB to notify the end of the data transmission. In step ST3820, DL data is sent from the UPF to the T-gNB. As a result, data is also sent and received in DL and UL between the UE, the T-gNB, and the UPF. In step ST3821, the AMF sends a PATH SWITCH REQUEST ACK to the T-gNB. In step ST3822, the T-gNB sends a UE CONTEXT RELEASE to the S-gNB.

[0412] The method disclosed above in which the T-gNB sends correction information of the settings of SPS and / or CG to the UE during RA processing can also be appropriately applied to the method of deactivating the SPS and / or CG set by the S-gNB and activating them by the T-gNB during mobile processing. The T-gNB can send the activation of SPS and / or CG and the correction information of the settings to the UE. The UE uses the activation of SPS and / or CG received from the T-gNB and the SPS and / or CG modified using the correction information of the settings to send and receive DL data or UL data.

[0413] By performing such a mobile process, it is possible to reduce a delay caused by a deviation in the transmission timing of DL data or UL data in the mobile process.

[0414] By using the method disclosed in this embodiment, it is possible to implement scheduling that takes into account the transmission processing of DL data in the mobile processing of UE and the deviation of the transmission timing of DL data or UL data caused by the RA processing between UE and gNB. Therefore, even if the mobile processing is performed, the delay caused by the transmission of DL data or UE data can be reduced. It is possible to reduce the situation where the transmission delay time of DL data or UL data exceeds the requested delay amount and is discarded. It is possible to reduce the degradation of communication quality.

[0415] In the present disclosure, it is recorded as gNB or cell, but unless otherwise specified, it can be either gNB or cell.

[0416] In the present disclosure, the gNB can be either MCG or SCG. In addition, the method disclosed in Implementation 7 can also be applied to the change of PSCell. The same effect can be obtained when the PSCell is changed.

[0417] The UE may notify the gNB of the preference information related to the CG setting. The preference information about the CG setting includes CG period, offset, time domain resource allocation, frequency domain resource allocation, etc. The preference information may also be the information disclosed in Implementation 2 to Implementation 2 Variation 3, Implementation 4 to Implementation 4 Variation 4, Implementation 6 to Implementation 6 Variation 2, and Implementation 7. It may also be a combination of them. The gNB receives the preference information related to the CG setting from the UE, so that the UE can identify the preferred CG setting.

[0418] The above-mentioned embodiments and their modifications are merely examples, and the embodiments and their modifications can be freely combined. In addition, arbitrary structural elements of the embodiments and their modifications can be appropriately changed or omitted.

[0419] For example, in each of the above embodiments and their variations, a subframe is an example of a time unit for communication in a fifth generation communication system. A time slot may be a scheduling unit. In each of the above embodiments and their variations, processing recorded in time slot units may be performed in TTI units, subframe units, sub-time slot units, and micro-time slot units.

[0420] For example, the methods disclosed in the above embodiments and their variations can be applied to IAB, can be applied to the communication between the IAB host and the IAB node, and can also be applied to the processing of using Uu in IAB.

[0421] For example, the methods disclosed in the above embodiments and their variations can be applied to SL communication. For example, they can be applied to communication between UE and NW via relay. They can be applied to communication between UE and NW based on L2 relay.

[0422] For example, the methods disclosed in the above embodiments and their variations are not limited to V2X (Vehicle-to-everything) services, but can also be applied to services using SL communication. For example, they can be applied to SL communication used in various services such as proximity-based services, public safety, communication between wearable terminals, and communication between devices in factories.

[0423] Hereinafter, each aspect of the present disclosure will be collectively described as a supplementary note.

[0424] (Note 1) A base station capable of periodic communication of sending and receiving data with a communication terminal at a predetermined period, characterized in that: When downlink data is transmitted to the communication terminal in the periodic communication, a physical downlink control channel and a physical downlink shared channel used in a first period as a transmission period of the downlink data are allocated, the physical downlink shared channel used in the first period is changed according to a change in the amount of downlink data transmitted to the communication terminal, and the communication terminal is notified of the result of the change through the physical downlink control channel allocated to the first period, When uplink data is received from the communication terminal in the periodic communication, a physical downlink control channel and a physical uplink shared channel used in a second period which is a transmission period of the uplink data are allocated, and according to a change in the amount of uplink data sent by the communication terminal, the physical uplink shared channel used in the second period is changed, and the communication terminal is notified of the result of the change via the physical downlink control channel allocated to the second period. (Note 2) A base station capable of periodic communication of sending and receiving data with a communication terminal at a predetermined period, characterized in that: When downlink data is transmitted to the communication terminal in the periodic communication, a physical downlink control channel and a physical downlink shared channel used in a first period which is a transmission period of the downlink data are allocated, the physical downlink shared channel used in the first period is changed according to a change in the amount of downlink data transmitted to the communication terminal, and the communication terminal is notified of the result of the change through the physical downlink shared channel allocated to the first period, When uplink data is received from the communication terminal in the periodic communication, a physical downlink control channel and a physical uplink shared channel used in a second period which is a transmission period of the uplink data are allocated, and according to a change in the amount of uplink data sent by the communication terminal, the physical uplink shared channel used in the second period is changed, and the communication terminal is notified of the result of the change via the physical downlink control channel allocated to the second period. (Note 3) The base station as described in Note 1 or 2 is characterized in that: When the downlink data is generated periodically, an offset value based on the relationship between the generation period of the downlink data and the first period is added to the first period to reduce the deviation between the generation timing of the downlink data and the transmission timing of the downlink data. (Note 4) The base station as described in Note 1, 2 or 3, is characterized in that: When the uplink data is generated periodically, an offset value based on the relationship between the generation period of the uplink data and the second period is added to the second period to reduce the deviation between the generation timing of the uplink data and the transmission timing of the uplink data. (Note 5) A communication system, characterized in that: comprising a plurality of base stations as described in any one of Notes 1 to 4, When a communication terminal connected to a first base station that is one of the plurality of base stations switches a connection destination to a second base station that is one of the plurality of base stations, The second base station allocates a physical downlink control channel and a physical downlink shared channel used in a sending period of downlink data to a connection target switching terminal, and allocates a physical downlink control channel and a physical uplink shared channel used in a sending period of uplink data of the connection target switching terminal, and notifies the connection target switching terminal via the first base station of the allocation results of the physical downlink control channel and the physical downlink shared channel used in sending downlink data to the connection target switching terminal and the allocation results of the physical downlink control channel and the physical uplink shared channel used by the connection target switching terminal in sending uplink data, wherein the connection target switching terminal is a communication terminal that switches the connection target. Description of symbols

[0425] 202 Communication terminal device (mobile terminal) 210 Communication System 213, 240-1, 240-2, 750 base station device (NR base station, base station) 214 5G Core Department 215 Central Unit 216 Dispersed Units 217 Central unit for control layer 218 Central unit for user layer 219TRP 301, 403 protocol processing department 302 Application Department 304, 405 Coding Department 305, 406 Modulation Department 306, 407 frequency conversion unit 307-1~307-4、408-1~408-4 Antenna 308, 409 Demodulation Unit 309, 410 Decoding Department 310, 411, 526 control unit 401 EPC Communications Department 402 Other base station communication department 412 5GC Communications Department 521 Data Network Communications Department 522 Base Station Communication Department 523 User Layer Communication Department 523-1PDU Processing Unit 523-2 Mobile anchoring unit 525 Control layer control department 525-1NAS Security Department 525-2 Idle Mobility Management Department 527 Session Management Department 527-1PDU Session Control Unit 527-2UE IP address allocation department 751-1~751-8 beam Community 752.

Claims

1. A base station capable of periodic communication of sending and receiving data with a communication terminal at a predetermined period, characterized in that: When downlink data is transmitted to the communication terminal in the periodic communication, a physical downlink control channel and a physical downlink shared channel used in a first period as a transmission period of the downlink data are allocated, the physical downlink shared channel used in the first period is changed according to a change in the amount of downlink data transmitted to the communication terminal, and the communication terminal is notified of the result of the change through the physical downlink control channel allocated to the first period, When uplink data is received from the communication terminal in the periodic communication, a physical downlink control channel and a physical uplink shared channel used in a second period which is a transmission period of the uplink data are allocated, and according to a change in the amount of uplink data sent by the communication terminal, the physical uplink shared channel used in the second period is changed, and the communication terminal is notified of the result of the change via the physical downlink control channel allocated to the second period.

2. A base station capable of periodic communication of sending and receiving data with a communication terminal at a predetermined period, characterized in that: When downlink data is transmitted to the communication terminal in the periodic communication, a physical downlink control channel and a physical downlink shared channel used in a first period which is a transmission period of the downlink data are allocated, the physical downlink shared channel used in the first period is changed according to a change in the amount of downlink data transmitted to the communication terminal, and the communication terminal is notified of the result of the change through the physical downlink shared channel allocated to the first period, When uplink data is received from the communication terminal in the periodic communication, a physical downlink control channel and a physical uplink shared channel used in a second period which is a transmission period of the uplink data are allocated, and according to a change in the amount of uplink data sent by the communication terminal, the physical uplink shared channel used in the second period is changed, and the communication terminal is notified of the result of the change via the physical downlink control channel allocated to the second period.

3. The base station according to claim 1 or 2, characterized in that: When the downlink data is generated periodically, an offset value based on the relationship between the generation period of the downlink data and the first period is added to the first period to reduce the deviation between the generation timing of the downlink data and the transmission timing of the downlink data.

4. The base station according to claim 1 or 2, characterized in that: When the uplink data is generated periodically, an offset value based on the relationship between the generation period of the uplink data and the second period is added to the second period to reduce the deviation between the generation timing of the uplink data and the transmission timing of the uplink data.

5. A communication system, characterized in that: comprising a plurality of base stations as claimed in claim 1 or 2, When a communication terminal connected to a first base station that is one of the plurality of base stations switches a connection destination to a second base station that is one of the plurality of base stations, The second base station allocates a physical downlink control channel and a physical downlink shared channel used in a sending period of downlink data to a connection target switching terminal, and allocates a physical downlink control channel and a physical uplink shared channel used in a sending period of uplink data of the connection target switching terminal, and notifies the connection target switching terminal via the first base station of the allocation results of the physical downlink control channel and the physical downlink shared channel used in sending downlink data to the connection target switching terminal and the allocation results of the physical downlink control channel and the physical uplink shared channel used by the connection target switching terminal in sending uplink data, wherein the connection target switching terminal is a communication terminal that switches the connection target.

Images