terminal and base station

Abstract

A terminal has a reception section that receives setting information in a high frequency band of a frequency range 2 (FR2) or more of the FR2 among a frequency range 1 (FR1) of a new radio (NR) system as a low frequency band and the FR2 as a high frequency band, and a control section that sets at least one of a format of a random access preamble, a sequence of the random access preamble, a subcarrier spacing applied to a channel for transmitting the random access preamble, and a subcarrier spacing applied to an uplink shared channel in accordance with the setting information.

Description

Technical Field

[0001] This invention relates to terminals and base stations in wireless communication systems. Background Technology

[0002] In 3GPP (Third Generation Partnership Project) Release 15 NR (New Radio) and Release 16 NR, the target frequency band is up to 52.6 GHz. Regarding the extension of NR to frequency bands above 52.6 GHz, Release 16 included a TSG RAN (Technical Specification Group Radio Access Network) level study item that investigated various regulations, use cases, requirements, etc. This study item was completed in December 2019. In Release 17, study items and work items were agreed upon for the actual extension of the specification to above 52.6 GHz.

[0003] In the research project of version 16, the frequency band for NR was envisioned to be extended from 52.6 GHz to 114.25 GHz. However, in version 17, due to time constraints, the frequency band for research was limited to 52.6 GHz to 71 GHz. Furthermore, it was envisioned that when extending the NR frequency band from 52.6 GHz to 71 GHz, the extension would be based on the current NR FR2 (Frequency Range 2) design.

[0004] Existing technical documents

[0005] Non-patent literature

[0006] Non-patent document 1: 3GPP TSG RAN Meeting #86, RP-193229, Sitges, Spain, December 9-12, 2019

[0007] Non-patent document 2: 3GPP TS 38.101-2 V15.8.0 (2019-12)

[0008] Non-patent document 3: 3GPP TSG-RAN4 Meeting #92bis, R4-1912870, Chongqing, China, 14-18 Oct, 2019

[0009] Non-patent document 4: 3GPP TSG-RAN4 Meeting #93, R4-1916167, Reno, United States, 18th-22nd November, 2019

[0010] Non-patent document 5: 3GPP TSG-RAN4 Meeting #92bis, R4-1912982, Chongqing, China, October 14-18, 2019

[0011] Non-patent document 6: 3GPP TSG-RAN4 Meeting #93, R4-1915982, Reno, US, November 18-22, 2019

[0012] Non-patent document 7: 3GPP TS 38.331 V15.8.0 (2019-12)

[0013] Non-patent document 8: 3GPP TS 38.213 V15.8.0 (2019-12) Summary of the Invention

[0014] The problem that the invention aims to solve

[0015] Imagine introducing new subcarrier spacing in the frequency band from 52.6 GHz to 71 GHz.

[0016] There is a need for a technique that enables terminals to properly configure the transmission of random access preambles in high-frequency bands above the FR2 band of NR.

[0017] Methods for solving problems

[0018] According to one aspect of the present invention, a terminal is provided, comprising: a receiving unit that receives setting information for a high-frequency band above the frequency band of a New Radio (NR) system, which is a frequency range 1 (FR1) as a low-frequency band and a frequency range 2 (FR2) as a high-frequency band; and a control unit that sets at least one of the following items according to the setting information: the format of a random access preamble, the sequence of the random access preamble, the subcarrier spacing of the channel used to transmit the random access preamble, and the subcarrier spacing of the uplink shared channel.

[0019] Invention Effects

[0020] According to an embodiment, a technique is provided that enables a terminal to appropriately configure the transmission of a random access preamble in a high-frequency band above the FR2 band of NR. Attached Figure Description

[0021] Figure 1 This is a structural diagram of the communication system in this embodiment.

[0022] Figure 2 This is a diagram illustrating an example of the extension of the NR frequency band.

[0023] Figure 3 This is a diagram illustrating an example of the long sequence-based PRACH format of NR version 15.

[0024] Figure 4 This is a diagram illustrating an example of the short sequence-based PRACH format of NR version 15.

[0025] Figure 5 This is a diagram illustrating examples of the requirements for OCB (occupied channel bandwidth) and PSD (power spectral density).

[0026] Figure 6 This is a diagram illustrating an example of a combination of sequence length, SCS for PRACH, and SCS for PUSCH applied to the PRACH format.

[0027] Figure 7 This is a diagram showing an example of a newly introduced table for the frequency band from 52.6 GHz to 71 GHz.

[0028] Figure 8 This is a diagram showing examples of formats A0, A1, A2, A3, B1, B2, B3, B4, C0, and C2.

[0029] Figure 9 This is a diagram illustrating an example of the format for inserting a cyclic prefix for each OFDM symbol of PRACH.

[0030] Figure 10 This is a diagram showing an example of a format where PRACH OFDM symbols are repeated a large number of times.

[0031] Figure 11 This is a diagram showing an example of a shorter format for the cyclic prefix (or guard period).

[0032] Figure 12This is a diagram illustrating an example of a table showing the correspondence between the PRACH configuration that can be applied to FR2 and the PRACH configuration index.

[0033] Figure 13 This is a diagram showing an example of importing new values ​​for parameters into a table.

[0034] Figure 14 This is a diagram illustrating an example of the functional structure of a terminal.

[0035] Figure 15 This is a diagram illustrating an example of the functional structure of a base station.

[0036] Figure 16 This is a diagram illustrating an example of the hardware structure of a terminal and a base station. Detailed Implementation

[0037] Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings. Furthermore, the embodiments described below are merely examples, and the application of the present invention is not limited to the embodiments described below.

[0038] The wireless communication system in the following embodiment is assumed to be based primarily on NR, but this is only one example. The wireless communication system in this embodiment may also be based on a wireless communication system other than NR (e.g., LTE) in part or all of its components.

[0039] (System Overall Structure)

[0040] Figure 1 A structural diagram of the wireless communication system according to this embodiment is shown. (For example...) Figure 1 As shown, the wireless communication system involved in this embodiment includes a terminal 10 and a base station 20. Figure 1 The image shows one terminal 10 and one base station 20, but this is just one example; there can be multiple of each.

[0041] Terminal 10 is a communication device with wireless communication capabilities, such as a smartphone, mobile phone, tablet computer, wearable terminal, or M2M (Machine-to-Machine) communication module. Terminal 10 receives control signals or data from base station 20 in the downlink (DL) and transmits control signals or data to base station 20 in the uplink (UL), thereby utilizing various communication services provided by the wireless communication system. For example, the channels transmitted from terminal 10 include PUCCH (Physical Uplink Control Channel) and PUSCH (Physical Uplink Shared Channel). Alternatively, terminal 10 can be referred to as a UE, and base station 20 as a gNB.

[0042] In this embodiment, the duplex mode can be either TDD (Time Division Duplex) or FDD (Frequency Division Duplex).

[0043] Furthermore, in the implementation, the "configure" wireless parameters can be preset values ​​or set according to wireless parameters notified from the base station 20 or the terminal 10.

[0044] Base station 20 is a communication device that provides one or more cells and wirelessly communicates with terminal 10. The physical resources of the wireless signal are defined in the time and frequency domains. The time domain can be defined by the number of OFDM symbols, and the frequency domain can be defined by the number of subcarriers or resource blocks. Base station 20 transmits synchronization signals and system information to terminal 10. Synchronization signals are, for example, NR-PSS and NR-SSS. Part of the system information is transmitted, for example, via NR-PBCH, also known as broadcast information. Synchronization signals and broadcast information can be periodically transmitted as SS blocks (SS / PBCH blocks) consisting of a predetermined number of OFDM symbols. For example, base station 20 transmits control signals or data to terminal 10 in the DL (Downlink) and receives control signals or data from terminal 10 in the UL (Uplink). Both base station 20 and terminal 10 are capable of beamforming for signal transmission and reception. For example, the reference signal transmitted from base station 20 includes CSI-RS (Channel State Information Reference Signal), and the channels transmitted from base station 20 include PDCCH (Physical Downlink Control Channel) and PDSCH (Physical Downlink Shared Channel).

[0045] (Multi-numerology)

[0046] To support a wide range of frequencies or use cases in 5G, multiple parameter sets (numerologies) (such as subcarrier spacing and symbol length) are required. Therefore, it is effective to design variable parameters scalably based on the LTE parameter set (numerology). Following this idea, a multi-numerology for NR is introduced. Specifically, it is assumed that the reference subcarrier spacing is the same as the LTE subcarrier spacing, at 15kHz. Other subcarrier spacings are specified by multiplying the reference subcarrier spacing by a power of 2. Multiple subcarrier spacing configurations μ are specified. Specifically, for μ=0, the subcarrier spacing Δf=15kHz, Cyclic prefix=Normal; for μ=1, the subcarrier spacing Δf=30kHz, Cyclic prefix=Normal; for μ=2, the subcarrier spacing Δf=60kHz, Cyclic prefix=Normal or Extended; for μ=3, the subcarrier spacing Δf=120kHz, Cyclic prefix=Normal; and for μ=4, the subcarrier spacing Δf=240kHz, Cyclic prefix=Normal.

[0047] For any subcarrier spacing configuration μ = 0, 1, 2, 3, 4, assume that the number of OFDM symbols in one time slot is also 14. However, for subcarrier spacing configuration μ = 0, 1, 2, 3, 4, the number of time slots in one frame is 10, 20, 40, 80, 160, and the number of time slots in one subframe is 1, 2, 4, 8, 16. Here, since the frame length is 10ms, the time slot lengths for subcarrier spacing configuration μ = 0, 1, 2, 3, 4 are 1ms, 0.5ms, 0.25ms, 0.125ms, 0.0625ms, respectively. Since the number of OFDM symbols in one time slot is also 14 for any subcarrier spacing configuration μ = 0, 1, 2, 3, 4, the OFDM symbol length varies according to each subcarrier spacing configuration. For subcarrier spacing configurations, μ = 0, 1, 2, 3, 4, and OFDM symbol lengths of (1 / 14) ms, (0.5 / 14) ms, (0.25 / 14) ms, (0.125 / 14) ms, and (0.0625 / 14) ms are used. This allows for low-latency communication by shortening the time slot length and OFDM symbol length. For example, in the subcarrierSpacing parameter of the information element BWP, base station 20 can set the subcarrier spacing for terminal 10 by specifying any one of μ = 0, 1, 2, 3, 4.

[0048] (NR expansion to frequency bands above 52.6 GHz)

[0049] In 3GPP (Third Generation Partnership Project) Release 15 NR (New Radio) and Release 16 NR, the target frequency band is up to 52.6 GHz. Regarding the extension of NR to frequency bands above 52.6 GHz, Release 16 included a TSG RAN (Technical Specification Group Radio Access Network) level study item that investigated various regulations, use cases, requirements, etc. This study item was completed in December 2019. In Release 17, study items and work items were agreed upon for the actual extension of the specification to above 52.6 GHz.

[0050] In the research project of version 16, the frequency band for NR was envisioned to be extended from 52.6 GHz to 114.25 GHz, but in version 17, research time was limited, such as... Figure 2 As shown, the frequency band under study is envisioned to be limited to 52.6 GHz to 71 GHz. Furthermore, when extending the NR frequency band from 52.6 GHz to 71 GHz, it is envisioned to be extended based on the current NR's FR2 (Frequency Range 2) design. This is because it is assumed that researching new waveforms would take a considerable amount of time.

[0051] Furthermore, reasons for limiting the frequency band of the research object to 52.6 GHz to 71 GHz can be cited as follows: Below 71 GHz, there are already unlicensed frequency bands from 54 GHz to 71 GHz that can be used by various countries, and at the World Radiocommunication Conference 2019 (WRC-2019), 66 GHz to 71 GHz became the highest frequency band as a candidate for new frequency bands for IMT (International Mobile Telecommunications), and there are no frequency bands above 71 GHz that can be immediately used as licensed bands.

[0052] The current NR frequency band consists of FR1 (Frequency Range 1), which corresponds to the frequency band from 410MHz to 7.125GHz, and FR2, which corresponds to the frequency band from 24.25GHz to 52.6GHz.

[0053] In addition, regarding the frequency band from 52.6 GHz to 71 GHz, the current definition of FR2 (the frequency band from 24.25 GHz to 52.6 GHz) can be changed and included in the revised FR2. Alternatively, it can be set as a new frequency range (FR: Frequency Range) separately from FR2.

[0054] (Work Item Objectives)

[0055] (RAN1: Characteristics of the physical layer)

[0056] A new set of one or more parameters for the operation of terminal 10 and base station 20 in the frequency band from 52.6 GHz to 71 GHz. If there is an impact on the physical signal / channel determined by Study Item (SI), this impact should be addressed.

[0057] Features related to the timelines of the respective new parameter sets. For example, the preparation time for BWP (Bandwidth Part), beam switching time, HARQ (Hybrid Automatic Repeat Request) scheduling, UE (User Equipment) processing, PDSCH (Physical Downlink Shared Channel), PUSCH (Physical Uplink Shared Channel) / SRS (Sounding Reference Signal), and CSI (Channel State Information), as well as the calculation time.

[0058] Operations in the licensed and unlicensed frequency bands from 52.6 GHz to 71 GHz can utilize up to 64 SSB (Synchronization Signal Block) beams.

[0059] The physical layer processing may also include a beam-based channel access mechanism designed to meet the constraints applicable to unlicensed frequency bands from 52.6 GHz to 71 GHz.

[0060] Figure 3 and Figure 4 This is a diagram illustrating the overview of the PRACH (Physical Random Access Channel) of NR version 15.

[0061] Figure 3 This diagram illustrates an example of the long sequence-based PRACH format for NR version 15. The long sequence-based PRACH format is used to transmit Zadoff-Chu sequences with a sequence length of 839, and is the same format supported in LTE.

[0062] Figure 4 This diagram illustrates an example of a short-sequence-based PRACH format for NR version 15. The short-sequence-based PRACH format is used to transmit a Zadoff-Chu sequence with a sequence length of 139. The short-sequence-based PRACH format can, for example, use the same subcarrier spacing applied to data as PUSCH, and can be used when using a PRACH with a wider bandwidth and shorter duration. For the short-sequence-based PRACH format, similar to the subcarrier spacing (SCS) applied to data, 15kHz, 30kHz, 60kHz, and 120kHz SCS can be used. In FR1, 15kHz and 30kHz SCS can be used for the short-sequence-based PRACH format. Furthermore, in FR2, 60kHz and 120kHz SCS can be used for the short-sequence-based PRACH format.

[0063] like Figure 4 The table shows that preamble formats A, B, and C are defined as PRACH formats based on short sequences. Preamble formats A, B, and C are mainly classified according to the presence or absence of a guard period (GP) and the relative length of the cyclic prefix (CP). For example, indices such as 0, 1, 2, 3, and 4 are defined for preamble formats A, B, and C, but these represent different time lengths. For instance, "0" represents a length of 1 symbol, "1" represents a length of 2 symbols, "2" represents a length of 4 symbols, "3" represents a length of 6 symbols, and "4" represents a length of 12 symbols.

[0064] like Figure 4As shown, for preamble format A, the protection period (T_GP) is 0. As a use case for preamble format A, consider transmitting multiple preamble formats A side-by-side in time slots. For preamble formats B and C, protection periods (T_GP) other than zero are defined. Therefore, as a use case for preamble formats B and C, consider using the format individually. The cyclic prefix lengths (T_CP) of preamble formats B and C are different. The cyclic prefix length of preamble format B is shorter than that of preamble format C, and the maximum cell radius corresponding to preamble format B is smaller than that corresponding to preamble format C. That is, consider using preamble format B in smaller cells and preamble format C in larger cells. Thus, preamble formats A, B, and C can be said to be classified according to their preamble use cases.

[0065] In FR2 of NR version 15, only the short sequence-based PRACH format can be used, and subcarrier spacing of 60kHz or 120kHz can be used for PRACH.

[0066] For NR-U (unlicensed band) version 16, the PRACH format has been extended. In NR-U version 16, all short-sequence-based PRACH formats from NR version 15 are available. In addition, the Zadoff-Chu sequence with a length of 1151 (for 15kHz SCS) and the Zadoff-Chu sequence with a length of 571 (for 30kHz SCS) are also available for formats A, B, and C.

[0067] Figure 5 This diagram illustrates examples of OCB (occupied channel bandwidth) and PSD (power spectral density) requirements. In Europe, the use of radio waves in unlicensed frequency bands is restricted according to OCB requirements. There are regulations stipulating that at least 80% of the system bandwidth must be used when transmitting signals. In the Zadoff-Chu sequence of length 139 in version 15, the OCB requirements are difficult to meet due to its narrow bandwidth. Therefore, the aforementioned Zadoff-Chu sequences of length 1151 and 571 were introduced.

[0068] Furthermore, in Europe, the use of radio waves in unlicensed frequency bands is restricted in various countries, in addition to the requirements of the Open Circuit Block (OCB) and the upper limit of the power spectral density (PSD). For example, in Europe, there are regulations requiring the power density to be below 10 dBm / MHz in the frequency band from 5150 MHz to 5350 MHz. Under these OCB requirements and the upper limit of PSD, a wider bandwidth allows for higher total power transmission, but a narrower bandwidth makes it difficult to achieve the same level of power. Therefore, the longer Zadoff-Chu sequence was introduced.

[0069] (Topic)

[0070] Imagine introducing new subcarrier spacing for both SSB and data within the 52.6 GHz to 71 GHz frequency band. In this case, it is currently unclear how the subcarrier spacing usable for PRACH will change. For example, regarding short-sequence-based PRACH formats, it is thought that the same subcarrier spacing applied to data could be used.

[0071] Furthermore, regarding the unlicensed frequency band from 52.6 GHz to 71 GHz, the requirements of the OCB were not applied, but requirements related to the upper limit of PSD were applied. Therefore, it is considered that when transmitting signals with a narrower bandwidth, the transmission power used for transmitting the signal decreases. Therefore, it is envisioned that it is necessary to increase the total transmission power used for transmitting the signal by ensuring a wider bandwidth for transmitting the signal.

[0072] (Proposal 1)

[0073] In the frequency band from 52.6 GHz to 71 GHz (including licensed and unlicensed bands), a new set of parameters can be imported for at least any of the preamble formats A, B, and C in the PRACH format. (For example, for μ = 5, the subcarrier spacing Δf = 480 kHz and the cyclic prefix = Normal or Extended can be specified. Alternatively, in addition to Normal, Extended can be specified as the cyclic prefix corresponding to the existing μ = 4. Furthermore, information other than the subcarrier spacing Δf or the cyclic prefix (e.g., frequency-related information) can be specified for each μ value.) For example, a 240 kHz SCS and / or a 480 kHz SCS can be applied for preamble formats A, B, and / or C with a sequence length of 139 for orthogonal sequences (e.g., Zadoff-Chu sequences).

[0074] In both licensed and unlicensed frequency bands, orthogonal sequences of the same or different sequence lengths can be applied in the PRACH format. For example, in the frequency band from 52.6 GHz to 71 GHz, the sequence length that can be applied to the PRACH format can be any of the following Alt.1 to Alt.5.

[0075] (Alt.1) In both licensed and unlicensed frequency bands, orthogonal sequences with a sequence length of 139 can be applied in the PRACH format, and orthogonal sequences with a sequence length of 571 and / or 1151 can also be applied in the PRACH format.

[0076] (Alt.2) In the licensed frequency band, orthogonal sequences with a sequence length of 139 may be used in the PRACH format, and in the unlicensed frequency band, orthogonal sequences with a sequence length of 571 and / or 1151 may be used in the PRACH format. Furthermore, in the licensed frequency band, orthogonal sequences with a sequence length of 139 may also be used in the PRACH format, and in the unlicensed frequency band, at least one of the following orthogonal sequences with a sequence length of 139, a sequence length of 571, and a sequence length of 1151 may also be used in the PRACH format.

[0077] (Alt.3) In both licensed and unlicensed frequency bands, orthogonal sequences with a sequence length of 139 can also be applied in the PRACH format, and orthogonal sequences with a new sequence length (longer than 139) can also be applied in the PRACH format.

[0078] (Alt.4) In licensed frequency bands, orthogonal sequences with a sequence length of 139 can also be applied in the PRACH format, and in unlicensed frequency bands, orthogonal sequences with a new sequence length (a sequence length longer than 139) can also be applied in the PRACH format.

[0079] (Alt.5) In licensed frequency bands, orthogonal sequences with new sequence lengths (shorter than 139) may also be applied in the PRACH format. In unlicensed frequency bands, orthogonal sequences with sequence lengths of 139, 571 and / or 1151, and / or orthogonal sequences with new sequence lengths (longer than 139) may also be applied in the PRACH format.

[0080] The sequence length used for PRACH format can be determined based on a set of parameters (e.g., subcarrier spacing), or it can be determined regardless of which of the multiple sets of parameters (e.g., subcarrier spacing) the sequence length is.

[0081] In the case of importing a new orthogonal sequence as in the example above, suppose base station 20 needs to notify terminal 10 which sequence length to apply for transmitting PRACH. Therefore, in the PRACH-related configuration information (e.g., the information element prach-RootSequenceIndex) received from base station 20, a parameter indicating which candidate value of the root sequence index can be selected is appended.

[0082] Figure 6 This diagram illustrates examples of combinations of sequence lengths, PRACH SCS, and PUSCH SCS applied to the PRACH format. For example, in addition to the combinations of sequence lengths, PRACH SCS, and PUSCH SCS applicable to the PRACH format in NR of 3GPP version 15 and NR-U of 3GPP version 16, combinations of sequence lengths, PRACH SCS, and PUSCH SCS applicable to the PRACH format can be added in the frequency band from 52.6 GHz to 71 GHz. In this case, the added new combination can include a combination with a sequence length of 139 and the same PRACH SCS and PUSCH SCS. Additionally, the added new combination can also include combinations where the PRACH SCS is wider than the PUSCH SCS, and combinations where the PUSCH SCS is wider than the PRACH SCS. Alternatively, the new combination added may contain only combinations where PUSCH's SCS is the same as PRACH's SCS.

[0083] In addition, Figure 6 In the example, it could also be L. RA Indicates the length of the sequence, used for Δf in PRACH. RA Δf represents the subcarrier spacing of PRACH, and Δf for PUSCH represents the subcarrier spacing of PUSCH. RA RB It can also be expressed as the number of resource blocks used for sending PRACH, represented by the number of resource blocks in PUSCH. k(-) can represent the parameters used for generating PRACH.

[0084] (Action Example 1)

[0085] For example, in the frequency band from 52.6 GHz to 71 GHz, during initial access, terminal 10 receives system information, including PRACH configuration information, from base station 20. Terminal 10 selects an orthogonal sequence of a format applicable to the PRACH based on the parameters specified by the information element `prach-RootSequenceIndex` contained in the received PRACH configuration information. Furthermore, terminal 10 sets the PRACH subcarrier spacing and the PUSCH subcarrier spacing based on the PRACH configuration information contained in the received system information. Terminal 10 then sends a random access preamble to base station 20 using the selected PRACH format and PRACH subcarrier spacing.

[0086] (Proposal 2)

[0087] The frequency band that can apply (A) a new subcarrier spacing, (B) a new sequence length, and (C) a sequence length, the SCS of PRACH, and the SCS of PUSCH can be a predetermined frequency band. For example, it can be any one of the following from Alt.A1 to Alt.A4.

[0088] (Alt.A1) can only be used in the frequency band from 52.6 GHz to 71 GHz.

[0089] (Alt.A2) can be used in the frequency band from 24.25 GHz to 71 GHz.

[0090] (Alt.A3) Alternatively, some (or all) of (A), (B), and (C) above may be used in the unlicensed frequency band from 52.6 GHz to 71 GHz, and some (or all) of (A), (B), and (C) above may be used in the licensed frequency band from 52.6 GHz to 71 GHz.

[0091] (Alt.A4) Alternatively, some (or all) of (A), (B), and (C) above may be used in the unlicensed frequency band from 24.25 GHz to 71 GHz, and some (or all) of (A), (B), and (C) above may be used in the licensed frequency band from 24.25 GHz to 71 GHz.

[0092] Figure 12 This is a diagram illustrating an example of a table showing the correspondence between the PRACH configuration that can be applied to FR2 and the PRACH configuration index.

[0093] (Alt.B1) can also be used as follows Figure 12The example shows a table specifying the correspondence between PRACH configurations and PRACH configuration indices applicable to FR2, which is applied to the frequency band from 52.6 GHz to 71 GHz. In this case, for example, formats A0, A1, A2, A3, B1, B2, B3, B4, C0, and C2 can be used as preamble formats, and the sequence length of the orthogonal sequence can be 139, 511, or 1151.

[0094] exist Figure 12 In the example, when the SCS of PRACH is 120kHz, there are two PRACH time slots within a 60kHz time slot. Figure 12 In the example, a value of 1 for the "Number of PRACH slots within a 60kHz slot" column indicates that there is actually a resource capable of transmitting PRACH only in the latter half of the two PRACH slots within a 60kHz slot. Conversely, a value of 2 for the "Number of PRACH slots within a 60kHz slot" column indicates that there is actually a resource capable of transmitting PRACH in each of the two PRACH slots within a 60kHz slot. In contrast, when the PRACH SCS is 240kHz, there are four PRACH slots within a 60kHz slot. In this case, for example, in... Figure 12 In the example shown, if the value of the column "Number of PRACH slots within a 60kHz slot" is 2, it may become unclear which two slots out of the four PRACH slots it refers to.

[0095] Here, in such Figure 12 In the example table showing the correspondence between PRACH configuration and PRACH configurationindex, when the PRACH SCS is larger (e.g., a PRACH SCS of 240kHz), the "Number of PRACH slots within a 60kHz time slot" can be defined as any of Alt.C1 to Alt.C3 below. Additionally, besides Alt.C1 to Alt.C3 below, if the value of the "Number of PRACH slots within a 60kHz time slot" column is 2, then there can be resources capable of actually transmitting PRACH in all four PRACH slots within a 60kHz time slot.

[0096] (Alt.C1) When the value of the column “Number of PRACH slots in a 60kHz time slot” is 2, there are resources that can actually transmit PRACH in the 3rd and 4th time slots of the 4 PRACH time slots in a 60kHz time slot.

[0097] (Alt.C2) When the value of the column “Number of PRACH slots in a 60kHz time slot” is 2, there are resources that can actually send PRACH in the 2nd and 4th time slots of the 4 PRACH time slots in a 60kHz time slot.

[0098] (Alt.C3) can be set via RRC signaling to either Alt.C1 or Alt.C2. That is, when the value of the "Number of PRACH time slots in a 60kHz time slot" column is 2, the base station 20 can set the actual PRACH transmission resources in any one of the four PRACH time slots in the 60kHz time slot, and notify the terminal 10 of the setting information via RRC signaling.

[0099] As mentioned above, when the number of PRACH time slots contained in a unit time slot is greater than 2, it can be specified that, as shown above, the number of PRACH time slots is greater than 2. Figure 12 The example shows which PRACH slot the PRACH configuration index specifies.

[0100] (Alt.B2) can import a new table specifying the correspondence between PRACH configuration and PRACH configuration index for the frequency band from 52.6GHz to 71GHz. Figure 7 This is a diagram showing an example of a newly introduced table for the frequency band from 52.6 GHz to 71 GHz.

[0101] (Opt.1) can also be used for the frequency band from 52.6 GHz to 71 GHz, but only a portion of the formats A0, A1, A2, A3, B1, B2, B3, B4, C0, and C2 are supported.

[0102] Figure 8This diagram illustrates examples of formats A0, A1, A2, A3, B1, B2, B3, B4, C0, and C2. For example, in the frequency band from 52.6 GHz to 71 GHz, due to the envisioned reduction in cell size, C0 and C2, corresponding to longer protection periods, may not be supported. Furthermore, since, for example, beam switching requires time, A0, A1, A2, and A3, which do not include protection periods, may also not be supported. For example, only B1, B2, B3, and B4 from formats A0, A1, A2, A3, B1, B2, B3, B4, C0, and C2 may be supported.

[0103] (Opt.2) can also import new formats for frequency bands from 52.6 GHz to 71 GHz.

[0104] For example, for the frequency band from 52.6 GHz to 71 GHz, a format can be imported in which a cyclic prefix is ​​inserted for each OFDM symbol of PRACH corresponding to the switching of the transmit beam in base station 20. Figure 9 This is a diagram illustrating an example of the format for inserting a cyclic prefix for each OFDM symbol of PRACH.

[0105] In addition, for example, for the frequency band from 52.6 GHz to 71 GHz, a format with a higher number of repetitions of PRACH OFDM symbols can be imported to improve coverage. Figure 10 This is a diagram showing an example of a format where PRACH OFDM symbols are repeated a large number of times.

[0106] In addition, for example, a shorter format of cyclic prefix (or guard period) can be imported for the frequency band from 52.6 GHz to 71 GHz. Figure 11 This is a diagram showing an example of a shorter format for the cyclic prefix (or guard period).

[0107] (Opt.3) Alternatively, for the frequency band from 52.6 GHz to 71 GHz, new values ​​for parameters can be imported into the table that specifies the correspondence between PRACH configuration and PRACH configuration index.

[0108] Figure 13 This is a diagram illustrating an example of importing new values ​​for parameters into a table. For example, as shown... Figure 13As shown in the example table, 44, 49, 54, 59, 64, 69, 74, and 70 can be added as slot numbers. Furthermore, for "Number of PRACH slots," the number of PRACH slots in the slot corresponding to the new subcarrier spacing can be added, such as "Number of PRACH slots within a 120kHz slot."

[0109] (Alt.B3) can be used as follows Figure 12 The example shows a table that specifies the correspondence between the PRACH configuration and the PRACH configuration index applicable to FR2, and is applied to the frequency band from 52.6 GHz to 71 GHz.

[0110] Figure 7 This diagram illustrates an example of changing the FR2 table to a frequency band from 52.6 GHz to 71 GHz. Figure 7 In the example, in the column for "Number of PRACH slots within a 60kHz slot", in addition to the column for PRACH SCS = 120kHz, a column for PRACH SCS = 240kHz has been added. Furthermore, in Figure 7 The example records SCSs of 120kHz and 240kHz, but this is just one example; there could be multiple other SCSs such as 120kHz and 480kHz.

[0111] (Action Example 2)

[0112] For example, in the frequency band from 52.6 GHz to 71 GHz, during initial access, terminal 10 receives system information, including PRACH configuration information, from base station 20. Based on the value of the PRACH configuration index contained in the received PRACH configuration information, terminal 10 sets the PRACH configuration associated with that PRACH configuration index value and sends a random access preamble to base station 20. Here, the PRACH configuration associated with the PRACH configuration index value can be any one of Alt.B1 to Alt.B3.

[0113] (UE capability)

[0114] Terminal 10 sends capability information related to whether the PRACH format can be applied (e.g., capability information indicating whether it is possible to apply all (or part) of the PRACH format (including sequence length and / or SCC) applicable to the frequency band from 52.6 GHz to 71 GHz). Based on this capability information, the base station sends configuration information related to PRCH to terminal 10 (such as the configuration information described in Proposal 1 and / or 2).

[0115] (Alt.D1) For terminal 10 that supports frequency bands from 52.6 GHz to 71 GHz, it is possible to apply all PRACH formats (including sequence length and / or SCS) applicable to frequency bands from 52.6 GHz to 71 GHz.

[0116] (Alt.D2) For terminal 10 that supports operation in the unlicensed frequency band from 52.6 GHz to 71 GHz, it is able to apply the full PRACH format (including sequence length and / or SCS) applicable to the frequency band from 52.6 GHz to 71 GHz.

[0117] In contrast, for terminal 10 which only supports operations in licensed frequency bands from 52.6 GHz to 71 GHz, the PRACH format (e.g., sequence length 1151 or 571) that can be applied to terminal 10 which supports operations in unlicensed frequency bands from 52.6 GHz to 71 GHz may not be applicable.

[0118] (Device Structure)

[0119] Next, an example of the functional structure of the terminal 10 and base station 20 performing the processing operations described above will be explained. The terminal 10 and base station 20 have all the functions described in this embodiment. However, the terminal 10 and base station 20 may also have only a portion of the functions described in this embodiment. Furthermore, the terminal 10 and base station 20 may be collectively referred to as a communication device.

[0120] <Terminal>

[0121] Figure 14 This is a diagram illustrating an example of the functional structure of terminal 10. (As shown...) Figure 14 As shown, terminal 10 has a transmitting unit 110, a receiving unit 120 and a control unit 130. Figure 14 The functional structure shown is merely an example. The functional divisions and names of the functional units can be arbitrary, as long as the operation of this embodiment can be performed. Alternatively, the transmitting unit 110 can be called a transmitter, and the receiving unit 120 can be called a receiver.

[0122] The transmitting unit 110 generates a transmission signal based on the transmission data and transmits the signal wirelessly. Furthermore, the transmitting unit 110 is capable of forming one or more beams. The receiving unit 120 wirelessly receives various signals and extracts higher-level signals from the received physical layer signals. Additionally, the receiving unit 120 includes a measurement unit that measures the signal to be received to obtain the received power, etc.

[0123] The control unit 130 controls the terminal 10. Alternatively, the functions of the control unit 130 related to transmission can be included in the transmission unit 110, and the functions of the control unit 130 related to reception can be included in the reception unit 120.

[0124] For example, in the frequency band from 52.6 GHz to 71 GHz, during initial access, the receiving unit 120 of terminal 10 receives system information, including PRACH configuration information, from base station 20. The control unit 130 of terminal 10 selects an orthogonal sequence of a format applicable to PRACH based on parameters specified by the information element prach-RootSequenceIndex included in the received PRACH configuration information. Furthermore, the control unit 130 of terminal 10 sets the PRACH subcarrier spacing and the PUSCH subcarrier spacing based on the PRACH configuration information included in the received system information. The transmitting unit 110 of terminal 10, applying the PRACH format and PRACH subcarrier spacing selected by the control unit 130, transmits a random access preamble to base station 20.

[0125] For example, in the frequency band from 52.6 GHz to 71 GHz, during initial access, the receiving unit 120 of terminal 10 receives system information, including PRACH configuration information, from base station 20. The control unit 130 of terminal 10 sets the PRACH configuration associated with the received PRACH configuration index value, and the transmitting unit 110 sends a random access preamble to base station 20. Here, the PRACH configuration associated with the PRACH configuration index value can be any one of Alt.B1 to Alt.B3.

[0126] <Base Station 20>

[0127] Figure 15 This is a diagram illustrating an example of the functional structure of base station 20. (As shown...) Figure 15 As shown, the base station 20 has a transmitting unit 210, a receiving unit 220 and a control unit 230. Figure 15The functional structure shown is merely an example. The functional divisions and names of the functional units can be arbitrary, as long as the operation of this embodiment can be performed. Alternatively, the transmitting unit 210 can be called a transmitter, and the receiving unit 220 can be called a receiver.

[0128] The transmitting unit 210 includes the function of generating a signal to be transmitted to the terminal 10 and transmitting the signal wirelessly. The receiving unit 220 includes the function of receiving various signals transmitted from the terminal 10 and obtaining, for example, higher-level information from the received signals. In addition, the receiving unit 220 includes a measurement unit for measuring the signal to be received to obtain the received power, etc.

[0129] The control unit 230 controls the base station 20. Alternatively, the functions of the control unit 230 related to transmission can be included in the transmission unit 210, and the functions of the control unit 230 related to reception can be included in the reception unit 220.

[0130] For example, in the frequency band from 52.6 GHz to 71 GHz, the control unit 230 of base station 20 includes parameters in the information element prach-RootSequenceIndex specifying candidate orthogonal sequences that can be applied to PRACH, and sends system information including the prach-RootSequenceIndex and other PRACH setting information to terminal 10. The receiving unit 220 of base station 20 uses the PRACH subcarrier spacing and PUSCH subcarrier spacing specified by the control unit 230 in the PRACH setting information to receive the random access preamble sent from terminal 10.

[0131] For example, the control unit 230 selects the PRACH configuration that is actually set for the terminal 10 from multiple PRACH configurations that can be set for the terminal 10 in the frequency band from 52.6 GHz to 71 GHz, and the transmitting unit 210 sends system information to the terminal 10, including PRACH configuration information such as the value of the PRACH configuration index corresponding to the PRACH configuration selected by the control unit 230. The receiving unit 220 of the base station 20 receives the random access preamble sent from the terminal 10 according to the PRACH configuration selected by the control unit 230.

[0132] <Hardware Structure>

[0133] The block diagrams used in the description of the above embodiments ( Figures 14-15The diagram illustrates blocks organized by function. These functional blocks (structural units) are implemented through any combination of hardware and / or software. Furthermore, there are no particular limitations on the means of implementing each functional block. That is, each functional block can be implemented by a device that physically and / or logically combines multiple elements, or by connecting two or more physically and / or logically separate devices directly or indirectly (e.g., using wired and / or wireless connections).

[0134] Furthermore, for example, in one embodiment of the present invention, both the terminal 10 and the base station 20 can function as computers performing the processing of this embodiment. Figure 16 This diagram illustrates an example of the hardware structure of the terminal 10 and base station 20 according to this embodiment. The terminal 10 and base station 20 can each be configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, and a bus 1007.

[0135] Additionally, in the following description, the term "device" can be replaced with "circuit," "device," "unit," etc. The hardware structure of terminal 10 and base station 20 can be configured to include one or more of the devices shown in figures 1001 to 1006, or it can be configured to not include any of them.

[0136] The functions in terminal 10 and base station 20 are implemented by reading predetermined software (programs) into hardware such as processor 1001 and memory 1002, so that processor 1001 performs calculations and controls the communication of communication device 1004, and the reading and / or writing of data in memory 1002 and storage 1003.

[0137] The processor 1001 controls the computer as a whole, for example, by enabling the operating system to function. The processor 1001 may also be a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic units, registers, etc.

[0138] Furthermore, the processor 1001 reads programs (program code), software modules, or data from the memory 1003 and / or communication device 1004 into the memory 1002, and performs various processes accordingly. As a program, a program is used that causes the computer to perform at least a portion of the actions described in the above embodiments. For example, this can also be achieved using a control program stored in the memory 1002 and operating in the processor 1001. Figure 14The terminal 10 shown includes a transmitting unit 110, a receiving unit 120, and a control unit 130. Alternatively, it can be implemented, for example, using a control program stored in memory 1002 and operated in processor 1001. Figure 15 The base station 20 shown includes a transmitting unit 210, a receiving unit 220, and a control unit 230. Although it has been described that the various processes described above are executed by a single processor 1001, they can also be executed simultaneously or sequentially by two or more processors 1001. Alternatively, more than one chip can be used to install the processor 1001. Furthermore, the program can also be transmitted from a network via a telecommunications line.

[0139] Memory 1002 is a computer-readable recording medium, and may be composed of at least one of ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), etc. Memory 1002 may also be referred to as a register, cache, main memory (main storage device), etc. Memory 1002 can store programs (program code), software modules, etc., that are executable for carrying out the processing involved in one embodiment of the present invention.

[0140] The memory 1003 is a computer-readable recording medium, which may be composed of at least one of the following: CD-ROM (Compact Disc ROM), hard disk drive, floppy disk, magneto-optical disk (e.g., compact disc, digital multipurpose disk, Blu-ray disc, smart card, flash memory (e.g., card, stick, key drive), floppy disk, magnetic stripe, etc.). The memory 1003 may also be referred to as an auxiliary storage device. The aforementioned storage medium may, for example, include a database, server, and other suitable media that include memory 1002 and / or memory 1003.

[0141] The communication device 1004 is hardware (transceiver) used for communication between computers via wired and / or wireless networks. It may also be referred to as a network device, network controller, network interface card (NIC), or communication module. For example, the transmitting unit 110 and receiving unit 120 of terminal 10 can also be implemented using the communication device 1004. Furthermore, the transmitting unit 210 and receiving unit 220 of base station 20 can also be implemented using the communication device 1004.

[0142] Input device 1005 is an input device that accepts input from external sources (e.g., keyboard, mouse, microphone, switch, button, sensor, etc.). Output device 1006 is an output device that performs output to external sources (e.g., display, speaker, LED, etc.). Alternatively, input device 1005 and output device 1006 can also be integrated (e.g., a touch panel).

[0143] Furthermore, devices such as processor 1001 and memory 1002 are connected via bus 1007 for communicating information. Bus 1007 can consist of a single bus or different buses between devices.

[0144] Furthermore, terminal 10 and base station 20 can be configured to include hardware such as microprocessors, digital signal processors (DSPs), ASICs (Application Specific Integrated Circuits), PLDs (Programmable Logic Devices), and FPGAs (Field Programmable Gate Arrays), and can also implement part or all of the functional blocks through such hardware. For example, processor 1001 can be installed using at least one of these hardware components.

[0145] (Summary of Implementation Methods)

[0146] This specification discloses at least the following terminals and base stations.

[0147] A terminal includes: a receiving unit that receives setting information for a high-frequency band above the frequency band of a New Radio (NR) system, which is a frequency range 1 (FR1) as a low-frequency band and a frequency range 2 (FR2) as a high-frequency band; and a control unit that sets at least one of the following items according to the setting information: the format of a random access preamble, the sequence of the random access preamble, the subcarrier spacing of the channel used to transmit the random access preamble, and the subcarrier spacing of the uplink shared channel.

[0148] Based on the above structure, the terminal can perform settings related to the transmission of random access preambles in high-frequency bands that can be applied to FR2 and above.

[0149] The sequence length of the random access preamble sequence may be greater than the sequence length of the random access preamble sequence that can be used in the unlicensed frequency band of FR2.

[0150] Based on the above structure, even in unlicensed frequency bands above the FR2 band, the terminal can set the total transmission power higher when the transmission output is limited by the upper limit of PSD (power spectrum density).

[0151] The subcarrier spacing used for transmitting the random access preamble and the subcarrier spacing used for the uplink shared channel can be the same.

[0152] Based on the above structure, the terminal can set the subcarrier interval used for transmitting the random access preamble and the subcarrier interval used when transmitting data to be the same.

[0153] The subcarrier spacing of the channel used for transmitting the random access preamble may be different from the subcarrier spacing used for the uplink shared channel.

[0154] Based on the above structure, the terminal can set the subcarrier spacing of the channel used for transmitting the random access preamble to be different from the subcarrier spacing used when transmitting data.

[0155] A base station includes: a control unit that sets setting information in a high-frequency band above the frequency band of a low-frequency band (FR1) and a high-frequency band (FR2) in a New Radio (NR) system, including at least one of the following: a format of a random access preamble that can be set for a terminal, a sequence of the random access preamble, a subcarrier spacing for a channel used to transmit the random access preamble, and a subcarrier spacing for an uplink shared channel; and a transmission unit that transmits the setting information to the terminal.

[0156] Based on the above structure, the base station can send information to the terminal regarding the setting of a random access preamble for the terminal application in a high-frequency band above the FR2 band.

[0157] (Supplement to the implementation method)

[0158] The embodiments of the present invention have been described above, but the disclosed invention is not limited to such embodiments. Those skilled in the art should understand various modifications, alterations, substitutions, and replacements. Specific numerical examples have been used to facilitate understanding of the invention, but unless otherwise specified, these values ​​are merely examples, and any appropriate values ​​may be used. The distinctions between items in the above description are not essential to the present invention. Items described in two or more items may be combined as needed, and items described in one item may be applied to items described in another item (as long as there is no contradiction). The boundaries of functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries of physical components. Multiple functional units may be operated by a single physical component, or a single functional unit may be operated by multiple physical components. Regarding the processing procedures described in the embodiments, the order of processing may be interchanged unless there is a contradiction. For ease of explanation, the terminal 10 and base station 20 have been described using functional block diagrams, but such a device may also be implemented in hardware, software, or a combination thereof. The software operating via the processor of terminal 10 according to an embodiment of the present invention and the software operating via the processor of base station 20 according to an embodiment of the present invention can also be stored in random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, register, hard disk (HDD), removable disk, CD-ROM, database, server and other suitable storage media, respectively.

[0159] The notification of information is not limited to the forms / implementations described in this specification, and may also be carried out by other methods. For example, the notification of information may be implemented through physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), higher layer signaling (e.g., RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling, broadcast information (MIB (Master Information Block), SIB (System Information Block)), other signals, or combinations thereof. In addition, RRC signaling may also be referred to as RRC messages, such as RRC connection setup messages, RRC connection reconfiguration messages, etc.

[0160] The various forms / implementations described in this specification can also be applied to LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G, 5G, FRA (Future Radio Access), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, UWB (Ultra-Wide Band), Bluetooth (registered trademark), systems using other suitable systems, and / or next-generation systems extended therefrom.

[0161] The processing procedures, timing, and flow of the various forms / implementations described in this specification may be rearranged in order, provided there is no contradiction. For example, the elements of each step in the methods described in this specification are indicated by an illustrated sequence, but are not limited to the specific sequence indicated.

[0162] In this specification, certain actions purported to be performed by base station 20 may sometimes be performed through its upper node, depending on the circumstances. In a network consisting of one or more network nodes having base station 20, it is obvious that various actions performed to communicate with terminal 10 can be performed through base station 20 and / or other network nodes besides base station 20 (e.g., consider MME or S-GW, but not limited to these). In the above, other network nodes besides base station 20 are illustrated as one case, but it could also be a combination of multiple other network nodes (e.g., MME and S-GW).

[0163] The various forms / implementations described in this specification can be used individually or in combination, and can be switched depending on the execution.

[0164] For terminal 10, those skilled in the art sometimes also use the following terms: subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handheld device, user agent, mobile client, client, or some other appropriate terms.

[0165] For base station 20, those skilled in the art sometimes also refer to it by the following terms: NB (NodeB), eNB (enhanced NodeB), base station, gNB, or some other appropriate terms.

[0166] The Bandwidth Part (BWP) (which may also be referred to as partial bandwidth, etc.) can represent a subset of contiguous common resource blocks (RBs) used for a certain parameter set in a given carrier. Here, common resource blocks can be determined by indexing RBs based on a common reference point of that carrier. PRBs can be defined and numbered within a BWP.

[0167] A BWP can include a UL BWP and a DL BWP. One or more BWPs can be set for a UE within one carrier.

[0168] At least one of the configured BWPs can be active, and it is not assumed that the UE will transmit or receive predetermined signals / channels outside of an active BWP. Furthermore, the terms "cell," "carrier," etc., used in this disclosure can be replaced with "BWP."

[0169] A radio frame can consist of one or more frames in the time domain. Each frame in the time domain can be called a subframe. A subframe can be further composed of one or more time slots in the time domain. A subframe can also be a fixed time length (e.g., 1 ms) independent of the parameter set (numerology). The parameter set can also be communication parameters applied to at least one party in the transmission and reception of a signal or channel. The parameter set can represent, for example, at least one of the following: subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame structure, specific filtering processing performed by the transceiver in the frequency domain, and specific windowing processing performed by the transceiver in the time domain. A time slot in the time domain can consist of one or more symbols (OFDM (Orthogonal Frequency Division Multiplexing) symbols, SC-FDMA (Single Carrier Frequency Division Multiple Access) symbols, etc.). A time slot can be a time unit based on a parameter set. A time slot can contain multiple mini-time slots. Each mini-time slot can consist of one or more symbols in the time domain. Furthermore, a mini-time slot can also be called a sub-time slot. A mini-time slot can consist of fewer symbols than a time slot. A PDSCH (or PUSCH) transmitted in time units larger than a mini-time slot can be called PDSCH (or PUSCH) mapping type (type) A. A PDSCH (or PUSCH) transmitted using mini-time slots can be called PDSCH (or PUSCH) mapping type (type) B. Radio frames, subframes, time slots, mini-time slots, and symbols all represent time units for transmitting signals. Radio frames, subframes, time slots, mini-time slots, and symbols can each use corresponding other names. For example, one subframe can be called a Transmission Time Interval (TTI), multiple consecutive subframes can also be called a TTI, and one time slot or one mini-time slot can also be called a TTI. That is, at least one of the subframe and TTI can be an existing LTE subframe (1ms), a period shorter than 1ms (e.g., symbols 1-13), or a period longer than 1ms. In addition, the unit representing TTI may not be called a subframe, but a slot, mini slot, etc.

[0170] Here, TTI refers, for example, to the smallest time unit for scheduling in wireless communication. For instance, in an LTE system, the base station schedules the allocation of radio resources (bandwidth, transmit power, etc., available to each user terminal) in units of TTI. However, the definition of TTI is not limited to this. TTI can be the transmission time unit for channel-coded data packets (transmission blocks), code blocks, codewords, etc., or it can be a processing unit for scheduling, link adaptation, etc. Furthermore, when a TTI is given, the actual time interval (e.g., the number of symbols) that the transmission block, code block, codeword, etc., is mapped to can be shorter than that TTI. Additionally, when one time slot or one mini-time slot is referred to as the TTI, more than one TTI (i.e., more than one time slot or more than one mini-time slot) can constitute the smallest time unit for scheduling. Moreover, the number of time slots (number of mini-time slots) constituting this smallest time unit for scheduling can be controlled. A TTI with a duration of 1ms can be referred to as a normal TTI (in LTE Rel.8-12), a long TTI, a normal subframe, a normal subframe, a long subframe, or a time slot. A TTI shorter than a normal TTI can be referred to as a shortened TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a mini time slot, a sub-time slot, or a time slot. Furthermore, a long TTI (e.g., a normal TTI, a subframe) can be replaced by a TTI with a duration longer than 1ms, and a short TTI (e.g., a shortened TTI) can be replaced by a TTI shorter than a long TTI but longer than 1ms.

[0171] A resource block (RB) is a unit of resource allocation in both the time and frequency domains. In the frequency domain, it can contain one or more consecutive subcarriers. The number of subcarriers contained in an RB can be the same regardless of the parameter set; for example, it can contain 12 subcarriers. The number of subcarriers contained in an RB can also be determined based on the parameter set. Furthermore, the time domain of an RB can contain one or more symbols, and can be a time slot, a mini-time slot, a subframe, or a time interval (TTI). A TTI, a subframe, etc., can each be composed of one or more resource blocks. Additionally, one or more RBs can be called a Physical Resource Block (PRB), a Sub-Carrier Group (SCG), a Resource Element Group (REG), a PRB pair, an RB pair, etc. Moreover, a resource block can be composed of one or more Resource Elements (REs). For example, 1 RE can be a radio resource area containing 1 subcarrier and 1 symbol.

[0172] The terms "determining" and "determining" used in this specification sometimes encompass a variety of actions. For example, "determining" or "determining" can include actions such as judging, calculating, computing, processing, deriving, investigating, looking up (e.g., searching in a table, database, or other data structure), and ascertaining, which are considered actions that have undergone "determining" or "determining." Furthermore, "determining" or "determining" can include actions such as receiving (e.g., receiving information), transmitting (e.g., sending information), inputting, outputting, and accessing (e.g., accessing data in memory), which are considered actions that have undergone "determining" or "determining." Additionally, "determining" or "determining" can include actions such as resolving, selecting, choosing, establishing, and comparing, which are considered actions that have undergone "determining" or "determining." That is, "judgment" and "decision" can include matters that are considered to have been "judged" or "decided" to take any action.

[0173] The use of the word "based on" in this specification, unless otherwise expressly stated, does not mean "based on only". In other words, the use of the word "based on" means both "based on only" and "based on at least".

[0174] When the terms "include," "including," and variations thereof are used in this specification or claims, these terms, like "comprising," imply inclusion. Furthermore, the term "or" as used in this specification or claims means not XOR.

[0175] Throughout this disclosure, for example, in cases where articles such as a, an, and the in English are added through translation, multiple articles may be included unless explicitly stated from the context otherwise.

[0176] The present invention has been described in detail above, but it will be clear to those skilled in the art that the invention is not limited to the embodiments described in this specification. The present invention can be practiced in modified and altered ways without departing from the spirit and scope of the invention as defined by the claims. Therefore, the purpose of this specification is illustrative and it is not intended to limit the scope of the invention.

[0177] Label Explanation

[0178] 10: Terminal;

[0179] 110: Dispatch Department;

[0180] 120: Receiving Unit;

[0181] 130: Control Department;

[0182] 20: Base station;

[0183] 210: Sending Department;

[0184] 220: Receiving unit;

[0185] 230: Control Department;

[0186] 1001: Processor;

[0187] 1002: Memory;

[0188] 1003: Memory;

[0189] 1004: Communication device;

[0190] 1005: Input device;

[0191] 1006: Output device.

Claims

1. A terminal having: The control unit generates a random access preamble in a frequency band above a predetermined frequency in the wireless communication system; and The transmitting unit transmits the random access preamble using a preamble format. Any subcarrier spacing among the multiple subcarrier spacings used in the frequency band is used in the preamble format. The control unit generates the random access preamble based on the sequence length of the random access preamble that can be applied to one of the plurality of subcarrier intervals. The subcarrier spacing is 480kHz, and the sequence length applicable to the subcarrier spacing is 571. Each subcarrier interval applied to the preamble format is associated with each subcarrier interval applied to the uplink shared channel, as well as the sequence length. The sequence lengths corresponding to the plurality of subcarrier intervals applied to the preamble format and the plurality of subcarrier intervals applied to the uplink shared channel are 139, 571, or 1151.

2. The terminal according to claim 1, wherein, The frequency band is from 52.6 GHz to 71 GHz.

3. The terminal according to claim 1, wherein, The subcarrier spacing is a subcarrier spacing of 120 kHz or higher.

4. The terminal according to claim 1, wherein, The plurality of subcarrier intervals include a 480 kHz subcarrier interval.

5. A base station, comprising: A transmitting unit that sends information representing the preamble format to the terminal, the preamble format being used for transmitting random access preambles; and The receiving unit receives a random access preamble transmitted by the terminal using the preamble format in a frequency band above a predetermined frequency in the wireless communication system. Any subcarrier spacing among the multiple subcarrier spacings used in the frequency band is used in the preamble format. The random access preamble is generated based on the sequence length of the random access preamble that can be applied to one of the plurality of subcarrier intervals. The subcarrier spacing is 480kHz, and the sequence length applicable to the subcarrier spacing is 571. Each subcarrier interval applied to the preamble format is associated with each subcarrier interval applied to the uplink shared channel, as well as the sequence length. The sequence lengths corresponding to the plurality of subcarrier intervals applied to the preamble format and the plurality of subcarrier intervals applied to the uplink shared channel are 139, 571, or 1151.

Images