Terminal, base station, receiving method, and transmitting method

Abstract

This terminal comprises a control circuit that sets a symbol type used for transmitting and receiving semi-static information, and a reception unit that receives the semi-static information using the symbol type.

Description

Terminal, base station, receiving method and transmitting method

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

[0002] The 3rd Generation Partnership Project (3GPP) has completed the physical layer specifications for Release 18 NR (New Radio access technology) as a functional extension of 5G (5th Generation mobile communication systems). 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-7).

[0003] 3GPP TS 38.211 V18.3.0, "Physical channels and modulation (Release 18) ", Jun. 20243GPP TS 38.212 V18.3.0, "Multiplexing and channel coding (Release 18)", Jun. 20243GPP TS 38.213 V18.3.0, "Physical layer procedure for control (Release 18)", Jun. 20243GPP TS 38.214 V18.3.0, "Physical layer procedures for data (Release 18)", Jun. 20243GPP TS 38.215 V18.3.0, "Physical layer measurements (Release 18)", Jun. 20243GPP TS 38.331 V18.2.0, "Radio Resource Control (RRC) protocol specification (Release 18)", Jun. 20243GPP TS 38.321 V18.2.0, "Medium Access Control (MAC) protocol specification (Release 18)", Jun. 2024

[0004] However, there is room for further study on the method of associating the symbol types used in transmitting and receiving quasi-static information.

[0005] Non-limiting embodiments of the present disclosure contribute to providing a terminal and a communication method capable of determining the symbol type to be used for transmitting and receiving semi-static information.

[0006] A terminal according to an embodiment of the present disclosure includes a control circuit that sets a symbol type used for transmitting and receiving quasi-static information, and a receiving unit that receives the quasi-static information using the symbol type.

[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, the terminal and the base station can have the same recognition of the symbol types used for transmitting and receiving quasi-static information.

[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] Figure showing an example of half duplex TDDFigure showing an example of SBFDFigure showing a slot configuration in a non-SBFD-compatible terminalFigure showing a slot configuration in an SBFD-compatible terminalFigure showing an example of CG-PUSCH spanning SBFD symbols and non-SBFD symbolsBlock diagram showing an example configuration of a base stationBlock diagram showing a detailed example configuration of a base stationBlock diagram showing an example configuration of a terminalBlock diagram showing a detailed example configuration of a terminalSequence diagram showing example operations of a base station and a terminalFigure showing an example of signaling method 1 in Configured grant PUSCH (CG-PUSCH)Figure showing an example of signaling method 2 in CG-PUSCHFigure showing an example of setting srs-ResourceIndicator corresponding to two TCI states in a CG-PUSCH configurationFigure showing applyIndicatedTCI-State in CG-PUSCHFigure showing an example of signaling of frequency hopping offset in CG-PUSCHFigure showing an example of determination method 1 in semi-persistent PUCCHFigure showing an example of determination method 2 in periodic PUCCHFigure showing an example of determination method 2 in CG-PUSCHActive FIG. 1 shows an example where BWP is limited to DL subbands. FIG. 2 shows an example architecture of a 3GPP NR system. FIG. 3 shows an example functional division in a 5G O-RAN.

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

[0012] [Regarding Subband Non-Overlapping Full Duplex (SBFD)] "Study on the Evolution of NR Duplex Operation" was discussed as a study item in Release 18. One of the main topics of this study item was support for subband non-overlapping full duplex (SBFD, also known as Cross Division Duplex (XDD)). Based on the results of the feasibility study in Release 18, it was decided that SBFD will be specified in Release 19.

[0013] 1A and 1B are diagrams showing an example of the Duplex method. In Fig. 1A and 1B, the vertical axis represents frequency and the horizontal axis represents time. Also, in Fig. 1, "U" represents uplink transmission and "D" represents downlink transmission.

[0014] 1A shows an example of half-duplex Time Division Duplex (TDD). In FIG. 1A, a terminal (UE: User Equipment) is a terminal connected to a base station (e.g., gNB). In the half-duplex shown in FIG. 1A, 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. 1B 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 not the other. On the other hand, in SBFD, a base station can transmit and receive data in both the uplink and downlink simultaneously. In addition, 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 a dotted frame and a white background in FIG. 1B).

[0016] 1A and 1B, a guard band may be arranged between an uplink subband (UL subband: U) and a downlink subband (DL subband: D). The guard band may be used to reduce interference (CLI: Cross Link Interference) 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 configured with SBFD symbols may also be called an "SBFD slot," and a slot configured with 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 1B is expressed as {DUD}.

[0019] [SBFD Symbol and SBFD-Compatible Terminal] The SBFD symbol may be configured using (for example, by changing) a legacy symbol (existing symbol) such as a DL symbol, a UL symbol, or a Flexible symbol. For example, the SBFD symbol may be configured using a DL symbol. The legacy symbol is configured by, for example, RRC signaling (for example, TDD-UL-DL-ConfigCommon). Here, the non-SBFD symbol is, for example, a symbol that is not an SBFD symbol (for example, a legacy symbol and a symbol not used as an SBFD symbol).

[0020] An SBFD-capable terminal (e.g., SBFD-aware UE) is a terminal that supports SBFD operation and control. An SBFD-capable terminal can acquire SBFD-related configurations, such as the frequency and time domain locations of subbands. An SBFD-incapable terminal is a terminal that does not support SBFD operation and control. An SBFD-incapable terminal (e.g., non-SBFD-aware UE), for example, does not recognize SBFD symbols, and therefore operates by recognizing the symbols as legacy symbols even when legacy symbols are set (or changed) to SBFD symbols.

[0021] 2A and 2B show examples of slot configurations.

[0022] Figure 2A shows the slot configuration for a non-SBFD-compatible terminal. The TDD UL-DL pattern period (the period during which the TDD slot configuration pattern is repeated) is 5 slots, where "D" indicates a DL slot consisting of DL symbols, "F" indicates a Flexible slot consisting of Flexible symbols, and "U" indicates a UL slot consisting of UL symbols.

[0023] Figure 2B shows the slot configuration for an SBFD-compatible terminal. Slots #1, #2, #3, and #6 represent SBFD slots consisting of SBFD symbols. The subband configuration is {DUD}. The SBFD time period (the period during which the SBFD slot configuration pattern is repeated) is five slots, the same as the TDD UL-DL pattern period. Non-SBFD-compatible terminals and SBFD-compatible terminals may share symbols. For example, non-SBFD-compatible terminals may recognize Slot #1 as a DL slot, and SBFD-compatible terminals may recognize it as an SBFD slot, and transmission and reception may be performed based on this. Note that for simplicity, the example shows the same symbol type included in each slot, but different symbol types may be mixed within a slot (for example, SBFD symbols and UL symbols may be mixed within the same slot).

[0024] [Transmission and reception spanning SBFD symbols and non-SBFD symbols] When transmitting and receiving across SBFD symbols and non-SBFD symbols (where a single transmission or reception opportunity in a channel or signal consists of either SBFD symbols or non-SBFD symbols), one of the following configurations may be set in the terminal. Configuration 1: Transmits and receives using only SBFD symbols or non-SBFD symbols. Configuration 2: Transmits and receives using both SBFD symbols and non-SBFD symbols.

[0025] The above configuration may be applied to, for example, PDSCH / PUSCH / PUCCH repetition, SPS PDSCH / CG PUSCH, TBoMS, multi-PUSCH / PDSCH scheduling with a single DCI, periodic / semi-persistent SRS / CSI-RS / PUCCH, and PDCCH.

[0026] Figure 3 shows an example of a CG-PUSCH spanning SBFD symbols and non-SBFD symbols. Resources for the CG-PUSCH are configured in an n-slot cycle, with resources allocated on the SBFD symbols in Slot #1 and resources allocated on non-SBFD symbols (UL symbols) in Slot #n+1. In Configuration 1, CG-PUSCH transmission is possible only in either slot #1 or slot #n+1, but in Configuration 2, CG-PUSCH transmission is possible in both slot #1 and #n+1.

[0027] In Configuration 1, the terminal must determine which symbol type (i.e., SBFD symbols or non-SBFD symbols) to use for transmission and reception. There are two possible cases for transmission and reception in Configuration 1. Case 1: Transmission and reception are dynamically scheduled by the downlink control channel (PDCCH). Case 2: Transmission and reception are semi-statically set by signaling from higher layers.

[0028] In case 1, the symbol type used for transmission and reception may be the symbol type of the scheduled resource (for example, if transmission and reception are scheduled for the SBFD symbol, subsequent transmission and reception may also be performed using only the SBFD symbol).

[0029] On the other hand, in case 2, it is necessary to enable the terminal to determine by some means which symbol type is used to transmit and receive information whose transmission and reception is semi-statically set (hereinafter referred to as "semi-static information"). Case 2 may be applied to CG PUSCH (type 1 CG), periodic / semi-persistent SRS / CSI-RS / PUCCH, and PDCCH.

[0030] [Overview of Communication System] A communication system according to an aspect of the present disclosure includes, for example, at least one base station and at least one terminal.

[0031] FIG. 4A is a block diagram showing a configuration example of a portion of a base station 400 according to an embodiment of the present disclosure, and FIG. 5A is a block diagram showing a configuration example of a portion of a terminal 500 according to an embodiment of the present disclosure.

[0032] 4A, a communication unit (e.g., corresponding to a receiver) receives an uplink control signal, and a control unit (e.g., corresponding to a control circuit) determines a resource for receiving the uplink control signal in consideration of an uplink muting resource.

[0033] 5A, a communication unit (e.g., a transmitter) transmits the uplink control signal using resources determined by a control unit. The control unit (e.g., a control circuit) determines resources for transmitting the uplink control signal in consideration of uplink muting resources.

[0034] [Configuration of Base Station] A detailed configuration of the base station will be described. Fig. 4B is a block diagram showing a detailed configuration example of a portion of a base station 400 according to one embodiment of the present disclosure. The base station 400 includes a receiving unit 401, a demapping unit 402, a demodulation / decoding unit 403, a scheduling unit 404, a control information holding unit 405, a quasi-static transmission / reception control unit 406, a data / control information generation unit 407, an encoding / modulation unit 408, a mapping unit 409, and a transmitting unit 410. At least one of the demapping unit 402, the demodulation / decoding unit 403, the scheduling unit 404, the control information holding unit 405, the quasi-static transmission / reception control unit 406, the data / control information generation unit 407, the encoding / modulation unit 408, and the mapping unit 409 may be configured as a control circuit 411. The receiving unit 401 may be configured as a receiving circuit, and the transmitting unit 410 may be configured as a transmitting circuit.

[0035] The receiving unit 401 performs reception processing such as down-conversion or A / D (Analog / Digital) conversion on a signal received via an antenna, and outputs the processed received signal to the demapping unit 402 .

[0036] The demapping unit 402 performs resource demapping on the received signal (for example, an uplink signal) input from the receiving unit 401, and outputs the modulated signal to the demodulation and decoding unit 403. Furthermore, the demapping unit 402 performs resource demapping on the received signal input from the receiving unit 401 in accordance with a reception instruction for UL reception in the quasi-static information from the scheduling unit 404, and outputs the modulated signal to the demodulation and decoding unit 403.

[0037] The demodulation and decoding unit 403 demodulates and decodes the modulated signal input from the demapping unit 402 , for example, and outputs the decoding result to the scheduling unit 404 .

[0038] The scheduling unit 404 may, for example, perform scheduling for the terminals 500. The scheduling unit 404 schedules transmission and reception for each terminal 500 based on, for example, at least one of the decoding result input from the demodulation and decoding unit 403, the quasi-static transmission and reception information used for transmitting and receiving the quasi-static information input from the quasi-static transmission and reception control unit 406 (e.g., information on symbol types used for transmitting and receiving the quasi-static information, information on resources for transmitting and receiving the quasi-static information, etc.), and the control information input from the control information holding unit 405, and instructs the data and control information generation unit 407 to generate at least one of data and control information. This generation instruction may include a generation instruction for DL ​​transmission of the quasi-static information based on the semi-static transmission and reception information. The scheduling unit 404 also instructs the data and control information generation unit 407 to transmit the quasi-static transmission and reception information input from the semi-static transmission and reception control unit 406 to the terminal 500 as signaling information. Furthermore, the scheduling unit 404 issues a reception instruction for UL reception of the semi-static information to the demapping unit 402 based on, for example, semi-static transmission and reception information input from the semi-static transmission and reception control unit 406. Furthermore, the scheduling unit 404 outputs control information related to the terminal 500 to the control information holding unit 405.

[0039] The control information holding unit 405 holds, for example, control information set in each terminal 500. The held control information may include, for example, information related to slot configuration and information related to SBFD. The control information holding unit 405 may output the held information to each component of the base station 400 (for example, the scheduling unit 404 and the quasi-static transmission / reception control unit 406) as necessary.

[0040] The semi-static transmission and reception control unit 406 determines semi-static transmission and reception information (e.g., information on the symbol type used for transmitting and receiving the semi-static information, information on resources for transmitting and receiving the semi-static information, etc.) based on the control information (e.g., information on the slot configuration, information on SBFD, etc.) input from the control information storage unit 405. The semi-static transmission and reception control unit 406 outputs the determined semi-static transmission and reception information to the scheduling unit 404.

[0041] The data and control information generating unit 407 generates at least one of data and control information, for example, in accordance with an instruction from the scheduling unit 404, and outputs a signal including the generated data or control information to the coding and modulation unit 408. The generated data may include, for example, signaling information of higher layers (e.g., quasi-static transmission and reception information).

[0042] The coding and modulation section 408 codes and modulates, for example, the signal (for example, data, control information) input from the data and control information generation section 407 and outputs the modulated signal to the mapping section 409 .

[0043] The mapping unit 409 performs resource mapping on the modulated signal input from the coding and modulation unit 408 , for example, and outputs the transmission signal to the transmission unit 410 .

[0044] The transmitting unit 410 performs transmission processing such as D / A (Digital / Analog) conversion, up-conversion, or amplification on the signal input from the mapping unit 409, and transmits the radio signal obtained by the transmission processing from the antenna to the terminal 500.

[0045] [Configuration of Terminal] A detailed configuration of the terminal will be described. Fig. 5B is a block diagram showing a detailed configuration example of a portion of a terminal 500 according to one aspect of the present disclosure. The terminal 500 includes a receiving unit 501, a demapping unit 502, a demodulation / decoding unit 503, a control unit 504, a control information holding unit 505, a quasi-static transmission / reception control unit 506, a data / control information generation unit 507, an encoding / modulation unit 508, a mapping unit 509, and a transmission unit 510. At least one of the demapping unit 502, the demodulation / decoding unit 503, the control unit 504, the control information holding unit 505, the quasi-static transmission / reception control unit 506, the data / control information generation unit 507, the encoding / modulation unit 508, and the mapping unit 509 may be configured as a control circuit 511. The receiving unit 501 may be configured as a receiving circuit, and the transmitting unit 510 may be configured as a transmitting circuit.

[0046] The receiving unit 501 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 502 .

[0047] The demapping unit 502, for example, performs resource demapping on the received signal input from the receiving unit 501, and outputs the modulated signal to the demodulation and decoding unit 503. Furthermore, in accordance with a reception instruction for quasi-static DL reception from the control unit 504, the demapping unit 502 performs resource demapping on the received signal input from the receiving unit 501, and outputs the modulated signal to the demodulation and decoding unit 503.

[0048] The demodulation / decoding unit 503 demodulates and decodes the modulated signal input from the demapping unit 502, for example, and outputs the result to the control unit 504. The decoding result may include, for example, signaling information of an upper layer.

[0049] The control unit 504 may issue an instruction to the data and control information generation unit 507 to generate at least one of data and control information, based on, for example, the decoding result (e.g., data or control information) input from the demodulation and decoding unit 503, the quasi-static transmission and reception information input from the quasi-static transmission and reception control unit 506, and the control information input from the control information storage unit 505. This generation instruction may include an instruction to generate the UL transmission of the quasi-static information based on the quasi-static transmission and reception information. Furthermore, the control unit 504 may issue a reception instruction to the demapping unit 502 for DL ​​reception of the quasi-static information, based on, for example, the quasi-static transmission and reception information input from the quasi-static transmission and reception control unit 506. Furthermore, the control unit 504 may output, for example, control information for the terminal 500 to the control information storage unit 505.

[0050] The control information holding unit 505 holds, for example, control information input from the control unit 504, and outputs the held information to each component (for example, the quasi-static transmission / reception control unit 506 and the control unit 504) as necessary.

[0051] The quasi-static transmission / reception control unit 506 determines quasi-static transmission / reception information (e.g., information regarding the symbol type used for transmitting and receiving quasi-static information) based on control information (e.g., information regarding slot configuration, information regarding SBFD, information regarding quasi-static transmission / reception information, etc.) input from the control information storage unit 505, and outputs the determined quasi-static transmission / reception information to the control unit 504.

[0052] The data and control information generating unit 507 generates data or control information according to instructions from the control unit 504 , for example, and outputs a signal including the generated data or control information to the encoding and modulation unit 508 .

[0053] The coding / modulation section 508 codes and modulates the signal input from the data / control information generation section 507 , for example, and outputs the modulated signal to the mapping section 509 .

[0054] The mapping section 509 performs resource mapping on the modulated signal input from the coding / modulation section 508 and outputs the transmission signal to the transmission section 510 .

[0055] The transmitter 510 performs transmission processing such as D / A conversion, up-conversion, or amplification on the signal input from the mapping unit 509, and transmits the radio signal obtained by the transmission processing from the antenna to the base station 400.

[0056] [Operations of Base Station and Terminal] An example of operation in the base station and terminal having the above configuration will be described below. Fig. 6 is a sequence diagram showing an example of operation of base station 400 and terminal 500.

[0057] 6, the base station 400 determines settings (configurations) related to, for example, semi-static information, SBFD, etc. (step S601). The base station 400 sets the determined settings.

[0058] The base station 400 transmits, for example, upper layer signaling information including the determined setting to the terminal 500 (step S602). The signaling information may be broadcast by, for example, an SIB (System Information Block), or may be notified as terminal-specific signaling information.

[0059] The terminal 500 determines semi-static transmission and reception information (for example, symbol types used for transmitting and receiving semi-static information) based on the received signaling information (step S603). The terminal 500 sets the determined semi-static transmission and reception information.

[0060] The base station 400 and the terminal 500 determine whether it is time to perform DL transmission and DL reception of the semi-static information based on the current symbol type and the setting of the semi-static transmission and reception information (steps S604 and S605).

[0061] If it is the timing for DL ​​transmission and DL reception of semi-static information (step S604, Yes, S605, Yes), the base station 400 transmits the semi-static information (at least one of data and control information), which is received by the terminal 500 (step S606).If it is not the timing for DL ​​transmission and DL reception of semi-static information (step S604, No, S605, No), the transmission and reception of the semi-static information are not performed.

[0062] The terminal 500 and the base station 400 determine whether it is time to transmit and receive UL information based on the current symbol type and quasi-static transmission / reception settings (steps S607 and S608).

[0063] If it is the timing for UL transmission and UL reception of the semi-static information (step S607, Yes, S608, Yes), the terminal 500 transmits the semi-static information (at least one of data and control information), and the base station 400 receives it (step S609). If it is not the timing for UL transmission and UL reception of the semi-static information (step S607, No, S608, No), the transmission and reception of the semi-static information are not performed.

[0064] The base station 400 and the terminal 500 each determine whether or not the transmission and reception of the semi-static information has been completed (steps S610 and S611). If the transmission and reception of the semi-static information has been completed (steps S610, Yes, S611, Yes), the base station 400 and the terminal 500 end the processing. If the transmission or reception of the semi-static information has not been completed, the base station 400 and the terminal 500 return to steps S604 and S605 and determine whether or not it is time to perform DL transmission and DL reception of the semi-static information.

[0065] [Symbol type determination method] A method for determining the symbol type of quasi-static transmission and reception information in the terminal 500 (for example, the quasi-static transmission and reception control unit 506) will be described. The base station 400 (for example, the quasi-static transmission and reception control unit 406) may set the quasi-static transmission and reception information for the terminal 500, assuming a symbol type determination method for quasi-static transmission and reception information implemented by the terminal 500. A specific determination method is shown below.

[0066] <Determination Method 1> In this determination method, the symbol type is explicitly notified by signaling information. The signaling information may be broadcast by SIB, for example, or may be notified as terminal-specific signaling information. For example, the symbol type may be notified by the following signaling method.

[0067] <Signaling Method 1> In this signaling method, only the symbol type is notified. For example, a parameter that is notified only when quasi-static information is transmitted and received using SBFD symbols is added to the configuration. The added parameter is optional and is notified as needed. If this parameter is notified, the terminal may determine that quasi-static information is transmitted and received using SBFD symbols, and if not notified, it may determine that quasi-static information is transmitted and received using non-SBFD symbols. The application of Configuration 1 may be notified by other signaling information or may be determined implicitly.

[0068] Figure 7 shows an example of signaling method 1 for Configured grant PUSCH (CG-PUSCH). symbolType-r19 is added under rrc-ConfiguredUplinkGrant. symbolType-r19 is an optional parameter and has only the value "SBFD". If symbolType-r19 is included, CG-PUSCH is transmitted only on SBFD symbols, and if symbolType-r19 is not included, CG-PUSCH is transmitted only on non-SBFD symbols.

[0069] In this way, in this signaling method, the symbol type can be notified by whether or not symbolType-r19 is included, so notification can be made with little signaling overhead.

[0070] <Signaling Method 2> In this signaling method, the symbol type is notified together with Configuration 1 and Configuration 2. For example, in addition to "SBFD" and "non-SBFD" as the setting value of the parameter (e.g., symbolType-r19) used to identify the symbol type in Configuration 1, "both" may be notified to indicate that it is Configuration 2.

[0071] 8 shows an example of signaling method 2 for CG-PUSCH. The setting values ​​of symbolType-r19 include {"SBFD", "non-SBFD", "both"}. When "SBFD" or "non-SBFD" is set, it is Configuration 1, and CG-PUSCH is transmitted only using the set symbol type. When "both" is set, it is Configuration 2, and CG-PUSCH is transmitted using both symbol types. symbolType-r19 may be an optional parameter, and if not included in ConfiguredGrantConfig, it may be a default operation (for example, the default operation may be defined in advance, such as transmitting only using non-SBFD symbols).

[0072] In this way, in this signaling method, Configuration 1 and Configuration 2 can be changed for each configuration of channel signals, etc., so that the flexibility of settings can be improved compared to Signaling Method 1.

[0073] In this way, according to this method, by explicitly notifying the symbol type, the complexity of determining the symbol type at the terminal can be reduced.

[0074] <Determination Method 2> In this method, the symbol type is determined in association with the configuration set separately for SBFD symbols and non-SBFD symbols. In transmitting and receiving quasi-static information, parameters used for transmission or reception (e.g., parameters for setting time and frequency resources) are set from the base station to the terminal through configuration. When parameters used for transmission and reception are set separately for SBFD symbols and non-SBFD symbols, the terminal can determine which symbol type to use for transmission or reception depending on which parameters are set. For example, if parameters for SBFD symbols are set in the configuration for UL transmission of quasi-static information, UL transmission of quasi-static information may be performed on the SBFD symbol (the same applies to DL and non-SBFD symbols). The application of Configuration 1 may be notified by other signaling information or may be implicitly determined. Specific parameter examples are given below.

[0075] <Parameter Example 1> In this example, separate TCI (Transmission Configuration Indication) states are set for SBFD symbols and non-SBFD symbols, and the TCI states are linked to the symbol types of quasi-static transmission and reception information. For example, in SBFD, a base station performs DL transmission and UL reception at the same time, so the antenna configuration used for transmission and reception may differ from that of TDD. In non-SBFD symbols (i.e., TDD operation), the base station can use all available antennas for DL ​​transmission or UL reception, while in SBFD symbols, the base station must perform DL transmission and UL reception simultaneously, so the available antennas may be allocated for use between DL transmission and UL reception. If the antenna configurations are different between SBFD symbols and non-SBFD symbols, the TCI states may also be different.

[0076] When separate TCI states are configured for SBFD symbols and non-SBFD symbols, the TCI states can be associated with the symbol type of quasi-static transmission and reception information. One TCI state is associated with the SBFD symbol, and the other TCI state is associated with the non-SBFD symbol. The multi-TRP function introduced in Release 17 or Release 18 may be used to configure two TCI states. That is, in Release 17, the configuration for transmitting different TCI states for each TRP during repeated transmission of PUCCH or PUSCH (during repetition transmission) may be used. Since two TCI states can be configured, they are associated with SBFD symbols and non-SBFD symbols, respectively. Additionally, the TCI state configuration function activated by a MAC CE command, introduced for single-DCI based multi-TRP in Release 18, may be used. Since up to two TCI states can be enabled as codepoints for setting the TCI state, two TCI states are associated with SBFD symbols and non-SBFD symbols, respectively. As an example, two signaling methods corresponding to the above are given below.

[0077] <Signaling Method 1> In this signaling method, the symbol type is notified using parameters associated with two TCI states. Two sets of parameters corresponding to the two TCI states are used to determine which TCI state is applied. For example, in the CG-PUSCH, parameters such as antennaPort, dmrs-SeqInitialization, precodingAndNumberOfLayers, and srs-ResourceIndicator may be set in pairs for each of the two TCI states.

[0078] FIG. 9 shows an example of srs-ResourceIndicator settings corresponding to two TCI states in a CG-PUSCH configuration (other parameters are omitted). srs-ResourceIndicator and srs-ResourceIndicator2-r17 are associated with the two TCI states. The symbol type is determined as follows by associating the first TCI state and the second TCI state with the first parameter and the second parameter (e.g., srs-ResourceIndicator and srs-ResourceIndicator2), respectively. If only the first parameter is set, the symbol type is a non-SBFD symbol. If only the second parameter is set, the symbol type is an SBFD symbol. If both the first and second parameters are set, Configuration 2 is applied.

[0079] In this way, in this signaling method, by using parameters associated with two TCI states, it is possible to associate quasi-static transmission / reception information with symbol types without introducing additional parameters, thereby reducing signaling overhead.

[0080] <Signaling Method 2> In this signaling method, up to two TCI states are enabled as codepoints for setting the TCI state, and the symbol type is notified. For example, the "applyIndicatedTCI-State" parameter included in the semi-static transmission / reception information configuration is used.

[0081] 10 shows applyIndicatedTCI-State in CG-PUSCH. The setting value of applyIndicatedTCI-State can be set to {first, second, both}. For example, "first" may be associated with a non-SBFD symbol, "second" with an SBFD symbol, and "both" with Configuration 2.

[0082] In this way, this signaling method utilizes the function of enabling up to two TCI states as a codepoint for setting the TCI state, thereby linking quasi-static transmission / reception information with symbol types without introducing additional parameters, thereby reducing signaling overhead.

[0083] <Parameter Example 2> In this example, individual frequency hopping (FH) offsets are set for SBFD symbols and non-SBFD symbols, and the frequency hopping offsets are linked to the symbol types of quasi-static transmission and reception information. Frequency hopping is used to obtain a frequency diversity effect in UL transmission. Because the usable UL resources differ between SBFD symbols and non-SBFD symbols, the offset used for frequency hopping must be changed between SBFD symbols and non-SBFD symbols.

[0084] In the quasi-static transmission and reception information, when the frequency hopping offset for SBFD symbols and non-SBFD symbols can be set, the frequency hopping offset can be linked to the symbol type.

[0085] FIG. 11 shows an example of signaling a frequency hopping offset in CG-PUSCH. A parameter for setting a conventional frequency hopping offset is frequencyHoppingOffset. In this example, frequencyHoppingOffset-r19 is added as a parameter for setting the frequency hopping offset of the SBFD symbol. By making frequencyHoppingOffset-r19 optional, the symbol type can be indicated by whether frequencyHoppingOffset-r19 is enabled or disabled. That is, if frequencyHoppingOffset-r19 is enabled, the symbol type of CG-PUSCH is an SBFD symbol. If frequencyHoppingOffset-r19 is disabled, the symbol type of CG-PUSCH is a non-SBFD symbol. If frequency hopping is not applied to the SBFD symbol, frequencyHoppingOffset-r19 can be disabled by enabling it and then setting the value to 0.

[0086] In this way, in this signaling method, by setting individual frequency hopping offsets for SBFD symbols and non-SBFD symbols and linking the TCI state with the symbol type of quasi-static transmission and reception, it is possible to associate quasi-static transmission and reception with the symbol type without introducing additional parameters, thereby reducing signaling overhead.

[0087] In this way, in this determination method, the symbol type of quasi-static transmission / reception information is determined in association with the configuration set individually for SBFD symbols and non-SBFD symbols, thereby eliminating the need for additional signaling for symbol type notification and reducing signaling overhead.

[0088] <Determination Method 3> In this determination method, the symbol type is determined from the resource of the quasi-static transmission / reception information at the reference timing. In the transmission and reception of quasi-static information triggered by higher layer signaling, the recognition of the initial transmission timing or reception timing between the base station and the terminal may differ due to Layer 1 and Layer 2 processing (e.g., HARQ retransmission). Therefore, in this method, the symbol type of the quasi-static transmission / reception information is determined by using a reference timing. The reference timing may be defined or set based on relative timing (relative time) or absolute timing (absolute time). For example, the following reference timing determination method may be used.

[0089] <Timing Determination Method 1> In this determination method, the first transmittable / receiveable timing based on the activation timing of semi-static information transmission and reception is set as the reference timing. For semi-persistent SRS / PUCCH / CSI-RS, the first transmittable / receiveable timing is determined after a predetermined number of slots have passed since activation. Regardless of whether the terminal transmits or receives at the first transmittable / receiveable timing, the first transmittable / receiveable timing is set as the reference timing, making it a unique reference timing between the base station and terminal. The symbol type is determined from the semi-static transmission and reception resources at the reference timing.

[0090] Fig. 12 shows an example of determination method 1 for quasi-static PUCCH. First, activation of quasi-static PUCCH transmission is performed from the base station to the terminal by MAC signaling. Since MAC signaling is transmitted by PDSCH, HARQ-ACK for PDSCH is transmitted from the terminal to the base station (ACK is sent in this example). Based on the timing of transmitting HARQ-ACK, The first PUCCH transmission timing after the first PUCCH transmission timing is set as the reference timing. is the number of slots per subframe at subcarrier spacing (SCS) μ (e.g., 1 slot for μ=15 kHz).

[0091] In this way, this determination method can determine the symbol type of quasi-static transmission / reception information by using the first transmission / reception possible timing based on the timing of activation of quasi-static transmission / reception as the reference timing. Although a terminal may not transmit CG-PUSCH due to reasons such as a lack of UL data or high-priority UL transmission, the symbol type can be determined at the first transmission / reception possible timing regardless of whether the terminal transmits CG-PUSCH. Since additional signaling (symbol type signaling) is not required, signaling overhead can be reduced.

[0092] <Timing Determination Method 2> In this determination method, the reference timing is determined by setting or defining absolute timing. For example, a reference SFN may be set or defined in the configuration. An SFN is set in the reference SFN, and the first transmission timing or reception timing at the set SFN is used as the reference timing. The Nth transmission timing or reception timing, rather than the first, may also be used as the reference timing. N may be defined or set in advance. The reference timing is uniquely determined regardless of whether the terminal actually transmits or receives. The symbol type is determined from the resources for transmitting and receiving quasi-static information at the reference timing.

[0093] Figure 13 shows an example of determination method 2 for periodic PUCCH. In this example, the reference SFN is defined as SFN 0. When a terminal receives RRC signaling at SFN n, the terminal calculates the first PUCCH transmission timing for SFN 0 and sets this as the reference timing. Note that the PUCCH is actually transmitted only after the terminal has received RRC signaling and is ready for transmission. The symbol type of the periodic PUCCH is determined from the symbol type of the PUCCH resource at the reference timing.

[0094] FIG. 14 shows an example of determination method 2 for CG-PUSCH. This is an example of CG-PUSCH type 1, where the reference SFN is set to n by configuration. Whether it is the timing to transmit the CG-PUSCH may be determined, for example, based on the following equation (that is, if the following equation is satisfied, the CG-PUSCH can be transmitted): [(SFN × numberOfSlotsPerFrame × numberOfSymbolsPerSlot) + (slot number in the frame × numberOfSymbolsPerSlot) + symbol number in the slot] = (timeReferenceSFN × numberOfSlotsPerFrame × numberOfSymbolsPerSlot + timeDomainOffset × numberOfSymbolsPerSlot + S + N × periodicity) modulo (1024 × numberOfSlotsPerFrame × numberOfSymbolsPerSlot)

[0095] Here, numberOfSlotsPerFrame is the number of slots per frame, numberOfSymbolsPerSlot is the number of symbols per slot, timeReferenceSFN is the reference SFN, timeDomainOffset is the offset from the reference SFN (unit: slot), S is the number of symbols until the start symbol of the PUSCH time domain resource (the number of symbols of S calculated from SLIV), N is the number of repetitions, and periodicity is the transmission period (unit: slot).

[0096] The first transmission timing can be found by setting N=0 on the right-hand side. A timing other than the first may also be used. When a timing other than the first is used, the value of N is notified or a predefined value is used. In FIG. 14 , CG-PUSCH configuration (RRC signaling) is received in SFN n+1. The reference SFN is set to n by configuration, and the first transmission timing of the CG-PUSCH is determined to be the CG-PUSCH in SFN n+1 based on timeDomainOffset and S, with SFN n as the reference timing. The CG-PUSCH in SFN n+1 is used as the reference timing, and the symbol type is determined from the resources to which the CG-PUSCH is allocated.

[0097] In this way, this determination method can determine the symbol type for quasi-static transmission and reception by using absolute timing as the reference timing. Since additional signaling (symbol type signaling) is not required, signaling overhead can be reduced. The reference timing can be determined even when there is no activation, as in determination method 1.

[0098] In this way, in this determination method, the symbol type is determined from the quasi-static transmission / reception resources at the reference timing, so additional signaling is not required, and signaling overhead can be reduced.

[0099] In determination method 3, when the time domain resource for one transmission and reception of quasi-static information at the reference timing is allocated across SBFD symbols and non-SBFD symbols, the symbol type may be determined by the following method. By determining the symbol type as described below, the symbol type can be uniquely determined even if the resource is allocated across SBFD symbols and non-SBFD symbols.

[0100] <Determination method 1 when symbol types are mixed> Determining is made based on the symbol type of the resource for the next transmission / reception timing. If the resource for the next transmission / reception timing also spans both SBFD symbols and non-SBFD symbols, the symbol type will be that of the next transmission / reception timing (this continues until only one of the symbol types remains).

[0101] <Determination Method 2 When Symbol Types are Mixed> Determination is made from the symbol type at a specific position, for example, the symbol type of the first or last symbol in the allocated resource.

[0102] <Determination method 3 when symbol types are mixed> Use the symbol type with the greater number of symbols. For example, if a resource is composed of 14 symbols, 8 symbols are SBFD symbols, and 6 symbols are non-SBFD symbols, the symbol type is SBFD symbols.

[0103] <Modification> The symbol type may be determined based on the UE capability. The base station may set the symbol type based on the UE capability (for example, by using determination method 1 or determination method 2), or the terminal may implicitly determine the symbol type. Examples are given below.

[0104] <Modification 1> When a terminal reports to a base station a UE capability that limits the symbol type to SBFD symbols or non-SBFD symbols, the symbol type is set or implicitly determined to be limited to SBFD symbols or non-SBFD symbols. For example, when the symbol type is limited to SBFD symbols, resources exist for both DL and UL in SBFD symbols, which helps to reduce transmission and reception delays. Furthermore, when the symbol type is limited to non-SBFD symbols, for example, it is useful when a terminal wants to quickly fall back from processing using SBFD symbols (SBFD operation) to legacy processing (legacy operation) (since quasi-static transmission and reception requires reconfiguration by RRC signaling, for example, in an environment with a large CLI, transmission and reception on SBFD symbols may fail, which may increase delays).

[0105] <Modification 2> The symbol type may be determined according to the frequency band in which the terminal can transmit and receive. For example, if the terminal is a RedCap terminal and the active BWP is limited to DL subbands or UL subbands, the symbol type may be limited. For example, if the active BWP in an SBFD symbol includes only DL subbands, even if quasi-static UL transmission is configured, the UL resources on the SBFD symbol cannot be used, so the symbol type may be determined to be a non-SBFD symbol.

[0106] An example in which Active BWP is limited to the DL subband is shown in Fig. 15. In this way, by determining the symbol type according to the available frequency band, it is possible to reduce signaling overhead.

[0107] (Supplementary Note) Information indicating whether the terminal 500 supports the functions, operations, or processes described in each of the above-described embodiments and each supplementary note may be transmitted (or notified) from the terminal 500 to the base station 400, for example, as capability information or capability parameters of the terminal 500.

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

[0109] For example, the base station 400 may determine (or decide or assume) the functions, operations, or processes that the terminal 500 that transmitted the capability information supports (or does not support) based on the capability information received from the terminal 500. The base station 400 may perform operations, processes, or controls according to the determination result based on the capability information. For example, the base station 400 may control the symbol type based on the capability information received from the terminal 500.

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

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

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

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

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

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

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

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

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

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

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

[0121] (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), Vehicle to Everything (V2X) communication, or communication between an Ambient IoT Reader and an Ambient IoT Device. 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, PRDCH (Physical Reader-to-Device Channel), PDRCH (Physical Device-to-Reader Channel), PDCCH, PUCCH, PDSCH, PUSCH, or PBCH. For example, the control information in an embodiment of the present disclosure may be replaced with any of DCI, UCI, SCI (Sidelink Control Information), R2D Control Information, and D2R Control Information. For example, the terminal and base station in an embodiment of the present disclosure may be replaced with an Ambient IoT Device or an Ambient IoT Reader.

[0122] The Ambient IoT Device may be a wireless communication device with a backscattering function or a transmission / reception bandwidth of several resource blocks or less. The Ambient IoT Reader may be a wireless communication device with a communication function with the Ambient IoT Device. The Ambient IoT Device may also be called an Ambient IoT terminal, IoT terminal, LPWA terminal, or tag.

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

[0124] (SBFD) In ​​one embodiment of the present disclosure, operations on uplink, downlink, and sidelink symbols may be applied to symbols (e.g., SBFD symbols) on which SBFD (Subband Non-Overlapping Full Duplex, Subband Full Duplex) operations or controls are performed. In SBFD symbols, a frequency domain (or frequency resource, frequency band) is divided into multiple frequency domains (e.g., subbands, RB sets, subbands, or sub-BWPs (Bandwidth Parts)). A terminal transmits and receives in different directions (e.g., downlink or uplink) in units of subbands, which are the divided domains. In SBFD symbols, a terminal may transmit and receive in one direction, either uplink or downlink, but not in the other direction. On the other hand, a base station may be capable of transmitting and receiving on both the uplink and downlink simultaneously. SBFD symbols may have a smaller frequency domain available for downlink transmission than symbols that transmit and receive only downlink transmission. Also, SBFD symbols may have a smaller frequency domain available for uplink transmission than symbols that transmit and receive only uplink transmission.

[0125] In addition, in the SBFD symbol, a terminal may transmit and receive uplink and downlink simultaneously. In this case, the frequency domain in which the terminal transmits and the frequency domain in which the terminal receives may not be adjacent, but may be separated by a frequency interval (also called a frequency gap).

[0126] In addition, different transmission and reception directions in subband units, which are divided areas, may include transmission and reception of side links.

[0127] (XDD: Cross Division Duplex) In one embodiment of the present disclosure, the operation for uplink, downlink, and sidelink symbols may be applied to symbols (e.g., full duplex symbols) where full duplex operation or control is performed. In a full duplex symbol, both the terminal and the base station can simultaneously transmit and receive on the uplink and downlink. In a full duplex symbol, the terminal and the base station may simultaneously transmit and receive in an available frequency region (or frequency resource, frequency band), or may simultaneously transmit and receive in a partial frequency region (i.e., transmission or reception may be performed in other frequency regions). In this case, the frequency region in which the base station or terminal transmits and receives may not be adjacent, but may have a frequency interval (also called a frequency gap). Furthermore, for the purpose of, for example, reducing interference, either the terminal or the base station may simultaneously transmit and receive (i.e., the other may transmit or receive).

[0128] In addition, full duplex operation may be applied to an operation in which a terminal can simultaneously transmit and receive sidelinks, or to an operation in which a terminal can simultaneously transmit and receive sidelinks and uplinks or downlinks.

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

[0130] <5G NR System Architecture and Protocol Stack> The 5G NR system architecture generally assumes an NG-RAN (Next Generation - Radio Access Network) including gNBs. The gNBs provide UE-side termination of the 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 that performs AMF) via an NG-C interface, and to a User Plane Function (UPF) (e.g., a specific core entity that performs UPF) via an NG-U interface. The NG-RAN architecture is shown in Figure 16 (see, for example, 3GPP TS 38.300 v15.6.0, section 4).

[0131] <RRC connection setup and reconfiguration procedure> This shows the NAS part of the interaction between the UE, gNB, and AMF (5GC entity) when the UE transitions from RRC_IDLE to RRC_CONNECTED (see TS 38.300 v15.6.0).

[0132] RRC is a higher layer signaling protocol used to configure the UE and gNB. 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.

[0133] Therefore, 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.

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

[0135] For each UE, 5GC establishes one or more PDU sessions. For each UE, the NG-RAN establishes, for example, at least one Data Radio Bearer (DRB) for each PDU session. 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.

[0136] (Open-RAN) The base station described in each embodiment (for example, a 5G NR base station called a gNB) may be configured with three functional modules: a Centralized Unit (CU), a Distributed Unit (DU), and a Radio Unit (RU).

[0137] A CU may be referred to as a centralized node, aggregation node, central station, aggregation station, or centralized unit. A DU may be referred to as an O-RAN Distributed Unit (O-DU), distributed node, distributed station, or distributed unit. An RU may be referred to as an O-RAN Radio Unit (O-RU), radio equipment, radio node, radio station, antenna unit, or radio unit.

[0138] There are several split options for the functional split configuration (or functional split point) between CU, DU, and RU. The term "functional split point" is sometimes referred to as "split," "option," or "split option."

[0139] Examples of "division options" include the following division options 1 to 8. The functions of the base station described in each embodiment may be divided into a CU, a DU, and an RU by any of the following division options 1 to 8. For example, the CU, DU, and RU may be functionally divided, or the functions may be divided only between the CU and DU or only between the DU and RU. (1) Segmentation option 1: Between RRC (radio resource control) and PDCP (2) Segmentation option 2: Between PDCP and RLC (High-RLC) (3) Segmentation option 3: Between High-RLC and Low-RLC (4) Segmentation option 4: Between RLC (Low-RLC) and MAC (High-MAC) (5) Segmentation option 5: Between High-MAC and Low-MAC (6) Segmentation option 6: Between MAC (Low-MAC) and PHY (High-PHY) (7) Segmentation option 7: Between High-PHY and Low-PHY (8) Segmentation option 8: Between PHY (Low-PHY) and RF

[0140] The functional split point between the CU and O-DU may be split option 2. The section between the CU and O-DU is called midhaul, and the F1 interface is specified by 3GPP. The section between the O-DU and O-RU is called fronthaul, and the functional split point may be split option 7-2x, which is adopted as the O-RAN fronthaul specification.

[0141] Figure 17 shows an example of functionally dividing the gNB base station functions into CU, O-DU, and O-RU using Split Option 2 and Split Option 7-2x.

[0142] The CU may have, for example, a radio resource control (RRC) function, a service data adaptation protocol (SDAP) function, and a packet data convergence protocol (PDCP) function.

[0143] The O-DU may include, for example, a radio link control (RLC) function, a MAC function, and a higher physical layer (HIGH-PHY) function. The HIGH-PHY function may include an encoding function, a scrambling function, a modulation function, a layer mapping function, a precoding function, and a resource element (RE) mapping function for downlink (DL) transmission. The HIGH-PHY function may also include a decoding function, a descrambling function, a demodulation function, a layer demapping function, and a resource element (RE) demapping function for uplink (UL) reception.

[0144] The O-RU may have, for example, a LOW-PHY function and an RF function. The LOW-PHY function may also have, for downlink transmission, a beamforming function, an IFFT (Inverse First Fourier Transform) + CP (Cyclic Prefix) assignment function, and a D / A (Digital to Analog) conversion function. The LOW-PHY function may also have, for uplink reception, an A / D (Analog to Digital) conversion function, a CP removal + FFT (First Fourier Transform) function, and a beamforming function.

[0145] In addition, if the O-DU does not have a precoding function, the O-RU may have a precoding function.

[0146] The O-RU may have a function related to LBT (listen before talk). The evolving common public radio interface (eCPRI) is specified as the communication method between the O-DU and the O-RU in Split Option 7-2x. In Split Option 7-2x, eCPRI transmits and receives sampling sequences of the in-phase (I) and quadrature (Q) components of the OFDM signal in the frequency domain, as well as information used for beamforming in the antenna and time synchronization signals.

[0147] Information transmitted by the signals described in each embodiment (PDCCH, PUCCH, PDSCH, PUSCH, MAC CE, RRC, etc.) may be transmitted between the O-DU and the O-RU via the eCPRI User Plane (U-Plane) or Control Plane (C-Plane).

[0148] When the functions described in each embodiment are performed in the O-RU by functional division, the O-DU may control the O-RU by transmitting information for controlling the functions via a control signal (e.g., eCPRI) between the O-DU and the O-RU.

[0149] When the functions described in each embodiment are performed in the O-DU by functional division, the O-RU may receive the results of the functions performed in the O-DU via a control signal (e.g., eCPRI) and control the O-RU based on the received results.

[0150] The CU, O-DU, and O-RU may be deployed in physically different devices with their respective functions connected by optical fiber or the like, or some or all of their functions may be deployed in the same physical device.

[0151] The CU and O-DU may be logical entities implemented as software running on a server in the cloud or the like as a virtualized RAN (virtual Radio Access Network: vRAN). Also, some or all of the functions of the CU and O-DU may be provided as a virtualized network function (Network Functions Virtualization: NFV) service.

[0152] The transceiver does not have to be a radio transceiver, but may be, for example, a network transceiver, an optical transceiver, etc. The radio resources allocated by the O-DU may be resources for wireless communication between the O-RU and the UE.

[0153] The present disclosure can be realized in software, hardware, or software in conjunction with hardware.

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

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

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

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

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

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

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

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

[0162] (1) A terminal according to an embodiment of the present disclosure includes a control circuit that sets a symbol type used for transmitting and receiving semi-static information, and a receiving unit that receives the semi-static information using the symbol type. (2) A terminal according to an embodiment of the present disclosure includes the terminal of (1), wherein the symbol type is notified by signaling information. (3) A terminal according to an embodiment of the present disclosure includes the terminal of (2), wherein the signaling information includes a symbol type and whether to receive only using subband non-overlapping full duplex (SBFD) symbols or non-SBFD symbols, or whether to transmit and receive using both SBFD symbols and non-SBFD symbols. (5) A terminal according to an embodiment of the present disclosure includes the terminal of (1), wherein the symbol type is determined in association with configurations that are set individually for SBFD symbols and non-SBFD symbols. (6) In a terminal according to an embodiment of the present disclosure, in the terminal of (5), the symbol type is determined in association with a TCI-state. (7) In a terminal according to an embodiment of the present disclosure, in the terminal of (6), the symbol type is determined in association with a frequency hopping offset. (8) In a terminal according to an embodiment of the present disclosure, in the terminal of (1), the symbol type is determined from a resource for transmitting the quasi-static information at a reference timing. (9) In a terminal according to an embodiment of the present disclosure, in the terminal of (8), the reference timing is an activation timing for transmitting and receiving the quasi-static information. (10) In a terminal according to an embodiment of the present disclosure, in the terminal of (8), the reference timing is a set or defined timing. (11) In a terminal according to an embodiment of the present disclosure, in the terminal of (1), when the reference timing is assigned across SBFD symbols and non-SBFD symbols, the reference timing is determined by the symbol type of the next transmission and reception timing, the symbol type at a specific position, or the symbol type with the larger number of symbols.(12) A base station according to an embodiment of the present disclosure includes a control circuit that sets a symbol type to be used for transmitting and receiving quasi-static information, and a transmitter that transmits the quasi-static information using the symbol type. (13) A reception method for a terminal according to an embodiment of the present disclosure includes setting a symbol type to be used for transmitting and receiving quasi-static information, and receiving the quasi-static information using the symbol type. (14) A transmission method for a base station according to an embodiment of the present disclosure includes setting a symbol type to be used for transmitting and receiving quasi-static information, and transmitting the quasi-static information using the symbol type.

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

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

[0165] 400 Base station 401, 501 Receiving unit 402, 502 Demapping unit 403, 503 Demodulation and decoding unit 404 Scheduling unit 405, 505 Control information holding unit 406, 506 Quasi-static transmission and reception control unit 407, 507 Data and control information generating unit 408, 508 Encoding and modulation unit 409, 509 Mapping unit 410, 510 Transmitting unit 411, 511 Control circuit 500 Terminal 504 Control unit

Claims

1. A terminal comprising: a control circuit that sets a symbol type to be used for transmitting and receiving quasi-static information; and a receiving unit that receives the quasi-static information using the symbol type.

2. The terminal according to claim 1, wherein the symbol type is notified by signaling information.

3. The terminal according to claim 2, wherein the signaling information includes the symbol type.

4. The terminal according to claim 2, wherein the signaling information includes the symbol type and whether reception is to be performed using only SBFD (Subband non-overlapping full duplex) symbols or non-SBFD symbols, or whether transmission and reception is to be performed using both SBFD symbols and non-SBFD symbols.

5. The terminal according to claim 1, wherein the symbol type is determined in association with a configuration that is set individually for SBFD symbols and non-SBFD symbols.

6. The terminal according to claim 5, wherein the symbol type is determined in association with a TCI-state.

7. The terminal according to claim 5, wherein the symbol type is determined in association with a frequency hopping offset.

8. The terminal according to claim 1, wherein the symbol type is determined from a resource for transmitting the quasi-static information at a reference timing.

9. The terminal according to claim 8, wherein the reference timing is an activation timing for transmitting and receiving the semi-static information.

10. The terminal according to claim 8, wherein the reference timing is a set or defined timing.

11. The terminal according to claim 8, wherein, when the reference timing is allocated across SBFD symbols and non-SBFD symbols, the reference timing is determined by the symbol type of the next transmission / reception timing, the symbol type at a specific position, or the symbol type with the greater number of symbols.

12. A base station comprising: a control circuit that sets a symbol type to be used for transmitting and receiving quasi-static information; and a transmitter that transmits the quasi-static information using the symbol type.

13. A receiving method for a terminal, comprising: setting a symbol type to be used for transmitting and receiving quasi-static information; and receiving the quasi-static information using the symbol type.

14. A transmission method for a base station, comprising: setting a symbol type to be used for transmitting and receiving quasi-static information; and transmitting the quasi-static information using the symbol type.

Images