Terminal and communication method
Patent Information
- Application Number
- IN202217042177
- Authority / Receiving Office
- IN · IN
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2022-07-22
- Publication Date
- 2026-10-23
- Estimated Expiration
- 2040-01-23
AI Technical Summary
In NR-U wireless communication systems, determining and applying an appropriate Cyclic Prefix (CP) extension value for uplink transmission is challenging, especially before Radio Resource Control (RRC) settings are executed, due to varying communication situations.
A terminal with a receiving unit and a control unit that determines a CP extension value for uplink transmission, allowing it to apply this value dynamically based on communication conditions, even before RRC settings are configured.
Enables effective determination and application of CP extension values in wireless communication systems, enhancing communication efficiency by adapting to changing conditions without relying on pre-configured RRC settings.
Abstract
Description
The present invention relates to a terminal and communication method in a wireless communication system.Background technology
[0002] NR (New Radio) (also called "5G"), which is the successor system of LTE (Long Term Evolution), has the following requirements: large-capacity system, high-speed data transmission speed, low delay, simultaneous operation of many terminals. Technologies that satisfy connection, low cost, power saving, etc. are being studied.
[0003] In addition, in the existing LTE system, in order to expand the frequency band, a frequency band (unlicensed band, unlicensed band) different from the frequency band (licensed band) licensed by the telecommunications carrier (operator) (Unlicensed carrier, also called unlicensed CC) is supported.As an unlicensed band, for example, Wi-Fi (registered trademark) or Bluetooth (registered trademark) can be used2. .4 GHz band or 5 GHz band, 6 GHz band, etc. are envisioned.
[0004] Specifically, Rel-13 supports Carrier Aggregation (CA) that integrates carriers (CC) of licensed bands and carriers (CC) of unlicensed bands. Such communication using an unlicensed band together with a licensed band is called License-Assisted Access (LAA).
[0005] In a wireless communication system that performs communication using an unlicensed band together with a licensed band, a base station apparatus (downlink) and a user terminal (uplink) communicate with another apparatus (e.g., base station) before transmitting data in the unlicensed band. Channel sensing (carrier sensing) is performed in order to confirm the presence or absence of transmission from station equipment, user terminals, Wi-Fi equipment, etc.). As a result of sensing, when it is confirmed that there is no transmission from other devices, a transmission opportunity can be acquired and transmission can be performed. This operation is called LBT (Listen Before Talk). In NR, a system that supports unlicensed bands is called an NR-U system.prior art documentsNon-patent literature
[0006] Non-Patent Document 1: 3GPP TS 38.331 V15.8.0 (2019-12)Non-Patent Document 2: 3GPP TS 38.212 V16.0.0 (2019-12)Non-Patent Document 3: 3GPP TS 38.213 V16.0.0 (2019-12)Non-Patent Document 4: 3GPP TS 37.213 V16.0.0 (2019-12)SUMMARY OF THE INVENTIONProblems to be Solved by the Invention
[0007] In NR-U, LBT gaps based on CP extension (Cyclic Prefix extension) are being considered for terminal UL transmission. For example, at least for CP extension before dynamically scheduled PUSCH (Physical Uplink Shared Channel) transmission, the CP extension may be arranged in the first symbol of PUSCH allocation notified by SLIV (Start and Length Indicator). . At this time, the CP extension period (time length) is notified from the base station to the terminal by RRC (Radio Resource Control) signaling and downlink control information (DCI). On the other hand, depending on the communication situation, the terminal needs to set the CP extension period before the RRC setting is executed.
[0008] The present invention has been made in view of the above points, and aims to determine a CP extension (Cyclic Prefix extension) value and apply it to communication in a wireless communication system.Means to solve problems
[0009] According to the disclosed technology, a receiving unit that receives information for allocating uplink transmission from a base station; A terminal is provided that includes a control unit that determines a CP extension value, and a transmission unit that performs the uplink transmission by applying the determined CP extension value.The invention's effect
[0010] According to the disclosed technology, a CP extension (Cyclic Prefix extension) value can be determined and applied to communication in a wireless communication system.Brief description of the drawing
[0011] 1 is a diagram showing a configuration example of a radio communication system according to an embodiment of the present invention; FIG.2 is a diagram for explaining a wireless communication system according to an embodiment of the present invention; FIG.3 is a diagram for explaining a multi-TTI grant; FIG.4 is a sequence diagram for explaining an example of signaling in the embodiment of the present invention; FIG.5 is a flowchart for explaining an operation example (1) of terminal 20 according to the embodiment of the present invention; FIG.6 is a flowchart for explaining an operation example (2) of terminal 20 according to the embodiment of the present invention; FIG.7 is a flowchart for explaining an operation example (3) of terminal 20 according to the embodiment of the present invention; FIG.8 is a diagram for explaining an example of CP extension in the embodiment of the present invention; FIG.9 is a diagram showing an example of a functional configuration of base station 10 according to the embodiment of the present invention; FIG.10 is a diagram showing an example of a functional configuration of terminal 20 according to the embodiment of the present invention; FIG.11 is a diagram showing an example of a hardware configuration of base station 10 or terminal 20 according to the embodiment of the present invention; FIG.MODE FOR CARRYING OUT THE INVENTION
[0012] Embodiments of the present invention will be described below with reference to the drawings. In addition, the embodiment described below is an example, and the embodiment to which the present invention is applied is not limited to the following embodiment.
[0013] Existing technologies are appropriately used for the operation of the wireless communication system according to the embodiment of the present invention. However, the existing technology is, for example, existing LTE, but is not limited to existing LTE. In addition, the term “LTE” used in this specification has a broad meaning including LTE-Advanced and LTE-Advanced and subsequent systems (eg, NR) unless otherwise specified.
[0014] Further, in the embodiments of the present invention described below, SS (Synchronization signal), PSS (Primary SS), SSS (Secondary SS), PBCH (Physical broadcast channel), PRACH (Physical terms such as random access channel), PDCCH (Physical Downlink Control Channel), PDSCH (Physical Downlink Shared Channel), PUCCH (Physical Uplink Control Channel), and PUSCH (Physical Uplink Shared Channel). This is for convenience of description, and signals, functions, etc. similar to these may be referred to by other names. Also, the above terms in NR correspond to NR-SS, NR-PSS, NR-SSS, NR-PBCH, NR-PRACH, and so on. However, even a signal used for NR is not necessarily specified as "NR-".
[0015] Further, in the embodiment of the present invention, the duplex system may be a TDD (Time Division Duplex) system, an FDD (Frequency Division Duplex) system, or other (for example, Flexible Duplex etc.) method may be used.
[0016] Further, in the embodiment of the present invention, "configuring" wireless parameters and the like may mean that predetermined values are preset (Pre-configure), and the base station 10 or A wireless parameter notified from the terminal 20 may be set.
[0017] FIG. 1 is a diagram showing a configuration example of a wireless communication system according to an embodiment of the present invention. A wireless communication system according to an embodiment of the present invention includes a base station 10 and terminals 20, as shown in FIG. Although one base station 10 and one terminal 20 are shown in FIG. 1, this is an example and there may be more than one.
[0018] The base station 10 is a communication device that provides one or more cells and performs wireless communication with the terminal 20. Physical resources of radio signals are defined in the time domain and the frequency domain. The time domain may be defined by the number of OFDM (Orthogonal Frequency Division Multiplexing) symbols, and the frequency domain is defined by the number of subcarriers or resource blocks. good too. The base station 10 transmits synchronization signals and system information to the terminal 20 . Synchronization signals are, for example, NR-PSS and NR-SSS. The system information is transmitted by, for example, NR-PBCH, and is also called broadcast information. As shown in FIG. 1, the base station 10 transmits control signals or data to the terminal 20 on DL (Downlink) and receives control signals or data from the terminal 20 on UL (Uplink). Both the base station 10 and the terminal 20 can perform beamforming to transmit and receive signals. Also, both the base station 10 and the terminal 20 can apply MIMO (Multiple Input Multiple Output) communication to DL or UL. Also, both the base station 10 and the terminal 20 may communicate via a secondary cell (SCell: Secondary Cell) and a primary cell (PCell: Primary Cell) by CA (Carrier Aggregation). Furthermore, the terminal 20 may communicate via a primary cell of the base station 10 and a primary secondary cell (PSCell: Primary Secondary Cell) of another base station 10 by DC (Dual Connectivity).
[0019] The terminal 20 is a communication device with a wireless communication function, such as a smartphone, mobile phone, tablet, wearable terminal, or M2M (Machine-to-Machine) communication module. As shown in FIG. 1 , the terminal 20 receives control signals or data from the base station 10 on the DL and transmits control signals or data to the base station 10 on the UL, thereby performing various functions provided by the wireless communication system. Use communication services.
[0020] FIG. 2 is a diagram for explaining the wireless communication system according to the embodiment of the present invention. FIG. 2 shows a configuration example of a radio communication system when NR-DC (NR-Dual connectivity) is performed. As shown in FIG. 2, a base station 10A serving as MN (Master Node) and a base station 10B serving as SN (Secondary Node) are provided. The base station 10A and the base station 10B are connected to the core network 30 respectively. Terminal 20 communicates with both base station 10A and base station 10B.
[0021] A cell group provided by the MN base station 10A is called MCG (Master Cell Group), and a cell group provided by the SN base station 10B is called SCG (Secondary Cell Group). The operation to be described later may be performed in either configuration shown in FIGS. 1 and 2. FIG.
[0022] The above-described LBT is performed in the wireless communication system according to the present embodiment. Base station 10 or terminal 20, if the LBT result is idle (if LBT succeeds) to acquire COT (Channel Occupancy Time), to perform transmission, if the LBT result is busy (LBT-busy) , sendMore about this source textSource text required for additional translation informationSend feedbackSide panelsHistorySavedContribute5,000 character limit. Use the arrows to translate more.do not believe
[0023] The radio communication system in the present embodiment may perform carrier aggregation (CA) operations using unlicensed CCs and licensed CCs, or perform dual connectivity (DC) operations using unlicensed CCs and licensed CCs. Alternatively, standalone (SA) operation using only unlicensed CCs may be performed. CA, DC, or SA may be performed by any one of NR and LTE systems. DC may be performed by at least two of NR, LTE, and other systems.
[0024] The terminal 20 detects a transmission burst from the base station 10, the signal in the PDCCH or group common PDCCH (group common (GC)-PDCCH) (for example, Reference Signal (RS) such as Demodulation Reference Signal (DMRS) ) may be assumed.
[0025] The base station 10 may transmit a specific PDCCH (PDCCH or GC-PDCCH) containing a specific DMRS that notifies the start of COT at the start of COT triggered by the base station apparatus. At least one of the specific PDCCH and specific DMRS may be called a COT start notification signal. For example, the base station 10 transmits a COT start notification signal to one or more terminals 20, and the terminals 20 can recognize the COT when detecting the specific DMRS.
[0026] FIG. 3 is a diagram for explaining the multi-TTI grant. Release 16NR-U envisions the use of multi-TTI (Transmission Time Interval) grants that schedule multiple PUSCHs over multiple slots / multiple mini-slots in one DCI (Downlink Control Information). Note that "to schedule (or schedule)" may be replaced with "to allocate."
[0027] A multi-TTI grant schedules multiple consecutive PUSCHs that transmit separate TBs (transport blocks). One TB is mapped to one slot or one minislot and transmitted on one PUSCH. One HARQ (Hybrid automatic repeat request) process is assigned to one PUSCH that transmits the one TB.
[0028] For multiple PUSCHs scheduled by one DCI, NDI (New data indicator) and RV (Redundancy version) are signaled for each PUSCH by one DCI. Also, the HARQ process ID notified by the DCI is applied to the first scheduled PUSCH, and the HARQ process IDs of subsequent PUSCHs are incremented by 1 in the order of the PUSCHs.
[0029] FIG. 3 is a diagram showing an example of the operation of terminal 20 that has received a multi-TTI grant. In the example of FIG. 3, PUSCH for 4 slots is scheduled by multi-TTI grant.
[0030] The terminal 20 performs LBT before the slot in which the first PUSCH indicated by A is scheduled, and if the LBT is OK, transmits data on four consecutive PUSCHs. If the first LBT is NG, the PUSCH denoted by B performs the LBT before the scheduled slot, and if the LBT is OK, it transmits data on three consecutive PUSCHs. Thereafter, similar processing is performed. If the last PUSCH, denoted D, performs LBT before the scheduled slot and it is NG, no transmission takes place.
[0031] For example, PUSCH scheduling may support multiple slots or minislots including multiple contiguous PUSCHs, which may include multiple TBs separated, by one DCI. Also, for example, DCI signaling multiple PUSCHs may include NDI and RV. Also, for example, code block group (CBG)-based retransmission may be supported in multiple PUSCH scheduling, and is signaled by the DCI field for one or more PUSCHs to be retransmitted, for each PUSCH, or for a fixed number of PUSCHs. may Also, for example, the HARQ process ID signaled by DCI may apply to the first scheduled PUSCH and may be incremented by 1 in subsequent PUSCHs.
[0032] Also, for example, resource allocation in the time domain in which PUSCH is scheduled may be extended. For example, the range of the start symbol position and the end symbol position may be extended, continuous time domain resource allocation may be extended, multiple PUSCHs may be arranged in the leading slot, and terminal-initiated Multiple starting symbol positions may be supported in the COT of .
[0033] Also, in NR-U, an LBT gap based on CP extension (Cyclic Prefix extension) is being considered for UL transmission of terminals. For example, at least dynamically scheduled PUSCH (Physical Uplink Shared Channel) for CP extension before transmission, SLIV (Start and Length Indicator) in the symbol preceding the PUSCH allocation notified by, even if the CP extension is arranged good. The duration of CP extension supported may be any of 1)-4) below.
[0034] 1) 0 (i.e. no CP extension)2) C1 x symbol length - 25 μs3) C2 x symbol length - 16 μs - TA (Timing Advance)4) C3×symbol length−25 μs−TA
[0035] The above C1, C2 and C3 may be values set according to the SCS (SubCarrier spacing). For example, when the SCS is 15 kHz or 30 kHz, C1 may be fixedly set to 1. Further, for example, when the SCS is 60 kHz, C1 may be fixedly set to 2. Note that C2 or C3 may be fixedly set based on the TA value for each SCS, or may be implicitly derived.
[0036] Note that the value N2 used to calculate the minimum delay from UL grant to PUSCH transmission may be relaxed in consideration of CP extension. Note that CP extension in a certain SCS may be limited to one symbol or less, or may exceed one symbol. Note that the above CP extension may be applied to other UL transmissions. Note that the number of CP extension periods dynamically signaled by the terminal 20 may be configurable.
[0037] Also, C2 and C3 may be set uniquely to the terminal 20 by RRC signaling. C2 and C3 may not limit the maximum TA used in the cell. Note that C2 and C3 may be set to values from 1 to 28 when the SCS is 30 kHz by RRC signaling. Also, by RRC signaling, C2 and C3 may be set to values from 2 to 28 when the SCS is 60 kHz. Other specifications may not be changed by the settings related to C2 and C3.
[0038] Regarding the UL grant by non-fallback DCI, the operations shown in 1)-4) below may be performed. The non-fallback DCI formats are, for example, DCI format 1_1 and DCI format 0_1 in the NR system. The non-fallback DCI format is, for example, a DCI format having a larger size than DCI format 1_0 and DCI format 0_0, which are the fallback DCI formats, and unlike the fallback DCI format, the size is changed depending on the setting. be. Below, "*" indicates multiplication.
[0039] 1) The LBT type, CP extension value and CAPC (Channel Access Priority Class) may be jointly encoded (that is, an index is associated with the combination thereof) and included in the UL grant.2) A combination of LBT type, CP extension value and CAPC may be configured in terminal 20 by terminal 20-specific RRC signaling.3) LBT type {Cat1-16 μs, Cat2-16 μs, Cat2-25 μs, Cat4}, CP extension {0, C1* symbol length-25 μs, C2* symbol length-16 μs-TA, C3* symbol length-25 μs-TA} , CAPC {1, 2, 3, 4}, (Cat2-25 μs, C2*symbol length-16 μs-TA), (Cat1-16 μs, C3* symbol length-25 μs-TA), and (Cat2 −16 μs, C3*symbol length−25 μs−TA) and (Cat2−16 μs or Cat2−16 μs, C1*symbol length−25 μs) may not be supported by RRC configuration.4) The corresponding DCI bit field may be up to 6 bits long. The length of the bit field may be determined depending on the number of combinations configured in RRC signaling for terminal 20 .
[0040] For non-fallback DL assignments that schedule UL transmissions (eg, PUCCH), the operations shown in 1)-5) below may be performed.
[0041] 1) LBT type and CP extension value may be joint encoded and included in the DL allocation.2) The highest CAPC may always be assumed.3) The combination of LBT type and CP extension value may be configured in terminal 20 by terminal 20-specific RRC signaling.4) LBT type {Cat1-16 μs, Cat2-16 μs, Cat2-25 μs, Cat4}, CP extension {0, C1* symbol length-25 μs, C2* symbol length-16 μs-TA, C3* symbol length-25 μs-TA} Of the combinations, (Cat2-25 μs, C2* symbol length-16 μs-TA), (Cat1-16 μs, C3* symbol length-25 μs-TA), and (Cat2-16 μs, C3* symbol length-25 μs-TA ) and (Cat2−16 μs or Cat2−16 μs, C1*symbol length−25 μs) may not be supported by the RRC configuration.5) The corresponding DCI bit field may be up to 4 bits long. The length of the bit field may be determined depending on the number of combinations configured in RRC signaling for terminal 20 .
[0042] On the other hand, in a UL grant with fallback DCI, the LBT type, CP extension value and CAPC may be jointly encoded with a 2-bit length and included in the UL grant. Note that combinations of LBT types, CP extension values, and CAPCs to be supported may be defined in advance by specifications.
[0043] Also, in fallback DL assignments that schedule UL transmissions (eg, PUCCH), the LBT type and CP extension value may be jointly encoded with a 2-bit length and included in the DL assignment. Note that the combinations of supported LBT types and CP extension values may be defined in advance by specifications.
[0044] Here, FBE (Frame Based Equipment) and LBE (Load Based Equipment) are being considered as LBT mechanisms. The difference between the two is the frame configuration used for transmission and reception, the channel occupancy time, and the like. FBE has a fixed timing configuration for transmission and reception related to LBT. On the other hand, LBEMore about this source textSource text required for additional translation informationSend feedbackSide panelsHistorySavedContribute5,000 character limit. Use the arrows to translate more.The configuration of transmission and reception related to LBT is not fixed in the direction of the time axis, and LBT is performed according to demand. Specifically, FBE has a fixed frame period, a certain period of time in a predetermined frame (LBT time (LBT duration), etc.) as a result of performing carrier sense, if the channel is available Transmission is performed, but if the channel cannot be used, it waits without transmission until the carrier sense timing in the next frame.
[0045] On the other hand, LBE will extend the carrier sense time if the channel is unusable as a result of performing carrier sense (initial Clear Channel Assessment: CCA), and will continue to perform carrier sense until the channel becomes available. ECCA (Extended CCA) procedure is performed. LBE requires random backoff for proper collision avoidance.
[0046] When LBT is operated in LBE, signaling of LBT type and CP extension value for both fallback DL allocation and fallback UL grant may be performed using Table 1, for example.
[0047] [table 1]
[0048] "Cat1" shown in Table 1 corresponds to category 1, "Cat2" corresponds to category 2, and "Cat4" corresponds to category 4. As shown in Table 1, if the LBT type is "Cat1-16 μs", the CP extension value may be "C2*symbol length-16 μs-TA". Also, when the LBT type is "Cat2-25 μs", the CP extension value may be "C3*symbol length-25 μs-TA". Also, if the LBT type is "Cat2-25 μs", the CP extension value may be "C1*symbol length-25 μs". Further, when the LBT type is "Cat4", the CP extension value may be "0".
[0049] The CAPC does not have to be explicitly notified. For UL grant, terminal 20 may assume CAPC=4 used by base station 10 to obtain CO. In addition, in the case of COT led by terminal 20, that is, category 4, terminal 20 may select CAPC by itself. Note that the mapping between CAPC and traffic class may be the same as the mapping defined for UL-CG (Configured Grant) transmission. Note that if Category 4 LBT is used, the highest priority CAPC may be used for the PUCCH associated with the DL allocation.
[0050] LBT, when operated in FBE, the terminal 20 notified that the LBT type is "Cat2-25μs" or "Cat4", one 9μs carrier sense slot is measured within a period of 25μs good too.
[0051] Also, regarding RAR (Random access response), terminal 20 may use the same LBT type and CP extension value table (eg, Table 1) and CAPC selection method as UL grant by fallback DCI. Two bits may be signaled over the RAR (ie PDSCH) for the above operation. When the terminal 20 multiplexes user plane data on PUSCH, the terminal 20 may assume that the base station 10 used CAPC=4 to acquire the CO. In addition, in the case of COT led by terminal 20, that is, category 4, terminal 20 may select CAPC by itself. Note that the mapping between CAPC and traffic class may be similar to the mapping defined for UL-CG transmission. Also, the field indicating frequency domain resource allocation contained in the RAR is reduced to accommodate the two bits.
[0052] In the case of CP extension of the first OFDM symbol l allocated for PUSCH transmission, T ext [sec] is the CP extension period. Table 2 is an example of indexing T ext for each SCS.
[0053] [Table 2]
[0054] μ=0 shown in Table 2 is 15 kHz SCS, μ=1 is 30 kHz SCS, μ=2 is 60 kHz SCS, T symb, l μ corresponds to the symbol length where SCS is μ and symbol position is l, and T TA is the timing advance value. . As shown in Table 2, the T ext corresponding to index 0 is undefined.
[0055] Index 1 corresponds to "symbol length-25*10-6" for 15 kHz SCS, "symbol length-25*10-6" for 30 kHz SCS, and "2* symbol length-25*10-6" for 60 kHz SCS. .
[0056] Index 2 corresponds to "C 2*symbol length-16*10-6-T TA" for both 15 kHz SCS, 30 kHz and 60 kHz. That is, CP extension is determined according to the timing advance value.
[0057] Index 3 corresponds to "C 3*symbol length-25*10-6-T TA" for both 15 kHz SCS, 30 kHz and 60 kHz. Similar to index 2, ie depending on the timing advance value, CP extension is determined.
[0058] Note that C2 and C3 may be integer values from 1 to 28 in the case of 15 kHz SCS or 30 kHz SCS. C2 and C3 may be integer values from 2 to 28 for 60 kHz SCS.
[0059] Here, while the CP extension is applied as described above, depending on the communication situation, the terminal 20 needs to set the CP extension period before the RRC setting is executed. For example, the communication status is UL grant by RAR, fallback DCI, and DL allocation by fallback DCI. In this communication situation, the terminal 20 does not know the values of C2 and C3 used for UL transmission.
[0060] Therefore, in UL transmission in NR-U, the CP extension value may be determined appropriately even before RRC configuration is performed.
[0061] FIG. 4 is a sequence diagram for explaining an example of signaling in the embodiment of the present invention. The base station 10 may instruct the terminal 20 to transmit PUSCH and / or PUCCH in steps S1 and S2, or may set a transmission opportunity. The terminal 20 may, for example, appropriately determine the CP extension value even before executing the RRC configuration in step S1.
[0062] In step S1, the base station 10 notifies the terminal 20 of the PUSCH and / or PUCCH settings via higher layer signaling. For example, a setting related to CP extension may be notified.
[0063] In step S2, the base station 10 transmits a DCI-based UL grant to the terminal 20 via PDCCH. Subsequently, the terminal 20 transmits data to the base station 10 via PUSCH determined based on the received DCI (S3). When the DCI indicates the CP extension value, the terminal 20 may apply the CP extension to the PUSCH and transmit it.
[0064] As another example, in step S2, the base station 10 transmits DL allocation by DCI to the terminal 20 via PDCCH. Subsequently, the terminal 20 transmits uplink control information (UCI) to the base station 10 via PUCCH determined based on the received DCI (S3). When the DCI indicates the CP extension value, the terminal 20 may apply the CP extension to the PUCCH and transmit it.
[0065] As another example, in step S2, the base station 10 transmits RAR to the terminal 20 via PDSCH. Subsequently, the terminal 20 transmits data to the base station 10 via PUSCH determined based on the received RAR (S3). When the CP extension value is notified in the RAR, the terminal 20 may apply the CP extension to the PUSCH and transmit it.
[0066] FIG. 5 is a flowchart for explaining an operation example (1) of terminal 20 according to the embodiment of the present invention. In step S11, the terminal 20 determines whether or not C2 and C3 are set in RRC signaling. If it is set (YES in S11), the process proceeds to step S12, and if it is not set (NO in S11), the process proceeds to step S13.
[0067] In step S12, the terminal 20 uses C2 and C3 by RRC signaling to determine the CP extension value. On the other hand, in step S13, the terminal 20 determines the CP extension value by assuming that C2 and C3 are predetermined fixed values.
[0068] For example, in step S13, the fixed values of C2 and C3 may be selected from any integer value from 1 to 28 for 15 kHz SCS or 30 kHz SCS, or any integer value from 2 to 28 for 60 kHz SCS. Either may be selected.
[0069] Also, for example, in step S13, if "C2*symbol length-16 μs-TA<0" assuming a prescribed fixed value of C2, the CP extension value may be assumed to be zero. For example, in step S13, if "C3*symbol length-25 μs-TA<0" assuming a defined fixed value of C3, then the CP extension value may be assumed to be zero.
[0070] FIG. 6 is a flowchart for explaining an operation example (2) of terminal 20 according to the embodiment of the present invention. In step S21, the terminal 20 determines whether or not C2 and C3 are set in RRC signaling. If it is set (YES in S21), the process proceeds to step S22, and if it is not set (NO in S21), the process proceeds to step S23.
[0071] In step S22, the terminal 20 uses C2 and C3 by RRC signaling to determine the CP extension value. Meanwhile, in step S23, the terminal 20 determines the CP extension value by determining C2 and C3 from the TA values applied to the corresponding UL transmissions.
[0072] For example, C2 may be the maximum value that satisfies "C2*symbol length-16 μs-TA<symbol length". C3 may be the maximum value that satisfies “C3*symbol length−25 μs−TA<symbol length”.
[0073] Also, for example, C2 may be the minimum value that satisfies "0<C2*symbol length-16 μs-TA". C3 may be the minimum value that satisfies "0<C3*symbol length-25 μs-TA".
[0074] FIG. 7 is a flowchart for explaining an operation example (3) of terminal 20 according to the embodiment of the present invention. In step S21, the terminal 20 determines whether or not C2 and C3 are set in RRC signaling. If it is set (YES in S21), the process proceeds to step S22, and if it is not set (NO in S21), the process proceeds to step S23.
[0075] In step S22, the terminal 20 uses C2 and C3 by RRC signaling to determine the CP extension value. On the other hand, in step S23, the terminal 20 may assume that the CP extension values to which C2 and C3 correspond are not notified by DCI. Table 3 is an example of CP extension values signaled by DCI.
[0076] [Table 3]
[0077] As shown in Table 3, the CP extension values to which C2 and C3 correspond are indices "0" and "1". Therefore, the terminal 20 may assume that the indexes "0" and "1" are not notified in the DCI notification of the CP extension value. Furthermore, the bit field length may be set to 1 bit and the index "2" or "3" may be notified.
[0078] In addition, the channel access type (LBT type) shown in Table 3 is a type of channel access method that uses a random period or a fixed period that the terminal 20 determines that the sensed slot is idle before UL transmission. . Channel access type 1 corresponds to "Cat4", channel access type 2A corresponds to "Cat2-25μMore about this source textSource text required for additional translation informationSend feedbackSide panelsHistorySavedContribute5,000 character limit. Use the arrows to translate more.s” and channel access type 2C corresponds to “Cat 1-16 μs”.
[0079] FIG. 8 is a diagram for explaining an example of CP extension in the embodiment of the present invention (when 16 μs or 25 μs+TA is 1 symbol length or less). When the CP extension value is set as shown in FIG. 8, 16 μs or 25 μs+CP extension value+TA is one symbol length. That is, CP extension value=1 symbol length-16 μs or 25 μs-TA. When setting a larger CP extension value, the CP extension value may be a value obtained by increasing the first term on the right side by one symbol unit.
Claims
we claimThe scope of the claims
1. a receiving unit that receives information for allocating uplink transmission from a base station;a control unit that determines the CP extension value when the parameter for calculating the CP extension value is not set from the base station when the information is received;a transmitting unit that performs the uplink transmission by applying the determined CP extension value.
2. The control unit determines the parameter, and calculates, as the CP extension value, a period obtained by subtracting a period based on the timing advance value and a predetermined period from a period that is an integral multiple of the symbol length based on the determined parameter. 1 terminal.
3. The terminal according to claim 2, wherein the control unit determines the parameter to be a predetermined value, and calculates the CP extension value based on the parameter.
4. The terminal according to claim 2, wherein said control unit determines said parameter based on a timing advance value, and calculates a CP extension value based on said parameter.
5. The terminal according to claim 1, wherein the control unit assumes that the CP extension value corresponding to the parameter is not reported from the base station.
6. a reception procedure for receiving information for allocating uplink transmission from the base station;a control procedure for determining the CP extension value when the parameter for calculating the CP extension value is not set from the base station when the information is received;A communication method in which a terminal executes a transmission procedure for executing the uplink transmission by applying the determined CP extension value.
