Terminal, base station and communication method

Abstract

A terminal is provided with: a control circuit for individually determining the activation and deactivation of semi-static transmission / reception for each of a plurality of bands in a manner in which transmission directions are set for each of the plurality of bands obtained by dividing a frequency band; and a communication circuit that transmits or receives a signal in accordance with the determination of activation and deactivation.

Description

Technical Field

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

[0002] The 3rd Generation Partnership Project (3GPP) has completed the planning and formulation of the physical layer specifications of NR (New Radio access technology) of Release 17 as a functional extension of the fifth generation mobile communication system (5G). In NR, in order to meet the requirements of high speed and large capacity, in addition to the realization of enhanced mobile broadband (eMBB), it also supports the realization of ultra-reliable and low-latency communication (URLLC) (for example, refer to non-patent documents 1-6).

[0003] Prior art literature

[0004] Non-patent literature

[0005] Non-patent document 1: 3GPP TS 38.211 V17.2.0, "NR; Physical channels and modulation (Release 17)," June 2022

[0006] Non-patent document 2: 3GPP TS 38.212 V17.2.0, "NR; Multiplexing and channel coding (Release 17)," June 2022

[0007] Non-patent document 3: 3GPP TS 38.213 V17.2.0, "NR; Physical layer procedure for control (Release 17)," June 2022

[0008] Non-patent document 4: 3GPP TS 38.214 V17.2.0, "NR; Physical layer procedures for data (Release 17)," June 2022

[0009] Non-patent document 5: 3GPP TS 38.215 V17.1.0, "NR; Physical layer measurements (Release 17)," June 2022

[0011] Non-patent document 6: 3GPP TS 38.331 V17.1.0, "NR; Radio Resource Control (RRC) protocol specification (Release 17)", June 2022 Summary of the invention

[0012] However, there is still room for research on the notification method of resource allocation in wireless communications.

[0013] The non-limiting embodiments of the present disclosure contribute to providing a terminal, a base station, and a communication method capable of appropriately notifying resource allocation.

[0014] A terminal according to an embodiment of the present disclosure includes: a control circuit that determines whether to enable or disable semi-static transmission and reception for each of the plurality of bands formed by dividing a frequency band, in a manner in which transmission directions are set for each of the plurality of bands; and a communication circuit that transmits or receives a signal according to the determination of enabling or disabling.

[0015] It should be noted that these general or specific aspects may be implemented by a system, an apparatus, a method, an integrated circuit, a computer program or a recording medium, or may be implemented by any combination of systems, apparatuses, methods, integrated circuits, computer programs and recording media.

[0016] According to one embodiment of the present disclosure, resource allocation can be properly notified.

[0017] More advantages and effects of an embodiment of the present disclosure will be explained through the description and drawings. These advantages and / or effects are provided by several embodiments, and the features described in the description and drawings, but not necessarily all of them need to be provided in order to obtain one or more of the same features. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Figure 1 This is a diagram showing an example of a duplex system.

[0019] Figure 2 This is a diagram showing an example of subband non-overlapping full duplex (SBFD: subband non-overlapping full duplex).

[0020] Figure 3 It is a diagram showing an example of SBFD.

[0021] Figure 4 It is a diagram showing an example of SBFD.

[0022] Figure 5 This is a block diagram showing a configuration example of a part of a base station.

[0023] Figure 6 This is a block diagram showing a configuration example of a part of a terminal.

[0024] Figure 7 It is a block diagram showing a structural example of a base station.

[0025] Figure 8 This is a block diagram showing a structural example of a terminal.

[0026] Fig. 9 It is a sequence diagram showing an operation example of a base station and a terminal.

[0027] Fig.10 It is a diagram showing an example of the format of downlink control information (DCI: Downlink Control Information).

[0028] Fig.11 This is a diagram showing an example of a state for notifying whether semi-static transmission and reception is enabled or disabled.

[0029] Fig.12 This is a diagram showing an example of the relationship between time slots / code symbols and states.

[0030] Fig.13 It is a diagram showing an example of SBFD.

[0031] Fig.14 This is a diagram showing an example of a slot format indicator (SFI).

[0032] Fig.15 It is a diagram showing an example of SBFD.

[0033] Fig.16 It is a diagram showing an example of SFI.

[0034] Fig.17 It is a diagram showing an example of SBFD.

[0035] Fig.18 is a diagram of an exemplary architecture of a 3GPP NR system.

[0036] Fig.19It is a schematic diagram showing the functional separation between NG-RAN (Next Generation-Radio Access Network) and 5GC (5th Generation Core).

[0037] Fig. 20 This is a sequence diagram of the procedure of setting / resetting a radio resource control (RRC) connection.

[0038] Fig.21 It is a schematic diagram showing the utilization scenarios of large-capacity high-speed communications (eMBB: enhanced Mobile Broadband), multiple simultaneous machine-type communications (mMTC: massive Machine Type Communications) and high-reliability and ultra-low latency communications (URLLC: Ultra Reliable and Low Latency Communications).

[0039] Fig. 22 is a block diagram representing an exemplary 5G system architecture for non-roaming scenarios.

[0040] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings. DETAILED DESCRIPTION

[0041] [Notice about the delivery direction]

[0042] For example, downlink (DL), uplink (UL), and flexible can be set as the transmission direction of each symbol. For example, flexible can be overwritten to either downlink or uplink and used.

[0043] The settings of the codeword transmission direction include, for example, a semi-statically set cell-specific UL / DL configuration, a semi-statically set UE-specific UL / DL configuration, and a dynamically set slot format indicator (SFI).

[0044] The semi-statically configured cell-specific UL / DL configuration and UE-specific UL / DL configuration may be sent to a terminal (eg, UE: User Equipment) via, for example, higher layer signaling (eg, Radio Resource Control (RRC) signaling).

[0045] The SFI may be sent to the terminal, for example, via a downlink control channel (e.g., PDCCH: Physical Downlink Control Channel). For example, downlink control information (DCI: Downlink Control Information) used to send the SFI may also be in DCI format 2_0. The bit position and bit size of the field on the DCI format 2_0 for sending the SFI may be set by RRC signaling.

[0046] In addition, the fields of SFI can be shared among multiple terminals (UEs). The slot format is a format that defines the transmission direction of each symbol in a slot, and the slot format of multiple slots can also be transmitted in SFI.

[0047] [About semi-static transmission and reception]

[0048] Semi-statically configured transmission / reception (semi-static transmission / reception, configured transmission / reception) can configure channels and signals through RRC signaling.

[0049] For example, semi-static transmission (e.g., configured transmission) may be configured for an uplink data channel (e.g., a physical uplink shared channel (PUSCH)), an uplink control channel (e.g., a physical uplink control channel (PUCCH)), a random access channel (e.g., a random access channel (RACH)), or a sounding reference signal (e.g., a sounding reference signal (SRS)). For example, as a semi-static transmission configured for PUSCH, there is a configured grant (CG).

[0050] In addition, for example, semi-static reception (e.g., configured reception) can be set for a downlink data channel (e.g., a physical downlink shared channel (PDSCH: Physical Downlink Shared Channel)), a downlink control channel (PDCCH), and a channel state information reference signal (e.g., a channel state information reference signal (CSI-RS: Channel State Information-Reference Signal)). For example, as a semi-static reception set for PDSCH, there is semi-persistent scheduling (SPS: Semi-persistent scheduling).

[0051] For example, there may be a case where semi-static transmission and reception are set for flexible symbols that are set semi-statically. In this case, the base station (e.g., gNB) can use SFI to control whether the terminal actually transmits and receives in semi-static transmission and reception. That is, the base station can control the transmission and reception of the terminal in semi-static transmission and reception through dynamic signaling.

[0052] In the following, actually performing transmission and reception in semi-static transmission and reception is expressed as “enabled”, “allowed” or “required”. In addition, not actually performing transmission and reception in semi-static transmission and reception is expressed as “disabled”, “canceled” or “not required”.

[0053] For example, for a flexible symbol set semi-statically, when the SFI notifies the terminal of "uplink" or "255", semi-static transmission can be enabled. In addition, for example, for a flexible symbol set semi-statically, when the SFI notifies the terminal of "downlink" or "flexible", semi-static transmission can be disabled.

[0054] In addition, for example, for a flexible symbol set semi-statically, when "downlink" or "255" is notified to the terminal by SFI, semi-static reception can be enabled. In addition, for example, for a flexible symbol set semi-statically, when "uplink" or "flexible" is notified to the terminal by SFI, semi-static reception can be disabled.

[0055] In addition, the time slot format of the time slot notified by SFI "255" is based on the semi-static setting. For example, in the time slot notified by SFI "255", the transmission direction of each codeword can be set based on the setting of the cell-specific UL / DL setting and the UE-specific UL / DL setting. At this time, unless the transmission direction is different from the semi-static setting through DCI scheduling, semi-static transmission and reception is effective.

[0056] Additionally, for PDCCH, reception is enabled even on symbols notified by SFI as "flexible".

[0057] [About Sub-Band Non-Overlapping Full-Duplex (SBFD)]

[0058] "Study on evolution of NR duplex operation" has been approved as a study item for Release 18. One of the main topics of this study item is the response to subband non-overlapping full duplex (or, also known as "SBFD", "cross-division duplex (XDD)").

[0059] Figure 1 is a diagram showing an example of a duplex system. Figure 1 In the figure, the vertical axis represents frequency and the horizontal axis represents time. Figure 1 In the figure, “U” represents uplink transmission and “D” represents downlink transmission.

[0060] Figure 1 (a) shows an example of time division duplex (TDD) of half duplex. Figure 1 In (a), UE#1 and UE#2 are terminals connected to a base station (e.g., gNB). Figure 1 In the half-duplex shown in (a), the transmission direction in a certain time resource can be common between the base station and the terminal. For example, in a certain time resource, the transmission direction does not differ between the terminals.

[0061] Figure 1 (b) represents an example of SBFD. In SBFD, frequency resources (or, frequency band) are divided into multiple bands (for example, also called "subbands", "RB sets (RB set)", "subband domains", "sub-BWP (Bandwidth part)") to support transmission in different directions (for example, downlink or uplink) of subband units. It should be noted that in SBFD, the terminal performs transmission and reception of one of the uplink and downlink in a certain time resource, and does not perform transmission and reception of the other. On the other hand, in SBFD, the base station can transmit and receive uplink and downlink at the same time. In addition, there may be a situation where the terminal does not use the resources of the transmission direction in a certain time resource (for example, Figure 1 (b) The situation of resources represented by dotted lines).

[0062] [About semi-static transmission and reception in SBFD]

[0063] One method of implementing SBFD is, for example, a method using flexible symbols that are set semi-statically.

[0064] A flexible symbol set semi-statically may become either an uplink symbol or a downlink symbol according to, for example, the SFI. Therefore, SBFD can be realized by notifying different terminals of different transmission directions from the base station.

[0065] By using flexible symbols set semi-statically, the terminal can perform SBFD without knowing the time resources and frequency resources of the subband (for example, SBFD can be implemented through transparent transmission or transparent method). For example, through transparent transmission control of SBFD, the base station can choose whether to apply SBFD (for example, whether to allocate subbands to symbols) according to the communication environment (for example, DL and UL business loads, the necessity of uplink coverage, the requirement for delay, etc.), thereby increasing the degree of freedom of scheduling and thus improving resource utilization efficiency.

[0066] Figure 2 An example of applying SBFD to flexible symbols set semi-statically is shown. Figure 2 In the , flexible codewords are semi-statically set in time slots #1, #2, and #3. PDCCH (or, DCI) is used to dynamically schedule PDSCH in time slot #1 and PUSCH in time slot #2. In addition, the action based on semi-persistent scheduling (SPS) in time slot #2 (for example, also called "SPS reception") is semi-static reception, and SPS uses PDSCH. In addition, the action based on setting authorization (CG) in time slot #3 (for example, also called "CG transmission") is semi-static transmission, and CG uses PUSCH.

[0067] In this way, by using dynamic scheduling and semi-static configuration on flexible symbols that are semi-statically configured, it is possible to implement SBFD operation.

[0068] [About enabling / disabling semi-static transmission and reception in SBFD]

[0069] When using semi-static transmission and reception in SBFD, there may be situations where semi-static transmission and reception cannot be enabled / disabled correctly. Figure 3 The settings shown are examples of preconditions.

[0070] exist Figure 3 In the time slot #1, #2, and #3, flexible symbols are semi-statically set. Figure 3 In time slot #2 of , SPS reception for UE #1 and CG transmission for UE #2 are semi-statically set. Figure 3 In time slot #2 of UE#3, reception of PDSCH (DG-PDSCH: Dynamic Grant PDSCH) dynamically scheduled by PDCCH is configured for UE#3. Here, UE#1, UE#2, and UE#3 are configured to monitor the same DCI format 2_0 (eg, the same SFI).

[0071] In for Figure 3 In the case of enabling / disabling semi-static transceiver as shown in the premise application, there may be at least the following four situations (for example, Figure 4 ).

[0072] (Case 1) When both SPS and CG are enabled

[0073] By notifying "255" using SFI, both SPS and CG can be enabled. After notifying the terminal of "255" using SFI, the transmission direction of the codeword becomes a flexible codeword according to the semi-statically set UL / DL setting. Therefore, in this case, unless the DCI schedules a transmission direction different from the semi-static transmission and reception, the semi-static transmission and reception is valid. In addition, in the flexible codeword, the dynamically scheduled transmission and reception is valid, so the terminal can receive the DG-PDSCH. That is, the notification of "255" using SFI does not affect the DG-PDSCH reception.

[0074] (Case 2) When both SPS and CG are disabled

[0075] By notifying "Flexible" using SFI, both SPS and CG can be disabled. After "Flexible" is notified to the terminal using SFI, semi-static transmission and reception are disabled. In addition, in the flexible codeword, dynamically scheduled transmission and reception are valid, so the terminal can receive DG-PDSCH. That is, the notification of "Flexible" using SFI does not affect DG-PDSCH reception.

[0076] (Case 3) When SPS is enabled and CG is disabled

[0077] By notifying "downlink" using SFI, SPS can be enabled and CG can be disabled. After notifying the terminal of "downlink" using SFI, semi-static reception is enabled and semi-static transmission is disabled. In the downlink codeword, the terminal can receive the downlink, so it can receive DG-PDSCH. That is, the notification of "downlink" using SFI does not affect DG-PDSCH reception.

[0078] (Case 4) SPS disabled and CG enabled

[0079] By notifying the "uplink" using SFI, it is possible to disable SPS and enable CG. However, after notifying the terminal of the "uplink" using SFI, semi-static reception is disabled and semi-static transmission is enabled, so it is possible to disable SPS and enable CG. On the other hand, it will affect DG-PDSCH reception. For example, when notifying the terminal of the "uplink" using SFI, the terminal does not assume the reception of the downlink in the uplink codeword, so the notification of DG-PDSCH reception is considered to be an error. Therefore, according to the above-mentioned method of enabling / disabling semi-static transmission and reception using SFI, SBFD cannot be controlled in situation 4.

[0080] In the above, an example of enabling / disabling semi-static transmission and reception using SFI is described.

[0081] Thus, there are cases where the semi-static transmission and reception activation / disablement using SFI cannot fully function for SBFD. It should be noted that the above example is only one example, and there are cases where the function cannot be fully realized by the combination of semi-static transmission and reception and dynamically notified transmission and reception.

[0082] In a non-limiting embodiment of the present disclosure, for example, the following method is described, which implements enabling / disabling of semi-static transceiving in SBFD by using a notification associated with a time slot format or SFI.

[0083] [Overview of Communication System]

[0084] A communication system according to one embodiment of the present disclosure may include, for example, Figure 5 and Figure 7 The base station 100 (eg, gNB) and Figure 6 and Figure 8 The terminal 200 (eg, UE) is shown. In the communication system, there may be a plurality of base stations 100 and a plurality of terminals 200, respectively.

[0085] Figure 5 1 is a block diagram showing a configuration example of a portion of a base station 100 according to one embodiment of the present disclosure. Figure 5 In the illustrated base station 100, the control unit (e.g., corresponding to the control circuit) determines whether to enable or disable semi-static transmission and reception by the terminal 200 for each of the plurality of bands (e.g., sub-bands) formed by dividing the frequency band in a method (e.g., SBFD) in which the transmission direction is set for each of the plurality of bands (e.g., sub-bands). The communication unit (e.g., corresponding to the communication circuit) receives or transmits a signal according to the decision of enabling or disabling.

[0086] Figure 6 1 is a block diagram showing a configuration example of a portion of a terminal 200 according to one embodiment of the present disclosure. Figure 6In the terminal 200 shown, the control unit (e.g., control circuit) determines whether to enable or disable semi-static transmission and reception for each of the plurality of bands (e.g., sub-bands) formed by dividing the frequency band in a method (e.g., SBFD) in which the transmission direction is set for each of the plurality of bands (e.g., sub-bands). The communication unit (e.g., corresponding to the communication circuit) includes a communication circuit that transmits or receives a signal based on the determination of enable or disable.

[0087] [Structure of base station]

[0088] Figure 7 1 is a block diagram showing a configuration example of a base station 100 according to one embodiment of the present disclosure. Figure 7 In the present invention, the base station 100 includes a receiving unit 101, a demodulation / decoding unit 102, a scheduling unit 103, a control information retention unit 104, a semi-static transmission and reception control unit 105, a data / control information generation unit 106, a coding / modulation unit 107 and a sending unit 108.

[0089] It should be noted that, for example, at least one of the demodulation / decoding unit 102, the scheduling unit 103, the control information storage unit 104, the semi-static transmission and reception control unit 105, the data / control information generation unit 106, and the encoding / modulation unit 107 may be included in Figure 5 At least one of the control unit, the receiving unit 101 and the sending unit 108 shown in FIG. Figure 5 Communications Department shown.

[0090] The receiving unit 101 performs reception processing such as down-conversion or A / D (Analog / Digital) conversion on a reception signal received via an antenna, and outputs the reception signal after the reception processing to the demodulation / decoding unit 102 .

[0091] The demodulation / decoding unit 102 demodulates and decodes the reception signal (for example, uplink signal) input from the reception unit 101 , for example, and outputs the decoding result to the scheduling unit 103 .

[0092] The scheduling unit 103 can, for example, schedule the terminal 200. The scheduling unit 103 can schedule the transmission and reception of each terminal 200 based on at least one of the decoding result input from the demodulation / decoding unit 102 and the control information input from the control information storage unit 104, and instruct the data / control information generation unit 106 to generate at least one of data and control information. In addition, the scheduling unit 103 outputs information related to scheduling to the semi-static transmission and reception control unit 105, for example. In addition, the scheduling unit 103 can output control information related to scheduling for the terminal 200 to the control information storage unit 104.

[0093] The control information retaining unit 104, for example, retains control information set for each terminal 200. The control information may include, for example, information related to semi-static transmission and reception (for example, information related to time resources and frequency resources for transmission and reception) for each terminal 200. The control information retaining unit 104 may output the retained information to each structural unit of the base station 100 (for example, the scheduling unit 103) as needed.

[0094] For example, the semi-static transmission and reception control unit 105 may instruct the data / control information generation unit 106 to generate control information for enabling and disabling semi-static transmission and reception based on information from the scheduling unit 103 .

[0095] The data / control information generation unit 106 generates at least one of data and control information, for example, according to an instruction from the scheduling unit 103, and outputs a signal including the generated data or control information to the coding / modulation unit 107. In addition, the data / control information generation unit 106 generates control information for enabling and disabling semi-static transceiving, for example, according to an instruction from the semi-static transceiving control unit 105, and outputs a signal including the generated control information to the coding / modulation unit 107. It should be noted that the generated data and control information may include, for example, at least one of high-layer signaling information and downlink control information.

[0096] The coding / modulation unit 107 encodes and modulates the signal (e.g., containing data, control information, or information related to enabling and disabling semi-static transmission and reception) input from the data / control information generation unit 106, and outputs the modulated signal to the transmission unit 108.

[0097] The transmission unit 108 performs transmission processing such as D / A (Digital / Analog) conversion, up-conversion, or amplification on the signal input from the encoding / modulation unit 107, and transmits a wireless signal obtained by the transmission processing to the terminal 200 from the antenna.

[0098] [Terminal structure]

[0099] Figure 8 1 is a block diagram showing a configuration example of a terminal 200 according to one embodiment of the present disclosure. Figure 8 In the embodiment, the terminal 200 includes a receiving unit 201, a demodulation / decoding unit 202, a semi-static transceiver control unit 203, a control unit 204, a control information retention unit 205, a data / control information generation unit 206, a coding / modulation unit 207 and a sending unit 208.

[0100] It should be noted that, for example, at least one of the demodulation / decoding unit 202, the semi-static transmission / reception control unit 203, the control unit 204, the control information storage unit 205, the data / control information generation unit 206, and the encoding / modulation unit 207 may be included in Figure 6 At least one of the control unit, receiving unit 201 and sending unit 208 shown in FIG. Figure 6 Communications Department shown.

[0101] The receiving unit 201 performs reception processing such as down-conversion or A / D conversion on a reception signal received via an antenna, and outputs the reception signal after the reception processing to the demodulation / decoding unit 202 .

[0102] The demodulation / decoding unit 202 demodulates and decodes the received signal input from the receiving unit 201, and outputs the decoding result to the control unit 204. The decoding result may include, for example, high-layer signaling information and downlink control information. In addition, when the decoding result includes information related to enabling and disabling of semi-static transmission and reception (for example, time slot format information, etc.), the demodulation / decoding unit 202 outputs the information to the semi-static transmission and reception control unit 203.

[0103] The semi-static transceiver control unit 203 determines (or identifies, determines) the enabling and disabling of the semi-static transceiver based on the information related to the enabling and disabling of the semi-static transceiver input from the demodulation / decoding unit 202 and the control information (for example, information related to the time resources of the semi-static transceiver) input from the control information retention unit 205, and outputs the determination result (for example, the information on the enabling and disabling of the semi-static transceiver within the time slot) to the control unit 204.

[0104] The control unit 204 can determine whether there is transmission or reception of data or control information based on the information related to the activation and deactivation of semi-static transmission and reception input from the semi-static transmission and reception control unit 203, the control information (for example, information related to the time resource and frequency resource of semi-static transmission and reception) input from the control information retention unit 205, or the decoding result (for example, data or control information) input from the demodulation / decoding unit 202. For example, when the result of the determination is that there is reception of data or control information, the control unit 204 can instruct the receiving unit 201 and the demodulation / decoding unit 202 to receive at least one of the data and control information (not shown). In addition, for example, when the result of the determination is that there is transmission of data or control information, the control unit 204 can instruct the data / control information generation unit 206 to generate at least one of the data and control information.

[0105] The control information storage unit 205 stores the control information input from the control unit 204, for example, and outputs the stored information to each component (for example, the semi-static transmission and reception control unit 203 and the control unit 204) as necessary.

[0106] The data / control information generation unit 206 generates data or control information, for example, according to an instruction from the control unit 204 , and outputs a signal including the generated data or control information to the coding / modulation unit 207 .

[0107] The coding / modulation unit 207 codes and modulates the signal input from the data / control information generation unit 206 , for example, and outputs the modulated transmission signal to the transmission unit 208 .

[0108] The transmission unit 208 performs transmission processing such as D / A conversion, up-conversion, or amplification on the signal input from the encoding / modulation unit 207 , and transmits a wireless signal obtained by the transmission processing to the base station 100 from an antenna.

[0109] [Operations of Base Station 100 and Terminal 200]

[0110] An operation example of the base station 100 and the terminal 200 having the above configuration will be described.

[0111] Fig. 9 It is a sequence diagram showing an operation example of the base station 100 and the terminal 200 .

[0112] exist Fig. 9 In the process, the base station 100 determines information related to configuration, such as a semi-static transmission direction configuration (e.g., a semi-static UL / DL configuration) and a semi-static transmission and reception configuration (e.g., resources and cycle) (S100).

[0113] The base station 100 transmits, for example, higher layer signaling information including the determined setting information to the terminal 200 ( S101 ).

[0114] The base station 100 schedules data transmission and reception for the terminal 200, for example (S102).

[0115] The base station 100, for example, determines the activation and deactivation of semi-static transmission and reception (S103). The base station 100, for example, can determine the activation and deactivation of semi-static transmission and reception by the terminal 200 for each of the plurality of subbands in SBFD. The base station 100, for example, can send information related to the determined activation and deactivation of semi-static transmission and reception to the terminal 200 (S104).

[0116] Terminal 200 determines whether to enable or disable semi-persistent transmission and reception (S105), for example, based on information on the enable or disable of semi-persistent transmission and reception from base station 100. Terminal 200 may determine whether to enable or disable semi-persistent transmission and reception for each of a plurality of subbands in SBFD, for example.

[0117] The terminal 200 may, for example, perform semi-static reception when the semi-static reception is enabled (S106). In addition, the terminal 200 may, for example, perform semi-static transmission when the semi-static transmission is enabled (S107).

[0118] [How to enable / disable semi-static transmission and reception]

[0119] A method of determining whether to enable or disable (hereinafter also referred to as “enable / disable”) semi-persistent transmission and reception in the base station 100 (for example, the scheduling unit 103 and the semi-persistent transmission and reception control unit 105 ) will be described.

[0120] Furthermore, the terminal 200 (for example, the semi-static transmission and reception control unit 203 and the control unit 204 ) may set the decision of enabling / disabling the semi-static transmission and reception performed by the base station 100 , and determine whether to enable or disable the semi-static transmission and reception.

[0121] An example of a method of enabling / disabling semi-static transmission and reception is described below.

[0122] [Method 1]

[0123] In method 1, the base station 100 notifies the enabling / disabling of the semi-static transceiving using information (e.g., "state") indicating the state in which the enabling / disabling of the semi-static transceiving is set. The terminal 200 determines whether to enable / disable the semi-static transceiving, for example, based on the information (state) indicating one of the enabling and disabling states of the semi-static transceiving.

[0124] The status can be notified to the terminal 200 using, for example, a field of a group-common PDCCH (or group-common DCI). In addition, the position and size (e.g., bit position, number of bits) of the status field on the group-common PDCCH can also be set by signaling. In addition, the SFI (e.g., which SFI the status is applied to) to which the status (e.g., the setting of enabling / disabling of semi-static transmission and reception) is applied can also be set by signaling.

[0125] For example, the SFI and status of the application status may also be sent at the same time. For example, in DCI format 2_0, the SFI and status are configured and sent at the same time. Here, the existing SFI may be used as the SFI. Fig.10 This shows an example of using DCI format 2_0 to notify the status. Fig.10 As shown, within the payload of the DCI format 2_0, the status field is set.

[0126] The value of the state corresponds to one of the enabled and disabled states of semi-static transceiving. For example, the state may be applied to semi-static transceiving but not to other transceivings. For example, transceivings dynamically notified by DCI or the like may also not be affected by the state.

[0127] Fig.11 1 is a diagram showing an example of the relationship between the state value and the state of enabling / disabling of semi-static transmission and semi-static reception. Fig.11In the example shown, the state is composed of a 2-bit bit field, and the enable / disable of each of semi-static transmission and semi-static reception is notified in 4 states. It should be noted that 1 bit may be allocated to each of semi-static transmission and semi-static reception and set as another bit field.

[0128] For example, based on any one of the following application methods 1 to 4, a slot or symbol to be enabled / disabled for semi-static transmission and reception according to the state may be determined and applied.

[0129] <Application method 1>

[0130] In application method 1, the state can be applied to the symbols of the slot whose slot format is notified by SFI regardless of the transmission direction. For example, in application method 1, the state can be applied to all downlink, uplink and flexible symbols.

[0131] In addition, in application method 1, the following rules can also be applied.

[0132] Rule 1: Enabling / disabling of semi-static transmission applies to uplink or flexible symbols. For example, semi-static transmission may not be applied to downlink symbols. For example, for downlink symbols, semi-static transmission is always disabled.

[0133] Rule 2: Enable / disable of semi-static reception applies to downlink or flexible symbols. For example, semi-static reception may not be applied to uplink symbols. For example, for uplink symbols, semi-static reception is always disabled.

[0134] By applying the status to all time slots and codewords of the time slot format notified by SFI, in addition to controlling the enabling / disabling of semi-static transmission and reception on flexible codewords, the enabling / disabling of semi-static transmission and reception on downlink codewords and uplink codewords can also be controlled.

[0135] By performing such control, it is possible to enable / disable semi-static transmission and reception on flexible symbols in SBFD. In addition, for downlink symbols and uplink symbols, it is also possible to control the enable / disable of semi-static transmission and reception, thereby increasing the degree of freedom of scheduling and thus improving resource utilization efficiency. For example, when there is no service for a certain terminal 200, the base station 100 can allocate resources to other terminals 200, thereby improving resource utilization efficiency.

[0136] <Application method 2>

[0137] In application method 2, a state may be applied to flexible symbols in a slot whose slot format is notified by SFI.

[0138] When SBFD is performed on flexible symbols, by applying a state to the flexible symbols, it is possible to enable / disable semi-static transmission and reception without affecting the operation of existing symbols.

[0139] In this way, according to application method 2, in SBFD, enabling / disabling of semi-static transmission and reception on flexible symbols can be achieved.

[0140] <Application method 3>

[0141] In application method 3, the status is applied to the symbol of the time slot notified of "255" among the time slots notified by SFI.

[0142] The state may be applied to the semi-statically set flexible symbols in the time slot notified of “255” or to all symbols in the time slot notified of “255.” In the latter case, Rule 1 and Rule 2 of Application Method 1 may be applied.

[0143] Thus, according to the application method 3, for the time slot notified by SFI "255", the semi-static transmission and reception on the flexible symbol can be enabled / disabled in the SBFD. In addition, when the state is applied to all symbols, the enable / disable of static transmission and reception can also be controlled for downlink symbols and uplink symbols.

[0144] <Application method 4>

[0145] In application method 4, a slot format for applying a state is imported, and the state is applied to symbols of the slot notified of the imported slot format.

[0146] For example, "254" may be added as a new time slot format. In addition, "254" is just an example, and other values ​​may be used.

[0147] After the SFI notifies "254", the transmission direction of each symbol can be determined based on the semi-statically configured UL / DL configuration. In addition, for the time slot notified "254" by the SFI, the enablement / disablement of semi-static transmission and reception can be determined depending on the state.

[0148] For example, the difference between the existing "255" in the SFI value and the "254" newly added in the application method 4 is whether to decide whether to enable / disable the semi-static transmission and reception according to the state.

[0149] For example, the state may be applied to semi-statically set flexible symbols in the time slot notified by SFI “254” or to all symbols in the time slot notified by SFI “254”. In the latter case, rules 1 and 2 of application method 1 may be applied.

[0150] Thus, according to the application method 4, for the time slot notified by SFI "254", the semi-static transmission and reception on the flexible symbol can be enabled / disabled in the SBFD. In addition, when the state is applied to all symbols, the enable / disable of static transmission and reception can also be controlled for downlink symbols and uplink symbols.

[0151] In the above, the application methods 1 to 4 of the status are described.

[0152] Fig.12 This section shows an example of applying the status using application methods 1 to 3.

[0153] exist Fig.12 In the , the first to second rows indicate conditions, and the third to fifth rows indicate the results when application methods 1 to 3 are applied respectively. In the first row, the transmission direction of each symbol using the semi-static UL / DL setting is indicated. For each symbol, one of the transmission directions of downlink, flexible, and uplink is semi-statically set. In the second row, the notification of the transmission direction using SFI is indicated. Fig.12 In the example of , the SFI for slots #5, #6, and #7 is notified. In addition, the slot format "255" is applied to all symbols in the slot.

[0154] exist Fig.12 The third, fourth, and fifth rows of respectively represent the symbols of the application status in application method 1, application method 2, and application method 3. It should be noted that application method 4 notifies SFI in time slot units in the same manner as application method 3, and the result is similar to that of application method 3, so it is omitted.

[0155] Fig.13 Indicates that method 1 is applied to situation 4 (for example, refer to Figure 4 ). Fig.13 In the example of the state application method, application method 1 is used. In addition, the relationship between the state value and the enable / disable of semi-static transmission and reception is used. Fig.11 .

[0156] like Fig.13 As shown, in order to comply with the conditions of Case 4 (the case where SPS is disabled and CG is enabled), the base station 100 sets "255" for SFI and "1" for the state (semi-static transmission: enabled, semi-static reception: disabled) for time slot #2. Fig.13 In the time slot #2 notified by SFI "255", semi-static transmission is valid and semi-static reception is invalid. Fig.13In the example, SPS in UE#1 is disabled and CG in UE#2 is enabled. In addition, in the semi-static flexible symbol of the time slot notified by SFI "255", DG-PDSCH reception is valid, so DG-PDSCH reception in UE#3 is not affected. Thus, according to method 1, an action that meets the conditions of situation 4 can be achieved.

[0157] Thus, in method 1, the base station 100 and the terminal 200 set one of the enabling and disabling of semi-static transmission and reception based on the state indicating one of the enabling and disabling states for semi-static transmission and semi-static reception, respectively. Thus, the enabling / disabling of semi-static transmission and reception can be realized in SBFD. By realizing the enabling / disabling of semi-static transmission and reception, the degree of freedom of scheduling can be increased, and the resource utilization efficiency can be improved.

[0158] In addition, in method 1, by applying the status, it is not necessary to change the existing definition and notification method of SFI, so it is possible to enable / disable semi-static transmission and reception without affecting the existing operation.

[0159] [Method 2]

[0160] In method 2, the enable / disable of semi-static transceiving is set using a specific time slot format. For example, the specific time slot format may correspond to either enable or disable of semi-static transceiving.

[0161] In method 2, the base station 100 notifies the activation / disablement of the semi-static transceiving using a time slot format corresponding to one of the activation and the disabling of the semi-static transceiving. The terminal 200 determines the activation / disabling of the semi-static transceiving based on the time slot format corresponding to one of the activation and the disabling of the semi-static transceiving, for example.

[0162] For example, the time slot format described below can be imported.

[0163] New slot format 1: For the configured slots, semi-static reception and transmission and reception dynamically scheduled by DCI, etc. are enabled, while semi-static transmission is disabled. In the new slot format 1, the transmission direction of each symbol can be set based on the semi-statically configured UL / DL configuration, similar to "255".

[0164] New slot format 2: For the configured slots, semi-static transmission and transmission and reception dynamically scheduled by DCI, etc. are enabled, while semi-static reception is disabled. In the new slot format 2, the transmission direction of each symbol can be set based on the semi-statically configured UL / DL configuration, similar to "255".

[0165] The above-mentioned new time slot formats 1 and 2 can both be added to the SFI, or only one of them can be added to the SFI. Fig.14 This shows an example of adding new slot formats 1 and 2 to SFI. Fig.14 Based on Table 11.1.1-1 of TS38.213. Fig.14 In the SFI, the new slot format 1 is added as "253", and the new slot format 2 is added as "254". In addition, in the SFI, "253" and "254" are indices that are not used as "reserved" in the existing slot formats. Fig.14 The "253" and "254" shown are examples, and the new slot format can also be allocated to other indexes.

[0166] exist Fig.14 In the example shown, "253" can be used when semi-static transmission is disabled, and "254" can be used when semi-static reception is disabled. In addition, "255" can be used when both semi-static transmission and semi-static reception are enabled.

[0167] Fig.15 Indicates that method 2 is applied to situation 4 (for example, refer to Figure 4 ) example.

[0168] like Fig.15 As shown, in order to comply with the conditions of Case 4 (the case where SPS is disabled and CG is enabled), the base station 100 sets "254" for time slot #2 using SFI. Fig.15 In the example, for time slot #2 notified by SFI "254", semi-static transmission is valid and semi-static reception is invalid. Fig.15 In the example, SPS in UE#1 is disabled and CG in UE#2 is enabled. In addition, in the semi-static flexible symbol of the time slot notified by SFI "254", DG-PDSCH reception is valid, so DG-PDSCH reception in UE#3 is not affected. Thus, according to method 2, actions that meet the conditions of situation 4 can be implemented.

[0169] Thus, in method 2, the base station 100 and the terminal 200 set one of the enabling and disabling of semi-static transmission and reception based on the time slot format corresponding to one of the enabling and disabling of semi-static transmission and semi-static reception. Thus, the enabling / disabling of semi-static transmission and reception can be realized in SBFD. By realizing the enabling / disabling of semi-static transmission and reception, the degree of freedom of scheduling can be increased and the resource utilization efficiency can be improved.

[0170] In method 1, semi-static transmission and reception are enabled / disabled uniformly for multiple time slots notified by SFI, while in the new time slot format of method 2, enablement and disablement are set (or specified) in time slot units. Therefore, method 2 can further improve the degree of freedom of scheduling.

[0171] [Method 3]

[0172] In method 3, the enable / disable of semi-static transceiving is set using a specific time slot format. For example, the specific time slot format may correspond to one of the enable and disable of semi-static transceiving. Although method 2 describes the case where the enable / disable of semi-static transceiving is set in time slot units, method 3 describes a method of setting the enable / disable of semi-static transceiving in symbol units.

[0173] In method 3, the base station 100 notifies the activation / disablement of the semi-static transceiving using a time slot format corresponding to one of the activation and the disabling of the semi-static transceiving. The terminal 200 determines the activation / disabling of the semi-static transceiving based on the time slot format corresponding to one of the activation and the disabling of the semi-static transceiving, for example.

[0174] For example, the symbol categories described below may be imported.

[0175] New symbol category 1: Semi-static reception and transmission and reception dynamically scheduled by DCI etc. are enabled, while semi-static transmission is disabled. D ”.

[0176] New symbol category 2: Semi-static transmission and transmission and reception dynamically scheduled by DCI etc. are enabled, while semi-static reception is disabled. U ”.

[0177] All of the above new symbol categories may be introduced, or only one of them may be introduced.

[0178] For example, "C D " can also be regarded as limiting the semi-statically transmitted symbol category relative to "F" (flexible symbol). In addition, "C U " can also be viewed as a symbol category that limits semi-static reception relative to "F" (flexible symbol).

[0179] In addition, regarding “C D ” and “C U ", the symbol type can also be overwritten. For example, the semi-statically set "D" (downlink symbol) and "U" (uplink symbol) symbol types cannot be overwritten to "C D ” and “C U In addition, the semi-statically set "F" (flexible symbol) symbol category can be overwritten with "C D " or "C U ”.

[0180] Fig.16 Indicates the addition of "CD ” and “C U An example of a time slot format for ”. Fig.16 Based on Table 11.1.1-1 of TS38.213, and corresponding to the time slot format with newly added index = 56~55+N+M. Fig.16 The "N" indicates that the D "The number of newly added time slot formats, "M" indicates the number of timeslot formats used for "C U "And the number of newly added time slot formats.

[0181] “C D ” and “C U "For example, it is a code element category that limits semi-static transmission or semi-static reception relative to flexible code elements, and its classification is close to flexible code elements. Therefore, for example, as an example of a method for adding a time slot format, it is possible to replace the "F" of the existing time slot format with "C D " or "C U In addition, there are also cases where "F" is used as a gap when transitioning to "D" or "U", so it is not necessary to replace "F" with "C" in all time slot formats. D " or "C U ”.

[0182] Fig.17 Indicates that method 3 is applied to situation 4 (for example, refer to Figure 4 ). Fig.17 In the time slot format, use Fig.16 Example shown.

[0183] like Fig.17 As shown, in order to comply with the conditions of Case 4 (the case where SPS is disabled and CG is enabled), the base station 100 sets "56+N" using SFI for time slot #2. For time slot format = "56+N", semi-static transmission is enabled and semi-static reception is disabled in all symbols. Fig.17 In the time slot #2 notified by SFI "56+N", semi-static transmission is valid and semi-static reception is invalid. Fig.17 In the example, SPS in UE#1 is disabled and CG in UE#2 is enabled. In addition, in the semi-static flexible symbol of the time slot notified by SFI "56+N", dynamic scheduling is effective, so it does not affect the DG-PDSCH reception in UE#3. Therefore, according to method 3, actions that meet the conditions of situation 4 can be achieved.

[0184] Thus, in method 3, the base station 100 and the terminal 200 set one of the enabling and disabling of semi-static transmission and reception based on the time slot format corresponding to one of the enabling and disabling of semi-static transmission and semi-static reception. Thus, the enabling / disabling of semi-static transmission and reception can be realized in SBFD. By realizing the enabling / disabling of semi-static transmission and reception, the degree of freedom of scheduling can be increased and the resource utilization efficiency can be improved.

[0185] In addition, in the slot format of method 3, enabling and disabling are set (or specified) in symbol units. Therefore, compared with method 2, method 3 can further improve the degree of freedom of scheduling.

[0186] The method of enabling / disabling semi-static transmission and reception has been described above.

[0187] As described above, in this embodiment, the base station 100 and the terminal 200 set the transmission direction for each of the plurality of sub-bands formed by dividing the frequency band, and decide or judge whether to enable or disable the semi-static transmission and reception for each of the plurality of sub-bands individually.

[0188] Thus, even when different transmission directions are set for a plurality of subbands in SBFD, it is possible to set the enable / disable of semi-static transmission and reception for each subband individually, so that it is possible to appropriately enable / disable semi-static transmission and reception in SBFD without depending on the combination of semi-static transmission and reception and transmission and reception notified dynamically. Thus, according to this embodiment, for example, resource allocation can be notified dynamically.

[0189] (Other embodiments)

[0190] In addition, although CG (an example of semi-static transmission) and SPS (an example of semi-static reception) are described as examples of semi-static transmission and reception in the above embodiment, semi-static transmission and reception are not limited to SPS and CG, and other transmission and reception may also be applied. For example, semi-static transmission and reception may also be applied to PUCCH, RACH, SRS, CSI-RS, PDCCH, etc.

[0191] In addition, although the present embodiment describes the operation in the case where a subband is configured on a flexible symbol that is set semi-statically and an SBFD operation is performed, it can also be applied to SBFD symbols when SBFD symbols (symbols of the subband configured for SBFD) are explicitly set. For example, the process of enabling / disabling semi-static transmission and reception that has been applied to flexible symbols can also be applied to SBFD symbols. This can be a case where a new symbol category, SBFD symbols, is set, or it can be a case where an existing symbol category is used to notify SBFD symbols. For example, for a symbol that is set to "D" in the cell-specific UL / DL setting, it can also be regarded as a SBFD symbol when it is set to "U" in the UE-specific UL / DL setting. In an SBFD symbol, both uplink and downlink exist at the same time. Therefore, by controlling the enabling / disabling of semi-static transmission and reception, the degree of freedom of scheduling can be increased and the efficiency of resource utilization can be improved.

[0192] In addition, the enabling / disabling of semi-static transmission and reception described in the above embodiment can also be applied to full duplex (for example, a duplex mode in which uplink and downlink exist simultaneously in the same time resource and frequency resource). For full duplex, uplink and downlink also exist simultaneously in the same codeword, so by applying the enabling / disabling of semi-static transmission and reception represented in this embodiment, the degree of freedom of scheduling can be increased and the efficiency of resource utilization can be improved.

[0193] In addition, in the above-mentioned embodiments, the values ​​such as the number of subbands, the number of terminals, the number of time slots, and the number of symbols are merely examples and are not limited thereto.

[0194] (Replenish)

[0195] The information indicating whether the terminal 200 supports the functions, actions or processes shown in the above-mentioned embodiments may be sent (or notified) by the terminal 200 to the base station 100 as capability information or capability parameters of the terminal 200, for example.

[0196] The capability information may also include the following information elements (IE: Information Element), which individually indicate whether the terminal 200 supports at least one of the functions, actions, and processes shown in the above embodiments. Alternatively, the capability information may also include the following information elements, which indicate whether the terminal 200 supports a combination of two or more of the functions, actions, and processes shown in the above embodiments.

[0197] The base station 100 may, for example, determine (or determine or assume) a function, action or process supported (or not supported) by the terminal 200 that is the source of the capability information based on the capability information received from the terminal 200. The base station 100 may implement an action, process or control corresponding to the result of the determination based on the capability information. For example, the base station 100 may control semi-static transmission and reception for the terminal 200 based on the capability information received from the terminal 200.

[0198] It should be noted that the terminal 200 does not support a part of the functions, actions or processes shown in the above embodiments, which may also be replaced by limiting such a part of the functions, actions or processes in the terminal 200. For example, information or requests related to such limitations may also be notified to the base station 100.

[0199] The information related to the capability or limitation of the terminal 200 may be defined in the standard, for example, or may be implicitly notified to the base station 100 by being associated with information known to the base station 100 or information transmitted to the base station 100 .

[0200] (Control signal)

[0201] In the present disclosure, a downlink control signal (or downlink control information) associated with an embodiment of the present disclosure may be, for example, a signal (or information) sent in a physical downlink control channel (PDCCH: Physical Downlink Control Channel) of the physical layer, or a signal (or information) sent in a medium access control control element (MAC CE: Medium Access Control Control Element) or a radio resource control (RRC: Radio Resource Control) of a higher layer. In addition, the signal (or information) is not limited to the case of being notified by a downlink control signal, and may be pre-defined in a specification (or standard), or may be pre-set in a base station and a terminal.

[0202] In the present disclosure, an uplink control signal (or uplink control information) associated with an embodiment of the present disclosure may be, for example, a signal (or information) sent in a PUCCH of a physical layer, or a signal (or information) sent in a MAC CE or RRC of a higher layer. In addition, the signal (or information) is not limited to the case where it is notified by an uplink control signal, and may be pre-defined in a specification (or standard), or may be pre-set in a base station and a terminal. In addition, the uplink control signal may be, for example, changed to uplink control information (UCI: uplink control information), first stage (1st stage) sidelink control information (SCI: sidelink control information), or second stage (2nd stage) SCI.

[0203] (Base Station)

[0204] In one embodiment of the present disclosure, the base station may also be a transceiver point (TRP: Transmission Reception Point), a cluster head, an access point, a remote radio head (RRH: Remote Radio Head), an eNodeB (eNB), a gNodeB (gNB), a base station (BS: Base Station), a base transceiver station (BTS: Base Transceiver Station), a mother machine, a gateway, etc. In addition, in the sidelink communication, the terminal may also assume the role of the base station. In addition, the base station may also be replaced by a relay device that relays the communication between the high-level node and the terminal. In addition, the base station may also be replaced by a roadside device.

[0205] (Uplink / Downlink / Sidelink)

[0206] An embodiment of the present disclosure can be applied to any link in the uplink, downlink and sidelink. For example, an embodiment of the present disclosure can also be applied to the physical uplink shared channel (PUSCH: Physical Uplink Shared Channel), physical uplink control channel (PUCCH: Physical UplinkControl Channel), physical random access channel (PRACH: Physical Random Access Channel) of the uplink, physical downlink shared channel (PDSCH: Physical Downlink Shared Channel), PDCCH, physical broadcast channel (PBCH: Physical Broadcast Channel) of the downlink, or physical sidelink shared channel (PSSCH: Physical Sidelink Shared Channel), physical sidelink control channel (PSCCH: PhysicalSidelink Control Channel), physical sidelink broadcast channel (PSBCH: Physical SidelinkBroadcast Channel) of the sidelink.

[0207] It should be noted that PDCCH, PDSCH, PUSCH and PUCCH are examples of downlink control channels, downlink data channels, uplink data channels and uplink control channels, respectively. In addition, PSCCH and PSSCH are examples of sidelink control channels and sidelink data channels. In addition, PBCH and PSBCH are examples of broadcast channels, and PRACH is an example of a random access channel.

[0208] (Data Channel / Control Channel)

[0209] An embodiment of the present disclosure may be applied to any channel in a data channel and a control channel. For example, the channel in an embodiment of the present disclosure may be replaced with a PDSCH, PUSCH, PSSCH of a data channel, or a PDCCH, PUCCH, PBCH, PSCCH, PSBCH of a control channel.

[0210] (Reference signal)

[0211] In one embodiment of the present disclosure, a reference signal is, for example, a signal known to both a base station and a mobile station, and is sometimes referred to as a "Reference Signal (RS)" or a "pilot signal". The reference signal may be any reference signal among a demodulation reference signal (DMRS), a channel state information-reference signal (CSI-RS), a tracking reference signal (TRS), a phase tracking reference signal (PTRS), a cell-specific reference signal (CRS), and a sounding reference signal (SRS).

[0212] (Time interval)

[0213] In one embodiment of the present disclosure, the unit of time resources is not limited to one of time slots and symbols or a combination thereof, and may be, for example, a frame, a superframe, a subframe, a time slot, a subslot, a minislot, or a symbol, an OFDM (Orthogonal Frequency Division Multiplexing) symbol, a single carrier-Frequency Division Multiplexing Access (SC-FDMA) symbol, or other time resource units. In addition, the number of symbols contained in one time slot is not limited to the number of symbols exemplified in the above-mentioned embodiment, and may be other numbers of symbols.

[0214] (frequency band)

[0215] An embodiment of the present disclosure may be applied to any one of a licensed band and an unlicensed band.

[0216] (communication)

[0217] An embodiment of the present disclosure may be applied to any communication between a base station and a terminal (Uu link communication), between terminals (sidelink communication), or in-vehicle wireless communication technology (V2X: Vehicle to Everything). For example, the channel in an embodiment of the present disclosure may be replaced with one of PSCCH, PSSCH, physical sidelink feedback channel (PSFCH: Physical Sidelink Feedback Channel), PSBCH, PDCCH, PUCCH, PDSCH, PUSCH, and PBCH.

[0218] In addition, an embodiment of the present disclosure can be applied to any network in a terrestrial network and a non-terrestrial network (NTN: Non-Terrestrial Network) using a satellite or a high altitude pseudo satellite (HAPS: High Altitude Pseudo Satellite). In addition, an embodiment of the present disclosure can also be applied to a terrestrial network such as a network with a large cell size and an ultra-wideband transmission network where the transmission delay is greater than the symbol length or the time slot length.

[0219] (Antenna port)

[0220] In one embodiment of the present disclosure, an antenna port refers to a logical antenna (antenna group) composed of one or more physical antennas. For example, an antenna port does not necessarily refer to a physical antenna, but sometimes refers to an array antenna composed of multiple antennas. For example, it may be that the antenna port is not specified to be composed of several physical antennas, but is specified as the minimum unit that the terminal can send a reference signal (reference signal). In addition, an antenna port is sometimes also specified as the minimum unit multiplied by the weight of a precoding vector.

[0221] <5G NR system architecture and protocol stack>

[0222] 3GPP is continuing work to implement the next version of fifth generation mobile technology (also referred to simply as "5G"), including the development of new radio access technology (NR) operating in the frequency range up to 100 GHz. The first version of the 5G standard was completed in late 2017, which enabled the transition to trial production of terminals (e.g., smartphones) compliant with the 5G NR standard and commercial deployment.

[0223] For example, the system architecture as a whole envisions a NG-RAN (Next Generation Radio Access Network) including gNBs. The gNB provides the UE-side termination of the protocols of the user plane (SDAP (Service Data Adaptation Protocol) / PDCP (Packet Data Convergence Protocol) / RLC (Radio Link Control) / MAC / PHY (Physical Layer)) and control plane (RRC) of the NG radio access. The gNBs are connected to each other through an Xn interface. In addition, the gNB is connected to the NGC (Next Generation Core) through a Next Generation (NG) interface, more specifically, to the AMF (Access and Mobility Management Function) (e.g., a specific core entity that executes the AMF) through an NG-C interface, and in addition, to the UPF (User Plane Function) (e.g., a specific core entity that executes the UPF) through an NG-U interface. Fig.18 Represents the NG-RAN architecture (for example, refer to 3GPP TS 38.300v15.6.0, section 4).

[0224] The protocol stack of the user plane of NR (e.g., refer to 3GPP TS 38.300, Section 4.4.1) includes the PDCP (Packet Data Convergence Protocol (see Section 6.4 of TS 38.300)) sublayer, the RLC (Radio Link Control (see Section 6.3 of TS 38.300)) sublayer and the MAC (Media Access Control (see Section 6.2 of TS 38.300)) sublayer terminated on the network side in the gNB. In addition, a sublayer (SDAP: Service Data Adaptation Protocol) of the new access stratum (AS: Access Stratum) has been introduced on PDCP (e.g., refer to Section 6.5 of 3GPP TS 38.300). In addition, a protocol stack of the control plane is defined for NR (e.g., refer to TS 38.300, Section 4.4.2). An overview of the functions of Layer 2 is described in Section 6 of TS 38.300. The functions of the PDCP sublayer, RLC sublayer and MAC sublayer are listed in Sections 6.4, 6.3 and 6.2 of TS 38.300 respectively. The functions of the RRC layer are listed in Section 7 of TS 38.300.

[0225] For example, the media access control layer handles multiplexing of logical channels, and scheduling including processing of various parameter sets and various functions associated with the scheduling.

[0226] For example, the physical layer (PHY) is responsible for coding, PHY HARQ (Physical Layer Hybrid Automatic Repeat Request) processing, modulation, multi-antenna processing, and mapping signals to appropriate physical time-frequency resources. In addition, the physical layer handles the mapping of transport channels to physical channels. The physical layer provides services to the MAC layer in the form of transport channels. A physical channel corresponds to a set of time-frequency resources used to send a specific transport channel, and each transport channel is mapped to a corresponding physical channel. For example, in the physical channel, the uplink physical channels include PRACH (Physical Random Access Channel), PUSCH (Physical Uplink Shared Channel), PUCCH (Physical Uplink Control Channel), and the downlink physical channels include PDSCH (Physical Downlink Shared Channel), PDCCH (Physical Downlink Control Channel), and PBCH (Physical Broadcast Channel).

[0227] The use cases / extended scenarios of NR may include enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), and massive machine type communications (mMTC), which have various requirements in terms of data rate, latency, and coverage. For example, eMBB is expected to support peak data rates (20 Gbps in the downlink and 10 Gbps in the uplink) and effective (user-experienced) data rates that are about 3 times the data rates provided by IMT-Advanced (International Mobile Telecommunications-Advanced). On the other hand, in the case of URLLC, more stringent requirements are proposed for ultra-low latency (the latency of the user plane is 0.5 ms in UL and DL, respectively) and high reliability (within 1 ms, 1-10-5). Finally, in mMTC, preferably, a high connection density is required (1,000,000 devices / km in an urban environment). 2 ), wide coverage in harsh environments and extremely long battery life (15 years) for a cheap device.

[0228] Therefore, sometimes the parameter set of OFDM that is suitable for one use case (for example, subcarrier spacing (SCS: SubCarrier Spacing), OFDM codeword length, cyclic prefix (CP: Cyclic Prefix) length, number of codewords per scheduling interval) is invalid for other use cases. For example, in low-latency services, it is preferred that the codeword length is shorter than that of mMTC services (therefore, the subcarrier spacing is larger) and / or the number of codewords per scheduling interval (also called "TTI (Transmission Time Interval)") is small. Moreover, in extended scenarios where the delay spread of the channel is large, it is preferred that the CP length is longer than that of scenarios where the delay spread is short. The subcarrier spacing can also be optimized according to the situation to maintain the same CP overhead. The value of the subcarrier spacing supported by NR can be more than one. Correspondingly, subcarrier spacings of 15kHz, 30kHz, 60kHz... are currently considered. The codeword length Tu and the subcarrier spacing Δf are directly related according to the formula Δf=1 / Tu. Similar to the LTE system, the term “resource element” can be used to represent the minimum resource unit composed of one subcarrier with a length of one OFDM / SC-FDMA (Single-Carrier Frequency Division Multiple Access) symbol.

[0229] In the new wireless system 5G-NR, for each parameter set and each carrier, a resource grid of subcarriers and OFDM symbols is defined in the uplink and downlink. Each element of the resource grid is called a "resource element", which is determined based on the frequency index in the frequency domain and the symbol position in the time domain (refer to 3GPP TS 38.211v15.6.0).

[0230] <Functional separation between NG-RAN and 5GC in 5G NR>

[0231] Fig.19 Indicates the functional separation between NG-RAN and 5GC. The logical node of NG-RAN is gNB or ng-eNB. 5GC has logical nodes AMF, UPF and SMF (Session Management Function).

[0232] For example, gNB and ng-eNB host the following main functions:

[0233] - Radio Bearer Control, Radio Admission Control, Connection Mobility Control, and Radio Resource Management functions such as dynamically allocating (scheduling) resources to UEs in both uplink and downlink;

[0234] -IP (Internet Protocol) header compression, encryption and integrity protection of data;

[0235] - Selection of the AMF when attaching the UE in case the routing towards the AMF cannot be decided based on the information provided by the UE;

[0236] - Routing of user plane data towards UPF;

[0237] - Routing of control plane information towards the AMF;

[0238] -Set up and disconnect connections;

[0239] - Scheduling and sending of paging messages;

[0240] - Scheduling and sending of system broadcast information (AMF or operation, admission, maintenance function (OAM) as the originator);

[0241] - Settings for measurements and measurement reports for mobility and scheduling;

[0242] - Packet marking of the transmission class in uplink;

[0243] -Session management;

[0244] - Network slicing support;

[0245] - Management of QoS (Quality of Service) flows and mapping to data radio bearers;

[0246] - Support of UE in RRC_INACTIVE state;

[0247] -NAS (Non Access Stratum) message distribution function;

[0248] -Sharing of wireless access networks;

[0249] -Dual connection;

[0250] -Close collaboration between NR and E-UTRA (Evolved Universal Terrestrial Radio Access).

[0251] The access and mobility management function (AMF) hosts the following main functions:

[0252] - Functionality to terminate non-access stratum (NAS) signaling;

[0253] -Security of NAS signaling;

[0254] - Security control of the access layer (AS);

[0255] -Core Network (CN) inter-node signaling for mobility between 3GPP access networks;

[0256] - the possibility of reaching the UE in idle mode (including the control and execution of paging retransmission);

[0257] - Management of the registration area;

[0258] -Support for intra-system and inter-system mobility;

[0259] -Access authentication;

[0260] - Access permission including roaming permission check;

[0261] -Mobility management control (subscription and policy);

[0262] - Network slicing support;

[0263] - Selection of Session Management Function (SMF).

[0264] In addition, the User Plane Function (UPF) hosts the following main functions:

[0265] - Anchor point for intra-RAT (Radio Access Technology) mobility / inter-RAT (Inter-RAT) mobility (where applicable);

[0266] - External PDU (Protocol Data Unit) session point for interconnection with data networks;

[0267] -Packet routing and forwarding;

[0268] -Policy rule enforcement for packet inspection and user plane;

[0269] - Business usage reporting;

[0270] - Uplink classifier for supporting routing of traffic towards data networks;

[0271] -BranchingPoint used to support multi-homed PDU session;

[0272] - QoS processing for the user plane (e.g., packet filtering, gating, UL / DL rate enforcement);

[0273] - Verification of uplink services (mapping of SDF (Service Data Flow) to QoS flows);

[0274] - Downlink packet buffering and downlink data notification triggering function.

[0275] Finally, the Session Management Function (SMF) hosts the following main functions:

[0276] -Session management;

[0277] -Allocation and management of UE IP addresses;

[0278] - UPF selection and control;

[0279] - Traffic steering configuration function in the user plane function (UPF) for directing traffic to the appropriate destination;

[0280] - Enforcement of policies and QoS in the control part;

[0281] -Notification of downlink data.

[0282] <RRC connection setup and re-setup process>

[0283] Fig. 20 Represents several interactions between the UE, gNB and AMF (5GC entity) when the NAS part of the UE transitions from RRC_IDLE (RRC Idle) to RRC_CONNECTED (RRC Connected) (refer to TS 38.300v15.6.0).

[0284] RRC is a high-layer signaling (protocol) used for the configuration of UE and gNB. Through this transition, AMF prepares UE context data (which includes, for example, PDU session context, security keys, UE radio capabilities (UE Radio Capability), UE security capabilities (UE Security Capabilities), etc.), and sends it to gNB together with the initial context setup request (INITIAL CONTEXTSETUP REQUEST). Next, the gNB activates AS security together with the UE. The gNB sends a Security Mode Command (SecurityModeCommand) message to the UE, and the UE responds to the gNB with a Security Mode Complete (SecurityModeComplete) message to activate AS security. Then, the gNB sends an RRC Reconfiguration (RRCReconfiguration) message to the UE, and the gNB receives an RRC Reconfiguration Complete (RRCReconfigurationComplete) from the UE for the RRC Reconfiguration message, thereby reconfiguring the Signaling Radio Bearer 2 (SRB2) and the Data Radio Bearer (DRB). For signaling-only connections, since SRB2 and DRB are not configured, the steps related to RRC reconfiguration can be omitted. Finally, the gNB notifies the AMF that the setup process is complete using the INITIAL CONTEXT SETUP RESPONSE.

[0285] Therefore, the present disclosure provides the following fifth generation core network (5GC) entity (e.g., AMF, SMF, etc.), which includes: a control circuit, which, when in action, establishes a next generation (Next Generation, NG) connection with a gNodeB (gNodeB); and a sending unit, which, when in action, sends an initial context setting message to the gNodeB via the NG connection to set a signaling radio bearer between the gNodeB and the user equipment (UE: User Equipment). Specifically, the gNodeB sends a radio resource control (RRC) signaling containing a resource allocation setting information element (IE: Information Element) to the UE via the signaling radio bearer. Then, the UE sends in the uplink or receives in the downlink based on the resource allocation setting.

[0286] <Application scenarios of IMT after 2020>

[0287] Fig.21Indicates several use cases for 5G NR. In the 3rd generation partnership project new radio (3GPP NR), three use cases supporting a wide range of services and applications conceived through IMT-2020 have been studied. The planning and development of the first phase of specifications for large-capacity high-speed communications (eMBB: enhanced mobile broadband) has been completed. In current and future work, in addition to gradually expanding support for eMBB, it also includes standardization for ultra-reliable and low-latency communications (URLLC: ultra-reliable and low-latency communications) and multiple simultaneous machine-type communications (mMTC: massive machine-type communications). Fig.21 Several examples of the conceptual use scenarios of IMT after 2020 are shown (for example, see ITU-R M.2083 Figure 2 ).

[0288] The use cases of URLLC have strict requirements related to performance such as throughput, latency (delay) and availability. The use cases of URLLC are conceived as an element technology for realizing future applications such as wireless control of industrial production processes or manufacturing processes, remote medical surgery, automation of power transmission and distribution in smart grids, and traffic safety. The ultra-high reliability of URLLC is supported by determining technologies that meet the requirements set by TR38.913. In version 15 of NR URLLC, as an important requirement, the target user plane latency is 0.5ms in UL (uplink) and 0.5ms in DL (downlink). The overall URLLC requirement for a packet transmission is that the block error rate (BLER) is 1E-5 for a packet size of 32 bytes when the user plane latency is 1ms.

[0289] Considering the physical layer, a number of possible approaches can be used to improve reliability. Current scope for improving reliability includes defining additional CQI (Channel Quality Indicator) tables for URLLC, more compact DCI formats, repetition of PDCCH, etc. However, as NR (an important prerequisite for NR URLLC) becomes more stable and further developed, the scope can be expanded to achieve ultra-high reliability. Specific use cases for NR URLLC in Release 15 include Augmented Reality / Virtual Reality (AR / VR), e-Health, e-Safety and critical applications.

[0290] In addition, the technical enhancements of the NR URLLC target are aimed at improving latency and increasing reliability. Technical enhancements for improving latency include configurable parameter sets, non-slot-based scheduling with flexible mapping, unauthorized (configured authorized) uplink, slot-level repetition in the data channel, and preemption in the downlink. Preemption means stopping the transmission of allocated resources and using the allocated resources for other transmissions that are requested later and meet the necessary conditions of lower latency / higher priority. Therefore, the transmission that has been allowed will be replaced by the subsequent transmission. Preemption can be applied regardless of the specific service type. For example, the transmission of service type A (URLLC) can also be replaced by the transmission of service type B (eMBB, etc.). Technical enhancements related to reliability improvement include dedicated CQI / MCS tables for target BLER of 1E-5.

[0291] The use case of mMTC (Massive Machine Type Communications) is characterized by the fact that typically there are a very large number of connected devices that send relatively small amounts of data that are not susceptible to latency. The devices are required to be low-priced and have very long battery life. From the NR point of view, utilizing very narrow bandwidth portions is one solution that can save power in the UE and extend its battery life.

[0292] As mentioned above, it is predicted that the room for reliability improvement in NR will be further expanded. It is one of the important requirements for all situations. For example, the important requirement related to URLLC and mMTC is high reliability or ultra-high reliability. From the wireless point of view and the network point of view, reliability can be improved in several mechanisms. In general, there are two to three important areas that may help improve reliability. These areas include compact control channel information, repetition of data channels / control channels, and diversity related to frequency domain, time domain and / or space domain. These areas can be used universally to improve reliability regardless of the specific communication scenario.

[0293] For NR URLLC, further use cases with stricter requirements are envisioned, such as factory automation, transportation, and power transmission. The strict requirements are high reliability (up to 10-6 reliability), high availability, packet size up to 256 bytes, time synchronization up to a few microseconds (μs) (the value can be set to 1μs or a few microseconds depending on the frequency range and short latency of around 0.5ms to 1ms (for example, 0.5ms latency in the user plane is set as the target) for the use case.

[0294] Moreover, regarding NR URLLC, from the perspective of the physical layer, there may be several technical enhancements. These technical enhancements include the enhancement of PDCCH (Physical Downlink Control Channel) related to compact DCI, repetition of PDCCH, and increased monitoring of PDCCH. In addition, the enhancement of UCI (Uplink Control Information) is related to the enhancement of enhanced HARQ (Hybrid Automatic Repeat Request) and CSI feedback. In addition, there may be enhancement of PUSCH related to frequency hopping at the mini-slot level and enhancement of retransmission / repetition. The term "mini-slot" refers to a transmission time interval (TTI) that contains fewer symbols than a slot (a slot has 14 symbols).

[0295] <QoS Control>

[0296] The 5G QoS (Quality of Service) model is based on QoS flows, supporting both QoS flows that require guaranteed bit rate (GBR: Guaranteed Bit Rate QoS flows) and QoS flows that do not require guaranteed bit rate (non-GBR QoS flows). Therefore, at the NAS level, QoS flows are the most fine-grained QoS divisions in a PDU session. QoS flows are determined within a PDU session based on the QoS flow ID (QFI: QoS Flow ID) transmitted by the encapsulation header via the NG-U interface.

[0297] For each UE, 5GC establishes one or more PDU sessions. For each UE, in conjunction with the PDU session, NG-RAN, for example, as described in the previous reference Fig. 20 As shown, at least one data radio bearer (DRB) is established. In addition, the DRB added to the QoS flow of the PDU session can also be set later (when to set it depends on NG-RAN). NG-RAN maps packets belonging to various PDU sessions to various DRBs. The NAS-level packet filters in the UE and 5GC are used to associate UL packets and DL packets with QoS flows, and the AS-level mapping rules in the UE and NG-RAN associate UL QoS flows and DL QoS flows with DRBs.

[0298] Fig. 22 Represents the non-roaming reference architecture of 5G NR (see TS23.501v16.1.0, section 4.23). Application Function (AF) (e.g., host Fig.21The 3GPP core network (an external application server for the 5G service illustrated) interacts with the 3GPP core network to provide services. For example, accessing the Network Exposure Function (NEF) to support applications that affect the routing of services, or interacting with the policy framework (refer to the Policy Control Function (PCF)) for policy control (for example, QoS control). Based on the operator's deployment, the operator considers that trusted application functions can interact directly with the associated network function (Network Function). Application functions that are not allowed by the operator to directly access network functions interact with associated network functions via NEF using an open framework to the outside.

[0299] Fig. 22 It also represents further functional units of the 5G architecture, namely, Network Slice Selection Function (NSSF), Network Repository Function (NRF), Unified Data Management (UDM), Authentication Server Function (AUSF), Access and Mobility Management Function (AMF), Session Management Function (SMF) and Data Network (DN: Data Network, such as services provided by operators, Internet access or services provided by third parties). All or part of the core network functions and application services can also be deployed and operated in a cloud computing environment.

[0300] Therefore, the present disclosure provides the following application server (for example, AF of 5G architecture), which includes: a sending unit, which, in action, sends a request for QoS requirements for at least one of URLLC service, eMMB service and mMTC service to at least one of the functions of 5GC (for example, NEF, AMF, SMF, PCF, UPF, etc.) in order to establish a PDU session of a wireless bearer between a g-node B and a UE corresponding to the QoS requirements; and a control circuit, which, in action, uses the established PDU session to provide service.

[0301] The present disclosure can be implemented by software, hardware or software in cooperation with hardware. Each functional block used in the description of the above-mentioned embodiments is partially or entirely implemented as an LSI (Large Scale Integration) as an integrated circuit, and each process described in the above-mentioned embodiments may also be partially or entirely controlled by an LSI or a combination of LSIs. LSI may be composed of individual chips, or may be composed of one chip in a manner that includes part or all of the functional blocks. LSI may also include input and output of data. LSI may also be referred to as "IC (Integrated Circuit)", "System LSI", "Super LSI", "Ultra LSI" depending on the degree of integration.

[0302] The method of integrated circuitization is not limited to LSI, and can also be implemented by a dedicated circuit, a general-purpose processor or a dedicated processor. In addition, an FPGA (Field Programmable Gate Array) that can be programmed after LSI manufacturing, or a reconfigurable processor (Reconfigurable Processor) that can reconfigure the connection or setting of the circuit block inside the LSI can also be used. The present disclosure can also be implemented as digital processing or analog processing.

[0303] Furthermore, if integrated circuit technology that replaces LSI emerges as semiconductor technology advances or other technologies are derived, it is of course possible to use this technology to achieve integration of functional blocks. There is also the possibility of applying biotechnology, etc.

[0304] The present disclosure can be implemented in all kinds of devices, equipment, and systems (collectively referred to as "communication devices") with communication functions. The communication device may also include a wireless transceiver and a processing / control circuit. The wireless transceiver may also include a receiving unit and a transmitting unit, or perform the functions of these parts. The wireless transceiver (transmitting unit, receiving unit) may also include an RF (Radio Frequency) module and one or more antennas. The RF module may also include an amplifier, an RF modulator / demodulator, or a device similar to these. Non-limiting examples of communication devices include: phones (mobile phones, smart phones, etc.), tablets, personal computers (PCs) (laptops, desktops, notebook computers, etc.), cameras (digital cameras, digital video cameras, etc.), digital players (digital audio / video players, etc.), wearable devices (wearable cameras, smart watches, tracking devices, etc.), game consoles, e-book readers, telehealth / telemedicine (telehealth / medical prescription) equipment, vehicles or transportation vehicles with communication functions (cars, airplanes, ships, etc.), and combinations of the above-mentioned various devices.

[0305] Communication devices are not limited to portable or mobile devices, but also include all kinds of devices, equipment, and systems that cannot be carried or fixed. For example, they include: smart home devices (home appliances, lighting equipment, smart meters or meters, control panels, etc.), vending machines, and all other "things" that can exist on the IoT (Internet of Things) network.

[0306] The communication includes data communication performed by a cellular system, a wireless LAN (Local Area Network) system, a communication satellite system, etc., and also includes data communication performed by a combination of these systems.

[0307] In addition, the communication device also includes devices such as controllers or sensors connected or linked to the communication device that performs the communication function described in the present invention. For example, it includes a controller or sensor that generates a control signal or data signal used by the communication device that performs the communication function of the communication device.

[0308] In addition, the communication device includes infrastructure equipment that communicates with the above-mentioned non-limiting various devices or controls the above-mentioned various devices, such as base stations, access points, and all other devices, equipment, and systems.

[0309] A terminal according to an embodiment of the present disclosure includes: a control circuit that determines whether to enable or disable semi-static transmission and reception for each of the plurality of bands formed by dividing a frequency band, in a manner in which transmission directions are set for each of the plurality of bands; and a communication circuit that transmits or receives a signal according to the determination of enabling or disabling.

[0310] In one embodiment of the present disclosure, the control circuit determines one of the enabling and disabling of the semi-static transceiving based on information indicating one of the enabling and disabling states.

[0311] In one embodiment of the present disclosure, the control circuit determines one of the enabling and disabling of the semi-static transceiving based on a time slot format corresponding to the one of the enabling and disabling.

[0312] In one embodiment of the present disclosure, in the time slot format, the enabling and disabling are set in time slot units.

[0313] In one embodiment of the present disclosure, in the time slot format, the enabling and disabling are set in codeword units.

[0314] A base station according to an embodiment of the present disclosure includes: a control circuit that individually determines whether to enable or disable semi-static transmission and reception by a terminal for each of the plurality of bands formed by dividing a frequency band, in a manner in which transmission directions are respectively set for the plurality of bands formed by dividing a frequency band; and a communication circuit that receives or transmits a signal according to the decision on enabling or disabling.

[0315] In a communication method according to an embodiment of the present disclosure, a terminal performs the following processing: in a method of setting transmission directions for a plurality of bands formed by dividing a frequency band, separately determining whether to enable or disable semi-static transmission and reception for the plurality of bands; and transmitting or receiving a signal according to the determination of enabling or disabling.

[0316] In a communication method according to an embodiment of the present disclosure, a base station performs the following processing: in a method of setting transmission directions for a plurality of bands formed by dividing a frequency band, separately determining whether to enable or disable semi-static transmission and reception by a terminal for each of the plurality of bands; and receiving or transmitting a signal according to the decision on enabling or disabling.

[0317] The disclosed contents of the specification, drawings, and abstract contained in the Japanese patent application No. 2022-128835 filed on August 12, 2022 are incorporated herein by reference in their entirety.

[0318] Industrial Applicability

[0319] One embodiment of the present disclosure is useful for a wireless communication system.

[0320] Description of Reference Numerals

[0321] 100 Base Stations

[0322] 101, 201 Receiving Department

[0323] 102, 202 Demodulation / decoding unit

[0324] 103 Dispatching Department

[0325] 104, 205 Control Information Retention Unit

[0326] 105, 203 Semi-static transceiver control unit

[0327] 106, 206 Data / control information generation unit

[0328] 107, 207 Coding / Modulation Unit

[0329] 108, 208 Sending Department

[0330] 200 Terminal

[0331] 204 Control Department

Claims

1. A terminal, characterized in that: include: A control circuit that determines whether to enable or disable semi-static transmission and reception for each of the plurality of bands individually in a manner in which transmission directions are set for each of the plurality of bands formed by dividing the frequency band; as well as The communication circuit sends or receives a signal according to the determination of enabling and disabling.

2. The terminal according to claim 1, wherein: The control circuit determines one of enabling and disabling of the semi-static transceiving based on information indicating one of the enabling and disabling states.

3. The terminal according to claim 1, wherein: The control circuit determines one of the enabling and disabling of the semi-static transceiving based on a time slot format corresponding to the one of the enabling and disabling.

4. The terminal according to claim 3, wherein: In the time slot format, the enabling and disabling are set in time slot units.

5. The terminal according to claim 3, wherein: In the slot format, the enabling and disabling are set in symbol units.

6. A base station, characterized in that: include: A control circuit that, in a method of setting transmission directions for each of a plurality of bands formed by dividing a frequency band, individually determines whether to enable or disable semi-static transmission and reception by the terminal for each of the plurality of bands; as well as The communication circuit receives or sends a signal according to the decision of enabling or disabling.

7. A communication method, characterized in that: The terminal performs the following processing: In a method of setting transmission directions for each of a plurality of bands formed by dividing a frequency band, enabling and disabling semi-static transmission and reception are determined individually for each of the plurality of bands; and According to the decision of enabling and disabling, a signal is sent or received.

8. A communication method, characterized in that: The base station performs the following processing: In a method of setting transmission directions for each of a plurality of bands formed by dividing a frequency band, enabling and disabling semi-static transmission and reception by a terminal are individually determined for each of the plurality of bands; and According to the decision of enabling and disabling, the signal is received or sent.

Images