Terminal, communication method, and integrated circuit

Abstract

This terminal comprises: a control circuit that determines, on the basis of the configuration of a measured reference signal, at least one of the contents and the number of measurement values included in a report field of the measurement with respect to the reference signal; and a transmission circuit that transmits, on the basis of the determined at least one of the number and contents, a signal including the measurement values.

Description

Terminal, base station, and communication method

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

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

[0003] 3GPP TS 38.211 V17.2.0, "NR; Physical channels and modulation (Release 17)," June 20223GPP TS 38.212 V17.2.0, "NR; Multiplexing and channel coding (Release 17)," June 20223GPP TS 38.213 V17.2.0, "NR; Physical layer procedure for control (Release 17)," June 20223GPP TS 38.214 V17.2.0, "NR; Physical layer procedures for data (Release 17)," June 20223GPP TS 38.215 V17.1.0, "NR; V17.1.0, "NR; Radio Resource Control (RRC) protocol specification (Release 17)", June 2022R1-2205520, "Summary #2 of [109-e-R18-Duplex-03] Email discussion on subband non-overlapping full duplex", 3GPP TSG-RAN WG1 Meeting#109-e

[0004] However, there is room for improvement in how to report interference between terminals.

[0005] Non-limiting examples of the present disclosure contribute to providing a terminal, a base station, and a communication method that can appropriately report interference between terminals.

[0006] A terminal according to one embodiment of the present disclosure includes a control circuit that determines, based on the configuration of a reference signal to be measured, at least one of the number and content of measurement values ​​to be included in a measurement report field for the reference signal, and a transmission circuit that transmits a signal including the measurement values ​​based on the determined at least one of the number and content.

[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, interference between terminals can be appropriately reported.

[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 subband non-overlapping full duplex (SBFD) Diagram showing an example of Sounding Reference Signal (SRS)-Reference Signal Received Power (RSRP) measurement and reporting Diagram showing an example of a Report field for L1-RSRP Diagram showing an example of Cross-Link Interference (CLI) between terminals Diagram showing an example of a Channel State Information (CSI) report-based SRS-RSRP report Block diagram showing an example of the configuration of a part of a base station Block diagram showing an example of the configuration of a part of a terminal Block diagram showing an example of the configuration of a base station Block diagram showing an example of the configuration of a terminal Sequence diagram showing an example of the operation of a base station and a terminal Diagram showing an example of a Report field Diagram showing an example of a Report field Diagram showing an example of a Report field Diagram showing an example of a Report field Diagram showing an example of a Report field Diagram showing an example of a Report field Diagram of an exemplary architecture of a 3GPP NR system Schematic diagram showing functional separation between NG-RAN (Next Generation - Radio Access Network) and 5GC (5th Generation Core) Sequence diagram of the procedure for setting up / reconfiguring a Radio Resource Control (RRC) connection Enhanced Mobile BroadBand (eMBB), massive Machine Type Communication (mMTC) A schematic diagram illustrating the use scenarios of 5G (Ultra Reliable and Low Latency Communications) 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)] Subband non-overlapping full duplex (SBFD) is being discussed in Release 18. Figure 1 shows an example of SBFD.

[0013] 1(a) shows an example of the operation of a base station (also referred to as gNB) and a terminal (UE: User Equipment) (e.g., UE #1 and UE #2) in the same cell in an SBFD scenario. In the SBFD scenario, the base station performs SBFD operation, and the terminal performs half-duplex operation.

[0014] Figure 1(b) shows an example of subband allocation in SBFD. In Figure 1(b), the vertical axis represents frequency and the horizontal axis represents time. Also, in Figure 1(b), "UL" represents uplink transmission and "DL" represents downlink transmission. Also, resources unused in each device (e.g., gNB, UE#1, and UE#2) are indicated by dotted lines.

[0015] As shown in Figure 1(b), in SBFD, a frequency resource (frequency band) is divided into multiple subbands (also called bands, RB sets, subbands, or sub-BWPs (Bandwidth parts)), and transmission in different directions is supported on a subband-by-subband basis. As shown in Figure 1(b), a base station can simultaneously transmit and receive on the uplink and downlink (e.g., SBFD operation), and a terminal can transmit and receive on either the uplink or downlink in a given time resource (e.g., half-duplex operation). For example, in the example of Figure 1(b), UE#1 communicates with the base station in the uplink, and UE#2 communicates with the base station in the downlink in the same time resource.

[0016] [Regarding Interference] As shown in Figure 1(a), when a base station performs SBFD operation and a terminal performs half-duplex operation, various types of interference can occur. For example, self-interference at the base station or cross-link interference (CLI) between terminals can occur. Self-interference at the base station and CLI between terminals significantly degrade reception characteristics, so countermeasures are required (see, for example, Non-Patent Document 7). For example, it is expected that measures can be taken to address CLI between terminals using limited terminal resources. Therefore, there is a need to consider methods for measuring CLI between terminals.

[0017] One of the methods for measuring CLI between end-users in existing standards is SRS-RSRP (SRS: Sounding Reference Signal, RSRP: Reference Signal Received Power) / CLI-RSSI (RSSI: Received Signal Strength Indicator). SRS-RSRP / CLI-RSSI is a Layer 3-based measurement and reporting of CLI between end-users, and is supported in Release 16.

[0018] SRS-RSRP is a measurement value of the received power of SRS transmitted by a terminal from another terminal.

[0019] The CLI-RSSI is a measurement of the linear average of the total received power of the resources that the terminal is configured to measure.

[0020] FIG. 2 is a diagram showing an example of the use of Layer 3-based SRS-RSRP. Layer 3-based SRS-RSRP measures and reports CLI between terminals (UE#1 and UE#2 in FIG. 2) belonging to different base stations (gNB#1 and gNB#2 in FIG. 2). For example, one terminal transmits an SRS, and the other terminal receives the SRS, measures the RSRP, and reports it. In the example shown in FIG. 2, UE#2 transmits an SRS to gNB#2. Also, in the example shown in FIG. 2, UE#1 receives the SRS transmitted from UE#2, measures the SRS-RSRP, and reports the measured SRS-RSRP to gNB#1.

[0021] However, methods for reporting CLI between terminals in SBFD scenarios have not been thoroughly considered.

[0022] In one non-limiting embodiment of the present disclosure, a method for reporting CLI between terminals in an SBFD scenario is described.

[0023] [CSI Report and Report Field] An example of the "Report field" that configures the measurement values ​​reported by the terminal will be described.

[0024] An existing Layer 1-based reporting method is the Channel State Information (CSI) report.

[0025] In the CSI report, for example, the terminal measures values ​​such as channel quality information (e.g., CQI: Channel Quality Information), transmission rank, and L1-RSRP (L1: Layer 1) using at least one of a CSI-Reference Signal (CSI-RS) and an SSB (Synchronization Signal Block) transmitted from the base station to the terminal, and reports a report including the measurement values ​​to the base station.

[0026] In the CSI report, the base station configures, for the terminal performing the measurement, the operation of the report in the time domain (for example, operation of reporting periodically, quasi-periodically, or aperiodically), a report configuration that sets the values ​​to be reported, and a resource configuration that includes information on the resources to be measured.

[0027] For example, the terminal quantizes the measurement values ​​and configures (or stores or places) them in the Report field. Report numbers that identify multiple reports to be reported are each associated with a Report field. For example, an Uplink Control Information (UCI) bit string corresponds to multiple report numbers reported by the terminal.

[0028] FIG. 3 shows an example of the structure of the L1-RSRP Report field. The Report field may include a "resource ID (e.g., Resource (CSI-RS or SSB) ID)" that identifies the resource to be measured, a "quantized measurement value (e.g., quantized RSRP or quantized differential RSRP)" that corresponds to the resource to be measured, and a "capability index" that identifies the capability corresponding to the resource to be measured. In the example shown in FIG. 3, up to four measurements (or resources) may be reported in each Report field, and they may be arranged in descending order in the Report field. In addition, in the quantized measurement value, the quantized differential RSRP indicates a quantized value of the difference between the RSRP of each resource and the maximum RSRP. For example, 7 bits may be allocated to the quantized RSRP and 4 bits to the quantized differential RSRP as the number of quantization bits for the L1-RSRP measurement value.

[0029] [Configuration of SRS resource and SRS resource set] The configuration of the SRS resource and the SRS resource set will be described.

[0030] The SRS resource set defines multiple SRS resources. For example, parameters such as an SRS resource set ID, SRS resource usage, or power control may be defined for each SRS resource set.

[0031] Furthermore, for example, for each SRS resource, parameters such as information on resource mapping (for example, symbol allocation or transmission frequency band to which the SRS resource is allocated), multiplexing parameters (for example, cyclic shift or frequency multiplexing), or antenna ports may be defined.

[0032] For example, {codebook, nonCodebook, antennaSwitching, beamManagement} can be set as usage defined in the SRS resource set. For example, codebook and nonCodebook may be set when the SRS is used to estimate uplink CSI, antennaSwitching may be set when the SRS is used to estimate downlink CSI, and beamManagement may be set when the SRS is used to establish a transmit / receive beam pair in the uplink.

[0033] Also, for example, {port1, port2, port4} can be set as the antenna port defined in the SRS resource. For example, when port2 is set as the antenna port, the terminal transmitting the SRS transmits the SRS resource using two antenna ports.

[0034] The types and values ​​of parameters defined in the SRS resource set and SRS resource are not limited to the above examples.

[0035] [Measurement of CLI Between Terminals in SBFD Scenario] In the SBFD scenario, a base station can transmit and receive uplink and downlink simultaneously, and therefore CLI may occur between terminals.

[0036] FIG. 4 shows an example of a CLI between terminals.

[0037] For example, CLI between terminals may occur when different terminals communicate with a base station in different directions. For example, in FIG. 4, UE#1 communicates with a gNB on the downlink (DL) and UE#2 communicates with a gNB on the uplink (UL) in the same time resource. In this case, CLI from UE#2 to UE#1 may occur. Here, "Victim UE" refers to the terminal that is interfered with (UE#1 in FIG. 4), and "Aggressor UE" refers to the terminal that causes interference (UE#2 in FIG. 4).

[0038] For example, if DL and UL are assigned to adjacent subbands, the reception performance of DL may be degraded due to interference from UL. The CLI between terminals depends on the transmission power of the interfering terminal or the positions of the interfered terminal and the interfering terminal.

[0039] Here, since the base station cannot grasp the detailed location of the terminal, it is difficult for the base station to estimate the CLI between terminals. Therefore, SRS-RSRP or CLI-RSSI, which terminals use to measure the interference between terminals, can be effectively used in the SBFD scenario.

[0040] When a terminal measures the CLI between terminals and reports it to a base station, the reported CLI measurement value (or observation value) is useful for scheduling in the base station. For example, the base station can perform scheduling that does not allocate terminals with large reported CLI measurement values ​​(e.g., terminals with large interference) to each other at the same time. Also, for example, the base station can perform scheduling that allocates terminals with small reported CLI measurement values ​​(e.g., terminals with small interference) to each other at the same time.

[0041] Furthermore, when measuring CLI between terminals, the more terminals there are in a cell, the greater the overhead of reporting CLI measurements. For example, since a base station can estimate the location of a terminal to some extent by the direction of a beam with the terminal or timing advance, it may set a limit on the terminals for which CLI is measured.

[0042] [CSI Report-Based SRS-RSRP Reporting] As an example, a CSI report-based SRS-RSRP report in an SBFD scenario will be described.

[0043] Figure 5 shows an example of a CSI report-based SRS-RSRP report. The left diagram of Figure 5 shows the situation between a terminal (e.g., UE#1, UE#2, and UE#3) and a base station (e.g., gNB), and the right diagram of Figure 5 shows an example of resource allocation in SBFD. In the right diagram of Figure 5, subband#0 and subband#2 are downlink subbands, and subband#1 is an uplink subband.

[0044] In the example of Fig. 5, UE#2 and UE#3 transmit SRS in subband#1. UE#1 measures the CLI between the terminals using the SRS (or SRS resource) transmitted from UE#2 and UE#3. For example, UE#1 may measure the SRS-RSRP corresponding to the CLI from UE#2 to UE#1 (or from UE#3 to UE#1). UE#1 reports the SRS-RSRP measurement value to the base station in subband#1.

[0045] In the CSI report-based SRS-RSRP report, the report configuration and resource configuration in the CSI report can be reused as they are. The report configuration is a setting related to the report of the terminal that measures the SRS-RSRP, and the resource configuration is a setting related to the SRS to be measured (e.g., SRS resource set, etc.).

[0046] On the other hand, the Report field of the uplink control information (UCI) bit string generation function in the SRS-RSRP report needs to be modified. For example, an SRS resource set-based report or a Report field that takes into account the SRS resource and SRS resource set configuration (e.g., usage or antenna port) can be a report that is useful for scheduling by the base station. For example, if a terminal reports a Report field that takes into account the usage of SRS transmission to the base station, the base station can process SRS, including SRS-RSRP, between terminals.

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

[0048] Fig. 6 is a block diagram showing a configuration example of a portion of a base station 100 according to one aspect of the present disclosure. In the base station 100 shown in Fig. 6, a control unit (e.g., corresponding to a control circuit) determines at least one of the number and content of measurement values ​​to be included in a report field of a measurement value (e.g., SRS-RSRP) for a reference signal based on the configuration of the reference signal (e.g., SRS) measured in a terminal 200. A receiving unit (e.g., corresponding to a receiving circuit) receives a signal including the measurement values ​​based on at least one of the determined number and content.

[0049] 7 is a block diagram showing a configuration example of a portion of terminal 200 according to one aspect of the present disclosure. In terminal 200 shown in FIG. 7, a control unit (e.g., corresponding to a control circuit) determines at least one of the number and content of measurement values ​​to be included in a report field of measurement values ​​for a reference signal (e.g., SRS-RSRP) based on the configuration of the reference signal (e.g., SRS) to be measured. A transmission unit (e.g., a transmission circuit) transmits a signal including the measurement values ​​based on at least one of the determined number and content.

[0050] [Configuration of Base Station] Fig. 8 is a block diagram showing an example configuration of a base station 100 according to one embodiment of the present disclosure. In Fig. 8, the base station 100 includes a receiving unit 101, a demodulating and decoding unit 102, an inter-terminal CLI determining unit 103, a scheduling unit 104, a control information holding unit 105, a data and control information generating unit 106, an encoding and modulating unit 107, and a transmitting unit 108.

[0051] For example, at least one of the demodulation / decoding unit 102, the terminal-to-terminal CLI determination unit 103, the scheduling unit 104, the control information storage unit 105, the data / control information generation unit 106, and the encoding / modulation unit 107 may be included in the control unit shown in Figure 6, and the receiving unit 101 may be included in the receiving unit shown in Figure 6.

[0052] 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 demodulation and decoding unit 102 .

[0053] Demodulation and decoding section 102, for example, demodulates and decodes the received signal input from receiving section 101 and outputs the decoded result to scheduling section 104. Furthermore, for example, if the decoded result includes SRS-RSRP report information, demodulation and decoding section 102 outputs the report information to inter-terminal CLI determination section 103.

[0054] Inter-terminal CLI determination section 103 may determine the CLI between terminals based on, for example, SRS-RSRP report information input from demodulation and decoding section 102 and control information input from control information holding section 105, and may identify a combination of terminals with strong inter-terminal CLI (for example, terminals with CLI equal to or greater than a threshold) or a combination of terminals with weak inter-terminal CLI (for example, terminals with CLI less than a threshold). Inter-terminal CLI determination section 103 outputs information related to the identified combination of terminals to scheduling section 104.

[0055] Scheduling section 104 may, for example, perform scheduling for terminals 200. Scheduling section 104 schedules transmission and reception for each terminal 200 based on, for example, at least one of the decoding result input from demodulation and decoding section 102, information on the combination of terminals input from inter-terminal CLI determination section 103, and control information input from control information storage section 105, and instructs data and control information generation section 106 to generate at least one of data and control information. Furthermore, scheduling section 104 may, for example, instruct data and control information generation section 106 to generate SRS transmission setting information and SRS measurement setting information (e.g., resource configuration and report configuration of an SRS-RSRP report) based on the control information input from control information storage section 105, and instruct inter-terminal CLI determination section 103 to perform SRS measurement.

[0056] The control information storage unit 105 stores, for example, control information set in each terminal 200. The control information may include, for example, information such as the SRS configuration (for example, information about the SRS to be assigned to the terminal 200), the configuration of an SRS-RSRP report, or past measurement values ​​of the SRS-RSRP. The control information storage unit 105 may output the stored information to each component of the base station 100 (for example, the inter-terminal CLI determination unit 103 and the scheduling unit 104) as necessary.

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

[0058] The coding / modulation section 107 codes and modulates the signal input from the data / control information generation section 106, for example, and outputs the modulated signal to the transmission section .

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

[0060] [Terminal Configuration] Fig. 9 is a block diagram showing an example configuration of terminal 200 according to one aspect of the present disclosure. In Fig. 9, terminal 200 includes receiving section 201, demodulating / decoding section 202, SRS receiving section 203, transmission control section 204, control information holding section 205, SRS generating section 206, data / control information generating section 207, encoding / modulating section 208, and transmitting section 209.

[0061] For example, at least one of the demodulation / decoding unit 202, SRS receiving unit 203, transmission control unit 204, control information holding unit 205, SRS generating unit 206, data / control information generating unit 207, and encoding / modulating unit 208 may be included in the control unit shown in Figure 7, and the transmitting unit 209 may be included in the transmitting unit shown in Figure 7.

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

[0063] The demodulation / decoding unit 202 demodulates and decodes, for example, the received signal input from the receiving unit 201, and outputs the decoded result to the transmission control unit 204. The decoded result may include, for example, upper layer signaling information and downlink control information. Furthermore, if the decoded result includes an SRS to be measured, the demodulation / decoding unit 202 outputs the decoded result to the SRS receiving unit 203.

[0064] The SRS receiving unit 203 extracts the SRS from the decoding result input from the demodulation and decoding unit 202. The SRS receiving unit 203 measures the SRS based on, for example, control information input from the control information holding unit 205 (e.g., information such as the resource configuration and report configuration of the SRS-RSRP report) and the extracted SRS, and outputs the quantized measurement value to the transmission control unit 204.

[0065] The transmission control unit 204 outputs signaling information (e.g., resource configuration information and report configuration information of the SRS-RSRP report, and settings related to SRS transmission) included in the decoding result input from the demodulation and decoding unit 202 to the control information holding unit 205. Furthermore, the transmission control unit 204 may instruct the data and control information generating unit 207 to generate at least one of data and control information, based on, for example, the control information input from the control information holding unit 205 (e.g., information related to the resource configuration and report configuration of the SRS-RSRP report) or the decoding result input from the demodulation and decoding unit 202 (e.g., downlink control information). Furthermore, the transmission control unit 204 outputs SRS measurement values ​​to the data and control information generating unit 207 based on information input from the SRS receiving unit 203. In addition, the transmission control unit 204 may instruct the SRS generation unit 206 to generate an SRS, for example, based on settings regarding SRS transmission input from the control information storage unit 205 or downlink control information input from the demodulation / decoding unit 202.

[0066] The control information holding unit 205 holds, for example, control information input from the transmission control unit 204 (for example, the resource configuration and report configuration of the SRS-RSRP report, and settings related to SRS transmission), and outputs the held information to each component (for example, the SRS receiving unit 203 and the transmission control unit 204) as necessary.

[0067] The SRS generating unit 206 generates a code sequence for the SRS based on, for example, signaling information related to SRS transmission input from the transmission control unit 204. The SRS generating unit 206 outputs the generated code sequence to the coding and modulation unit 208 as an SRS, for example.

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

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

[0070] The transmitting unit 209 performs transmission processing such as D / A conversion, up-conversion, or amplification on the signal input from the encoding / modulating unit 208, and transmits the radio signal obtained by the transmission processing from the antenna to the base station 100.

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

[0072] 10 is a sequence diagram showing an example of the operation of base station 100 and terminal 200. In FIG. 10, as an example, UE#1 (terminal 200) performs SRS measurement using the SRS transmitted from UE#2 and reports an SRS-RSRP report to base station 100.

[0073] 10, the base station 100 determines settings (configuration) related to SRS transmission (S101). The base station 100 transmits higher layer signaling information including the determined configuration information related to SRS transmission to the UE#2 (S102).

[0074] UE#2 configures SRS transmission based on the configuration information from base station 100 (S103).

[0075] The base station 100 determines, for example, settings (configuration) related to SRS measurement (S104). The base station 100 transmits higher layer signaling information including the determined setting information related to SRS measurement to the UE#1 (S105).

[0076] UE#1 configures resources and reports for the SRS-RSRP report based on the configuration information from base station 100 (S106).

[0077] For example, UE#2 transmits the set SRS to base station 100 (S107).

[0078] At this time, UE#1 receives the SRS transmitted from UE#2 to base station 100 and performs SRS measurement (S108). UE#1 transmits a signal (e.g., PUCCH or PUSCH) including an SRS-RSRP report to base station 100 based on the SRS-RSRP report settings and the SRS measurement results (S109).

[0079] Base station 100 may perform scheduling for terminals 200 including UE#1 and UE#2 based on, for example, at least one of the SRS measurement results transmitted from UE#2 and the SRS-RSRP report transmitted from UE#1 (not shown).

[0080] [Method of Configuring Report Field] Next, a description will be given of an example of a method of configuring a Report field in terminal 200 (e.g., SRS receiving unit 203 and transmission control unit 204). Terminal 200 determines at least one of the number and content of measurement values ​​(e.g., SRS-RSRP) to be included in the Report field of measurement for an SRS, based on, for example, the configuration of the SRS to be measured (e.g., the configuration of an SRS resource set or an SRS resource).

[0081] Report field configuration methods 1 to 3 will be explained below.

[0082] <Configuration Method 1> In configuration method 1, each Report field corresponds to one SRS resource set. Furthermore, the Report field is configured by the SRS-RSRP of multiple (e.g., all) SRS resources that make up one SRS resource set corresponding to the Report field.

[0083] FIG. 11 shows an example of the structure of the Report field in the structure method 1.

[0084] The uplink control information (UCI) bit string is composed of multiple reports, and for example, report numbers may be assigned to each report in ascending order.

[0085] The Report field refers to a bit field of each report. In Fig. 11, each Report field (e.g., Report #n) is associated with one SRS resource set ID (e.g., SRS Resource set ID #m).

[0086] For example, terminal 200 measures all (e.g., K) SRS resources constituting an SRS resource set corresponding to each Report field and quantizes the measurement values ​​(e.g., SRS-RSRP). Quantization may define, for example, an n1-bit quantization table (n1: the number of bits in the table obtained from the range and step size) and an n2-bit quantization difference table (n2: the number of bits in the table obtained from the range and step size). Terminal 200 may convert the measurement values ​​into quantized values ​​using, for example, the quantization table and the quantization difference table.

[0087] In this case, as shown in Fig. 11, the first column of the Report field may store the quantized SRS-RSRP of the SRS resource to which the smallest SRS resource ID (e.g., #1) in the SRS resource set is set. The quantized SRS-RSRP is a value obtained by quantizing a measurement value using a quantization table.

[0088] 11, the remaining columns (e.g., the second to K-th columns) of the Report field may store the quantized difference SRS-RSRP of each SRS resource to which an SRS resource ID (e.g., #2 to #K) arranged in ascending order is set. The quantized difference SRS-RSRP is a value obtained by quantizing the difference value from the SRS-RSRP in the first column of the Report field (the RSRP corresponding to SRS resource #1) using a quantization difference table.

[0089] Note that the quantized SRS-RSRP used as the basis for the quantized differential SRS-RSRP is not limited to the SRS-RSRP corresponding to the smallest SRS resource ID among the SRS resources, and may be another SRS-RSRP. For example, the quantized SRS-RSRP may be the SRS-RSRP corresponding to an SRS resource ID different from the smallest SRS resource ID, or may be the maximum or minimum SRS-RSRP.

[0090] In this way, in configuration method 1, the Report field stores the SRS-RSRP for each of multiple (e.g., all) SRS resources constituting one SRS resource set. For example, the number of SRS resources constituting an SRS resource set may be set individually for each SRS resource set. In configuration method 1, the configuration of the Report field may vary based on the configuration of the SRS resource set (e.g., the number of SRS resources).

[0091] For example, terminal 200 reports to base station 100 the SRS-RSRP of all SRS resources that make up one SRS resource set corresponding to the Report field. This allows base station 100 to acquire detailed information about the CLI between terminals 200. For example, base station 100 can perform scheduling that takes into account the CLI between terminals 200, based on the detailed information about the CLI between terminals 200. For example, base station 100 can perform scheduling that reduces the CLI between terminals, such as not allocating terminals 200 with strong inter-terminal interference at the same time, or allocating terminals 200 with weak inter-terminal interference at the same time, thereby reducing degradation of the reception characteristics of terminal 200.

[0092] <Configuration Method 2> In configuration method 2, each Report field is configured by an SRS-RSRP corresponding to the usage of the SRS resource set. For example, in configuration method 2, the content of the measurement value (SRS-RSRP) included in the Report field may differ depending on the usage of the SRS resource set (e.g., the purpose of SRS transmission).

[0093] FIG. 12 shows an example of the configuration of the Report field in configuration method 2 when the usage of the SRS resource set (SRS resource set #m) is set to “codebook.”

[0094] The uplink control information (UCI) bit string is composed of multiple reports, and for example, report numbers may be assigned to each report in ascending order.

[0095] The Report field refers to a bit field of each report. In Fig. 12, each Report field (e.g., Report #n) is associated with one SRS resource set ID (e.g., SRS Resource set ID #m).

[0096] For example, terminal 200 measures the SRS-RSRP of each antenna port (e.g., L) of all (e.g., K) SRS resources constituting an SRS resource set corresponding to each Report field and quantizes the measurement values. For example, as shown in Fig. 12, the Report field of Report #m may store a total of K x L SRS-RSRPs for each of the L antenna ports of K SRS resources #1 to #K constituting SRS resource set #m.

[0097] 12, the first column of the Report field may store a quantized SRS-RSRP corresponding to the smallest antenna port ID (e.g., #1) of an SRS resource to which the smallest SRS resource ID (e.g., #1) in an SRS resource set is set. The quantized SRS-RSRP is a value obtained by quantizing a measurement value using a quantization table.

[0098] 12, the remaining columns of the Report field (e.g., the second column to the K*Lth column) may store quantized differences SRS-RSRP for SRS resources, each of which has SRS resource IDs (e.g., #2 to #K) arranged in ascending order and antenna port IDs (e.g., #1 (or #2) to #L) arranged in ascending order for each SRS resource. The quantized differences SRS-RSRP are values ​​obtained by quantizing the difference between the SRS-RSRP in the first column of the Report field (the RSRP corresponding to SRS resource #1 and antenna port #1) using a quantization difference table.

[0099] Note that the quantized SRS-RSRP used as the basis for the quantized differential SRS-RSRP is not limited to the SRS-RSRP corresponding to the smallest SRS resource ID and the smallest antenna port ID in the SRS resource, and may be another SRS-RSRP. For example, the quantized SRS-RSRP may be the SRS-RSRP corresponding to an SRS resource ID and an antenna port ID different from the smallest SRS resource ID and the smallest antenna port ID, or may be the maximum or minimum SRS-RSRP.

[0100] In this way, in configuration method 2, the content of the measurement value included in the Report field may be determined based on, for example, the SRS configuration (for example, the usage of the SRS resource set).

[0101] Terminal 200 reports, for example, an SRS-RSRP corresponding to the usage of the SRS resource set. This enables base station 100 to perform scheduling that takes into account inter-terminal CLI when performing transmission and reception control based on the usage of the received SRS (for example, when using the SRS for uplink CSI estimation in codebook-based SRS transmission).

[0102] For example, when "usage" is set to "codebook," terminal 200 transmits multiple SRSs (SRS resources) using multiple antenna ports. Base station 100 receives the SRSs of these SRS resources, estimates uplink CSI, and selects an optimal SRS resource, uplink transmission rank, or precoding based on the CSI estimation result. According to configuration method 2, base station 100 can consider the CLI between terminals in addition to the CSI between terminal 200 and base station 100 by taking into account the CLI between terminals for each antenna port included in the Report field when selecting the SRS resource, uplink transmission rank, and precoding.

[0103] Furthermore, for example, terminal 200 may report a different Report field for each SRS usage to base station 100, thereby enabling base station 100 to perform scheduling that takes CLI into consideration when performing scheduling (or control of transmission and reception) based on SRS usage.

[0104] Note that, in configuration method 2, the case where usage is set to codebook has been described, but usage is not limited to codebook. When usage is different from codebook, terminal 200 may determine the contents of the measurement value included in the Report field corresponding to that usage and report the SRS-RSRP report to base station 100. For example, when usage is set to codebook, terminal 200 may apply the Report field configuration of configuration method 2, and when usage is set to a value different from codebook, terminal 200 may apply the Report field configuration of configuration method 1 or configuration method 3 described below.

[0105] <Configuration Method 3> In configuration method 3, each Report field corresponds to multiple SRS resource sets and is configured with SRS-RSRPs of up to m SRS resources. In configuration method 3, for example, a specified number m of measurement values ​​from among the measurement values ​​for multiple SRS resources may be stored in the Report field. For example, the contents of the measurement values ​​included in the Report field may be determined based on the SRS configuration (e.g., the configuration of an SRS resource set or an SRS resource).

[0106] Terminal 200 may measure a plurality of SRS resources, quantize up to m SRS-RSRPs arranged in descending (or ascending) order, and store the quantized values ​​in the Report field, for example.

[0107] "m", which indicates the number of SRS-RSRPs to report, may be defined (or specified) in a standard, may be set in terminal 200 by higher layer signaling, or may be set (or notified) to the terminal by downlink control information (e.g., DCI).

[0108] Furthermore, m may be defined as a function of payload size n of uplink control information (UCI) bits reported to base station 100. For example, m and n may differ depending on whether transmission is via an uplink data channel (e.g., a Physical Uplink Shared Channel (PUSCH)) or an uplink control channel (e.g., a Physical Uplink Control Channel (PUCCH)).

[0109] As in configuration method 3, by limiting the number of SRS-RSRPs that make up the Report field, it is possible to reduce the number of uplink control information (UCI) bits and the number of reports to base station 100. For example, there is a limit to the number of uplink control information (UCI) bits, and when reporting all SRS-RSRPs, terminal 200 may transmit uplink control information (including SRS-RSRP reports) multiple times to base station 100. In contrast, by limiting the number of SRS-RSRPs to be reported, it is possible to reduce the number of reports to base station 100.

[0110] Furthermore, by having terminals 200 report SRS-RSRP in descending order, base station 100 can identify terminals 200 with strong inter-terminal CLI, making it possible to schedule terminals 200 so that the same time resources are not allocated to those terminals 200.

[0111] Alternatively, by having terminals 200 report SRS-RSRP in ascending order, base station 100 can identify terminals 200 with weak CLI between them, making it possible to schedule the allocation of the same time resources to these terminals 200.

[0112] By performing such scheduling that can reduce interference between terminals, it is possible to reduce degradation of reception characteristics at terminal 200.

[0113] Regarding configuration method 3, a method for limiting the number of SRS-RSRPs to be reported will be described.

[0114] <Configuration Method 3-1> In configuration method 3-1, the Report field is configured with a plurality of SRS-RSRPs, a plurality of SRS resources corresponding to the SRS-RSRPs, and an SRS resource set ID corresponding to the SRS resource ID.

[0115] Terminal 200 reports up to m SRS-RSRPs in descending (or ascending) order. For example, the Report field may store a specified number m of measurement values ​​of each of a plurality of SRS resources included in a plurality of SRS resource sets in descending or ascending order.

[0116] FIG. 13 shows an example of the configuration of the Report field in configuration method 3-1.

[0117] The uplink control information (UCI) bit string is composed of multiple reports, and for example, report numbers may be assigned to each report in ascending order.

[0118] The Report field refers to a bit field of each report. In Fig. 13, each Report field (e.g., Report #n) is composed of, for example, up to four (m = 4) quantized SRS-RSRPs. In the Report field, up to four SRS-RSRPs are arranged in descending (or ascending) order, and the Report field stores an SRS resource ID (SRS Resource indicator in Fig. 13) corresponding to each SRS-RSRP. Furthermore, the Report field stores the ID of the SRS resource set to which each SRS resource belongs (SRS resource set ID in Fig. 13).

[0119] For example, the maximum four SRS-RSRPs stored in the Report field may include SRS-RSRPs of different SRS resource sets, or may include SRS-RSRPs of the same SRS resource set.

[0120] In configuration method 3-1, for example, the top (or bottom) m SRS-RSRPs from among multiple measurement values ​​(SRS-RSRPs) are stored (or configured) in the Report field, and the remaining SRS-RSRPs are not included in the Report field, thereby reducing the number of uplink control information bits and the number of reports.

[0121] <Configuration Method 3-2> In configuration method 3-2, the Report field is configured with a plurality of average SRS-RSRPs and a plurality of SRS resource set IDs corresponding to the average SRS-RSRPs.

[0122] Terminal 200 reports up to m average SRS-RSRPs in descending (or ascending) order. For example, the Report field may store the average SRS-RSRP for each of a specified number m of SRS resource sets among the SRS resource sets.

[0123] The average SRS-RSRP may be calculated by averaging the SRS-RSRPs of multiple (eg, all) SRS resources in the SRS resource set.

[0124] FIG. 14 shows an example of the configuration of the Report field in configuration method 3-2.

[0125] The uplink control information (UCI) bit string is composed of multiple reports, and for example, report numbers may be assigned to each report in ascending order.

[0126] The Report field refers to a bit field of each report. In Fig. 14, each Report field (e.g., Report #n) is composed of, for example, up to four (m=4) quantized average SRS-RSRPs. In the Report field, up to four SRS-RSRPs are arranged in descending (or ascending) order, and the ID of the SRS resource set corresponding to each average SRS-RSRP (SRS resource set ID in Fig. 14) is stored (or configured) in the Report field.

[0127] In configuration method 3-2, the average SRS-RSRP is stored in the Report field for each SRS resource set, thereby reducing the number of uplink control information bits and the number of reports.

[0128] Furthermore, in configuration method 3-2, one average SRS-RSRP is obtained for each SRS resource set, so the Report field is not occupied by the SRS-RSRP of a specific SRS resource set. For example, in configuration method 3-1, when SRS measurements are performed for multiple SRS resource sets (SRS resource sets in which multiple SRS resources are configured), the Report field may be occupied by multiple SRS-RSRPs in a specific SRS resource set. However, in configuration method 3-2, one average SRS-RSRP is obtained for each SRS resource set, so the Report field is not occupied by a specific SRS resource set.

[0129] In configuration method 3-2, the case where the average SRS-RSRP of each SRS resource set is stored in the Report field has been described. However, the measurement value to be stored is not limited to the average SRS-RSRP value, and may be another measurement value (e.g., maximum or minimum value) for each SRS resource set.

[0130] <Configuration Method 3-3> In configuration method 3-3, the Report field is configured with a plurality of average SRS-RSRPs and a plurality of SRS resource set group IDs corresponding to the average SRS-RSRPs.

[0131] Terminal 200 reports up to m average SRS-RSRPs in descending (or ascending) order. For example, the Report field may store the average SRS-RSRP for each of a specified number m of SRS resource set groups among multiple SRS resource set groups.

[0132] The average SRS-RSRP may be calculated, for example, by averaging the SRS-RSRPs of multiple (eg, all) SRS resources in the SRS resource set group.

[0133] An SRS resource set group may consist of multiple SRS resource sets.

[0134] FIG. 15 shows an example of the configuration of the Report field in configuration method 3-3.

[0135] The uplink control information (UCI) bit string is composed of multiple reports, and for example, report numbers may be assigned to each report in ascending order.

[0136] The Report field refers to a bit field of each report. In Fig. 15, each Report field (e.g., Report #n) is composed of, for example, up to four (m=4) quantized average SRS-RSRPs. In the Report field, up to four SRS-RSRPs are arranged in descending (or ascending) order, and the ID of the SRS resource set group corresponding to each average RSRP (SRS resource set group ID in Fig. 15) is stored (or configured) in the Report field.

[0137] In configuration method 3-3, the number of uplink control information bits and the number of reports can be further reduced by calculating the average SRS-RSRP for each SRS resource set group.

[0138] Furthermore, for example, in a situation where CLI fluctuations between terminals are unlikely to change, reporting a long-term CLI that averages multiple SRS-RSRPs may be beneficial to base station 100. For example, if terminal 200 moves slowly, reporting a long-term (averaged) CLI can reduce the number of reports compared to reporting a short-term (non-averaged) CLI, thereby enabling more effective use of resources. For example, the configuration of the Report field may be switched between a configuration in which the SRS-RSRPs for all SRS resources that make up an SRS resource set are stored, as in Configuration Method 1, and a configuration in which the average SRS-RSRP for an SRS resource set group (or SRS resource set) is stored, as in Configuration Method 3 (or Configuration Method 2).

[0139] In configuration method 3-3, the case where the average SRS-RSRP of each SRS resource set group is stored in the Report field has been described. However, the measurement value to be stored is not limited to the average SRS-RSRP value, and may be another measurement value (e.g., maximum or minimum value) for each SRS resource set group.

[0140] Report field configuration methods 1 to 3 have been described above.

[0141] It is also possible to combine any of the configuration methods 1 to 3. For example, by combining the configuration methods 2 and 3, the Report field may store a specified number m of SRS-RSRP measurement values ​​according to the usage of the SRS resource set.

[0142] Thus, in this embodiment, base station 100 and terminal 200 determine the configuration of the Report field of measurements for SRS (e.g., the number of SRS-RSRPs to be reported, the contents of the measurement values ​​to be reported) based on the configuration of the SRS to be measured.

[0143] This makes it possible to configure a Report field that takes into account the configuration of the SRS resource and SRS resource set (e.g., usage or antenna port), and allows terminal 200 to appropriately report CLI between terminals in an SBFD scenario. Therefore, for example, base station 100 can improve the reception characteristics of terminal 200 by scheduling terminal 200 based on the reported SRS-RSRP report.

[0144] (Other Embodiments) Note that an embodiment of the present disclosure is not limited to Layer 1-based reporting, but can also be applied to Layer 2-based reporting using Medium Access Control (MAC) signaling or Layer 3-based reporting using Radio Resource Control (RRC) messages. Compared to Layer 1-based reporting, Layer 2-based reporting reduces the frequency of reports but increases the number of transmittable bits. Furthermore, Layer 3-based reporting can reuse the functionality of the reporting method (e.g., configuration or notification method) in the existing L3-based SRS-RSRP.

[0145] Furthermore, in the above embodiment, measurement and reporting of short-term interference between terminals is not limited to within the same cell, but can also be applied to multiple cells. For example, when communications are performed in different directions in different cells, a terminal at a cell boundary receives CLI from a terminal in a different cell. Therefore, measurement and reporting of short-term interference between terminals is effective for reducing CLI between terminals in multiple cells.

[0146] In the above embodiment, the reported measurement value is not limited to SRS-RSRP, but may be other measurement values. For example, the reported measurement value may be SRS-RSRQ (Reference Signal Received Quality), and in the case of SRS-RSRQ, a Report field configuration method similar to that of SRS-RSRP can be defined.

[0147] Furthermore, in the above-described embodiment, the reported measurement value is not limited to SRS-RSRP, and for example, the same operation as the SRS-RSRP report (method of configuring the Report field) is possible with RSSI as well. Note that for RSSI, the resources to be measured (for example, OFDM (Orthogonal Frequency Division Multiplexing) symbols and measurement bandwidth, etc.) are set by base station 100. Therefore, the Report field may be configured with the ID of the resource and the RSSI of the resource.

[0148] In the above-described embodiment, the values ​​of the number of SRS resources in the Report field, the number of bits allocated to SRS-RSRP, and the prescribed number m are merely examples and are not limited to these.

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

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

[0151] 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 reporting of SRS-RSRP to the terminal 200 based on the capability information received from the terminal 200.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0171] NR use cases / deployment scenarios may include enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), and massive machine-type communication (mMTC), which have diverse requirements in terms of data rate, latency, and coverage. For example, eMBB is expected to support peak data rates (20 Gbps in the downlink and 10 Gbps in the uplink) and effective (user-experienced) data rates approximately three times higher than those offered by IMT-Advanced. On the other hand, URLLC imposes stricter requirements on ultra-low latency (0.5 ms for user plane latency in both UL and DL) and high reliability (1-10-5 within 1 ms). Finally, mMTC 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0191] 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 18. 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.

[0192] Figure 20 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 19) interacts with the 3GPP core network to provide services. For example, it may access a Network Exposure Function (NEF) to support applications that affect traffic routing, or interact with a policy framework for policy control (e.g., QoS control) (see Policy Control Function (PCF)). Based on operator deployment, Application Functions considered trusted by the operator can interact directly with the associated Network Functions. Application Functions not authorized by the operator to directly access Network Functions interact with the associated Network Functions using an external exposure framework via the NEF.

[0193] Figure 20 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.

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

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

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

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

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

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

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

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

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

[0203] A terminal according to one embodiment of the present disclosure includes a control circuit that determines, based on the configuration of a reference signal to be measured, at least one of the number and content of measurement values ​​to be included in a measurement report field for the reference signal, and a transmission circuit that transmits a signal including the measurement values ​​based on the determined at least one of the number and content.

[0204] In one embodiment of the present disclosure, the report field stores the measurement value for each of a plurality of resources that constitute one resource set for the reference signal.

[0205] In one embodiment of the present disclosure, the content of the measurement value included in the report field varies depending on the use of the resource set of the reference signal.

[0206] In one embodiment of the present disclosure, the report field stores a predetermined number of measurement values ​​among the measurement values ​​for a plurality of resources for the reference signal.

[0207] In one embodiment of the present disclosure, the report field stores the specified number of measurement values ​​among the measurement values ​​for each of the multiple resources included in multiple resource sets for the reference signal in descending or ascending order.

[0208] In one embodiment of the present disclosure, the report field stores an average value of the measurement values ​​for each of the specified number of resource sets among a plurality of resource sets for the reference signal.

[0209] In one embodiment of the present disclosure, the report field stores an average value of the measurement values ​​for each of the specified number of groups among a plurality of groups of resource sets for the reference signal.

[0210] A base station according to one embodiment of the present disclosure includes a control circuit that determines, based on the configuration of a reference signal measured in a terminal, at least one of the number and content of measurement values ​​to be included in a measurement report field for the reference signal, and a receiving circuit that receives a signal including the measurement values ​​based on the determined at least one of the number and content.

[0211] In a communication method according to one embodiment of the present disclosure, a terminal determines at least one of the number and content of measurement values ​​to be included in a measurement report field for a reference signal based on the configuration of the reference signal to be measured, and transmits a signal including the measurement values ​​based on the determined at least one of the number and content.

[0212] In a communication method according to one embodiment of the present disclosure, a base station determines at least one of the number and content of measurement values ​​to be included in a measurement report field for a reference signal based on the configuration of the reference signal measured in the terminal, and receives a signal including the measurement values ​​based on the determined at least one of the number and content.

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

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

[0215] 100 Base station 101, 201 Receiving unit 102, 202 Demodulation and decoding unit 103 Inter-terminal CLI determining unit 104 Scheduling unit 105, 205 Control information holding unit 106, 207 Data and control information generating unit 107, 208 Encoding and modulation unit 108, 209 Transmitting unit 200 Terminal 203 SRS receiving unit 204 Transmission control unit 206 SRS generating unit

Claims

1. A control circuit for performing measurements on a sounding reference signal (SRS) resource; a transmitter circuit configured to transmit uplink control information (UCI) including an identifier of each of the SRS resources and a result of the measurement of each of the SRS resources; A terminal equipped with:

2. The SRS resources include a first SRS resource included in a first SRS resource set and a second SRS resource included in a second SRS resource set. The terminal according to claim 1 .

3. The measurement result includes one or more differential values ​​for one RSRP (Reference Signal Received Power). The terminal according to claim 1 .

4. The UCI includes a plurality of identifiers of the SRS resources followed by the results of the measurements for each of the SRS resources. The terminal according to claim 1 .

5. The number of measurements included in the UCI is determined based on the configuration of the SRS resources to be measured. The terminal according to claim 1 .

6. If the number of measurements included in the UCI is greater than a predetermined number, the UCI includes the results of the predetermined number of measurements. The terminal according to claim 1 .

7. The method of claim 6, wherein the measurement for each of the SRS resources is performed to measure cross-link interference (CLI) between terminals. The terminal according to claim 1 .

8. A communication device comprising: performing measurements on a sounding reference signal (SRS) resource; transmitting uplink control information (UCI) including an identifier of each of the SRS resources and a result of the measurement for each of the SRS resources. Communication method.

9. The SRS resources include a first SRS resource included in a first SRS resource set and a second SRS resource included in a second SRS resource set. The communication method according to claim 8.

10. The measurement result includes one or more differential values ​​for one RSRP (Reference Signal Received Power). The communication method according to claim 8.

11. The UCI includes a plurality of identifiers of the SRS resources followed by the results of the measurements for each of the SRS resources. The communication method according to claim 8.

12. The number of measurements included in the UCI is determined based on the configuration of the SRS resources to be measured. The communication method according to claim 8.

13. If the number of measurements included in the UCI is greater than a predetermined number, the UCI includes the results of the predetermined number of measurements. The communication method according to claim 8.

14. The method of claim 13, wherein the measurement for each of the SRS resources is performed to measure cross-link interference (CLI) between terminals. The communication method according to claim 8.

15. An integrated circuit executed by a communications device, comprising: a control circuit for controlling the performance of measurements on a sounding reference signal (SRS) resource; a transmitter circuit configured to control transmission of uplink control information (UCI) including an identifier of each of the SRS resources and a result of the measurement of each of the SRS resources; An integrated circuit comprising: