Base station, communication method and integrated circuit

Abstract

This base station comprises a control circuit that individually sets a first transmission timing for uplink in a first time resource and a second transmission timing for uplink in a second time resource different from the first time resource, and a reception circuit that receives a signal on the basis of the first transmission timing.

Description

Base station, terminal and communication method

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

[0002] The 3rd Generation Partnership Project (3GPP) has completed the physical layer specifications for Release 17 NR (New Radio access technology) as a functional extension of 5th Generation mobile communication systems (5G). NR supports enhanced mobile broadband (eMBB) to meet the requirements of high speed and large capacity, as well as ultra-reliable and low latency communication (URLLC) (see, for example, Non-Patent Documents 1-6).

[0003] 3GPP TS 38.211 V17.2.0, "NR; Physical channels and modulation (Release 17)," June 20223GPP TS 38.212 V17.2.0, "NR; Multiplexing and channel coding (Release 17)," June 20223GPP TS 38.213 V17.2.0, "NR; Physical layer procedure for control (Release 17)," June 20223GPP TS 38.214 V17.2.0, "NR; Physical layer procedures for data (Release 17)," June 20223GPP TS 38.215 V17.1.0, "NR; V17.1.0, "NR; Radio Resource Control (RRC) protocol specification (Release 17)", June 2022

[0004] However, there is room for further study on the method of controlling transmission timing in wireless communication.

[0005] Non-limiting examples of the present disclosure contribute to providing a base station, a terminal, and a communication method that can appropriately control transmission timing in wireless communication.

[0006] A base station according to one embodiment of the present disclosure includes a control circuit that individually sets a first transmission timing of an uplink in a first time resource and a second transmission timing of an uplink in a second time resource different from the first time resource, and a receiving circuit that receives a signal based on the first transmission timing and the second transmission timing.

[0007] These comprehensive or specific aspects may be realized as a system, an apparatus, a method, an integrated circuit, a computer program, or a recording medium, or may be realized as any combination of a system, an apparatus, a method, an integrated circuit, a computer program, and a recording medium.

[0008] According to an embodiment of the present disclosure, transmission timing in wireless communication can be appropriately controlled.

[0009] Further advantages and benefits of one embodiment of the present disclosure will become apparent from the specification and drawings. Such advantages and / or benefits may be provided by some embodiments and features described in the specification and drawings, respectively, but not necessarily all of them may be provided to obtain one or more identical features.

[0010] 1. A diagram showing an example of a duplex scheme. 2. A diagram showing an example of downlink and uplink transmission timing and reception timing. 3. A diagram showing an example of transmission and reception timing in Subband non-overlapping full duplex (SBFD). 4. Block diagram showing an example of the configuration of a part of a base station. 5. Block diagram showing an example of the configuration of a part of a terminal. 6. Block diagram showing an example of the configuration of a base station. 7. Block diagram showing an example of the configuration of a terminal. 8. Sequence diagram showing an example of the operation of a base station and a terminal. 9. A diagram showing an example of downlink and uplink transmission timing and reception timing. 10. A diagram showing an example of setting a transient period. 11. A diagram of an exemplary architecture of a 3GPP NR system. 12. A schematic diagram showing functional separation between NG-RAN (Next Generation - Radio Access Network) and 5GC (5th Generation Core). 13. A sequence diagram of the procedure for setting up / resetting a Radio Resource Control (RRC) connection. 14. A schematic diagram showing usage scenarios of enhanced Mobile BroadBand (eMBB), massive Machine Type Communications (mMTC), and Ultra Reliable and Low Latency Communications (URLLC). 15. Block diagram of an exemplary 5G system architecture for a non-roaming scenario.

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

[0012] [Regarding Subband Non-Overlapping Full Duplex (SBFD)] "Study on the 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 support for subband non-overlapping full duplex (SBFD, also known as Cross Division Duplex (XDD)).

[0013] Figure 1 is a diagram showing an example of the Duplex system. In Figure 1, the vertical axis represents frequency and the horizontal axis represents time. Also, in Figure 1, "U" represents uplink transmission and "D" represents downlink transmission.

[0014] FIG. 1(a) shows an example of half-duplex Time Division Duplex (TDD). In FIG. 1(a), UE#1 and UE#2 are terminals (UE: User Equipment) connected to a base station (e.g., gNB). In the half-duplex shown in FIG. 1(a), the transmission direction (e.g., downlink or uplink) in a certain time resource may be common between the base station and the terminal. For example, the transmission direction in a certain time resource does not differ between terminals.

[0015] FIG. 1(b) shows an example of SBFD. In SBFD, a frequency resource (or a frequency band) is divided into multiple bands (e.g., subbands, RB sets, subbands, or sub-BWPs (Bandwidth Parts)), and transmission in different directions (e.g., downlink or uplink) is supported for each subband. In SBFD, a terminal transmits and receives data in either the uplink or downlink in a certain time resource, but does not transmit or receive data in the other direction. On the other hand, in SBFD, a base station can transmit and receive data in both the uplink and downlink simultaneously. There may be cases where a terminal does not use resources in the transmission direction in a certain time resource (e.g., resources indicated by dotted lines in FIG. 1(b)).

[0016] [Timing Alignment] For example, the uplink transmission timing at the terminal is T TA (e.g., parameters related to timing advance between downlink and uplink) may be set early. TA is defined, for example, by the following equation (1):

[0017] where N TA(For example, a parameter related to the timing advance between the downlink and the uplink, or a timing setting value) may be used in the base station to adjust the reception timing of the uplink from each terminal. For example, when adjusting the reception timing of the uplink from each terminal to the transmission timing of the downlink, N TA For each terminal, N may be set to twice the propagation time (for example, the time corresponding to the round-trip propagation delay time). For example, since the propagation delay time may vary depending on the location of the terminal (for example, the distance between the base station and the terminal), N TA may be adjusted for each terminal by the Timing Advance command.

[0018] N TA,offset (e.g., the offset value used in calculating the timing advance) may be set for the switch time from uplink reception to downlink transmission at the base station. TA,offset may be set, for example, by higher layer signaling (e.g., Cell-specific Radio Resource Control (RRC) signaling). TA,offset A predefined default value (or a fixed value) may be set for the parameter.

[0019] In addition, N TA and N TA,offset may be set depending on the implementation of the base station, for example.

[0020] N TA,adj common and N TA,adj UE (e.g., parameters related to timing correction) are parameters used in a Non-Terrestrial Network (NTN). In the following description, as an example, TA,adj common and N TA,adj UE If you do not handle (e.g., N TA,adj common =N TA,adj UE = 0) will be explained.

[0021] FIG. 2 shows an example of transmission and reception timing in a base station and a terminal.

[0022] In the example of Fig. 2, transmission and reception timings in Slot #0, Slot #1, and Slot #2 will be described. In Fig. 2, "D" represents downlink, "U" represents uplink, and "gap" represents a gap section not used for transmission and reception.

[0023] In Fig. 2, the first line shows the slot structure, and the second to fifth lines show the transmission timing and reception timing at the base station and the terminal, respectively. TA is set to twice the propagation delay time, and N TA,offset is set to a non-zero value (e.g., a value greater than 0).

[0024] The second line in Fig. 2 shows the downlink transmission timing of the base station, and the third line in Fig. 2 shows the downlink reception timing of the terminal. As shown in Fig. 2, the downlink reception timing of the terminal is delayed by a propagation delay compared to the downlink transmission timing of the base station.

[0025] The fourth line in FIG. 2 shows the uplink transmission timing of the terminal, and the fifth line in FIG. 2 shows the uplink reception timing of the base station. As shown in FIG. 2, the uplink transmission timing of the terminal is (N TA +N TA,offset )T c minutes (for example, T shown in Equation (1) TA minutes), and is set early (Note that in Figure 2, c (Note that the time periods indicated by the dashed lines are omitted.) As shown in Fig. 2, the uplink reception timing of the base station is delayed by a propagation delay time compared to the uplink transmission timing of the terminal.

[0026] In FIG. 2, when comparing the transmission and reception timing of the base station (for example, the downlink transmission timing in the second row and the uplink reception timing in the fifth row), the uplink reception timing is N times earlier than the downlink transmission timing. TA,offsetAs a result, in FIG. 2, N TA,offset Since an interval (gap period) occurs, the base station can perform a process of switching from uplink reception to downlink transmission during this period.

[0027] [Timing Alignment in SBFD] In SBFD, a downlink subband and an uplink subband can exist within the same time resource (e.g., slot or symbol, hereinafter also referred to as "slot / symbol"). For example, in SBFD, TA,offset When r is set to a value other than 0 (e.g., a value greater than 0), it is assumed that the symbol timing (or symbol boundary) is shifted between the downlink and the uplink in the base station. When the symbol boundary is shifted between the downlink and the uplink, the base station may experience increased self-interference from the downlink subband to the uplink subband.

[0028] FIG. 3 shows an example of transmission and reception timing of a base station in SBFD. In the example shown in FIG. 3, Subband #0 and Subband #2 are assigned to the downlink, and Subband #1 is assigned to the uplink. Also, in FIG. 3, N TA,offset is set to a value greater than 0. As shown in Figure 3, the symbol timing (or symbol boundary) of uplink Subband #1 is earlier than the symbol timing (or symbol boundary) of downlink Subband #0 and Subband #2. Therefore, in Figure 3, the symbol timing (or symbol boundary) is shifted between Subband #1 and Subband #0 and Subband #2, which can increase self-interference from downlink Subband #0 or Subband #2 to uplink Subband #1.

[0029] In one non-limiting embodiment of the present disclosure, a timing control method for suppressing interference between subbands in SBFD will be described.

[0030] [Overview of Communication System] A communication system according to one aspect of the present disclosure may include, for example, a base station 100 (e.g., gNB) shown in Figures 4 and 6, and a terminal 200 (e.g., UE) shown in Figures 5 and 7. A plurality of base stations 100 and a plurality of terminals 200 may exist in the communication system.

[0031] 4 is a block diagram illustrating a configuration example of a portion of a base station 100 according to an aspect of the present disclosure. In the base station 100 illustrated in FIG. 4, a control unit (e.g., corresponding to a control circuit) individually sets a first transmission timing of an uplink in a first time resource and a second transmission timing of an uplink in a second time resource different from the first time resource. A receiving unit (e.g., corresponding to a receiving circuit) receives a signal based on the first transmission timing and the second transmission timing.

[0032] 5 is a block diagram illustrating a configuration example of a portion of a terminal 200 according to an aspect of the present disclosure. In the terminal 200 illustrated in FIG. 5 , a control unit (e.g., corresponding to a control circuit) separately sets a first transmission timing of an uplink in a first time resource and a second transmission timing of an uplink in a second time resource different from the first time resource. A transmission unit (e.g., corresponding to a transmission circuit) transmits a signal based on the first transmission timing and the second transmission timing.

[0033] [Configuration of Base Station] Fig. 6 is a block diagram showing an example configuration of a base station 100 according to one aspect of the present disclosure. In Fig. 6, the base station 100 includes a receiving unit 101, a demodulating and decoding unit 102, a scheduling unit 103, a timing control unit 104, a control information holding unit 105, a data and control information generating unit 106, an encoding and modulation unit 107, and a transmitting unit 108.

[0034] For example, at least one of the demodulation / decoding unit 102, the scheduling unit 103, the timing control unit 104, the control information storage unit 105, the data / control information generation unit 106, and the encoding / modulation unit 107 may be included in the control unit shown in Figure 4, and the receiving unit 101 may be included in the receiving unit shown in Figure 4.

[0035] The receiving unit 101 performs receiving processing such as down-conversion or A / D conversion on a received signal received via an antenna, and outputs the received signal after the receiving processing to the demodulation and decoding unit 102. For example, the receiving unit 101 may perform the receiving processing in accordance with the timing set by the timing control unit 104.

[0036] The demodulation and decoding unit 102 demodulates and decodes, for example, a received signal (for example, an uplink signal) input from the receiving unit 101 and outputs the decoding result to the scheduling unit 103 .

[0037] The scheduling unit 103 may, for example, perform scheduling for the terminals 200. The scheduling unit 103 schedules transmission and reception for each terminal 200 based on, for example, at least one of the decoding result input from the demodulation and decoding unit 102 and the control information input from the control information storage unit 105, and instructs the data and control information generation unit 106 to generate at least one of data and control information. The scheduling unit 103 may also instruct the timing control unit 104 on uplink reception timing. The scheduling unit 103 may also output control information related to scheduling for the terminals 200 to the control information storage unit 105.

[0038] The timing control unit 104, for example, in accordance with an instruction from the scheduling unit 103, TA,offset The timing control unit 104 may determine the value of the time resource (e.g., slot or symbol) to which the set transmission timing is to be applied, and output the determined information to the data and control information generation unit 106. Furthermore, the timing control unit 104 may set the reception timing for the receiving unit 101 based on the determined information.

[0039] The control information storage unit 105 stores, for example, control information set for each terminal 200. The control information may include, for example, information related to the transmission timing of each terminal 200. The control information storage unit 105 may output the stored information to each component of the base station 100 (for example, the scheduling unit 103) as necessary.

[0040] The data and control information generating unit 106 generates at least one of data and control information, for example, in accordance with an instruction from the scheduling unit 103, and outputs a signal including the generated data or control information to the coding and modulation unit 107. Furthermore, the data and control information generating unit 106 generates control information for the terminal 200 based on information regarding the transmission timing of the terminal 200, for example, input from the timing control unit 104, and outputs a signal including the generated control information to the coding and modulation unit 107. The generated data and control information may include, for example, at least one of upper layer signaling information and downlink control information. For example, the control information regarding the transmission timing of the terminal may be transmitted as physical layer control information (for example, control information on a PDCCH (Physical Downlink Control Channel)) or may be transmitted as upper layer signaling information (or upper layer parameters).

[0041] The encoding / modulation unit 107 encodes and modulates, for example, a signal (including, for example, data, control information, or information regarding the transmission timing of the terminal 200) input from the data / control information generation unit 106, and outputs the modulated signal to the transmission unit 108.

[0042] The transmitting unit 108 performs transmission processing such as D / A conversion, up-conversion, or amplification on the signal input from the encoding / modulating unit 107, and transmits the radio signal obtained by the transmission processing from an antenna to the terminal 200.

[0043] [Terminal Configuration] Fig. 7 is a block diagram showing an example configuration of terminal 200 according to one aspect of the present disclosure. In Fig. 7, terminal 200 includes receiving section 201, demodulation and decoding section 202, control section 203, timing control section 204, control information holding section 205, data and control information generation section 206, coding and modulation section 207, and transmission section 208.

[0044] For example, at least one of the demodulation / decoding unit 202, control unit 203, timing control unit 204, control information storage unit 205, data / control information generation unit 206, and encoding / modulation unit 207 may be included in the control unit shown in Figure 5, and the transmission unit 208 may be included in the transmission unit shown in Figure 5.

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

[0046] The demodulation and decoding unit 202 demodulates and decodes, for example, the received signal input from the receiving unit 201, and outputs the decoded result to the control unit 203. The decoded result may include, for example, signaling information of higher layers and downlink control information. In addition, the demodulation and decoding unit 202 may add, for example, information about the transmission timing of the terminal 200 (for example, N TA,offset , information on the time resource (for example, slot or symbol) to which the set transmission timing is to be applied, etc.), the timing control unit 204 outputs the information.

[0047] The control unit 203 may determine whether data or control information is to be transmitted or received, for example, based on the decoding result (e.g., data or control information) input from the demodulation / decoding unit 202 and the control information input from the control information storage unit 205. For example, if the determination result indicates that data or control information is to be received, the control unit 203 may instruct the receiving unit 201 and the demodulation / decoding unit 202 to receive at least one of the data and the control information (not shown). Furthermore, for example, if the determination result indicates that data or control information is to be transmitted, the control unit 203 may instruct the data / control information generating unit 206 to generate at least one of the data and the control information. Furthermore, the control unit 203 may instruct the timing control unit 204 to set the transmission timing, for example. Furthermore, the control unit 203 may output control information related to the setting of the transmission timing to the control information storage unit 205.

[0048] The timing control unit 204 may determine the transmission timing based on, for example, information regarding the transmission timing input from the demodulation / decoding unit 202 and control information regarding the setting of the transmission timing input from the control unit 203, and set the transmission timing for the transmitting unit 208.

[0049] The control information holding unit 205 holds, for example, control information input from the control unit 203, and outputs the held information to each component (for example, the control unit 203) as necessary.

[0050] The data and control information generating unit 206 generates data or control information according to instructions from the control unit 203 , for example, and outputs a signal including the generated data or control information to the encoding and modulation unit 207 .

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

[0052] The transmitting unit 208 performs transmission processing such as D / A conversion, up-conversion, or amplification on the signal input from the encoding / modulating unit 207, and transmits the radio signal obtained by the transmission processing from an antenna to the base station 100. For example, the transmitting unit 208 may perform the transmission processing in accordance with the transmission timing set by the timing control unit 204.

[0053] [Operations of Base Station 100 and Terminal 200] An example of operations in the base station 100 and terminal 200 having the above configuration will be described.

[0054] FIG. 8 is a sequence diagram showing an example of the operation of the base station 100 and the terminal 200.

[0055] In FIG. 8, the base station 100 determines information on the configuration, such as the transmission timing setting of the terminal 200 in a specific time resource (for example, slot / symbol) (S101).

[0056] The base station 100 transmits, for example, upper layer signaling information including the determined setting information to the terminal 200 (S102).

[0057] The base station 100 schedules, for example, data transmission and reception for the terminal 200 (S103). At this time, the base station 100 determines whether the resource scheduled for the terminal 200 is included in a specific time resource (for example, a slot / symbol).

[0058] For example, based on the scheduling result, the base station 100 instructs the terminal 200 to perform uplink transmission (for example, transmission of a Physical Uplink Shared Channel (PUSCH)) using a PDCCH (for example, including an Uplink grant) (S104). At this time, the base station 100 may notify the terminal 200 of information (for example, information on the type of slot / symbol) regarding whether or not the resource to be allocated for uplink transmission is a specific time resource (for example, slot / symbol).

[0059] The terminal 200 determines uplink transmission timing (e.g., PUSCH transmission timing) based on, for example, an uplink grant (PDCCH) transmitted from the base station 100 (S105). For example, the terminal 200 may determine whether the uplink transmission timing (allocated resource) notified from the base station 100 corresponds to a specific time resource (e.g., slot or symbol) or corresponds to another time resource different from the specific time resource, and may determine (or set or adjust) the PUSCH transmission timing.

[0060] The terminal 200 transmits a PUSCH based on an uplink grant (PDCCH) transmitted from the base station 100 and the determined transmission timing (S106).

[0061] [Uplink Transmission Timing Setting Method] A method for setting the uplink transmission timing of the terminal 200 in the base station 100 (e.g., the timing control unit 104) will be described. Note that the terminal 200 (e.g., the timing control unit 204) may set the uplink transmission timing, for example, assuming the method for setting the uplink transmission timing performed by the base station 100.

[0062] In this embodiment, the base station 100 and the terminal 200 individually set (or adjust) the uplink transmission timing in a specific time resource (e.g., slot / symbol) and the uplink transmission timing in other time resources (e.g., slot / symbol) different from the specific time resource.

[0063] Below, methods 1 to 3 relating to uplink transmission timing setting will be explained.

[0064] [Method 1] In method 1, the base station 100 receives N SBFD symbols or SBFD candidate symbols (e.g., corresponding to a specific time resource). TA,offset (offset value of transmission timing) and N in other symbols different from SBFD symbols and SBFD candidate symbols (for example, normal symbols with a unit transmission direction) TA,offset may be different from the above.

[0065] For example, the base station 100 may use N TA,offset may be set to 0. For example, the base station 100 may set N TA,offset may be set to a value different from the SBFD symbol and the BFD candidate symbol (for example, a value greater than or equal to 0).

[0066] As will be described later, for SBFD candidate symbols, the same N as for normal symbols is used. TA,offset The operation may be to set the following.

[0067] Here, "SBFD symbol" refers to, for example, a symbol to which SBFD is actually applied (for example, a symbol in which the same symbol has multiple subbands with different transmission directions).

[0068] Furthermore, an "SBFD candidate symbol" represents a symbol to which SBFD may be applied. For example, depending on the traffic situation, the SBFD candidate symbol may be applied to SBFD (become an SBFD symbol) or may not be applied to SBFD (become a normal symbol). For example, the SBFD candidate symbol may be set (or changed or overwritten) to either an SBFD symbol or a normal symbol by signaling from the base station 100 or the like.

[0069] Also, for example, N TA,offset may be set.

[0070] FIG. 9 shows an example of transmission and reception timing according to Method 1.

[0071] The example of Figure 9 shows the transmission and reception timing for five slots, Slot #0 to Slot #4. For example, Slot #0, Slot #3, and Slot #4 are slots consisting of normal symbols (symbols with a single transmission direction), and Slot #1 and Slot #2 are slots consisting of SBFD symbols. Also, as an example, three subbands are set on the SBFD symbols of Slot #1 and Slot #2.

[0072] 9 indicates the symbol type (e.g., normal symbol or SBFD symbol) and the transmission / reception timing in the base station 100. For example, "Normal DL" indicates a downlink slot consisting of normal symbols, and "Normal UL" indicates an uplink slot consisting of normal symbols. Also, for example, "SBFD DL" indicates a downlink slot (or downlink subband) consisting of SBFD symbols, and "SBFD UL" indicates an uplink slot (or uplink subband) consisting of SBFD symbols.

[0073] As shown in FIG. 9, in an uplink slot (Normal UL) consisting of normal symbols, TA,offsetis set to a value greater than 0. Therefore, as shown in FIG. 9, the symbol timing of Slot#3 is N TA,offset minutes earlier, and there is a N TA,offset There is a gap corresponding to

[0074] On the other hand, as shown in FIG. 9, in Slot #1 and Slot #2 consisting of SBFD symbols, N TA,offset is set to 0. Therefore, as shown in Fig. 9, in Slot #1 and Slot #2, the symbol timing of the uplink subband (SBFD UL) is the same as the symbol timing of the downlink subband (SBFD DL), and the symbol timing (or symbol boundary) between the SBFD UL and the SBFD DL coincides.

[0075] Therefore, in Figure 9, in Slot #1 and Slot #2, which consist of SBFD symbols, the symbol boundaries between multiple subbands are aligned, so self-interference from the SBFD downlink subband (SBFD DL) to the SBFD uplink subband (SBFD UL) can be suppressed.

[0076] In method 1, which symbols are set as SBFD symbols (or SBFD candidate symbols) (for example, symbol types) may be notified to terminal 200 by the following notification method.

[0077] <Notification Method 1> In notification method 1, whether or not a symbol is an SBFD symbol (or the symbol type) is notified using UE-specific DCI.

[0078] For UE-specific DCI, for example, DCI formats 0_0, 0_1, 0_2, 1_0, 1_1, and 1_2 may be used, or other DCI formats may be used.

[0079] For example, the UE-specific DCI may indicate whether the resources scheduled by the DCI (e.g., resources used for PUSCH, Physical Uplink Control Channel (PUCCH), and Sounding Reference Signal (SRS)) are normal symbols or SBFD symbols.

[0080] Note that, after scheduling, base station 100 can notify the symbol type using UE-specific DCI. For example, base station 100 can notify terminal 200 of the symbol type after determining whether each symbol assigned to terminal 200 is to be used as an SBFD symbol or a normal symbol. Therefore, in notification method 1, SBFD candidate symbols do not need to be used, and base station 100 may set SBFD symbols instead of SBFD candidate symbols.

[0081] An example of notification using notification method 1 is given below.

[0082] Example 1: The symbol type (either a normal symbol or an SBFD symbol) may be signaled using a 1-bit field of the UE-specific DCI. For example, a 1-bit field may be added to the DCI. For example, a value of "0" in the field may indicate a normal symbol, and a value of "1" in the field may indicate an SBFD symbol.

[0083] Example 2: The symbol type (either a normal symbol or an SBFD symbol) may be signaled by reusing an existing field of the UE-specific DCI, such as a field that configures time domain resources, such as "Time domain resource assignment", "PUCCH resource indicator", or "PDSCH-to-HARQ_feedback timing indicator".

[0084] For example, in "Time domain resource assignment," information (e.g., information in a table format) relating to the association between time domain resources (e.g., parameter setting values ​​relating to time domain resources) and values ​​notified by DCI fields (e.g., values ​​relating to indexes) is configured in advance by RRC signaling. For example, in "Time domain resource assignment," one of the settings in the table (e.g., one of the parameters) may include a setting indicating either "SBFD symbol" or "normal symbol" as the symbol type.

[0085] The notification example of notification method 1 has been described above.

[0086] According to notification method 1, the base station 100 can notify the terminal 200 of whether or not the symbol is an SBFD symbol, in addition to instructing uplink transmission, by using UE-specific DCI, thereby reducing notification overhead.

[0087] <Notification Method 2> In notification method 2, whether or not a symbol is an SBFD symbol (or the symbol type) is notified using group-common DCI.

[0088] For the group-common DCI, for example, DCI formats 2_0, 2_1, 2_2, 2_3, 2_4, 2_5, 2_6, and 2_7 may be used, or other DCI formats may also be used.

[0089] In notification method 2, the base station 100 can notify the symbol type using group-common DCI after scheduling, and therefore, as in notification method 1, the SBFD symbol may be set instead of the SBFD candidate symbol.

[0090] An example of notification using notification method 2 is given below.

[0091] For example, a bit field indicating whether or not it is an SBFD symbol may be added to DCI format 2_0.

[0092] For example, the added field may indicate the symbol types (e.g., SBFD symbol and normal symbol) of multiple slots corresponding to the Slot Format Indicator (SFI). For example, if the SFI can indicate the slot formats of up to five slots, a 5-bit field may be added to DCI format 2_0 to indicate the symbol types. Each bit of the added bit field (e.g., 5 bits) may correspond to each slot (e.g., 5 slots) indicated by the SFI.

[0093] For example, in the added bit field, a bit value of "0" may indicate a normal symbol, and a bit value of "1" may indicate an SBFD symbol. As an example, if the value notified in a 5-bit bit field is "0b01110", it means that of the five slots notified by the SFI, the symbols in the second, third, and fourth slots are SBFD symbols, and the other symbols (the first and fifth symbols) are normal symbols.

[0094] The number of slots whose slot format is notified by the SFI is not limited to 5, and may be other numbers. The size (number of bits) of the bit field added to the group-common DCI (e.g., DCI format 2_0) may be set according to the number of slots whose slot format is notified by the SFI.

[0095] Here, for example, semi-statically configured uplink transmission such as PUSCH transmission by configured grant or periodic transmission of SRS is not instructed to transmit by UE-specific DCI, and transmission is performed without DCI. For this reason, in notification method 1 using UE-specific DCI, it is difficult to notify the symbol type for semi-statically configured transmission. In contrast, in notification method 2, whether or not it is an SBFD symbol can be notified by group common DCI, and therefore it is also applicable to semi-statically configured transmission.

[0096] <Notification Method 3> In notification method 3, whether or not a symbol is an SBFD symbol (or the symbol type) is notified using semi-static signaling (for example, RRC signaling).

[0097] For example, multiple slots / symbols may be set as SBFD candidate symbols.

[0098] In notification method 3, the symbol type is set quasi-statically before the scheduling is determined. For example, if a certain symbol is set (or confirmed) as an SBFD symbol before the scheduling is determined, the symbol cannot be switched to a normal symbol depending on the communication environment, etc., and the flexibility of scheduling may be reduced. For this reason, in notification method 3, for example, base station 100 may set for each symbol whether it is an SBFD candidate symbol.

[0099] An example of notification using notification method 3 is given below.

[0100] For example, a setting of an SBFD candidate symbol may be added to "tdd-UL-DL-ConfigurationDedicated," which is RRC signaling that sets the symbol transmission direction for each terminal individually. For example, a setting of the first (or starting or leading) symbol number (e.g., any of 0 to 13) where an SBFD candidate symbol is arranged within a slot, and the number of SBFD candidate symbols (or allocation length; e.g., any of 0 to 14) may be added. As an example, when symbol number = 0 and number of symbols = 14 are set as the SBFD candidate symbol setting, all symbols within the slot are set to SBFD candidate symbols. Note that the symbol number and number of symbols are merely examples, and other values ​​may be used.

[0101] In notification method 3, a symbol that can be an SBFD symbol (for example, a symbol to which SBFD may be applied) can be set as an SBFD candidate symbol. As described above, notification method 1 using UE-specific DCI is difficult to apply to semi-statically configured transmission (for example, Configured grant, etc.), whereas notification method 3 can semi-statically set symbol types for multiple slots / symbols, and therefore can be applied to semi-statically configured transmission.

[0102] Notification methods 1 to 3 have been described above.

[0103] It should be noted that any of notification methods 1 to 3 may be combined.

[0104] For example, a case where all three notification methods 1 to 3 are combined will be described.

[0105] For example, the base station 100 quasi-statically sets a symbol that can become an SBFD symbol to an SBFD candidate symbol by notification method 3. Furthermore, after scheduling, the base station 100 may set the symbol type (SBFD symbol or normal symbol) by notification method 1 for uplink transmissions that are dynamically scheduled by DCI, and may set the symbol type (SBFD symbol or normal symbol) by notification method 2 for uplink transmissions that are quasi-statically set. In this case, the symbol type of the SBFD candidate symbol set by notification method 3 may be overwritten to either the SBFD symbol or the normal symbol in accordance with the notification by notification method 1 or notification method 2. In this way, the symbol type can be flexibly switched by combining notification methods 1 to 3, thereby improving scaling flexibility and improving resource utilization efficiency.

[0106] For example, N in each of the SBFD symbol and the normal symbol TA,offset may be set individually. For example, N TA,offset may be set to 0. Also, for example, N TA,offset may be set to a value greater than or equal to 0.

[0107] In addition, in Method 1, for example, N in the SBFD candidate symbol TA,offset may be set to 0 (e.g., the same value as the SBFD symbol) or the same value as the normal symbol. TA,offset Whether to set to 0 or to the same value as that of a normal symbol may be determined, for example, by semi-static setting or definition.

[0108] N in SBFD candidate symbols TA,offset When is set to 0, the default behavior of the SBFD candidate symbol may be the same as that of the SBFD symbol. For example, when there is no notification of the symbol type for the SBFD candidate symbol, it may be assumed that the SBFD candidate symbol has a subband. In addition, N TA,offset When is set to the same value as a normal symbol, the default operation for the SBFD candidate symbol may be the same as that for a normal symbol. For example, when there is no notification of the symbol type for the SBFD candidate symbol, it may be assumed that there is no subband for the SBFD candidate symbol. Note that when there is notification of the symbol type for the SBFD candidate symbol, the operation corresponding to the notified symbol type (or N TA,offset Setting of the above) may be performed.

[0109] The above describes the case where the three notification methods 1 to 3 are combined.

[0110] In this way, in method 1, it is possible to match the symbol timing (or symbol boundary) between the uplink subband and the downlink subband in the SBFD symbol and the SBFD candidate symbol, thereby reducing self-interference in the base station 100.

[0111] Furthermore, in method 1, the symbol type can be flexibly switched from an SBFD candidate symbol to an SBFD symbol (for example, a symbol with a subband) or a normal symbol (for example, a symbol without a subband), thereby improving the flexibility of scaling and improving the resource utilization efficiency.

[0112] [Method 2] In Method 2, the base station 100 calculates N TA,offset (transmission timing offset value) and N in other time resources different from a specific time resource TA,offset may be different from the above.

[0113] For example, the base station 100 may TA,offset Set to 0 and N in other slots / symbols TA,offset may be set to a different value (e.g., greater than or equal to 0) for a particular slot / symbol.

[0114] In the following, a specific slot / symbol will be referred to as a "transmission timing change slot / symbol (or transmission timing change symbol)," and other slots / symbols different from the transmission timing change slot / symbol will be referred to as a "normal slot / symbol (or normal symbol)."

[0115] In method 2, which symbol is set as the transmission timing change symbol (for example, the symbol type) may be notified to terminal 200 by the following notification method.

[0116] <Notification Method 1> In notification method 1, whether or not a symbol is a transmission timing change symbol (or the symbol type) is notified using UE-specific DCI.

[0117] For UE-specific DCI, for example, DCI formats 0_0, 0_1, 0_2, 1_0, 1_1, and 1_2 may be used, or other DCI formats may be used.

[0118] For example, the UE-specific DCI may indicate whether the resource scheduled by the DCI (e.g., the resource used for PUSCH, PUCCH, or SRS) is a normal symbol or a transmission timing change symbol.

[0119] An example of notification using notification method 1 is given below.

[0120] Example 1: The symbol type (either a normal symbol or a transmission timing change symbol) may be notified using a 1-bit field of UE-specific DCI. For example, a value of "0" in the field may indicate a normal symbol, and a value of "1" in the field may indicate a transmission timing change symbol.

[0121] Example 2: The symbol type (either a normal symbol or a transmission timing change symbol) may be notified by reusing existing fields of the UE-specific DCI. For example, fields that configure time domain resources, such as "Time domain resource assignment," "PUCCH resource indicator," and "PDSCH-to-HARQ_feedback timing indicator," may be reused.

[0122] For example, in "Time domain resource assignment," information (e.g., information in a table format) relating to the association between time domain resources (e.g., parameter setting values ​​relating to time domain resources) and values ​​notified by DCI fields (e.g., values ​​relating to indexes) is configured in advance by RRC signaling. For example, in "Time domain resource assignment," one of the settings in the table (e.g., one of the parameters) may include a setting indicating either a "transmission timing change symbol" or a "normal symbol" as the symbol type.

[0123] The notification examples of the notification method have been described above.

[0124] According to notification method 1, the base station 100 can use the UE-specific DCI to notify the terminal 200 whether or not the symbol is a transmission timing change symbol in addition to instructing uplink transmission, thereby reducing notification overhead.

[0125] <Notification Method 2> In notification method 2, whether or not a symbol is a transmission timing change symbol (or the symbol type) is notified using group-common DCI.

[0126] For the group-common DCI, for example, DCI formats 2_0, 2_1, 2_2, 2_3, 2_4, 2_5, 2_6, and 2_7 may be used, or other DCI formats may also be used.

[0127] An example of notification using notification method 2 is given below.

[0128] For example, a bit field indicating whether or not a symbol is a transmission timing change symbol may be added to DCI format 2_0.

[0129] For example, the symbol types of multiple slots corresponding to the SFI (e.g., either a transmission timing change symbol or a normal symbol) may be notified by the added field. For example, if the slot formats of up to five slots can be notified by the SFI, a 5-bit field may be added to DCI format 2_0 to notify the symbol types. Each bit of the added bit field (e.g., 5 bits) may correspond to each slot (e.g., 5 slots) notified by the SFI.

[0130] For example, in the added bit field, a bit value of "0" may indicate a normal symbol, and a bit value of "1" may indicate a transmission timing change symbol. As an example, if the value notified in a 5-bit bit field is "0b01110", it means that of the five slots notified by the SFI, the symbols in the second, third, and fourth slots are transmission timing change symbols, and the other symbols (the first and fifth symbols) are normal symbols.

[0131] The number of slots whose slot format is notified by the SFI is not limited to 5, and may be other numbers. The size (number of bits) of the bit field added to the group-common DCI (e.g., DCI format 2_0) may be set according to the number of slots whose slot format is notified by the SFI.

[0132] Here, for example, semi-statically configured uplink transmission, such as PUSCH transmission by a configured grant or periodic transmission of SRS, is not instructed to transmit by a UE-specific DCI and is transmitted without DCI. Therefore, in notification method 1 using UE-specific DCI, it is difficult to notify the symbol type for semi-statically configured transmission. In contrast, in notification method 2, it is possible to notify whether or not the symbol is a transmission timing change symbol using a group common DCI, and therefore it is also applicable to semi-statically configured transmission.

[0133] <Notification Method 3> In notification method 3, whether or not a symbol is a transmission timing change symbol (or the symbol type) is notified using semi-static signaling (for example, RRC signaling).

[0134] For example, multiple slots / symbols may be set as transmission timing change symbols.

[0135] An example of notification using notification method 3 is given below.

[0136] For example, a setting for a transmission timing change symbol may be added to "tdd-UL-DL-ConfigurationDedicated," which is RRC signaling that sets the symbol transmission direction for each terminal individually. For example, a setting for the first (or starting or head) symbol number (e.g., any one of 0 to 13) in which the transmission timing change symbol is arranged within a slot and the number of transmission timing change symbols (or allocation length, e.g., any one of 0 to 14) may be added. As an example, when the symbol number = 0 and the number of symbols = 14 are set as the transmission timing change symbol setting, all symbols within the slot are set as transmission timing change symbols. Note that the symbol number and the number of symbols are merely examples, and other values ​​may be used.

[0137] For example, notification method 1 using UE-specific DCI is difficult to apply to semi-statically configured transmissions (e.g., Configured grant, etc.), whereas notification method 3 can semi-statically set symbol types for multiple slots / symbols, and is therefore applicable to semi-statically configured transmissions.

[0138] Notification methods 1 to 3 have been described above.

[0139] As with method 1, method 2 may also be used in combination with any of notification methods 1 to 3.

[0140] In Method 2, N TA,offset may be set individually. For example, N TA,offset may be set to 0. Also, for example, N TA,offset may be set to a value different from the transmission timing change symbol (for example, a value greater than or equal to 0).

[0141] In Method 2, N TA,offsetBy setting to 0, when the transmission timing change symbol is an SBFD symbol, it becomes possible to align the symbol timing (or symbol boundary) between the uplink subband and the downlink subband, thereby reducing self-interference at base station 100.

[0142] Furthermore, in method 2, terminal 200 adjusts the uplink transmission timing based on an instruction from base station 100 (e.g., information related to transmission timing modification symbols) without specifying which symbols are SBFD symbols. This allows terminal 200 to operate without being aware of which symbols are SBFD symbols, even when SBFD is applied, for example. In this way, method 2 can achieve SBFD in a transparent manner.

[0143] Thus, according to Method 2, it is possible to align the symbol timing between the uplink and downlink in the transmission timing change symbol, thereby reducing self-interference in SBFD at the base station 100. Furthermore, according to Method 2, the base station 100 can transparently control subbands and select whether to apply SBFD (for example, whether to allocate subbands to symbols) depending on the communication environment (for example, downlink and uplink traffic loads, the need for uplink coverage, delay requirements, etc.), thereby improving the flexibility of scheduling and improving resource utilization efficiency.

[0144] In Method 2, different equations (2) and (3) may be applied to calculate the uplink transmission timing for the transmission timing change symbol and the normal symbol, respectively.

[0145] where N TA,offset The same value (common value) may be applied to the normal symbol and the transmission timing change symbol. TA,offset2 is set in a terminal 200 that uses a transmission timing change symbol (for example, a terminal 200 that supports SBFD operation), and does not need to be set in a terminal 200 that uses a normal symbol.

[0146] In this way, the base station 100 transmits to the terminal 200 a common offset value (N TA,offset ), and an offset value (N TA,offset2 ) may be set.

[0147] Also, N TA,offset may be set to cell-specific, and may be shared with terminals 200 that do not support the transmission timing modification symbol. TA,offset2 may be set to UE-specific, for example, and may be set to the terminal 200 corresponding to the transmission timing change symbol.

[0148] N TA,offset2 For example, N TA,offset A negative value of the same magnitude as TA,offset As an example, N TA,offset If =25600 is set, N TA,offset2 =-25600. As a result, the transmission timing change symbol has an offset value (N TA,offset +N TA,offset2 ) is set to 0, so that the symbol timing between the uplink and downlink subbands can be matched.

[0149] In this way, N TA,offset2 By adding the existing parameter (N TA,offset ), it is possible to improve compatibility with existing operations when the terminal 200 performs SBFD operations.

[0150] [Method 3] In Method 3, an additional timing setting value (e.g., "N TA '") applies.

[0151] For example, the base station 100 may set a transmission timing setting (N TA ') and the transmission timing setting value (N TA ) may be different.

[0152] N TA ', the existing N TA The set value (for example, absolute value, or increase / decrease value (or difference)) may be notified separately from N. TA The set value of ' may be notified to terminal 200 by MAC signaling or RRC signaling, for example.

[0153] Also, N TA and N TA ' may be managed separately as different cumulative values. For example, N TA The value of N can be increased or decreased by the Timing Advance Command in MAC signaling. TA The value of ' is, for example, N TA Different Timing Advance Commands may be used to increase or decrease by different amounts.

[0154] The transmission timing of the normal symbol and the transmission timing of the transmission timing change symbol may be calculated using equations (4) and (5), respectively.

[0155] For example, in the transmission timing change symbol, N TA '=N TA -N TA,offset So that N TA ' may be set. This allows the value of N TA,offset This makes it possible to eliminate (or cancel) the influence of the above. For example, when SBFD is applied to a transmission timing change symbol, it is possible to align the symbol timing (or symbol boundary) between a downlink subband and an uplink subband in the SBFD symbol.

[0156] In addition, N TAThe value of N' is not limited to the above example. TA Since N′ can be increased or decreased by the Timing Advance Command, the transmission timing can be dynamically adjusted under the control of the base station 100. For example, TA By adjusting ', the timing difference between the uplink and downlink symbols in the SBFD symbol can be adjusted within the cyclic prefix (CP), thereby reducing the timing difference between the normal symbol and the transmission timing change symbol.

[0157] The transmission timing of the transmission timing change symbol may be calculated by the following equation (6) instead of equation (5).

[0158] where N TA2 is N TA ' is a timing setting value similar to that of the formula above, but the format is different. For example, N TA '=N TA + N TA2 For example, the base station 100 may transmit to the terminal 200 a timing setting value (N TA ), and a timing setting value specific to the transmission timing change symbol (N TA2 ) may be set.

[0159] In addition, in Method 3, the notification method of Method 2 may be applied as a method for notifying which slot / symbol is the transmission timing change slot / symbol.

[0160] Thus, according to Method 3, it is possible to align the symbol timing of the uplink and downlink in the transmission timing modification symbol, thereby reducing self-interference at the base station 100 in SBFD. Furthermore, according to Method 3, the timing of uplink transmission can be dynamically controlled using a Timing Advance Command, thereby improving the flexibility of timing control at the base station 100. Furthermore, according to Method 3, similar to Method 2, the base station 100 can transparently control subbands and can select whether to apply SBFD (e.g., whether to assign subbands to symbols) depending on the communication environment (e.g., downlink and uplink traffic loads, the need for uplink coverage, delay requirements, etc.), thereby improving the flexibility of scheduling and improving resource utilization efficiency.

[0161] Methods 1 to 3 for setting the uplink transmission timing have been described above.

[0162] As described above, in this embodiment, the base station 100 and the terminal 200 individually adjust the uplink transmission timing in a specific time resource (for example, an SBFD symbol, an SBFD candidate symbol, or a transmission timing change symbol) and the uplink transmission timing in other time resources (for example, a normal symbol), and transmit and receive signals based on each transmission timing.

[0163] As a result, for example, in a specific time resource to which SBFD is applied, the symbol timing (or symbol boundary) can be matched between the uplink subband and the downlink subband, and self-interference from the downlink subband to the uplink subband can be reduced. On the other hand, for example, in other time resources to which SBFD is not applied, the uplink symbol timing can be advanced, thereby improving the uplink reception performance at the base station 100.

[0164] Therefore, according to this embodiment, it is possible to appropriately control the transmission timing in wireless communication.

[0165] (Other Embodiments) [Symbol Overlap] The uplink transmission timing (e.g., symbol timing) may differ between SBFD symbols (or transmission timing change symbols) and normal symbols, and therefore the symbols may overlap. For example, in the example shown in FIG. 9 , the last symbol (SBFD symbol) of Slot #2 overlaps with the first symbol (normal symbol) of Slot #3. Therefore, the same terminal 200 cannot perform uplink transmission using both the last symbol of Slot #2 and the first symbol of Slot #3. To avoid such overlap, the following method may be applied.

[0166] <Method 1> In method 1, the later symbol of the overlapping symbols is given priority.

[0167] For example, the terminal 200 may transmit the signal of the later symbol among the overlapping symbols and not transmit the signal of the earlier symbol (for example, may discard or drop the signal).Furthermore, the base station 100 may not perform allocation to the earlier symbol that overlaps with the later symbol by scheduling.

[0168] In the example shown in FIG. 9, in the last symbol of Slot#2, terminal 200 does not need to transmit a signal, and base station 100 does not need to allocate resources.

[0169] <Method 2> In method 2, the SBFD symbol (or transmission timing change symbol) is given priority among the overlapping symbols.

[0170] For example, the terminal 200 may transmit a signal of the SBFD symbol (or a transmission timing change symbol) among the overlapping symbols, but may not transmit a signal of the normal symbol. Furthermore, the base station 100 may not allocate the SBFD symbol (or a transmission timing change symbol) to the normal symbol that overlaps with the SBFD symbol (or a transmission timing change symbol) by scheduling.

[0171] In the example shown in FIG. 9, in the first symbol (normal symbol) of Slot #3, terminal 200 does not need to transmit a signal, and base station 100 does not need to allocate resources.

[0172] Method 2 is effective, for example, when it is necessary to improve the performance of the SBFD symbol (or the transmission timing change symbol). For example, since the performance of the SBFD symbol may be degraded due to interference between the uplink and the downlink, prioritizing the SBFD symbol can improve the performance of the SBFD symbol, or can suppress performance degradation by not discarding the transmission of the symbol.

[0173] <Method 3> In method 3, priority is given to normal symbols among overlapping symbols.

[0174] For example, terminal 200 may transmit signals of normal symbols among the overlapping symbols, and may not transmit signals of SBFD symbols (or transmission timing change symbols). Furthermore, base station 100 may not allocate signals to SBFD symbols (or transmission timing change symbols) that overlap with normal symbols by scheduling.

[0175] In the example shown in FIG. 9, in the last symbol (SBFD symbol or transmission timing change symbol) of Slot #2, terminal 200 does not need to transmit a signal, and base station 100 does not need to allocate resources.

[0176] When the normal symbols are shared between terminal 200 and existing terminals (for example, when transmission and reception are restricted to existing terminals using SBFD symbols), discarding the transmission of the normal symbols may affect the operation of existing terminals. Therefore, method 3 is effective for protecting the operation of existing terminals.

[0177] [Regarding Transient Periods] It is assumed that transient periods overlap in transmissions using consecutive time resources (for example, slots / symbols).

[0178] The transient period represents a power transition period when, for example, transmission is turned on / off or when transmission is performed at different transmission power levels.

[0179] If the transient period of the SBFD symbol (or transmission timing change symbol) and the transient period of the normal symbol overlap, the transient period may be set by the following method.

[0180] <Method 1> In method 1, the transient period is divided equally between both symbols.

[0181] For example, when the transient periods overlap, the transient period may be equally divided into SBFD symbols (or transmission timing change symbols) and normal symbols.

[0182] Fig. 10 shows an example of setting a transient period using Method 1. In Fig. 10, "SBFD symbol" represents an SBFD symbol, and "Normal symbol" represents a normal symbol. As shown in Fig. 10, the transient period spans both symbols equally.

[0183] Method 1 is effective, for example, when it is desired that the influence of the transient period be equally extended to both SBFD symbols (or transmission timing change symbols) and normal symbols.

[0184] Note that, although the case where the transient period is equally divided between SBFD symbols (or transmission timing change symbols) and normal symbols has been described here, this is not limited to this, and for example, the transient period may be set unevenly between SBFD symbols (or transmission timing change symbols) and normal symbols.

[0185] <Method 2> In method 2, the SBFD symbol (or transmission timing change symbol) is given priority.

[0186] For example, when a transient period overlaps with consecutive symbols, the transient period is assigned to the period of a normal symbol.

[0187] Fig. 10 shows an example of setting a transient period according to Method 2. As shown in Fig. 10, the transient period is set to a normal symbol.

[0188] Method 2 is effective when it is necessary to improve the performance of the SBFD symbol (or the transmission timing change symbol). For example, since the performance of the SBFD symbol may be degraded due to interference between the uplink and the downlink, the performance of the SBFD symbol can be improved by prioritizing the SBFD symbol, or the degradation of performance can be suppressed by setting the transient period outside the SBFD symbol.

[0189] <Method 3> In method 3, normal symbols are given priority.

[0190] For example, when the transient period overlaps with consecutive symbols, the transient period is allocated to the period of the SBFD symbol (or transmission timing change symbol).

[0191] Fig. 10 shows an example of setting a transient period according to Method 3. As shown in Fig. 10, the transient period is set to SBFD symbols.

[0192] When the normal symbol is shared between terminal 200 and existing terminals (for example, when transmission and reception are restricted to existing terminals using the SBFD symbol), setting the transient period to the normal symbol period may affect the operation of existing terminals. Therefore, method 3 is effective when protecting the operation of existing terminals.

[0193] The transient period has been explained above.

[0194] In the above-described embodiment, the number of subbands, the number of terminals, the number of slots, the number of symbols, and parameters related to transmission timing (N TA , N TA ', N TA,offset , N TA,offset2 , the number of bits in the notification field in the DCI) are examples and are not limiting.

[0195] (Supplementary Note) Information indicating whether the terminal 200 supports the functions, operations, or processes described in the above-described embodiments may be transmitted (or notified) from the terminal 200 to the base station 100, for example, as capability information or capability parameters of the terminal 200.

[0196] The capability information may include an information element (IE) that individually indicates whether or not the terminal 200 supports at least one of the functions, operations, or processes described in the above-described embodiments. Alternatively, the capability information may include an information element that indicates whether or not the terminal 200 supports a combination of any two or more of the functions, operations, or processes described in the above-described embodiments.

[0197] For example, the base station 100 may determine (or decide or assume) the functions, operations, or processes that the terminal 200 that transmitted the capability information supports (or does not support) based on the capability information received from the terminal 200. The base station 100 may perform operations, processes, or controls according to the determination result based on the capability information. For example, the base station 100 may control the uplink transmission timing for the terminal 200 based on the capability information received from the terminal 200.

[0198] Note that the fact that terminal 200 does not support some of the functions, operations, or processes described in the above-described embodiments may be interpreted as meaning that such some of the functions, operations, or processes are restricted in terminal 200. For example, information or a request regarding such restrictions may be notified to base station 100.

[0199] Information regarding the capabilities or limitations of terminal 200 may, for example, be defined in a standard, or may be implicitly notified to base station 100 in association with information known at base station 100 or information transmitted to base station 100.

[0200] (Control Signal) In the present disclosure, a downlink control signal (or downlink control information) related to an embodiment of the present disclosure may be, for example, a signal (or information) transmitted in a Physical Downlink Control Channel (PDCCH) of a physical layer, or a signal (or information) transmitted in a Medium Access Control Control Element (MAC CE) or Radio Resource Control (RRC) of a higher layer. Furthermore, the signal (or information) is not limited to being notified by a downlink control signal, but may be predefined in a specification (or standard) or preconfigured in a base station and a terminal.

[0201] In the present disclosure, an uplink control signal (or uplink control information) related to an embodiment of the present disclosure may be, for example, a signal (or information) transmitted in a PUCCH of a physical layer, or a signal (or information) transmitted in a MAC CE or RRC of a higher layer. Furthermore, the signal (or information) is not limited to being notified by an uplink control signal, but may be predefined in a specification (or standard) or preconfigured in a base station and a terminal. Furthermore, the uplink control signal may be replaced with, for example, uplink control information (UCI), 1st stage sidelink control information (SCI), or 2nd stage SCI.

[0202] (Base Station) In an embodiment of the present disclosure, the base station may be a Transmission Reception Point (TRP), a cluster head, an access point, a Remote Radio Head (RRH), an eNodeB (eNB), a gNodeB (gNB), a Base Station (BS), a Base Transceiver Station (BTS), a parent device, a gateway, or the like. In sidelink communication, a terminal may play the role of a base station. Instead of a base station, a relay device that relays communication between an upper node and a terminal may be used. Alternatively, a roadside unit may be used.

[0203] (Uplink / Downlink / Sidelink) An embodiment of the present disclosure may be applied to, for example, any of the uplink, downlink, and sidelink. For example, an embodiment of the present disclosure may be applied to a Physical Uplink Shared Channel (PUSCH), a Physical Uplink Control Channel (PUCCH), or a Physical Random Access Channel (PRACH) in the uplink, a Physical Downlink Shared Channel (PDSCH), a PDCCH, or a Physical Broadcast Channel (PBCH) in the downlink, or a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Control Channel (PSCCH), or a Physical Sidelink Broadcast Channel (PSBCH) in the sidelink.

[0204] The PDCCH, PDSCH, PUSCH, and PUCCH are examples of a downlink control channel, a downlink data channel, an uplink data channel, and an uplink control channel, respectively. The PSCCH and PSSCH are examples of a sidelink control channel and a sidelink data channel. The PBCH and PSBCH are examples of a broadcast channel, and the PRACH is an example of a random access channel.

[0205] (Data Channel / Control Channel) An embodiment of the present disclosure may be applied to, for example, either a data channel or a control channel. For example, the channel in an embodiment of the present disclosure may be replaced with any of the data channels PDSCH, PUSCH, and PSSCH, or the control channels PDCCH, PUCCH, PBCH, PSCCH, and PSBCH.

[0206] (Reference Signal) In one embodiment of the present disclosure, a reference signal is, for example, a signal known by both a base station and a mobile station, and may also be called a Reference Signal (RS) or a pilot signal. The reference signal may be any of 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), or a Sounding Reference Signal (SRS).

[0207] (Time Interval) In one embodiment of the present disclosure, the unit of time resource is not limited to one or a combination of slots and symbols, but may be, for example, a time resource unit such as a frame, a superframe, a subframe, a slot, a time slot subslot, a minislot, or a symbol, an Orthogonal Frequency Division Multiplexing (OFDM) symbol, a Single Carrier-Frequency Division Multiplexing (SC-FDMA) symbol, or another time resource unit. Furthermore, the number of symbols included in one slot is not limited to the number of symbols exemplified in the above-mentioned embodiment, and may be another number of symbols.

[0208] (Frequency Band) An embodiment of the present disclosure may be applied to either a licensed band or an unlicensed band.

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

[0210] An embodiment of the present disclosure may be applied to a terrestrial network, a non-terrestrial network (NTN) using a satellite or a high altitude pseudo satellite (HAPS), or a terrestrial network in which transmission delay is large compared to the symbol length or slot length, such as a network with a large cell size or an ultra-wideband transmission network.

[0211] (Antenna Port) In one embodiment of the present disclosure, an antenna port refers to a logical antenna (antenna group) consisting of one or more physical antennas. For example, an antenna port does not necessarily refer to a single physical antenna, but may refer to an array antenna consisting of multiple antennas. For example, the number of physical antennas that an antenna port is composed of is not specified, and the antenna port may be specified as the smallest unit by which a terminal station can transmit a reference signal. Furthermore, an antenna port may also be specified as the smallest unit by which a weighting of a precoding vector is multiplied.

[0212] 5G NR System Architecture and Protocol Stack 3GPP continues work on the next release of fifth-generation cellular technology (also referred to simply as "5G"), which includes 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 at the end of 2017, allowing for the prototyping and commercial deployment of 5G NR-compliant devices (e.g., smartphones).

[0213] For example, the system architecture generally assumes a Next Generation - Radio Access Network (NG-RAN) comprising gNBs. The gNBs provide UE-side termination of NG radio access user plane (SDAP / PDCP / RLC / MAC / PHY) and control plane (RRC) protocols. The gNBs are connected to each other via an Xn interface. The gNBs are also connected to a Next Generation Core (NGC) via a Next Generation (NG) interface, more specifically to an Access and Mobility Management Function (AMF) (e.g., a specific core entity performing AMF) via an NG-C interface, and to a User Plane Function (UPF) (e.g., a specific core entity performing UPF) via an NG-U interface. The NG-RAN architecture is shown in Figure 11 (see, for example, 3GPP TS 38.300 v15.6.0, section 4).

[0214] The NR user plane protocol stack (see, for example, 3GPP TS 38.300, section 4.4.1) includes a PDCP (Packet Data Convergence Protocol (see, for example, TS 38.300, section 6.4)) sublayer, a RLC (Radio Link Control (see, for example, TS 38.300, section 6.3)) sublayer, and a MAC (Medium Access Control (see, for example, TS 38.300, section 6.2)) sublayer, which are terminated on the network side in the gNB. A new access stratum (AS) sublayer (SDAP: Service Data Adaptation Protocol) has also been introduced above PDCP (see, for example, 3GPP TS 38.300, section 6.5). A control plane protocol stack has also been defined for the NR (see, for example, TS 38.300, section 4.4.2). An overview of Layer 2 functions is described in Section 6 of TS 38.300. The functions of the PDCP sublayer, RLC sublayer, and MAC sublayer are listed in clauses 6.4, 6.3, and 6.2 of TS 38.300, respectively. The functions of the RRC layer are listed in clause 7 of TS 38.300.

[0215] For example, the Medium-Access-Control layer handles logical channel multiplexing and scheduling and scheduling-related functions, including handling various numerologies.

[0216] For example, the physical layer (PHY) is responsible for coding, PHY HARQ processing, modulation, multi-antenna processing, and mapping of signals to appropriate physical time-frequency resources. The physical layer also handles 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 for transmitting a specific transport channel, and each transport channel is mapped to a corresponding physical channel. For example, physical channels include the Physical Random Access Channel (PRACH), the Physical Uplink Shared Channel (PUSCH), and the Physical Uplink Control Channel (PUCCH) as uplink physical channels, and the Physical Downlink Shared Channel (PDSCH), the Physical Downlink Control Channel (PDCCH), and the Physical Broadcast Channel (PBCH) as downlink physical channels.

[0217] NR use cases / deployment scenarios may include enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), and massive machine-type communication (mMTC), which have diverse 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 approximately three times those offered by IMT-Advanced. On the other hand, URLLC imposes stricter requirements for ultra-low latency (0.5 ms for user plane latency in both UL and DL) and high reliability (1-10-5 within 1 ms). Finally, mMTC may require preferably high connection density (1,000,000 devices / km in urban environments), wide coverage in adverse environments, and extremely long battery life (15 years) for low-cost devices.

[0218] Therefore, OFDM numerology (e.g., subcarrier spacing, OFDM symbol length, cyclic prefix (CP) length, number of symbols per scheduling interval) suitable for one use case may not be valid for another use case. For example, low-latency services may preferably require a shorter symbol length (and therefore a larger subcarrier spacing) and / or fewer symbols per scheduling interval (also referred to as TTI) than mMTC services. Furthermore, deployment scenarios with large channel delay spreads may preferably require a longer CP length than scenarios with short delay spreads. The subcarrier spacing may be optimized accordingly to maintain similar CP overhead. NR may support one or more subcarrier spacing values. Correspondingly, subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, etc. are currently considered. The symbol length Tu and subcarrier spacing Δf are directly related by the formula Δf = 1 / Tu. Similar to LTE systems, the term "resource element" can be used to mean the smallest resource unit consisting of one subcarrier for the length of one OFDM / SC-FDMA symbol.

[0219] In the new radio system 5G-NR, for each numerology and each carrier, a resource grid of subcarriers and OFDM symbols is defined for each uplink and downlink. Each element of the resource grid is called a resource element and is specified based on a frequency index in the frequency domain and a symbol position in the time domain (see 3GPP TS 38.211 v15.6.0).

[0220] <Functional Separation Between NG-RAN and 5GC in 5G NR> Figure 12 shows 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.

[0221] For example, gNB and ng-eNB host the following main functions: - Radio Resource Management functions such as Radio Bearer Control, Radio Admission Control, Connection Mobility Control, dynamic allocation (scheduling) of resources to UEs in both uplink and downlink; - IP header compression, ciphering and integrity protection of data; - AMF selection at UE attach time if routing to the AMF cannot be determined from the information provided by the UE; - Routing of user plane data towards the UPF; - Routing of control plane information towards the AMF; - Connection setup and release; - Scheduling and transmission of paging messages; - Scheduling and transmission of system broadcast information (sourced from the AMF or Operation, Admission, Maintenance (OAM)); - Configuration of measurements and measurement reports for mobility and scheduling; - Transport level packet marking in the uplink; - Session management; Support for network slicing; - QoS flow management and mapping to data radio bearers; - Support for UEs in RRC_INACTIVE state; - NAS message delivery function; - Radio access network sharing; - Dual connectivity; - Close coordination between NR and E-UTRA.

[0222] The Access and Mobility Management Function (AMF) hosts the following main functions: - Termination of Non-Access Stratum (NAS) signaling; - Security of NAS signaling; - Security control of Access Stratum (AS); - Signaling between Core Network (CN) nodes for mobility between 3GPP access networks; - Reachability to idle mode UEs (including control and execution of paging retransmissions); - Registration area management; - Support for intra-system and inter-system mobility; - Access authentication; - Access authorization including checking of roaming rights; - Mobility management control (subscription and policy); - Support for network slicing; - Selection of Session Management Function (SMF).

[0223] Furthermore, the User Plane Function (UPF) hosts the following main functions: - anchor point for intra-RAT / inter-RAT mobility (if applicable); - external PDU (Protocol Data Unit) session point for interconnection with data networks; - packet routing and forwarding; - packet inspection and policy rule enforcement for the user plane part; - traffic usage reporting; - uplink classifier to support routing of traffic flows to the data network; - branching point to support multi-homed PDU sessions; - QoS processing for the user plane (e.g. packet filtering, gating, UL / DL rate enforcement); - uplink traffic validation (mapping of SDF to QoS flows); - downlink packet buffering and triggering of downlink data notifications.

[0224] Finally, the Session Management Function (SMF) hosts the following main functions: session management; allocation and management of IP addresses for UEs; selection and control of UPF; configuration of traffic steering in the User Plane Function (UPF) to route traffic to the appropriate destination; policy enforcement and QoS of the control part; downlink data notification.

[0225] <RRC connection setup and reconfiguration procedure> Figure 13 shows some of the interactions between the UE, gNB, and AMF (5GC entities) when the UE transitions from RRC_IDLE to RRC_CONNECTED in the NAS part (see TS 38.300 v15.6.0).

[0226] RRC is a higher layer signaling (protocol) used to configure the UE and gNB. With this transition, the AMF prepares UE context data (including, for example, PDU session context, security keys, UE radio capabilities, UE security capabilities, etc.) and sends it to the gNB along with an INITIAL CONTEXT SETUP REQUEST. The gNB then activates AS security together with the UE. This is done by the gNB sending a SecurityModeCommand message to the UE, and the UE responding with a SecurityModeComplete message to the gNB. The gNB then sends an RRCReconfiguration message to the UE, and upon receiving an RRCReconfigurationComplete from the UE, the gNB performs reconfiguration to set up Signaling Radio Bearer 2 (SRB2) and Data Radio Bearer (DRB). For signaling-only connections, the steps related to RRCReconfiguration are omitted because SRB2 and DRB are not set up. Finally, the gNB notifies the AMF that the setup procedure is complete with an INITIAL CONTEXT SETUP RESPONSE.

[0227] Accordingly, the present disclosure provides a 5th Generation Core (5GC) entity (e.g., AMF, SMF, etc.) that includes: a control circuit that, upon operation, establishes a Next Generation (NG) connection with a gNodeB; and a transmitter that, upon operation, transmits an initial context setup message to the gNodeB via the NG connection so that a signaling radio bearer between the gNodeB and a user equipment (UE) is set up. Specifically, the gNodeB transmits Radio Resource Control (RRC) signaling, including a resource allocation configuration information element (IE), to the UE via the signaling radio bearer. The UE then transmits in uplink or receives in downlink based on the resource allocation configuration.

[0228] <IMT Usage Scenarios Beyond 2020> Figure 14 shows some use cases for 5G NR. The 3rd Generation Partnership Project New Radio (3GPP NR) is considering three use cases envisioned by IMT-2020 to support a wide variety of services and applications. The first phase of specifications for enhanced mobile broadband (eMBB) has been completed. Current and future work includes standardization for ultra-reliable and low-latency communications (URLLC) and massive machine-type communications (mMTC), in addition to expanding support for eMBB. Figure 14 shows some examples of envisioned usage scenarios for IMT beyond 2020 (see, for example, ITU-R M.2083 Figure 2).

[0229] The URLLC use case has stringent performance requirements for throughput, latency, and availability. It is envisioned as one of the enabling technologies for future applications such as wireless control of industrial production or manufacturing processes, remote medical surgery, automated power transmission and distribution in smart grids, and road safety. URLLC's ultra-high reliability is supported by identifying technologies that meet the requirements set by TR 38.913. Key requirements for NR URLLC in Release 15 include a target user plane latency of 0.5 ms on the uplink (UL) and 0.5 ms on the downlink (DL). The overall URLLC requirement for a single packet transmission is a block error rate (BLER) of 1E-5 for a 32-byte packet size with a user plane latency of 1 ms.

[0230] From a physical layer perspective, reliability can be improved in many possible ways. Current room for reliability improvement includes defining a separate CQI table for URLLC, more compact DCI formats, PDCCH repetition, etc. However, this room can be expanded to achieve ultra-high reliability as NR (with respect to the key requirements of NR URLLC) becomes more stable and developed. Specific use cases for NR URLLC in Release 15 include Augmented Reality / Virtual Reality (AR / VR), e-health, e-safety, and mission-critical applications.

[0231] Additionally, the technology enhancements targeted by NR URLLC aim to improve latency and reliability. Technology enhancements for latency improvement include configurable numerology, non-slot-based scheduling with flexible mapping, grant-free (configured grant) uplink, slot-level repetition in the data channel, and preemption in the downlink. Preemption means that a transmission with already allocated resources is stopped and the already allocated resources are used for another transmission with a later requested lower latency / higher priority. Therefore, a previously allowed transmission is preempted by a later transmission. Preemption is applicable regardless of the specific service type. For example, a transmission of service type A (URLLC) may be preempted by a transmission of service type B (eMBB, etc.). Technology enhancements for reliability improvement include a dedicated CQI / MCS table for a target BLER of 1E-5.

[0232] The use case of mMTC (massive machine type communication) is characterized by a very large number of connected devices that typically transmit relatively small amounts of data that are not sensitive to delays. These devices are required to be low-cost and have very long battery life. From the NR perspective, utilizing very narrow bandwidth portions is one solution that saves power and extends battery life from the UE's perspective.

[0233] As mentioned above, the scope of reliability improvement in NR is expected to be broader. One of the key requirements for all cases, for example, URLLC and mMTC, is high or ultra-high reliability. Several mechanisms can improve reliability from a radio perspective and a network perspective. Generally, there are two to three key areas that can help improve reliability. These areas include compact control channel information, repetition of data channels / control channels, and diversity in the frequency, time, and / or spatial domains. These areas are generally applicable to reliability improvement regardless of the specific communication scenario.

[0234] For NR URLLC, further use cases with more stringent requirements are envisaged, such as factory automation, transportation, and power distribution, with high reliability (up to 10-6 level reliability), high availability, packet sizes up to 256 bytes, time synchronization down to a few μs (depending on the use case, the value can be 1 μs or a few μs depending on the frequency range and low latency in the order of 0.5 ms to 1 ms (e.g., 0.5 ms latency on the targeted user plane)).

[0235] Furthermore, for NR URLLC, there may be several technical enhancements from the physical layer perspective. These technical enhancements include PDCCH (Physical Downlink Control Channel) enhancements for compact DCI, PDCCH repetition, and increased PDCCH monitoring. Also, UCI (Uplink Control Information) enhancements relate to enhanced Hybrid Automatic Repeat Request (HARQ) and CSI feedback enhancements. There may also be PUSCH enhancements related to minislot-level hopping and retransmission / repetition enhancements. The term "minislot" refers to a Transmission Time Interval (TTI) that contains fewer symbols than a slot (a slot comprises 14 symbols).

[0236] <QoS Control> The 5G Quality of Service (QoS) model is based on QoS flows and supports both QoS flows that require a guaranteed flow bit rate (Guaranteed Bit Rate QoS flows (GBR)) and QoS flows that do not require a guaranteed flow bit rate (non-GBR QoS flows). Thus, at the NAS level, a QoS flow is the finest granularity of QoS classification in a PDU session. A QoS flow is identified within a PDU session by a QoS Flow ID (QFI) carried in an encapsulation header over the NG-U interface.

[0237] For each UE, 5GC establishes one or more PDU sessions. For each UE, the NG-RAN establishes at least one Data Radio Bearer (DRB) for each PDU session, e.g., as shown above with reference to Figure 13. Additional DRBs for the QoS flows of that PDU session can be configured later (when this is up to the NG-RAN). The NG-RAN maps packets belonging to different PDU sessions to different DRBs. NAS-level packet filters in the UE and 5GC associate UL and DL packets with QoS flows, while AS-level mapping rules in the UE and NG-RAN associate UL and DL QoS flows with DRBs.

[0238] Figure 15 shows the non-roaming reference architecture for 5G NR (see TS 23.501 v16.1.0, section 4.23). An Application Function (AF) (e.g., an external application server hosting 5G services, as illustrated in Figure 14) interacts with the 3GPP core network to provide services. For example, it may access a Network Exposure Function (NEF) to support applications that affect traffic routing, or interact with a policy framework for policy control (e.g., QoS control) (see Policy Control Function (PCF)). Based on operator deployment, Application Functions considered trusted by the operator can interact directly with the associated Network Functions. Application Functions not permitted by the operator to directly access Network Functions interact with the associated Network Functions using an external exposure framework via the NEF.

[0239] Figure 15 further illustrates 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, e.g., operator-provided services, Internet access, or third-party services). All or part of the core network functions and application services may be deployed and run in a cloud computing environment.

[0240] Therefore, the present disclosure provides an application server (e.g., an AF in a 5G architecture) comprising: a transmitter that, in operation, sends a request including QoS requirements for at least one of a URLLC service, an eMMB service, and an mMTC service to at least one of 5GC functions (e.g., an NEF, an AMF, an SMF, a PCF, an UPF, etc.) to establish a PDU session including a radio bearer between a gNodeB and a UE according to the QoS requirements; and a control circuit that, in operation, performs a service using the established PDU session.

[0241] The present disclosure can be realized by software, hardware, or software in conjunction with hardware. Each functional block used in the description of the above embodiments may be partially or entirely realized as an LSI, which is an integrated circuit, and each process described in the above embodiments may be partially or entirely controlled by a single LSI or a combination of LSIs. The LSI may be composed of individual chips, or may be composed of a single chip that includes some or all of the functional blocks. The LSI may have data input and output. Depending on the degree of integration, the LSI may also be called an IC, system LSI, super LSI, or ultra LSI.

[0242] The integrated circuit method is not limited to LSI, and may be realized by a dedicated circuit, a general-purpose processor, or a dedicated processor. Also, a field programmable gate array (FPGA) that can be programmed after LSI manufacturing, or a reconfigurable processor that can reconfigure the connections and settings of circuit cells within the LSI, may be used. The present disclosure may be realized as digital processing or analog processing.

[0243] Furthermore, if an integrated circuit technology that can replace LSI emerges due to advances in semiconductor technology or other derivative technologies, it is natural that such technology may be used to integrate functional blocks. The application of biotechnology, etc. is also a possibility.

[0244] The present disclosure may be implemented in any type of apparatus, device, or system (collectively referred to as a communications apparatus) that has a communications function. The communications apparatus may include a radio transceiver and processing / control circuitry. The radio transceiver may include a receiver and a transmitter, or both functions. The radio transceiver (transmitter and receiver) may include a radio frequency (RF) module and one or more antennas. The RF module may include an amplifier, an RF modulator / demodulator, or the like. Non-limiting examples of communication devices include telephones (e.g., cell phones, smartphones), tablets, personal computers (PCs) (e.g., laptops, desktops, notebooks), cameras (e.g., digital still / video cameras), digital players (e.g., digital audio / video players), wearable devices (e.g., wearable cameras, smartwatches, tracking devices), game consoles, digital book readers, telehealth / telemedicine devices, communication-enabled vehicles or mobile transportation (e.g., cars, airplanes, ships), and combinations of the above devices.

[0245] The communication devices are not limited to portable or mobile devices, but also include any kind of non-portable or fixed equipment, devices, and systems, such as smart home devices (such as home appliances, lighting equipment, smart meters or measuring devices, control panels, etc.), vending machines, and any other "things" that may exist on an IoT (Internet of Things) network.

[0246] Communications include data communications via cellular systems, wireless LAN systems, communication satellite systems, and the like, as well as data communications via combinations of these.

[0247] A communications apparatus also includes devices such as controllers and sensors connected or coupled to a communications device that performs the communications functions described in this disclosure, such as controllers and sensors that generate control and data signals used by the communications device to perform the communications functions of the communications apparatus.

[0248] The communication apparatus also includes infrastructure facilities, such as base stations, access points, and any other apparatus, device, or system that communicates with or controls the various apparatuses listed above, but are not limited to these.

[0249] A base station according to one embodiment of the present disclosure includes a control circuit that individually sets a first transmission timing of an uplink in a first time resource and a second transmission timing of an uplink in a second time resource different from the first time resource, and a receiving circuit that receives a signal based on the first transmission timing and the second transmission timing.

[0250] In one embodiment of the present disclosure, the control circuit causes an offset value of the transmission timing in the first time resource to differ from an offset value of the transmission timing in the second time resource.

[0251] In one embodiment of the present disclosure, the control circuit sets the offset value of the first time resource to zero.

[0252] In one embodiment of the present disclosure, the first time resource is a symbol to which a scheme in which a transmission direction is set for each of multiple bands obtained by dividing a frequency band is applied, or a symbol to which the scheme may be applied.

[0253] In one embodiment of the present disclosure, the first time resource is a symbol that is dynamically or semi-statically set.

[0254] In one embodiment of the present disclosure, the control circuit sets an offset value common to the transmission timing in each of the first time resource and the second time resource, and an offset value specific to the transmission timing in the first time resource.

[0255] In one embodiment of the present disclosure, the control circuit makes a setting value of the transmission timing in the first time resource different from a setting value of the transmission timing in the second time resource.

[0256] A terminal according to one embodiment of the present disclosure includes a control circuit that individually sets a first transmission timing of an uplink in a first time resource and a second transmission timing of an uplink in a second time resource different from the first time resource, and a transmission circuit that transmits a signal based on the first transmission timing and the second transmission timing.

[0257] In a communication method according to one embodiment of the present disclosure, a base station individually sets a first transmission timing of an uplink in a first time resource and a second transmission timing of an uplink in a second time resource different from the first time resource, and receives a signal based on the first transmission timing and the second transmission timing.

[0258] In a communication method according to one embodiment of the present disclosure, a terminal individually sets a first transmission timing of an uplink in a first time resource and a second transmission timing of an uplink in a second time resource different from the first time resource, and transmits a signal based on the first transmission timing and the second transmission timing.

[0259] The disclosures of the specification, drawings and abstract contained in Japanese Patent Application No. 2022-128841, filed on August 12, 2022, are incorporated herein by reference in their entirety.

[0260] One embodiment of the present disclosure is useful in wireless communication systems.

[0261] 100 Base station 101, 201 Receiving unit 102, 202 Demodulation and decoding unit 103 Scheduling unit 104, 204 Timing control unit 105, 205 Control information holding unit 106, 206 Data and control information generating unit 107, 207 Encoding and modulation unit 108, 208 Transmitting unit 200 Terminal 203 Control unit

Claims

1. A circuit for allocating a transition period between a first time resource having subband non-overlapping full duplex (SBFD) symbols and a second time resource having non-SBFD symbols and following the first time resource; a receiver that receives an uplink signal based on the transition period; Equipped with the transition period is allocated within either the first time resource or the second time resource; Base station.

2. The transition period is allocated within the first time resource having the SBFD symbol. The base station of claim 1 .

3. The uplink signal is received in the second time resource; the transition period is allocated within the second time resource. The base station of claim 1 .

4. The method of claim 3, wherein the first time resource having the SBFD symbol is signaled by higher layer signaling. The base station of claim 1 .

5. The first time resource and the second time resource are each composed of slots. The base station of claim 1 .

6. The base station is allocating a transition period between a first time resource having subband non-overlapping full duplex (SBFD) symbols and a second time resource having non-SBFD symbols following the first time resource; receiving an uplink signal based on the transition period; the transition period is allocated within either the first time resource or the second time resource; Communication method.

7. The transition period is allocated within the first time resource having the SBFD symbol. The communication method according to claim 6.

8. The method of claim 7, wherein the uplink signal is received in the second time resource; the transition period is allocated within the second time resource. The communication method according to claim 6.

9. The method of claim 8, wherein the first time resource having the SBFD symbol is signaled by higher layer signaling. The communication method according to claim 6.

10. The first time resource and the second time resource each consist of a slot. The communication method according to claim 6.

11. A control circuit that controls allocation of a transition period between a first time resource having subband non-overlapping full duplex (SBFD) symbols and a second time resource having non-SBFD symbols and following the first time resource; a receiving circuit that controls reception of an uplink signal based on the transition period; Equipped with the transition period is allocated within either the first time resource or the second time resource; Integrated circuit.