Base station, terminal, and communication method

Abstract

The present invention appropriately controls repetitive transmission in wireless communication. This base station is provided with: a control circuit that determines, on the basis of a group including at least a symbol type, a slot that can be used for repetitive transmission of an uplink signal; and a reception circuit that receives the uplink signal in the determined slot.

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-5).

[0003] 3GPP TS 38.211 V17.5.0, "NR; Physical channels and modulation (Release 17)," June 20233GPP TS 38.212 V17.5.0, "NR; Multiplexing and channel coding (Release 17)," March 20233GPP TS 38.213 V17.6.0, "NR; Physical layer procedure for control (Release 17)," June 20233GPP TS 38.214 V17.6.0, "NR; Physical layer procedures for data (Release 17)," June 20233GPP TS 38.331 V17.5.0, "NR; Radio Resource Control (RRC) protocol specification (Release 17)", June 2023

[0004] However, there is room for further study regarding repeat transmission control 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 perform repeat transmission control in wireless communication.

[0006] A base station according to one embodiment of the present disclosure includes a control circuit that determines slots available for repeated transmission of an uplink signal based on a group including at least a symbol type, and a receiving circuit that receives the uplink signal in the determined slots.

[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, repeat transmission control in wireless communication can be appropriately performed.

[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] Diagram showing an example of a duplex methodDiagram showing an example of Dynamic Subband non-overlapping full duplex (SBFD)Diagram showing an example of available slot countingBlock diagram showing an example configuration of a part of a base stationBlock diagram showing an example configuration of a part of a terminalBlock diagram showing an example configuration of a base stationBlock diagram showing an example configuration of a terminalSequence diagram showing an example operation of a base station and a terminalDiagram showing an example of a method for determining an available slotDiagram showing an example of a method for determining an available slotDiagram showing an example of a method for determining an available slotDiagram showing an example of a method for determining an available slotDiagram showing an example of a method for determining an available slotDiagram showing an example of a method for determining an available slotDiagram showing an example of a method for determining an available slotDiagram showing an example of a method for determining an available slotDiagram showing an example of a method for determining an available slotDiagram showing an example of a method for determining an available slotDiagram showing an example of a method for determining an available slotDiagram of an example architecture of a 3GPP NR systemSchematic diagram showing functional separation between NG-RAN (Next Generation - Radio Access Network) and 5GC (5th Generation Core)Radio Resource A sequence diagram of the RRC connection setup / reconfiguration procedure. A schematic diagram illustrating the use scenarios of enhanced Mobile BroadBand (eMBB), massive Machine Type Communications (mMTC), and Ultra Reliable and Low Latency Communications (URLLC). A block diagram illustrating an example 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] [Subband non-overlapping full duplex (SBFD)] "Study on evolution of NR duplex operation" is being discussed as a study item in 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), a terminal (UE: User Equipment) is a terminal 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] Although not shown in Fig. 1, a guard band may be arranged between the uplink band (UL sub-band: U) and the downlink sub-band (DL sub-band: D). The guard band may be used to reduce cross link interference (CLI) between different transmission directions (links).

[0017] In the following description, a symbol on which SBFD operation or control is performed is called an "SBFD symbol." A symbol on which SBFD operation or control is not performed (for example, a symbol different from an SBFD symbol) may also be called a "non-SBFD symbol." For example, a slot consisting of SBFD symbols may also be called an "SBFD slot," and a slot consisting of non-SBFD symbols may also be called a "non-SBFD slot."

[0018] The subband configuration is expressed as {X...X}, where X represents the UL subband (U) or DL ​​subband (D). The order of notation corresponds to the order in which the subbands are arranged. For example, the subband configuration in Figure 1(b) is expressed as {DUD}.

[0019] [SBFD symbol / operation] The SBFD symbol may be configured using a legacy symbol (or an existing symbol) such as a DL symbol, a UL symbol, or a Flexible symbol. For example, the SBFD symbol may be configured using at least one legacy symbol of a DL symbol and a Flexible symbol. For example, a legacy symbol may be changed and used as the SBFD symbol. The legacy symbol is configured by, for example, RRC signaling (for example, TDD-UL-DL-ConfigCommon). Here, a non-SBFD symbol is, for example, a legacy symbol that is not used as an SBFD symbol.

[0020] Furthermore, as the SBFD control, for example, at least one of semi-static SBFD and dynamic SBFD may be applied. In semi-static SBFD, the transmission direction in a subband is set semi-statically (e.g., the transmission direction is not changed dynamically). In dynamic SBFD, the transmission direction of a subband may be changed dynamically. Figure 2 shows an example of dynamic SBFD. Figure 2(a) shows an example of a semi-statically set subband transmission direction ({DUD}), and Figure 2(b) shows an example of a dynamically changed transmission direction ({DDD}). In the example of Figure 2, the transmission direction of the second subband is changed from uplink (U) to downlink (D).

[0021] [Available slot counting] Release 17 introduces "Available slot counting" for repetitive transmission of the Physical Uplink Shared Channel (PUSCH) (for example, PUSCH repetition type A).

[0022] In the existing PUSCH repetition type A, for example, if the time domain resource for one of four repetition transmissions overlaps with a DL symbol, the one transmission is not performed, and the remaining three transmissions are performed. In this case, the effective coding rate increases, and the effect of the repetition transmission may not be fully achieved. Therefore, for example, if a symbol set for PUSCH repetition transmission overlaps with a DL symbol, PUSCH resources are allocated to a slot (referred to as an "available slot") available for PUSCH repetition transmission after the DL symbol. This makes it possible to transmit the PUSCH up to the set number of repetitions, and prevents a decrease in the coding rate.

[0023] For example, PUSCH transmission using available slot counting is performed by the following two steps.

[0024] <Step 1> Based on the PUSCH resource allocation and slot format configuration, slots available for K repetitions of the PUSCH are determined (where K represents the number of repetitions). If the PUSCH resource allocation overlaps with a DL symbol, the slot containing the DL symbol is determined to be unavailable (unavailable or not available). Note that the time domain resource allocation (e.g., the symbol number used for the PUSCH in each slot) is the same between slots. The slot format may be configured by RRC signaling (e.g., TDD-UL-DL-ConfigCommon or TDD-UL-DL-ConfigDedicated). Furthermore, the symbol in which the SSB configured by RRC signaling (e.g., ssb-PositionsInBurst) is transmitted may be considered a DL symbol.

[0025] <Step 2> The terminal determines whether to drop the PUSCH transmission (e.g., discard the transmission) based on dynamic factors. For example, the PUSCH transmission may be dropped due to another UL transmission with a higher priority than the PUSCH transmission. Note that even if the PUSCH transmission is dropped, the number of PUSCH transmissions does not need to be increased. For example, if one transmission is dropped out of K PUSCH transmissions, the number of PUSCH transmissions becomes K-1.

[0026] Note that transmission using available slots is applicable to repetition transmission of a Physical Uplink Control Channel (PUCCH) or transmission of a Sounding Reference Signal (SRS) in addition to PUSCH repetition type A. Furthermore, transmission using available slots may be applied to repetition of a Configured Grant PUSCH (CG-PUSCH), for example.

[0027] FIG. 3 shows an example of available slot counting.

[0028] In FIG. 3, Slots #0 and #4 are UL slots (slots consisting of UL symbols, represented by "U"), Slots #1 and #2 are DL slots (slots consisting of DL symbols, represented by "D"), and Slot #3 is a Flexible slot (slot consisting of Flexible symbols, represented by "F"). As an example, a case will be described where PUSCH is scheduled with two repetitions (e.g., PUSCH rep #1 and PUSCH rep #2) in Slot #0. In this case, the terminal determines slots available for two repetition transmissions. For example, as shown in FIG. 3, Slots #1 and #2 are DL slots and are therefore determined to be "unavailable." Also, as shown in FIG. 3, Slot #3 is a Flexible slot and is therefore determined to be "available." Therefore, PUSCH transmission is allocated to Slot #0 and Slot #3. In FIG. 3, Slot #4 is also a UL slot and is therefore determined to be available, but since two PUSCH transmissions (the set number of repetitions) have been performed in Slot #3, it is not necessary to determine whether slots after Slot #3 are available.

[0029] In a non-limiting example of the present disclosure, a method for controlling PUSCH repetition (for example, available slot counting) when performing SBFD operation will be described.

[0030] [Overview of Communication System] A communication system according to an embodiment 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 embodiment of the present disclosure. In the base station 100 illustrated in FIG. 4, a control unit (e.g., corresponding to a control circuit) determines slots available for repeated transmission of uplink signals (e.g., repetitive transmission of PUSCH) based on a group including at least a symbol type. A receiving unit (e.g., a receiving circuit) receives the uplink signals in the determined slots.

[0032] 5 is a block diagram illustrating a configuration example of a portion of a terminal 200 according to an embodiment of the present disclosure. In the terminal 200 illustrated in FIG. 5, a control unit (e.g., corresponding to a control circuit) determines slots available for repeated transmission of uplink signals (e.g., repetition transmission of PUSCH) based on a group including at least a symbol type. A transmission unit (e.g., a transmission circuit) transmits the uplink signals in the determined slots.

[0033] [Configuration of Base Station] Fig. 6 is a block diagram showing an example configuration of a base station 100 according to an embodiment of the present disclosure. In Fig. 6, the base station 100 includes a receiving unit 101, a demapping unit 102, a demodulation / decoding unit 103, a scheduling unit 104, an available slot control unit 105, a control information holding unit 106, a data / control information generating unit 107, an encoding / modulation unit 108, a mapping unit 109, and a transmitting unit 110.

[0034] For example, at least one of the demapping unit 102, demodulation / decoding unit 103, scheduling unit 104, available slot control unit 105, control information storage unit 106, data / control information generation unit 107, coding / modulation unit 108, and mapping unit 109 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 reception processing such as down-conversion or A / D conversion on a signal received via an antenna, and outputs the processed received signal to the demapping unit 102 .

[0036] The demapping unit 102 performs resource demapping on the received signal (for example, an uplink signal) input from the receiving unit 101 , and outputs the modulated signal to the demodulation and decoding unit 103 .

[0037] The demodulation and decoding section 103 demodulates and decodes the modulated signal input from the demapping section 102 , for example, and outputs the decoding result to the scheduling section 104 .

[0038] The scheduling unit 104 may perform scheduling for the terminals 200, for example. The scheduling unit 104 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 103, information input from the available slot control unit 105 (e.g., information related to available slots), and control information input from the control information storage unit 106, and instructs the data and control information generation unit 107 to generate at least one of data and control information. Furthermore, the scheduling unit 104 outputs, for example, information related to scheduling (e.g., resource allocation information) to the available slot control unit 105. Furthermore, the scheduling unit 104 outputs control information related to scheduling for the terminals 200 to the control information storage unit 106.

[0039] The available slot control unit 105 determines, for example, available slots for the PUSCH based on information related to scheduling (e.g., resource allocation information) input from the scheduling unit 104 and control information (e.g., slot format information) input from the control information holding unit 106. The available slot control unit 105 outputs information related to the determined available slots to the scheduling unit 104.

[0040] The control information holding unit 106 holds, for example, control information set in each terminal 200. The control information may include, for example, information related to SBFD and information related to the uplink channel (for example, the number of repetitions, etc.). The control information holding unit 106 may output the held information to each component of the base station 100 (for example, the scheduling unit 104 and the available slot control unit 105) as necessary.

[0041] The data and control information generating unit 107 generates at least one of data and control information, for example, in accordance with an instruction from the scheduling unit 104, and outputs a signal including the generated data or control information to the coding and modulation unit 108. The generated data may include, for example, signaling information of an upper layer.

[0042] The coding and modulation section 108 codes and modulates, for example, the signal (for example, data, control information) input from the data and control information generation section 107 , and outputs the modulated signal to the transmission section 110 .

[0043] The mapping section 109 performs resource mapping on the modulated signal input from the coding and modulation section 108 , for example, and outputs the transmission signal to the transmitting section 110 .

[0044] The transmitter 110 performs transmission processing such as D / A conversion, up-conversion, or amplification on the signal input from the mapping unit 109, and transmits the radio signal obtained by the transmission processing from an antenna to the terminal 200.

[0045] [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, demapping section 202, demodulation and decoding section 203, available slot determining section 204, control section 205, control information holding section 206, data and control information generating section 207, coding and modulation section 208, mapping section 209, and transmitting section 210.

[0046] For example, at least one of the demapping unit 202, demodulation / decoding unit 203, available slot determination unit 204, control unit 205, control information storage unit 206, data / control information generation unit 207, coding / modulation unit 208, and mapping unit 209 may be included in the control unit shown in Figure 5, and the transmission unit 210 may be included in the transmission unit shown in Figure 5.

[0047] 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 demapping unit 202 .

[0048] The demapping unit 202 performs resource demapping on the received signal input from the receiving unit 201 , for example, and outputs the modulated signal to the demodulation and decoding unit 203 .

[0049] The demodulation / decoding unit 203 demodulates and decodes the modulated signal input from the demapping unit 202, and outputs the decoding result to the control unit 205. The decoding result may include, for example, at least one of upper layer signaling information and downlink control information.

[0050] The available slot determination unit 204 determines an available slot based on, for example, control information (e.g., slot format information) input from the control information storage unit 206 or control information (e.g., resource allocation information) input from the control unit 205, and outputs information regarding the determined available slot to the control unit 205.

[0051] The control unit 205 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 and decoding unit 203 and the control information input from the control information storage unit 206. For example, if the determination result indicates that data or control information is to be transmitted, the control unit 205 outputs resource allocation information to the available slot determination unit 204. Furthermore, the control unit 205 may determine a slot for transmitting data or control information based on information regarding available slots input from the available slot determination unit 204, and instruct the data and control information generation unit 207 to generate at least one of data and control information. Furthermore, the control unit 205 outputs, for example, control information regarding scheduling for the terminal 200 to the control information storage unit 206.

[0052] The control information holding unit 206 holds, for example, control information input from the control unit 205, and outputs the held information to each component (for example, the available slot determination unit 204 and the control unit 205) as necessary.

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

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

[0055] The mapping section 209 performs resource mapping on the modulated signal input from the coding and modulation section 208 and outputs the transmission signal to the transmission section 210 .

[0056] The transmitter 210 performs transmission processing such as D / A conversion, up-conversion, or amplification on the signal input from the mapping unit 209, and transmits the radio signal obtained by the transmission processing from an antenna to the base station 100.

[0057] [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.

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

[0059] In FIG. 8, the base station 100 determines, for example, a setting (configuration) related to SBFD or an uplink channel (for example, PUSCH or PUCCH) (S101).

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

[0061] The base station 100 performs scheduling and resource allocation for, for example, the terminal 200 (S103). The base station 100 may determine available slots for the terminal 200 (for example, PUSCH transmission) and schedule the PUSCH, for example.

[0062] The base station 100 transmits the PDCCH based on the results of the scheduling and resource allocation (S104).

[0063] The terminal 200 determines (or sets, decides, or identifies) available slots and transmission resources (time and / or frequency resources (e.g., also referred to as time-frequency resources)) for the PUSCH, for example, based on the setting information included in the signaling information transmitted from the base station 100 and the PDCCH transmitted from the base station 100 (S105).

[0064] The terminal 200 transmits the PUSCH based on the determined transmission resource, for example (S106).

[0065] [Method of Determining Available Slots] A method of determining available slots in the base station 100 (e.g., the available slot control unit 105) will be described. Note that the terminal 200 (e.g., the available slot determination unit 204) may determine available slots, for example, assuming the method of determining available slots implemented by the base station 100.

[0066] An example of how to determine available slots will be described below.

[0067] <Method 1> In method 1, the base station 100 determines available slots for PUSCH transmission based on the symbol type.

[0068] For example, the application of repetition transmission is expected to be set (or limited) within some symbol types. For example, since SBFD symbols and non-SBFD symbols may have different radio qualities or antenna configurations, repetition may be applied separately to SBFD symbols and non-SBFD symbols by differently determining available slots depending on the symbol type. This enables, for example, transmission using different MCSs (Modulation and Coding Schemes) for SBFD symbols and non-SBFD symbols or transmission according to different antenna configurations.

[0069] For example, the following symbol types may be used:

[0070] "Type 1": Non-SBFD symbols that are not dynamically converted to SBFD symbols (e.g., non-SBFD symbols to which Dynamic SBFD is not applied). Note that Type 1 DL symbols are not considered to be symbols that can be transmitted on the UL.

[0071] "Type 2": A non-SBFD symbol that can be dynamically converted to an SBFD symbol (e.g., a non-SBFD symbol to which Dynamic SBFD can be applied). Note that Type 2 DL symbols are not considered to be UL transmittable symbols.

[0072] "Type 3": SBFD symbols that are not dynamically transformed into non-SBFD symbols (e.g., SBFD symbols to which Dynamic SBFD does not apply)

[0073] "Type 4": An SBFD symbol that can be dynamically converted to a non-SBFD symbol (for example, an SBFD symbol to which Dynamic SBFD can be applied). Note that if it is known that a Type 4 symbol will become a DL symbol (or the transmission direction of all subbands is DL) when converted to a non-SBFD symbol, it is not considered to be a symbol that can be transmitted in the UL.

[0074] "Type 5": A non-SBFD symbol to which SBFD control can be applied in a transparent manner. For example, Type 5 symbols may include Flexible symbols.

[0075] The symbol types may be explicitly set (defined or specified) or may be implicitly determined from other settings (or parameters, etc.). For example, multiple symbol types may be grouped. How the symbol types are used may vary depending on the method described below.

[0076] For example, the base station 100 may group the above-described multiple symbol types and determine (or judge) available slots for PUSCH transmission based on the groups including each symbol type.

[0077] The method for determining available slots based on the symbol type will be described below.

[0078] <Method 1-1> In method 1-1, the base station 100 determines available slots based on the symbol type without taking into account dynamic conversion between SBFD symbols and non-SBFD symbols.

[0079] For example, we will explain the case where UL transmission is scheduled to a non-SBFD symbol (e.g., including multiple non-SBFD symbols) that is set to semi-static (e.g., when scheduled to a symbol whose symbol type is Type 1 or Type 2).

[0080] In this case, in a slot after the symbol for which UL transmission is scheduled, if the symbol of the symbol number for which UL transmission is scheduled is a non-SBFD symbol that is set semi-statically (for example, if the symbol type is Type 1 or Type 2), and if the symbol is a UL symbol or a Flexible symbol, base station 100 determines the slot containing that symbol to be an available slot.

[0081] In Method 1-1, dynamic conversion between SBFD symbols and non-SBFD symbols is not taken into consideration, and therefore Type 1 and Type 2 symbols are not distinguished when determining available slots.

[0082] Next, we will explain the case where UL transmission is scheduled to an SBFD symbol (e.g., including multiple SBFD symbols) that is set to semi-static (e.g., when scheduling is performed on a symbol whose symbol type is Type 3 or Type 4).

[0083] In this case, if the symbol of the symbol number for which UL transmission is scheduled is an SBFD symbol in a slot after the symbol for which UL transmission is scheduled (for example, if the symbol type is Type 3 or Type 4), base station 100 determines the slot containing that symbol to be an available slot.

[0084] In Method 1-1, dynamic conversion between SBFD symbols and non-SBFD symbols is not taken into consideration, and therefore Type 3 and Type 4 symbols are not distinguished when determining available slots.

[0085] In this way, in Method 1-1, available slots for PUSCH transmission are determined based on a group including Type 1 and Type 2, and a group including Type 3 and Type 4, for example.

[0086] Fig. 9 shows an example of determining available slots according to method 1-1. In the example of Fig. 9, the number of repetitions of PUSCH is set to two (for example, represented as PUSCH rep#1 and PUSCH rep#2).

[0087] In the example of FIG. 9, Slots #0 and #3 are UL slots (e.g., slots consisting of UL symbols), and Slots #1, #2, #4, and #5 are SBFD slots (e.g., slots consisting of SBFD symbols).

[0088] FIG. 9(a) shows an example in which a PUSCH is scheduled in an UL slot (for example, including a non-SBFD symbol (UL symbol)). As shown in FIG. 9(a), PUSCH transmission (PUSCH rep#1) is scheduled in Slot#0 (for example, a slot consisting of Type 1 non-SBFD symbols). In this case, the following Slot#1 and Slot#2 are determined to be unavailable, for example, because they are slots consisting of Type 3 SBFD symbols. On the other hand, Slot#3 is determined to be available, because it is an UL slot (for example, a slot consisting of Type 1 non-SBFD symbols). Therefore, in the example of FIG. 9(a), slots#0 and #3 are determined to be available slots, and the second PUSCH (PUSCH rep#2) is transmitted in Slot#3.

[0089] FIG. 9(b) shows an example in which a PUSCH is scheduled in an SBFD slot (for example, a slot consisting of SBFD symbols). As shown in FIG. 9(b), PUSCH transmission (PUSCH rep#1) is scheduled in Slot#2 (for example, a slot consisting of Type 3 SBFD symbols). In this case, the next Slot#3 is a UL slot (for example, a slot consisting of Type 1 non-SBFD symbols) and is therefore determined to be unavailable. On the other hand, Slot#4 is, for example, a slot consisting of Type 3 SBFD symbols and is therefore determined to be available. Therefore, in the example of FIG. 9(b), Slot#2 and #4 are determined to be available slots, and the second PUSCH (PUSCH rep#2) is transmitted in Slot#4.

[0090] Thus, according to method 1-1, terminal 200 can perform PUSCH transmission that is tailored to the communication quality of each of SBFD symbols and non-SBFD symbols (for example, setting separate MCSs for SBFD symbols and non-SBFD symbols), thereby improving the performance of UL transmission.

[0091] <Method 1-2> In method 1-2, the base station 100 determines available slots based on the symbol type, taking into consideration dynamic conversion between SBFD symbols and non-SBFD symbols.

[0092] For example, when UL transmission is scheduled for a non-SBFD symbol, an SBFD symbol that can be dynamically converted to a non-SBFD symbol may be considered a UL transmittable symbol. However, this is only applicable if there is a possibility that the SBFD symbol will become a UL symbol or a Flexible symbol (or a UL transmittable symbol) when converted to a non-SBFD symbol. For example, if an SBFD symbol is converted only to a DL symbol, the symbol is not considered a UL transmittable symbol. For example, when UL transmission is scheduled for a symbol of the following symbol types, Type 1, Type 2, and Type 4 symbols may be considered as UL transmittable symbols. Note that Type 3 symbols are always SBFD symbols, and are therefore excluded from UL transmittable symbols. - Type 1 symbols - Type 2 symbols and symbols that have not been converted to SBFD symbols - Type 4 symbols and symbols that have been converted to non-SBFD symbols

[0093] For example, in method 1-2, the base station 100 may include these symbol types in one group and determine the available slots for PUSCH transmission based on the group.

[0094] Furthermore, for example, when UL transmission is scheduled for an SBFD symbol, non-SBFD symbols that can be dynamically converted to SBFD symbols may be considered to be UL transmittable symbols. For example, when UL transmission is scheduled for symbols of the following symbol types, Type 2, Type 3, and Type 4 symbols may be considered to be UL transmittable symbols. Note that Type 1 symbols are always non-SBFD symbols, and are therefore excluded from UL transmittable symbols. - Type 3 symbols - Type 2 symbols and symbols converted to SBFD symbols - Type 4 symbols and symbols not converted to non-SBFD symbols

[0095] For example, in method 1-2, the base station 100 may include these symbol types in one group and determine the available slots for PUSCH transmission based on the group.

[0096] Fig. 10 shows an example of determining available slots according to method 1-2. In the example of Fig. 10, the number of repetitions of PUSCH is set to two (for example, represented as PUSCH rep#1 and PUSCH rep#2).

[0097] Figure 10(a) shows an example of a semi-static slot configuration and available slot determination. In the example of Figure 10(a), PUSCH transmission (PUSCH rep #1) is scheduled to Slot #0 (a slot consisting of Type 1 non-SBFD symbols). In this case, the next Slot #1 (a slot consisting of Type 3 SBFD symbols) is determined to be unavailable because it is not converted to a non-SBFD symbol. Also in Figure 10(a), Slot #2 (a slot consisting of Type 4 SBFD symbols) can be converted to a non-SBFD symbol, so it is determined to be available. Therefore, in the example of Figure 10(a), Slots #0, #2, and #3 are determined to be available slots.

[0098] 10(b) shows a case where Slot #2 is actually dynamically converted from the slot configuration of FIG. 10(a) to a UL slot (a slot consisting of non-SBFD symbols). In this case, PUSCH rep #2 can be transmitted in Slot #2.

[0099] 10(c) shows a case where Slot #2 is not actually dynamically converted from the slot configuration of FIG. 10(a) to a UL slot (a slot consisting of non-SBFD symbols) (for example, a case where Slot #2 remains a slot consisting of SBFD symbols). In this case, since the resources allocated to PUSCH rep #2 in Slot #2 are DL subbands, the transmission of PUSCH rep #2 is dropped (for example, PUSCH rep #2 is not transmitted).

[0100] Note that, although FIG. 10 describes a case where UL transmission (for example, PUSCH rep#1) is scheduled in a slot constituting a non-SBFD symbol, a similar operation may be applied to a case where UL transmission (for example, PUSCH rep#1) is scheduled in a slot constituting an SBFD symbol.

[0101] In this way, according to Method 1-2, the terminal 200 determines available slots taking into account the state of symbols after dynamic conversion in Dynamic SBFD, thereby improving (increasing) repetition transmission opportunities.

[0102] <Method 1-3> In Method 1-3, base station 100 determines available slots based on symbol types, taking into account that Flexible symbols are used for SBFD operation in a transparent manner. That is, base station 100 determines available slots for PUSCH transmission, taking into account the transparent use of Flexible symbols in SBFD operation.

[0103] Flexible symbols can be used for both UL transmission and DL reception, for example, through dynamic control (e.g., scheduling of transmission and reception by PDCCH). Therefore, SBFD operation can be realized in a transparent manner using flexible symbols. For example, by using flexible symbols, DL reception and UL transmission can be realized with the same symbols without explicitly configuring subbands.

[0104] Furthermore, for example, it is assumed that terminals 200 that support SBFD operation (hereinafter referred to as "SBFD-compatible terminals") and terminals 200 that do not support SBFD operation (hereinafter referred to as "SBFD-incompatible terminals") will be connected together to the same base station 100. For this reason, SBFD operation using a transparent method using Flexible symbols is effective for SBFD-incompatible terminals.

[0105] For example, even a terminal that does not support SBFD can transmit and receive by separately allocating DL reception and UL transmission for each subband, just like an SBFD-compatible terminal. On the other hand, if an SBFD-compatible terminal can identify (or grasp) the possibility of transparent SBFD operation (for example, when the Type 5 symbol type is set in an SBFD-compatible terminal), performance may be improved by treating Flexible symbols in the same way as SBFD symbols. In other words, when SBFD operation is performed with Flexible symbols, interference between DL and UL may occur, so assuming communication quality similar to that of SBFD allows for more efficient configuration of MCS, etc.

[0106] An SBFD-compatible terminal is also referred to as, for example, a terminal that supports SBFD control and functions, or an SBFD-aware UE. An SBFD-incompatible terminal is also referred to as, for example, a terminal that does not support SBFD control and functions, or a non-SBFD-aware UE.

[0107] For example, if UL transmission is scheduled on a Type 1 or Type 2 symbol (e.g., a non-SBFD symbol), the Type 1 and Type 2 symbols may be considered as UL transmittable symbols.

[0108] Also, for example, if UL transmission is scheduled for a Type 3, Type 4, or Type 5 symbol, the Type 3, Type 4, and Type 5 symbols may be considered as UL transmittable symbols.

[0109] Thus, in methods 1-3, for example, base station 100 may determine available slots for PUSCH transmission based on a group including symbol types of Type 1 and Type 2, and a group including symbol types of Type 3, Type 4, and Type 5.

[0110] Fig. 11 shows an example of determining available slots according to methods 1 to 3. In the example of Fig. 11, the number of repetitions of PUSCH is set to two (for example, represented as PUSCH rep#1 and PUSCH rep#2).

[0111] 11, Slots #4 and #5 are slots consisting of Flexible symbols. Slot #4 is a slot consisting of symbols that may not perform SBFD operations (e.g., Type 1 symbols), and Slot #5 is a slot consisting of symbols that may perform SBFD operations transparently (e.g., Type 5 symbols).

[0112] In the example of FIG. 11, PUSCH transmission (PUSCH rep #1) is scheduled in Slot #2 (a slot consisting of Type 3 SBFD symbols). In this case, the next Slot #3 (a slot consisting of Type 1 symbols) is determined to be unavailable because it is not converted to an SBFD symbol. Furthermore, Slot #4 (a slot consisting of Type 1 Flexible symbols) is determined to be unavailable because it is not used for SBFD operation (or because even if it is used for SBFD operation, it is transparent to SBFD-compatible terminals). On the other hand, Slot #5 (a slot consisting of Type 5 Flexible symbols) can be used for SBFD operation, so it is determined to be available.

[0113] Therefore, in the example of FIG. 11, Slots #2 and #5 are determined to be available slots, and the second PUSCH (PUSCH rep #2) is transmitted in Slot #5.

[0114] Thus, according to Methods 1-3, by using Flexible symbols to perform SBFD operation transparently for SBFD-non-compatible terminals while setting the possibility of SBFD operation for SBFD-compatible terminals, it becomes possible to efficiently accommodate SBFD-non-compatible terminals and SBFD-compatible terminals in the same base station. This increases transmission and reception opportunities for SBFD-non-compatible terminals, and improves UL transmission performance for SBFD-compatible terminals by taking into account interference due to SBFD, etc.

[0115] The method for determining available slots according to Method 1 has been described above.

[0116] <Additional Rules> The following additional rules may be applied to Method 1.

[0117] <Rule 1-1> Set a specific SBFD symbol / slot to always be determined as unavailable.

[0118] By always determining a specific SBFD symbol / slot as unavailable, it is possible to stop UL transmission in the specific SBFD symbol / slot (e.g., repetition transmission using an available slot). Stopping UL transmission in the SBFD symbol / slot can be used, for example, to protect transmission and reception of SBFD-incompatible terminals.

[0119] For example, when DL reception is performed in an SBFD symbol, interference may occur from the UL subband of that SBFD symbol. Therefore, by stopping UL transmission in a specific SBFD symbol, the DL reception quality of a terminal that does not support SBFD can be improved.

[0120] Rule 1-1 reduces interference between DL and UL in a specific SBFD symbol, improving the quality of transmission and reception.

[0121] Note that whether or not the setting of rule 1-1 is applied may differ for each terminal.

[0122] <Rule 1-2> Set to determine that part or all of the slots including the SBFD symbol in which the SSB (Synchronization Signal Block) is placed are unavailable.

[0123] For example, if an SSB is assigned to an SBFD symbol and UL transmission is scheduled for the same symbol, terminal 200 cannot receive the SSB due to half-duplex communication. If terminal 200 cannot receive the SSB, synchronization processing of terminal 200 may be affected.

[0124] Therefore, in rule 1-2, some or all of the slots including the SBFD symbol in which the SSB is allocated are determined to be unavailable, thereby enabling SSB reception in terminal 200.

[0125] The timing for determining that a signal is unavailable (or the timing for receiving an SSB) may be set differently among terminals 200 .

[0126] Figure 12 shows an example of SSB reception when rule 1-2 is applied. In the example of Figure 12, an SSB is transmitted from base station 100 (e.g., gNB) every 20 ms, and terminal 200 (e.g., UE#1 or hUE#2) receives the SSB every 160 ms. Note that the SSB transmission period and the period at which terminal 200 receives the SSB are not limited to the example of Figure 12.

[0127] In Fig. 12, UE#1 is configured to receive an SSB at the first timing in a 160 ms period, so that the slot in which the first SSB is transmitted is determined to be unavailable. Similarly, in Fig. 12, UE#2 is configured to receive an SSB at the second timing in a 160 ms period, so that the slot in which the second SSB is transmitted is determined to be unavailable.

[0128] 12, by determining that a portion of a slot including an SBFD symbol in which an SSB is allocated is unavailable, terminal 200 becomes able to receive the SSB. Furthermore, by determining that a portion of a slot including an SBFD symbol in which an SSB is allocated is unavailable, UL transmission opportunities in the slot are secured, the advantages of SBFD are prevented from being lost, and opportunities for SSB reception and UL transmission can be adjusted.

[0129] <Method 2> In method 2, the base station 100 determines available slots for PUSCH transmission based on the symbol type and frequency domain resources allocated to UL transmission (repetition transmission).

[0130] In Method 2, available slots are determined by taking into consideration the location of frequency domain resources to which UL transmissions are allocated, in addition to taking into consideration the same symbol types as in Method 1. For example, the available slots may be determined by determining whether or not the resources to which UL transmissions are allocated are within UL resources (e.g., UL subbands) in the SBFD symbol.

[0131] Furthermore, in Method 2, repetition transmission may be applied across both SBFD symbols and non-SBFD symbols regardless of the symbol type. For example, the first PUSCH transmission may be performed in an SBFD symbol, and the second PUSCH transmission may be performed in a non-SBFD symbol.

[0132] Furthermore, for example, when frequency hopping is configured, the location where frequency hopping is applied may be taken into consideration as the frequency domain resource. For example, the base station 100 may determine whether the resource for UL transmission is within the UL resource in the SBFD symbol based on the resource after frequency hopping is applied.

[0133] Furthermore, for example, when an SBFD symbol includes multiple UL subbands, the repetition transmission may be performed in a UL subband different from the UL subband in which the UL transmission is initially scheduled. Furthermore, when different frequency hopping is configured or defined for the SBFD symbol and the non-SBFD symbol, different frequency hopping may be applied to each symbol in which the repetition transmission is performed.

[0134] A method for determining available slots based on the symbol type and frequency domain resources for UL transmission will be described below.

[0135] <Method 2-1> In method 2-1, the base station 100 determines available slots based on the symbol type and UL transmission frequency domain resources, without considering dynamic conversion between SBFD symbols and non-SBFD symbols.

[0136] For example, based on the slot and symbol configuration that are set semi-statically, if the frequency domain resources for UL transmission are arranged within the frequency domain of the UL subband (for example, if the frequency domain resources for UL transmission do not collide with DL resources), base station 100 determines that the slot is an available slot.

[0137] For example, when UL transmission is scheduled, the base station 100 may determine, as an available slot, a slot that satisfies both of the following conditions after the slot in which UL transmission is scheduled.

[0138] Condition 1: If the symbol of the symbol number for which UL transmission is scheduled is a non-SBFD symbol configured semi-statically (for example, if the symbol type is Type 1 or Type 2), and if it is a UL symbol or a Flexible symbol

[0139] Condition 2: When the symbol of the symbol number for which UL transmission is scheduled is an SBFD symbol configured to be semi-static (for example, when the symbol type is Type 3 or Type 4), and when the frequency domain resource for UL transmission is included in the UL resource for the SBFD symbol

[0140] Figure 13 shows an example of determining available slots according to method 2-1. In the example of Figure 13, the number of repetitions of PUSCH is set to two (for example, represented as PUSCH rep #1 and PUSCH rep #2). Note that in the example of Figure 13, frequency hopping is not applied.

[0141] Figure 13(a) shows an example in which frequency domain resources for which UL transmission is scheduled are included in UL resources (UL subbands) in SBFD symbols. In Figure 13(a), PUSCH transmission (PUSCH rep #1) is scheduled in Slot #0 (a slot consisting of non-SBFD symbols), and the frequency domain resources to which PUSCH rep #1 is allocated are located within the UL subbands in the SBFD symbols (for example, Slots #1, #2, #4, and #5). In this case, as shown in Figure 13(a), both the UL slots (Slots #0, #3) and the SBFD slots (Slots #1, #2, #4, and #5) are determined to be available. Therefore, in the example of Figure 13(a), slots #0 to #5 are determined to be available slots, and the second PUSCH (PUSCH rep #2) is transmitted in Slot #1.

[0142] Figure 13(b) shows an example in which the frequency domain resources for which UL transmission is scheduled are not included in the UL resources (UL subbands) in the SBFD symbol (for example, are included in the DL resources). In Figure 13(b), PUSCH transmission (PUSCH rep #1) is scheduled in Slot #0 (a slot consisting of non-SBFD symbols), and the frequency domain resources to which PUSCH rep #1 is allocated are located in resources (DL subbands) different from the UL subbands in the SBFD symbol (for example, symbols Slot #1, #2, #4, and #5). In this case, as shown in Figure 13(b), the UL slots (Slot #0, #3) are determined to be available, and the SBFD slots (Slot #1, #2, #4, and #5) are determined to be unavailable. Therefore, in the example of Figure 13(b), slots #0 and #3 are determined to be available slots, and the second PUSCH (PUSCH rep #2) is transmitted in Slot #3.

[0143] In this way, according to method 2-1, terminal 200 can reduce UL delay by performing repetitive transmission across SBFD symbols and non-SBFD symbols.

[0144] <Method 2-2> In method 2-2, the base station 100 determines available slots based on the symbol type and frequency domain resources for UL transmission, taking into account dynamic conversion between SBFD symbols and non-SBFD symbols.

[0145] For example, if a non-SBFD symbol can be dynamically converted to an SBFD symbol, the non-SBFD symbol may be considered as a UL transmittable symbol even if an UL transmission is scheduled on the SBFD symbol, provided that the frequency domain resource of the UL transmission falls within the UL resource of the SBFD symbol.

[0146] Furthermore, for example, if there is a possibility that an SBFD symbol may be dynamically converted to a non-SBFD symbol, the SBFD symbol may be considered as a UL transmittable symbol even if UL transmission is scheduled for the non-SBFD symbol. However, this is only in the case where there is a possibility that the SBFD symbol may become a UL symbol or a Flexible symbol (or a UL transmittable symbol) when converted to a non-SBFD symbol. For example, if an SBFD symbol is converted only to a DL symbol, the symbol is not considered as a UL transmittable symbol.

[0147] Figure 14 shows an example of determining available slots according to method 2-2. In the example of Figure 14, the number of repetitions of PUSCH is set to two (for example, represented as PUSCH rep #1 and PUSCH rep #2). Note that in the example of Figure 14, frequency hopping is not applied.

[0148] Figure 14(a) shows an example in which there is no dynamic conversion from non-SBFD symbols to SBFD symbols. In the example of Figure 14(a), PUSCH transmission (PUSCH rep#1) is scheduled to Slot#0 (e.g., a slot consisting of non-SBFD symbols), and the frequency domain resources to which PUSCH rep#1 is allocated are located within the UL subband of the SBFD symbols (e.g., symbols of Slot#2, #4, and #5). In Figure 14(a), the next symbol of Slot#1 is a DL symbol (non-SBFD symbol) and a symbol that cannot be converted to an SBFD symbol (e.g., a Type 1 symbol), and is therefore determined to be unavailable. In Figure 14(a), the symbol of Slot#2 (SBFD symbol) is determined to be available because the frequency domain resources to which UL transmission is allocated fall within the UL resources of the SBFD symbol. Therefore, in the example of FIG. 14(a), slots #0 and #2 (and slots #3 to #5) are determined to be available slots, and the second PUSCH (PUSCH rep#2) is transmitted in Slot #2.

[0149] Figure 14(b) shows an example in which there is dynamic conversion from non-SBFD symbols to SBFD symbols. In the example of Figure 14(b), PUSCH transmission (PUSCH rep#1) is scheduled to Slot#0 (e.g., a slot consisting of non-SBFD symbols), and the frequency domain resources to which PUSCH rep#1 is allocated are located within the UL subband of the SBFD symbols (e.g., Slot#2, #4, and #5 symbols). In Figure 14(b), the next Slot#1 is a symbol (e.g., a Type 2 symbol) that may be converted to an SBFD symbol, and the frequency domain resources allocated to the UL transmission fall within the UL resources of the SBFD symbols (e.g., Slot#2, #4, and #5 symbols). Therefore, Slot#1 is determined to be available. Therefore, in the example of FIG. 14(b), slots #0 and #1 (and slots #2 to #5) are determined to be available slots, and the second PUSCH (PUSCH rep#2) is transmitted in Slot #1.

[0150] In FIG. 14(b), if Slot#1 is not converted to an SBFD symbol before transmitting PUSCH rep#2, the transmission of PUSCH rep#2 is dropped.

[0151] In this way, according to method 2-2, terminal 200 can determine available slots taking into account the state of symbols after dynamic conversion in Dynamic SBFD, thereby improving UL transmission opportunities.

[0152] <Method 2-3> In method 2-3, base station 100 determines available slots based on the symbol type and the frequency domain resources of UL transmission, taking into account mapping in which one UL transmission (e.g., a transmission opportunity) in repetition transmission spans SBFD symbols and non-SBFD symbols.

[0153] When determining the available slot, even if the time domain resource for UL transmission spans an SBFD symbol and a non-SBFD symbol, if the UL transmission resource is located within the frequency domain of the UL subband of the SBFD symbol (for example, if the UL transmission resource does not collide with the DL resource), the base station 100 determines the slot containing these symbols as the available slot.

[0154] In addition, whether or not one UL transmission (e.g., one transmission opportunity) can be mapped across SBFD symbols and non-SBFD symbols may be set by the capability of terminal 200, or may be set from base station 100 to terminal 200 by RRC signaling, etc.

[0155] Figure 15 shows an example of determining available slots according to method 2-3. In the example of Figure 15, the number of repetitions of PUSCH is set to two (for example, represented as PUSCH rep #1 and PUSCH rep #2). Note that in the example of Figure 15, frequency hopping is not applied.

[0156] Figure 15(a) shows a case where one UL transmission is not mapped across SBFD symbols and non-SBFD symbols. In Figure 15(a), PUSCH transmission (PUSCH rep#1) is scheduled in Slot#1. In Figure 15(a), Slot#2 consists of SBFD symbols (8 symbols) and non-SBFD symbols (Flexible symbols: 2 symbols, UL symbols: 4 symbols). Because the time domain resources of the PUSCH (e.g., 14 symbols) span both SBFD symbols and non-SBFD symbols, slot#2 is determined to be unavailable, and PUSCH rep#2 is not allocated to slot#2.

[0157] Figure 15(b) shows a case where one UL transmission is mapped across SBFD symbols and non-SBFD symbols. In Figure 15(b), PUSCH transmission (PUSCH rep#1) is scheduled in Slot#1. Furthermore, the frequency domain resources to which PUSCH rep#1 is allocated are located within the UL subband in the SBFD symbols (for example, symbols in Slots#2, #4, and #5). In this case, in Slot #2 shown in Figure 15(b), PUSCH can be mapped across SBFD symbols and non-SBFD symbols, and there is no collision between the UL transmission resources and the DL resources, so slot #2 is determined to be available, and PUSCH rep#2 is allocated to slot #2.

[0158] Thus, according to Method 2-3, the available slots are determined taking into consideration that one UL transmission is mapped across SBFD symbols and non-SBFD symbols, thereby improving UL transmission opportunities.

[0159] The method for determining available slots according to Method 2 has been described above.

[0160] <Additional Rules> The following additional rules may be applied to Method 2.

[0161] <Rule 2-1> When a frequency domain resource allocated to UL transmission collides with a specific frequency domain resource in the SBFD symbol, it is set to always be determined as unavailable.

[0162] By always determining that a specific frequency domain resource of an SBFD symbol is unavailable, UL transmission using that specific frequency domain (e.g., repetition transmission using an available slot) is blocked. Blocking UL transmission using a specific frequency domain can be used, for example, to protect transmission and reception of terminals that do not support SBFD (such as existing terminals). For example, when performing DL reception in an SBFD symbol, interference from the UL subband may occur. Therefore, by not using a specific frequency domain resource for UL transmission, the quality of DL reception for terminals that do not support SBFD can be improved.

[0163] Rule 2-1 reduces interference between DL and UL in specific frequency domain resources and improves the quality of transmission and reception.

[0164] Note that whether or not the setting of Rule 2-1 is applied may differ for each terminal. In addition to the frequency domain resource setting, time domain resources may also be set (for example, UL transmission may be limited to a specific slot or symbol).

[0165] <Rule 2-2> In Flexible symbols, if the frequency domain resource for UL transmission fits within a specific frequency domain resource, it is determined to be available.

[0166] Here, the specific frequency domain resource may be, for example, the same resource as the frequency domain of the UL subband. As described in Methods 1-3, Flexible symbols can be used for SBFD operation in a transparent manner. Therefore, when applying transparent SBFD operation to Flexible symbols, the frequency domain resource available for UL transmission is set (or restricted) like the SBFD symbol.

[0167] This makes it possible to prevent UL transmission resources from colliding with the frequency domain that serves as DL resources when performing SBFD operation, for example.

[0168] Whether or not to apply the setting of Rule 2-2 may be configured in terminal 200 by RRC signaling, etc. Furthermore, Rule 2-2 may be configured to be applied to a specific time domain resource (for example, a slot or a symbol).

[0169] 16 shows an example in which Rule 2-2 is applied in addition to Method 2-1. In FIG. 16, the number of repetitions is set to three.

[0170] Figure 16(a) shows a case where a Flexible symbol is determined to be unavailable as a result of applying rule 2-2. In Figure 16(a), Slot #2 is a Flexible slot, and is set to allow UL transmission in the frequency domain corresponding to the UL subband in the SBFD symbol. In the example of Figure 16(a), PUSCH transmission (PUSCH rep #1) is scheduled in Slot #1 (UL slot), and the frequency domain resources of PUSCH rep #1 are located outside the UL subband in the SBFD symbol (for example, within the DL subband). In this case, although slot #2 is a Flexible slot, the frequency domain resources of PUSCH are located outside the UL subband, so it is determined to be available. Therefore, in Figure 16(a), PUSCH rep #2 and PUSCH rep #3 are assigned to Slot #3 and Slot #5 (both UL slots) which are determined to be available.

[0171] FIG. 16(b) shows a case in which a Flexible symbol is determined to be available as a result of applying Rule 2-2. In the example of FIG. 16(b), PUSCH transmission (PUSCH rep #1) is scheduled to Slot #0 (UL slot), and the frequency domain resources of PUSCH rep #1 fall within the UL subband of the SBFD symbol. In FIG. 16(b), Slot #1 is composed of SBFD symbols, and the frequency domain resources of the PUSCH fall within the UL resources (UL subband) of the SBFD symbol, so Slot #1 is determined to be available. Therefore, PUSCH rep #2 is allocated to Slot #1. Also in FIG. 16(b), Slot #2 is a Flexible slot, and is set to allow UL transmission in the frequency domain corresponding to the UL subband of the SBFD symbol. In FIG. 16(b), the frequency domain resources of the PUSCH are located within the UL subband, so Slot #2 is determined to be available. Therefore, PUSCH rep#3 is assigned to Slot#2.

[0172] Rule 2-2 uses Flexible symbols to perform SBFD operation transparently for non-SBFD-compatible terminals and to set the possibility of SBFD operation for SBFD-compatible terminals, thereby efficiently accommodating a mixture of SBFD-compatible and non-SBFD-compatible terminals.

[0173] <Rule 2-3> The method for determining whether UL transmission is available varies depending on whether it is scheduled in an SBFD symbol or a non-SBFD symbol.

[0174] For example, SBFD symbols tend to have lower communication quality than non-SBFD symbols due to possible link interference. Therefore, the MCS set for SBFD symbols may be lower than the MCS set for non-SBFD symbols. For example, it is preferable to use a lower coding rate for SBFD symbols.

[0175] For this reason, for example, when PUSCH is scheduled in non-SBFD symbols and transmitted repeatedly in SBFD symbols, the coding rate of the SBFD symbols may not be sufficient. For example, even if the resource size is the same for SBFD symbols and non-SBFD symbols, a lower coding rate may be required for SBFD symbols to compensate for degradation due to interference.

[0176] Therefore, when UL transmission is scheduled in an SBFD symbol, available slots may be determined according to the method described above. On the other hand, when UL transmission is scheduled in a non-SBFD symbol, the SBFD symbol may be determined to be non-available.

[0177] 17 shows an example in which rule 2-3 is applied in addition to method 2-1. In FIG. 17, the number of repetitions is set to two.

[0178] Figure 17 (a) shows an example in which PUSCH is scheduled to an SBFD symbol. In Figure 17 (a), PUSCH transmission (PUSCH rep #1) is scheduled to Slot #2 (a slot consisting of SBFD symbols). In this case, as in method 2-1, Slot #3 (UL slot) is determined to be available, and PUSCH rep #2 is assigned to Slot #3.

[0179] Figure 17(b) shows an example in which PUSCH is scheduled to a non-SBFD symbol. In Figure 17(b), PUSCH transmission (PUSCH rep #1) is scheduled to Slot #0 (a slot consisting of non-SBFD symbols), and the frequency domain resources of PUSCH rep #1 are located within the UL subband of the SBFD symbol. In this case, if rule 2-3 is not applied, slot #1 and slot #2 (slots consisting of SBFD symbols) are determined to be available, but by applying rule 2-3, slot #1 and slot #2 are determined to be unavailable. As a result, PUSCH rep #2 is assigned to slot #3 (UL slot).

[0180] Rule 2-3 determines available slots by taking into account the difference in communication quality between SBFD symbols and non-SBFD symbols, thereby improving the performance of repetition transmission (for example, reducing reception failures).

[0181] An example of a method for determining available slots has been described above.

[0182] As described above, in the present embodiment, base station 100 and terminal 200 determine available slots for PUSCH transmission (e.g., repetition transmission) based on a group including at least a symbol type, and transmit or receive the PUSCH in the determined available slot. As a result, even when, for example, SBFD symbols and non-SBFD symbols are mixed, available slot counting can be appropriately controlled, and base station 100 and terminal 200 can appropriately control PUSCH repetition transmission when performing SBFD operation. Therefore, according to the present embodiment, repetition transmission in wireless communication can be appropriately controlled.

[0183] (Other Embodiments) Note that even when Dynamic SBFD is not used, the above-described methods for determining available slots may be applied (for example, excluding Method 1-2 and Method 2-2). In this case, for example, Type 1 and Type 3 may be used instead of Type 2 and Type 4 to determine the above-described available slots.

[0184] In addition, in the above-described method for determining available slots, the instruction for the first UL transmission is described as "scheduling," but this is not limited to dynamic scheduling by PDCCH, and may include a case where UL transmission is set semi-statically by RRC signaling, etc. For example, the instruction for UL transmission may include a case where transmission of Configured Grant (CG)-PUSCH, PUCCH, SRS, etc. is set periodically.

[0185] Furthermore, in the above-described embodiments, the determination of available slots may be performed on a symbol-by-symbol basis. For example, the determination of available slots may be performed depending on whether all symbols satisfy a condition. Although the examples and explanations of the above-described methods (e.g., FIG. 9 and the explanation therefor) are described on a slot-by-slot basis for simplicity, in practice, determination on a symbol-by-symbol basis may also be applied. In one embodiment of the present disclosure, unless otherwise specified, determination on a symbol-by-symbol basis is assumed.

[0186] Figure 18 shows an example of determining available slots on a symbol-by-symbol basis. In the example shown in Figure 18, available slots are determined by method 1-1. In Figure 18, Slot #2 is composed of SBFD symbols (8 symbols) and non-SBFD symbols (Flexible symbols: 2 symbols, UL symbols: 4 symbols).

[0187] Figure 18 (a) shows an example in which available is determined on a symbol-by-symbol basis. In the example of Figure 18 (a), in Slot #2, the time domain resource of PUSCH rep #2 is scheduled with 8 symbols. In this case, as shown in Figure 18 (a), in Slot #2, the time domain resource of PUSCH falls within the SBFD symbol, so Slot #2 is determined to be available.

[0188] Figure 18 (b) shows an example in which a symbol is determined to be unavailable. In the example of Figure 18 (b), in Slot #1, the time domain resource of PUSCH rep #1 is scheduled with 14 symbols. In this case, as shown in Figure 18 (b), in Slot #2, the time domain resource of PUSCH does not fit within the SBFD symbol, so Slot #2 is determined to be unavailable.

[0189] Furthermore, in the above embodiment, a slot consisting of multiple symbols has been described as an example, but the unit of time domain resources is not limited to symbols and slots, and may be other time domain resources or other combinations of time domain resources.

[0190] Furthermore, in the above-described embodiment, in Dynamic SBFD, when symbols are converted (e.g., converted from SBFD symbols to non-SBFD symbols, or converted from non-SBFD symbols to SBFD symbols) by dynamic signaling (e.g., notification by PDCCH), UL transmission may be dropped. In this case, as an alternative, UL transmission is not performed in the next available slot, thereby simplifying the determination of available slots or scheduling by base station 100. For example, by not changing the count of available slots by dynamic signaling, it is possible to avoid making the determination of available slots complicated.

[0191] 19 shows an example of dropping UL transmissions by dynamic signaling. In the example shown in FIG. 19, available slots are determined by method 1-1.

[0192] 19(a) shows a semi-statically configured slot configuration. PUSCH rep #1 is scheduled in Slot #2. At this time, Slot #4 (a slot consisting of SBFD symbols) is determined to be available, and PUSCH rep #2 is assigned to Slot #4.

[0193] Figure 19(b) shows the result of changing the slot configuration of Figure 19(a) based on dynamic signaling. As shown in Figure 19(b), Slot #4 is changed from an SBFD slot to a non-SBFD slot (DL slot). In this case, the PUSCH resource collides with the DL symbol, so the transmission of PUSCH rep #2 is dropped.

[0194] Alternatively, after a UL transmission is dropped due to dynamic signaling, the next available slot may be used as an alternative for UL transmission. For example, once a UL transmission is dropped, available slots may be determined again until the repetition count is reached. In this case, the increase in coding rate due to dropping can be suppressed, improving UL performance.

[0195] Furthermore, in the above embodiment, a case where SBFD is applied is described, but an embodiment of the present disclosure may be applied in addition to SBFD as long as the transmission direction (e.g., DL or UL) is set in multiple bands (e.g., subbands) obtained by dividing the frequency band.

[0196] In the above-described embodiments, values ​​such as the number of subbands, the number of DL subbands, the number of UL subbands, the number of slots, the number of symbols, and the number of repetitions are merely examples and are not limited thereto. Also, the subband configurations used in the above-described embodiments are merely examples, and the number of subbands and the arrangement order of DL subbands and UL subbands are not limited thereto.

[0197] Furthermore, although the above-described embodiment has described the determination of available slots for PUSCH transmission, the determination of available slots may be applied not only to PUSCH but also to other uplink channels or signals, or channels or signals of different transmission directions such as downlink or sidelink.

[0198] (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.

[0199] 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.

[0200] 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 control according to the determination result based on the capability information. For example, the base station 100 may control resource allocation for the terminal 200 based on the capability information received from the terminal 200.

[0201] 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.

[0202] 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.

[0203] (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.

[0204] 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.

[0205] (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.

[0206] (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.

[0207] 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.

[0208] (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.

[0209] (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).

[0210] (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, a subslot, a minislot, a symbol, an Orthogonal Frequency Division Multiplexing (OFDM) symbol, a Single Carrier-Frequency Division Multiplexing Access (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.

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

[0212] (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.

[0213] 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.

[0214] (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.

[0215] 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).

[0216] 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 20 (see, for example, 3GPP TS 38.300 v15.6.0, section 4).

[0217] 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.

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

[0219] 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.

[0220] 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 that are approximately three times higher than those offered by IMT-Advanced. On the other hand, for URLLC, stricter requirements are placed on ultra-low latency (0.5 ms for user plane latency in both UL and DL) and high reliability (1-10 ms within 1 ms). －５Finally, mMTC preferably requires high connection density (1,000,000 devices / km in urban environments). ２ ), wide coverage in adverse environments, and extremely long battery life (15 years) for a low-cost device may be desired.

[0221] 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.

[0222] 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).

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

[0224] 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.

[0225] 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).

[0226] 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.

[0227] 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.

[0228] <RRC connection setup and reconfiguration procedure> Figure 22 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).

[0229] 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.

[0230] 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.

[0231] <IMT Usage Scenarios Beyond 2020> Figure 23 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 23 shows some examples of envisioned usage scenarios for IMT beyond 2020 (see, for example, ITU-R M.2083 Figure 2).

[0232] 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.

[0233] 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.

[0234] 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.

[0235] 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.

[0236] 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.

[0237] For NR URLLC, further use cases with more stringent requirements are envisioned, such as factory automation, transportation, and power distribution. －６ level reliability), high availability, packet size 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., targeted user plane latency of 0.5 ms)).

[0238] 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).

[0239] <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.

[0240] 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 22. 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.

[0241] Figure 24 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 23) 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 associated Network Functions. Application Functions not permitted by the operator to directly access Network Functions interact with associated Network Functions using an external exposure framework via the NEF.

[0242] Figure 24 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.

[0243] 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.

[0244] 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.

[0245] 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.

[0246] 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.

[0247] 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.

[0248] 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.

[0249] 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.

[0250] 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.

[0251] 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.

[0252] A base station according to one embodiment of the present disclosure includes a control circuit that determines slots available for repeated transmission of an uplink signal based on a group including at least a symbol type, and a receiving circuit that receives the uplink signal in the determined slots.

[0253] In one embodiment of the present disclosure, the control circuit determines slots available for the repeated transmission based on the symbol type.

[0254] In one embodiment of the present disclosure, the control circuit determines the slots available for the repeated transmission without taking into account dynamic conversion between a first symbol in which a frequency band is divided into multiple bands and a second symbol different from the first symbol.

[0255] In one embodiment of the present disclosure, the control circuit determines the slots available for the repeated transmission by taking into account dynamic conversion between a first symbol in which a frequency band is divided into multiple bands and a second symbol different from the first symbol.

[0256] In one embodiment of the present disclosure, the control circuit determines the slots available for the repeated transmission, taking into account the use of flexible symbols in a scheme in which transmission directions are set in multiple bands divided from a frequency band.

[0257] In one embodiment of the present disclosure, the control circuit determines slots available for the repeated transmission based on the symbol type and frequency resources allocated to the repeated transmission.

[0258] In one embodiment of the present disclosure, the control circuit determines the slots available for the repeated transmission without taking into account dynamic conversion between a first symbol in which the frequency domain is divided into multiple bands and a second symbol different from the first symbol.

[0259] In one embodiment of the present disclosure, the control circuit determines the slots available for the repeated transmission by taking into account dynamic conversion between a first symbol in which the frequency domain is divided into multiple bands and a second symbol different from the first symbol.

[0260] In one embodiment of the present disclosure, the control circuit determines slots available for the repeated transmission by taking into account a mapping in which one transmission opportunity in the repeated transmission spans a first symbol in which a frequency band is divided into multiple bands and a second symbol different from the first symbol.

[0261] A terminal according to one embodiment of the present disclosure includes a control circuit that determines slots available for repeated transmission of an uplink signal based on a group including at least a symbol type, and a transmission circuit that transmits the uplink signal in the determined slots.

[0262] In a communication method according to one embodiment of the present disclosure, a base station determines slots available for repeated transmission of an uplink signal based on a group including at least a symbol type, and receives the uplink signal in the determined slots.

[0263] In a communication method according to one embodiment of the present disclosure, a terminal determines slots available for repeated transmission of an uplink signal based on a group including at least a symbol type, and transmits the uplink signal in the determined slots.

[0264] The disclosures of the specification, drawings and abstract contained in Japanese Patent Application No. 2023-129366, filed on August 8, 2023, are incorporated herein by reference in their entirety.

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

[0266] 100 Base station 101, 201 Receiving unit 102, 202 Demapping unit 103, 203 Demodulation and decoding unit 104 Scheduling unit 105 Available slot control unit 106, 206 Control information holding unit 107, 207 Data and control information generating unit 108, 208 Encoding and modulation unit 109, 209 Mapping unit 110, 210 Transmitting unit 200 Terminal 204 Available slot determining unit 205 Control unit

Claims

1. A base station comprising: a control circuit that determines a slot available for repeated transmission of an uplink signal based on a group including at least a symbol type; and a receiving circuit that receives the uplink signal in the determined slot.

2. The base station according to claim 1, wherein the control circuit determines slots available for the repeated transmission based on the symbol type.

3. The base station according to claim 2, wherein the control circuit determines the slots available for the repeated transmission without taking into account dynamic conversion between a first symbol in which a frequency band is divided into multiple bands and a second symbol different from the first symbol.

4. The base station according to claim 2, wherein the control circuit determines the slots available for the repeated transmission by taking into consideration dynamic conversion between a first symbol in which a frequency band is divided into a plurality of bands and a second symbol different from the first symbol.

5. The base station according to claim 2, wherein the control circuit determines the slots available for the repeated transmission, taking into consideration the use of flexible symbols in a method in which the transmission direction is set in multiple bands obtained by dividing a frequency band.

6. The base station according to claim 1, wherein the control circuit determines slots available for the repeated transmission based on the symbol type and frequency resources allocated to the repeated transmission.

7. The base station according to claim 6, wherein the control circuit determines the slots available for the repeated transmission without taking into consideration dynamic conversion between a first symbol in which a frequency domain is divided into a plurality of bands and a second symbol different from the first symbol.

8. The base station according to claim 6, wherein the control circuit determines the slots available for the repeated transmission by taking into consideration dynamic conversion between a first symbol in which a frequency domain is divided into a plurality of bands and a second symbol different from the first symbol.

9. The base station according to claim 6, wherein the control circuit determines slots available for the repeated transmission by taking into consideration a mapping in which one transmission opportunity in the repeated transmission spans a first symbol in which a frequency band is divided into multiple bands, and a second symbol different from the first symbol.

10. A terminal comprising: a control circuit that determines a slot available for repeated transmission of an uplink signal based on a group including at least a symbol type; and a transmission circuit that transmits the uplink signal in the determined slot.

11. A communication method, comprising: a base station determining a slot available for repeated transmission of an uplink signal based on a group including at least a symbol type; and receiving the uplink signal in the determined slot.

12. A communication method, comprising: a terminal determining a slot available for repeated transmission of an uplink signal based on a group including at least a symbol type; and transmitting the uplink signal in the determined slot.

Images