Terminal and communication method

By configuring terminals with multiple resource candidates and employing efficient resource management strategies, the transmission opportunities and reliability of uplink signals in unlicensed bands are enhanced, addressing the challenge of interference and delay in unlicensed frequency environments.

JP7594002B2Active Publication Date: 2024-12-03PANASONIC INTELLECTUAL PROPERTY CORP OF AMERICA
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
JP2022516864
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Priority Date
2020-04-24
Filing Date
2021-02-18
Publication Date
2024-12-03
Estimated Expiration
2041-02-18

AI Technical Summary

Technical Problem

There is a need to increase transmission opportunities of uplink signals in unlicensed bands to improve communication reliability and reduce delays, particularly in environments with potential interference from other systems.

Method used

A terminal is configured with multiple resource candidates for carrier sense, allowing it to select and transmit uplink signals using available resources, and employs methods such as common parameter setting, transport block reuse, and resource candidate switching to enhance transmission opportunities and reduce processing time.

Benefits of technology

This approach increases the chances of successful uplink signal transmission, improves communication reliability, and reduces delays by optimizing resource utilization and processing time, even in the presence of interference.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007594002000004
    Figure 0007594002000004
  • Figure 0007594002000005
    Figure 0007594002000005
  • Figure 0007594002000006
    Figure 0007594002000006
Patent Text Reader

Abstract

This terminal is provided with a control circuit which employs carrier sensing to determine an available resource candidate among a plurality of resource candidates based on units of carrier sensing, and a transmitting circuit which transmits an uplink signal using the available resource candidate.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present disclosure relates to a terminal and a communication method. [Background technology]

[0002] The 3rd Generation Partnership Project (3GPP) has completed the formulation of the Release 16 NR (New Radio access technology) physical layer specifications as an extension of the 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 functions to realize ultra-reliable and low latency communication (URLLC) (see, for example, non-patent documents 1-5). [Prior art documents] [Non-patent literature]

[0003] [Non-Patent Document 1] 3GPP TS 38.211 V16.1.0, "NR; Physical channels and modulation (Release 16)," March 2020 [Non-Patent Document 2] 3GPP TS 38.212 V16.1.0, "NR; Multiplexing and channel coding (Release 16)," March 2020 [Non-Patent Document 3] 3GPP TS 38.213 V16.1.0, "NR; Physical layer procedure for control (Release 16)," March 2020 [Non-Patent Document 4] 3GPP TS 38.214 V16.1.0, "NR; Physical layer procedures for data (Release 16)," March 2020 [Non-Patent Document 5] 3GPP TS 38.331 V16.0.0, "NR; Radio Resource Control (RRC) protocol specification (Release 16)", March 2020 Summary of the Invention

[0004] However, there is room for improvement in methods for increasing the opportunities for transmitting uplink signals in unlicensed bands.

[0005] Non-limiting embodiments of the present disclosure contribute to providing a terminal and a communication method that can increase opportunities to transmit uplink signals in unlicensed bands.

[0006] A terminal according to one embodiment of the present disclosure includes a control circuit that determines a usable resource candidate by carrier sense from among multiple resource candidates based on a unit of carrier sense, and a transmission circuit that transmits an uplink signal using the usable resource candidate.

[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 one embodiment of the present disclosure, it is possible to increase opportunities for transmitting uplink signals in unlicensed bands.

[0009] Further advantages and benefits of an embodiment of the present disclosure will become apparent from the specification and drawings. Such advantages and / or benefits may be provided by some of the 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. [Brief description of the drawings]

[0010] [Figure 1] Block diagram showing an example of a partial configuration of a terminal [Diagram 2] Block diagram showing a configuration example of a base station [Diagram 3] Block diagram showing an example of a terminal configuration [Figure 4] A sequence diagram showing an example of the operation of a base station and a terminal. [Diagram 5] FIG. 1 shows an example of setting CG parameters according to setting method 1 of embodiment 1. [Figure 6] FIG. 13 illustrates an example of generating a transport block according to a configuration method 3 of the first embodiment. [Figure 7] FIG. 13 is a diagram showing an example of switching of a BWP (bandwidth part) according to a switching method 1 of the second embodiment. [Figure 8] FIG. 13 is a diagram showing an example of switching of BWP according to a switching method 2 of the second embodiment. [Figure 9] FIG. 13 is a diagram showing an example of CG (configured grant) resource settings according to the third embodiment. [Figure 10] FIG. 13 is a diagram showing an example of setting CG resources according to the third embodiment. [Figure 11] FIG. 1 is an example architecture diagram of a 3GPP NR system. [Figure 12] Schematic diagram showing the functional separation between NG-RAN (Next Generation - Radio Access Network) and 5GC (5th Generation Core) [Figure 13] Sequence diagram of Radio Resource Control (RRC) connection setup / reconfiguration procedure [Figure 14]A schematic diagram showing the usage scenarios of enhanced Mobile BroadBand (eMBB), massive Machine Type Communications (mMTC), and Ultra Reliable and Low Latency Communications (URLLC). [Figure 15] Block diagram illustrating an example 5G system architecture for a non-roaming scenario DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

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

[0012] [Unlicensed frequency bands] In Release 16 NR, for example, the introduction of NR-Unlicensed (also called NR-U), which will communicate based on the NR radio access method in unlicensed frequency bands (also called unlicensed bands), is being considered.

[0013] In unlicensed frequency bands, for example, each device performs carrier sense (also called Listen Before Talk (LBT)) to check whether or not another system or terminal is using the radio channel before transmission. In NR-U, for example, whether or not transmission is possible is determined according to the result of LBT, so a procedure is being considered for a terminal (also called user equipment (UE)) to detect the start of transmission of downlink data (for example, downlink burst (DL burst)) by a base station (also called gNB). For example, in Release 16 NR, detection of DL burst based on PDCCH is being considered.

[0014] In addition, in Release 17 NR, an extension is being considered for operating, for example, Ultra Reliable and Low Latency Communications (URLLC) services in unlicensed frequency bands. In unlicensed frequency bands, for example, interference from other systems may occur. For example, if an LBT failure (also called an LBT failure) occurs due to interference from other systems, a waiting time may occur until transmission, and delays may increase.

[0015] For this reason, Release 17 NR assumes that URLLC services will be operated in an environment where there is basically no interference from other systems (e.g., called a "controlled environment"). However, even in a controlled environment, it is assumed that interference may occur unexpectedly.

[0016] [Configured grant transmission] This section describes configured grant transmission (e.g., configured grant transmission in licensed frequency bands) supported in Release 15 NR.

[0017] Configured grant transmission for uplink data (eg, PUSCH: Physical Uplink Shared Channel) includes, for example, a "Configured grant type 1 transmission" and a "Configured grant type 2 transmission".

[0018] In configured grant type 1 transmission, information such as a coding and modulation scheme (MCS), radio resource allocation (e.g., allocation of at least one of time resources and frequency resources), transmission timing, and the number of Hybrid Automatic Repeat Request (HARQ) processes (e.g., referred to as configured grant setting information or CG setting information) may be configured (in other words, notified or instructed) in the terminal by a terminal-specific higher layer signal. For example, when uplink data is generated, the terminal may transmit uplink data (e.g., PUSCH) based on CG setting information such as a previously configured MCS and radio resources, without a UL grant (e.g., dynamic uplink data scheduling information) by a downlink control channel (e.g., PDCCH: Physical Downlink Control Channel) from the base station.

[0019] In addition, the higher layer signal may also be called, for example, a Radio Resource Control (RRC) signal, higher layer signaling, or higher layer parameter.

[0020] Furthermore, in Configured grant type 2 transmission, for example, the Configured grant transmission is activated or released by the PDCCH from the base station. In Configured grant type 2 transmission, for example, information such as the transmission timing and the number of HARQ processes may be set by a higher layer signal specific to the terminal, as in Configure grant type 1 transmission. On the other hand, in Configured grant type 2 transmission, information such as the MCS and radio resource allocation information may be set by Downlink Control Information (DCI) for Activation. For example, when uplink data is generated, the terminal may transmit uplink data (for example, PUSCH) by semi-permanently (in other words, statically or semi-statically) using CG setting information such as the MCS and radio resources set by the higher layer signal and DCI for Activation (in other words, without a UL grant or UL grant free).

[0021] In Release 15 NR, for example, a UL grant is used for retransmission control of a configured grant transmission. For example, the MCS and radio resource allocation information of uplink data for retransmission may be controlled by the UL grant.

[0022] Furthermore, the HARQ process number (or HARQ process ID) used in the configured grant transmission may be uniquely determined from the slot number for transmitting the PUSCH (in other words, the transmission timing of the PUSCH), as a non-limiting example. For example, the PUSCH transmitted in the configured grant transmission may be treated in the same manner as a signal transmitted for the first time, and the redundancy version (RV) may be 0.

[0023] [Configured grant transmission in unlicensed frequency bands] In a Configured grant transmission in NR-U (NR in an unlicensed frequency band), some of the parameters (e.g., parameters related to retransmission control) used for decoding the PUSCH, such as the HARQ process number, New Data Indicator (NDI), and RV, may be notified from the terminal to the base station by uplink control information for the Configured grant transmission (e.g., called CG-UCI: Configured grant Uplink Control Information).

[0024] The CG-UCI may be transmitted at the same transmission timing (e.g., the same slot) as the PUSCH (also referred to as CG-PUSCH) by using, for example, a part of the radio resources allocated to the PUSCH. In other words, the CG-UCI may be multiplexed with the CG-PUSCH.

[0025] Here, the reason why the HARQ process number is explicitly notified using the CG-UCI in NR-U is as follows. For example, in NR-U, PUSCH is not necessarily transmitted depending on the result of LBT. For this reason, in a method of determining the HARQ process number in association with the transmission timing of PUSCH, such as in a licensed frequency band, the HARQ process may not be flexibly used depending on whether the PUSCH is actually transmitted. Therefore, the HARQ process number may be notified using the CG-UCI transmitted together with the CG-PUSCH, for example.

[0026] In addition, in NR-U, for example, when a NACK is received or a timer expires, a terminal supports an operation of retransmitting data without a UL grant using radio resources set for a Configured grant. Therefore, for example, information indicating the initial transmission or retransmission state (for example, NDI: New Data Indicator) and an RV to be applied to the PUSCH at the time of retransmission may be transmitted by the CG-UCI.

[0027] In NR-U, for example, HARQ-ACK feedback for CG-PUSCH may be explicitly notified from the gNB to the UE by information called DFI (Downlink Feedback Indicator). For CG-PUSCH, for example, a HARQ process number is notified by CG-UCI. For this reason, for example, if the gNB fails to receive CG-UCI, it may be impossible to specify which HARQ process data was transmitted on the gNB side, and it may not be possible to specify the HARQ process and instruct retransmission of PUSCH. Therefore, for example, the gNB may notify (in other words, feedback) HARQ-ACK feedback information for all HARQ processes. In addition, the gNB can reduce overhead due to LBT and improve efficiency of retransmission control by, for example, collectively feeding back HARQ-ACK feedback information for multiple PUSCHs to the terminal.

[0028] In the retransmission control by the DFI, the MCS and the radio resource allocation of the PUSCH for retransmission may be the same as those in the initial transmission. Also, the DFI may be transmitted, for example, in the PDCCH. Also, the DFI may include other parameters such as a transmission power control (TPC) command in addition to the HARQ-ACK.

[0029] In one embodiment of the present disclosure, a method for increasing transmission opportunities of an uplink signal (e.g., CG-PUSCH) in the above-mentioned unlicensed frequency band will be described. Increasing the transmission opportunities of the uplink signal can, for example, improve communication reliability and reduce delay. Furthermore, according to one embodiment of the present disclosure, for example, when operating a URLLC service in an unlicensed band, even if interference occurs suddenly, the increased transmission opportunities of the uplink signal make it easier to satisfy the requirements of URLLC.

[0030] [Success rate of sending and receiving in configured grant] The reception success rate of the PUSCH (e.g., CG-PUSCH) of the Configured grant may be based on, for example, the number of radio resources (hereinafter also referred to as "CG resources") configured for the Configured grant that are available at a certain timing. For example, when there are N CG resources (for example, when N CG resources are configured in advance in a terminal and the terminal can select a CG resource for transmitting a CG-PUSCH from among the N CG resources), the transmission and reception success rate of the CG-PUSCH may be calculated according to the following formulas (1) and (2).

number

number

[0031] Here, "P CG-PUSCH ” represents the probability that CG-PUSCH transmission and reception is successful, and “P CG-UCI ” represents the probability of successful decoding of CG-UCI, and “P CG-PUSCHdata " represents the probability of successful decoding of the CG-PUSCH alone (for example, the CG-PUSCH when the control information (CG-UCI) is correctly acquired). LBT ” represents the probability that the LBT will be successful, and “P LBT,n " represents the probability that LBT will be successful on the nth CG resource out of N CG resources.

[0032] For example, since control information contained in the CG-UCI transmitted together with the CG-PUSCH is used to receive the CG-PUSCH, the equation expressing the transmission and reception success rate of the CG-PUSCH shown in equation (1) may also include parameters related to the CG-UCI.

[0033] Here, in formula (1), for example, "P CG-UCI P CG-PUSCHdata Even if the value of "P LBT When " is low, the CG-PUSCH transmission and reception success rate P CG-PUSCH can be low. For example, P CG-UCI PCG-PUSCHdata =1-10 -5 (e.g., 99.999%), and P LBT =1-10 -2 In the case of (99%), the success rate of CG-PUSCH transmission and reception P CG-PUSCH The decoding success rate of CG-UCI and CG-PUSCH (P CG-UCI P CG-PUSCHdata )=1-10 -5 is decreased compared to

[0034] In addition, as shown in equation (2), the more CG resources available at a given time, the higher the success rate of LBT P LBT As an example, the LBT success probability P LBT,n =1-10 -2 (99%), P for N=1 LBT =1-10 -2 (99%), and for N=4, P LBT =1-10 -6 (99.9999%). In this way, the larger the value of N, the lower the probability of LBT failure for N CG resources (for example, the multiplication term in equation (2)). Therefore, the success rate of LBT P LBT (In other words, the probability that LBT will be successful in at least one of the N CG resources) can be improved.

[0035] From the above, in order to improve the transmission and reception success rate of the CG-PUSCH, for example, the success rate of the LBT may be improved. In addition, in order to improve the success rate of the LBT, it is sufficient that there are a plurality of CG resources available at a certain timing in the terminal. In other words, it is sufficient to increase the transmission opportunities of the uplink signal in the terminal.

[0036] Therefore, in one embodiment of the present disclosure, for example, a plurality of CG resources (in other words, resource candidates) may be configured for a terminal. The terminal may transmit an uplink signal using, for example, any one of the plurality of configured CG resources (for example, a resource for which LBT has succeeded).

[0037] [Relationship between increase in transmission opportunities and terminal processing time] As described above, in order to increase the transmission opportunities of an uplink signal in a terminal, for example, multiple CG resources (also called transmission resources or LBT opportunities) may be configured in the terminal at a certain timing.

[0038] For example, the CG resource may be a resource unit for performing carrier sensing (for example, LBT). The CG resource may be a resource unit such as a resource block set (RB set), a bandwidth part (BWP), or a carrier (for example, a component carrier (CC)), or may be a resource unit obtained by dividing the RB set, the BWP, or the carrier.

[0039] For example, even when a terminal transmits a CG-PUSCH in any one of a plurality of CG resources, the terminal is expected to perform preparations for CG-PUSCH transmission (e.g., data encoding processing, etc.) for each of the plurality of CG resources. This is because there is a limit to the preparation time from when the LBT result is known until when the transmission of the CG-PUSCH starts. Therefore, if preparations for CG-PUSCH transmission are performed after the LBT result is known, it may not be possible to make time for the start of the transmission of the CG-PUSCH.

[0040] Therefore, when multiple CG resources available at a certain timing are configured in a terminal, it is expected that the processing time for CG-PUSCH transmission can be reduced. The multiple CG resources may be, for example, frequency division multiplexed or space division multiplexed.

[0041] In one embodiment of the present disclosure, a method for reducing the processing time for CG-PUSCH transmission when multiple CG resources are configured for a terminal will be described. Examples of a method for reducing the processing time for CG-PUSCH transmission include a method for reducing the processing time compared to a case where preparation for CG-PUSCH transmission is performed for each of multiple CG resources in parallel, or a method for reducing the processing time for preparing CG-PUSCH transmission for each of multiple CG resources (in other words, one CG resource).

[0042] (Embodiment 1) [Communication system overview] A communication system according to an embodiment of the present disclosure may include, for example, a base station 100 (e.g., gNB) shown in Fig. 2 and a terminal 200 (e.g., UE) shown in Fig. 1 and Fig. 3. There may be a plurality of base stations 100 and a plurality of terminals 200 in the communication system.

[0043] Fig. 1 is a block diagram showing a configuration example of a part of a terminal 200 according to an embodiment of the present disclosure. In the terminal 200 shown in Fig. 1, a transmission control unit 204 (e.g., corresponding to a control circuit) determines a usable resource candidate by carrier sense from among multiple resource candidates (e.g., CG resources) based on the unit of carrier sense. A transmission unit 208 (e.g., corresponding to a transmission circuit) transmits an uplink signal from the usable resource candidate.

[0044] [Base station configuration] Fig. 2 is a block diagram showing a configuration example of a base station 100 according to an embodiment of the present disclosure. In Fig. 2, the base station 100 includes a receiving unit 101, a demodulating and decoding unit 102, a carrier sensing 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.

[0045] The receiving unit 101 performs reception processing such as down-conversion or A / D conversion on a received signal received via an antenna, and outputs the received signal after reception processing to the demodulation and decoding unit 102 and the carrier sense unit 103. The received signal may include, for example, a signal transmitted from the terminal 200 (for example, an uplink signal) or a signal of another system.

[0046] The demodulation / decoding unit 102 demodulates and decodes a received signal (eg, an uplink signal) input from the receiving unit 101 , and outputs the decoded result to the scheduling unit 104 .

[0047] The carrier sense unit 103 may perform carrier sense (e.g., LBT) based on, for example, a received signal input from the receiving unit 101. For example, the carrier sense unit 103 may determine whether the channel state is "busy" or "idle" (in other words, whether the channel is available or not) based on the received signal input from the receiving unit 101. The carrier sense unit 103 outputs information indicating the determined channel state to the scheduling unit 104. Note that the channel state may be determined, for example, for each CC, for each BWP, or for each RB set.

[0048] The scheduling unit 104, for example, determines CG setting information (for example, information such as a transmission period, a frequency domain resource, a time domain resource, or an MCS) for the terminal 200, and outputs the determined CG setting information to the control information holding unit 105. Furthermore, the scheduling unit 104 may instruct the data and control information generating unit 106 to generate data or control information, for example, based on information indicating a channel state input from the carrier sense unit 103, or a decoding result input from the demodulation and decoding unit 102. Furthermore, when transmitting signaling information including the CG setting information, the scheduling unit 104 may instruct the data and control information generating unit 106 to generate signaling information.

[0049] The control information storage unit 105 stores, for example, control information such as CG setting information for each terminal 200. The control information storage unit 105 may output the stored information to each component of the base station 100 (for example, the scheduling unit 104) as necessary.

[0050] The data and control information generating unit 106 generates data or 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. For example, the data and control information generating unit 106 may generate data including signaling information based on an instruction to generate signaling information input from the scheduling unit 104, and output the generated data to the coding and modulation unit 107.

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

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

[0053] [Device configuration] Fig. 3 is a block diagram showing an example configuration of terminal 200 according to an embodiment of the present disclosure. In Fig. 3, terminal 200 includes receiving section 201, demodulation and decoding section 202, carrier sense section 203, transmission control section 204, control information holding section 205, data and control information generation section 206, coding and modulation section 207, and transmission section 208.

[0054] 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 received signal after reception processing to the demodulation and decoding unit 202 and the carrier sense unit 203. The received signal may include, for example, a signal transmitted from the base station 100 (for example, a downlink signal) or a signal of another system.

[0055] The demodulation / decoding unit 202 demodulates and decodes a received signal (eg, a downlink signal) input from the receiving unit 201 , and outputs the decoded result to the transmission control unit 204 .

[0056] The carrier sense unit 203 may perform carrier sense (or LBT) based on, for example, a carrier sense instruction from the transmission control unit 204 and a received signal input from the receiving unit 201. For example, the carrier sense unit 203 may determine whether the channel state is "busy" or "idle" (in other words, whether the channel is available or not) based on the received signal input from the receiving unit 201. The carrier sense unit 203 outputs information indicating the determined channel state to the transmission control unit 204. Note that the channel state may be determined, for example, for each CC, for each BWP, or for each RB set.

[0057] The transmission control unit 204 outputs, for example, signaling information (for example, CG setting information) 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 206 to generate data or control information based on, for example, control information such as the CG setting information input from the control information holding unit 205. Furthermore, the transmission control unit 204 may instruct, for example, the carrier sense unit 203 to perform carrier sense. Furthermore, the transmission control unit 204 determines resources to be used for transmitting the uplink signal based on, for example, information indicating the channel state input from the carrier sense unit 203, and outputs resource information indicating the determined resources to the encoding and modulation unit 207.

[0058] The control information storage unit 205 stores control information such as signaling information (e.g., CG setting information) input from the transmission control unit 204, and outputs the stored information to each component (e.g., the transmission control unit 204) as necessary.

[0059] The data and control information generating unit 206 generates data or control information, for example, according to an instruction from the transmission control unit 204, and outputs a signal including the generated data or control information to the coding and modulation unit 207. For example, the data and control information generating unit 206 may generate data including signaling information based on an instruction to generate signaling information input from the transmission control unit 204, and output the generated data to the coding and modulation unit 207.

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

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

[0062] [Operation of base station 100 and terminal 200] An example of the operation of base station 100 and terminal 200 having the above configuration will be described.

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

[0064] Base station 100, for example, determines a configured grant setting for terminal 200 (S101). The configured grant setting may include, for example, information on MCS, radio resource allocation, transmission timing, and HARQ process. In addition, for example, base station 100 may configure, for terminal 200, a plurality of CG resources (in other words, resource candidates) as units for performing carrier sensing in an unlicensed frequency band.

[0065] The base station 100 transmits control information to the terminal 200 (S102). The control information may include, for example, CG setting information.

[0066] The terminal 200 performs, for example, carrier sensing (for example, LBT) (S103).

[0067] The terminal 200 determines the CG resource based on, for example, the CG setting information and the result of carrier sensing (S104). For example, the terminal 200 may select a CG resource determined to be available by carrier sensing from among a plurality of CG resources set in the unlicensed frequency band.

[0068] Terminal 200 transmits the CG-PUSCH, for example, in the determined CG resource (S105). Base station 100 receives the CG-PUSCH, for example, in a CG resource that terminal 200 has determined to be available by carrier sensing, among a plurality of CG resources configured in terminal 200.

[0069] [How to set CG resources and how to transmit CG-PUSCH] We will explain an example of a method for setting CG resources (e.g., physical resources for CG transmission) in base station 100 (e.g., scheduling unit 104) and terminal 200 (e.g., transmission control unit 204), and a method for transmitting CG-PUSCH in terminal 200 when multiple CG resources are set.

[0070] Terminal 200 may control transmission of the CG-PUSCH based on, for example, a setting of a plurality of CG resources in an RB set, a BWP, or a CC.

[0071] <Setting method 1> In setting method 1, a common parameter may be set for a plurality of CG resources (for example, an RB set, a BWP, or a CC) set in terminal 200. In other words, a plurality of CG resources may be associated with a common parameter.

[0072] For example, some of the multiple parameters set for each CG resource may be set in common among the multiple CG resources, and other parameters may be set for each of the multiple CG resources.

[0073] For example, parameters commonly set among a plurality of CG resources may include parameters related to processing before resource mapping (for example, processing up to encoding processing). Parameters commonly set among a plurality of CG resources may include parameters such as the number of RBs, the number of symbols, the MCS, the number of layers, and the number of symbols of a demodulation reference signal (DMRS). By setting common values ​​for these parameters for a plurality of CG resources, for example, processing before resource mapping in terminal 200 can be made common among a plurality of CG resources.

[0074] Furthermore, the parameters that are set individually for each of a plurality of CG resources may include, for example, parameters related to processing after resource mapping (for example, parameters such as the position in the frequency domain).

[0075] For example, in terminal 200, when the processing before resource mapping is common among a plurality of CG resources, terminal 200 may perform the processing in the following order of (1), (2), and (3). (1) Terminal 200 sets common values ​​for parameters used in processing before resource mapping among a plurality of CG resources. (2) Terminal 200 performs processing up to and including resource mapping of CG-PUSCH to one CG resource among multiple CG resources. (3) Terminal 200 determines a CG resource from among a plurality of CG resources to transmit a CG-PUSCH based on a result of the LBT, and transmits the CG-PUSCH mapped to the determined CG resource.

[0076] In this way, for example, by sharing the processing before resource mapping among multiple CG resources, terminal 200 can reduce processing time compared to performing the processing before resource mapping in parallel for each of the multiple CG resources.

[0077] Furthermore, for example, when the settings for multiple CG resources are shared, setting (in other words, instructing or notifying) parameters for each CG resource individually may increase signaling overhead. For this reason, for example, base station 100 and terminal 200 may duplicate parameters for one CG resource and set the parameters for each of the multiple CG resources.

[0078] Fig. 5 is a diagram showing an example of parameter settings when the CG resource is an RB set. In Fig. 5, for example, four RB sets #0 to #3 are set for terminal 200. Note that the number of RB sets set for terminal 200 is not limited to four and may be another number.

[0079] For example, when common parameters are configured for four RB sets, base station 100 may notify terminal 200 of one set of parameters related to CG resources (for example, parameters included in ConfiguredGrantConfig of Non-Patent Document 5). In other words, base station 100 does not need to notify each of the common parameters to each of the multiple RB sets configured in terminal 200 individually.

[0080] Furthermore, base station 100 may notify terminal 200 of a 4-bit bitmap that corresponds to (in other words, is linked to) the number of RB sets set in terminal 200, for example.

[0081] Each bit constituting the bitmap may correspond to, for example, each RB set set in terminal 200. For example, when the setting value of the bit is "1", a common parameter related to the CG resource notified from base station 100 to terminal 200 may be applied to the corresponding RB set. On the other hand, when the setting value of the bit is "0", for example, the common parameter related to the CG resource notified from base station 100 to terminal 200 may not be applied to the corresponding RB set. For example, a parameter different from the common parameter may be individually set to the RB set corresponding to the setting value of the bit "0".

[0082] 5, when a 4-bit bitmap corresponding to four RB sets #0 to #3 is "1111," terminal 200 may copy one set of parameters related to CG resources of RB set #0 (in other words, CG setting information) and set the copied parameters to each of the other RB sets #1 to #3. Note that the RB set from which the parameters are copied is not limited to RB set #0, and for example, parameters set in any of RB sets #1 to #3 may be set to the other RB sets.

[0083] This method allows terminal 200 to configure a plurality of CG resources using one parameter set notified from base station 100, for example, and therefore makes it possible to suppress an increase in signaling overhead.

[0084] Also, for example, when some of the parameters set for a CG resource are made common among a plurality of CG resources, the parameters to be common may be grouped, and a copy of the parameters for the plurality of CG resources may be applied to the group, while parameters not included in the group may be set for each CG resource.

[0085] Also, for example, in configured grant type 2 transmission, base station 100 may configure, for terminal 200, a CG resource for enabling (in other words, disabling) application of a common parameter, using a DCI for Activation. For example, base station 100 may notify, in the DCI for Activation, a bitmap corresponding to each of a plurality of RB sets configured in terminal 200. The bitmap may indicate, for example, whether or not to enable application of a common parameter related to the CG resource for a plurality of RB sets.

[0086] For bitmap notification by DCI for activation, for example, a field that is not used (or has a low priority) in DCI for activation may be reused. Fields that can be reused include, for example, a field for a parameter such as an HARQ process number, an RV, a Downlink assignment index (DAI), or a TPC. In addition, a combination of the above-mentioned multiple fields may be used for bitmap notification according to the number of bits corresponding to the number of CG resources (for example, the number of RB sets) set in terminal 200. This makes it possible to activate multiple CG resources without increasing the number of bits.

[0087] For example, when applying common parameters to multiple RB sets in order to standardize processing before resource mapping, even if the positions of the frequency domain in the RB set are different, as long as the number of RBs used is the same, the processing before resource mapping can be standardized. For example, if the number of RBs is the same and the size of the physical resource is the same in each of multiple CG resources, processing such as rate matching can be standardized. Therefore, for example, multiple CG resources may be arranged at different positions in the RB set, BWP, and CC. By arranging CG resources at different positions, resource utilization efficiency can be improved even when the resource usage status or congestion degree in the RB set, BWP, and CC is different.

[0088] In this way, in setting method 1, for example, a plurality of CG resources available at a certain timing are set for terminal 200. As a result, even if a certain CG resource among the plurality of CG resources set for terminal 200 cannot be used due to an LBT failure, for example, if another CG resource is available, terminal 200 can transmit an uplink signal (for example, CG-PUSCH), thereby increasing the opportunities for transmitting an uplink signal in terminal 200 and reducing the delay time.

[0089] Furthermore, for multiple CG resources set in terminal 200, parameters used for processing before resource mapping (for example, processing up to encoding processing) may be set to common values. This allows terminal 200 to generate encoded data of CG-PUSCH in one CG resource for multiple CG resources (for example, an RB set). This allows terminal 200 to reduce processing time in terminal 200 compared to a case where processing up to encoding processing (in other words, preparation for CG-PUSCH transmission) is performed in parallel for each of multiple CG resources.

[0090] Therefore, according to setting method 1, even when multiple CG resources are configured, terminal 200 can reduce the processing time for CG-PUSCH transmission and also increase the opportunities to transmit uplink signals, thereby improving communication reliability and reducing delays.

[0091] In the above example, the case where the parameter duplication is applied to the frequency domain resource has been described, but the present invention is not limited to this. For example, the above parameter duplication may be applied to the time domain resource. For example, periodicity (for example, a parameter for setting the transmission period of the CG-PUSCH) may be used for setting the time domain CG resource. The periodicity supports, for example, transmission at a constant interval (for example, 14 symbol interval). On the other hand, for example, a non-constant transmission interval can be supported by duplicating and applying a parameter using a bitmap to the time domain resource. This makes it possible to suppress an increase in signaling overhead and to more flexibly increase transmission opportunities in the time domain.

[0092] In the above example, an RB set has been described as an example of a CG resource, but the CG resource is not limited to an RB set. For example, multiple BWPs or multiple CCs may be set for terminal 200 at a certain timing.

[0093] <Setting method 2> In the setting method 2, terminal 200 may set a transport block (TB) size based on the number of multiple CG resources set in terminal 200. For example, terminal 200 may set (for example, limit) a maximum TB size based on the number of CG resources.

[0094] The encoding processing time may depend on, for example, the size of the data. For this reason, for example, the encoding processing time can be reduced by limiting the TB size, so that the processing time for transmitting the CG-PUSCH in each CG resource in terminal 200 is reduced, and the possibility of in time for the start of transmission of the CG-PUSCH increases. In other words, the TB size of each CG resource may be set so that the processing for transmitting the CG-PUSCH for each of the multiple CG resources does not exceed the processing capacity of terminal 200.

[0095] For example, when multiple CG resources are configured for terminal 200 at a certain timing in an RB set, BWP, or CC, the maximum TB size may be set (e.g., limited) according to the number of CG resources. Examples of methods for setting the maximum TB size include the following methods.

[0096] Example 1: How to set the available MCS index according to the number of CG resources For example, when the number of CG resources set in terminal 200 is 4, the maximum TB size may be set to 1 / 4 compared to when the number of CG resources is 1. In this case, the MCS index available to terminal 200 may be restricted so that the maximum TB size that can be set for terminal 200 becomes 1 / 4.

[0097] For example, when the number of CG resources is N, the maximum TB size may be set to 1 / N of the maximum TB size when compared with the case where the number of CG resources is 1, or may be set to a ratio different from 1 / N.

[0098] Example 2: How to scale TB size The terminal 200 determines the TB size "N info " may be scaled.

number

[0099] In formula (3), "N RE " represents the number of resource elements (RE), "R" represents the target coding rate, and "Q m " represents the modulation multi-level number, "ν" represents the number of layers, and "S" represents a scaling factor.

[0100] For example, when the number of CG resources set in terminal 200 is four, terminal 200 may set scaling factor S to 0.25. When the number of CG resources is N, scaling factor S may be set to 1 / N or may be set to a value different from 1 / N.

[0101] In this way, according to setting method 2, terminal 200 can reduce the processing time for preparing CG-PUSCH transmission for each of multiple CG resources by setting (in other words, limiting) the TB size according to the number of CG resources, for example, thereby reducing the processing time in terminal 200.

[0102] Setting the TB size can reduce the processing time in terminal 200, and therefore, for example, multiple CG resources available at a certain timing can be set for terminal 200, thereby increasing the opportunities for transmitting an uplink signal in terminal 200. As a result, even if, for example, a certain CG resource among multiple CG resources set for terminal 200 cannot be used due to an LBT failure, if other CG resources are available, terminal 200 can transmit an uplink signal (for example, CG-PUSCH).

[0103] Therefore, according to setting method 2, even when multiple CG resources are configured, terminal 200 can reduce the processing time for CG-PUSCH transmission and increase the opportunities to transmit uplink signals, thereby improving communication reliability and reducing delays.

[0104] <Setting method 3> In setting method 3, terminal 200 uses (in other words, reuses) a TB (e.g., a Medium Access Control Protocol Data Unit (MAC PDU)) generated in any one of multiple CG resources set in terminal 200 as a TB for another CG resource.

[0105] For example, in each RB set, BWP, or CC, when multiple CG resources available at a certain timing are configured, terminal 200 may reuse (in other words, copy) a TB generated in a certain CG resource in layer 1 (or physical layer, also called L1). By reusing the TB, terminal 200 can generate a TB in, for example, one CG resource in layer 2 (or also called L2) and not have to generate a TB in other CG resources, thereby reducing the TB processing time.

[0106] For example, as shown in FIG. 6(a), when a TB (e.g., a MAC PDU) is generated for each CG resource (here, an RB set) in layer 2, layer 2 processing for the TB is performed in each of the multiple CG resources. On the other hand, as shown in FIG. 6(b), when a TB is generated in one CG resource (RB set #1 in FIG. 6(b)) among multiple CG resources in layer 2 and the TB is copied to another CG resource in layer 1, layer 2 processing does not need to be performed in the other CG resource (RB set #2 in FIG. 6(b)). Therefore, in FIG. 6(b), for example, only one TB is generated in layer 2, and the TB processing time can be reduced compared to FIG. 6(a).

[0107] In addition, when the TB sizes differ among multiple CG resources set in terminal 200, terminal 200 may, for example, generate a TB (e.g., a MAC PDU) by layer 2 processing in the CG resource corresponding to the smallest TB size, and in other CG resources, generate a TB by padding a TB of the smallest TB size based on the TB size in each CG resource.

[0108] This allows a TB generated in a certain CG resource to be reused for another CG resource even if the TB sizes of the multiple CG resources are different. The base station 100 on the receiving side may perform reception excluding the padded bits.

[0109] In this way, according to setting method 3, terminal 200 can reduce the layer 2 processing time in multiple CG resources by, for example, reusing a TB (MAC PDU) generated by layer 2 processing in one CG resource among multiple CG resources in another CG resource, thereby reducing the processing time in terminal 200.

[0110] Since the processing time in terminal 200 can be reduced by reusing TB, for example, multiple CG resources available at a certain timing can be configured for terminal 200, thereby increasing the opportunities for transmitting uplink signals in terminal 200. As a result, even if, for example, a certain CG resource among multiple CG resources configured for terminal 200 cannot be used due to an LBT failure, if other CG resources are available, terminal 200 can transmit an uplink signal (for example, CG-PUSCH).

[0111] Therefore, according to setting method 3, even when multiple CG resources are configured, terminal 200 can reduce the processing time for CG-PUSCH transmission and increase the opportunities to transmit uplink signals, thereby improving communication reliability and reducing delays.

[0112] Setting methods 1 to 3 have been explained above.

[0113] In this embodiment, terminal 200 sets multiple CG resources (in other words, resource candidates) as units for performing LBT in an unlicensed band, and transmits an uplink signal (e.g., CG-PUSCH) in a CG resource determined to be usable by LBT among the multiple set CG resources.

[0114] This process allows terminal 200 to transmit an uplink signal using any one of the multiple configured CG resources (for example, a resource for which LBT has succeeded). In other words, terminal 200 can increase the opportunities to transmit an uplink signal. Therefore, for example, when operating a URLLC service in an unlicensed frequency band, even if interference occurs suddenly, the increased opportunities to transmit an uplink signal make it easier to satisfy the requirements of URLLC.

[0115] Furthermore, in this embodiment, terminal 200 can reduce the processing time for CG-PUSCH transmission, for example, by using common parameters, setting a TB size according to the CG resource to be set, or reusing TBs between multiple CG resources. This makes it easier to complete the processing for CG-PUSCH transmission from when the LBT result is determined until the start of CG-PUSCH transmission, even when multiple CG resources are set for terminal 200, for example.

[0116] (Embodiment 2) For example, if all channels (or RB sets) included in the BWP or CC targeted by carrier sensing (e.g., LBT) are busy, the base station and terminal may wait to transmit or receive until the channels become idle, which may increase the delay time.

[0117] In this embodiment, for example, a plurality of BWPs or CCs may be set for a terminal. Also, a method of increasing the possibility of detecting an idle channel by switching a BWP or CC that performs carrier sensing among a plurality of BWPs or CCs set for terminal 200 and increasing the chance of transmitting an uplink signal will be described.

[0118] In the configuration example of the base station and terminal according to the present embodiment, for example, some functions may be different from those in the first embodiment, and other functions may be the same as those in the first embodiment.

[0119] In base station 100 (FIG. 2), scheduling section 104 may control scheduling for terminal 200, for example, assuming a switching (or selection or decision) operation of a BWP or CC that performs carrier sensing in terminal 200.

[0120] In terminal 200 (Figure 3), transmission control unit 204 may, for example, determine the BWP or CC for which carrier sensing is to be performed based on the channel state (e.g., busy or idle) input from carrier sense unit 203, and instruct carrier sense unit 203 on the determination result (e.g., information regarding the BWP or CC for which carrier sensing is to be performed).

[0121] The carrier sense unit 203 may determine the BWP or CC for which carrier sense is to be performed, based on information input from the transmission control unit 204, for example.

[0122] [Example of Operation of Base Station 100 and Terminal 200] An example of the operation of base station 100 and terminal 200 having the above configuration will be described.

[0123] <Switching method 1> In the switching method 1, the terminal 200 may, for example, perform the BWP or CC performing the LBT in a time-division manner. In other words, the switching of the BWP or CC performing the LBT may be performed every specified period.

[0124] For example, terminal 200 may switch the BWP or CC performing the LBT at a certain time granularity (for example, 9 microseconds (us)). Note that the granularity for switching the BWP or CC performing the LBT is not limited to 9us, and may be other granularities.

[0125] In switching method 1, for example, it is assumed that a plurality of BWPs or CCs are active, and the BWP or CC for which terminal 200 is capable of LBT at a certain timing is any one of the active BWPs or CCs.

[0126] Examples of methods for switching the BWP or CC that performs LBT include the following.

[0127] Example 1: For example, terminal 200 may switch the BWP or CC for performing the LBT from among the set BWPs or CCs in accordance with an order determined by terminal 200.

[0128] For example, terminal 200 may perform LBT in a BWP or CC switched in any order among multiple set BWPs or CCs. Through this process, terminal 200 can use, for example, a BWP or CC that has succeeded in LBT earlier (in other words, a BWP or CC that has determined that the channel is idle) for transmitting an uplink signal.

[0129] Example 2: For example, terminal 200 may switch the BWP or CC for performing LBT from among the set BWPs or CCs in accordance with an order defined by a standard (or specification) or an order set by signaling.

[0130] For example, if the channel state of the BWP or CC currently subject to LBT is busy, the terminal 200 may perform LBT on the next BWP or CC. In other words, switching the BWP or CC to perform LBT includes, for example, performing LBT on another BWP or CC when a certain BWP is unavailable due to LBT.

[0131] The order of BWPs or CCs for which LBT is performed may follow, for example, the priority order of BWPs or CCs used for transmitting uplink signals. For example, by setting different orders between different terminals 200, different BWPs or CCs are more likely to be selected between terminals 200 at a certain timing, and the possibility of collision between transmission signals of multiple terminals 200 can be reduced.

[0132] FIG. 7 is a diagram showing an example of switching between BWPs or CCs performing LBT according to switching method 1. In FIG.

[0133] In Fig. 7, for example, BWP#0, BWP#1, and BWP#2 are set for terminal 200. Also, in Fig. 7, for example, the order of BWPs performing LBT is set to BWP#0, BWP#1, and BWP#2. Note that the number of BWPs set for terminal 200 is not limited to three, and may be another number.

[0134] In Fig. 7, terminal 200 may perform LBT in BWP#0, for example, and switch the BWP in which LBT is performed from BWP#0 to BWP#1 because the channel state is busy. Similarly, terminal 200 may perform LBT in BWP#1, for example, and switch the BWP in which LBT is performed from BWP#1 to BWP#2 because the channel state is busy. Terminal 200 may also perform LBT in BWP#2, for example, and transmit CG-PUSCH in BWP#2 because the channel state is idle.

[0135] In this way, in switching method 1, even if an LBT failure (channel busy) occurs, terminal 200 can improve the possibility of successful LBT by switching to another BWP or CC, and can increase the opportunities to transmit uplink signals.

[0136] Furthermore, in switching method 1, terminal 200 performs LBT on any one of the multiple BWPs or CCs set in accordance with the set order, thereby reducing power consumption compared to performing LBT at one timing for multiple BWPs or CCs set in terminal 200.

[0137] Although BWP and CC have been described here, switching method 1 may be applied to RB sets. For example, when terminal 200 cannot simultaneously perform LBT on multiple RB sets due to the processing capacity of terminal 200, the RB set for which LBT is performed may be switched in a time-division manner.

[0138] <Switching method 2> In the switching method 2, for example, the terminal 200 may switch the active BWP among the multiple BWPs based on an order defined or set in the standard.

[0139] In the switching method 2, for example, it is assumed that among a plurality of BWPs set in the terminal 200, one BWP is active.

[0140] For example, when the terminal 200 does not detect a DL burst, it may switch the active BWP among the multiple BWPs that have been set.

[0141] Here, the channel access method includes, for example, Frame based equipment (FBE) and Load based equipment (LBE, also called dynamic channel occupancy).

[0142] In FBE, base station 100 may acquire LBT and channel occupancy time (e.g., COT: Channel occupancy time) in a cycle called a Fixed frame period (FFP), for example. Terminal 200 may switch the active BWP based on the presence or absence of a COT structure indication (e.g., notification in DCI format 2_0) from base station 100 at the beginning of the FFP, for example. For example, when terminal 200 does not detect a COT structure indication, it may switch the active BWP to another BWP. On the other hand, terminal 200 may transmit a CG-PUSCH in a BWP in which a COT structure indication is detected, for example.

[0143] Also, in LBE, base station 100 can attempt to acquire COT at any timing, for example. Therefore, in LBE, terminal 200 has difficulty in determining a change in BWP at a fixed timing, as in FBE. Therefore, terminal 200 may switch the active BWP to another BWP, for example, based on a timer, if it does not receive a COT structure indication from the base station within a certain period from the last symbol of the currently set COT (or does not receive a notification indicating COT acquisition). On the other hand, terminal 200 may transmit CG-PUSCH in the current active BWP, for example, if it receives a COT structure indication from the base station within a certain period from the last symbol of the COT (or receives a notification indicating COT acquisition).

[0144] For example, the switching order of active BWPs in terminal 200 may be set in advance from base station 100 to terminal 200. This setting allows the base station 100 and terminal 200 to agree on the recognition of BWP switching. In addition, the switching order of active BWPs may be set, for example, semi-statically or dynamically.

[0145] Semi-static setting of the switching order of active BWP has an advantage that, for example, the recognition between the base station 100 and the terminal 200 is less likely to differ.

[0146] On the other hand, in dynamic setting of the switching order of active BWPs, for example, a candidate BWP to be switched (for example, BWP index) may be notified in advance from base station 100 to terminal 200 using PDCCH or GC-PDCCH (Group common PDCCH). This allows base station 100 to set a BWP to be changed to active BWP for terminal 200 based on the availability of the channel (whether the channel is idle or not). This allows terminal 200 to reduce a situation in which transmission and reception are not possible due to LBT failure.

[0147] FIG. 8 is a diagram showing an example of switching of an Active BWP according to the switching method 2 (for example, in the case of LBE).

[0148] In Fig. 8, for example, BWP#0, BWP#1, and BWP#2 are set for terminal 200. Also, in Fig. 8, for example, BWP#1 is set as the Active BWP at the beginning of the slot. Note that the number of BWPs set for terminal 200 is not limited to three, and may be another number.

[0149] 8A shows, for example, a case where LBT failure does not occur. In this case, the active BWP for terminal 200 remains BWP #1, and there is no need to switch BWPs. Therefore, terminal 200 may transmit CG-PUSCH in BWP #1, for example.

[0150] On the other hand, FIG. 8(b) illustrates, for example, a state in which an LBT failure occurs in BWP#1 (for example, a state in which base station 100 cannot acquire a COT and terminal 200 does not receive a COT structure indication). In this case, for example, terminal 200 may switch the active BWP to BWP#2 when a certain time elapses (for example, a timer expires) without receiving a COT structure indication. For example, when terminal 200 receives a COT structure indication at a preset PDCCH reception timing in BWP#2, transmission and reception in BWP#2 becomes possible.

[0151] 8B, even after an LBT failure occurs in BWP #1, the terminal 200 can transmit and receive in another BWP #2, so that the terminal 200 can continue transmitting and receiving with reduced delay time. Note that switching between other BWPs may be performed in the same manner.

[0152] As described above, in switching method 2, even if LBT fails in the active BWP, terminal 200 can increase the chance of transmitting an uplink signal by switching the active BWP to another BWP. Also, in switching method 2, LBT is performed in the active BWP, so power consumption can be reduced compared to when LBT is performed at a certain timing in multiple BWPs set in terminal 200.

[0153] Note that switching method 2 is not limited to changing (or switching) the BWP, and may be applied to changing the CC, for example. For example, even if multiple CCs can be set to active depending on the processing capacity of terminal 200 (UE), by switching an active CC (for example, a secondary cell (Scell)) as in the above-mentioned BWP, the number of CCs that transmit and receive signals at one timing in terminal 200 can be reduced, thereby reducing power consumption.

[0154] (Embodiment 3) For example, another example of a method for increasing the transmission opportunities of an uplink signal in terminal 200 is to share CG resources between terminals 200. In configured grant transmission, the same resources can be set for multiple terminals 200, for example.

[0155] Fig. 9 is a diagram showing an example in which four CG resources (here, an RB set) are allocated to two terminals 200 (e.g., UE#0 and UE#1). Fig. 9(a) shows an example in which one terminal 200 is allocated to one CG resource without sharing the CG resource between the terminals, and Fig. 9(b) shows an example in which four CG resources are shared by two terminals 200.

[0156] For example, in FIG. 9(a), when RB sets #0 and #1 are busy and RB sets #2 and #3 are idle, the number of available CG resources is two, RB sets #2 and #3, so UE #0 waits to transmit an uplink signal. On the other hand, in FIG. 9(b), when RB sets #0 and #1 are busy and RB sets #2 and #3 are idle, both UE #0 and UE #1 can transmit uplink signals using RB sets #2 and #3. Here, in FIG. 9(b), for example, when UE #0 and UE #1 use the CG resources of the same RB set, transmission may collide between UE #0 and UE #1.

[0157] In this embodiment, a method for suppressing transmission collisions between a plurality of terminals when a CG resource is shared among the plurality of terminals will be described.

[0158] In the configuration example of the base station and terminal according to the present embodiment, for example, some functions may be different from those in the first embodiment, and other functions may be common to the first embodiment.

[0159] In base station 100 (Figure 2), scheduling unit 104 may control scheduling for terminal 200 by assuming the selection operation of a CG resource to be used for transmission in terminal 200 from among multiple CG resources set in terminal 200, based on a set or specified selection method (in other words, conditions or rules).

[0160] In terminal 200 (FIG. 3), transmission control unit 204 selects a CG resource to be used for transmission from among multiple CG resources set in terminal 200, based on, for example, information (for example, CG setting information) input from control information storage unit 205. Transmission control unit 204 outputs information related to the selected CG resource to encoding / modulation unit 207, for example.

[0161] [How to select CG resources] An example of a method for selecting a CG resource in the terminal 200 having the above configuration will be described.

[0162] For example, when multiple CG resources are configured in terminal 200, terminal 200 may select a CG resource for transmitting a CG-PUSCH based on one or more selection methods (in other words, selection rules).

[0163] <Selection method 1> In selection method 1, terminal 200 may select a CG resource to be used for transmitting a CG-PUSCH, for example, based on information (for example, priority) related to priority (in other words, selection order) included in a CG configuration.

[0164] For example, when different priorities are set for multiple CG resources, the terminal 200 may select the CG resources in descending order of priority.

[0165] In Rel. 16, for example, two priority values, high and low, can be set for the terminal 200 by the CG setting information.

[0166] According to selection method 1, for example, a different priority can be set for each of a plurality of CG resources shared by a plurality of terminals 200. This makes it easier for different terminals 200 to select different CG resources at a certain timing, for example, and can reduce transmission collisions between terminals 200. Also, for example, by using existing signaling to notify the priority of the CG resource, terminal 200 can select a CG resource while suppressing an increase in signaling overhead.

[0167] The priority value may be set to, for example, three or more levels.

[0168] <Selection method 2> In selection method 2, terminal 200 may select a CG resource to be used for transmitting a CG-PUSCH, for example, based on an index (for example, ConfiguredGrantConfigIndex) included in a CG configuration.

[0169] For example, when each CG resource is set based on a plurality of CG settings, the terminal 200 may select a CG resource corresponding to a CG setting with a lower index (or a CG resource with a higher index) in that order.

[0170] According to selection method 2, for example, a different index can be set for each of a plurality of CG resources for each terminal 200. This makes it easier for different terminals 200 to select different CG resources at a certain timing, for example, and can reduce transmission collisions between terminals 200. In addition, for example, by using existing signaling to notify of an index corresponding to a CG resource, terminal 200 can select a CG resource while suppressing an increase in signaling overhead.

[0171] <Selection method 3> In selection method 3, terminal 200 may select a CG resource to be used for transmitting a CG-PUSCH based on a selection order set by base station 100, for example.

[0172] For example, the selection order may be set semi-statically or dynamically.

[0173] Furthermore, the selection order may be set based on the location where a CG resource such as an RB set, a BWP, or a CC is placed, or may be set for each CG setting.

[0174] As an example of setting the selection order based on the position where the CG resource is arranged, when the selection order is set for each RB set, the selection order may be set as {RB set#0, RB set#1, RB set#2}={1, 2, 0}. When selecting an RB set from a low value of the selection order, for example, if RB set#2 is idle and a CG resource is set, terminal 200 may transmit a CG-PUSCH using the CG resource of RB set#2. Also, when RB set#2 is busy, for example, terminal 200 may select RB set#0 corresponding to the next selection order. For RB sets#0 and #1, terminal 200 may control the transmission of the CG-PUSCH based on the result of the LBT, similar to RB set#2.

[0175] Also, as an example of setting the selection order for each CG setting, even if CG resources are set to multiple RB sets by one CG setting (e.g., corresponding to one index), the selection order can be set individually for each CG resource based on selection method 3.

[0176] Furthermore, semi-static setting of the selection order has the advantage that the recognition between the base station 100 and the terminal 200 is less likely to differ, for example.

[0177] On the other hand, in dynamic setting of the selection order, for example, information on the selection order may be notified from base station 100 to terminal 200 by PDCCH or GC-PDCCH. Also, for example, base station 100 may semi-statically set combinations (or sets or candidates) of the selection order in terminal 200, and dynamically notify an index indicating the combination by PDCCH or GC-PDCCH. This makes it possible to suppress an increase in the number of bits of the PDCCH or GC-PDCCH.

[0178] Furthermore, in dynamic setting of the selection order, the selection order can be set based on, for example, the usage status of CG resources between terminals 200 or the occurrence status of data transmission and reception, thereby reducing the possibility of CG transmission collisions between terminals 200.

[0179] Furthermore, the dynamic setting of the selection order may include the unusable state of the CG resources in addition to the use order of the CG resources. For example, for a certain terminal 200, the selection order may be set as {RB set#0, RB set#1, RB set#2}={1, "NA", 0}, and RB set#1 may be set as unavailable (NA). This allows RB set#1 to be allocated to other terminals 200, so that when there are few resources available for terminal 200, it is possible to suppress transmission collisions between terminals 200.

[0180] <Selection method 4> In selection method 4, terminal 200 may select a CG resource to be used for transmitting a CG-PUSCH based on, for example, an index of an RB set and an offset specific to a UE.

[0181] For example, if each terminal 200 selects a CG resource based on the index of the RB set, the selection order of CG resources may be the same between terminals 200. Therefore, in selection method 4, terminal 200 determines the selection order based on, for example, the index of the RB set and an offset value for each terminal 200. This allows the selection order to vary between terminals 200, making it possible to suppress transmission collisions between terminals 200.

[0182] The terminal 200 may calculate the metric value corresponding to the selection order based on, for example, the following equation (4). {((RB set index) + offset) mod (the number of RB sets)} (4)

[0183] Terminal 200 may select, for example, a CG resource of an RB set with a lower (or higher) metric value among RB sets in which a CG resource is available (for example, an RB set in which a CG resource is configured and the LBT result is idle).

[0184] FIG. 10 is a diagram showing an example of selection of a CG resource according to the selection method 4. In FIG.

[0185] 10, a case will be described in which three terminals 200 (for example, UE#0, UE#1, and UE#2) share an RB set. For example, four RB sets, RB sets #0 to #3, are configured in UE#0 and UE#1. Also, RB sets #0 to #2 are configured in UE#2. In other words, RB set #3 is not configured in UE#2.

[0186] Moreover, one CG resource is set in each RB set in the slot shown in Fig. 10. Note that the number of CG resources set in an RB set may be two or more.

[0187] 10, offset values ​​of 0, 1 and 2 are set for UE#0, UE#1 and UE#2, respectively. Note that the offset value is not limited to any one of 0 to 2 and may be another value.

[0188] In this case, the metric value set for each RB set in each of UE#0, UE#1, and UE#2 may be calculated according to equation (4). For example, as shown in Fig. 10, metric values ​​0, 1, 2, and 3 are set for RB sets #0 to #3 in UE#0, metric values ​​1, 2, 3, and 0 are set for RB sets #0 to #3 in UE#1, and metric values ​​2, 0, and 1 are set for RB sets #0 to #2 in UE#2.

[0189] For example, in the slot shown in Fig. 10, UE #0 selects RB set #0, UE #1 selects RB set #3, and UE #2 selects RB set #1. For example, in RB set #0 shown in Fig. 10, the metric values ​​(in other words, the selection order) in each UE are different. The same is true for the other RB sets. Therefore, in the slot shown in Fig. 10, it is possible to avoid transmission collisions between UEs.

[0190] The offset value may be explicitly notified to terminal 200 or may be implicitly determined in terminal 200, for example.

[0191] For example, in the method of explicitly notifying the offset value, base station 100 may notify terminal 200 of the offset value by semi-static setting or by dynamic setting. In the dynamic setting, the offset value may be notified using, for example, the PDCCH or GC-PDCCH.

[0192] Semi-static setting of the offset value has the advantage that, for example, the recognition between base station 100 and terminal 200 is less likely to differ.

[0193] On the other hand, dynamic setting of the offset value makes it possible to set the offset value based on, for example, the usage status of CG resources between terminals 200 or the occurrence status of data transmission and reception, thereby reducing the possibility of CG transmission collision between terminals 200.

[0194] Also, the method of implicitly determining the offset value may include, for example, a method of using a UE ID as the offset value, or a method of using a Radio Network Temporary Identifier (RNTI) as the offset value. Note that the information associated with the offset value is not limited to the UE ID and the RNTI, and may be other UE-specific information. For example, the terminal 200 may determine the offset value associated with the UE-specific information. In this way, the base station 100 can notify the terminal 200 of the offset value while suppressing, for example, an increase in signaling overhead.

[0195] Also, for example, different values ​​may be set for the offset value between slots. For example, a different pseudo-random number may be added to the set offset value for each slot. This causes the order of the RB offset selected by terminal 200 to change between slots, thereby reducing the probability of collisions occurring in successive transmissions from one terminal 200.

[0196] Also, for example, terminal 200 may determine not to transmit an uplink signal in an RB set whose metric value is greater than a threshold. For example, in Fig. 10, each UE may determine not to transmit an uplink signal in an RB set whose metric value is 2 or more. For example, in a case where the number of unusable RB sets increases due to LBT failure and transmission collisions between terminals 200 may occur when multiple terminals 200 transmit, each RB set can be divided into terminals that can transmit and terminals that cannot transmit, thereby suppressing transmission collisions between terminals 200.

[0197] The CG resource selection methods 1 to 4 have been described above.

[0198] As described above, according to this embodiment, when CG resources are shared by a plurality of terminals 200, the probability of collisions occurring in transmissions between the terminals 200 can be reduced, thereby improving the efficiency of resource usage.

[0199] An embodiment of the present disclosure has been described above.

[0200] (Other embodiments) In the above-described embodiment, the uplink signal is not limited to an uplink data channel such as PUSCH or CG-PUSCH, but may be another signal or channel.

[0201] In addition, in the above-described embodiments, the "higher layer signal" may be called, for example, an "RRC signal" or a "MAC signal".

[0202] In the above embodiment, the control signal may be a PDCCH that transmits DCI of the physical layer, or may be a MAC or RRC of a higher layer.

[0203] In the above embodiment, the base station may be a TRP (Transmission Reception Point), a cluster head, an access point, an RRH (Remote Radio Head), an eNodeB (eNB), a gNodeB (gNB), a BS (Base Station), a BTS (Base Transceiver Station), a parent device, a gateway, etc. In addition, in sidelink communication, a terminal may act instead of a base station.

[0204] In the above embodiment, the reference signal is a signal known to both the base station and the mobile station, and may be called an RS (Reference Signal) or a pilot signal. The reference signal is not limited to the DMRS, and may be a CSI-RS (Channel State Information - Reference Signal), a TRS (Tracking Reference Signal), a PTRS (Phase Tracking Reference Signal), or a CRS (Cell-specific Reference Signal).

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

[0206] The above embodiment may be applied to communication using a sidelink used for V2X (Vehicle to Everything) or terminal-to-terminal communication. In that case, PDCCH may be read as PSCCH (Physical Sidelink Control Channel), PUSCH / PDSCH as PSSCH (Physical Sidelink Shared Channel), and PUCCH as PSFCH (Physical Sidelink Feedback Channel).

[0207] Moreover, the above-described embodiments may be applied in combination.

[0208] <5G NR system architecture and protocol stack> 3GPP continues to work on the next release of the fifth generation of mobile phone technology (also known simply as "5G"), which includes the development of a new radio access technology (NR) that will operate in the frequency range up to 100 GHz. The first version of the 5G standard was completed at the end of 2017, which will allow for the prototyping and commercial deployment of 5G NR compliant devices (e.g. smartphones).

[0209] For example, the system architecture generally assumes a Next Generation - Radio Access Network (NG-RAN) with 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 by an Xn interface. The gNBs are also connected to a Next Generation Core (NGC) by a Next Generation (NG) interface, more specifically to an Access and Mobility Management Function (AMF) (e.g., a specific core entity performing AMF) by an NG-C interface, and to a User Plane Function (UPF) (e.g., a specific core entity performing UPF) by an NG-U interface. The NG-RAN architecture is shown in Figure 11 (see, e.g., 3GPP TS 38.300 v15.6.0, section 4).

[0210] The NR user plane protocol stack (see, for example, 3GPP TS 38.300, section 4.4.1) includes the Packet Data Convergence Protocol (PDCP) (see section 6.4 of TS 38.300), Radio Link Control (RLC) (see section 6.3 of TS 38.300), and Medium Access Control (MAC) (see section 6.2 of TS 38.300) sublayers, which are terminated on the network side at the gNB. A new Access Stratum (AS) sublayer (Service Data Adaptation Protocol (SDAP)) is also introduced on top of PDCP (see, for example, 3GPP TS 38.300, section 6.5). A control plane protocol stack is also defined for NR (see, for example, TS 38.300, section 4.4.2). An overview of Layer 2 functions is given in section 6 of TS 38.300. The functions of the PDCP, RLC and MAC sublayers 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.

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

[0212] 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 the transmission of a particular transport channel, and each transport channel is mapped to a corresponding physical channel. For example, the physical channels include the PRACH (Physical Random Access Channel), PUSCH (Physical Uplink Shared Channel), and PUCCH (Physical Uplink Control Channel) as uplink physical channels, and the PDSCH (Physical Downlink Shared Channel), PDCCH (Physical Downlink Control Channel), and PBCH (Physical Broadcast Channel) as downlink physical channels.

[0213] 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 rates, latency, and coverage. For example, eMBB is expected to support peak data rates (20 Gbps in downlink and 10 Gbps in uplink) and effective (user-experienced) data rates that are about three times higher than those offered by IMT-Advanced. On the other hand, for URLLC, more stringent requirements are imposed on ultra-low latency (0.5 ms for user plane latency in UL and DL, respectively) and high reliability (1-10-5 within 1 ms). Finally, mMTC may require preferably high connection density (1,000,000 devices / km2 in urban environments), wide coverage in adverse environments, and extremely long battery life (15 years) for low-cost devices.

[0214] 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 other use cases. 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 called TTI) than mMTC services. Furthermore, deployment scenarios with large channel delay spreads may preferably require a longer CP length than scenarios with small delay spreads. 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... 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.

[0215] In the new radio system 5G-NR, for each numerology and each carrier, a resource grid of subcarriers and OFDM symbols is defined for the uplink and downlink, respectively. 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).

[0216] <Functional separation between NG-RAN and 5GC in 5G NR> Figure 12 shows the functional separation between NG-RAN and 5GC. The logical node of NG-RAN is gNB or ng-eNB. 5GC has logical nodes AMF, UPF, and SMF.

[0217] For example, the 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, encryption, and integrity protection of data; - Selection of the AMF at UE attach time if routing to the AMF cannot be determined from information provided by the UE; - Routing of user plane data towards the UPF; - Routing of control plane information towards AMF; - Setting up and tearing down connections; - Scheduling and sending paging messages; - Scheduling and transmission of system broadcast information (AMF or Operation, Admission, Maintenance (OAM) origin); - Configuration of measurements and measurement reporting for mobility and scheduling; - Transport level packet marking in the uplink; - Session management; - Support for network slicing; - Management of QoS flows and their mapping to data radio bearers; - Support for UEs in RRC_INACTIVE state; - NAS message delivery function; - Sharing of radio access networks; - Dual connectivity; - Close cooperation between NR and E-UTRA.

[0218] The Access and Mobility Management Function (AMF) hosts the following main functions: - Ability to terminate Non-Access Stratum (NAS) signalling; - NAS signaling security; - Access Stratum (AS) security control; - 3GPP Core Network (CN) inter-node signalling for mobility between access networks; - Reachability to idle mode UEs (including control and execution of paging retransmissions); - Managing the registration area; - Support for intra-system and inter-system mobility; - Access authentication; - Access authorization including roaming privilege checks; - Mobility management control (subscription and policies); - Support for network slicing; - Select the Session Management Function (SMF).

[0219] Additionally, the User Plane Function (UPF) hosts the following main functions: - anchor points for intra-RAT mobility / inter-RAT mobility (if applicable); - External PDU (Protocol Data Unit) Session Points 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 for supporting multi-homed PDU session; - QoS processing for the user plane (e.g., packet filtering, gating, UL / DL rate enforcement); - Verification of uplink traffic (mapping to the QoS flow of the SDF); - Downlink packet buffering and trigger function for downlink data notification.

[0220] Finally, the Session Management Function (SMF) hosts the following main functions: - Session management; - IP address allocation and management for the UE; - Selection and control of the UPF; - Traffic steering setting function in the User Plane Function (UPF) for routing traffic to the appropriate destination; - Enforcement of control part policies and QoS; - Notification of downlink data.

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

[0222] RRC is a higher layer signaling (protocol) used for UE and gNB configuration. With this transition, the AMF prepares UE context data (which includes, for example, PDU session context, security keys, UE Radio Capability, UE Security Capabilities, etc.) and sends it to the gNB 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 reconfigures to set up Signaling Radio Bearer 2 (SRB2) and Data Radio Bearer (DRB) by sending an RRCReconfiguration message to the UE and receiving an RRCReconfigurationComplete from the UE. For signaling-only connections, the steps related to RRCReconfiguration are omitted since SRB2 and DRB are not set up. Finally, the gNB informs the AMF that the setup procedure is complete with an INITIAL CONTEXT SETUP RESPONSE.

[0223] Therefore, the present disclosure provides an entity (e.g., AMF, SMF, etc.) of a 5th Generation Core (5GC), comprising: a control circuit that operatively establishes a Next Generation (NG) connection with a gNodeB; and a transmitter that operatively 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. Then, the UE transmits in uplink or receives in downlink based on the resource allocation configuration.

[0224] <IMT usage scenarios after 2020> Figure 14 shows some of the use cases for 5G NR. The 3rd generation partnership project new radio (3GPP NR) considers three use cases that were envisioned by IMT-2020 to support a wide variety of services and applications. The first phase of specifications for enhanced mobile-broadband (eMBB) has been completed. Current and future work includes standardization for ultra-reliable and low-latency communications (URLLC) and massive machine-type communications (mMTC), in addition to expanding support for eMBB. Figure 14 shows some examples of envisioned usage scenarios for IMT beyond 2020 (see e.g. ITU-R M.2083 Figure 12).

[0225] URLLC use cases have stringent requirements for performance such as throughput, latency, and availability. URLLC use cases are envisioned as one of the enabling technologies for future applications such as wireless control of industrial production or manufacturing processes, remote medical surgery, automation of 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 UL (uplink) and 0.5 ms on the DL (downlink). The overall URLLC requirement for a single packet transmission is a block error rate (BLER) of 1E-5 for a packet size of 32 bytes with a user plane latency of 1 ms.

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

[0227] Also, technology enhancements targeted by NR URLLC aim at improving latency and improving reliability. Technology enhancements for improving latency include configurable numerology, non-slot-based scheduling with flexible mapping, grant-free (configured grant) uplink, slot-level repetition in data channel, and pre-emption in downlink. Pre-emption means that a transmission with already allocated resources is stopped and the already allocated resources are used for other transmissions with lower latency / higher priority requirements that are requested later. Thus, a transmission that was already allowed is preempted by a later transmission. Pre-emption 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 improving reliability include dedicated CQI / MCS tables for a target BLER of 1E-5.

[0228] The use case of mMTC (massive machine type communication) is characterized by a very large number of connected devices transmitting relatively small amounts of data that are typically not sensitive to delays. The devices are required to be low-cost and have a very long battery life. From an NR perspective, the use of very narrow bandwidth portions is one solution that allows UEs to save power and extend battery life.

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

[0230] Further use cases with more stringent requirements are envisaged for NR URLLC, such as factory automation, transportation and power distribution, such as high reliability (up to 10-6 level of reliability), high availability, packet size up to 256 bytes, time synchronization up 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 in the targeted user plane)).

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

[0232] <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) and QoS flows that do not require a guaranteed flow bit rate (non-GBR QoS flows). Therefore, at the NAS level, a QoS flow is the finest-grained QoS differentiation in a PDU session. A QoS flow is identified within a PDU session by a QoS Flow ID (QFI) that is carried in an encapsulation header via the NG-U interface.

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

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

[0235] Figure 15 further illustrates further functional units of the 5G architecture: 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.

[0236] Therefore, the present disclosure provides an application server (e.g., an AF in a 5G architecture) comprising: a transmitter that, when operated, 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 the 5GC functions (e.g., NEF, AMF, SMF, PCF, 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, when operated, performs a service using the established PDU session.

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

[0238] The method of integration is not limited to LSI, but may be realized by a dedicated circuit, a general-purpose processor, or a dedicated processor. Also, after LSI manufacturing, a programmable FPGA (Field Programmable Gate Array) or a reconfigurable processor that can reconfigure the connections and settings of circuit cells inside the LSI may be used. The present disclosure may be realized as digital processing or analog processing.

[0239] Furthermore, if a new integrated circuit technology that can replace LSI appears due to the progress of semiconductor technology or a derivative technology, it is possible to integrate the functional blocks using that technology. The application of biotechnology is also a possibility.

[0240] The present disclosure may be implemented in any type of apparatus, device, or system having a communication function (collectively referred to as a communication apparatus). The communication apparatus may include a radio transceiver and processing / control circuitry. The radio transceiver may include a receiver and a transmitter, or both as 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, etc.), tablets, personal computers (PCs) (e.g., laptops, desktops, notebooks, etc.), cameras (e.g., digital still / video cameras), digital players (e.g., digital audio / video players), wearable devices (e.g., wearable cameras, smart watches, tracking devices, etc.), game consoles, digital book readers, telehealth and telemedicine devices, communication-enabled vehicles or mobile conveyances (e.g., cars, airplanes, boats, etc.), and combinations of the above devices.

[0241] Communications Equipment includes, but is not limited to portable or mobile equipment, non-portable or fixed equipment, devices and systems of any kind, such as smart home devices (appliances, lighting equipment, smart meters or metering devices, control panels, etc.), vending machines and any other "Things" that may exist on an Internet of Things (IoT) network.

[0242] Communications include data communications via cellular systems, wireless LAN systems, communications satellite systems, etc., as well as data communications via combinations of these.

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

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

[0245] A terminal according to one embodiment of the present disclosure includes a control circuit that determines a usable resource candidate by carrier sense from among multiple resource candidates based on a unit of carrier sense, and a transmission circuit that transmits an uplink signal using the usable resource candidate.

[0246] In one embodiment of the present disclosure, the control circuit controls transmission of the uplink signal based on a configuration of the plurality of resource candidates.

[0247] In one embodiment of the present disclosure, the multiple resource candidates are associated with a common parameter.

[0248] In one embodiment of the present disclosure, the control circuit determines a size of the uplink signal based on the number of the plurality of resource candidates.

[0249] In an embodiment of the present disclosure, the control circuit uses a transport block generated in any one of the plurality of resource candidates as a transport block of another resource candidate.

[0250] In an embodiment of the present disclosure, the control circuit switches a resource candidate for performing the carrier sense among the plurality of resource candidates.

[0251] In an embodiment of the present disclosure, switching the resource candidate for performing carrier sensing includes performing carrier sensing on a second resource candidate when a first resource candidate is unavailable as a result of the carrier sensing.

[0252] In one embodiment of the present disclosure, the resource candidates for performing carrier sensing are switched at regular intervals.

[0253] In one embodiment of the present disclosure, the control circuit switches an active resource candidate among the plurality of resource candidates according to a certain order.

[0254] In one embodiment of the present disclosure, the multiple resource candidates are shared by multiple terminals including the terminal, and the control circuit selects a resource candidate to be used for transmitting the uplink signal from the multiple resource candidates according to an order that differs among the multiple terminals.

[0255] In a communication method relating to one embodiment of the present disclosure, a terminal sets multiple resource candidates as units for performing carrier sensing in an unlicensed band, and transmits an uplink signal using a usable resource candidate detected by the carrier sensing among the multiple resource candidates.

[0256] The disclosures of the specification, drawings and abstract contained in Japanese Patent Application No. 2020-077694, filed on April 24, 2020, are incorporated herein by reference in their entirety. [Industrial Applicability]

[0257] One embodiment of the present disclosure is useful in wireless communication systems. [Explanation of symbols]

[0258] 100 base stations 101,201 Receiver 102,202 Demodulation and decoding section 103,203 Carrier Sense Department 104 Scheduling Department 105,205 Control information storage unit 106,206 Data and control information generation unit 107,207 Coding and modulation section 108,208 Transmitter 200 terminals 204 Transmission control section

Claims

1. A control circuit that determines a usable resource candidate by carrier sense from among a plurality of resource candidates based on a unit of carrier sense; a transmission circuit for transmitting an uplink signal in the available resource candidate; Equipped with The control circuit determines a size of the uplink signal based on a number of the plurality of resource candidates. Terminal.

2. A control circuit that determines a usable resource candidate by carrier sense from among a plurality of resource candidates based on a unit of carrier sense; a transmission circuit for transmitting an uplink signal in the available resource candidate; Equipped with The control circuit uses a transport block generated in any one of the plurality of resource candidates as a transport block of another resource candidate. Terminal.

3. The control circuit switches a resource candidate for performing the carrier sense among the plurality of resource candidates. A terminal according to claim 1 or 2.

4. The switching of the resource candidate for which carrier sensing is performed includes performing carrier sensing on a second resource candidate when a first resource candidate is unavailable as a result of the carrier sensing. The terminal according to claim 3.

5. The switching of the resource candidates for performing the carrier sense is performed at regular intervals. The terminal according to claim 3.

6. The control circuit switches an active resource candidate among the plurality of resource candidates in accordance with a certain order. A terminal according to claim 1 or 2.

7. The plurality of resource candidates are shared by a plurality of terminals including the terminal; The control circuit selects, from the plurality of resource candidates, a resource candidate to be used for transmitting the uplink signal according to an order that differs among the plurality of terminals. A terminal according to claim 1 or 2.

8. The terminal is determining a usable resource candidate by carrier sense from among a plurality of resource candidates based on a unit of carrier sense; Transmitting an uplink signal on the available resource candidates; A size of the uplink signal is determined based on the number of the plurality of resource candidates. Communication methods.

9. The terminal comprises: determining a usable resource candidate by carrier sensing from among a plurality of resource candidates based on a unit of carrier sensing; Transmitting an uplink signal on the available resource candidates; A transport block generated in any one of the plurality of resource candidates is used for a transport block of another resource candidate. Communication methods.

Citation Information

Patent Citations

  • Transmission adaptation and grant-free access

    US20200077437A1