Integrated circuit, communication device, communication method, and base station

Abstract

Integrated circuits, communication devices, communication methods, and base stations are provided. The integrated circuit includes: a receiving circuit that controls the reception of control information related to the setting of unlicensed frequency bands; and a decision circuit that controls the determination of content to be included in uplink control information, wherein the retransmission control information to be included in the uplink control information is determined based on the received control information.

Description

[0001] This application is a divisional application of the invention patent application filed on December 2, 2020, with application number 202080096486.7 and title "Terminal, Base Station, Communication Method and Integrated Circuit". Technical Field

[0002] This disclosure relates to terminals and communication methods. Background Technology

[0003] Within the 3rd Generation Partnership Project (3GPP), as a functional extension of 5G (5th Generation mobile communication systems), the physical layer specification for Release 16 (NR) (New Radio access technology) was finalized. NR, matching the fundamental requirements of enhanced Mobile Broadband (eMBB)—namely, high speed and high capacity—supports the implementation of Ultra Reliable and Low Latency Communication (URLLC) functionality (see, for example, Non-Patent Literature 1-4).

[0004] Existing technical documents

[0005] Non-patent literature

[0006] Non-patent literature 1: 3GPP TS 38.211 V16.0.0, "NR; Physical channels and modulation (Release 16)," December 2019

[0007] Non-patent document 2: 3GPP TS 38.212 V16.0.0, "NR; Multiplexing and channelcoding (Release 16)," December 2019

[0008] Non-patent literature 3: 3GPP TS 38.213 V16.0.0, "NR; Physical layer procedure for control (Release 16)," December 2019

[0009] Non-patent literature 4: 3GPP TS 38.214 V16.0.0, "NR; Physical layer procedures for data (Release 16)," December 2019 Summary of the Invention

[0010] However, the methods for transmitting uplink control information (e.g., UCI: Uplink Control Information) in unlicensed band domains have not been sufficiently studied.

[0011] The non-limiting embodiments of this disclosure contribute to providing a terminal and communication method capable of improving the transmission efficiency of uplink control information in an unlicensed band domain.

[0012] One embodiment of the terminal disclosed herein includes: a receiving circuit that receives parameters related to an unlicensed band domain; and a control circuit that determines information included in uplink control information based on the parameters.

[0013] It should be noted that these general or specific methods can be implemented by systems, devices, methods, integrated circuits, computer programs, or recording media, or by any combination of systems, devices, methods, integrated circuits, computer programs, and recording media.

[0014] According to one embodiment of this disclosure, the transmission efficiency of uplink control information in an unlicensed band can be improved.

[0015] Further advantages and effects of one embodiment of this disclosure will be illustrated by the specification and drawings. These advantages and / or effects are provided by the various embodiments and the features described in the specification and drawings, but not necessarily all of them need to be provided in order to obtain one or more of the same features. Attached Figure Description

[0016] Figure 1 This is a diagram illustrating an example of a frame-based equipment (FBE).

[0017] Figure 2 It is a block diagram representing a part of the terminal's structure.

[0018] Figure 3 This is a block diagram representing the structure of a base station.

[0019] Figure 4 It is a block diagram representing the structure of the terminal.

[0020] Figure 5 This is a timing diagram representing the actions of the base station and the terminal.

[0021] Figure 6 This is a diagram illustrating the exemplary architecture of a 3GPP NR system.

[0022] Figure 7 This is a schematic diagram illustrating the functional separation between NG-RAN and 5GC.

[0023] Figure 8 This is a timing diagram of the setup / reset process for a Radio Resource Control (RRC) connection.

[0024] Figure 9 This is a diagram illustrating the application scenarios of high-capacity high-speed communication (eMBB), massive machine-type communications (mMTC), and ultra-reliable and low-latency communications (URLLC).

[0025] Figure 10 This is a block diagram illustrating an exemplary 5G system architecture for non-roaming scenarios. Detailed Implementation

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

[0027] [Unlicensed frequency band]

[0028] In Release 16 NR, for example, in the unlicensed band (or also known as the unlicensed band domain), NR-Unlicensed (or NR-U) for communication using NR-based radio access methods was introduced.

[0029] In unlicensed frequency bands, for example, devices perform carrier sensing (e.g., Listen Before Talk (LBT)) to confirm whether other systems or terminals are using the radio channel before transmitting. In NR-U, for example, the decision to transmit is based on the results of LBT; therefore, the process of detecting the start of transmission of a series of downlink data (e.g., downlink burst (DL burst)) in the terminal (or user equipment (UE)) is under investigation. For example, in Release 16 NR, the detection of DL bursts based on PDCCH is under investigation.

[0030] Additionally, in Release 17 NR, research is underway on extending the use of Ultra Reliable and Low Latency Communications (URLLC) services in unlicensed frequency bands. In unlicensed frequency bands, interference from other systems may occur. For example, if an LBT failure (or LBT failure) occurs due to interference from other systems, a latency period until transmission is incurred, potentially increasing delays.

[0031] Therefore, the application of URLLC services is being explored in environments where interference from other systems is unlikely to occur (e.g., referred to as "controlled environments").

[0032] [Configured grant sent]

[0033] This describes the configuration license transmission (e.g., configuration license transmission in licensed bands) supported in Release 15 NR.

[0034] In the uplink data configuration permission transmission, there are, for example, "Configured grant type 1 transmission" and "Configured grant type 2 transmission".

[0035] In setting permission type 1 transmission, information such as the coding and modulation scheme (Modulation and Coding Scheme (MCS)), radio resource allocation (e.g., allocation of time or frequency resources), transmission timing, and the number of Hybrid Automatic Repeat Request (HARQ) processes (e.g., referred to as permission setting information) can be set (in other words, notified or indicated) to the terminal via terminal-specific higher-layer signals. For example, when uplink data (e.g., Physical Uplink Shared Channel (PUSCH)) is generated, the terminal can transmit uplink data based on the pre-set MCS and radio resource permission setting information, even without a UL grant (e.g., dynamic uplink data scheduling information) from the downlink control channel (e.g., Physical Downlink Control Channel (PDCCH)) from the base station (e.g., also called gNB).

[0036] Additionally, higher-layer signals are also known as Radio Resource Control (RRC) signals, higher-layer signaling, or higher-layer parameters.

[0037] Furthermore, in Type 2 transmission, the transmission permission is activated or released, for example, via PDCCH from the base station. In Type 2 transmission, information such as transmission timing and HARQ process count can be set via terminal-specific higher-layer signals, similar to Type 1 transmission. On the other hand, in Type 2 transmission, information such as MCS and radio resource allocation information is set via downlink control information (DCI) activation. For example, when uplink data is generated, the terminal can semi-permanently (in other words, statically or semi-statically) use the transmission permission settings such as MCS and radio resources set by higher-layer signals and DCI activation (in other words, without UL permission) to transmit uplink data (e.g., PUSCH).

[0038] Additionally, in Release 15 NR, UL licensing is used, for example, in retransmission control for configured permitted transmission. For instance, UL licensing controls the MCS of uplink data used for retransmission and radio resource allocation information.

[0039] Furthermore, as a non-limiting example, the HARQ process number (or HARQ process ID) used in a configuration-permitted transmission can also be uniquely determined based on the slot number of the transmitted PUSCH (in other words, the timing of the PUSCH transmission). For example, the PUSCH transmitted in a configuration-permitted transmission can have the same processing as the initial transmitted signal, and the Redundancy Version (RV) can also be 0.

[0040] [Setting up permission to send in unlicensed frequency bands]

[0041] In the configuration grant transmission in NR-U (NR in the unlicensed band), for example, part of the parameters for PUSCH decoding such as HARQ process number, New Data Indicator (NDI) and RV (e.g., parameters related to retransmission control) is notified from the terminal to the base station through uplink control information for configuration grant transmission (e.g., called Configured grant Uplink Control Information (CG-UCI)).

[0042] Regarding CG-UCI, for example, it can be transmitted using a portion of the radio resources allocated to PUSCH (or, sometimes also called CG-PUSCH) at the same transmission timing (e.g., the same time slot) as PUSCH. In other words, CG-UCI can be multiplexed with CG-PUSCH.

[0043] Here, the reason for explicitly notifying the HARQ process number using CG-UCI in NR-U is as follows. For example, in NR-U, the transmission of PUSCH is not limited to the result of LBT. Therefore, for example, in a method that determines the HARQ process number in association with the transmission timing of PUSCH, such as licensed frequency bands, it may not be possible to flexibly utilize the HARQ process based on whether the PUSCH was actually transmitted. Therefore, for example, it is possible to use CG-UCI, which is transmitted along with CG-PUSCH, to notify the HARQ process number.

[0044] Additionally, NR-U supports, for example, the terminal retransmitting using radio resources configured to be permitted, without UL permission, upon receiving NACK or upon timer expiration. Therefore, information indicating the initial transmission or retransmission status (e.g., New Data Indicator (NDI)) and the RV in the PUSCH applied during retransmission are transmitted via CG-UCI.

[0045] In NR-U, for example, HARQ-ACK feedback for CG-PUSCH can be explicitly notified to the UE from the gNB via information called DFI (Downlink Feedback Indicator). For example, for CG-PUSCH, the HARQ process number is notified via CG-UCI. Therefore, for example, there might be a situation where, when the gNB fails to receive CG-UCI, it cannot determine which HARQ process's data was transmitted, and therefore cannot specify the HARQ process to instruct PUSCH retransmission. Thus, the gNB can, for example, notify (in other words, provide feedback) HARQ-ACK feedback information for all HARQ processes. Furthermore, by aggregating HARQ-ACK feedback information for multiple PUSCHs and providing it to the terminal, the gNB can reduce LBT-based overhead and improve the efficiency of retransmission control.

[0046] Furthermore, in DFI-based retransmission control, the MCS of the PUSCH used for retransmission and the radio resource allocation can be the same as those used in the initial transmission. Additionally, the DFI can be transmitted, for example, in the PDCCH. Moreover, in addition to HARQ-ACK, the DFI can also contain other parameters such as transmit power control (TPC) commands.

[0047] Frame-based equipment (FBE)

[0048] FBE is one of the channel access methods in NR-U. FBE is also known as semi-static channel occupancy. Figure 1 This is a diagram representing an example of FBE.

[0049] In FBE, the gNB can determine the channel occupancy time (COT) by performing a Category 2 LBT (e.g., a fixed LBT for which carrier sensing is performed) at the beginning of a period known as the Fixed Frame Period (FFP). The UE can obtain the COT by performing a Category 2 LBT within the gNB's COT, or a Category 1 LBT (e.g., an LBT without carrier sensing).

[0050] Furthermore, in load-based equipment (LBE) (not shown) that serves as another channel access method, for example, the UE can attempt to acquire COT at any time. On the other hand, in LBE, there may be cases where a Category 4 LBT (e.g., an LBT with a random carrier sensing period) can be acquired by performing a longer LBT period compared to a Category 2 LBT in FBE.

[0051] Thus, in FBE, compared to LBE, UE can achieve COT within a shorter LBT period. On the other hand, in FBE, for example, as... Figure 1 As shown, the study is investigating a period during which neither the gNB nor the UE can transmit (in other words, cannot obtain COT) (e.g., also known as the idle period).

[0052] The above explains FBE

[0053] However, methods for maintaining or improving the reliability of uplink signals (e.g., uplink control information or uplink data) in unlicensed frequency bands have not been sufficiently discussed. Furthermore, unlicensed frequency bands, such as a portion of CG-PUSCH, may contain CG-UCI, thus potentially increasing the amount of resources used in CG-PUSCH transmissions compared to licensed frequency bands.

[0054] (Implementation Method 1)

[0055] [Overview of Communication Systems]

[0056] One aspect of the communication system disclosed herein may include, for example, a communication system that can include... Figure 3 The base station 100 shown (e.g., gNB) and Figure 2 and Figure 4 The terminal 200 (e.g., UE) shown is also shown.

[0057] Figure 2This is a block diagram illustrating a structural example of a terminal 200 according to one embodiment of the present disclosure. Figure 3 In the terminal 200 shown, the receiving unit 201 receives parameters related to the unlicensed band (e.g., unlicensed frequency band). The transmitting control unit 204 determines the information to be included in the uplink control information (e.g., CG-UCI) based on the parameters.

[0058] [Base station structure]

[0059] Figure 3 This is a block diagram illustrating a structural example of a base station 100 according to one embodiment of the present disclosure. Figure 3 In this system, base station 100 includes a receiving unit 101, a separating unit 102, a control information demodulation / decoding unit 103, a data demodulation / decoding unit 104, a scheduling unit 105, a control information holding unit 106, a data / control information generation unit 107, an encoding / modulation unit 108, and a transmitting unit 109.

[0060] The receiving unit 101 receives the signal sent from the terminal 200 via the antenna, performs receiving processing such as down-conversion or A / D conversion on the received signal, and outputs the received signal after receiving processing to the separation unit 102.

[0061] Separation unit 102, for example, based on information input from scheduling unit 105 (e.g., CG-UCI setting information), separates the received signal input from receiving unit 101 into a control information portion and a data portion. Separation unit 102, for example, outputs the control information portion to control information demodulation / decoding unit 103 and the data portion to data demodulation / decoding unit 104. Furthermore, the control information may, for example, include CG-UCI. Additionally, for example, the received signal may sometimes not contain control information.

[0062] The control information demodulation / decoding unit 103 demodulates and decodes the received signal (e.g., the control information portion) input from the separation unit 102, and outputs the decoding result (e.g., CG-UCI) to the data demodulation / decoding unit 104. Alternatively, if the received signal does not contain CG-UCI, the control information demodulation / decoding unit 103 may not output a signal to the data demodulation / decoding unit 104.

[0063] The data demodulation / decoding unit 104 demodulates and decodes the data portion input from the separation unit 102 based on the CG-UCI input from the control information demodulation / decoding unit 103 and the scheduling information input from the scheduling unit 105, and outputs the decoding result to the scheduling unit 105.

[0064] The scheduling unit 105 determines, for example, the parameters and their size (e.g., number of bits) included in the CG-UCI based on the control information (e.g., setting permission setting information) input from the control information holding unit 106. The scheduling unit 105 outputs the determined information (e.g., referred to as CG-UCI setting information) to the separation unit 102 and the data demodulation / decoding unit 104.

[0065] Furthermore, for example, when the scheduling unit 105 performs retransmission control based on explicit HARQ-ACK information according to the data decoding result input from the data demodulation / decoding unit 104, it instructs the data / control information generation unit 107 to generate HARQ-ACK feedback information. Additionally, when sending signaling information, the scheduling unit 105 instructs the data / control information generation unit 107 to generate signaling information. Furthermore, the scheduling unit 105 may, for example, instruct the data / control information generation unit 107 to generate data or control information.

[0066] The control information holding unit 106 holds, for example, configuration permission settings information (e.g., MCS and radio resource allocation information) for each terminal 200. The control information holding unit 106 may also output the held information to various structural units of the base station 100 (e.g., scheduling unit 105) as needed.

[0067] The data / control information generation unit 107 generates data or control information according to instructions from the scheduling unit 105, and outputs a signal containing the generated data or control information to the encoding / modulation unit 108. For example, the data / control information generation unit 107 may also generate control information based on generation instructions for HARQ-ACK feedback information or signaling information input from the scheduling unit 105.

[0068] The encoding / modulation unit 108 encodes and modulates the signal input from the data / control information generation unit 107, and outputs the modulated signal (symbol sequence) to the transmission unit 109.

[0069] The transmitting unit 109 performs D / A conversion, up-conversion, or amplification on the signal input from the encoding / modulation unit 108, and transmits the wireless signal obtained through the transmission process to the terminal 200 from the antenna.

[0070] [Terminal Structure]

[0071] Figure 4 This is a block diagram illustrating a structural example of a terminal 200 according to one embodiment of the present disclosure. Figure 4In the terminal 200, there are receiving unit 201, demodulation / decoding unit 202, control information holding unit 203, transmission control unit 204, data generation unit 205, control information generation unit 206, encoding / modulation / multiplexing unit 207, and transmission unit 208.

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

[0073] The demodulation / decoding unit 202 demodulates and decodes, for example, the data or control information contained in the received signal input from the receiving unit 201, and outputs the decoding result to the transmission control unit 204. The control information may, for example, include HARQ-ACK feedback information. Furthermore, for example, the demodulation / decoding unit 202 outputs the signaling information contained in the decoding result to the control information holding unit 203.

[0074] The control information holding unit 203 holds, for example, the signaling information input from the demodulation / decoding unit 202 (e.g., setting permission setting information), and outputs the held information to the respective structural units (e.g., the transmission control unit 204) as needed.

[0075] The transmitting control unit 204 determines the parameters or size (e.g., number of bits) included in the CG-UCI, for example, based on the decoding result of the control information or data input from the demodulation / decoding unit 202 and the setting permission setting information input from the control information holding unit 203. Based on the determined information, the transmitting control unit 204 instructs the control information generation unit 206 to generate control information (e.g., CG-UCI). Additionally, the transmitting control unit 204 instructs the data generation unit 205 to generate data (e.g., CG-PUSCH).

[0076] The data generation unit 205 generates transmission data (e.g., CG-PUSCH) based on a data generation instruction input from the transmission control unit 204, and outputs it to the encoding / modulation / multiplexing unit 207.

[0077] The control information generation unit 206 generates control information (e.g., CG-UCI) based on a control information generation instruction input from the transmission control unit 204, and outputs it to the encoding / modulation / multiplexing unit 207.

[0078] The encoding / modulation / multiplexing unit 207 encodes and modulates, for example, the transmit data input from the data generation unit 205 and the control information input from the control information generation unit 206. Additionally, the encoding / modulation / multiplexing unit 207 multiplexes the data and control information and outputs it to the transmission unit 208.

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

[0080] [Actions of base station 100 and terminal 200]

[0081] Explain the operation examples in the base station 100 and terminal 200 with the above structure.

[0082] Figure 5 This is a timing diagram representing the actions of base station 100 and terminal 200.

[0083] Base station 100 may, for example, determine the configuration permission settings (ST101) for terminal 200. The configuration permission settings may also include information related to MCS, radio resource allocation, transmission timing, and HARQ process.

[0084] Base station 100 sends control information (ST102) to terminal 200. For example, the control information may include setting permission settings.

[0085] Base station 100 determines the CG-UCI setting of terminal 200, for example, based on setting permission setting information (ST103). Additionally, terminal 200 determines the CG-UCI setting, for example, based on setting permission setting information sent from base station 100 (ST104). For example, base station 100 and terminal 200 may also determine the information contained in the CG-UCI (e.g., also called CG-UCI parameters) based on parameters related to unlicensed frequency bands (e.g., information related to setting permission setting information or unlicensed frequency bands). In other words, base station 100 and terminal 200 can determine information not included in the CG-UCI. For example, base station 100 and terminal 200 may also determine the size of the CG-UCI in the control of the information contained in the CG-UCI. For example, the CG-UCI setting may include the setting of a mode related to the CG-UCI parameters (an example described later).

[0086] Terminal 200, for example, generates CG-UCI (ST105) based on CG-UCI settings, and sends the generated CG-UCI to base station 100 (ST106).

[0087] Base station 100, for example, based on the CG-UCI setting of terminal 200, separates the CG-UCI (ST107) from the received signal from terminal 200.

[0088] [Method for determining CG-UCI parameters]

[0089] Describe an example of a method for determining CG-UCI parameters in a base station 100 (e.g., scheduling unit 105) and a terminal 200 (e.g., transmission control unit 204) (e.g., Figure 5 processing of ST103 and ST104 in

[0090] In an unlicensed band, the CG-UCI parameters included in CG-UCI can be determined according to a mode, for example. In the mode, there are, for example, a "reduction mode" that reduces the number of bits of CG-UCI and a "non-reduction mode" that does not reduce the number of bits of CG-UCI. Examples of methods for determining the mode are described later.

[0091] In addition, the "number of bits" can also be replaced with the "bit size" or "bit length", for example. In addition, the "mode" can also be replaced with the "method" or "type", for example.

[0092] In the reduction mode of CG-UCI, at least a part of the CG-UCI parameters is reduced, for example. Among the reduced parameters, there can be the following parameters (e.g., HARQ process number or retransmission parameter), for example.

[0093] Hereinafter, the case where information related to the HARQ process number is not included in CG-UCI in the reduction mode is described.

[0094] In the reduction mode, information related to the HARQ process number may not be included in CG-UCI, for example.

[0095] On the other hand, in the reduction mode, the HARQ process number can be determined (or calculated) based on the transmission timing of CG-PUSCH, for example. Examples of calculation methods for the HARQ process number are as follows.

[0096] <Calculation method 1 of HARQ process number>

[0097] The HARQ process number is calculated based on the system frame number (e.g., SFN: System framenumber) and symbol number when CG-PUSCH is transmitted, for example. In other words, in calculation method 1, the HARQ process number can be determined by the same method as in a licensed band (e.g., licensed band).

[0098] <Calculation method of HARQ process number

[0099] The HARQ process number can be calculated according to the relative timing within the gNB COT, for example.

[0100] For example, the HARQ process number can be determined based on the beginning of the gNB COT (or a specific timer within the COT) using the following method.

[0101] Decision Method 1:

[0102] In method 1, for example, the HARQ process number of the same pattern can be set across multiple COTs.

[0103] For example, the HARQ process ID can be defined as follows.

[0104]

[0105] Here, CURRENT_symbol represents the number of symbols starting from the beginning of the COT, periodicity represents the transmission period for the set permission, and nrofHARQ-Processes represents the number of HARQ processes allocated to the set permission. Additionally, the function floor(x) represents the floor function that returns the largest integer less than or equal to x.

[0106] Decision Method 2:

[0107] In method 2, for example, HARQ process numbers for different modes can be set among multiple COTs.

[0108] For example, the HARQ process ID can be defined as follows.

[0109]

[0110] Here, n represents the value that is notified to the UE from the gNB for each COT. Additionally, CURRENT_symbol, periodicity, and nrofHARQ-Processes are the same as determined by method 1.

[0111] For example, decision method 1 may not require the following processing, such as decision method 2, which involves pre-determining the signaling or mode-changing method for applying different HARQ process numbers to each COT, and the processing for cognition between the shared base station 100 (e.g., gNB) and the terminal 200 (e.g., UE). Therefore, compared to decision method 2, decision method 1 has advantages such as simplifying the processing or minimizing cognitive biases between the gNB and the UE.

[0112] On the other hand, in decision method 2, even when the COT length is short, the cycle is long, or the number of HARQ processes allocated to the specified license is large, and all HARQ processes allocated to the specified license are not allocated in one COT, other HARQ processes can still be used in another COT. Therefore, decision method 2 has the advantage of being able to use more HARQ processes compared to decision method 1.

[0113] Alternatively, for example, the decision method (method 1) or decision method 2 can be determined based on at least one of the following: COT length (e.g., maximum COT length), periodicity, or a set number of permitted HARQ processes. For instance, decision method 1 can be applied when the number of HARQ processes is below a threshold, while decision method 2 can be applied when the number of HARQ processes exceeds the threshold. Thus, for example, it is possible to select a decision method corresponding to the maximum COT length, periodicity, or number of HARQ processes. Furthermore, the threshold can be, for example, based on the maximum COT length.

[0114] The above explains method 2 for calculating the HARQ process number.

[0115] In this way, by reducing the HARQ process number in the reduction mode, the number of bits in CG-UCI can be reduced, which can improve the reliability of CG-UCI compared with the non-reduction mode, for example, when using the same amount of resources.

[0116] The above explains the situation where information related to the HARQ process number is not included in the CG-UCI in the reduction mode.

[0117] On the other hand, in non-reduction mode, the HARQ process number is determined by, for example, terminal 200 and notified to base station 100 via CG-UCI. Therefore, for example, in environments where LBT failures may occur and PUSCH transmission in the configured permitted resources (hereinafter referred to as CG resources) cannot be performed in terminal 200, HARQ can be used effectively by having terminal 200 determine the HARQ process number and notify it via CG-UCI.

[0118] Next, we will explain the situation where retransmission parameters such as NDI and RV are not included in CG-UCI in the reduction mode.

[0119] In reduction modes, such as CG-UCI, NDI and RV may not be included.

[0120] Additionally, in reduced-down mode, for example, retransmission on CG resources that use HARQ-ACK feedback information (e.g., DFI) or retransmission timers may not be supported, but retransmission based on UL permission may be supported. For example, in URLLC, by transmitting with high reliability, the probability of retransmission is sometimes low compared to other service types. Furthermore, in environments where LBT failures are unlikely, HARQ-ACK feedback is less likely to be hindered. In such cases, the necessity for aggregated HARQ-ACK feedback across multiple HARQ processes via DFI, or for using retransmission timers to control retransmission, is lower. Therefore, for example, in the case of URLLC services, or in environments where LBT failures are unlikely, in reduced-down mode, retransmission parameters are not included in the CG-UCI, and retransmission on CG resources that use DFI or retransmission timers is not supported.

[0121] In cases where retransmission of CG resources is not supported, sending CG resources is not considered a retransmission, but rather an initial transmission. During the initial transmission, for example, NDI could be toggled and treated as RV=0. Therefore, NDI and RV can be absent.

[0122] Therefore, in the reduction mode, by reducing the retransmission parameters, the number of bits in CG-UCI can be reduced, thus improving CG-UCI reliability compared to the non-reduction mode, for example, when using the same amount of resources. Furthermore, for example, there may be no DFI used for retransmission, thus reducing the overhead of control information in the downlink.

[0123] The above explains the situation where information related to retransmission parameters is not included in the CG-UCI in the reduction mode.

[0124] On the other hand, in non-reduction mode, retransmission on CG resources using DFI or retransmission timers can also be supported. In non-reduction mode, retransmission parameters such as NDI and RV are determined by the terminal 200 and notified to the base station 100 via CG-UCI. Thus, in non-reduction mode, such as in environments where LBT failures may occur, retransmission control using CG resources can be performed, thereby increasing the retransmission opportunity and improving the efficiency of such retransmission control.

[0125] Thus, in the reduction mode, by reducing the number of CG-UCI bits, for example, compared to not reducing the number of CG-UCI bits, it is possible to achieve high reliability of CG-UCI (e.g., in the case of transmitting CG-UCI) and CG-PUSCH transmission and reception with fewer resources. Furthermore, in the non-reduction mode, for example, in cases where LBT failures may occur due to interference from other systems, retransmission control that improves the efficiency of the HARQ process can be implemented. Therefore, by switching between reduction and non-reduction modes, control can be used separately to improve reliability by reducing PUSCH resources and to improve resistance to LBT failures. Therefore, for example, base station 100 and terminal 200 can control CG-UCI according to the radio transmission environment (or conditions) between base station 100 and terminal 200.

[0126] Additionally, for example, in reduction mode, at least one of the HARQ process number and retransmission parameters mentioned above can be reduced. Alternatively, in reduction mode, all CG parameters included in the CG-UCI can also be reduced. In this case, terminal 200 may not send the CG-UCI, so transmission and reception processing related to the CG-UCI may not be performed.

[0127] Furthermore, this section describes the case where at least one of the HARQ process number and retransmission parameters is reduced in the reduction mode. However, the parameter to be reduced can also be a parameter different from the HARQ process number and retransmission parameters. For example, by reducing a parameter different from the HARQ process number and retransmission parameters, the coding rate of CG-UCI can be reduced, and therefore, as described above, the coding rate of CG-UCI can be improved.

[0128] Furthermore, in the reduction mode, the deletion is not limited to the removal of the parameter itself; for example, the number of bits for the parameter can also be reduced. For instance, instead of setting the number of bits for RV to 2 bits in non-reduction mode, the number of bits for RV can be set to 1 bit in reduction mode. Thus, for example, when the probability of retransmission is low and only two modes of RV (e.g., RV=0, 3, etc.) are needed, it is possible to retain the notification of RV based on CG-UCI and reduce the number of bits for CG-UCI.

[0129] The above explains how the CG-UCI parameters are determined.

[0130] Next, an example of a method for determining patterns will be given.

[0131] For example, terminal 200 can determine the mode based on parameters related to the unlicensed frequency band (in other words, information contained in the CG-UCI, or information not contained in the CG-UCI). Among the parameters related to the unlicensed frequency band, there may be parameters that are set or notified to terminal 200 in the unlicensed frequency band, or parameters related to the wireless transmission environment of terminal 200 in the unlicensed frequency band.

[0132] <Decision Method 1>

[0133] In method 1, the mode can be explicitly set, for example, by semi-static signaling such as higher-layer signals (e.g., RRC signals).

[0134] For example, parameters can be appended to semi-static signaling to notify either the slash mode or the non-slash mode.

[0135] In addition, semi-static signaling includes, for example, cell-specific signaling and UE-specific signaling.

[0136] Community-specific signaling:

[0137] For example, imagine that the URLLC service is used in a controlled environment.

[0138] Furthermore, it is conceivable that the status of a controlled environment will not change based on local areas. For example, it is conceivable to determine whether an environment is controlled on a cell-by-cell basis. Therefore, for example, the mode can be determined on a cell-by-cell basis based on whether an environment is controlled.

[0139] Therefore, by using notifications based on cell-specific signaling patterns, such as enabling common processing of terminals 200 within a cell, the control and processing of base station 100 (e.g., gNB) can be simplified.

[0140] UE-specific signaling:

[0141] For example, notifications based on UE-specific signaling patterns are valid when LBT failure occurs in a subset of multiple UEs, or when URLLC service is applied in a subset of multiple UEs.

[0142] The mode setting based on the UE-specific signaling can also be associated with a configuration grant setting (e.g., also known as a configured grant configuration). For example, a mode can be set for each configuration grant setting. For example, between base station 100 (gNB) and terminal 200 (UE), CG-UCI and DFI can be performed by ensuring that the recognition of the mode of each terminal 200 (e.g., UE) or each configuration grant setting is consistent.

[0143] In this way, by notifying users of the mode based on UE-specific signaling, it is possible to set a mode suitable for each UE or each setting permission setting, such as in the process of reducing PUSCH resources (in other words, reduction mode) and in the process of envisioning the occurrence of LBT failure (in other words, non-reduction mode).

[0144] The above explains cell-specific signaling and UE-specific signaling.

[0145] Thus, in decision method 1, the mode is explicitly notified, so that, for example, based on the radio conditions between base station 100 and terminal 200, base station 100 can appropriately set one of the following: a process that reduces PUSCH resources (e.g., reduction mode) or a process that anticipates the occurrence of LBT failure (e.g., non-reduction mode).

[0146] Furthermore, while method 1 describes situations where the mode is explicitly notified, it is not limited to this. For example, base station 100 may notify terminal 200 of signaling indicating whether it is a controlled environment, and terminal 200 may also set (e.g., change) the mode in association with that signaling. For example, in a configured environment (e.g., an environment without interference from other systems), a reduction mode may be set, while in an environment that is not a configured environment (e.g., an environment where there may be interference from other systems), a non-reduction mode may be set. For example, if the signaling indicating whether it is a controlled environment is also used for other processing different from mode setting, the signaling indicating whether it is a controlled environment can be shared, reducing signaling overhead.

[0147] Decision Method

[0148] In method 2, the mode can be set, for example, through dynamic signaling. Dynamic signaling includes, for example, a PDCCH for activation or reactivation, as present in license type 2.

[0149] The notification method in decision method 2 is explained below.

[0150] Notification Method 1:

[0151] The mode can be explicitly notified, for example, through parameters included in the PDCCH. For instance, a 1-bit parameter can also be appended to the PDCCH. Base station 100 can, for example, notify terminal 200 of a 1-bit parameter representing either the reduction mode or the non-reduction mode.

[0152] Notification Method 2

[0153] The mode can be associated with a DCI format, for example. For instance, terminal 200 can set either a reduction mode or a non-reduction mode based on the DCI format.

[0154] For example, DCI format 0_2 could be associated with a reduction mode, while DCI formats 0_0 and 0_1 could be associated with a non-reduction mode. For instance, it is envisioned that DCI format 0_2 is used for URLLC services. Furthermore, regarding URLLC services, it is envisioned for use in environments where LBT failures are unlikely (e.g., environments free from interference from other systems, such as controlled environments). Therefore, it is envisioned that when DCI format 0_2 is used, the environment is unlikely to cause LBT failures, and a reduction mode is set.

[0155] Furthermore, in notification method 2, compared to notification method 1, no additional parameters are required in the PDCCH, thus reducing signaling overhead. On the other hand, notification method 1 is effective in switching between reduced and non-reduced modes without relying on the DCI format.

[0156] Thus, in decision method 2, the mode can be changed, for example, via PDCCH, thereby enabling more dynamic mode changes compared to methods that use semi-static signaling, such as decision method 1.

[0157] Decision Method

[0158] In decision method 3, the mode can be set (in other words, changed) based on the priority of the permission setting (in other words, the parameter related to the priority).

[0159] For example, in setting permissions, it is possible to set the priority for each permission, and the priority is set to semi-static. For example, in Release 16 NR, the priority is set to High or Low. In addition, the priority (e.g., High or Low) can be set to terminal 200, for example, via a higher-level signal (as an example, the priority (e.g., High or Low) in configuredGrantConfig).

[0160] When the priority is high, for example, it is conceivable to apply URLLC services. Furthermore, as mentioned above, the use of URLLC services is envisioned, for example, in environments where LBT failure is unlikely (e.g., environments free from interference from other systems, such as controlled environments). Therefore, for example, terminal 200 can set a reduction mode when the priority is high and a non-reduction mode when the priority is low.

[0161] According to decision method 3, since mode switching can be performed without additional signaling, signaling overhead can be reduced.

[0162] Decision Method

[0163] In method 4, the mode can be set (in other words, changed) based on parameters related to the channel access method (e.g., FBE or LBE).

[0164] The channel access mode can be set to terminal 200, for example, via a higher-layer signal (ChannelAccessMode-r16, for example, semi-static or dynamic)).

[0165] For example, in FBE mode, there may be situations where effective operation is impossible if a system that could potentially interfere is present. Furthermore, in FBE mode, for example, since the timing for the start of transmission is predetermined, terminal 200 may wait to transmit until the transmission start timing even without interference from other systems. Therefore, when operating in FBE mode, it is conceivable that there may be situations where other systems can be considered non-existent as interference.

[0166] On the other hand, compared to FBE mode, LBE mode is easier to coexist with other systems, for example. Therefore, when operating in LBE mode, interference from other systems can be anticipated.

[0167] Therefore, for example, terminal 200 can set a reduction mode when FBE mode is set, and an LBE mode when LBE mode is set.

[0168] According to decision method 3, since mode switching can be performed without additional signaling, signaling overhead can be reduced.

[0169] <Decision Method 5>

[0170] In method 5, the schema can be set (in other words, changed) based on parameters related to the MCS. Parameters related to the MCS can be, for example, an MCS table or an MCS index.

[0171] The following is an example of pattern determination in method 5.

[0172] Method 1

[0173] The pattern can be determined, for example, based on the MC table of GC-PUSCH.

[0174] In PUSCH transmission, for example, by having the terminal 200 (e.g., UE) select and instruct the base station 100 (e.g., gNB) to use the MCS index in the transmission, it is possible to select the modulation scheme and coding rate corresponding to the communication quality. On the other hand, in NR, use cases such as URLLC, which require very high reliability compared to other services, are also envisioned. Therefore, in NR, it is specified, for example, that instead of a single MCS table supporting multiple use cases, the MCS table used can be changed from multiple MCS tables depending on the use case or the service corresponding to the transmitted data.

[0175] In addition, the MCS form used can be set (in other words, notified) to terminal 200 via, for example, RRC signaling, DCI format, or Radio Network Temporary Identifier (RNTI).

[0176] Terminal 200 can, for example, set a reduction mode when using a high-reliability MCS table (in other words, an MCS table that supports a lower coding rate than a normal MCS table), and set a non-reduction mode when using a normal MCS table.

[0177] This is because, when using the MCS table for high reliability, the scenario of sending and receiving data via URLLC service is considered, and it is assumed that LBT (Low Bit Blowout) is unlikely to occur.

[0178] Therefore, mode switching can be performed without additional signaling, thus reducing signaling overhead.

[0179] Method 2:

[0180] The pattern can be determined, for example, based on the MC index of GC-PUSCH.

[0181] Additionally, the MCS index used can be set (in other words, notified) to terminal 200 via RRC signaling or PDCCH, for example.

[0182] Modulation schemes and coding rates are determined, for example, based on the MCS index. For instance, a lower MCS index allows for more reliable combinations of modulation schemes and coding rates. For example, by associating the use of an MCS index lower than a threshold with actions such as sending and receiving data for URLLC services (e.g., throttling), an environment less prone to LBT failures can be considered when using an MCS index lower than a threshold.

[0183] Therefore, terminal 200 can, for example, set a throttling mode when the MCS index is low (e.g., below the threshold) and a non-throttling mode when the MCS index is high (e.g., above the threshold).

[0184] Alternatively, the threshold can be notified (in other words, set) to terminal 200 via signaling, or it can be specified in the standard. Furthermore, the threshold can also be set for each MCS table, for example.

[0185] Therefore, mode switching can be performed without additional signaling, thus reducing signaling overhead.

[0186] In addition, as an example, the comparison between the MCS index and the threshold is illustrated, but the terminal 200 may also set the mode based on the comparison between the coding rate corresponding to the MCS index and the threshold.

[0187] Alternatively, methods 1 and 2 can be combined. For example, even when using a high-reliability MCS table, the coding rate may increase with a higher MCS index, so combining these methods allows for more granular control.

[0188] The above explains decision-making methods 1 through 5.

[0189] In this embodiment, the terminal 200 controls the information contained in the CG-UCI (e.g., uplink control information related to resource allocation set for the terminal 200) based on parameters related to the unlicensed frequency band.

[0190] Through this control, for example, the size (e.g., number of bits) of the CG-UCI can vary depending on the wireless transmission environment between base station 100 and terminal 200. For example, by using a reduction mode, the size of the CG-UCI can be reduced, and the reliability of the CG-UCI can be improved. On the other hand, by using a non-reduction mode (e.g., maintaining the size of the CG-UCI), the reliability of the CG-UCI can be maintained by considering LBT failure control. Therefore, according to this embodiment, in unlicensed frequency bands (in other words, unlicensed band domains), the reliability of uplink signals can be maintained or improved, and the transmission efficiency of uplink signals can be improved.

[0191] The embodiments of this disclosure have been described above.

[0192] (Other implementation methods)

[0193] In the above embodiments, when applying the reduction mode, other parameters (e.g., parameters used in URLLC) may be included instead of parameter reduction. In other words, the bits of the reduction amount of a certain parameter can be allocated to other parameters. For example, as another parameter, when using the same resources (e.g., at least one of time domain, frequency domain, and DMRS settings) in different UEs or different configuration permission settings, information for easy separation during reception in the gNB can be included. This information may be, for example, the UE ID or the configuration permission setting ID. By adding other parameters, for example, when the base station 100 uses the same resources in different UEs or different configuration permission settings, the signal separation accuracy can be improved, and thus the reliability can be improved.

[0194] Furthermore, in the above embodiments, additional parameters may be included in the CG-UCI during the non-reduction mode. These additional parameters may include, for example, the UE ID or configuration permission setting ID as described above. For instance, when sufficient resources exist for the CG-UCI, by selecting the non-reduction mode and considering the additional parameters, such as when base station 100 uses the same resources for different UEs or different configuration permission settings, the signal separation accuracy can be improved, thereby enhancing reliability.

[0195] Furthermore, in the above embodiments, the reduction of the number of bits in CG-UCI is not limited to the method of switching the above mode by, for example, the processing method when high reliability is required and the processing method when high reliability is not required.

[0196] Furthermore, in the above embodiments, the scenario described involves setting the mode based on parameters such as information explicitly representing the mode, setting the permission priority, channel access method, or MCS index (or MCS table) notified to the terminal 200 from the base station 100. However, the parameters used in setting the mode are not limited to these. For example, other parameters that can be set in URLLC services, or other parameters that can be set in an environment where LBT failure (in other words, interference from other systems) is assumed to occur (or, in an unassigned environment).

[0197] Furthermore, in the above embodiments, the uplink data channel is not limited to PUSCH, but can also be a control channel with other names.

[0198] In addition, the above-described embodiments can also be used in combination.

[0199] <5G NR System Architecture and Protocol Stack>

[0200] To realize the next version of fifth-generation mobile phone technology (also known simply as "5G"), which includes the development of a new radio access technology (NR) operating in the frequency range up to 100 GHz, 3GPP is continuing its work. The first version of the 5G standard was completed at the end of 2017, thus enabling the transition to the trial production of terminals (e.g., smartphones) according to the 5G NR standard and commercial deployment.

[0201] For example, the overall system architecture envisions a gNB-RAN (Next Generation Radio Access Network). The gNB provides UE-side termination for the NG radio access user plane (SDAP (Service Data Adaptation Protocol) / PDCP (Packet Data Convergence Protocol) / RLC (Radio Link Control) / MAC / PHY (Physical Layer)) and control plane (RRC) protocols. gNBs are interconnected via the Xn interface. Additionally, gNBs are connected to the NGC (Next Generation Core) via the Next Generation (NG) interface, and more specifically, to the AMF (Access and Mobility Management Function) (e.g., a specific core entity implementing the AMF) via the NG-C interface, and to the UPF (User Plane Function) (e.g., a specific core entity implementing the UPF) via the NG-U interface. Figure 6 This refers to the NG-RAN architecture (e.g., refer to 3GPP TS 38.300 v15.6.0, section 4).

[0202] The user plane protocol stack for NR (e.g., refer to 3GPP TS 38.300, section 4.4.1) for the gNB includes the PDCP (Packet Data Convergence Protocol (refer to TS 38.300, section 6.4)) sublayer, RLC (Radio Link Control (refer to TS 38.300, section 6.3)) sublayer, and MAC (Media Access Control (refer to TS 38.300, section 6.2)) sublayer, which terminates on the network side of the gNB. Additionally, a new Access Stratum (AS) sublayer (SDAP: Service Data Adaptation Protocol) has been incorporated into PDCP (e.g., refer to 3GPP TS 38.300, section 6.5). Furthermore, a control plane protocol stack is defined for NR (e.g., refer to TS 38.300, section 4.4.2). A summary of Layer 2 functionality is described in Section 6 of TS 38.300. The functions of the PDCP sublayer, RLC sublayer, and MAC sublayer are listed in Sections 6.4, 6.3, and 6.2 of TS 38.300, respectively. The functions of the RRC layer are listed in Section 7 of TS 38.300.

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

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

[0205] In NR use cases / extended scenarios, enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), and massive machine-type communications (mMTC) may have multiple necessary conditions in terms of data rate, latency, and coverage. For example, eMBB is expected to support peak data rates approximately three times that of IMT-Advanced (20Gbps in downlink and 10Gbps in uplink) and effective (user-experienced) data rates. On the other hand, in the case of URLLC, more stringent necessary conditions are proposed for ultra-low latency (0.5ms latency in both UL and DL) and high reliability (within 1ms, 1-10-5). Finally, in mMTC, high connectivity density (1,000,000 devices / km2 in urban environments), wide coverage in harsh environments, and extremely long-life batteries (15 years) for inexpensive devices are preferred.

[0206] Therefore, a set of OFDM parameters suitable for one use case (e.g., subcarrier spacing (SCS), OFDM symbol length, cyclic prefix (CP) length, number of symbols per scheduling interval) may be ineffective for other use cases. For example, in low-latency services, it is preferable to require a shorter symbol length than in mMTC services (therefore, a larger subcarrier spacing) and / or fewer symbols per scheduling interval (also known as "TTI"). Moreover, in extended scenarios with large channel delay spread, it is preferable to require a longer CP length than in scenarios with shorter delay spread. The subcarrier spacing can also be optimized depending on the situation to maintain the same CP overhead. NR supports more than one subcarrier spacing value. Correspondingly, subcarrier spacings of 15kHz, 30kHz, 60kHz, etc., are currently considered. The symbol length Tu and the subcarrier spacing Δf are directly related according to the formula Δf = 1 / Tu. Similar to LTE systems, the term "resource element" can be used to represent the smallest unit of resources consisting of a subcarrier of the length of one OFDM / SC-FDMA (Single-Carrier Frequency Division Multiple Access) symbol.

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

[0208] Functional separation between NG-RAN and 5GC in 5GNR

[0209] Figure 7 This indicates the functional separation between NG-RAN and 5GC. The logical node of NG-RAN is either gNB or ng-eNB. 5GC has logical nodes AMF, UPF, and SMF (Session Management Function).

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

[0211] - Functions such as Radio Bearer Control, Radio Admission Control, Connection Mobility Control, and Radio Resource Management (RRM) that dynamically allocates (schedules) resources to the UE in both the uplink and downlink links;

[0212] - Data IP (Internet Protocol) header compression, encryption, and integrity protection;

[0213] - Selection of AMF when attaching a UE in situations where the route to the AMF cannot be determined based on the information provided by the UE;

[0214] - Routing to user plane data towards UPF;

[0215] - Routing of control plane information toward AMF;

[0216] - Setting and canceling connections;

[0217] - Scheduling and sending paging messages;

[0218] - The scheduling and transmission of system broadcast information (originating from AMF or Operation, Admission, and Maintenance functions (OAM));

[0219] - Setting up measurements and measurement reports for mobility and scheduling;

[0220] - Packet markings for transmission class in the uplink;

[0221] -Session management;

[0222] -Support for network slicing;

[0223] - QoS (Quality of Service) flow management and mapping to data radio bearers;

[0224] Support for UEs in RRC_INACTIVE (RRC inactive) state;

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

[0226] - Sharing of wireless access networks;

[0227] - Dual connectivity;

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

[0229] The Access and Mobility Management Function (AMF) administers the following main functions:

[0230] - Function to terminate Non-Access Stratum (NAS) signaling;

[0231] -Security of NAS signaling;

[0232] - Security controls at the access layer (AS);

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

[0234] - The possibility of a UE reaching idle mode (including control and execution of paging retransmission);

[0235] -Management of the registered area;

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

[0237] -Access authentication;

[0238] - Access licenses that include roaming permission checks;

[0239] - Mobility management controls (subscription and policies);

[0240] -Support for network slicing;

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

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

[0243] - Anchor points for intra-RAT (Radio Access Technology) mobility / inter-RAT (where applicable) mobility;

[0244] - External PDU (Protocol Data Unit) session points used for interconnection with data networks;

[0245] - Packet routing and forwarding;

[0246] - Enforcement of policy rules in group checks and user-facing aspects;

[0247] - Reports on business usage;

[0248] - Uplink classifier used to support routing of service flows toward the data network;

[0249] - Branching points used to support multi-homed PDU sessions;

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

[0251] - Uplink service verification (SDF (Service Data Flow) mapping to QoS flow);

[0252] - Downlink packet buffering and downlink data notification triggering functions.

[0253] Finally, the Session Management Function (SMF) administers the following main functions:

[0254] -Session management;

[0255] - The allocation and management of UE IP addresses;

[0256] -Selection and control of UPF;

[0257] - A function for setting traffic steering in the User Plane Function (UPF) to direct traffic to the appropriate destination;

[0258] - Enforcing policies and QoS in the control section;

[0259] - Notification of downlink data.

[0260] <The process of setting up and resetting RRC connection>

[0261] Figure 8 This refers to several interactions between the UE, gNB, and AMF (5GC entity) when the UE in the NAS part transitions from RRC_IDLE (RRC idle) to RRC_CONNECTED (RRC connected) (refer to TS 38.300 v15.6.0).

[0262] RRC is a higher-level signaling (protocol) used for UE and gNB configuration. Through this transition, the AMF prepares UE context data (which includes, for example, PDU session context, security keys, UE radio capabilities, and UE security capabilities) and sends it to the gNB along with an initial context setting request. Next, the gNB and UE activate AS security together. The gNB sends a SecurityModeCommand message to the UE, and the UE responds with a SecurityModeComplete message, thereby activating AS security. Then, the gNB sends an RRCReconfiguration message to the UE, and receives an RRCReconfigurationComplete message from the UE for this message, thus performing the reconfiguration of Signaling RadioBearer 2 (SRB2) and Data Radio Bearer (DRB). For signaling-only connections, since SRB2 and DRB are not configured, the steps related to RRC reconfiguration can be omitted. Finally, the gNB notifies the AMF that the configuration process is complete using the Initial Context Setup Reply.

[0263] Therefore, this disclosure provides an entity (e.g., AMF, SMF, etc.) for a fifth-generation core network (5GC), comprising: a control circuit that, upon operation, establishes a Next Generation (NG) connection with a gNodeB; and a transmission unit that, upon operation, transmits an initial context setting message to the gNodeB via the NG connection to configure the signaling radio bearer between the gNodeB and the User Equipment (UE). Specifically, the gNodeB transmits Radio Resource Control (RRC) signaling containing an Information Element (IE) to the UE via the signaling radio bearer. The UE then performs uplink transmission or downlink reception based on the resource allocation settings.

[0264] <Application Scenarios of IMT after 2020>

[0265] Figure 9 This section outlines several use cases for 5G NR. Within the 3rd Generation Partnership Project New Radio (3GPP NR), three use cases supporting a wide variety of services and applications, conceived through IMT-2020, have been explored. Planning for the first phase of specifications for enhanced mobile broadband (eMBB) has been completed. Current and future work, in addition to gradually expanding eMBB support, includes standardization for ultra-reliable and low-latency communications (URLLC) and massive machine-type communications (mMTC). Figure 9 Several examples illustrating conceptual application scenarios for IMT after 2020 (e.g., referring to ITU-R M.2083). Figure 2 ).

[0266] URLLC use cases have strict requirements related to performance aspects such as throughput, latency, and availability. URLLC is conceived as a key technology for enabling wireless control of future industrial production or manufacturing processes, remote medical surgery, automation of power transmission and distribution in smart grids, and traffic safety applications. Ultra-high reliability of URLLC is supported by defining technologies that meet the requirements set by TR38.913. In NR URLLC version 15, a crucial requirement is a target user plane latency of 0.5ms in the UL (uplink) and 0.5ms in the DL (downlink). For a single packet transmission, the overall requirement for URLLC is a block error rate (BLER) of 1E-5 for a 32-byte packet size with a user plane latency of 1ms.

[0267] Considering the physical layer, numerous methods are available to improve reliability. Current possibilities for reliability enhancement include defining additional CQI (Channel Quality Indicator) tables for URLLC, a more compact DCI format, and PDCCH iteration. However, as NR (a crucial prerequisite for NR URLLC) becomes more stable and is further developed, this scope can be expanded to achieve ultra-high reliability. Specific use cases for NR URLLC in version 15 include augmented reality / virtual reality (AR / VR), e-health, e-safety, and other critical applications.

[0268] Furthermore, the technical enhancements for NR URLLC aim to improve latency and reliability. Latency enhancements include configurable parameter sets, non-slot-based scheduling utilizing flexible mapping, unlicensed (already licensed) uplinks, slot-level repetition in the data channel, and pre-emption in the downlink. Pre-emption means stopping transmissions with allocated resources and using those resources for later-requested transmissions that require lower latency / higher priority. Therefore, a permitted transmission is replaced by a subsequent transmission. Pre-emption can be applied regardless of the specific service type. For example, a transmission in service type A (URLLC) can be replaced by a transmission in service type B (eMBB, etc.). Reliability enhancements include a dedicated CQI / MCS table for a target BLER of 1E-5.

[0269] The use cases for mMTC (massive machine-type communications) are characterized by a large number of connected devices that transmit relatively small amounts of data that are not easily affected by latency. These devices require low cost and very long battery life. From NR's perspective, utilizing very narrow bandwidth is a solution to save UE power and extend its battery life.

[0270] As mentioned above, the potential for reliability improvements in NR is further expanded. It is one of the essential conditions for all situations; for example, high or ultra-high reliability is an important necessity related to URLLC and mMTC. From both wireless and network perspectives, reliability can be improved through several mechanisms. Generally, there are two to three important areas that could potentially contribute to improved reliability. These areas include compact control channel information, data / control channel iteration, and diversity related to the frequency, time, and / or spatial domains. These areas can be used to improve reliability generally, regardless of the specific communication scenario.

[0271] Regarding NR URLLC, further use cases with more stringent requirements are envisioned, such as factory automation, transportation, and power transmission. Stricter requirements refer to high reliability (reaching level 10⁻⁶), high availability, a packet size of 256 bytes, and time synchronization of approximately several microseconds (μs) (capable of corresponding to use cases, with values ​​set to 1 μs or several microseconds depending on the frequency range and short latency of approximately 0.5ms to 1ms (e.g., 0.5ms latency in the target user plane)).

[0272] Furthermore, from a physical layer perspective, there are several technical enhancements to NR URLLC. These enhancements include strengthening the PDCCH (Physical Downlink Control Channel) associated with compact DCI, PDCCH repetition, and increased PDCCH monitoring. Additionally, enhancements to UCI (Uplink Control Information) are related to enhanced HARQ (Hybrid Automatic Repeat Request) and CSI feedback. Furthermore, there may be enhancements to PUSCH and retransmission / repetition related to mini-slot-level frequency hopping. The term "mini-slot" refers to a transmission time interval (TTI) containing fewer symbols than a time slot (a time slot has 14 symbols).

[0273] <QoS Control>

[0274] 5G's QoS (Quality of Service) model is based on QoS flows, supporting both QoS flows that require guaranteed bit rate (GBR) and QoS flows that do not require guaranteed bit rate (non-GBR QoS flows). Therefore, at the NAS level, QoS flows represent the finest granular QoS classification within a PDU session. QoS flows are determined within a PDU session based on the QoS Flow ID (QFI) transmitted via the encapsulation header through the NG-U interface.

[0275] For each UE, 5GC establishes one or more PDU sessions. For each UE, in conjunction with the PDU session, NG-RAN, for example, refers to the previous text. Figure 8 As explained, at least one Data Radio Bearer (DRB) is established. Additionally, DRBs can be subsequently configured in QoS flows added to this PDU session (when to configure this depends on the NG-RAN). The NG-RAN maps packets belonging to various PDU sessions to various DRBs. NAS-level packet filters in the UE and 5GC are used to 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.

[0276] Figure 10 This refers to the non-roaming reference architecture of 5G NR (refer to TS 23.501 v16.1.0, section 4.23). Application Function (AF) (e.g., hosting...) Figure 9 The external application server (exemplified in the 5G service example) interacts with the 3GPP core network to provide services. For example, it may access a Network Exposure Function (NEF) to support applications that impact service routing, or it may interact with a policy framework (see Policy Control Function (PCF)) for policy control (e.g., QoS control). Based on operator deployment, operators deem trusted application functions capable of directly interacting with associated network functions. Application functions not permitted by the operator to directly access network functions interact with associated network functions via the NEF, using an open framework accessible to the outside world.

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

[0278] Therefore, this disclosure provides an application server (e.g., an AF in a 5G architecture) comprising: a transmitting unit that, in order to establish a PDU session containing a radio bearer between a g node B and a UE corresponding to QoS requirements, sends, upon operation, at least one of the functions of the 5GC (e.g., NEF, AMF, SMF, PCF, UPF, etc.) containing a request for at least one of the QoS requirements of URLLC service, eMMB service, and mMTC service; and a control circuit that, upon operation, performs services using the established PDU session.

[0279] This disclosure can be implemented in software, hardware, or software in cooperation with hardware. The functional blocks used in the above embodiments are implemented partially or wholly as LSIs (Large Scale Integration), and the processes described in the above embodiments can also be controlled partially or wholly by a single LSI or a combination of LSIs. An LSI can be composed of individual chips, or it can be composed of a single chip containing some or all of the functional blocks. An LSI can also include data input and output. Depending on the degree of integration, an LSI can also be referred to as an "IC (Integrated Circuit)," "System LSI," "Super LSI," or "Ultra LSI."

[0280] The method of integrating the LSI is not limited to LSI; it can also be implemented using dedicated circuits, general-purpose processors, or special-purpose processors. Alternatively, it can utilize FPGAs (Field Programmable Gate Arrays) that can be programmed after LSI fabrication, or reconfigurable processors that can reconfigure the connections or settings of the circuit blocks within the LSI. This disclosure can also be implemented for digital or analog processing.

[0281] Furthermore, if advancements in semiconductor technology or the emergence of other derivative technologies lead to integrated circuit technologies that can replace LSIs, these technologies could also be used to integrate functional blocks. There are also possibilities for applications such as biotechnology.

[0282] This disclosure can be implemented in all kinds of devices, apparatuses, and systems with communication capabilities (collectively referred to as "communication devices"). A communication device may also include a wireless transceiver and processing / control circuitry. The wireless transceiver may also include a receiving unit and a transmitting unit, or perform the functions of these parts. The wireless transceiver (transmitting unit, receiving unit) may also include an RF (Radio Frequency) module and one or more antennas. The RF module may also include an amplifier, an RF modulator / demodulator, or similar devices. Non-limiting examples of communication devices include: telephones (mobile phones, smartphones, etc.), tablet computers, personal computers (PCs) (laptops, desktops, laptops, etc.), cameras (digital cameras, digital camcorders, etc.), digital players (digital audio / video players, etc.), wearable devices (wearable cameras, smartwatches, tracking devices, etc.), game consoles, e-book readers, remote health / telemedicine (remote healthcare / medical prescription) devices, vehicles or transportation vehicles with communication capabilities (cars, airplanes, ships, etc.), and combinations of the various devices described above.

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

[0284] In addition to data communication via cellular systems, wireless LAN (Local Area Network) systems, and communication satellite systems, communication also includes data communication via a combination of these systems.

[0285] In addition, the communication device also includes devices such as controllers or sensors that are connected or linked to a communication device performing the communication functions described in this disclosure. For example, it includes a controller or sensor that generates control signals or data signals used by the communication device to perform the communication functions of the communication device.

[0286] In addition, the communication device includes infrastructure equipment that communicates with or controls the various devices described above (not limited to these), such as base stations, access points, and all other devices, equipment, and systems.

[0287] A terminal according to an embodiment of the present disclosure includes: a receiving circuit for receiving parameters related to an unlicensed band domain; and a control circuit for determining information included in uplink control information based on the parameters.

[0288] In one embodiment of this disclosure, the control circuit is configured to one of a first mode and a second mode. In the first mode, uplink control information including information related to retransmission control is transmitted. In the second mode, uplink control information excluding at least a portion of the information related to retransmission control is transmitted.

[0289] In one embodiment of this disclosure, the parameter represents either the first mode or the second mode.

[0290] In one embodiment of this disclosure, the receiving circuit receives a semi-static control signal including the parameters.

[0291] In one embodiment of this disclosure, the parameter is a parameter related to the priority in the settings of resource allocation assigned to the terminal.

[0292] In one embodiment of this disclosure, the parameter is a parameter related to the channel access method.

[0293] In one embodiment of this disclosure, the parameter is a parameter related to the coding and modulation method.

[0294] In one embodiment of this disclosure, the parameter is a parameter indicating whether it is a controlled environment.

[0295] The entire contents of the specification, drawings and abstract contained in Japanese Patent Application No. 2020-022297, filed on February 13, 2020, are incorporated herein by reference.

[0296] Industrial availability

[0297] One embodiment of this disclosure is useful for wireless communication systems.

[0298] Label Explanation

[0299] 100 base stations

[0300] Receiver units 101 and 201

[0301] 102 Separation Unit

[0302] 103 Control Information Demodulation / Decoding Unit

[0303] 104 Data Demodulation / Decoding Units

[0304] 105 Scheduling Unit

[0305] 106, 203 Control Information Holding Unit

[0306] 107 Data / Control Information Generation Unit

[0307] 108 coding / modulation units

[0308] Transmitting units 109 and 208

[0309] 200 terminals

[0310] 202 Demodulation / Decoding Unit

[0311] 204 Send Control Unit

[0312] 205 Data Generation Unit

[0313] 206 Control Information Generation Unit

[0314] 207 Encoding / Modulation / Multiplexing Unit.

Claims

1. An integrated circuit, comprising: The receiving circuit controls the reception of control information related to the setting of unlicensed band domain permissions; as well as The decision circuit determines the content to be included in the uplink control information, wherein the retransmission control information to be included in the uplink control information is determined based on the received control information.

2. The integrated circuit according to claim 1, wherein, The decision circuit sets a first mode or a second mode. In the first mode, it sends uplink control information including information related to retransmission control. In the second mode, it sends uplink control information that does not include at least a portion of the information related to retransmission control.

3. The integrated circuit according to claim 2, wherein, The control information indicates either the first mode or the second mode.

4. The integrated circuit according to claim 1, wherein, The receiving circuit receives higher-layer signaling including the received control information.

5. The integrated circuit according to claim 1, wherein, The decision circuit determines whether the uplink control information includes configuration permission-uplink control information (CG-UCI) based on the received control information.

6. The integrated circuit according to claim 5, wherein, The CG-UCI includes the HARQ process number, the New Data Indicator (NDI), and the Redundancy Version (RV).

7. The integrated circuit according to claim 5, wherein, If the uplink control information includes the CG-UCI, a retransmission timer is set; otherwise, if the uplink control information does not include the CG-UCI, the retransmission timer is not set.

8. The integrated circuit according to claim 1, wherein, The received control information also indicates whether the terminal receives downlink feedback information (DFI) for the configured licensed-physical uplink shared channel (CG-PUSCH).

9. An integrated circuit, comprising: The transmitting circuit controls the transmission of control information related to the setting of permission for the unlicensed bandfield; as well as A receiving circuit that controls the reception of content included in uplink control information, wherein the retransmission control information to be included in the uplink control information is determined based on the control information.

10. The integrated circuit according to claim 9, wherein, A first mode or a second mode is set, in which the uplink control information including information related to retransmission control is transmitted, and in the second mode, the uplink control information excluding at least a portion of the information related to the retransmission control is transmitted.

11. The integrated circuit according to claim 10, wherein, The control information indicates either the first mode or the second mode.

12. The integrated circuit according to claim 9, wherein, The transmitting circuit transmits higher-level signaling that includes the control information.

13. The integrated circuit according to claim 9, wherein, Whether the uplink control information includes configuration permission-uplink control information (CG-UCI) is determined based on the control information.

14. The integrated circuit according to claim 13, wherein, The CG-UCI includes the HARQ process number, the New Data Indicator (NDI), and the Redundancy Version (RV).

15. The integrated circuit according to claim 13, wherein, If the uplink control information includes the CG-UCI, a retransmission timer is set; otherwise, if the uplink control information does not include the CG-UCI, the retransmission timer is not set.

16. The integrated circuit according to claim 9, wherein, The control information also indicates whether the terminal receives downlink feedback information (DFI) for the configured licensed-physical uplink shared channel (CG-PUSCH).

17. A communication device, comprising: The receiving unit receives control information related to the setting of unlicensed band domains; as well as The circuit determines what to include in the uplink control information, wherein the retransmission control information to be included in the uplink control information is determined based on the received control information.

18. The communication device according to claim 17, wherein, The circuit determines whether the uplink control information includes configuration permission-uplink control information (CG-UCI) based on the received control information.

19. The communication device according to claim 18, wherein, The CG-UCI includes the HARQ process number, the New Data Indicator (NDI), and the Redundancy Version (RV).

20. The communication device according to claim 18, wherein, If the uplink control information includes the CG-UCI, a retransmission timer is set; otherwise, if the uplink control information does not include the CG-UCI, the retransmission timer is not set.

21. The communication device according to claim 17, wherein, The received control information also indicates whether the terminal receives downlink feedback information (DFI) for the configured licensed-physical uplink shared channel (CG-PUSCH).

22. The communication device according to claim 17, comprising: The transmitting circuit transmits uplink control information, including the determined content, in the Physical Uplink Shared Channel (PUSCH).

23. A communication method, comprising: Receive control information related to setting permissions for unlicensed bandfields; as well as The decision on what to include in the uplink control information is based on the received control information.

24. The communication method according to claim 23, comprising: Based on the received control information, determine whether the uplink control information includes Configuration Grant-Uplink Control Information (CG-UCI).

25. The communication method according to claim 24, wherein, The CG-UCI includes the HARQ process number, the New Data Indicator (NDI), and the Redundancy Version (RV).

26. The communication method according to claim 24, wherein, If the uplink control information includes the CG-UCI, a retransmission timer is set; otherwise, if the uplink control information does not include the CG-UCI, the retransmission timer is not set.

27. The communication method according to claim 23, wherein, The received control information also indicates whether the terminal receives downlink feedback information (DFI) for the configured licensed-physical uplink shared channel (CG-PUSCH).

28. The communication method according to claim 23, comprising: Uplink control information, including the determined content, is transmitted in the Physical Uplink Shared Channel (PUSCH).

29. A base station, comprising: The sending unit sends control information related to the setting of unlicensed bandfield permissions; as well as A receiving unit receives content included in uplink control information, wherein the retransmission control information to be included in the uplink control information is determined based on the control information.

30. A communication method, comprising: Send control information related to setting permissions for unlicensed bandgap domains; as well as Receive content included in uplink control information, wherein the retransmission control information to be included in the uplink control information is determined based on the control information.

Images