Terminal device

Abstract

To efficiently perform communication.SOLUTION: A terminal device includes: a reception part that receives a PDCCH to which DCI is mapped; and a transmission part that transmits a random access preamble in a random access procedure started by the PDCCH. If the DCI includes a DCI field and the DCI field indicates a first value, a random access procedure is initiated based on a first higher layer parameter. If the DCI includes a DCI field and if the DCI field indicates a second value, the random access procedure is initiated based on a second higher layer parameter. If the DCI does not include the DCI field, a random access procedure is initiated based on a third higher layer parameter. All of the first higher layer parameter, the second higher layer parameter, and the third higher layer parameter include a RACH configuration, and the first higher layer parameter corresponds to one additional PCI index.SELECTED DRAWING: Figure 10

Description

[Technical Field]

[0001] The present invention relates to a terminal device. [Background technology]

[0002] The radio access method and radio network for cellular mobile communications (hereinafter referred to as "Long Term Evolution (LTE)" or "EUTRA: Evolved Universal Terrestrial Radio Access") is being developed by the Third Generation Partnership Project (3GPP). rd This is being studied in the LTE Generation Partnership Project. In LTE, base station devices are also called eNodeBs (evolved NodeBs) and terminal devices are also called UEs (User Equipment). LTE is a cellular communication system in which areas covered by base station devices are arranged in multiple cell-like configurations. A single base station device may manage multiple serving cells.

[0003] 3GPP is currently studying the next-generation standard (NR: New Radio) to propose it to IMT (International Mobile Telecommunication)-2020, a standard for next-generation mobile communication systems formulated by the International Telecommunication Union (ITU) (Non-Patent Document 1). NR is a technology that combines eMBB (enhanced Mobile Broadband) and ), mMTC (massive Machine Type Communication), and URLLC (Ultra Reliable and Low Latency Communication). .

[0004] 3GPP is currently studying the expansion of services supported by NR (non- Patent document 2). [Prior art documents] [Non-patent literature]

[0005] [Non-Patent Document 1] "New SID proposal: Study on New Radio Access Technology", RP-160671, NTT docomo, 3GPP TSG RAN Meeting #71, Goteborg, Sweden, 7th - 10th March, 2016. [Non-patent document 2] “Release 17 package for RAN”, RP-193216, RAN chairman, RAN1 chairman, RAN2 chairman, RAN3 chairman, 3GPP TSG RAN Meeting #86, Sitges, Spain, 9th ― 12th December, 2019 [Non-patent document 3] “Release 18 package summary”, RP-213469, RAN chairman, RAN1 chairman, RAN2 chairman, RAN3 chairman, 3GPP TSG RAN Meeting #94-e, 6th ― 17th December, 2021 Summary of the Invention [Problem to be solved by the invention]

[0006] The present invention provides a terminal device that performs efficient communication, a communication method used in the terminal device, a base station device that performs efficient communication, and a communication method used in the base station device. [Means for solving the problem]

[0007] (1) A first aspect of the present invention is a terminal device, comprising: a receiver for receiving a PDCCH on which DCI is arranged; and a random access control unit for controlling a random access in a random access procedure initiated by the PDCCH. a transmitter for transmitting a preamble, wherein if the DCI includes a DCI field and if the DCI field indicates a first value, the transmitter for transmitting a preamble based on a first higher layer parameter When the random access procedure is initiated and the DCI includes the DCI field, and if the DCI field indicates a second value, the random access procedure is initiated based on a second higher layer parameter. If a random access procedure is initiated and the DCI does not include the DCI field, the random access procedure is initiated based on third upper layer parameters, where all of the first upper layer parameters, the second upper layer parameters, and the third upper layer parameters include a RACH configuration, and the first upper layer parameters correspond to one additional PCI index.

[0008] (2) A second aspect of the present invention is a base station apparatus, comprising: a transmitter that transmits a PDCCH on which DCI is arranged; and a random access procedure initiated by the PDCCH, a receiving unit for receiving a system access preamble, and if the DCI includes a DCI field and if the DCI field indicates a first value, and if the DCI includes the DCI field and if the DCI field indicates a second value, and if the DCI does not include the DCI field, the random access procedure is initiated based on a third upper layer parameter, wherein all of the first upper layer parameter, the second upper layer parameter, and the third upper layer parameter include a RACH configuration, and the first upper layer parameter corresponds to one additional PCI index.

[0009] (3) A third aspect of the present invention is a terminal device, comprising: a receiving unit for receiving a PDCCH on which DCI is arranged; and a random access procedure initiated by the PDCCH, a transmitter unit for transmitting an access preamble, wherein if a CORESET pool index corresponding to the PDCCH has a first value, the random access procedure is initiated based on a first upper layer parameter, if the CORESET pool index corresponding to the PDCCH has a second value, the random access procedure is initiated based on a second upper layer parameter, if the first upper layer parameter is not configured, the random access procedure is initiated based on a third upper layer parameter, and all of the first upper layer parameter, the second upper layer parameter, and the third upper layer parameter include a RACH configuration.

[0010] (4) A fourth aspect of the present invention is a base station apparatus, comprising: a transmitter that transmits a PDCCH on which DCI is arranged; and a random access procedure initiated by the PDCCH, and a receiving unit for receiving a random access preamble, wherein if a CORESET pool index corresponding to the PDCCH has a first value, the random access procedure is initiated based on a first higher layer parameter, if the CORESET pool index corresponding to the PDCCH has a second value, the random access procedure is initiated based on a second higher layer parameter, and if the first higher layer parameter is not configured, the random access procedure is initiated based on a third higher layer parameter, and all of the first higher layer parameter, the second higher layer parameter, and the third higher layer parameter include a RACH configuration. [Effects of the Invention]

[0011] According to the present invention, the terminal device can perform communication efficiently, and the base station device can perform communication efficiently. [Brief explanation of the drawings]

[0012] [Figure 1] 1 is a conceptual diagram of a wireless communication system according to an aspect of the present embodiment. [Figure 2] 10 is an example showing the relationship between a subcarrier spacing setting μ, the number of OFDM symbols per slot Nslot symb, and a cyclic prefix (CP) setting according to one aspect of the present embodiment. [Figure 3] FIG. 10 is a diagram illustrating an example of a method for configuring a resource grid according to an aspect of the present embodiment. [Figure 4] FIG. 3 is a diagram illustrating an example of the configuration of a resource grid 3001 according to an aspect of the present embodiment. [Figure 5] 2 is a schematic block diagram illustrating an example of the configuration of a base station device 3 according to one aspect of the present embodiment. FIG. [Figure 6] 1 is a schematic block diagram showing an example of the configuration of a terminal device 1 according to an aspect of the present embodiment. [Figure 7] FIG. 2 is a diagram illustrating an example of the configuration of an SS / PBCH block according to one aspect of this embodiment. [Figure 8] FIG. 10 is a diagram illustrating an example of a monitoring opportunity for a set of search areas according to one aspect of the present embodiment. [Figure 9] FIG. 10 is a diagram illustrating an example of second TA acquisition according to one aspect of the present embodiment. [Figure 10] FIG. 1 is a diagram showing examples of means 1a, means 1b, and means 1c according to one aspect of the present embodiment. [Figure 11] FIG. 2 is a diagram showing examples of means 2a and means 2b according to one aspect of the present embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0013] Hereinafter, an embodiment of the present invention will be described.

[0014] floor(C) may be a floor function for real number C. For example, floor(C) may be a function that outputs the largest integer that does not exceed real number C. ceil(D) may be a ceiling function for real number D. For example, ceil(D) may be a function that outputs the smallest integer that does not fall below real number D. mod(E,F) is a function that outputs the remainder when E is divided by F. mod(E,F) is a function that outputs the value corresponding to the remainder when E is divided by F. exp(G)=e^G, where e is Napier's constant. H^I indicates H to the Ith power. max(J,K) is a function that outputs the maximum value among J and K. Here, if J and K are equal, max(J,K) is a function that outputs J or K. min(L,M) is a function that outputs the maximum value among L and M. Here, if L and M are equal, min(L,M) is a function that outputs L or M. round(N) is a function that outputs the integer value closest to N. "·" indicates multiplication.

[0015] In a wireless communication system according to an aspect of the present embodiment, at least Orthogonal Frequency Division Multiplexing (OFDM) is used. An OFDM symbol is a unit of time domain of OFDM. An OFDM symbol includes at least one or more subcarriers. The OFDM symbol is converted into a time-continuous signal in baseband signal generation. In the downlink, at least CP-OFDM (Cyclic Prefix - Orthogonal Frequency Division Multiplex) is used. In the uplink, either CP-OFDM or DFT-s-OFDM (Discrete Fourier Transform - spread - Orthogonal Frequency Division Multiplex) is used. DFT-s-OFDM is an improvement over CP-OFDM. It may be provided by applying transform precoding.

[0016] The OFDM symbol may be a name including a CP added to the OFDM symbol. In other words, a certain OFDM symbol may be configured to include the certain OFDM symbol and the CP added to the certain OFDM symbol.

[0017] Fig. 1 is a conceptual diagram of a wireless communication system according to one aspect of the present embodiment. In Fig. 1, the wireless communication system includes at least terminal devices 1A to 1C and a base station device 3 (BS#3: Base station#3). Hereinafter, the terminal devices 1A to 1C will also be referred to as terminal device 1 (UE#1: User Equipment#1).

[0018] The base station device 3 may be configured to include one or more transmitting devices (or transmission points, transmitting / receiving devices, transmitting / receiving points). When the base station device 3 is configured by multiple transmitting devices, each of the multiple transmitting devices may be located at a different position. For example, the base station device 3 may be configured as follows: For example, the base station device 3 may be configured with a transmission / reception point 3a and a transmission device 3b. For example, the base station device 3 may be configured with a transmitting / receiving point 3a and a transmitting / receiving point 3b. It may be configured as follows.

[0019] The base station device 3 may provide one or more serving cells. A serving cell may be defined as a set of resources used for wireless communication. A serving cell may also be referred to as a cell.

[0020] A serving cell may be configured to include one or both of a downlink component carrier (downlink carrier) and one or both of an uplink component carrier (uplink carrier). A serving cell may be configured to include one or both of two or more downlink component carriers and two or more uplink component carriers. Downlink component carriers and uplink component carriers are also collectively referred to as component carriers (carriers).

[0021] For example, one resource grid may be provided for each component carrier. Alternatively, one resource grid may be provided for each set of one component carrier and a certain subcarrier spacing configuration μ, where the subcarrier spacing configuration μ is also referred to as numerology. For example, one resource grid may be provided for a set of a certain antenna port p, a certain subcarrier spacing configuration μ, and a certain transmission direction x.

[0022] The resource grid is size,μ grid,x N RB sc where The resource grid is divided into common resource blocks N start,μ grid,x It starts from Resource Block N start,μ grid,x is also called the reference point of the resource grid.

[0023] The resource grid is subframe,μ symb It contains OFDM symbols.

[0024] The subscript x attached to the resource grid related parameters specifies the sending direction. For example, the subscript x indicates either the downlink or the uplink. It may also be used for

[0025] N size,μ grid,x is indicated by a parameter provided by the RRC layer (e.g., Data CarrierBandwidth) offset setting. start,μ grid,x is the bandwidth configuration indicated by parameters provided by the RRC layer (e.g., parameter OffsetToCarrier). The offset setting and band setting are the configuration of the SCS-specific carrier. This is the setting used for

[0026] Subcarrier spacing (SCS) for a given subcarrier spacing setting μ )Δf is Δf=2 μ 15 kHz. Here, the subcarrier spacing setting μ is 0 , 1, 2, 3, or 4 may be indicated.

[0027] FIG. 2 shows a subcarrier spacing setting μ and the number of OFDM symbols per slot N according to one aspect of this embodiment. slot symb 2A, for example, when the subcarrier spacing setting μ is 2 and the CP setting is normal cyclic prefix (CP), N slot symb =14, N frame,μ slot =40, N subframe, μ slot = 4. In addition, in FIG. 2B, for example, if the subcarrier spacing setting μ is 2, If the CP setting is an extended cyclic prefix (CP),slot symb =12, N frame ,μ slot =40, N subframe,μ slot =4.

[0028] Time unit T c may be used to represent a length in the time domain. Time unit T c is T c =1 / (Δf max N f ) Δf max = 480 kHz. f =409 6. The constant κ is κ=Δf max N f / (Δf ref N f,ref )=64. Δf ref is 1 5kHz. N f,ref is 2048.

[0029] The transmission of the signal in the downlink and / or the transmission of the signal in the uplink may be a period of length T f The radio frame (system frame, frame) may be organized into T f =(Δf max N f / 100)·T s = 10 ms. A radio frame consists of 10 subframes. The length of a subframe is T sf =(Δf max N f / 1000)·T s = 1 ms. The number of OFDM symbols per subframe is N subframe,μ symb =N slot symb N subframe,μ slot is.

[0030] In one carrier, there is a first set of one or more frames in the uplink and a second set of one or more frames in the downlink. The uplink frame for transmission from the terminal device 1 is T 10 15 20 25 30 35 40 45 50 55 60 65 2 before the start of the downlink frame. TA Start from the front T TA is (N TA N TA,offset )T c may be.

[0031] An OFDM symbol is a time domain unit of a communication system. For example, an OFDM symbol may be a time domain unit of CP-OFDM. Also, an OFDM symbol may be a time domain unit of DFT-s-OFDM.

[0032] A slot may consist of multiple OFDM symbols, for example, N consecutive OFDM symbols. slot symb One slot may be composed of OFDM symbols. For example, In the settings, N slot symb = 14. In addition, in the setting of the extended CP, N slot symb =12.

[0033] For a given subcarrier spacing setting μ, the number and index of slots contained in the subframe may be given. For example, slot index n μ s ranges from 0 to N in the subframe subframe,μ slot The sub-characters may be given in ascending order as integer values ​​in the range -1. For setting the rear interval μ, the number and index of slots included in the radio frame may be given. Also, the slot index n μ s,f ranges from 0 to N in the radio frame. frame,μ slot Integer values ​​in the range -1 to +1 may be given in ascending order.

[0034] Fig. 3 is a diagram showing an example of a resource grid configuration method according to one aspect of this embodiment. The horizontal axis in Fig. 3 represents the frequency domain. Fig. 3 shows an example of a resource grid configuration with subcarrier spacing μ1 in a component carrier 300, and an example of a resource grid configuration with subcarrier spacing μ2 in the component carrier. In this way, one or more subcarrier spacings may be set for a given component carrier. Fig. 3 assumes that μ1 = μ2-1, but various aspects of this embodiment are not limited to the condition μ1 = μ2-1.

[0035] The component carrier 300 is a band having a predetermined width in the frequency domain.

[0036] Point 3000 is an identifier for identifying a certain subcarrier. The point 3000 is also called point A. The common resource block (CRB) set 3100 is a common resource block for the subcarrier spacing setting μ1. It's a rock set.

[0037] Of the common resource block set 3100, the common resource block that includes the point 3000 (the black block in the common resource block set 3100 in FIG. 3) is also called the reference point of the common resource block set 3100. The reference point of the common resource block set 3100 may be the common resource block with index 0 in the common resource block set 3100.

[0038] The offset 3011 is the offset from the reference point of the common resource block set 3100 to the reference point of the resource grid 3001. The offset 3011 is indicated by the number of common resource blocks for the subcarrier spacing setting μ1. The resource grid 3001 is N size,μ grid1,x It contains common resource blocks.

[0039] The offset 3013 is the distance from the reference point of the resource grid 3001 to the reference point (N start,μ BWP,i1 ) is the offset to

[0040] Common resource block set 3200 is a set of common resource blocks for subcarrier spacing setting μ2.

[0041] In the common resource block set 3200, the common resource block including the point 3000 (the black block in the common resource block set 3200 in FIG. 3) is also referred to as the reference point of the common resource block set 3200. The reference point of the common resource block set 3200 may be the common resource block with index 0 in the common resource block set 3200.

[0042] The offset 3012 is the offset from the reference point of the common resource block set 3200 to the reference point of the resource grid 3002. The offset 3012 is indicated by the number of common resource blocks relative to the subcarrier spacing μ. The resource grid 3002 is N size,μ grid2,x It contains common resource blocks.

[0043] The offset 3014 is the distance from the reference point of the resource grid 3002 to the reference point of the BWP 3004 with index i2 (N start,μ BWP,i2) is the offset to

[0044] 4 is a diagram showing an example of the configuration of a resource grid 3001 according to one aspect of this embodiment. In the resource grid of FIG. 4, the horizontal axis represents OFDM symbol index l sym and the vertical axis is the subcarrier index k sc The resource grid 3001 is size,μ grid1,x N RB sc contains N subcarriers, subframe,μ symb Contains OFDM symbols. Within the grid, subcarrier index k sc and OFDM symbol index l sym The resource specified by is also called a resource element (RE).

[0045] Resource Block (RB) is N RB sc Contains consecutive subcarriers Resource blocks are divided into common resource blocks, physical resource blocks (PRBs), and virtual resource blocks (VRBs). Here, N RB sc =12.

[0046] A resource block unit is a set of resources corresponding to one OFDM symbol in one resource block, i.e., one resource block unit includes 12 resource elements corresponding to one OFDM symbol in one resource block.

[0047] The common resource blocks for a given subcarrier spacing setting μ are indexed in ascending order in the frequency domain starting from 0 in a given common resource block set. xing). For a given subcarrier spacing configuration μ, the common resource block with index 0 contains (or collides with, or coincides with) point 3000. For a given subcarrier spacing configuration μ, the common resource block with index n μ CRB is n μ CRB =ceil(k sc / N RB sc ) relationship is satisfied. Here, k sc The subcarrier with 0 corresponds to point 3000. It is a subcarrier having the same center frequency as the center frequency of the subcarrier being used.

[0048] The physical resource blocks for a given subcarrier spacing setting μ are given as follows in a given BWP: The indexes are assigned in ascending order starting from 0 in the frequency domain. The index n of the physical resource block for a given subcarrier spacing setting μ is μ PRB is n μ CRB =n μ PRB +N start,μ BWP,i where N start,μ BWP,i denotes the reference point of the BWP with index i.

[0049] A BWP is defined as a subset of common resource blocks contained in a resource grid. The BWP is located at the reference point N of the BWP. start,μ BWP,i Starting with N size,μ BWP,i Common litho The BWP configured for a downlink carrier is also called a downlink BWP. The BWP configured for an uplink component carrier is also called an uplink BWP.

[0050] An antenna port may be defined such that the channel over which a symbol on the antenna port is conveyed can be inferred from the channel over which another symbol on the same antenna port is conveyed. For example, a channel may correspond to a physical channel, a symbol may correspond to an OFDM symbol, a symbol may correspond to a resource block unit, or a symbol may correspond to a resource element.

[0051] When the large-scale properties of the channel through which symbols are transmitted at one antenna port can be estimated from the channel through which symbols are transmitted at another antenna port, the two antenna ports are said to be Quasi Co-Located (QCL). Here, the large-scale characteristics may include at least long-range channel characteristics. The large-scale characteristics may include at least some or all of delay spread, Doppler spread, Doppler shift, average gain, average delay, and beam parameters (spatial Rx parameters). The first antenna port and the second antenna port are QCLs in terms of beam parameters when the receiving beam assumed by the receiving side for the first antenna port and the second antenna port are QCLs in terms of beam parameters. The first antenna port and the second antenna port are QCLs in terms of beam parameters when the transmission beam assumed by the receiver for the first antenna port is the same (or corresponds to) the transmission beam assumed by the receiver for the first antenna port. The transmission beam assumed by the receiving side for the second antenna port may be the same (or correspond to) the transmission beam assumed by the receiving side for the second antenna port. The terminal device 1 assumes that the two antenna ports are QCLs if the large-scale characteristics of the channel through which symbols are transmitted at one antenna port can be estimated from the channel through which symbols are transmitted at the other antenna port. The fact that the two antenna ports are QCLs may mean that the two antenna ports are assumed to be QCLs.

[0052] Carrier aggregation is the process of providing multiple aggregated serving The carrier aggregation may be a method of performing communication using a plurality of aggregated component carriers. The carrier aggregation may be a method of performing communication using a plurality of aggregated downlink component carriers. Furthermore, carrier aggregation may involve communication using multiple aggregated uplink component carriers.

[0053] 5 is a schematic block diagram showing an example of the configuration of a base station device 3 according to one aspect of the present embodiment. As shown in FIG. 5, the base station device 3 includes at least a radio transmission / reception unit (physical layer processing unit) 30 and / or part or all of a higher layer processing unit 34. The radio transmission / reception unit 30 includes an antenna unit 31, an RF (Radio Frequency) unit 32, and a base station The upper layer processing unit 34 includes at least a part or all of a media access control layer processing unit 35 and a part or all of a radio resource control (RRC) layer processing unit 36.

[0054] The wireless transceiver 30 includes at least a wireless transmitter 30a and part or all of a wireless receiver 30b. The baseband unit included in the wireless transmitter 30a and the baseband unit included in the wireless receiver 30b may have the same or different device configurations. The RF unit included in the wireless transmitter 30a and the RF unit included in the wireless receiver 30b may have the same or different device configurations. The antenna unit included in the wireless transmitter 30a and the wireless receiver The antenna units included in the receiving unit 30b may have the same or different device configurations.

[0055] For example, the radio transmitting unit 30a may generate and transmit a baseband signal of a PDSCH. For example, the radio transmitting unit 30a may generate and transmit a baseband signal of a PDCCH. For example, the radio transmitting unit 30a may generate and transmit a baseband signal of a PBCH. For example, the radio transmitting unit 30a may generate and transmit a baseband signal of a radio The wireless transmitter 30a may generate and transmit a baseband signal of the synchronization signal. The radio transmitter 30a may generate and transmit a baseband signal for the PDSCH DMRS. For example, the radio transmitter 30a may generate and transmit a baseband signal for the PDCCH DMRS. For example, the radio transmitter 30a may generate and transmit a baseband signal for the CSI-RS. For example, the radio transmitter 30a may generate and transmit a baseband signal for the DL PTRS.

[0056] For example, the radio receiver 30b may receive a PRACH. For example, the radio receiver 30b may receive and demodulate a PUCCH. For example, the radio receiver 30b may receive and demodulate a PUSCH. For example, the radio receiver 30b may receive a PUCCH DMRS. For example, the radio receiver 30b The radio receiver 30b may receive a PUSCH DMRS. For example, the radio receiver 30b may receive an UL PTRS. For example, the radio receiver 30b may receive an SRS.

[0057] The upper layer processing unit 34 outputs the downlink data (transport block) to the radio transceiver unit 30 (or the radio transmitter unit 30a). The upper layer processing unit 34 performs processing on the Medium Access Control (MAC) layer, the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer, and the RRC layer.

[0058] The medium access control layer processing unit 35 included in the upper layer processing unit 34 performs MAC layer processing. The MAC layer processing may be processing by a MAC entity.

[0059] The radio resource control layer processing unit 36 ​​included in the upper layer processing unit 34 performs processing of the RRC layer. The RRC layer processing unit 36 ​​processes various setting information / parameters (RRC parameters) of the terminal device 1. The radio resource control layer processing unit 36 ​​manages the RRC message received from the terminal device 1. Set the parameters based on the message.

[0060] The radio transceiver 30 (or the radio transmitter 30a) performs processing such as modulation and encoding. The radio transceiver 30 (or the radio transmitter 30a) modulates, encodes, and transmits downlink data. The radio transmission / reception unit 30 (or the radio transmission unit 30a) generates a physical signal by generating a baseband signal (converting it into a time-continuous signal) and transmits it to the terminal device 1. Alternatively, the signal may be arranged on a component carrier and transmitted to the terminal device 1.

[0061] The radio transmitting / receiving unit 30 (or the radio receiving unit 30b) performs processes such as demodulation and decoding. The wireless transceiver 30 (or the wireless receiver 30b) separates, demodulates, and The radio transmitting / receiving unit 30 (or the radio receiving unit 30b) may perform a channel access procedure prior to transmitting a physical signal.

[0062] The RF unit 32 converts (down-converts) the signal received via the antenna unit 31 into a baseband signal by quadrature demodulation, and removes unnecessary frequency components. The RF unit 32 outputs the processed analog signal to the baseband unit.

[0063] The baseband unit 33 converts the analog signal input from the RF unit 32 into The baseband unit 33 removes a portion corresponding to a CP (Cyclic Prefix) from the converted digital signal, and performs the following on the signal from which the CP has been removed: A fast Fourier transform (FFT) is performed to extract the frequency domain signal.

[0064] The baseband unit 33 performs an inverse fast Fourier transform (IFFT) on the data to generate OFDM symbols, adds a CP to the generated OFDM symbols, and outputs the baseband symbols. The baseband unit 33 generates a baseband digital signal, and converts the baseband digital signal into an analog signal. The baseband unit 33 outputs the converted analog signal to the RF unit 32.

[0065] The RF unit 32 uses a low-pass filter to remove unnecessary frequency components from the analog signal input from the baseband unit 33, and up-converts the analog signal to a carrier frequency. The RF unit 32 converts the received signal into a digital signal and transmits it via the antenna unit 31. The RF unit 32 may also have a function to control transmission power. The RF unit 32 is also referred to as a transmission power control unit.

[0066] For the terminal device 1, one or more serving cells (or component carriers, downlink component carriers, uplink component carriers) may be configured.

[0067] Each of the serving cells configured for the terminal device 1 is a PCell (Primary cell, The SpCell may be any of a PCell, a PSCell (Primary SCG cell), a PSCell (Primary SCG cell), and a SCell (Secondary Cell). It may refer to one or both of the PSCell and the PSCell.

[0068] The PCell is a serving cell included in an MCG (Master Cell Group). The PCell is a cell (cell) in which the terminal device 1 performs an initial connection establishment procedure or a connection re-establishment procedure. (cells where the treatment was performed).

[0069] A PSCell is a serving cell included in an SCG (Secondary Cell Group). , is the serving cell to which random access is performed by the terminal device 1.

[0070] An SCell may be included in either an MCG or an SCG.

[0071] The term "serving cell group" (cell group) refers to at least an MCG and an SCG. A serving cell group may include one or more serving cells (or component carriers). The one or more serving cells (or component carriers) included in a serving cell group may be aggregated by carrier aggregation. It may be operated.

[0072] One or more downlink BWPs may be configured for each serving cell (or downlink component carrier). One or more uplink BWPs are configured for each component carrier. That's fine.

[0073] Of one or more downlink BWPs configured for a serving cell (or a downlink component carrier), one downlink BWP is set as the active downlink BWP. may be configured (or one downlink BWP may be activated). Of one or more uplink BWPs configured for a serving cell (or uplink component carrier), one uplink BWP is set as the active uplink BWP. (Alternatively, one uplink BWP may be activated).

[0074] The PDSCH, PDCCH, and CSI-RS may be received in an active downlink BWP. The terminal device 1 may attempt to receive the PDSCH, PDCCH, and CSI-RS in an active downlink BWP. The PUCCH and PUSCH are transmitted in an active uplink BWP. The terminal device 1 may transmit PUCCH and PUSCH in the active uplink BWP. The active downlink BWP and the active uplink BWP are also collectively referred to as the active BWP.

[0075] PDSCH, PDCCH, and CSI-RS are transmitted in downlink BWPs other than the active downlink BWP ( The terminal device 1 may not receive the signal in the inactive downlink BWP. In a downlink BWP that is not an active downlink BWP, the reception of PDSCH, PDCCH, and CSI-RS is PUCCH and PUSCH are not active uplink BWPs and therefore no transmission is attempted. The terminal device 1 does not need to transmit the PUCCH and the PUSCH in an uplink BWP that is not an active uplink BWP. Active BWPs are collectively referred to as inactive BWPs.

[0076] A downlink BWP switch is a process of switching one active UE in a serving cell. Deactivate the downlink BWP and deactivate the in-band BWP of the serving cell. This is the procedure to activate one of the active downlink BWPs. Downlink BWP switching may be controlled by the BWP field included in the downlink control information. Downlink BWP switching may also be controlled based on higher layer parameters. good.

[0077] Uplink BWP switching is used to deactivate one active uplink BWP and activate any inactive uplink BWP other than the one active uplink BWP. The handover may be controlled by the BWP field included in the downlink control information. BWP switching of a link may be controlled based on higher layer parameters.

[0078] Of one or more downlink BWPs configured for the serving cell, two or more A downlink BWP does not have to be set as the active downlink BWP. For a serving cell, one downlink BWP may be active at a given time.

[0079] Two or more of one or more uplink BWPs configured for the serving cell An uplink BWP does not have to be set as the active uplink BWP. For a serving cell, one uplink BWP may be active at a given time.

[0080] Fig. 6 is a schematic block diagram showing an example configuration of a terminal device 1 according to one aspect of the present embodiment. As shown in Fig. 6, the terminal device 1 includes at least one or all of a radio transmission / reception unit (physical layer processing unit) 10 and an upper layer processing unit 14. The radio transmission / reception unit 10 includes at least an antenna unit 11, an RF unit 12, and part or all of a baseband unit 13. The upper layer processing unit 14 includes at least a medium access control layer processing unit 15 and part or all of a radio resource control layer processing unit 16.

[0081] The wireless transceiver 10 includes at least a wireless transmitter 10a and a part or all of a wireless receiver 10b. The device configuration of the baseband unit 13 included in 10b may be the same or different. The RF unit 12 included in the wireless transmitting unit 10a and the RF unit 12 included in the wireless receiving unit 10b may have the same configuration or may have different configurations. The antenna unit 11 and the antenna unit 11 included in the wireless receiving unit 10b have the same device configuration. may or may not be the same.

[0082] For example, the radio transmitting unit 10a may generate and transmit a baseband signal of a PRACH. For example, the radio transmitting unit 10a may generate and transmit a baseband signal of a PUCCH. For example, the radio transmitting unit 10a may generate and transmit a baseband signal of a PUSCH. For example, the radio transmitting unit 10a may generate and transmit a baseband signal of a PUCCH DMRS. For example, the radio transmitting unit 10a may generate and transmit a baseband signal of a PUSCH DMRS. For example, the radio transmitting unit 10a may generate and transmit a baseband signal of a UL PTRS. For example, the radio transmitting unit 10a may generate and transmit a baseband signal of a PUCCH DMRS. The receiving unit 10a may generate and transmit a baseband signal of the SRS. Generating the signal may include generating an SRS sequence.

[0083] For example, the radio receiving unit 10b may receive and demodulate a PDSCH. For example, the radio receiving unit 10b may receive and demodulate a PDCCH. For example, the radio receiving unit 10b may receive a PBCH and For example, the wireless receiving unit 10b may receive a synchronization signal. The wireless receiver 10b may receive a PDSCH DMRS. For example, the wireless receiver 10b may receive a PDCCH DMRS. For example, the wireless receiver 10b may receive a CSI-RS. For example, the wireless receiver 10b may receive a DL PTRS.

[0084] The upper layer processing unit 14 outputs the uplink data (transport block) to the radio transceiver unit 10 (or the radio transmitter unit 10a). The upper layer processing unit 14 performs processing on the MAC layer, the integrated packet data protocol layer, the radio link control layer, and the RRC layer.

[0085] The medium access control layer processing unit 15 included in the upper layer processing unit 14 performs processing of the MAC layer.

[0086] The radio resource control layer processing unit 16 included in the upper layer processing unit 14 performs processing for the RRC layer. The RRC layer processing unit 16 processes various setting information / parameters (RRC parameters) of the terminal device 1. The radio resource control layer processing unit 16 manages the RRC messages received from the base station device 3. Set RRC parameters based on the message.

[0087] The radio transmission / reception unit 10 (or the radio transmission unit 10a) performs processing such as modulation and encoding. The radio transceiver 10 (or the radio transmitter 10a) modulates, encodes, and transmits uplink data. The radio transmitter / receiver 10 (or the radio transmitter 10a) generates a physical signal by generating a baseband signal (converting it into a time-continuous signal) and transmits it to the base station device 3. It may be arranged in a certain BWP (active uplink BWP) and transmitted to the base station device 3.

[0088] The radio transmitting / receiving unit 10 (or the radio receiving unit 10b) performs processes such as demodulation and decoding. The radio transceiver 10 (or the radio receiver 30b) may receive a physical signal in a certain BWP (active downlink BWP) of a certain serving cell. The radio receiving unit 10b) separates, demodulates, and decodes the received physical signal, and outputs the decoded information as The radio transmission / reception unit 10 (radio reception unit 10b) outputs the physical signal to the upper layer processing unit 14. A channel access procedure may be performed prior to the

[0089] The RF unit 12 converts (down-converts) the signal received via the antenna unit 11 into a baseband signal by quadrature demodulation, and removes unnecessary frequency components. The analog signal processed by the digital signal processing unit 12 is output to the baseband unit 13 .

[0090] The baseband unit 13 converts the analog signal input from the RF unit 12 into a digital signal. The baseband unit 13 extracts a cyclic prefix (CP) from the converted digital signal. The signal from which the CP has been removed is subjected to a fast Fourier transform (FFT) to extract the signal in the frequency domain.

[0091] The baseband unit 13 performs an inverse fast Fourier transform (IFFT) on the uplink data to generate an OFDM symbol, and adds a CP to the generated OFDM symbol. The baseband unit 13 converts the baseband digital signal into an analog signal, and outputs the converted analog signal to the RF unit 12.

[0092] The RF unit 12 uses a low-pass filter to remove unnecessary frequency components from the analog signal input from the baseband unit 13, and up-converts the analog signal to a carrier frequency. The RF unit 12 converts the received signal into a digital signal and transmits it via the antenna unit 11. The RF unit 12 may also have a function to control transmission power. The RF unit 12 is also referred to as a transmission power control unit.

[0093] The physical signals (signals) will be explained below.

[0094] The physical signal is a general term for a downlink physical channel, a downlink physical signal, an uplink physical channel, and an uplink physical channel. The physical channel is a general term for a downlink physical channel and an uplink physical channel. The physical signal is a general term for a downlink physical signal and an uplink physical signal.

[0095] The uplink physical channel may correspond to a set of resource elements that convey information generated in a higher layer. The uplink physical channel may be a physical channel used in an uplink component carrier. The uplink physical channel may be transmitted by a terminal device 1. The uplink physical channel may be received by a base station device 3. In a wireless communication system according to one aspect of the present embodiment, at least some or all of the following uplink physical channels may be used. ·PUCCH (Physical Uplink Control CHannel) ·PUSCH (Physical Uplink Shared CHannel) ·PRACH(Physical Random Access CHannel)

[0096] PUCCH is used to transmit uplink control information (UCI). The PUCCH may be used. The PUCCH may be transmitted to deliver (deliver, transmit, convey) uplink control information. The uplink control information may be mapped to the PUCCH. The terminal device 1 may transmit the PUCCH in which the uplink control information is mapped. Base station The device 3 may receive a PUCCH in which the uplink control information is arranged.

[0097] Uplink control information (uplink control information bit, uplink control information sequence, uplink control information type) is used in combination with channel state information (CSI), schedule The packet contains at least part or all of the Scheduling Request (SR) and Hybrid Automatic Repeat request ACKnowledgement (HARQ-ACK) information.

[0098] The channel state information is also referred to as a channel state information bit or a channel state information sequence. The scheduling request is also referred to as a scheduling request bit or a scheduling request sequence. The HARQ-ACK information is also referred to as a HARQ-ACK information bit or a HARQ-ACK information sequence.

[0099] The HARQ-ACK information may include at least a HARQ-ACK corresponding to a transport block (TB). The HARQ-ACK may indicate an acknowledgement (ACK) or a negative acknowledgement (NACK) corresponding to the transport block. The ACK may indicate that the transport block has been decoded successfully. The NACK may indicate that the transport block has not been decoded successfully. The HARQ-ACK information may include a HARQ-ACK codebook including one or more HARQ-ACK bits.

[0100] A transport block is a sequence of information bits delivered from higher layers. Here, the sequence of information bits is also called a bit sequence. Here, the transport block may be transmitted via an Uplink-Shared Channel (UL-SCH) in the transport layer.

[0101] HARQ-ACK for a transport block may be referred to as HARQ-ACK for a PDSCH. In this case, the "HARQ-ACK for PDSCH" is transmitted to the transport included in the PDSCH. Indicates the HARQ-ACK for the block.

[0102] The HARQ-ACK may indicate an ACK or NACK corresponding to one Code Block Group (CBG) included in the transport block.

[0103] A scheduling request is a request to retrieve the UL-SCH for a new transmission. The scheduling request bit may be used at least to request a resource. The scheduling request bit may be used to indicate either a positive SR or a negative SR. When the scheduling request bit indicates a positive SR, this is also referred to as "a positive SR is transmitted." A positive SR indicates that the terminal device 1 is to transmit a UL-SCH A positive SR may indicate that resources of UL-SCH are requested for initial transmission. A positive SR may indicate that a scheduling request is triggered by a higher layer. A positive SR may be transmitted when a scheduling request is indicated by a higher layer. When the scheduling request bit indicates a negative SR, this is also referred to as "a negative SR is transmitted." A negative SR may indicate that no resources of UL-SCH are requested by the terminal device 1 for initial transmission. A negative SR may indicate that no resources of UL-SCH are requested for initial transmission by the terminal device 1. A positive SR may indicate that no scheduling request is triggered by higher layers. A negative SR may be conveyed when no scheduling request is indicated by higher layers.

[0104] The channel state information may include at least some or all of a Channel Quality Indicator (CQI), a Precoder Matrix Indicator (PMI), and a Rank Indicator (RI). The CQI is an indicator related to the quality of a propagation path (e.g., propagation strength) or the quality of a physical channel, and the PMI is an indicator related to a precoder. RI is an index related to the transmission rank (or the number of transmission layers).

[0105] The channel state information is an indicator of the reception state of at least the physical signal (e.g., CSI-RS) used for channel measurement. The value of the channel state information is used for channel measurement. The channel measurement may be determined by the terminal device 1 based on the reception conditions assumed by at least the physical signals used for the channel measurement. The channel measurement may include an interference measurement.

[0106] The PUCCH may correspond to a PUCCH format. The PUCCH may be a set of resource elements used to convey the PUCCH format. The PUCCH may include a PUCCH format. The PUCCH may be transmitted with a certain PUCCH format. The PUCCH format may be interpreted as a format of information. The PUCCH format may also be interpreted as a set of information set in a certain information format.

[0107] The PUSCH carries transport blocks and / or uplink control information. The transport block may be placed on the PUSCH. The transport block delivered by the UL-SCH may be arranged in the PUSCH. The uplink control information may be arranged in the PUSCH. A PUSCH in which one or both of the uplink control information and the PUSCH are arranged may be transmitted. The base station device 3 may receive a PUSCH in which one or both of a transport block and uplink control information are allocated.

[0108] The PRACH may be transmitted to carry a random access preamble. The base station device 1 may transmit the PRACH. The base station device 3 may receive the PRACH. column x u,v (n) is x u,v (n)=x u(mod(n+C v ,L RA )), where x u is a ZC (Zadoff-Chu) sequence. u x u =exp(-jπui(i+1) / L RA ) by j is the imaginary unit. Also, π is the ratio of the circumference of a circle to its circumference. Also, C v corresponds to the cyclic shift of the PRACH sequence. RA corresponds to the length of the PRACH sequence. RA is 839 or 139. Also, i ranges from 0 to L RA -1 and u is the sequence index for the PRACH sequence.

[0109] For each PRACH opportunity, 64 random access preambles are defined. The access preamble is the cyclic shift C of the PRACH sequence. v , and the sequence index u for the PRACH sequence. An index may be assigned to each of the bulls.

[0110] The uplink physical signal may correspond to a set of resource elements. The uplink physical signal does not have to be used to transmit information generated in a higher layer. The uplink physical signal may be used to transmit information generated in a physical layer. The uplink physical signal may be a physical signal used in an uplink component carrier. The terminal device 1 may transmit the uplink physical signal. The base station device 3 may receive the uplink physical signal. In a wireless communication system according to one aspect of the present embodiment, at least some or all of the following uplink physical signals may be used. ·UL DMRS(UpLink Demodulation Reference Signal) ·SRS(Sounding Reference Signal) ·UL PTRS(UpLink Phase Tracking Reference Signal)

[0111] UL DMRS is a general term for DMRS for PUSCH and DMRS for PUCCH.

[0112] The set of antenna ports for DMRS for PUSCH (DMRS related to PUSCH, DMRS included in PUSCH, DMRS corresponding to PUSCH) is given based on the set of antenna ports for the PUSCH. For example, the set of antenna ports of a DMRS for a PUSCH may be the same as the set of antenna ports for the PUSCH.

[0113] The transmission of the PUSCH and the transmission of the DMRS for the PUSCH are indicated by one DCI format. The PUSCH and the DMRS for the PUSCH may be collectively referred to as a PUSCH. Transmitting the PUSCH may be equivalent to transmitting the PUSCH and the DMRS for the PUSCH.

[0114] The propagation path of the PUSCH may be estimated from the DMRS for the PUSCH.

[0115] The set of antenna ports for DMRS for PUCCH (DMRS related to PUCCH, DMRS included in PUCCH, DMRS corresponding to PUCCH) may be the same as the set of antenna ports for PUCCH. stomach.

[0116] The transmission of the PUCCH and the transmission of the DMRS for the PUCCH are indicated by one DCI format. Mapping of PUCCH to resource elements (resource element mapping), and to the resource elements of the DMRS for the PUCCH One or both of the mappings may be provided by one PUCCH format. The PUCCH and the DMRS for the PUCCH may be collectively referred to as the PUCCH. This may involve transmitting a PUCCH and a DMRS for the PUCCH.

[0117] The propagation path of the PUCCH may be estimated from the DMRS for the PUCCH.

[0118] The downlink physical channel may correspond to a set of resource elements that convey information generated in a higher layer. The downlink physical channel may be a physical channel used in a downlink component carrier. The base station device 3 may transmit the downlink physical channel. The terminal device 1 may receive the downlink physical channel. In a wireless communication system according to one aspect of this embodiment, at least some or all of the following downlink physical channels may be used. ·PBCH(Physical Broadcast Channel) ·PDCCH (Physical Downlink Control Channel) ·PDSCH(Physical Downlink Shared Channel)

[0119] The PBCH may be transmitted to convey one or both of a Master Information Block (MIB) and physical layer control information. Here, the physical layer control information is information generated in the physical layer. The MIB is a set of parameters placed on a Broadcast Control Channel (BCCH), which is a logical channel of the MAC layer. The BCCH is a channel of the transport layer. The MIB and / or physical layer control information may be mapped to a certain BCH. The BCH may be mapped to a PBCH. The terminal device 1 may receive a PBCH in which one or both of the MIB and the physical layer control information are mapped. The base station device 3 may transmit a PBCH in which one or both of the MIB and the physical layer control information are mapped. stomach.

[0120] For example, the physical layer control information may be configured with 8 bits. The physical layer control information may include at least some or all of the following 0A to 0D. 0A) Radio frame bit 0B) Half radio frame (half system frame, half frame) bit 0C) SS / PBCH block index bit 0D) Subcarrier offset bit

[0121] The radio frame bits are used to indicate the radio frame in which the PBCH is transmitted (the radio frame including the slot in which the PBCH is transmitted). The radio frame bits include 4 bits. The radio frame bits may be configured by 4 bits of a 10-bit radio frame indicator. For example, the radio frame indicator is assigned from index 0 to index 1023. It may be used at least to identify radio frames up to

[0122] The half radio frame bit is used to indicate whether the PBCH is transmitted in the first five subframes or the last five subframes of a radio frame in which the PBCH is transmitted. Here, a half radio frame may be configured to include five subframes. Alternatively, a half radio frame may be configured to include the first five subframes of ten subframes included in a radio frame. Alternatively, a half radio frame may be configured to include the last five subframes of ten subframes included in a radio frame.

[0123] The SS / PBCH block index bits are used to indicate the SS / PBCH block index. The SS / PBCH block index bits include 3 bits. The SS / PBCH block index bits may be configured with 3 bits of a 6-bit SS / PBCH block index indicator. The SS / PBCH block index indicator may be used at least to identify SS / PBCH blocks from index 0 to index 63. The SS / PBCH blocks may be referred to as SSBs.

[0124] The subcarrier offset bits are used to indicate a subcarrier offset, which may be used to indicate the difference between the first subcarrier to which the PBCH is mapped and the first subcarrier to which the control resource set with index 0 is mapped.

[0125] The PDCCH may be transmitted to convey downlink control information (DCI). The downlink control information may be mapped to the PDCCH. The base station device 3 may receive the PDCCH in which the downlink control information is arranged. A PDCCH in which downlink control information is allocated may be transmitted.

[0126] The downlink control information may be transmitted with a DCI format. The DCI format may be interpreted as a format of the downlink control information. The DCI format may be It may also be interpreted as a set of downlink control information set in a certain downlink control information format.

[0127] DCI format 0_0, DCI format 0_1, DCI format 1_0, and DCI format 1_1 are DCI formats. The downlink DCI format is a general term for DCI format 0_0 and DCI format 0_1. The downlink DCI format is a general term for DCI format 1_0 and DCI format 1_1.

[0128] DCI format 0_0 is used at least for scheduling PUSCHs allocated to a cell. DCI format 0_0 is used for scheduling some of the fields from 1A to 1E or It consists of at least all of the above. 1A) Identifier field for DCI formats 1B) Frequency domain resource assignment field 1C) Time domain resource assignment field 1D) Frequency hopping flag field 1E) MCS field (Modulation and Coding Scheme field)

[0129] The DCI format specific field is a DCI format specific field. In other words, the DCI format specification field may indicate whether the format is an uplink DCI format or a downlink DCI format. The DCI format specification field may be included in each of the downlink DCI formats. Here, the DCI format specification field included in the DCI format 0_0 may indicate 0.

[0130] The frequency domain resource allocation field included in DCI format 0_0 may be used to indicate the allocation of frequency resources for the PUSCH.

[0131] The time domain resource allocation field included in DCI format 0_0 may be used to indicate the allocation of time resources for the PUSCH.

[0132] The frequency hopping flag field indicates whether frequency hopping is applied to the PUSCH. It may be used to indicate whether or not

[0133] The MCS field included in DCI format 0_0 specifies the modulation scheme for PUSCH, and , and the target coding rate for the transport block placed on the PUSCH. The size of the transport block (TBS) allocated to the PUSCH may be determined based on the target coding rate and one or more of the modulation schemes for the PUSCH. may be determined based on both.

[0134] DCI format 0_0 does not include fields used for CSI requests. It's not necessary.

[0135] DCI format 0_0 may not include a carrier indicator field. That is, the serving cell to which the uplink component carrier on which the PUSCH scheduled by DCI format 0_0 is allocated belongs uses the DCI format 0_0. The serving cell is the same as the uplink component carrier on which the PDCCH including the The terminal device 1 may transmit a PUSCH scheduled in accordance with the DCI format 0_0 to an uplink component carrier of a serving cell based on detecting the DCI format 0_0 in a downlink component carrier of the serving cell. It may be recognized that the carrier may be placed.

[0136] DCI format 0_0 may not include the BWP field. The DCI format 0_0 may be a DCI format for scheduling a PUSCH without changing the active uplink BWP. The terminal device 1 may recognize that the PUSCH is to be transmitted without switching the active uplink BWP based on detecting the DCI format 0_0 used for scheduling the PUSCH.

[0137] DCI format 0_1 ​​is used at least for scheduling PUSCHs allocated to a cell. DCI format 0_1 ​​is used for part of fields 2A to 2H or It consists of at least all of the above. 2A) DCI format specific fields 2B) Frequency domain resource allocation field 2C) Uplink time domain resource allocation field 2D) Frequency hopping flag field 2E) MCS Field 2F) CSI request field 2G) BWP field 2H) Carrier indicator field

[0138] The DCI format specific field included in DCI format 0_1 ​​may indicate 0. stomach.

[0139] The frequency domain resource allocation field included in DCI format 0_1 ​​may be used to indicate the allocation of frequency resources for the PUSCH.

[0140] The time domain resource allocation field included in DCI format 0_1 ​​may be used to indicate the allocation of time resources for the PUSCH.

[0141] The MCS field included in DCI format 0_1 ​​specifies the modulation scheme for PUSCH, and and / or may at least be used to indicate some or all of the target code rate.

[0142] The BWP field of DCI format 0_1 ​​is the The DCI format 0_1 ​​may be used to indicate an uplink BWP in which a PUSCH to be scheduled is arranged. That is, the DCI format 0_1 ​​may involve a change of the active uplink BWP. The terminal device 1 may recognize the uplink BWP in which the PUSCH is arranged based on detecting the DCI format 0_1 ​​used for scheduling the PUSCH.

[0143] DCI format 0_1, which does not include the BWP field, is used to change the active uplink BWP. The terminal device 1 may use a DCI format 0_1 ​​used for scheduling the PUSCH and a DCI format that does not include the BWP frame. Based on detecting the DCI format D0_1 that does not include the field, it may be recognized that the PUSCH is to be transmitted without switching the active uplink BWP.

[0144] DCI format 0_1 ​​includes a BWP field, but terminal device 1 does not include the DCI format If the terminal device 1 does not support the BWP switching function by 0_1, the BWP field may be ignored by the terminal device 1. In other words, the terminal device 1 that does not support the BWP switching function , DCI format 0_1 ​​used for PUSCH scheduling and BWP format Based on detecting the DCI format 0_1 ​​including the field, the terminal device 1 may recognize that it will transmit the PUSCH without switching the active uplink BWP. If the terminal device 1 supports the BWP switching function, it may report that "the terminal device 1 supports the BWP switching function" in the RRC layer capability information reporting procedure.

[0145] The CSI request field is used to indicate the reporting of CSI.

[0146] If DCI format 0_1 ​​includes a carrier indicator field, The rear indicator field indicates the uplink component carrier in which the PUSCH is located. DCI format 0_1 ​​may be used to indicate a carrier indicator. If the field is not included, the uplink component carrier on which the PUSCH is allocated is A PDCCH including DCI format 0_1 ​​used for scheduling the PUSCH is arranged. When the number of uplink component carriers configured in the terminal device 1 in a certain serving cell group is two or more (when uplink carrier aggregation is operated in a certain serving cell group), the scheduling of the PUSCH allocated to the certain serving cell group may be the same as the uplink component carrier configured in the certain serving cell group. The carrier indicator field included in DCI format 0_1 ​​used for The number of bits may be 1 or more (for example, 3 bits). When the number of uplink component carriers configured in the terminal device 1 in a certain serving cell group is 1 (when uplink carrier aggregation is not operated in a certain serving cell group), the scheduling of the PUSCH allocated to the certain serving cell group Carrier indicator field included in DCI format 0_1 ​​used for The number of bits in the carrier indicator field may be 0 (or the DCI format 0_1 ​​used for scheduling the PUSCH allocated to the certain serving cell group may not include the carrier indicator field).

[0147] DCI format 1_0 is used at least for scheduling PDSCHs allocated to a certain cell. DCI format 1_0 may use at least some or all of 3A to 3F. It also includes the following: 3A) DCI Format Specific Fields 3B) Frequency domain resource allocation field 3C) Time Domain Resource Allocation Field 3D) MCS field 3E) PDSCH_HARQ feedback timing indicator field 3F) PUCCH resource indicator field

[0148] The DCI format specific field included in DCI format 1_0 may indicate 1.

[0149] The frequency domain resource allocation field included in DCI format 1_0 may be used at least to indicate the allocation of frequency resources for the PDSCH.

[0150] The time domain resource allocation field included in DCI format 1_0 may be used at least to indicate the allocation of time resources for the PDSCH.

[0151] The MCS field included in DCI format 1_0 specifies the modulation scheme for PDSCH, and , and the target coding rate for the transport block placed on the PDSCH. The size of the transport block (TBS) allocated to the PDSCH may be determined by the target coding rate and one or more of the modulation schemes for the PDSCH. may be determined based on both.

[0152] The PDSCH_HARQ feedback timing indication field specifies the offset from the slot containing the last OFDM symbol of the PDSCH to the slot containing the first OFDM symbol of the PUCCH. It may also be used to indicate a

[0153] The PUCCH resource indication field may be a field indicating an index of one or more PUCCH resources included in a PUCCH resource set. A PUCCH resource set may include one or more PUCCH resources.

[0154] DCI format 1_0 may not include a carrier indicator field. That is, the downlink component carrier on which the PDSCH scheduled by DCI format 1_0 is arranged may be the same as the downlink component carrier on which the PDCCH including the DCI format 1_0 is arranged. Based on detecting DCI format 1_0 in a certain downlink component carrier, the terminal device 1 may arrange the PDSCH scheduled by the DCI format 1_0 in the downlink component carrier. It may be recognized that the carrier may be placed.

[0155] DCI format 1_0 may not include the BWP field. The packet 1_0 may be a DCI format for scheduling the PDSCH without changing the active downlink BWP. Based on detecting DCI format 1_0, it may be recognized that the PDSCH will be received without switching the active downlink BWP.

[0156] DCI format 1_1 is used at least for scheduling PDSCHs allocated to a certain cell. DCI format 1_1 includes at least some or all of 4A to 4I. It also includes the following: 4A) DCI Format Specific Fields 4B) Frequency domain resource allocation field 4C) Time Domain Resource Allocation Field 4E) MCS Field 4F) PDSCH_HARQ feedback timing indication field 4G) PUCCH resource indication field 4H) BWP Field 4I) Career Indicator Field

[0157] The DCI format specific field included in DCI format 1_1 may indicate 1.

[0158] The frequency domain resource allocation field included in DCI format 1_1 may be used at least to indicate the allocation of frequency resources for the PDSCH.

[0159] The time domain resource allocation field included in DCI format 1_1 may be used at least to indicate the allocation of time resources for the PDSCH.

[0160] The MCS field included in DCI format 1_1 specifies the modulation scheme for PDSCH, and , may be used to indicate at least one or both of the target coding rates.

[0161] When DCI format 1_1 includes a PDSCH_HARQ feedback timing indication field, the PDSCH_HARQ feedback timing indication field shall be set from the slot containing the last OFDM symbol of the PDSCH to the slot containing the first OFDM symbol of the PUCCH. If DCI format 1_1 does not include a PDSCH_HARQ feedback timing indication field, the offset from the slot containing the last OFDM symbol of the PDSCH to the slot containing the first OFDM symbol of the PUCCH may be specified by a parameter of a higher layer.

[0162] The PUCCH resource indication field may be a field indicating an index of one or more PUCCH resources included in a PUCCH resource set.

[0163] The BWP field of DCI format 1_1 is the The DCI format 1_1 may be used to indicate the downlink BWP in which the PUSCH to be scheduled is arranged. That is, the DCI format 1_1 may involve a change of the active downlink BWP. The terminal device 1 may recognize the downlink BWP in which the PUSCH is arranged based on detecting the DCI format 1_1 used for scheduling the PDSCH.

[0164] DCI format 1_1, which does not include the BWP field, is used to change the active downlink BWP. The terminal device 1 may use a DCI format 1_1 that is used for scheduling the PDSCH and that is not accompanied by a BWP frame. The active downstream link is determined based on detecting DCI format 1_1 that does not include the It may be possible to recognize that the PDSCH is received without switching the link BWP.

[0165] DCI format 1_1 includes a BWP field, but terminal device 1 does not If the terminal device 1 does not support the BWP switching function by 1_1, the BWP field may be ignored by the terminal device 1. In other words, the terminal device 1 that does not support the BWP switching function , DCI format 1_1 used for PDSCH scheduling and BWP format Based on detecting the DCI format 1_1 including the field, the terminal device 1 may recognize that it will receive the PDSCH without switching the active downlink BWP. If the terminal device 1 supports the BWP switching function, it may report that "the terminal device 1 supports the BWP switching function" in the RRC layer capability information reporting procedure.

[0166] If DCI format 1_1 includes a carrier indicator field, The rear indicator field indicates the downlink component carrier on which the PDSCH is located. DCI Format 1_1 may be used to indicate a carrier indicator. If the field is not included, the downlink component carrier on which the PDSCH is allocated is A PDCCH including DCI format 1_1 used for scheduling the PDSCH is arranged. When the number of downlink component carriers configured in the terminal device 1 in a certain serving cell group is two or more (when downlink carrier aggregation is operated in a certain serving cell group), the scheduling of the PDSCH allocated to the certain serving cell group may be the same as the downlink component carrier configured in the certain serving cell group. The carrier indicator field included in DCI format 1_1 used for The number of bits may be 1 or more (for example, 3 bits). When the number of downlink component carriers configured in the terminal device 1 in a certain serving cell group is 1 (when downlink carrier aggregation is not operated in a certain serving cell group), the scheduling of the PDSCH arranged in the certain serving cell group Carrier indicator field included in DCI format 1_1 used for The number of bits in may be 0 (or the carrier indicator field may not be included in DCI format 1_1 used for scheduling the PDSCH allocated to the certain serving cell group).

[0167] The PDSCH may be transmitted to transmit a transport block. The PDSCH may be used to transmit a transport block delivered by the DL-SCH. The PDSCH may be used to transmit a transport block. The transport block may be placed on the PDSCH. The transport block corresponding to the DL-SCH is placed on the PDSCH. The base station device 3 may transmit the PDSCH, and the terminal device 1 may receive the PDSCH.

[0168] The downlink physical signal may correspond to a set of resource elements. The downlink physical signal may not carry information generated in a higher layer. The downlink physical signal may be a physical signal used in a downlink component carrier. The downlink physical signal may be transmitted by a base station device 3. The downlink physical signal may be transmitted by a terminal device 1. In a wireless communication system according to one aspect of this embodiment, at least some or all of the following downlink physical signals may be used. ·Synchronization signal (SS) ·DL DMRS(DownLink DeModulation Reference Signal) ·CSI-RS(Channel State Information-Reference Signal) ·DL PTRS(DownLink Phase Tracking Reference Signal)

[0169] The synchronization signal may be used by the terminal device 1 to synchronize one or both of the frequency domain and the time domain of the downlink. The synchronization signal is a general term for a PSS (Primary Synchronization Signal) and an SSS (Secondary Synchronization Signal).

[0170] FIG. 7 is a diagram showing an example of the configuration of an SS / PBCH block according to one aspect of this embodiment. In FIG. 7, the horizontal axis is the time axis (OFDM symbol index l sym ), where the vertical axis represents the frequency domain. Block 700 represents a set of resource elements for the PSS. Block 720 shows the set of resource elements for SSS. Blocks 710, 711, 712, and 713 indicate a set of resource elements for the PBCH and DMRS for the PBCH (DMRS associated with the PBCH, DMRS included in the PBCH, and DMRS corresponding to the PBCH).

[0171] As shown in Figure 7, the SS / PBCH block includes a PSS, SSS, and PBCH. The SS / PBCH block includes four consecutive OFDM symbols. The SS / PBCH block includes 240 subcarriers. The PSS is the 57th to 183rd subcarriers in the first OFDM symbol. The SSS is located in the 57th to 183rd subcarriers in the third OFDM symbol. The PBCH is allocated to the 1st subcarrier of the first OFDM symbol. Zeros may be set to the 1st to 56th subcarriers of the first OFDM symbol. Zeros may be set to the 184th to 240th subcarriers of the first OFDM symbol. Zeros may be set to the 49th to 56th subcarriers of the third OFDM symbol. Zeros may be set to the 184th to 192nd subcarriers of the third OFDM symbol. The PBCH is allocated to the 1st to 240th subcarriers of the second OFDM symbol, which are subcarriers where DMRS for the PBCH is not allocated. The PBCH is allocated to the 1st to 48th subcarriers of the third OFDM symbol, which are subcarriers where DMRS for the PBCH is not allocated. The PBCH is allocated to the 193rd to 240th subcarriers of the third OFDM symbol, which are subcarriers where DMRS for the PBCH is not allocated. The PBCH is allocated to the 1st to 240th subcarriers of the fourth OFDM symbol, which are subcarriers to which the DMRS for the PBCH is not allocated.

[0172] The antenna ports for the PSS, SSS, PBCH, and DMRS for the PBCH may be the same.

[0173] The PBCH on which the PBCH symbol is transmitted at a certain antenna port may be estimated by the DMRS for the PBCH that is placed in the slot to which the PBCH is mapped and is included in the SS / PBCH block to which the PBCH belongs.

[0174] DL DMRS is a general term for DMRS for PBCH, DMRS for PDSCH, and DMRS for PDCCH.

[0175] The set of antenna ports for DMRS for PDSCH (DMRS related to PDSCH, DMRS included in PDSCH, DMRS corresponding to PDSCH) is given based on the set of antenna ports for the PDSCH. That is, the set of antenna ports of the DMRS for the PDSCH may be the same as the set of antenna ports for the PDSCH.

[0176] The transmission of the PDSCH and the transmission of the DMRS for the PDSCH are indicated by one DCI format. The PDSCH and the DMRS for the PDSCH may be collectively referred to as the PDSCH. Transmitting the PDSCH may be equivalent to transmitting the PDSCH and the DMRS for the PDSCH.

[0177] The propagation path of a PDSCH may be estimated from the DMRS for that PDSCH. A set of resource elements on which a DMRS symbol is transmitted and the DMRS symbol for the PDSCH are transmitted. If the set of resource elements on which the PDS signal is transmitted is included in the same precoding resource group (PRG), the PDS signal is transmitted to an antenna port. The PDSCH on which the symbols of the CH are transmitted may be estimated by the DMRS for that PDSCH.

[0178] The antenna port of the DMRS for the PDCCH (DMRS related to the PDCCH, DMRS included in the PDCCH, DMRS corresponding to the PDCCH) may be the same as the antenna port for the PDCCH.

[0179] The PDCCH may be estimated from the DMRS for the PDCCH, i.e., the propagation path of the PDCCH may be estimated from the DMRS for the PDCCH. a set of resource elements and a resource on which the DMRS symbols for the PDCCH are transmitted; If the same precoder is applied (or is assumed to be applied) to a set of elements, the symbols of the PDCCH on a certain antenna port are transmitted. The PDCCH to be used may be estimated by the DMRS for the PDCCH.

[0180] BCH (Broadcast CHannel), UL-SCH (Uplink-Shared CHannel), and DL-SCH (Downlink-Shared CHannel) are transport channels. Transport channels define the relationship between physical layer channels and MAC layer channels (also called logical channels). do.

[0181] The BCH of the transport layer is mapped to the PBCH of the physical layer. The transport blocks that pass through the BCH are delivered to the PBCH of the physical layer. The UL-SCH of the transport layer is mapped to the PUSCH of the physical layer. That is, the transport block carried by the UL-SCH of the transport layer is delivered to the PUSCH of the physical layer. The DL-SCH of the transport layer is mapped to the PDSCH of the physical layer. The transport blocks that pass through are delivered to the PDSCH of the physical layer.

[0182] One UL-SCH and one DL-SCH may be provided for each serving cell. The BCH may be provided for the PCell. The BCH does not necessarily have to be provided for the PSCell or SCell.

[0183] In the MAC layer, HARQ (Hybrid Automatic Repeat reQuest) control is performed for each transport block.

[0184] BCCH (Broadcast Control CHannel), CCCH (Common Control CHannel), and DCCH (Dedicated Control CHannel) are logical channels. For example, BCCH is a MIB, Or, it is a channel of the RRC layer used to transmit system information. (Common Control CHannel) transmits common RRC messages to multiple terminal devices 1. Here, the CCCH may be used for, for example, a terminal device that is not RRC connected. 1. In addition, the DCCH (Dedicated Control CHannel) may be used for the terminal device. 1, where DCCH may be used to transmit RRC messages dedicated to may be used, for example, for a terminal device 1 that is in an RRC connection.

[0185] For example, system information (SI) may be composed of MIB and several SIBs (System Information blocks). Also, system information may be divided into Minimum SI and Other SI. Minimum SI may include basic information required for initial access. Furthermore, Minimum SI may include information for acquiring Other SI. Minimum SI may be composed of MIB and SIB1. Other SI is notified by Minimum SI. This may include all SIBs that are not broadcast or transmitted in the DL-SCH.

[0186] SIB1 may define the scheduling of Other SI. SIB1 may contain information required for initial access. SIB1 may be referred to as RMSI (Remaining Minimum SI). SIB1 may be periodically left on DL-SCH. SIB1 is used in the RRC_CONNECTED state. The UEs may be sent in a dedicated manner on the DL-SCH to some UEs in the DL-SCH.

[0187] Upper layer parameters that are common to multiple terminal devices 1 are also referred to as common upper layer parameters. Here, the common upper layer parameters may be defined as parameters specific to a serving cell. Here, parameters specific to a serving cell are parameters that are common to terminal devices (e.g., terminal devices 1-A, B, C) in which the serving cell is set. It may also be a

[0188] For example, the common upper layer parameters may be included in the RRC messages delivered on the BCCH. For example, common upper layer parameters may be included in RRC messages delivered on the DCCH. .

[0189] Among certain upper layer parameters, upper layer parameters different from common upper layer parameters are also referred to as dedicated upper layer parameters. Here, the dedicated upper layer parameters can provide dedicated RRC parameters to the terminal device 1-A in which the serving cell is configured. In other words, the dedicated RRC parameters are upper layer parameters that can provide unique settings for each of the terminal devices 1-A, 1-B, and 1-C.

[0190] The BCCH of the logical channel is mapped to the BCH of the transport layer or the DL-SCH. For example, a transport block containing MIB information is delivered to the BCH of the transport layer. Also, a transport block containing non-MIB system information is delivered to the transport layer. The CCCH is delivered to the DL-SCH of the transport layer. The CCCH is also mapped to the DL-SCH or UL-SCH. Therefore, a transport block mapped to a CCCH is delivered to either the DL-SCH or the UL-SCH, and a DCCH is mapped to either the DL-SCH or the UL-SCH, i.e., a transport block mapped to a DCCH is delivered to either the DL-SCH or the UL-SCH.

[0191] The RRC message includes one or more parameters managed in the RRC layer. Here, the parameters managed in the RRC layer are also referred to as RRC parameters. For example, The message may include an MIB. The RRC message may also include system information. The RRC message may also include a message corresponding to a CCCH. The RRC message may also include a message corresponding to a DCCH. An RRC message including a message corresponding to a DCCH is also referred to as a dedicated RRC message.

[0192] The upper layer parameters are RRC parameters or parameters included in the MAC CE (Medium Access Control Element). The parameters are MIB, system information, messages corresponding to CCCH, and messages corresponding to DCCH. The parameters included in MAC CE are transmitted by a MAC CE (Control Element) command.

[0193] The procedure performed by the terminal device 1 includes at least some or all of the following steps 5A to 5C. 5A) Cell Search 5B) Random Access 5C) Data communication

[0194] The cell search is a procedure used by the terminal device 1 to synchronize with a certain cell in the time domain and the frequency domain and detect a physical cell identity. That is, the terminal device 1 may perform the cell search to synchronize with a certain cell in the time domain and the frequency domain and detect a physical cell ID.

[0195] The PSS sequence is based at least on the physical cell ID. The SSS sequence is based on the physical cell ID. At least based on.

[0196] The SS / PBCH block candidates indicate resources on which transmission of the SS / PBCH block is permitted (possibly, reserved, configured, defined, possible).

[0197] The set of SS / PBCH block candidates in a half radio frame is also called the SS burst set. The SS burst set is a set of candidates for the transmission window. It is also called the SS transmission window, the DRS transmission window, or the Discovery Reference Signal transmission window. The SS burst set is a general term that includes at least the first SS burst set and the second SS burst set.

[0198] The base station device 3 transmits SS / PBCH blocks of one or more indexes at a predetermined period. The terminal device 1 may detect at least one of the SS / PBCH blocks of the one or more indexes and attempt to decode the PBCH included in the SS / PBCH block.

[0199] Random access is a procedure that includes at least some or all of message 1, message 2, message 3, and message 4.

[0200] Message 1 is a procedure for transmitting a PRACH by the terminal device 1. The terminal device 1 A PRACH is transmitted in one PRACH opportunity selected from one or more PRACH opportunities based at least on an index of a SS / PBCH block candidate detected based on a cell search. Each PRACH opportunity is defined based on at least time and frequency domain resources. can be.

[0201] The terminal device 1 transmits one random access preamble selected from the PRACH opportunities corresponding to the index of the SS / PBCH block candidate in which the SS / PBCH block is detected. .

[0202] Message 2 is a DCI frame with a CRC (Cyclic Redundancy Check) scrambled by the terminal device 1 with an RA-RNTI (Random Access - Radio Network Temporary Identifier). The terminal device 1 detects a control resource set provided based on the MIB included in the PBCH included in the SS / PBCH block detected based on the cell search. The DCI format is used in the resource indicated based on the search area set setting. Message 2 is also called a random access response. It is called.

[0203] Message 3 is contained in DCI format 1_0 detected by the Message 2 procedure. The PUSCH is transmitted by the random access response grant. Here, the random access response grant grant) is indicated by the MAC CE included in the PDSCH scheduled by the DCI format 1_0.

[0204] The PUSCH scheduled based on the random access response grant is Message 3 PUSCH contains a contention resolution identifier MAC CE. The contention resolution identifier MAC CE is used to identify the contention. Contains the conflict resolution ID.

[0205] Message 3 PUSCH retransmission is performed using TC-RNTI (Temporary Cell - Radio Network Temporary Time Increment). Scheduled by DCI format 0_0 with scrambled CRC based on the 0_0_1_0_2_0_3_0_4_0_5_0_6_1_0_7_0_8_1_1_0_9_10_11_12_13_14_15_16_17_18_19_20_21_22_23_24_25_26_27_28_29_3

[0206] Message 4 is a procedure for attempting to detect DCI format 1_0 with a CRC scrambled based on either a C-RNTI (Cell-Radio Network Temporary Identifier) ​​or a TC-RNTI. The terminal device 1 performs scheduling based on the DCI format 1_0. The PDSCH may include a collision resolution ID.

[0207] Data communication is a general term for downlink communication and uplink communication.

[0208] In data communication, the terminal device 1 attempts to detect the PDCCH in the resources specified based on the control resource set and the search space set (monitors the PDCCH, detects the PDCCH, etc.). monitor).

[0209] A control resource set is a set of resources consisting of a predetermined number of resource blocks and a predetermined number of OFDM symbols. In the frequency domain, a control resource set may consist of contiguous resources (non-interleaved mapping) or distributed resources. (interleaver mapping).

[0210] A set of resource blocks constituting the control resource set may be indicated by a higher layer parameter, and the number of OFDM symbols constituting the control resource set may be indicated by a higher layer parameter.

[0211] The terminal device 1 attempts to detect the PDCCH in the search space set. Attempting to detect a PDCCH in the search space set may be attempting to detect a PDCCH candidate in the search space set, or attempting to detect a DCI format in the search space set. Alternatively, the PDCCH may be detected in the control resource set. Alternatively, the PDCCH may be detected in the control resource set. , it may be to attempt to detect the DCI format in the control resource set.

[0212] The search space set is defined as a set of PDCCH candidates. The search space set may be a Common Search Space (CSS) set or a UE-specific Search Space (USS) set. The terminal device 1 may select a part or a part of a Type 0 PDCCH common search space set (Type 0 PDCCH common search space set), a Type 0a PDCCH common search space set (Type 0a PDCCH common search space set), a Type 1 PDCCH common search space set (Type 1 PDCCH common search space set), a Type 2 PDCCH common search space set (Type 2 PDCCH common search space set), a Type 3 PDCCH common search space set (Type 3 PDCCH common search space set), and / or a UE-specific search space set (UE-specific search space set). Attempts to detect PDCCH candidates in all cases.

[0213] The Type 0 PDCCH common search space set is used as the common search space set with index 0. The Type 0 PDCCH common search space set may include the common search space with index 0. It may be a set.

[0214] The CSS set is a collective term for the Type 0 PDCCH common search space set, Type 0a PDCCH common search space set, Type 1 PDCCH common search space set, Type 2 PDCCH common search space set, and Type 3 PDCCH common search space set. The USS set is a UE-specific PDCCH search space set. It is also called.

[0215] A set of search areas is related to (contains, corresponds to) a set of controlled resources. The index of the control resource set associated with the search space set may be indicated by a higher layer parameter.

[0216] For a given search area set, some or all of 6A to 6C may be indicated by at least higher layer parameters. 6A) PDCCH monitoring periodicity 6B) PDCCH monitoring pattern within a slot 6C) PDCCH monitoring offset

[0217] A monitoring occasion for a certain set of search areas is defined as The monitoring opportunity for a search space set may correspond to an OFDM symbol in which the first OFDM symbol of the associated control resource set is located. The monitoring opportunity for a search space set may correspond to resources of a control resource set associated with the search space set starting from the first OFDM symbol of the control resource set. The monitoring opportunity for the search space set is based on at least some or all of the PDCCH monitoring interval, the PDCCH monitoring pattern within the slot, and the PDCCH monitoring offset.

[0218] 8 is a diagram illustrating an example of a monitoring opportunity for a search area set according to one aspect of the present embodiment. In FIG. 8, search area set 91 and search area set 92 are set in primary cell 301, search area set 93 is set in secondary cell 302, and search area set 94 is set in secondary cell 303.

[0219] In Figure 8, the solid white blocks in primary cell 301 indicate search area set 91, the solid black blocks in primary cell 301 indicate search area set 92, the blocks in secondary cell 302 indicate search area set 93, and the blocks in secondary cell 303 indicate search area set 94.

[0220] The monitoring interval of the search area set 91 is set to 1 slot, and the monitoring interval of the search area set 91 is set to 1 slot. The offset is set to 0 slots, and the monitoring pattern of the search area set 91 is [1,0 ,0,0,0,0,0,1,0,0,0,0,0,0]. The monitoring opportunities for search area set 91 correspond to the first OFDM symbol (OFDM symbol #0) and the eighth OFDM symbol (OFDM symbol #7) in each slot.

[0221] The monitoring interval of the search area set 92 is set to 2 slots, the monitoring offset of the search area set 92 is set to 0 slots, and the monitoring pattern of the search area set 92 is [1,0 ,0,0,0,0,0,0,0,0,0,0,0,0,0]. The monitoring opportunity for search area set 92 corresponds to the first OFDM symbol (OFDM symbol #0) in each of the even slots.

[0222] The monitoring interval of the search area set 93 is set to 2 slots, the monitoring offset of the search area set 93 is set to 0 slots, and the monitoring pattern of the search area set 93 is [0,0 ,0,0,0,0,0,1,0,0,0,0,0,0]. The monitoring opportunity for search area set 93 corresponds to the eighth OFDM symbol (OFDM symbol #7) in each of the even slots.

[0223] The monitoring interval of the search area set 94 is set to 2 slots, the monitoring offset of the search area set 94 is set to 1 slot, and the monitoring pattern of the search area set 94 is set to [1,0 ,0,0,0,0,0,0,0,0,0,0,0,0,0]. The monitoring opportunity for search area set 94 corresponds to the first OFDM symbol (OFDM symbol #0) in each odd slot.

[0224] The Type 0 PDCCH common search space set may be used at least for DCI formats with a Cyclic Redundancy Check (CRC) sequence scrambled by a System Information-Radio Network Temporary Identifier (SI-RNTI).

[0225] The Type 0a PDCCH common search space set is the SI-RNTI (System Information-Radio Network Time Interference (SNTI)). CRC (Cyclic Redundancy Check) scrambled by a Temporary Identifier It may be used at least for DCI formats involving sequences.

[0226] The Type 1 PDCCH common search space set may be used at least for DCI formats with a CRC sequence scrambled by a Random Access-Radio Network Temporary Identifier (RA-RNTI) and / or a CRC sequence scrambled by a Temporary Cell-Radio Network Temporary Identifier (TC-RNTI).

[0227] A Type 2 PDCCH common search space set may be used for a DCI format with a CRC sequence scrambled by a Paging-Radio Network Temporary Identifier (P-RNTI).

[0228] The Type 3 PDCCH common search space set is used for DCI formats with CRC sequences scrambled by the Cell-Radio Network Temporary Identifier (C-RNTI). Good too.

[0229] The UE dedicated PDCCH search space set may be used at least for DCI formats with CRC sequences scrambled by the C-RNTI.

[0230] In downlink communication, the terminal device 1 detects the downlink DCI format. The detected downlink DCI format is used at least for resource allocation of the PDSCH. The detected downlink DCI format is also called a downlink assignment. The terminal device 1 attempts to receive the PDSCH. Based on the PUCCH resource indicated based on the PUCCH DCI format, the HARQ-ACK corresponding to the PDSCH (HARQ-ACK corresponding to the transport block included in the PDSCH) is reported to the base station device 3.

[0231] In uplink communication, the terminal device 1 detects the uplink DCI format. The detected DCI format is used at least for PUSCH resource allocation. The detected uplink DCI format is also called an uplink grant. The terminal device 1 transmits the PUSCH.

[0232] In the configured grant, PUSCH is scheduled. An uplink grant for scheduling is configured for each transmission period of the PUSCH. When the PUSCH is scheduled by the uplink DCI format, some or all of the information indicated by the uplink DCI format may be indicated by the uplink grant configured in the case of configured scheduling.

[0233] The UL slot may be a slot consisting of UL symbols. The special slot may be a slot consisting of UL symbols, flexible symbols, and DL symbols. The DL slot may be a slot consisting of DL symbols.

[0234] The UL symbol may be an OFDM symbol configured or designated for uplink in time division duplex. The UL symbol may be an OFDM symbol configured or designated for PUSCH, PUCCH, PRACH, or SRS. The UL symbol may be an OFDM symbol configured or designated for uplink in time division duplex. The UL symbols may be provided by the layer parameter tdd-UL-DL-ConfigurationCommon. The UL symbols may be provided by the higher layer parameter tdd-UL-DL-ConfigurationDedicated. The UL slots may be provided by the higher layer parameter tdd-UL-DL-ConfigurationCommon. The UL slots may be provided by the higher layer parameter tdd-UL-DL-ConfigurationDedicated. It may be provided accordingly.

[0235] The DL symbol may be an OFDM symbol configured or indicated for downlink in time division duplex. The DL symbol may be an OFDM symbol configured or indicated for PDSCH or PDCCH. ... -DL-ConfigurationCommon. The DL symbols may be provided by the higher layer parameters The DL slot may be provided by the data tdd-UL-DL-ConfigurationDedicated. DL slots may be provided by the higher layer parameter tdd-UL-DL-ConfigurationCommon. DL slots may be provided by the higher layer parameter tdd-UL-DL-ConfigurationDedicated. good.

[0236] The flexible symbols may be OFDM symbols within a certain period that are not configured or indicated as UL symbols or DL ​​symbols. The certain period may be a period given by the upper layer parameter dl-UL-TransmissionPeriodicity. The flexible symbols may be used for PDSCH, PDCCH, PUSCH, PUCCH, or PRACH. It may be an OFDM symbol set or indicated.

[0237] The upper layer parameter tdd-UL-DL-ConfigurationCommon may be a parameter that sets one or more slots as either a UL slot, a DL slot, or a special slot. The upper layer parameter tdd-UL-DL-ConfigurationDedicated may be a parameter that sets one or more slots as either a UL slot, a DL slot, or a special slot. tdd-UL-DL-ConfigurationCommon may be a common upper layer parameter. tdd-UL-DL-ConfigurationDedicated may be a dedicated upper layer parameter.

[0238] Multiple TRPs (Transmission Reception Points or Transmit / Receive Points) are used. The base station device 3 may be configured with multiple TRPs (Multi-TRP). The terminal device 1 may be scheduled by two TRPs in one serving cell. In Multi-TRP, one of the operation modes of single-DCI and multi-DCI may be used. In Multi-TRP, uplink control may be completed in the MAC layer and the physical layer. In Multi-TRP, MAC Downlink control may be completed at the layer and the physical layer. In single-DCI mode, the terminal device 1 may be scheduled by the same DCI for two TRPs. In multi-DCI mode, the terminal device 1 may be scheduled by independent DCI from each TRP. Each TRP in multi-TRP may be identified by TRP information. That is, one TRP in multi-TRP may be identified by one piece of TRP information. The TRP information may be used to select one TRP.

[0239] The value of the TA offset (Timing advance offset) may be provided by a higher layer parameter. The timing advance (TA) may be determined based at least on the TA offset. One TA offset may be provided in one serving cell. Two TA offsets may be provided in one serving cell. If higher layer parameters are not provided, the terminal device 1 may determine the value of the TA offset. The terminal device 1 may determine two TA offset values ​​in one serving cell. The TA offset value is N. TA,offset The higher layer parameters are n-TimingAdvanceOffset Determining the TA may result in adjusting the uplink timing.

[0240] When two uplink carriers are configured in one serving cell, one TA The TA offset value may be applied to two uplink carriers. When two TRPs (Transmission Reception Points) are configured in one serving cell, one TA offset is used. The value may be applied to two TRPs. If two TRPs are configured in one serving cell, If so, two TA offset values ​​may be applied to the two TRPs.

[0241] The terminal device 1 may adjust the uplink timing. For example, the terminal device 1 may adjust the uplink timing in response to receiving a TA command (Timing advance command). For example, in response to receiving one TA command (Timing advance command) for one TAG (Timing advance group), the terminal device 1 may adjust the uplink timing for PUSCH / SRS / PUCCH transmission in all serving cells in one TAG. For example, in response to receiving one TA command for one TAG, the terminal device 1 adjusts the uplink timing for PUSCH / SRS / PUCCH transmission in one or more serving cells belonging to one TAG. For example, the terminal device 1 may TA,offet The uplink timing may be adjusted based on the value of N TA,offset may be the same for all serving cells in one TAG. TA,offset may not be the same for all serving cells in one TAG. TA,offset The value of and one or both of the TA commands The uplink timing may be adjusted based on the It may be the same for all serving cells in the TAG. The timing may not be the same for all serving cells in one TAG. For example, the first uplink timing may be the same for a first subset of serving cells in one TAG. For example, the second uplink timing may be the same as the serving timing in one TAG. The same may be true for the second part of the serving cells in one TAG. All serving cells in one TAG may be divided into a first part and a second part.

[0242] In response to receiving one TA command (Timing advance command) for one subTAG, the terminal device 1 may adjust the uplink timing for PUSCH / SRS / PUCCH transmission corresponding to one subTAG (or subTAG ID). For example, in response to receiving one TA command for one subTAG, the terminal device 1 may adjust the uplink timing for one or more serving cells, or may adjust the uplink timing for PUSCH / SRS / PUCCH transmission in the TRP. TA,offset may be the same for all serving cells in one subTAG The uplink timing is the same for all serving cells in one subTAG. Two subTAGs may be used in one serving cell.

[0243] The terminal device 1 may determine the uplink timing based on at least some or all of the TA command, the TA offset, and the TRP information. For example, the TRP (Transmission Reception Point) information may identify one TRP among one or more TRPs. For example, the TRP information may be an index for identifying one TRP. For example, one TRP may be determined based on the TRP information. For example, the TRP information may be information for identifying one or more TRPs. The TRP information may be provided by higher layer parameters. The TRP information may be provided in a random access response (RAN). The TRP information may be included in the DCI format. The TRP information may be a CORESET pool index. The TRP information may be associated with an index of a CORESET resource pool. For example, a first CORESET pool index may be associated with a first TRP, and a second CORESET pool index may be associated with a second TRP. TRP The information may be associated with a pool (or pool index) of TCI states. The first TCI state or states are associated with the first TCI state pool index. The second one or more TCI states may be pooled in the second TCI state. The TRP information may be a TAG ID (subTAG ID). For example, a first TAG ID (subTAG ID) may be associated with a first TRP, and a second TAG ID (subTAG ID) may be associated with a second TRP.

[0244] Based on the timing adjustment indication for one TAG from the MCG The first uplink timing may be determined based on the timing adjustment instruction for one TAG from the SCG. The second uplink timing may be determined based on the timing adjustment instruction for one TAG from the MCG. Based on the timing adjustment instructions for the two TAGs, the first uplink timing and the second uplink timing may be determined.

[0245] The TA command may be changed based on the subcarrier spacing. For example, in the subcarrier spacing setting μ, one TA command for one TAG is changed depending on the uplink timing. For example, the uplink timing may be 16*64*T c / 2 μ "*" may be a multiplication operator.

[0246] The TA (Timing advance) of the random access preamble may be zero.

[0247] A TA command may be included in a random access response. For example, a single TAG (or A TA command for a TAG (or subTAG) is a random action associated with one TAG (or subTAG). For example, a TA command related to one TRP information may be included in one The TRP information included in the random access response in the random access procedure related to The TA command may be sent as a MAC CE command. For example, the TA command may be an Absolute timing advance command MAC CE. The TA command T in the case of a random access response or an Absolute timing advance command MAC CE A For one TAG, N TA You may also specify a value for T. A is an integer between 0 and 3846 It can also be a number, for example, N TA is T A *16*64 / 2 μ N TA may be related to the subcarrier spacing of a certain uplink transmission. For example, the certain uplink transmission may be an uplink transmission from the terminal device 1. For example, the certain uplink transmission may be a random access For example, an uplink transmission may be the first uplink transmission after receiving an absolute timing advance command MAC CE. A may be an index value. The uplink transmission may be an uplink channel transmission.

[0248] TA Command TA For one TAG, the current N TA You can also specify the value adjustment. For example, the TA command T A is N TA,old From N TA,new N TA,new is N TA,old +(T A -31)*16*64 / 2 μ For example, T A may be an integer between 0 and 63.

[0249] If the terminal equipment has one or more active uplink BWPs, the TA command (TA command The code value) may also be related to the maximum subcarrier spacing of one or more active uplink BWPs. The TA command may be a TA command in one TAG including uplink BWPs in two uplink carriers of one serving cell. For example, N for one uplink BWP with interval TA,new may be rounded to fit the timing advance granularity for one uplink BWP with initial subcarrier spacing. Rounding a value may involve rounding off a value. For example, N TA,new is a circle It may be possible to do so.

[0250] N by positive value TA The adjustment of the uplink transmission for one TAG (Timing advance group) It may also indicate advancing of timing (uplink timing). TA The adjustment may also indicate a delay in uplink transmission timing for one TAG. good.

[0251] If a TA command is received in the first slot n, an uplink transmission timing adjustment may be applied starting from the beginning of the second slot. The first slot n may be an uplink slot. The uplink slot is a slot in an uplink frame. The second slot may be the slot corresponding to n+k+1+2. μ *K offset Even if That is, the second slot is the first slot n to k+1+2. μ *K offset It may be a slot after a slot. offset may be provided by higher layer parameters. k is the sum of ceil(N subframe,μ slot ·(N T,1 +N T,2 +N TA,max +0.5) / T sf ) may be used. T,1 Units of N may be in milliseconds. T,1 is the duration of N1 symbols in milliseconds N1 symbols may correspond to a PDSCH processing time. T,2 may be a duration in milliseconds of N2 symbols, which may correspond to a PUSCH preparation time. TA,max N may be the maximum timing advance value (TA) in milliseconds. TA,max N may be the maximum TA value that can be provided by the 12-bit TA command field. subframe,μ slot may be the number of slots in one subframe. sf T may be 1 millisecond. sf teeth , may be the duration of a subframe. offset is K cell,offset -KUE,offset It may be. K cell,offset may be provided by a higher layer parameter. UE,offset is one It may be provided by the MAC CE command of K cell,offset may be 0. UE,offset may be 0. One or both of N1 and N2 may be determined relative to a minimum subcarrier spacing (SCS). The minimum subcarrier spacing is set It may be the smallest subcarrier spacing among all the subcarrier spacings of all the downlink BWPs and all the configured uplink BWPs. When μ=0, N1 may be 14. Slot n and N subframe,μ slot may be determined relative to the minimum subcarrier spacing. TA,max may be determined relative to the minimum subcarrier spacing. Slot n may be the last slot of one or more slots that overlap with the slots for PDSCH reception. For PDSCH reception, T TA = 0. One TA command is received on the PDSCH. A PDSCH containing one TA command may be received. The PDSCH may provide one TA command.

[0252] When the terminal device 1 changes the active uplink BWP, the terminal device 1 may determine a TA command (TA command value) based on the subcarrier spacing of the changed active uplink BWP. For example, when the terminal device 1 changes the active uplink BWP between the time when the TA command is received and the time when the adjustment for the uplink transmission timing is applied, the terminal device 1 may determine a new The TA command may be determined based on the subcarrier spacing of the active uplink BWP. After applying the adjustment for uplink transmission timing, the active uplink BWP changes. When the active uplink BWP is changed, the terminal device 1 may assume the same absolute timing advance command value (absolute timing advance command MAC CE). The first absolute timing advance command value before the change may be the same as the second absolute timing advance command value after the active uplink BWP change.

[0253] When the downlink timing is changed and the downlink timing is not corrected, the terminal device 1 TA When the downlink timing is changed and the downlink timing is partially corrected by the uplink timing adjustment without the TA command, the terminal device 1 may change N TA The uplink timing adjustment may be that the uplink timing is determined or changed.

[0254] If one TA command overlaps two adjacent slots, the latter slot may be reduced.

[0255] A TAG (Timing advance group) may be a group of one or more serving cells. One or more serving cells may be configured by RRC. One or more serving cells may be configured by RRC. A serving cell may use one TA value. One or more serving cells may use one TA value. A timing reference cell may be used. A PTAG (Primary TAG) may be a TAG that includes an SpCell. A STAG (Secondary TAG) is a TAG that does not include an SpCell. One or more serving cells may use two TA values.

[0256] A subTAG may be a group of one or more serving cells. A subTAG may be a group of serving cells that use the same TA (TA value). For example, a subTAG may be associated with one TRP information. For example, a subTAG may be associated with one TRP. The serving cell associated with a subTAG may not be associated with the TAG. For example, a subTAG may be configured for one serving cell. For example, the serving cell associated with a subTAG may be associated with a TAG. A subTAG may be a group of one or more TRPs. A subTAG may be a group of TRPs that use the same TA (TA value). For example, a subTAG may be associated with one serving cell. A subTAG may be a TA group for one serving cell. In one serving cell, two subTAGs may be provided, configured, or determined. A subTAG ID may be determined for each subTAG. A subTAG may be a type of TAG. That is, a TAG and a subTAG may be referred to as a TAG.

[0257] The RRC layer may configure one or more higher layer parameters for uplink time alignment maintenance. For example, the RRC layer may configure a time alignment timer. For example, the time alignment timer may be configured by a higher layer parameter timeAlignmentTimer. The time alignment timer may control a first time. The first time may be a time at which the MAC entity considers multiple serving cells to belong to the associated TAG. For example, the time alignment timer may It may also be time for time alignment, i.e., when the time synchronization timer is running. The term "operating" may mean that time synchronization has been achieved. The term "time synchronization" may mean that uplink timing has been determined (or adjusted). That is, the TA may be time synchronized.

[0258] The RRC layer may configure one or more higher layer parameters for maintaining uplink time synchronization. For example, the RRC layer may configure time synchronization timers. At least one of the multiple time synchronization timers may be associated with the subTAG. At least one of the synchronization timers may be associated with a TAG.

[0259] The time synchronization timer may correspond to one subTAG. For example, the time synchronization timer may be the time at which the MAC entity considers one or more serving cells to belong to the subTAG. For example, a time synchronization timer may control the time that a MAC entity considers one or more TRPs to belong to a subTAG.

[0260] The MAC entity may perform some or all of the first through fourth steps. stomach.

[0261] In the first process, a TA command MAC CE (Timing advance command MAC CE) is received, and then N TA If N is held in the indicated TAG, the MAC entity may apply the TA command for the indicated TAG. In the first process, a TA command MAC CE (Timing advance command MAC CE) is received and N TA If a TA command is held in the indicated TAG, the MAC entity shall start or restart the time synchronization timer associated with the indicated TA command. The time synchronization timer may be a timeAlignmentTimer.

[0262] The second process is when the TA command is a random access response ( The second process may be a process when the TA command is received. The second processing may be processing in one serving cell belonging to one TAG (or subTAG). The second processing may be processing in an SpCell. In the second processing, if a random access preamble is not selected from preambles in CBRA (Contention-based random access), the MAC entity selects a random access preamble for one TAG (or subTAG). A TA command may be applied to initiate or restart a time synchronization timer associated with one TAG (or subTAG). The TA command may be received via a random access response.

[0263] In a second process, when a time synchronization timer associated with a TAG (or subTAG) is not running, the MAC entity may apply a TA command for the TAG (or subTAG) and start the time synchronization timer. Furthermore, if contention resolution is not completed successfully, the MAC entity may stop the time synchronization timer.

[0264] In the second process, when the time synchronization timer associated with one subTAG is stopped, the MAC entity may apply the TA command in the random access response in the first random access procedure and start the time synchronization timer. Furthermore, if the contention resolution is not completed successfully, the MAC entity may stop the time synchronization timer. The first random access procedure was a random access procedure related to one subTAG. The first random access procedure may be a random access procedure for acquiring a TA.

[0265] In the second process, if a random access preamble is selected from the preambles in the CBRA and if a time synchronization timer associated with one TAG (or subTAG) is running, the MAC entity may ignore the received TA command.

[0266] In a third process, if an Absolute Timing Advance Command is received for a Message A (MSGA) transmission containing a C-RNTI MAC CE, the MAC entity may apply the absolute TA command for the Primary TAG (PTAG) and may start or restart a time synchronization timer associated with the Primary TAG (PTAG).

[0267] In the third process, when an absolute timing advance command related to one subTAG is received for a message A (MSGA) transmission containing a C-RNTI MAC CE, the MAC An entity may apply an absolute TA command for a subTAG and may start or restart a time synchronization timer associated with a subTAG.

[0268] The fourth process may be a process when the time synchronization timer expires. In the fourth process, the time synchronization timer expires in relation to the PTAG (or the subTAG associated with the first TRP). In this case, the MAC entity may perform some or all of the first through seventh sub-operations. A first sub-operation may be to flush all HARQ buffers for all serving cells. A second sub-operation may be to flush all HARQ buffers for all serving cells. The third sub-operation may be to notify RRC to release PUCCH for all serving cells. The third sub-operation may be to notify RRC to release SRS for all serving cells. The fourth sub-operation may be to clear the configured downlink assignment and the configured uplink grant. The fifth sub-operation may be to clear PUSCH resources for semi-persistent CSI reporting. The sixth sub-action is to consider all time-synchronized timers to have expired. The seventh sub-operation is to perform N for all TAGs (or subTAGs). TA That is, the time synchronization timer is not running. If N, the MAC entity TA In the fourth process, if the time synchronization timer is associated with a STAG (or a subTAG associated with the second TRP), the MAC entity may perform some or all of the eighth to thirteenth suboperations. The eighth suboperation may include performing all HARQ buffers for the serving cell that belong to this TAG (or this subTAG). A ninth sub-action may be to notify RRC to release the PUCCH for the serving cells that belong to this TAG (or this subTAG). A tenth sub-action may be to notify RRC to release the PUCCH for the serving cells that belong to this TAG (or this subTAG). An eleventh sub-action may be to notify RRC to release the SRS for the serving cell that belongs to this TAG (or this subTAG). Clearing the link assignment and the uplink grant that is set The twelfth sub-operation is to determine whether the serving cell belonging to this TAG (or this subTAG) Even if the PUSCH resource for quasi-static CSI reporting is cleared, The thirteenth sub-action is to TA It may also be to maintain.

[0269] The HARQ buffer may store MAC PDUs for transmission. A HARQ process may be associated with one HARQ process. One HARQ process may correspond to one HARQ process ID. Flushing the HARQ buffer may mean that the HARQ buffer becomes empty. A HARQ entity may allocate a transport block for one transport block. When requesting a new transmission, the HARQ process sends the MAC PDU to the associated Alternatively, the received data may be stored in a HARQ buffer.

[0270] Maximum uplink transmission timing difference If the MAC entity stops uplink transmission for the SCell because The entity may consider the time synchronization timer to expire when stopped. The time synchronization timer may be a time synchronization timer associated with the SCell.

[0271] If the time synchronization timer expires, the MAC entity shall perform uplink transmission. If the time synchronization timer is not running, the MAC entity The service may not perform uplink transmissions. This uplink transmission may not include a random access preamble transmission. This uplink transmission may not include a message A transmission. This uplink transmission may be an uplink transmission in one serving cell. The uplink transmission may be an uplink transmission in one TRP. The time synchronization timer may be a time synchronization timer associated with a TAG to which one serving cell belongs. The time synchronization timer may be associated with a subTAG to which one serving cell belongs. It may be a related time synchronization timer. This time synchronization timer may be a time synchronization timer related to the subTAG to which one TRP belongs.

[0272] If the time synchronization timer associated with one subTAG expires, the MAC entity The entity performs uplink transmission for one or more TRPs included in the one subTAG. If the time synchronization timer associated with a subTAG has expired, the MAC entity may not perform an uplink transmission associated with that subTAG. This uplink transmission may be a random access preamble transmission or a message A transmission. For example, if the time synchronization timer associated with one TRP information expires, the MAC entity may not perform uplink transmission associated with that one TRP information. You don't have to.

[0273] If the time synchronization timer associated with the PTAG is not running, the MAC entity will eventually In the serving cell, the MAC entity may not perform uplink transmissions. This uplink transmission may not include a random access preamble transmission in the SpCell. This uplink transmission may not include a message A transmission in the SpCell.

[0274] A MAC Protocol Data Unit (PDU) may be a byte-aligned bit string. A MAC PDU may be a transport block. For example, a MAC PDU may consist of one or more MAC subPDUs. Each MAC subPDU is assigned to one MAC subheading. Each MAC subPDU consists of one MAC subheader and one MAC SDU (Service Each MAC subPDU may consist of one MAC subheader and one MAC CE (Control Element). Each MAC subPDU may consist of one MAC header and padding. The MAC SDU may be data from a higher layer. The MAC SDU may be data to a higher layer.

[0275] The TA command may be a MAC CE. Also, the TA command may be included in a MAC CE. For example, the TA command may be included in a TA command MAC CE. The TA command MAC CE may be composed of a TAG ID and a TA command. The TAG ID is one of one TAG and one subTAG. The TAG containing the SpCell may correspond to TAG ID 0. The TAG ID may be specified by 2 bits. The TAG ID may specify one subTAG. The TAG ID may specify one TRP. The TA command specifies the T A You may also specify T A can be an integer between 0 and 63. A may be used to control the amount of timing adjustment. The timing adjustment may be applied by the MAC entity. The TA command may be indicated by 6 bits. The TA command MAC CE is a MAC subheader with a certain LCID (Logical channel ID). A certain LCID may be the LCID corresponding to index 61.

[0276] The TA command may be included in an absolute Timing advance command MAC CE. The absolute TA command MAC CE may consist of a reserved bit and the TA command. The TA command is included in an index value T A You may also specify T A may be used to control the amount of timing adjustment. The TA command may be indicated by 12 bits. The reserved bit may be 4 bits. The reserved bit may be set to the value 0. The absolute TA command MAC CE may consist of at least a TAG ID. The TAG ID may indicate one subTAG. The TAG ID may indicate one TRP. The absolute TA command MAC CE is , may be identified by a MAC subheader with an eLCID. The eLCID may be the corresponding eLCID in the address 316.

[0277] The TA command may be included in the random access response. For example, the TA command may be included in the MAC payload of the random access response. For example, the TA command is the index value T A You may also specify T A may be used to control the amount of timing adjustment. The size of the TA command field may be 12 bits. The random access response may consist of a TA command, an uplink grant, and a Temporary C-RNTI. The uplink grant may indicate the resources to be used in the uplink. The uplink grant field may be 27 bits. The Temporary C-RNTI indicates a temporary ID to be used by the MAC entity during random access. The Temporary C-RNTI field may be 16 bits. The random access response may be a MAC RAR. For example, the random access response may be a fallbackRAR. The TA command may be included in message B (MSGB). For example, the TA command The TA command may be included in the MAC payload of message B. The TA command may be included in successRAR. The random access response may also include TRP information. For example, the TA corresponding to one TRP identified by the TRP information sends the random access response This may be indicated by a TA command included in the request.

[0278] Random access (or random access procedure) is initiated by the MAC entity. Random access may be initiated by a PDCCH order (or PDCCH). Random access may be initiated by RRC. Random access on an SCell may be initiated by a PDCCH order. Random access may also be triggered by the MAC entity. Random access may be initiated by a PDCCH order. The random access may be triggered by the RRC.

[0279] For example, random access may be triggered by an event. For example, an event may be initial access from the RRC_IDLE state. For example, an event may be an RRC connection re-establishment procedure. For example, an event may be the arrival of uplink or downlink data in the RRC_CONNECTED state when the uplink synchronization state is 'non-synchronized'. For example, an event may be uplink data arrival during RRC_CONNECTED state when there are no PUCCH resources. For example, an event may be a scheduling request failure. For example, an event may be a request by RRC in response to a handover. For example, an event may be an RRC connection resume. For example, an event may be establishing time synchronization. For example, an event may be establishing time synchronization for a STAG. For example, an event may be establishing time synchronization for a TRP. For example, an event may be to request Other SI. For example, an event may be Beam failure recovery. For example, an event may be TA acquisition. For example, an event may be secondary TA acquisition. An event may be the purpose of a random access procedure.

[0280] The random access (random access type) may be a 4-step random access (4-step random access type). The 2-step random access type may be a 2-step random access type. The random access may support CBRA (Contention-based random access). That is, the random access may be CBRA. The random access may support CFRA (Contention-free random access). That is, the random access may be CFRA. For example, the random access may be a 4-step random access type. For example, the random access may be a CBRA of a four-step random access type. For example, the random access may be a CFRA of a two-step random access type. For example, the random access may be a CBRA of a two-step random access type. For example, the random access may be a CFRA of a two-step random access type.

[0281] In the 4-step random access type CBRA, the terminal device 1 receives message 1 (random In the two-step random access type CBRA, the terminal device 1 may transmit message A (random access preamble) and receive message B (contention resolution). In the four-step random access type CFRA, the terminal device 1 may transmit message A (random access preamble) and receive message B (contention resolution). In the two-step random access type CFRA, the terminal device 1 may receive a random access preamble, transmit a random access preamble, and receive a random access response. The random access control unit 100 may receive a random access preamble and PUSCH assignment, transmit a random access preamble and PUSCH, and receive a random access response.

[0282] If the CFRA resource is not configured, the 2-step random access type and the 4-step random access type are used. RSRP (Reference Signal Received Power) is used to select one of the random access types. A threshold may be used. 4-step - Random access type CFRA resource When the access is set, the terminal device 1 uses the random access of the 4-step random access type. When a CFRA resource of a two-step-random access type is configured, the terminal device 1 may perform a random access of a two-step-random access type. stomach.

[0283] Message 1 may be configured with one preamble on the PRACH. After transmitting Message 1, the terminal device 1 may send one response (random access request) within a set window. In CFRA, a dedicated preamble is assigned. In the CFRA, in response to receiving the random access response, the terminal device 1 In CBRA, in response to receiving the random access response, the terminal device 1 may transmit a message 3. For example, the terminal device 1 may Message 3 may be sent using the random access response grant. In CBRA, terminal device 1 may monitor message 4 (contention resolution). If contention resolution after transmission is not successful, terminal device 1 may transmit message 1.

[0284] Message A may include one preamble in the PRACH. Message A may also include a payload in the PUSCH. After transmitting message A, the terminal device 1 In CFRA, a dedicated preamble and PUSCH resource for transmitting message A may be allocated. In CFRA, upon receiving one response, the terminal device 1 may terminate random access. In CBRA, If the contention resolution is successful, the terminal device 1 may terminate the random access. If a fallback indication is received at node B, terminal device 1 MAY send message 3 based on fallback instructions and monitor conflict resolution. If the conflict resolution after sending message 3 is not successful, terminal device 1 will not If the random access of the two-step random access type is not completed, the terminal device 1 may be configured to switch to the CBRA of the four-step random access type.

[0285] The random access procedure may be initiated (triggered) by a PDCCH order. The random access procedure may be initiated (triggered) by MAC. The random access procedure may be initiated (triggered) by RRC. The random access procedure in the SCell may be initiated by a PDCCH order. The random access procedure in the cell associated with the additional PCI index The access procedure may be initiated by a PDCCH order.

[0286] In the MAC entity, only one random access may be in progress at a time. If a first random access is in progress and a second random access is triggered, the terminal device 1 may continue with the first random access. If in progress and if a second random access is triggered, the terminal device 1 may initiate the second random access.

[0287] For random access, RRC may request some or all of the first through ninth higher layer parameters. A first set of PRACH occasions for message 1 (random access preamble) transmission may be configured by a first higher layer parameter. The first set may be used for message A PRACH. A second set of PRACH occasions for random access preamble transmission for message A may be configured by a first higher layer parameter. The first higher layer parameter may be set by the RA parameter. That is, the first higher layer parameter may determine the available set of PRACH opportunities for the transmission of the random access preamble. The PRACH opportunities may also be referred to as RA opportunities. The PRACH opportunities may also be referred to as RACH occasions. Good too.

[0288] Some or all of the first to ninth upper layer parameters may be referred to as RACH configuration. The RACH configuration may be configured in the upper layer parameter SI-RequestConfig, the upper layer parameter ReconfigurationWithSync, the upper layer parameter BeamFailureRecoveryConfig, the upper layer parameter RACH-ConfigCommon, the upper layer parameter TwoTA-Config1-r18, and the upper layer parameter TwoTA-Config2-r18. The RACH configuration may be configured in the upper layer parameter SI-RequestConfig, The RACH configuration may be included in some or all of the upper layer parameter ReconfigurationWithSync, the upper layer parameter BeamFailureRecoveryConfig, the upper layer parameter RACH-ConfigCommon, the upper layer parameter TwoTA-Config1-r18, and the upper layer parameter TwoTA-Config2-r18. , RACH-ConfigGeneric.

[0289] The first upper layer parameter may be prach-ConfigurationIndex. The first upper layer parameter may be set in the configuration for second TA acquisition (one or both of the upper layer parameter twoTA-Config1-r18 and the upper layer parameter twoTA-Config2-r18). The second TA acquisition is performed when two TAs (TAGs or subTAGs) are determined, provided, and assigned in one serving cell. Alternatively, it may be set.

[0290] The power of the random access preamble may be set by a third higher layer parameter, for example, the power of the initial (first transmission) random access preamble may be set by a third higher layer parameter.

[0291] The RSRP threshold may be set by a fourth higher layer parameter. For example, the RSRP threshold may be the RSRP threshold for SS / PBCH block selection or CSI-RS selection. For example, The RSRP threshold may be an RSRP threshold for selecting between two uplink carriers. The two uplink carriers may be a normal uplink (NUL) and a supplementary uplink (SUL). good.

[0292] The maximum number of transmissions of one or both of message 1 and message A may be set by a fifth upper layer parameter. One or both of message 1 and message A may change their transmission power for each transmission. For example, the power of one or both of message 1 and message A may be changed based on a sixth upper layer parameter. The sixth upper layer parameter may be a power ramping factor.

[0293] The random access preamble may be configured by a seventh higher layer parameter, e.g., the index of the random access preamble used in the PRACH occasion. may be set by a seventh upper layer parameter. The seventh upper layer parameter is 0 The seventh upper layer parameter may be ra-PreambleIndex.

[0294] The number of SS / PBCH blocks mapped to each PRACH opportunity may be defined by an eighth higher layer parameter. The number of ambles may be defined by an eighth higher layer parameter. The CBRA random access preamble may be a Contention-based Random Access Preamble. The transmission of message 1 and / or message A is performed by group A or group B. For example, the terminal device 1 may transmit a message A using random access preamble group A. For example, the terminal device 1 may transmit a message A using random access preamble group B. may be executed.

[0295] The ninth higher layer parameter may define a PRACH opportunity associated with one SS / PBCH block (SSB). The MAC entity may transmit a random access preamble in the PRACH opportunity. The ninth higher layer parameter may be ra-ssb-OccasionMaskIndex.

[0296] First through twelfth UE variables may be used for the random access procedure. The first variable may be PREAMBLE_INDEX. The second variable may be PREAMBLE_TRANSMISSION_COUNTER. The third variable may be PREAMBLE_POWER_RAMPING_COUNTER. The fourth variable may be PREAMBLE_POWER_RAMPING_STEP. The fifth variable The sixth variable may be PREAMBLE_RECEIVED_TARGET_POWER. The sixth variable may be PREAMBLE_BACKOFF. The seventh variable may be PCMAC. The eighth variable may be SCALING_FACTOR_BI. The ninth variable may be TEMPORARY_C-RNTI. The tenth variable may be RA_TYPE. The eleventh variable may be POWER_OFFSET_2STEP_RA. The twelfth variable may be MSGA_PREAMBLE_POWER_RAMPIPNG_STEP.

[0297] RA_TYPE may be set to 4-step RA. For example, if the random access procedure is initiated by a PDCCH order, and the index of the random access preamble (ra-PreambleIndex) is provided by the PDCCH, and the index of the random access preamble (ra-PreambleIndex) is set to 4-step RA. If the index is not 0b000000, RA_TYPE may be set to 4-step RA. For example, SI If a random access procedure is initiated for a request and if random access resources (RACH configuration) are provided by RRC for an SI request, RA_TYPE may be set to 4-stepRA. If a random access procedure is initiated for beam failure recovery (or beam failure recovery for an SpCell) and if CFRA resources corresponding to a beam failure recovery request for 4-step-random access type are provided, RA_TYPE A 4-step RA may be set to for Reconfiguration with sync. If a random access procedure is initiated in the next TA acquisition, and if the higher layer parameter rach-ConfigDedicated provides CFRA resources for the 4-step random access type, RA_TYPE may be set to 4-stepRA. If a random access procedure is initiated and a random access resource (e.g. For example, if a random access resource (CFRA resource) is provided, RA_TYPE may be set to 4-step RA. The random access resource may be one or both of a CFRA resource and a CBRA resource. Providing a random access resource may mean that a RACH configuration is configured. Obtaining a second TA means obtaining a second (or two) TAs in one serving cell. If RA_TYPE is set to 4-stepRA, the 4-step A random access of the random access type may be performed. If the random access is set to 0, a two-step random access type random access may be performed.

[0298] If RA_TYPE is set to 4-StepRA, the MAC entity may perform any of the first to sixth operations.

[0299] The first operation may be performed when a random access procedure is initiated for beam failure recovery. The first operation may be performed when a beam failure recovery timer (beamFailureRecoveryTimer) is running or is not set. The first operation may be performed if contention-free Random Access Resources (CFRA) for the beam failure recovery request are provided by the RRC. The beam failure recovery request may be related to either SSB or CSI-RS. The first operation may be performed by at least This may be performed if one more SSB or at least one CSI-RS is available. At least one SSB may be an SSB with a Reference Signal Received Power (RSRP) above a threshold. At least one CSI-RS may be a CSI-RS with an RSRP above a threshold. In a first operation, the MAC entity may select a first SSB. The first SSB is In a first operation, the MAC entity may select a first CSI-RS. The first CSI-RS may be a CSI-RS included in a first reference signal set. The first SSB may be an SSB with an RSRP exceeding a certain threshold. In a first operation, the MAC entity may select a first CSI-RS. The first CSI-RS may be a CSI-RS included in a first reference signal set. The first CSI-RS may be a CSI-RS with an RSRP exceeding a certain threshold. The first reference signal set is set by candidateBeamRSList. If the first SSB is selected, the first random access A preamble index (ra-PreambleIndex) may be set. The first random access preamble index may be ra-PreambleIndex corresponding to an SSB selected from a set of random access preambles for beam obstruction recovery.

[0300] A second operation may be performed if a random access preamble index (ra-PreambleIndex) is provided by the PDCCH (PDCCH order). A second operation may be performed if the random access preamble index is not 0b000000. In the second operation, the MAC entity sets the random access preamble index in PREAMBLE_INDEX. In the second operation, one SSB is signaled by the PDCCH. This may be done.

[0301] The second operation may be performed if a random access preamble index (ra-PreambleIndex) is provided by the PDCCH (PDCCH order). The second operation may be performed if the random access preamble index is not 0b000000. The second operation may be performed if the PDCCH provides a first value. The second operation may be performed if the first value is determined by the PDCCH. In the second operation, the MAC entity The first value may set PREAMBLE_INDEX to a second random access preamble index. The second random access preamble index may be a random access preamble index for acquiring a second TA. The second random access preamble index may be ra-PreambleIndex corresponding to an indicated SSB from a set of random access preambles for acquiring a second TA. The first value may specify one RACH configuration. The first value may specify one higher layer parameter including the RACH configuration. The first value may be additional PCI index, TAG ID, and TRP information.

[0302] A third action may be performed: If a source is provided, a third operation may be performed. If at least one SSB is available, a third operation may be performed. The at least one SSB may be an SSB with an RSRP above a certain threshold. In the third operation, the MAC entity may select one SSB. The one SSB may have an RSRP above a certain threshold. In the third operation, PREAMBLE_INDEX may be set to the ra-PreambleIndex corresponding to the selected SSB.

[0303] A fourth operation may be performed. If a random access procedure for the SI request is initiated, the fourth operation may be performed. If a random access resource for the SI request is provided by the RRC, the fourth operation may be performed. In the fourth operation, If at least one SSB is available, the MAC entity may select one SSB. At least one SSB may have an RSRP above a certain threshold. One SSB may have an RSRP above a certain threshold. In a fourth operation, the MAC entity may select any SSB, as determined according to the higher layer parameter ra-PreambleStartIndex. From the random access preambles, one random access preamble corresponding to the selected SSB may be selected. In a fourth operation, PREAMBLE_INDEX may be set to the selected random access preamble.

[0304] A fifth operation may be performed. A fifth operation may be performed for CBRA preamble selection. In the fifth operation, the MAC entity may select one SSB. The one SSB may be In a fifth operation, the MAC entity may You may select any SSB.

[0305] A sixth operation may be performed. If a random access procedure for acquiring the second TA is initiated, the sixth operation may be performed. If a random access resource for acquiring the second TA is provided by RRC, the sixth operation may be performed. In the sixth operation, the MAC entity may select one SSB. The one SSB may have an RSRP exceeding a certain threshold. In the sixth operation, an arbitrary SSB may be selected. In the sixth operation, a random access preamble index (ra-PreambleIndex) corresponding to the selected SSB may be set. The random access resource for acquiring the second TA may be determined in one or both of the upper layer parameter twoTA-Config1-r18 and the upper layer parameter twoTA-Config2-r18.

[0306] The random access preamble is associated with a reference signal (SSB and / or CSI-RS). For example, the number of random access preambles per reference signal may be set to the upper layer packet size. The time may be determined by the parameter.

[0307] When the random access procedure is initiated due to an SI request and when the first higher layer parameter is configured, the MAC entity may determine a first PRACH occasion. The first PRACH occasion may be associated with the selected SSB. First PRACH occasion may be determined based on a first constraint. The first constraint may be given by an upper layer parameter ra-ssb-OccasionMaskIndex. The first PRACH opportunity may be the next valid PRACH opportunity. The first upper layer parameter may be one or both of ra-AssociationPeriodIndex and si-RequestPeriod.

[0308] When RA_TYPE is set to 4-StepRA, it will be one of the first to sixth actions. In the case where SSB is selected, the MAC entity may determine a second PRACH opportunity. The selected SSB may be permitted by a first restriction, or may be indicated by a PDCCH (PDCCH order).

[0309] When RA_TYPE is set to 4-StepRA, it will be one of the first to sixth actions. In the above, if a CSI-RS is selected and there is no CFRA resource associated with the selected CSI-RS, the MAC entity may determine a third PRACH opportunity based on the SSB.

[0310] When RA_TYPE is set to 4-StepRA, it will be one of the first to sixth actions. In this case, if a CSI-RS is selected, the MAC entity transmits the first CSI-RS corresponding to the selected CSI-RS. Four PRACH opportunities may be determined.

[0311] Random access (random access procedure) is initiated in one serving cell When the MAC entity receives the message 3, it may flush the message 3 buffer, flush the message A buffer, and select a carrier for performing random access. The random access resource selection procedure may be performed, a random access type may be determined, and a random access resource selection procedure may be performed.

[0312] The MAC entity may randomly select one PRACH opportunity from the multiple PRACH opportunities.

[0313] The MAC entity may perform a random access preamble transmission procedure.

[0314] The MAC entity allocates power based on a counter for each random access type. The MAC entity may calculate the RA-RNTI associated with the PRACH opportunity on which the random access preamble is transmitted. The MAC entity may determine the selected PRACH opportunity. The PRACH may be used to signal the physical layer to transmit a random access preamble. The RA-RNTI associated with the opportunity is the index of the first OFDM symbol of the PRACH opportunity and the The PRACH opportunity index may be calculated based on some or all of the index of the first slot of the PRACH opportunity in the system frame, the index of the PRACH opportunity in the frequency domain, and the uplink carrier on which the random access preamble is transmitted.

[0315] The MAC entity shall transmit the first window The random access preamble may be a Contention-free Random Access Preamble (CFRA Random Access Preamble). The random access preamble may be a Contention-based Random Access Preamble (CBRA Random Access Preamble). The MAC entity may use a PDCCH for the random access response. For example, while the first window is running, the MAC entity may monitor the PDCCH. The PDCCH may be the PDCCH in the SpCell. Reception of the PDCCH An indication of this may be received from the physical layer. The PDCCH transmission may be addressed to the C-RNTI. If a CFRA random access preamble is sent by the MAC entity, the MAC entity may consider the random access to be successfully completed.

[0316] A valid downlink assignment may be received on a PDCCH corresponding to the RA-RNTI. The received transport block may be decoded. The random access response may include a MAC subPDU. The MAC subPDU may be accompanied by a random access preamble ID. Based at least on the random access response including the MAC subPDU, the MAC entity may determine that the random access response was successfully received. It may be considered as such.

[0317] A MAC entity may consider receipt of a random access response to be successful. Based at least on the deemed successful receipt of the random access response, the MAC entity may consider the random access to have been successfully completed, may indicate receipt of an acknowledgement to upper layers, and may apply the received TA command. For example, the MAC entity may process the value of the received UL grant, or may indicate the received UL grant to the physical layer.

[0318] If the reception of the random access response is considered successful, and one service When a random access preamble is transmitted in the receiving cell, the MAC entity The random access response is considered to be received successfully and the random access command is processed for one serving cell. and based at least on the dumb access preamble being transmitted, the MAC entity The random access level may apply a TA command for one serving cell. Based at least on the response being considered successful, the MAC entity For example, if a MAC PDU contains a TA command (e.g. For example, if the MAC PDU contains an absolute TA command (MAC CE), the MAC entity may process the TA command. For example, the MAC PDU may be included in a transport block. For example, , one or more MAC SDUs may be multiplexed into a transport block. Alternatively, multiple MAC SDUs may be demultiplexed from a transport block. Good too.

[0319] For the MAC entity, the BFR (Beam failure recovery) procedure is sent to the RRC. The BFR procedure configuration may include RACH configuration. The BFR procedure configuration may be the higher layer parameter BeamFailureRecoveryConfig. The MAC entity may BFI_COUNTER is a beam obstruction candidate indicator. The first random access procedure may be a random access procedure for beam failure recovery.

[0320] The terminal device 1 may receive the higher layer parameters. The terminal device 1 may initiate a random access procedure in response to receiving the higher layer parameters RRCReconfiguration. For example, when the higher layer parameters RRCReconfiguration are received in the higher layer parameters nr-SCG, and when the higher layer parameters nr-SCG include the higher layer parameters reconfigurationWithSync, The terminal device 1 may initiate a second random access procedure in the RRC. RRCReconfiguration may be received for NR SCG RRC Reconfiguration. The second random access procedure is a random access for reconfiguration with sync. It may also be a procedure.

[0321] A second TA acquisition procedure may be configured by RRC for the MAC entity. The configuration of the second TA acquisition procedure may include RACH configuration. The configuration of the second TA acquisition procedure may be one or both of TwoTA-Config1-r18 and TwoTA-Config2-r18. The MAC entity For example, the MAC entity may acquire a tag associated with the subTAG. A second TA acquisition may be triggered based on the expiration of a subTAG. A maximum of two subTAGs may be provided in one serving cell. The second TA acquisition may be triggered based on the expiration of a subTAG in one serving cell. A third random access procedure may be initiated based on the triggering of the second TA acquisition. The third random access procedure may be a random access procedure for acquiring the second TA. TwoTA-Config1-r18 If one or both of TwoTA-Config2-r18 are provided, The random access procedure may be initiated in MAC or RRC.

[0322] Before the start of random access (physical random access procedure), the physical layer may receive a set of SS / PBCH block indices from higher layers and provide a set of RSRP measurements to higher layers. Before starting random access, the physical layer may instruct the upper layer to perform Type 1 random access. Before starting random access, the physical layer may instruct the upper layer to perform Type 2 random access. Type 1 random access may be a 4-step random access type random access. Type 2 random access may be a 2-step random access type random access. Before starting random access, the physical layer may instruct the upper layer to perform Type 2 random access. The one or more parameters may be received from a layer. The one or more parameters may include a PRACH transmission parameter configuration. The PRACH transmission parameter configuration may be a RACH configuration. The PRACH transmission parameter may be a PRACH preamble format, a time resource, or a frequency resource for the PRACH transmission. The one or more parameters may be a PRACH preamble format, a time resource, or a frequency resource for determining the root sequence. The one or more parameters may include a PRACH preamble sequence (e.g., Parameter that determines the cyclic shift in the random access preamble sequence The one or more parameters may include TRP information. For example, A random access preamble may be associated with one TRP.

[0323] Random access is achieved by transmitting message 1 and message 2 on the PRACH at least once. The random access may include transmission of message 1 on the PRACH, message 2, transmission of a PUSCH scheduled by a random access response uplink grant, and a PDSCH for contention resolution. Message 1 may be a random access preamble. Message 2 may be a random access response message (random access response). For example, message 2 may be a random access response accompanied by a PDCCH / PDSCH. The random access procedure is called random access. Good too.

[0324] The random access may include at least the transmission of a message A and the reception of a message B. The random access may include the transmission of the message A, the reception of the message B, the transmission of a PUSCH scheduled by a random access response grant, and contention resolution. Message A may include a PDSCH for random access protocol on PRACH. The message B may be a random access response grant. For example, the message B may be a random access response grant accompanied by a PDCCH / PDSCH. The random access response grant may be a fallback random access response grant.

[0325] If random access is initiated by a PDCCH order, the PRACH transmission (random access The PRACH transmission (pre-preamble transmission) may have the same subcarrier spacing as the PRACH transmission initiated by a higher layer. When two uplink carriers are configured in one serving cell and the terminal device 1 detects a PDCCH order, the terminal device 1 may use the value of the UL / SUL indication field from the detected PDCCH order to determine one uplink carrier for the PRACH transmission. When N TRPs are configured in one serving cell, If this is the case, and if the terminal device 1 detects a PDCCH order, the terminal device 1 may use one field (or field number) of the detected PDCCH order to determine one TRP for PRACH transmission. In the random access procedure for acquiring the second TA, one field of the PDCCH order may include an additional PCI index.

[0326] The random access may be triggered by a higher layer or a PDCCH order in response to a request for PRACH transmission. The configuration by the higher layer for PRACH transmission may include some or all of the following: a configuration for PRACH transmission, a preamble index (index of the random access preamble), a preamble SCS (subcarrier spacing of the random access preamble), RA-RNTI, PRACH resources, and TRP information.

[0327] The random access preamble may be a contention-based preamble. The dumb access preamble may be a contention-free preamble. The number of contention-based preambles per opportunity and per SS / PBCH block index may be configured by higher layer parameters. The PRACH opportunity may be enabled. For example, Based at least on the OFDM symbols configured for time division duplex, the PRACH opportunity is It may be effective.

[0328] Terminal device 1 decodes DCI format 1_0 with CRC scrambled with RA-RNTI For example, in response to a PRACH transmission, the terminal device 1 may attempt to decode DCI format 1_0 with a CRC scrambled with the RA-RNTI within a certain window. A certain window may be determined based at least on the first OFDM symbol of the CORESET. It may be started.

[0329] The terminal device 1 detects DCI format 1_0 with a scrambled CRC in the RA-RNTI. and, based at least on the terminal device 1 receiving the transport block, The terminal device 1 may pass the transport block to a higher layer. The PRACH transmission may be received on the PDSCH within a window. Higher layers may parse the transport block corresponding to the Random Access Preamble Identity (RAPID) associated with the PRACH transmission. To identify RAPID in a response (random access response message), The upper layer instructs the physical layer to send an uplink grant (random access response grant). The random access response may be a transport block random access response. The random access response grant may be a random access response uplink grant.

[0330] Terminal device 1 winds up DCI format 1_0 with CRC scrambled with RA-RNTI. If the PDSCH transport block is not detected within the window, or If the PRACH is not received within the specified time, the higher layer may instruct the physical layer to transmit the PRACH. If the higher layer does not identify a RAPID associated with the PRACH transmission, the higher layer shall For example, the terminal device 1 may instruct the physical layer to The terminal device 1 may be expected to transmit the PRACH within a predetermined time after the last OFDM symbol of the PDSCH reception. Furthermore, the terminal device 1 may be expected to transmit the PRACH within a predetermined time after the last OFDM symbol of the PDSCH reception. Transmitting the PRACH means transmitting a random access preamble. It is also possible.

[0331] A PDCCH order may trigger a contention-free random access procedure (CFRA). For example, a PDCCH order may trigger a CFRA in one SpCell. The terminal device 1 may initiate a PRACH transmission. If a PDCCH with DCI format 1_0 with CRC scrambled by RA-RNTI is attempted to detect in response to a PRACH transmission from the same DMRS antenna, the PDCCH with DCI format 1_0 and the PDCCH with DCI format 1_0 are transmitted from the same DMRS antenna. It may be assumed that the port has QCL characteristics, which may be large-scale characteristics of the channel.

[0332] A random access response grant may consist of one or more fields. For example, one or more fields may include a frequency hopping flag field. For example, the one or more fields may include a frequency domain resource allocation field (or a PUSCH frequency resource allocation field). The number of fields may include a time domain resource allocation field (or a PUSCH time resource allocation field). For example, one or more fields may include a Transmission Power Control (TPC) command field. For example, one or more fields may include a CSI request field. For example, one or more fields may include a field with TRP information.

[0333] When the CRC of DCI format 1_0 is scrambled by C-RNTI, and If the area resource allocation field is all "1", DCI format 1_0 is the first line. The first random access procedure may be used for the PDCCH. It may also be called an order-initiated random access procedure, i.e., DCI The PDCCH to which format 1_0 is mapped may be in PDCCH order.

[0334] The DCI format in the PDCCH order may include a Random Access Preamble Index field. The Random Access Preamble Index may be ra-PreambleIndex. The DCI format in the PDCCH order may include a UL / SUL indicator field. The UL / SUL indicator field may indicate an UL carrier. The DCI format in the PDCCH order may include an SS / PBCH index field. The SS / PBCH index field may indicate one SS / PBCH. One SS / PBCH is used as the RACH for PRACH transmission. The random access preamble may be used to determine the PRACH opportunity. If the index value is not all "0", the SS / PBCH index field may indicate one SS / PBCH. The DCI format in the PDCCH order is PRACH mask index. The PRACH Mask Index field may include a PRACH Mask Index field. A RACH opportunity may be associated with one SS / PBCH. If the value of the random access preamble index is not all "0", the PRACH mask index field may indicate one RACH opportunity. The DCI format in the PDCCH order may include an Additional PCI Index field. The Additional PCI Index field indicates the first higher layer parameter including the RACH configuration. The Additional PCI Index field indicates one additional PCI index. One additional PCI index may be associated with a first upper layer parameter including a RACH configuration. The first upper layer parameter may be twoTA-Config1-r18. The layer parameter may be twoTA-Config2-r18.

[0335] The PCI (Physical Cell ID) may be referred to as a physical cell ID. The additional PCI may be a physical cell ID for a non-serving cell. The additional PCI index may be: The additional PCI index may be an index for specifying an additional PCI. The additional PCI index may be set by a higher layer parameter. The additional PCI index may be indicated by a DCI field. The additional PCI index may be used to indicate a physical cell ID. good.

[0336] FIG. 9 is a diagram illustrating an example of obtaining a second TA according to one aspect of this embodiment.

[0337] The terminal device 1 receives the first random access preamplifier in the first random access 9000. The terminal device 1 may transmit the first random access 9000. The terminal device 1 may receive a random access response 9020. The terminal device 1 may transmit a second random access preamble 9011 in the second random access process 9001. The terminal device 1 may receive a second random access response 9021 in the second random access process 9001. For example, when the first random access 9000 is initiated (triggered), the terminal device 1 may transmit a first random access preamble 9010. When the second random access 9001 is initiated (triggered), the terminal device 1 may transmit a second random access preamble 9011, and may receive an access response 9020. A second random access response 9021 may be received.

[0338] The terminal device 1 may transmit a first random access preamble 9010 based at least on the first TRP information 9030. For example, the first random access preamble 9010 may correspond to a first TRP 9040. The terminal device 1 may receive a first random access response 9020 including the first TRP information 9030. The terminal device 1 may transmit a second random access preamble 9011 based at least on the second TRP information 9031. For example, the second random access preamble 9011 may correspond to a second TRP 9041. The terminal device 1 may receive a second random access response 9020 including the second TRP information 9031. For example, the first higher layer parameter may indicate that the first random access preamble 9010 is to be transmitted to the first TRP 9040. For example, the second random access preamble 9011 is transmitted to the second TRP 9041, and the second higher layer parameter The first upper layer parameter and the second upper layer parameter may be the same.

[0339] The random access response may include a TA command. For example, the first random access response 9020 may include a first TA command 9050. For example, the second random access response 9021 may include a second TA command 9051. The first TA command 9050 may be different from the second TA command 9051. That is, the first TA command 9050 may be independent of the second TA command 9051. The terminal device 1 may receive the first TA command 9050. The terminal device 1 may receive the second TA command 9051.

[0340] Based on the first TA command 9050, a first TA 9060 may be determined. A first uplink timing 9070 may be determined based on the first TA command 9050. The first uplink timing 9070 is the uplink timing between the terminal device 1 and the first TRP 9040. Based on the second TA command 9051, the second TA 9061 is determined. That is, the second uplink timing 9071 may be determined based on the second TA command 9051. The second uplink timing 9071 is determined by the terminal device 1 and the second TRP 9041. The uplink timing may be TA.

[0341] The first TA 9060 may correspond to the first subTAG 9200. The second TA 9061 may correspond to the second subTAG 9201. The first subTAG 9200 may correspond to the first TAG ID 9300. The second subTAG 9201 may correspond to the second TAG ID 9301.

[0342] The first TRP 9040 and the second TRP 9041 may be different TRPs. The second TRP 9041 may be set by a higher layer parameter. The first TRP 9040 and the second TRP 9041 may be determined by a higher layer parameter. If the higher layer parameter is not set, it may be assumed that there is no second TRP 9041. The first TRP 9040 is configured with a first ID ( The second TRP 9041 may be identified by a second ID (or index). The first ID and the second ID are determined by the upper layer parameter The first ID and the second ID may be included in the DCI format. The first ID and the second ID may be included in the random access response.

[0343] The base station device 3 may be configured with a first TRP 9040 and a second TRP 9041. For example, The station device 3 may have two transmission / reception points (base station device 3a and base station device 3b). The first TRP 9040 may be the transmission / reception point of the base station device 3a. The second TRP 9041 may be the transmission / reception point of the base station device 3b. The base station device 3a has the functions of the base station device 3. The base station device 3b may be independent of the base station device 3. For example, the base station device 3a may not be synchronized with the base station device 3b. The TRP information is used to select either the base station device 3a or the base station device 3b. It may also be used to

[0344] The first TA command 9050 and the second TA command 9051 may be applied to one serving cell 9900. For example, the first TA command 9050 and the second TA command 9051 may be applied to one serving cell 9900. For example, the first TA command 9050 and the second TA command 9051 may be received in one serving cell 9900. The first TA command 9050 and the second TA command 9051 are TA commands for one serving cell 9900. For example, the first TA command 9050 and the second TA command 9051 may be TA commands for one TAG. For example, the first TA command 9050 and the second TA command 9051 may be TA commands for one time synchronization timer. The first command 9050 and the second TA command 9051 are for one time synchronization timer associated with one TAG. It may be a TA command.

[0345] The first TA 9060 and the second TA 9061 may apply to one serving cell 9900. For example, the first TA 9060 and the second TA 9061 are received in one serving cell 9900. For example, the first TA 9060 and the second TA 9061 may be TAs for one serving cell 9900. That is, the terminal device 1 may use the first TA 9060 and the second TA 9061 in one serving cell 9900. The first TA 9060 may use the first TA 9060 and the second TA 9061 based on the second TA command 9051. The second TA 9061 does not have to be updated (changed) based on the first TA command 9050.

[0346] The first uplink timing 9070 and the second uplink timing 9071 are used for one service. For example, the first uplink timing 9070 and the second uplink timing 9071 may be received in one serving cell 9900. For example, the first uplink timing 9070 and the second uplink timing 9071 are one service. The timing may be the uplink timing for the receiving cell 9900. That is, the terminal device 1 In one serving cell 9900, a first uplink timing 9070 and a second uplink timing The first uplink timing 9070 may be used based on the second TA command 9051. The second uplink timing 9071 may not be updated (changed) based on the first TA command 9050.

[0347] The terminal device 1 receives the first uplink timing 9070 and the second uplink timing 9071. For example, for transmission of one uplink physical channel in one serving cell 9900, the terminal device 1 may switch between the first uplink timing 9070 and the second uplink timing 9080. For example, the terminal device 1 may use one of the first uplink timing 9070 and the second uplink timing 9071 as one uplink timing based on the TRP information. For example, the terminal device 1 may determine, based on the subTAG, One of the first uplink timing 9070 and the second uplink timing 9071 is used as one uplink For example, the terminal device 1 may correspond one of the first uplink timing 9070 and the second uplink timing 9071 to one uplink physical channel transmission based on an instruction from an upper layer (e.g., MAC layer). The device 1 selects one of the first uplink timing 9070 and the second uplink timing 9071. For example, the terminal device 1 may select the first uplink timing based on certain information. The TRP may select one of the first uplink timing 9070 and the second uplink timing 9071. The terminal device 1 may receive certain information or a subTAG. The parameter containing the information may be received. The parameter containing the information may be either a higher layer parameter or a DCI format.

[0348] Switching between the first uplink timing 9070 and the second uplink timing 9071 may be switching between the first uplink frame 9080 and the second uplink frame 9081. This switching may be called TA switching. This switching may be indicated in the DCI format. TA switching is performed by switching the transmission of the uplink physical channel. The TA switching may be triggered based on the DCI format instructing the TA switching. The TA switching may take a predetermined time 9090. For example, the TA switching may be completed after the predetermined time 9090 from the first time position. The first time position may be a DCI format instructing the TA switching. The TA switching may be performed on the first OFDM symbol of the PDCCH. When TA switching is performed from the first uplink timing 9070 to the second uplink timing 9071, the first time position may be the last OFDM symbol of the latest uplink physical channel corresponding to the first uplink timing 9070. When TA switching is performed from the first uplink timing 9070 to the second uplink timing 9071, the first time position indicates the transmission of the uplink physical channel corresponding to the second uplink timing 9071 (uplink The predetermined time 9090 may be the last OFDM symbol of the PDCCH in which the DCI format (scheduling the physical channel) is placed. The predetermined time 9090 may be defined by any of a time unit, a real time (e.g., milliseconds, seconds), a number of OFDM symbols, and a number of slots. The time 9090 may be determined based on some or all of the following: maximum propagation delay difference, maximum uplink transmission timing difference, CP, UE capability, frequency range, and higher layer parameters. For example, the predetermined time period 9090 may be 14 OFDM symbols.

[0349] The terminal device 1 may transmit, in one serving cell 9900, a first uplink physical channel 9100 corresponding to a first uplink timing 9070 and a second uplink physical channel 9101 corresponding to a second uplink timing 9071. The first uplink physical channel 9100 and the second uplink physical channel 9101 may be the same. For example, The first uplink physical channel transmission 9101 may be a repetition of the first uplink physical channel transmission 9100. That is, the terminal device 1 simultaneously transmits one uplink corresponding to the first uplink timing 9070 and the second uplink timing 9071 in one serving cell. That's fine.

[0350] The first random access 9000 may be a CBRA, and the second random access 9001 may be a CFRA. For example, the second random access 9001 may be initiated (triggered) by a PDCCH order. One of the first random access 9000 and the second random access 9001 may be a CFRA. One of the first random access 9000 and the second random access 9001 For example, the second random access 9001 is initiated by CFRA. In some cases, the second random access response 9021 may correspond to the first TRP 9040. For example, if the second random access 9001 is a CFRA, the second random access preamble 9011 may correspond to the second TRP 9041, and the second random access response may correspond to the first TRP 9040. That is, the CFRA acquires the second TA 9061 (acquires the second TA). That is, the CSS set for the second TRP 9041 is not set. Good too.

[0351] Corresponding to the first TRP 9040 may be corresponding to any of the first TRP information 9030, the first TA 9060, the first uplink timing 9070, the first subTAG 9200, and the first TAG ID 9300. Corresponding to the second TRP 9041 may be corresponding to any of the second TRP information 9031, the second The timing information may correspond to any of the TA 9061, the second uplink timing 9071, the second subTAG 9201, and the second TAG ID 9301.

[0352] The first random access 9000 may be a first CBRA, and the second random access 9001 may be a second CBRA. The first random access 9000 and the second random access 9001 may not be performed simultaneously. For example, the first random access 9000 may be performed by accessing a part of the first SS / PBCH block index, the first SS / PBCH block, and the first SS / PBCH candidate. The second random access 9001 may be based on the second SS / PBCH block. The second SS / PBCH candidate may be based on some or all of the index, the second SS / PBCH block, and the second SS / PBCH candidate.

[0353] The first random access preamble 9010 may be transmitted to the first TRP. The random access preamble 9011 may be transmitted to a second TRP. A higher layer parameter may indicate that the random access preamble 9010 is to be transmitted to the first TRP 9040. For example, a higher layer parameter may indicate that the second random access preamble 9011 is to be transmitted to the second TRP 9041. A PDCCH (e.g., a PDCCH order) may indicate that the first random access preamble 9010 is to be transmitted to the first TRP 9040. A PDCCH (e.g., a PDCCH order) may indicate that the second random access preamble 9011 is to be transmitted to the second TRP 9041.

[0354] The first TA 9060 and / or the first uplink timing 9070 are The second TA 9061 and / or the second uplink timing 9071 may be determined based at least on the TA offset 9400 and the first TA command 9050. The first TA offset 9400 and the second TA offset 9401 may be determined based at least on the offset 9401 and the second TA command 9051. The first TA offset 9400 and the second TA offset 9401 may be the same. For example, the first TA offset 9400 and the second TA offset 9401 may be set by one upper layer parameter. For example, if one higher layer parameter is not provided, the terminal device 1 may determine the first TA offset 9400 and the second TA offset 9401 as one value.

[0355] The first TA command 9050 may control the amount of the first timing adjustment (first uplink timing adjustment). The second TA command 9051 may control the amount of the second timing adjustment (second uplink timing adjustment). That is, the first TA command 9050 may control the amount of the first T A The second TA command 9051 may instruct the second T A You may also specify the first T A and Second T A may be different.

[0356] In response to receiving the first TA command 9050, the terminal device 1 may adjust (determine) the first uplink timing 9070 for transmitting the first uplink physical channel 9100. In response to receiving the command 9051, the terminal device 1 transmits the second uplink physical channel 9101. Therefore, the second uplink timing 9071 may be adjusted (determined).

[0357] The RRC layer uses a first time alignment timer 9800 and a second time alignment timer The RRC layer may configure a first time synchronization timer 9800 and a second time synchronization timer 9801 for one serving cell 9900. For example, the RRC layer may configure a first time synchronization timer 9800 and a second time synchronization timer 9801 for one serving cell 9900. For example, the first time synchronization timer 9800 may be configured by a first upper layer parameter. For example, the second time synchronization timer 9801 may be configured by a second upper layer parameter. The first upper layer parameter and the second upper layer parameter may not be the upper layer parameter timeAlignmentTimer. The first time synchronization timer 9800 may control a first time. The first time may be a time at which the MAC entity considers that at least a first TRP 9040 belongs to the first subTAG 9200. The second time synchronization timer 9801 may control a second time. The second time may be a time at which the MAC entity considers that at least a second TRP 9041 belongs to the second subTAG 9201.

[0358] Based at least on the first TA command 9050, a first time synchronization timer 9800 may be started or restarted. The first time synchronization timer 9800 may be associated with the first TRP 9040. The first time synchronization timer 9800 may be associated with the first subTAG 9200. The first subTAG 9200 may identify the first TRP 9040 from one or more TRPs. First subTAG 9200 may include a first TRP 9040. For example, the first subTAG 9200 may include one or more TRPs corresponding to the first TA 9060. A first time synchronization timer 9800 may be associated with the third TAG 9502. That is, the first time synchronization timer 9800 may be associated with the first subTAG 9200 and the third TAG 9502. A third time synchronization timer 9802 may be associated with the third TAG 9502.

[0359] Based at least on the second TA command 9051, a second time synchronization timer 9801 may be started or restarted. The second time synchronization timer 9801 may be associated with a second TRP 9041. The second time synchronization timer 9801 may be associated with a second subTAG 9201. The second subTAG 9201 may identify the second TRP 9041 from one or more TRPs. Second subTAG 9201 For example, the second subTAG 9201 may include one or more TRPs corresponding to the second TA 9061. The second time synchronization timer 9801 may be associated with the third TAG 9502. That is, the second time synchronization timer 9801 may be associated with the second subTAG 9201 and The first subTAG 9200 and the second subTAG 9201 may correspond to one serving cell 9900.

[0360] The first time synchronization timer 9800 may be different from the second time synchronization timer 9801. That is, the first time synchronization timer 9800 may be independent of the second time synchronization timer 9801. For example, a first upper layer parameter that sets the first time synchronization timer 9800 may be independent of a second upper layer parameter that sets the second time synchronization timer 9801. The entity may manage the first time synchronization timer 9800 and the second time synchronization timer 9801 in parallel.

[0361] The second TA command 9051 may be included in a TA command MAC CE or an absolute TA command MAC CE. For example, the TA command MAC CE or the absolute TA command MAC CE may include a field for specifying either a second TRP 9041 or a second subTAG 9201. That is, the TA command MAC CE includes the TA command, the TAG ID, and the second subTAG 9201. and TRP information for the second TRP 9041. Absolute TA command MAC CE is for TA command, TAG ID and second subTAG 9201 and TRP information for the second TRP 9041. stomach.

[0362] A TA command MAC CE including a first TA command 9050 is received, and the first N TA is held in the first subTAG 9200, the MAC entity may apply the first TA command 9050 A TA command MAC CE including a first TA command 9050 is received, and the first N TA is the If held in one subTAG 9200, the MAC entity may start or restart a first time synchronization timer 9800 associated with the first TA command 9050.

[0363] A TA command MAC CE including a second TA command 9051 is received, and a second N TA is held in the second subTAG 9201, the MAC entity may apply the second TA command 9051 A TA command MAC CE including a second TA command 9051 is received, and a second N TA is the If held in the second subTAG 9201, the MAC entity may start or restart a second time synchronization timer 9801 associated with the second TA command 9051. The MAC entity may manage some or all of the first time synchronization timer 9800, the second time synchronization timer 9801, and the third time synchronization timer 9802.

[0364] When the first time synchronization timer 9800 is stopped (not running), the MAC entity may apply the first TA command 9050 and start the first time synchronization timer 9800. Furthermore, when contention resolution in the first random access 9000 is successful, If the first time synchronization timer 9800 is not successfully completed, the MAC entity stops the first time synchronization timer 9800. When the second time synchronization timer 9801 is stopped (not running), the MAC entity may apply the second TA command 9051 and start the second time synchronization timer 9801. Furthermore, if the contention resolution in the second random access 9001 is not completed successfully, the MAC entity may stop the second time synchronization timer 9801. The time synchronization timer 9800 and the second time synchronization timer 9801 are running simultaneously. Good too.

[0365] If the first random access preamble 9010 is selected from the preambles in the CBRA and if the first time synchronization timer 9800 is running, the MAC entity may ignore the first TA command 9050. If the second random access preamble 9011 is selected from the preambles in the CBRA and if the second time synchronization timer 9801 is running, the MAC entity may ignore the second TA command 9051.

[0366] The first time synchronization timer 9800 and the second time synchronization timer 9801 may correspond to one serving cell 9900. If the first time synchronization timer 9800 or the second time synchronization timer 9801 expires, the MAC entity may flush all HARQ buffers for one serving cell 9900. If the first time synchronization timer 9800 or the second time synchronization timer 9801 expires, the MAC entity may notify RRC to release the PUCCH for one serving cell 9900. If the first time synchronization timer 9800 or the second time synchronization timer 9801 expires, the MAC entity may notify RRC to release the SRS for one serving cell 9900. If the first time synchronization timer 9800 or the second time synchronization timer 9801 expires, the MAC entity may notify RRC to release the configured downlink assignment and the configured uplink grant. The first time synchronization timer 9800 or the second time synchronization timer 9801 may be cleared. If the timer 9801 expires, the MAC entity may clear the PUSCH resources for semi-persistent CSI reporting. If timer 9800 or second time synchronization timer 9801 expires, the MAC entity The property is that all time synchronization timers corresponding to one serving cell 9900 have expired. If the first time synchronization timer 9800 expires, the MAC entity Tee is the first N TA The second time synchronization timer 9801 may expire. If so, the MAC entity TA may be maintained.

[0367] If the first time synchronization timer 9800 is not running (expired), the MAC entity The service shall transmit a first uplink transmission (first uplink physical The second time synchronization timer 9801 is running. If not (expired), the MAC entity shall The second uplink transmission (transmission on the second uplink physical channel 9101) may not be performed. The first uplink transmission and the second uplink transmission may not include one or both of the random access preamble transmission and the message A transmission.

[0368] If the reception of at least the first random access response 9020 is successfully completed, the MAC entity may process the first TA command 9050 for one serving cell 9900. The reception of the first random access response 9020 is considered successful. and a first random access preamble 9010 for one serving cell 9900. and based at least on the transmission of the first TRP 9040, the MAC entity may apply a first TA command 9050 for one or both of the one serving cell 9900 and the first TRP 9040. stomach.

[0369] In order to improve the degree of freedom of terminal positioning, reduce interference, and expand coverage, the terminal device 1 is The problem is to determine uplink timing for each of the multiple transmission and reception points. This problem may be solved by obtaining a second TA. For example, means 1a, means 1b, means 1c, means 2a, and means 2b may be used to obtain the second TA.

[0370] Fig. 10 is a diagram showing examples of means 1a, means 1b, and means 1c according to one aspect of this embodiment, and Fig. 11 is a diagram showing examples of means 2a and means 2b according to one aspect of this embodiment.

[0371] In means 1a, means 1b, means 1c, means 2a, and means 2b, the second TA acquisition may be determining one or both of a first TA 9060 and a second TA 9061 in the serving cell 9900. The second TA acquisition may be executing one or both of a first random access procedure 9000 and a second random access procedure 9001 in the serving cell 9900. The second TA acquisition may be transmitting one or both of a first random access preamble 9010 and a second random access preamble 9011 in the serving cell 9900. The second TA acquisition may be receiving one or both of a first random access response 9020 and a second random access response 9021 in the serving cell 9900. The second TA acquisition may be using one or both of first TRP information 9030 and second TRP information 9031 in the serving cell 9900. The second TA acquisition may be the reception of one or both of a first TA command 9050 and a second TA command 9051 in the serving cell 9900. The second TA acquisition may be the determination or adjustment of one or both of a first uplink timing 9070 and a second uplink timing 9071 in the serving cell 9900. The second TA acquisition may be the determination of one or both of a first uplink frame 9080 and a second uplink frame 9081 in the serving cell 9900. The second TA acquisition may be performed for one or both of a first uplink physical channel 9100 and a second uplink physical channel 9101 in the serving cell 9900. The second TA acquisition may be performed by determining one or both of the first subTAG 9200 and the second subTAG 9201 in the serving cell 9900. The second TA acquisition may be performed based on one or both of the first TAG ID 9300 and the second TAG ID 9301 in the serving cell 9900. The second TA acquisition may be performed based on one or both of the first TAG 9500 and the second TAG 9501 in the serving cell 9900. The second TA acquisition may be performed by operating, starting, or restarting one or both of the first time synchronization timer 9800 and the second time synchronization timer 9801 in the serving cell 9900.

[0372] In means 1a, means 1b, and means 1c, the terminal device 1 may receive a PDCCH 1010. In means 1a, means 1b, and means 1c, the terminal device 1 may receive a PDCCH 1010 to which a DCI 1000 is arranged (mapped). For example, the DCI 1000 may be DCI format 1_0. For example, the PDCCH 1010 may be a PDCCH order.

[0373] In means 1a, means 1b, and means 1c, the terminal device 1 may transmit a random access preamble 1015. For example, in a random access procedure initiated (triggered) by the PDCCH 1010, the terminal device 1 may transmit the random access preamble 1015. The random access procedure initiated by the PDCCH 1010 may be any of a random access procedure 1050, a random access procedure 1051, and a random access procedure 1052. The random access preamble 1015 may be transmitted in a PRACH opportunity 1025.

[0374] In means 1a, means 1b, means 1c, means 2a, and means 2b, some or all of the first upper layer parameter 1040, the second upper layer parameter 1041, and the third upper layer parameter 1042 may include RACH configuration.

[0375] In the means 1a, 1b, 1c, 2a, and 2b, the first upper layer parameter 1040 may be twoTA-Config1-r18. The second upper layer parameter 1041 may be twoTA-Config2-r18. The second upper layer parameter 1041 may be RACH-ConfigCommon. The third upper layer parameter 1042 may be RACH-ConfigCommon. The parameter 1040 may be a dedicated upper layer parameter. The second upper layer parameter 1040 may be a dedicated upper layer parameter. The second upper layer parameter 1041 may be a common upper layer parameter. The third upper layer parameter 1042 may be a common upper layer parameter. The first upper layer parameter 1040 may correspond to one additional PCI index. The second upper layer parameter 1041 and the third upper layer parameter 1042 may be the same common upper layer parameter (e.g., RACH-ConfigCommon).

[0376] twoTA-Config1-r18 may correspond to one additional PCI index. twoTA-Config1-r18 may include one additional PCI index. a first serving cell ID, a first physical cell ID, and a first set of SS / PBCH blocks; twoTA-Config1-r18 may correspond to either a second serving cell ID, a second physical cell ID, and a second set of SS / PBCH blocks. twoTA-Config2-r18 may be used when one cell is configured.

[0377] twoTA-Config1-r18 includes the first TAG information 9030, the first TRP 9040, the first TA 9060, and the first In relation to some or all of the uplink timing 9070, the first uplink frame 9080, the first subTAG 9200, the first TAG ID 9300, the first TAG 9500, and the serving cell 9900, twoTA-Config2-r18 includes second TAG information 9031, second TRP 9041, second TA 9061, The second uplink timing 9071, the second uplink frame 9081, the second subTAG 9201, the second TAG ID 9301, the second TAG 9501, and the ... uplink timing 9071, the second uplink frame 9081, the second uplink timing 9071, the second uplink timing 9071, the second uplink frame 9081, the second uplink timing 9071, the second uplink timing 9071, the second uplink timing 9071, the second uplink timing 9071, the second uplink timing 9071, the second uplink timing 9071, the second It may be connected.

[0378] The means 1a, the means 1b, and the means 1c may initiate a random access procedure 1050 based on the first upper layer parameter 1040. The random access procedure 1051 may be initiated based on the second upper layer parameter 1041. The random access procedure 1052 may be initiated based on the third upper layer parameter 1042. Some or all of the random access procedures 1050, 1051, and 1052 may be the random access procedure 9000. Some or all of the random access procedures 1050, 1051, and 1052 may be the random access procedure 9001. Some or all of the random access procedures 1050, 1051, and 1052 may be initiated to obtain a second TA.

[0379] The means 1a, 1b, and 1c may determine a PRACH opportunity 1025 based on a first higher layer parameter 1040. The PRACH opportunity 1025 may be determined based on a second higher layer parameter 1041. The PRACH opportunity 1025 may be determined based on a third higher layer parameter 1042. The random access preamble 1015 may be determined based on the first higher layer parameter 1040. The random access preamble 1015 may be determined based on the second higher layer parameter 1041. The random access preamble 1015 may be determined based on the third higher layer parameter 1042.

[0380] In the means 1a, the DCI 1000 may include the DCI field 1020. The DCI 1000 may not include the DCI field 1020. The DCI field 1020 may indicate one value. A value may be set in the parameter field 1020. The value may be a first value 1030. The value may be a second value 1031. A value may be associated with one upper layer parameter. The one higher layer parameter may include a RACH configuration. The one higher layer parameter may be a first higher layer parameter 1040. The one higher layer parameter may be a second higher layer parameter 1041. One upper layer parameter may be a third upper layer parameter 1041. It may be the data 1042.

[0381] In the means 1a, if the DCI field 1020 indicates a first value 1030, a first upper layer parameter If the DCI field 1020 indicates a second value 1031, the second If the DCI 1000 does not include the DCI field 1020, a third upper layer parameter 1042 may be used. If the DCI field 1020 indicates the first value 1030, a random access procedure 1050 may be performed based on the first upper layer parameter 1040. If the DCI field 1020 indicates a second value 1031, a second higher layer A random access procedure 1051 may be initiated based on the parameter 1041. If the DCI 1000 does not include the DCI field 1020, a random access procedure 1052 may be initiated based on a third higher layer parameter 1042.

[0382] In the means 1a, if the DCI field 1020 indicates a first value 1030, a first upper layer parameter If the DCI field 1020 indicates a second value 1031, the PRACH opportunity 1025 may be determined based on a second higher layer parameter 1041. If the DCI 1000 does not include the DCI field 1020, the PRACH opportunity 1025 may be determined based on a third higher layer parameter 1042. In the means 1a, if the DCI field 1020 indicates a first value 1030, the random access preamble 1015 may be determined based on a first higher layer parameter 1040. If the DCI field 1020 indicates a second value 1031, , the random access preamble 1015 may be determined based on the second higher layer parameter 1041. If the DCI 1000 does not include the DCI field 1020, the random access preamble 1015 may be determined based on the third higher layer parameter 1042.

[0383] In the method 1a, the first value 1030 and / or the second value 1031 are one additional PCI It may be any of an index (AdditionalPCIIndex), one CORESET pool index (CORESETPoolIndex), first TRP information 9030, second TRP information 9031, first TRP 9040, second TRP 9041, first subTAG 9200, second subTAG 9201, first TAG ID 9300, second TAG ID 9301, first TAG 9500, second TAG 9501, first time synchronization timer 9800, and second time synchronization timer 9801.

[0384] In the means 1a, whether the DCI 1000 includes the DCI field 1020 may be determined based on whether the first upper layer parameter 1040 or the second upper layer parameter 1041 is set. For example, if the first upper layer parameter 1040 is set, the DCI 1000 may include the DCI field 1020. If the first upper layer parameter 1040 is not set, the DCI 1000 may not include the DCI field 1020. For example, if the second upper layer parameter 1041 is set, the DCI 1000 may include the DCI field 1020. If the second upper layer parameter 1041 is not set, the DCI 1000 may not include the DCI field 1020.

[0385] In the means 1b, the DCI 1000 or the PDCCH 1000 may be associated with or correspond to one CORESET pool index. For example, one CORESET pool index may be a first value 1030. One CORESET pool index may be a second value 1031. The first value 1030 may be 1 and the second value 1031 may be 0. The first value 1030 may be 0 and the second value 1031 may be 1.

[0386] In the means 1b, if one CORESET pool index is a first value 1030, a first upper layer parameter 1040 may be used. If one CORESET pool index is a second value 1031, a second upper layer parameter 1041 may be used. If one or both of the first upper layer parameter 1040 and the second upper layer parameter 1041 are not set, a third upper layer parameter 1042 may be used.

[0387] In the means 1b, if one CORESET pool index is a first value 1030, a random access procedure 1050 may be initiated based on a first upper layer parameter 1040. If one CORESET pool index is a second value 1031, a random access procedure 1051 may be initiated based on a second upper layer parameter 1041. If one or both of the first upper layer parameter 1040 and the second upper layer parameter 1041 are not configured, a random access procedure 1052 may be initiated based on a third upper layer parameter 1042.

[0388] In the means 1b, when a CORESET pool index is a first value 1030, a PRACH opportunity 1025 may be determined based on a first higher layer parameter 1040. If the index is a second value 1031, the PRACH opportunity 1025 may be determined based on a second higher layer parameter 1041. If one or both of the parameters 1041 are not set, the PRACH opportunity 1025 may be determined based on a third higher layer parameter 1042. In the means 1b, one CORESET pool index If the CORESET pool index is a first value 1030, the random access preamble 1015 may be determined based on a first higher layer parameter 1040. If a CORESET pool index is a second value 1031, the random access preamble 1015 may be determined based on a second higher layer parameter 1041. If one or both of the first higher layer parameter 1040 and the second higher layer parameter 1041 are not configured, the random access preamble 1015 may be determined based on a third higher layer parameter 1042.

[0389] In the means 1c, if the first upper layer parameter 1040 is set and the third upper layer parameter 1042 is set, the first upper layer parameter 1040 may be used. If the first upper layer parameter 1040 is not set and the third upper layer parameter 1042 is set, the third upper layer parameter 1042 may be used. If the first upper layer parameter 1040 is configured and the third upper layer parameter 1042 is configured, a random access procedure 1050 may be initiated based on the first upper layer parameter 1040. If the first upper layer parameter 1040 is not configured and the third upper layer parameter 1042 is configured, a random access procedure 1052 may be initiated based on the third upper layer parameter 1042. If the first upper layer parameter 1040 is configured and the third upper layer parameter 1042 is configured, a PRACH opportunity 1025 is determined based on the first upper layer parameter 1040. If the first upper layer parameter 1040 is not configured and the third upper layer parameter 1042 is configured, the PRACH opportunity 1025 may be determined based on the third upper layer parameter 1042. If the first upper layer parameter 1040 is configured and the third upper layer parameter 1042 is configured, the PRACH opportunity 1025 may be determined based on the third upper layer parameter 1042. If the upper layer parameter 1042 is configured, the random access preamble 1015 may be determined based on the first upper layer parameter 1040. If the first upper layer parameter 1040 is not configured and the third upper layer parameter 1042 is configured, the random access preamble 1015 may be determined based on the third upper layer parameter 1042.

[0390] In the means 2a and 2b, the terminal device 1 transmits a random access preamble 1115. For example, the terminal device 1 may perform random access in the random access procedure 1150. For example, the terminal device 1 may transmit the random access preamble 1115 in the random access procedure 1151. At opportunity 1125, the terminal device 1 may transmit a random access preamble 1115. The terminal device 1 may receive a random access response 1160. In step 1150, the terminal device 1 may receive a random access response 1160. In the random access procedure 1151, a random access response 1160 may be received. The random access preamble 1115 may be either the random access preamble 9010 or the random access preamble 9011. The random access response 1160 may be either the random access response 9020 or the random access response 9021. The random access preamble 1115 and one of the PRACH opportunities 1125 or Both may be associated with the random access procedure 1150 or the random access procedure 1151. One or both of the random access procedure 1150 and the random access procedure 1151 may be initiated to obtain a second TA.

[0391] In the means 2a and 2b, the first TAG 1170 is a subTAG 9200 and a TAG 9500. The second TAG 1171 may be either the subTAG 9201 or the TAG 9501. The first TAG 1170 may be associated with the TAG ID 9300. The second TAG 1171 may be associated with TAG ID 9301. The first TAG 1170 may be associated with the first time synchronization timer 9800. The second TAG 1170 may correspond to or be associated with the first TRP information 9030. The second TAG 1171 may correspond to or be associated with the second time synchronization timer 9801. The first TAG 1170 may correspond to or be associated with the first TRP information 9030. The second TAG 1171 may correspond to or be associated with the second TPR information 9031.

[0392] In the means 2a and 2b, the random access procedure 1150 performs the following for the first TAG 1170: A random access procedure 1151 may be initiated for the second TAG 1171. In the means 2a and 2b, the random access procedure 1150 and the random access procedure 1151 may be initiated in the RRC or the MAC.

[0393] In the embodiment 2a, the first TAG 1170 and the second TAG 1171 may correspond to the serving cell 9900. In the embodiment 2a, the first TAG 1170 and the second TAG 1171 may correspond to different serving cells. For example, in the embodiment 2a, the first TAG 1170 may be associated with an additional PCI.

[0394] In means 2b, the first TAG 1170 and the second TAG 1171 may correspond to the serving cell 9900.

[0395] In the means 2a and 2b, a random access procedure 1150 may be initiated for the first TAG 1170. A random access procedure 1151 may be initiated for the second TAG 1171. For example, if a time synchronization timer associated with the first TAG 1170 has expired (is not running), If the second TAG 1171 is associated with the random access procedure 1150, the random access procedure 1150 may be initiated. If the inter-synchronization timer has expired (is not running), a random access procedure 1151 may be initiated.

[0396] In the means 2a, when the first upper layer parameter 1040 is set, and the first TAG 1170 is set, If the associated time synchronization timer expires, the random access procedure 1150 may be initiated based on the second higher layer parameter 1041. If the first higher layer parameter 1040 is not configured and the time synchronization timer associated with the first TAG 1170 expires, the random access procedure 1150 may be initiated based on the second higher layer parameter 1041. The system access procedure 1150 may be initiated based on a second higher layer parameter 1041.

[0397] In the means 2a, when the first upper layer parameter 1040 is set, and the second TAG 1171 is set, If the associated time synchronization timer expires, the random access procedure 1151 may be initiated based on the first higher layer parameter 1040. If the first higher layer parameter 1040 is not configured and the time synchronization timer associated with the second TAG 1171 expires, the random access procedure 1151 may be initiated based on the first higher layer parameter 1040. The system access procedure 1151 may be initiated based on the second higher layer parameter 1041. If the first higher layer parameter 1040 is not set and the time synchronization associated with the second TAG 1171 is not set, the system access procedure 1151 may be initiated based on the second higher layer parameter 1041. If the timer expires, the random access procedure 1151 may not be initiated. If the first higher layer parameter 1040 is not configured and the time synchronization associated with the second TAG 1171 If the timer expires, the random access procedure 1151 may not be expected to be initiated.

[0398] In the means 2a, the second upper layer parameter 1041 may be RACH-ConfigCommon or twoTA-Config2-r18. The twoTA-Config2-r18 may provide CFRA resources. RACH-ConfigCommon may provide CBRA resources. The first higher layer parameter 1040 is , twoTA-Config1-r18. twoTA-Config1-r18 may provide CFRA resources. For example, a random access procedure initiated based on one or both of twoTA-Config1-r18 and twoTA-Config2-r18 may be considered as a random access procedure for acquiring a second TA.

[0399] In the means 2b, the second upper layer parameter 1041 may be twoTA-Config2-r18. The three upper layer parameters 1042 may be RACH-ConfigCommon, two TA-Config2-r18 may provide CFRA resources, and RACH-ConfigCommon may provide CBRA resources. The random access procedure initiated based on twoTA-Config2-r18 is used to obtain the second TA. In the means 2b, the random access 1151 may be regarded as a random access procedure for obtaining the second TA.

[0400] In the means 2b, a third upper layer parameter 1042 may be set. When the second upper layer parameter 1041 is set and the time synchronization timer associated with the first TAG 1170 expires, In this case, the random access procedure 1150 may be initiated based on either the second upper layer parameter 1041 or the third upper layer parameter 1042. For example, if the second upper layer parameter 1041 is set and the time synchronization timer associated with the first TAG 1170 expires, In case of expiration, a random access procedure 1150 may be initiated based on the second higher layer parameter 1041 .

[0401] In the means 2b, when the second upper layer parameter 1041 is not set and the first TAG 1170 If a time synchronization timer associated with the UE has expired, a random access procedure 1150 may be initiated based on a third higher layer parameter 1042.

[0402] In the means 2b, when the second upper layer parameter 1041 is set, and the second TAG 1171 is set, If the associated time synchronization timer expires, a random access procedure 1151 may be initiated based on the second higher layer parameter 1041 .

[0403] In the means 2b, when the second upper layer parameter 1041 is not set and the second TAG 1171 If the time synchronization timer associated with the random access procedure 1151 has expired, the random access procedure 1151 may not be initiated.

[0404] The random access procedure 1050, the random access procedure 1051, and the random access procedure 1052 may be a CFRA or a CBRA. The random access procedure 1150 may be a CBRA or a CFRA. The random access procedure 1151 may be a CFRA. The random access procedure 1150 and the random access procedure 1151 may be a random access procedure for acquiring a second TA.

[0405] Various aspects of the device according to one aspect of this embodiment will be described below.

[0406] (1) In order to achieve the above object, the aspects of the present invention provide the following means. That is, a first aspect of the present invention is a terminal device, comprising: a receiver for receiving a PDCCH on which DCI is arranged; a transmitter for transmitting a preamble, wherein if the DCI includes a DCI field and if the DCI field indicates a first value, the transmitter for transmitting a preamble based on a first higher layer parameter When the random access procedure is initiated and the DCI includes the DCI field, and if the DCI field indicates a second value, the random access procedure is initiated based on a second higher layer parameter. When a random access procedure is initiated and the DCI does not include the DCI field, the random access procedure is initiated based on third upper layer parameters, where all of the first upper layer parameters, the second upper layer parameters, and the third upper layer parameters include a RACH configuration, and the first upper layer parameters correspond to one additional PCI index. Also, when the first upper layer parameters are configured, the DCI may include the DCI field. Also, the second upper layer parameters and the third upper layer parameters may be the same common upper layer parameters.

[0407] (2) A second aspect of the present invention is a terminal device, comprising: a receiver for receiving a PDCCH on which DCI is arranged; and a random access control unit for controlling a random access in a random access procedure initiated by the PDCCH. a transmitter unit that transmits a preamble, wherein if a CORESET pool index corresponding to the PDCCH has a first value, the random access procedure is initiated based on a first upper layer parameter, if the CORESET pool index corresponding to the PDCCH has a second value, the random access procedure is initiated based on a second upper layer parameter, and if the first upper layer parameter is not configured, the random access procedure is initiated based on a third upper layer parameter, and all of the first upper layer parameter, the second upper layer parameter, and the third upper layer parameter include a RACH configuration.

[0408] (3) A third aspect of the present invention is a terminal device, comprising: a receiver for receiving a PDCCH on which DCI is arranged; and a random access control unit for controlling a random access in a random access procedure initiated by the PDCCH. and a transmitting unit that transmits a spramble, wherein if a first upper layer parameter is set and a second upper layer parameter is set, the random access procedure is initiated based on the first upper layer parameter, and if the first upper layer parameter is not set and the second upper layer parameter is set, the random access procedure is initiated based on the second upper layer parameter, and the first upper layer parameter and the second upper layer parameter include a RACH configuration.

[0409] (4) A fourth aspect of the present invention is a terminal device, comprising: a transmitter that transmits a random access preamble in a random access procedure; and a receiver that receives a random access response in the random access procedure, wherein when a first upper layer parameter is configured and a first time synchronization timer associated with a first TAG has expired, If the first upper layer parameter is not configured and the first time synchronization timer has expired, the random access procedure is initiated based on the second upper layer parameter; if the first upper layer parameter is configured and the first time synchronization timer has expired, the random access procedure is initiated based on the second upper layer parameter; if the first upper layer parameter is configured and the first time synchronization timer has expired, the random access procedure is initiated based on the second upper layer parameter; if the first upper layer parameter is configured and the first time synchronization timer has expired, the random access procedure is initiated based on the If the second time synchronization timer expires, the random access procedure is initiated based on the first upper layer parameter; if the first upper layer parameter is not configured and the second time synchronization timer expires, the random access procedure is not initiated, and the first upper layer parameter and the second upper layer parameter include RACH configuration. The random access procedure initiated based on the first upper layer parameter may be regarded as a random access procedure for acquiring a second TA. The first TAG is , one additional PCI may be supported.

[0410] (5) A fifth aspect of the present invention is a terminal device, comprising: a transmitter that transmits a random access preamble in a random access procedure; and a receiver that receives a random access response in the random access procedure, wherein a third upper layer parameter is set, a second upper layer parameter is set, and a first TAG associated with the first upper layer parameter is set. If a time synchronization timer has expired, the random access procedure is initiated based on either the second upper layer parameter or the third upper layer parameter; if the second upper layer parameter is not configured and the first time synchronization timer has expired, the random access procedure is initiated based on the third upper layer parameter; if the second upper layer parameter is configured and the second upper layer parameter is configured and the random access procedure is initiated based on the second upper layer parameter associated with the TAG. If a second time synchronization timer set in the second upper layer parameter is expired, the random access procedure is initiated based on the second upper layer parameter, and if the second upper layer parameter is not configured and the second time synchronization timer is expired, the random access procedure is not initiated, the second upper layer parameter and the third upper layer parameter include a RACH configuration, and the first TAG and the second TAG correspond to one serving cell. The random access procedure when the second time synchronization timer is expired may be regarded as a random access procedure for acquiring a second TA.

[0411] (6) A sixth aspect of the present invention is a base station device, comprising: a receiving unit that receives a random access preamble in a random access procedure; and a transmitting unit that transmits a random access response in the random access procedure, wherein a first upper layer parameter is configured and a first time synchronization timer associated with a first TAG has expired. If the first upper layer parameter is not configured and the first time synchronization timer has expired, the random access procedure is initiated based on the second upper layer parameter, if the first upper layer parameter is configured and a second TAG associated with the first upper layer parameter is configured. If a second time synchronization timer has expired, the random access procedure is initiated based on the first upper layer parameter, and if the first upper layer parameter is not configured and the second time synchronization timer has expired, the random access procedure is not initiated, and the first upper layer parameter and the second upper layer parameter include RACH configuration. The random access procedure initiated based on the first upper layer parameter may be regarded as a random access procedure for acquiring a second TA. may accommodate one additional PCI.

[0412] The programs that run on the base station device 3 and terminal device 1 according to the present invention may be programs that control a CPU (Central Processing Unit) or the like (programs that make a computer function) so as to realize the functions of the above-described embodiments according to the present invention. Information handled by these devices is temporarily stored in RAM (Random Access Memory) during processing. The data is then stored in various ROMs such as Flash ROM (Read Only Memory) or HDD (Hard Disk Drive), and is read, modified, and written by the CPU as needed.

[0413] Note that the terminal device 1 and part of the base station device 3 in the above-described embodiment may be realized by a computer. In this case, a program for realizing this control function may be recorded on a computer-readable recording medium, and the program recorded on this recording medium may be read into a computer system and executed to realize the function.

[0414] The term "computer system" used here refers to a computer system built into the terminal device 1 or base station device 3, and includes hardware such as an OS and peripheral devices. Also, the term "computer-readable recording medium" refers to portable media such as flexible disks, optical magnetic disks, ROMs, and CD-ROMs, as well as storage devices such as hard disks built into the computer system.

[0415] Furthermore, the term "computer-readable recording medium" may include a medium that dynamically stores a program for a short period of time, such as a communication line when transmitting a program via a network such as the Internet or a communication line such as a telephone line, or a medium that stores a program for a fixed period of time, such as volatile memory within a computer system that serves as a server or client in such a case. The program may also be one that realizes part of the above-mentioned functions, or one that can realize the above-mentioned functions in combination with a program already stored in the computer system.

[0416] Furthermore, the base station device 3 in the above-described embodiment can also be realized as a collection (device group) consisting of multiple devices. Each of the devices constituting the device group may have some or all of the functions or functional blocks of the base station device 3 according to the above-described embodiment. It is sufficient for the device group to have all of the functions or functional blocks of the base station device 3. Furthermore, the terminal device 1 according to the above-described embodiment can also communicate with the base station device as a collection.

[0417] Furthermore, the base station device 3 in the above-described embodiment may be an EUTRAN (Evolved Universal Terrestrial Radio Access Network) and / or an NG-RAN (NextGen RAN, NR RAN). Furthermore, the base station device 3 in the above-described embodiment may be an eNodeB and / or a gNB. It may have some or all of the functions of its higher-level node.

[0418] Furthermore, some or all of the terminal device 1 and base station device 3 in the above-described embodiments may be realized as an LSI, which is typically an integrated circuit, or may be realized as a chipset. Each functional block of the terminal device 1 and the base station device 3 may be individually integrated into a chip, or part or all of them may be integrated into a chip. The integrated circuit method is not limited to LSI, but may be a dedicated circuit, Alternatively, it may be realized by a general-purpose processor. In addition, with the advancement of semiconductor technology, it is expected that LSI will replace the general-purpose processor. When integrated circuit technology emerges, it is also possible to use integrated circuits based on that technology.

[0419] Furthermore, in the above-described embodiment, a terminal device is described as an example of a communication device, but the present invention is not limited to this and can also be applied to terminal devices or communication devices such as stationary or non-movable electronic devices installed indoors or outdoors, for example, AV equipment, kitchen equipment, cleaning / washing equipment, air conditioning equipment, office equipment, vending machines, and other household appliances.

[0420] Although the embodiments of the present invention have been described in detail above with reference to the drawings, the specific configuration is not limited to this embodiment and includes design modifications within the scope of the invention. Furthermore, the present invention is susceptible to various modifications within the scope of the claims, and embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of the present invention. Furthermore, configurations in which elements described in the above embodiments are substituted with elements that achieve the same effect are also included. [Explanation of symbols]

[0421] 1(1A, 1B, 1C) Terminal equipment 3 Base station equipment 10, 30 Radio transmitter / receiver 10a, 30a Radio transmitter 10b, 30b Wireless receiver 11, 31 Antenna section 12, 32 RF section 13, 33 Baseband section 14, 34 Upper layer processing unit 15, 35 Medium access control layer processing unit 16, 36 Radio resource control layer processing unit 91, 92, 93, 94 Search area set 300 Component Carriers 301 Primary Cell 302, 303 Secondary Cell 700 Set of resource elements for PSS 710, 711, 712, 713 Set of resource elements for PBCH and DMRS for PBCH 720 Set of Resource Elements for SSS 3000 points 3001, 3002 Resource Grid 3003, 3004 BWP 3011, 3012, 3013, 3014 offset 3100, 3200 common resource block set 9000, 9001 Random Access (Random Access Procedure) 9010, 9011 Random Access Preamble 9020, 9021 Random Access Response 9030, 9031 TRP information 9040, 9041 TRP 9050, 9051 TA Command 9060, 9061 TA 9070, 9071 Uplink Timing 9080, 9081 Uplink Frame 9082 Downlink Frame 9090 specified time 9100, 9101 Uplink Physical Channels 9200, 9201 subTAG 9300, 9301 TAG ID 9400, 9401 TA offset 9500, 9501, 9502 TAG 9800, 9801, 9802 Time Synchronization Timer 9900 serving cells 1000 DCI 1010 PDCCH 1015, 1115 Random Access Preamble 1020 DCI Field 10:25, 11:25 PRACH Opportunities 1030, 1031 values 1040, 1041, 1042 Upper layer parameters 1050, 1051, 1052, 1150, 1151 Random Access Procedure 1160 Random Access Response 1170, 1171 TAG

Claims

1. a receiving unit for receiving a PDCCH in which DCI is arranged; In the random access procedure initiated by the PDCCH, a transmitter for transmitting an amble; If the DCI includes a DCI field, and the DCI field indicates a first value, the random access procedure is initiated based on a first higher layer parameter; If the DCI includes the DCI field, and the DCI field indicates a second value, if so, the random access procedure is initiated based on second higher layer parameters; If the DCI does not include the DCI field, the random access procedure is initiated based on a third higher layer parameter; all of the first upper layer parameter, the second upper layer parameter, and the third upper layer parameter include a RACH configuration; The first upper layer parameter corresponds to one additional PCI index. Terminal device.

2. If the first higher layer parameter is configured, the DCI includes the DCI field. The terminal device according to claim 1 .

3. The second upper layer parameter and the third upper layer parameter are the same common upper layer parameter. The terminal device according to claim 1 .

4. a receiving unit for receiving a PDCCH in which DCI is arranged; In the random access procedure initiated by the PDCCH, a transmitter for transmitting an amble; If a CORESET pool index corresponding to the PDCCH is a first value, the random access procedure is initiated based on a first higher layer parameter; If a CORESET pool index corresponding to the PDCCH is a second value, the random access procedure is initiated based on second higher layer parameters; if the first higher layer parameter is not configured, initiating the random access procedure based on a third higher layer parameter; The first upper layer parameter, the second upper layer parameter, and the third upper layer parameter all include a RACH configuration. Terminal device.

5. a receiving unit for receiving a PDCCH in which DCI is arranged; In the random access procedure initiated by the PDCCH, a transmitter for transmitting an amble; if a first upper layer parameter is configured and if a second upper layer parameter is configured, initiating the random access procedure based on the first upper layer parameter; if the first upper layer parameter is not configured and the second upper layer parameter is configured, initiating the random access procedure based on the second upper layer parameter; The first upper layer parameter and the second upper layer parameter include a RACH configuration. Terminal device.

Images