Terminal device, base station device, and communication method
By employing multiple random access preambles and timing advance commands, the solution optimizes uplink timing and synchronization in cellular networks, addressing inefficiencies and enhancing communication efficiency.
Patent Information
- Application Number
- CN202380033178.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-04-13
- Filing Date
- 2023-04-13
- Publication Date
- 2024-12-03
AI Technical Summary
Existing wireless communication systems face inefficiencies in managing uplink timing adjustments and time synchronization in cellular networks, particularly in scenarios involving multiple service cells and random access processes, which affect communication efficiency.
The proposed solution involves a terminal device and base station device that utilize multiple random access preambles and timing advance commands to adjust uplink timings and synchronize time synchronization timers, with the media access control layer refreshing HARQ buffers when timers expire, thereby optimizing communication methods.
This approach enhances communication efficiency by improving uplink timing management and synchronization, leading to more effective data transmission and reception in cellular networks.
Smart Images

Figure CN119072973A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to a terminal device, a base station device and a communication method. This application claims priority to Japanese Patent Application No. 2022-66025 filed in Japan on April 13, 2022, and the contents are incorporated herein by reference. Background Art
[0002] In the Third Generation Partnership Project (3GPP: rd In the LTE (Global Network Operations Framework) project (a registered trademark), wireless access methods and wireless networks (hereinafter also referred to as "Long Term Evolution (LTE)" or "Evolved Universal Terrestrial Radio Access (EUTRA)") for cellular mobile communications were studied. In LTE, the base station device is also called eNodeB (evolved NodeB), and the terminal device is also called UE (User Equipment). LTE is a cellular communication system that covers an area with multiple base station devices configured in a cell shape. A single base station device can manage multiple service cells.
[0003] In 3GPP, the next generation standard (NR: New Radio) was studied in order to make recommendations to IMT (International Mobile Telecommunication)-2020, which is the next generation mobile communication system standard established by the International Telecommunication Union (ITU) (Non-patent document 1). NR is required to meet the requirements of the following three scenarios in a single technical framework: eMBB (enhanced Mobile BroadBand), mMTC (massive Machine Type Communication), and URLLC (Ultra Reliable and Low Latency Communication).
[0004] In 3GPP, research is being conducted on the extension of services supported by NR (Non-Patent Document 2). Prior art literature 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 that the invention aims to solve
[0006] The present invention provides a terminal device that efficiently communicates, a communication method used for the terminal device, a base station device that efficiently communicates, and a communication method used for the base station device. Technical Solution
[0007] (1) A first scheme of the present invention is a terminal device, comprising: a sending unit, which sends a first random access preamble in a first random access and sends a second random access preamble in a second random access; and a receiving unit, which receives a first TA command in the first random access and receives a second TA command in the second random access, adjusts a first uplink timing in a service cell based at least on the first TA command, adjusts a second uplink timing in the service cell based at least on the second TA command, and uses one of the first uplink timing and the second uplink timing based on certain information.
[0008] (2) In addition, a second scheme of the present invention is a base station device, comprising: a receiving unit, which receives a first random access preamble in a first random access and receives a second random access preamble in a second random access; and a sending unit, which sends a first TA command in the first random access and sends a second TA command in the second random access, adjusts a first uplink timing in a service cell at least based on the first TA command, adjusts a second uplink timing in the one service cell at least based on the second TA command, and uses one of the first uplink timing and the second uplink timing based on certain information.
[0009] (3) In addition, the third scheme of the present invention is a communication method for a terminal device, comprising the following steps: sending a first random access preamble in a first random access, and sending a second random access preamble in a second random access; and receiving a first TA command in the first random access, and receiving a second TA command in the second random access, adjusting a first uplink timing in a service cell at least based on the first TA command, and adjusting a second uplink timing in the one service cell at least based on the second TA command, and using one of the first uplink timing and the second uplink timing based on certain information.
[0010] (4) In addition, a fourth scheme of the present invention is a communication method for a base station device, comprising the following steps: receiving a first random access preamble in a first random access, and receiving a second random access preamble in a second random access; and sending a first TA command in the first random access, and sending a second TA command in the second random access, adjusting a first uplink timing in a service cell at least based on the first TA command, and adjusting a second uplink timing in the one service cell at least based on the second TA command, and using one of the first uplink timing and the second uplink timing based on certain information.
[0011] (5) The fifth scheme of the present invention is a terminal device, comprising: a wireless resource control layer processing unit, which sets a first time synchronization timer and a second time synchronization timer for a service cell; and a media access control layer processing unit, which starts or restarts the first time synchronization timer at least based on receiving a first TA command, and starts or restarts the second time synchronization timer at least based on receiving a second TA command, and when the first time synchronization timer or the second time synchronization timer expires, the media access control layer processing unit refreshes all HARQ buffers used for the one service cell.
[0012] (6) In addition, the sixth scheme of the present invention is a base station device, comprising: a wireless resource control layer processing unit, which sets a first time synchronization timer and a second time synchronization timer for a service cell; and a media access control layer processing unit, which starts or restarts the first time synchronization timer at least based on receiving a first TA command, and the media access control layer processing unit starts or restarts the second time synchronization timer at least based on receiving a second TA command, and when the first time synchronization timer or the second time synchronization timer expires, the media access control layer processing unit refreshes all HARQ buffers used for the one service cell.
[0013] (7) In addition, the seventh scheme of the present invention is a communication method for a terminal device, comprising: a first step, in a wireless resource control layer processing unit, setting a first time synchronization timer and a second time synchronization timer for a service cell; and a second step in a media access control layer processing unit, in which the media access control layer processing unit starts or restarts the first time synchronization timer at least based on receiving a first TA command, and in which the media access control layer processing unit starts or restarts the second time synchronization timer at least based on receiving a second TA command, and in which the media access control layer processing unit refreshes all HARQ buffers for the one service cell when the first time synchronization timer or the second time synchronization timer expires.
[0014] (8) In addition, the eighth scheme of the present invention is a communication method for a base station device, comprising: a first step, in a wireless resource control layer processing unit, setting a first time synchronization timer and a second time synchronization timer for a service cell; and a second step in a media access control layer processing unit, in which the media access control layer processing unit starts or restarts the first time synchronization timer at least based on receiving a first TA command, and in which the media access control layer processing unit starts or restarts the second time synchronization timer at least based on receiving a second TA command, and in which the media access control layer processing unit refreshes all HARQ buffers for the one service cell when the first time synchronization timer or the second time synchronization timer expires. Beneficial Effects
[0015] According to the present invention, a terminal device can efficiently communicate. In addition, a base station device can efficiently communicate. BRIEF DESCRIPTION OF THE DRAWINGS
[0016] Figure 1 This is a conceptual diagram of a wireless communication system according to one aspect of the present embodiment. Figure 2 is a subcarrier spacing setting μ, the number of OFDM symbols per time slot N, and slot symb And an example of the relationship between CP (cyclic prefix) settings. Figure 3 This is a diagram showing an example of a resource grid configuration method according to one aspect of the present embodiment. Figure 4 This is a diagram showing a configuration example of a resource grid 3001 according to one aspect of the present embodiment. Figure 5 It is a schematic block diagram showing a configuration example of the base station device 3 according to one aspect of the present embodiment. Figure 6 It is a schematic block diagram showing a configuration example of the terminal device 1 according to one aspect of the present embodiment. Figure 7 This is a diagram showing an example configuration of an SS / PBCH block according to one scenario of the present embodiment. Figure 8 This is a diagram showing an example of monitoring opportunities of a search area set according to one scenario of the present embodiment. Fig. 9 This is a diagram showing an example of transmission of two uplink channels in one serving cell according to one scheme of the present embodiment. DETAILED DESCRIPTION
[0017] Hereinafter, embodiments of the present invention will be described.
[0018] floor(C) may be a floor function for a real number C. For example, floor(C) may be a function that outputs the largest integer within a range not exceeding the real number C. ceil(D) may be a ceiling function for a real number D. For example, ceil(D) may be a function that outputs the smallest integer within a range not less than D. mod(E,F) may be a function that outputs the remainder obtained by dividing E by F. mod(E,F) may also be a function that outputs a value corresponding to the remainder obtained by dividing E by F. exp(G) = e^G. Here, e is the Napier number. H^I represents H raised to the power of I. max(J,K) is a function that outputs the maximum value between J and K. Here, when 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 minimum value between L and M. Here, when 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.
[0019] In a wireless communication system of one scheme of the present embodiment, at least OFDM (Orthogonal Frequency Division Multiplex) is used. OFDM symbol is the unit of time domain of OFDM. OFDM symbol includes at least one or more subcarriers. OFDM symbol is converted into a time-continuous signal in baseband signal generation. At least CP-OFDM (Cyclic Prefix-Orthogonal Frequency Division Multiplex) is used in the downlink. In the uplink, either CP-OFDM or DFT-s-OFDM (Discrete Fourier Transform-spread-Orthogonal FrequencyDivision Multiplex) is used. DFT-s-OFDM can be given by applying transform precoding to CP-OFDM.
[0020] The OFDM symbol may be a name including the CP added to the OFDM symbol. That is, a certain OFDM symbol may be constructed to include the certain OFDM symbol and the CP added to the certain OFDM symbol.
[0021] Figure 1 FIG. 1 is a conceptual diagram of a wireless communication system according to one embodiment of the present invention. Figure 1 In the wireless communication system, 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 are also referred to as terminal device 1 (UE#1: User Equipment #1).
[0022] The base station device 3 may be configured to include one or more transmission devices (or transmission points, transceivers, transceiver points). In the case where the base station device 3 is composed of multiple transmission devices, the multiple transmission devices may be respectively configured at different positions. For example, the base station device 3 may be composed of a transmission device 3a and a transmission device 3b. For example, the base station device 3 may also be composed of a transceiver point 3a and a transceiver point 3b. For example, the base station device 3 may also be composed of a transceiver 3a and a transceiver 3b.
[0023] The base station device 3 may provide one or more serving cells. A serving cell may be defined as a collection of resources used for wireless communication. In addition, a serving cell is also referred to as a cell.
[0024] The serving cell may be configured to include one or both of a downlink component carrier (downlink carrier) and an uplink component carrier (uplink carrier). The serving cell may also be configured to include one or both of more than two downlink component carriers and more than two uplink component carriers. The downlink component carrier and the uplink component carrier are collectively referred to as component carriers (carriers).
[0025] For example, one resource grid may be provided for each component carrier. In addition, one resource grid may be provided for each set of a component carrier and a subcarrier spacing configuration μ. Here, the subcarrier spacing configuration μ is also referred to as a numerology. For example, one resource grid may be provided for a set of an antenna port p, a subcarrier spacing configuration μ, and a transmission direction x.
[0026] The resource grid includes N size,μ grid,x N RB sc Here, the resource grid is composed of a common resource block N start,μ grid,x In addition, the public resource block N start,μ grid,x Also called the reference point of the resource grid.
[0027] The resource grid includes N subframe,μ symb OFDM symbols.
[0028] The subscript x added to the parameter associated with the resource grid indicates the transmission direction. For example, the subscript x may be used to indicate either a downlink or an uplink.
[0029] N size,μ grid,x The offset setting is indicated by the parameter provided by the RRC layer (for example, the parameter CarrierBandwidth). start,μ grid,x The bandwidth setting is represented by a parameter (e.g., parameter OffsetToCarrier) provided by the RRC layer. The offset setting and the bandwidth setting are settings for configuring an SCS-specific carrier.
[0030] For a certain subcarrier spacing setting μ, the subcarrier spacing (SCS: SubCarrier Spacing) Δf can be Δf=2 μ· 15 kHz. Here, the subcarrier spacing setting μ can represent any one of 0, 1, 2, 3, or 4.
[0031] Figure 2 is a setting μ of the subcarrier spacing and the number N of OFDM symbols per time slot according to one embodiment of the present invention. slot symb And an example of the relationship between CP (cyclic prefix) settings. Figure 2 In A, for example, when the subcarrier spacing μ is set to 2 and the CP is set to a normal cyclic prefix (CP), N slot symb =14, N frame,μ slot =40, N subframe,μ slot =4. In addition, Figure 2 In B, for example, when the subcarrier spacing μ is set to 2 and the CP is set to an extended CP (extended cyclic prefix), N slot symb =12, N frame,μ slot =40, N subframe,μ slot =4.
[0032] Time unit (time unit) T c Can be used to indicate the length of the time domain. Time unit T c It is T c =1 / (Δf max ·N f ). Δf max =480kHz. f =4096. The constant κ is κ = Δf max ·N f / (Δf ref N f,ref )=64. Δf ref is 15kHz. f,ref It is 2048.
[0033] The transmission of the signal in the downlink and / or the transmission of the signal in the uplink may be performed by a transmission of length T f The wireless frames (system frames, frames) are organized into (organized into). f =(Δf max N f / 100)·T s = 10ms. The radio frame consists of 10 subframes. The length of the subframe is Tsf =(Δf max N f / 1000)·T s =1ms. The number of OFDM symbols in each subframe is N subframe,μ symb =N slot symb N subframe,μ slot .
[0034] In one carrier, there is a first set of one or more frames in uplink, and there is a second set of one or more frames in downlink. The uplink frame for transmission from the terminal device 1 is T before the start of the downlink frame. TA Start. TA It can be (N TA ·N TA,offset )T c .
[0035] The OFDM symbol is a unit of the time domain of a communication method. For example, the OFDM symbol can be a unit of the time domain of CP-OFDM. In addition, the OFDM symbol can be a unit of the time domain of DFT-s-OFDM.
[0036] A time slot can be constructed to include multiple OFDM symbols. For example, a time slot can be composed of N consecutive OFDM symbols. slot symb OFDM symbols. For example, in a conventional CP setting, it can be N slot symb =14. In addition, in the conventional CP setting, N slot symb =12.
[0037] The number and index of the time slots included in the subframe can be given for setting μ for a certain subcarrier spacing. For example, the time slot index n μ s In the subframe, it can be subframe,μ slot -1 are given in ascending order. The number and index of the time slots included in the radio frame can also be given for setting the subcarrier spacing μ. In addition, the time slot index n μ s,f It can also be in the wireless frame from 0 to N frame,μ slot Integer values in the range -1 are given in ascending order.
[0038] Figure 3 This is a diagram showing an example of a method of configuring a resource grid according to one aspect of the present embodiment. Figure 3 The horizontal axis represents the frequency domain. Figure 3 , an example of a resource grid configuration of a subcarrier spacing μ1 in component carrier 300 and an example of a resource grid configuration of a subcarrier spacing μ2 in a certain component carrier are shown. In this way, one or more subcarrier spacings can be set for a certain component carrier. Figure 3 In the example, it is assumed that μ1=μ2-1, but the various aspects of the present embodiment are not limited to the condition of μ1=μ2-1.
[0039] Component carrier 300 is a frequency band having a predetermined width in the frequency domain.
[0040] Point 3000 is an identifier for identifying a certain subcarrier. Point 3000 is also referred to as point A. Common resource block (CRB) set 3100 is a set of common resource blocks for the subcarrier spacing setting μ1.
[0041] The common resource block set 3100 includes the common resource blocks of point 3000 ( Figure 3 The black monochrome block in the common resource block set 3100 in FIG. 3 is also referred to as a reference point of the common resource block set 3100 . The reference point of the common resource block set 3100 may also be a common resource block with index 0 in the common resource block set 3100 .
[0042] Offset 3011 is the offset from the reference point of common resource block set 3100 to the reference point of resource grid 3001. Offset 3011 is represented by the number of common resource blocks for the setting μ1 of subcarrier spacing. Resource grid 3001 includes N starting from the reference point of resource grid 3001. size,μ grid1,x A common resource block.
[0043] The offset 3013 is the distance from the reference point of the resource grid 3001 to the reference point (N) of the BWP (BandWidth Part) 3003 of the index i1. start,μ BWP,i1 ) offset.
[0044] The common resource block set 3200 is a set of common resource blocks for the subcarrier spacing setting μ2.
[0045] The common resource block set 3200 includes the common resource blocks of point 3000 ( Figure 3 The black monochrome 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 also be the common resource block of index 0 in the common resource block set 3200.
[0046] Offset 3012 is an offset from a reference point of common resource block set 3200 to a reference point of resource grid 3002. Offset 3012 is represented by the number of common resource blocks for subcarrier spacing μ2. Resource grid 3002 includes N size,μ grid2,x A common resource block.
[0047] 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 ) offset.
[0048] Figure 4 FIG. 3 is a diagram showing an example of the configuration of a resource grid 3001 according to one embodiment of the present invention. Figure 4 In the resource grid, the horizontal axis is the OFDM symbol index l sym , the vertical axis is the subcarrier index k sc The resource grid 3001 includes N size,μ grid1,x N RB sc subcarriers, including N subframe,μ symb OFDM symbols. Within the resource grid, subcarrier index k sc and OFDM symbol index l sym The identified resource is called a resource element (RE: Resource Element).
[0049] Resource Block (RB) includes N RB sc A resource block is a general term for a common resource block, a physical resource block (PRB) and a virtual resource block (VRB). RB SC =12.
[0050] The resource block unit is a set of resources corresponding to one OFDM symbol in one resource block. That is, one resource block unit includes 12 resource elements corresponding to one OFDM symbol in one resource block.
[0051] The common resource blocks for a certain subcarrier spacing setting μ are indexed in ascending order starting from 0 in the frequency domain in a certain common resource block set. The common resource blocks with index 0 for a certain subcarrier spacing setting μ include (or contend for, or agree on) point 3000. The index n of the common resource blocks for a certain subcarrier spacing setting μ isμ CRB Satisfy n μ CRB =ceil(k sc / N RB sc ). Here, k sc The subcarrier with =0 is a subcarrier having the same center frequency as the center frequency of the subcarrier corresponding to point 3000.
[0052] The physical resource blocks for a certain subcarrier spacing setting μ are indexed in ascending order starting from 0 in the frequency domain in a certain BWP. The index n of the physical resource block for a certain subcarrier spacing setting μ is μ PRB Satisfy n μ CRB =n μ PRB +N start ,μ BWP,i Here, N start,μ BWP,i Represents the reference point of the BWP with index i.
[0053] BWP is defined as a subset of common resource blocks included in a resource grid. BWP includes a reference point N from the BWP. start,μ BWP,i Starting N size,μ BWP,i Common resource blocks. The BWP set for a downlink carrier is also called a downlink BWP. The BWP set for an uplink component carrier is also called an uplink BWP.
[0054] An antenna port may be defined as follows: 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. In addition, a symbol may correspond to an OFDM symbol. In addition, a symbol may correspond to a resource block unit. In addition, a symbol may correspond to a resource element.
[0055] The large-scale property of the channel that transmits symbols in one antenna port can be estimated based on the channel that transmits symbols in another antenna port, which is called the two antenna ports being QCL (Quasi Co-Located). Here, the large-scale property may include at least the long-term property of the channel. The large-scale property may also include at least a part or all of delay spread, Doppler spread, Doppler shift, average gain, average delay, and beam parameters (spatial Rx parameters). The beam parameters of the first antenna port and the second antenna port being QCL may be that the receiving beam assumed by the receiving side for the first antenna port and the receiving beam assumed by the receiving side for the second antenna port are the same (or corresponding). The beam parameters of the first antenna port and the second antenna port being QCL may also be that the transmitting beam assumed by the receiving side for the first antenna port and the transmitting beam assumed by the receiving side for the second antenna port are the same (or corresponding). Terminal device 1 may assume that the two antenna ports are QCL when the large-scale characteristics of the channel that transmits symbols at one antenna port can be estimated from the channel that transmits symbols at the other antenna port. The two antenna ports may be QCL, which may also mean assuming that the two antenna ports are QCL.
[0056] Carrier aggregation may be the use of multiple aggregated service cells for communication. In addition, carrier aggregation may also be the use of multiple aggregated component carriers for communication. In addition, carrier aggregation may also be the use of multiple aggregated downlink component carriers for communication. In addition, carrier aggregation may also be the use of multiple aggregated uplink component carriers for communication.
[0057] Figure 5 1 is a schematic block diagram showing an example of the configuration of a base station device 3 according to one embodiment of the present invention. Figure 5 As shown, the base station device 3 includes at least a part or all of a wireless transceiver unit (physical layer processing unit) 30 and / or an upper layer (Higher layer) processing unit 34. The wireless transceiver unit 30 includes at least an antenna unit 31, an RF (Radio Frequency) unit 32, and a part or all of a baseband unit 33. The upper layer processing unit 34 includes at least a part or all of a media access control layer processing unit 35 and a radio resource control (RRC: Radio Resource Control) layer processing unit 36.
[0058] The wireless transceiver unit 30 includes at least a part or all of the wireless transmission unit 30a and the wireless reception unit 30b. Here, the device configuration of the baseband unit included in the wireless transmission unit 30a and the baseband unit included in the wireless reception unit 30b may be the same or different. In addition, the device configuration of the RF unit included in the wireless transmission unit 30a and the RF unit included in the wireless reception unit 30b may be the same or different. In addition, the device configuration of the antenna unit included in the wireless transmission unit 30a and the antenna unit included in the wireless reception unit 30b may be the same or different.
[0059] For example, the wireless transmission unit 30a may generate and transmit a baseband signal of the PDSCH. For example, the wireless transmission unit 30a may generate and transmit a baseband signal of the PDCCH. For example, the wireless transmission unit 30a may generate and transmit a baseband signal of the PBCH. For example, the wireless transmission unit 30a may generate and transmit a baseband signal of a synchronization signal. For example, the wireless transmission unit 30a may generate and transmit a baseband signal of a PDSCH DMRS. For example, the wireless transmission unit 30a may generate and transmit a baseband signal of a PDCCH DMRS. For example, the wireless transmission unit 30a may generate and transmit a baseband signal of a CSI-RS. For example, the wireless transmission unit 30a may generate and transmit a baseband signal of a DL PTRS.
[0060] For example, the wireless receiving unit 30b may receive PRACH. For example, the wireless receiving unit 30b may also receive and demodulate PUCCH. The wireless receiving unit 30b may also receive and demodulate PUSCH. For example, the wireless receiving unit 30b may also receive PUCCH DMRS. For example, the wireless receiving unit 30b may also receive PUSCH DMRS. For example, the wireless receiving unit 30b may also receive ULPTRS. For example, the wireless receiving unit 30b may also receive SRS.
[0061] The upper layer processing unit 34 outputs the downlink data (transmission block) to the wireless transceiver unit 30 (or the wireless transmission unit 30a). The upper layer processing unit 34 performs processing on the MAC (Medium Access Control) layer, the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer, and the RRC layer.
[0062] The media 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.
[0063] The radio resource control layer processing unit 36 included in the upper layer processing unit 34 performs RRC layer processing. The radio resource control layer processing unit 36 manages various setting information / parameters (RRC parameters) of the terminal device 1. The radio resource control layer processing unit 36 sets the RRC parameters based on the RRC message received from the terminal device 1.
[0064] The wireless transceiver 30 (or the wireless transmission unit 30a) performs modulation, coding and other processing. The wireless transceiver 30 (or the wireless transmission unit 30a) generates a physical signal by modulating, coding and generating a baseband signal (converting into a time-continuous signal) the downlink data, and transmits it to the terminal device 1. The wireless transceiver 30 (or the wireless transmission unit 30a) can configure the physical signal to a component carrier and transmit it to the terminal device 1.
[0065] The wireless transceiver 30 (or wireless receiving unit 30b) performs demodulation, decoding and other processing. The wireless transceiver 30 (or wireless receiving unit 30b) separates, demodulates and decodes the received physical signal, and outputs the decoded information to the upper layer processing unit 34. The wireless transceiver 30 (or wireless receiving unit 30b) can implement a channel access process before sending the physical signal.
[0066] The RF unit 32 converts (down converts) the signal received via the antenna unit 31 into a baseband signal by orthogonal demodulation, and removes unnecessary frequency components. The RF unit 32 outputs the processed analog signal to the baseband unit.
[0067] The baseband unit 33 converts the analog signal input from the RF unit 32 into a digital signal. The baseband unit 33 removes a portion corresponding to the CP (Cyclic Prefix) from the converted digital signal, performs a fast Fourier transform (FFT) on the signal after the CP is removed, and extracts a signal in the frequency domain.
[0068] 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 to generate 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.
[0069] The RF unit 32 uses a low-pass filter to remove unnecessary frequency components from the analog signal input from the baseband unit 33, up-converts the analog signal to a carrier frequency, and transmits it via the antenna unit 31. In addition, the RF unit 32 may also have a function of controlling the transmission power. The RF unit 32 is also called a transmission power control unit.
[0070] One or more serving cells (or component carriers, downlink component carriers, uplink component carriers) may be configured for the terminal device 1 .
[0071] Each serving cell configured for the terminal device 1 may be any one of a PCell (Primary cell), a PSCell (Primary SCG cell), and a SCell (Secondary Cell). The SpCell may be one or both of a PCell and a PSCell.
[0072] The PCell is a serving cell included in the MCG (Master Cell Group). The PCell is a cell in which the terminal device 1 performs an initial connection establishment procedure or a connection re-establishment procedure (an already performed cell).
[0073] The PSCell is a serving cell included in an SCG (Secondary Cell Group) and is a serving cell to which the terminal device 1 performs random access.
[0074] The SCell may be included in either the MCG or the SCG.
[0075] A serving cell group (cell group) is a term that includes at least an MCG and an SCG. A serving cell group may include one or more serving cells (or component carriers). One or more serving cells (or component carriers) included in a serving cell group may be used through carrier aggregation.
[0076] One or more downlink BWPs may be configured for each serving cell (or downlink component carrier). One or more uplink BWPs may be configured for each serving cell (or uplink component carrier).
[0077] One of the one or more downlink BWPs set for the serving cell (or downlink component carrier) may be set as an activated downlink BWP (or one downlink BWP may be activated). One of the one or more uplink BWPs set for the serving cell (or uplink component carrier) may be set as an activated uplink BWP (or one uplink BWP may be activated).
[0078] PDSCH, PDCCH and CSI-RS can be received in the activated downlink BWP. Terminal device 1 can attempt to receive PDSCH, PDCCH and CSI-RS in the activated downlink BWP. PUCCH and PUSCH can be sent in the activated uplink BWP. Terminal device 1 can send PUCCH and PUSCH in the activated uplink BWP. The activated downlink BWP and the activated uplink BWP are collectively referred to as the activated BWP.
[0079] PDSCH, PDCCH and CSI-RS may not be received in a downlink BWP other than the activated downlink BWP (inactivated downlink BWP). Terminal device 1 may also attempt to receive PDSCH, PDCCH and CSI-RS in a downlink BWP that is not an activated downlink BWP. PUCCH and PUSCH may not be sent in an uplink BWP that is not an activated uplink BWP (inactivated uplink BWP). Terminal device 1 may not send PUCCH and PUSCH in an uplink BWP that is not an activated uplink BWP. Inactivated downlink BWP and inactivated uplink BWP are collectively referred to as inactivated BWP.
[0080] Downlink BWP switching is a process for deactivating an activated downlink BWP of a certain serving cell and activating any one of the inactivated downlink BWPs of the certain serving cell. Downlink BWP switching can be controlled by the BWP field included in the downlink control information. Downlink BWP switching can also be controlled based on upper layer parameters.
[0081] The uplink BWP switching is used to deactivate an activated uplink BWP and activate any of the inactivated uplink BWPs that are not the activated uplink BWP. The uplink BWP switching can be controlled by the BWP field included in the downlink control information. The uplink BWP switching can also be controlled based on the parameters of the upper layer.
[0082] Two or more downlink BWPs among one or more downlink BWPs set for the serving cell may not be set as the activated downlink BWPs. Alternatively, one downlink BWP may be activated for the serving cell at a certain time.
[0083] Two or more uplink BWPs among one or more uplink BWPs configured for the serving cell may not be configured as activated uplink BWPs. One uplink BWP may be activated for the serving cell at a certain time.
[0084] Figure 6 1 is a schematic block diagram showing an example of the configuration of a terminal device 1 according to one embodiment of the present invention. Figure 6 As shown, the terminal device 1 includes at least one or all of a wireless transceiver unit (physical layer processing unit) 10 and an upper layer processing unit 14. The wireless transceiver unit 10 includes at least a part or all of an antenna unit 11, an RF unit 12, and a baseband unit 13. The upper layer processing unit 14 includes at least a part or all of a media access control layer processing unit 15 and a wireless resource control layer processing unit 16.
[0085] The wireless transceiver 10 includes at least a part or all of a wireless transmitting unit 10a and a wireless receiving unit 10b. Here, the device configuration of the baseband unit 13 included in the wireless transmitting unit 10a and the baseband unit 13 included in the wireless receiving unit 10b may be the same or different. In addition, the device configuration of the RF unit 12 included in the wireless transmitting unit 10a and the RF unit 12 included in the wireless receiving unit 10b may be the same or different. In addition, the device configuration of the antenna unit 11 included in the wireless transmitting unit 10a and the antenna unit 11 included in the wireless receiving unit 10b may be the same or different.
[0086] For example, the wireless transmission unit 10a may generate and transmit a baseband signal of PRACH. For example, the wireless transmission unit 10a may generate and transmit a baseband signal of PUCCH. For example, the wireless transmission unit 10a may generate and transmit a baseband signal of PUSCH. For example, the wireless transmission unit 10a may generate and transmit a baseband signal of PUCCH DMRS. For example, the wireless transmission unit 10a may generate and transmit a baseband signal of PUSCH DMRS. For example, the wireless transmission unit 10a may generate and transmit a baseband signal of ULPTRS. For example, the wireless transmission unit 10a may generate and transmit a baseband signal of SRS. Generating a baseband signal of SRS may be generating an SRS sequence.
[0087] For example, the wireless receiving unit 10b may receive and demodulate the PDSCH. For example, the wireless receiving unit 10b may receive and demodulate the PDCCH. For example, the wireless receiving unit 10b may receive and demodulate the PBCH. For example, the wireless receiving unit 10b may receive a synchronization signal. For example, the wireless receiving unit 10b may receive a PDSCH DMRS. For example, the wireless receiving unit 10b may receive a PDCCH DMRS. For example, the wireless receiving unit 10b may receive a CSI-RS. For example, the wireless receiving unit 10b may receive a DLPTRS.
[0088] The upper layer processing unit 14 outputs uplink data (transport block) to the wireless transceiver unit 10 (or the wireless transmission unit 10a). The upper layer processing unit 14 performs processing of the MAC layer, the packet data convergence protocol layer, the radio link control layer, and the RRC layer.
[0089] The media access control layer processing unit 15 included in the upper layer processing unit 14 performs processing at the MAC layer.
[0090] The radio resource control layer processing unit 16 included in the upper layer processing unit 14 performs RRC layer processing. The radio resource control layer processing unit 16 manages various setting information / parameters (RRC parameters) of the terminal device 1. The radio resource control layer processing unit 16 sets the RRC parameters based on the RRC message received from the base station device 3.
[0091] The wireless transceiver 10 (or the wireless transmission unit 10a) performs modulation, coding and other processing. The wireless transceiver 10 (or the wireless transmission unit 10a) generates a physical signal by modulating, coding and generating a baseband signal (converting to a time-continuous signal) the uplink data, and transmits it to the base station device 3. The wireless transceiver 10 (or the wireless transmission unit 10a) can configure the physical signal to a certain BWP (activate the uplink BWP) and transmit it to the base station device 3.
[0092] The wireless transceiver 10 (or wireless receiving unit 10b) performs demodulation, decoding and other processing. The wireless transceiver 10 (or wireless receiving unit 30b) can receive a physical signal in a certain BWP (activated downlink BWP) of a certain serving cell. The wireless transceiver 10 (or wireless receiving unit 10b) separates, demodulates and decodes the received physical signal, and outputs the decoded information to the upper layer processing unit 14. The wireless transceiver 10 (wireless receiving unit 10b) can implement a channel access process before sending a physical signal.
[0093] The RF unit 12 converts the signal received by the antenna unit 11 into a baseband signal by orthogonal demodulation (down conversion) and removes unnecessary frequency components. The RF unit 12 outputs the processed analog signal to the baseband unit 13 .
[0094] The baseband unit 13 converts the analog signal input from the RF unit 12 into a digital signal. The baseband unit 13 removes a portion corresponding to a CP (Cyclic Prefix) from the converted digital signal, performs a fast Fourier transform (FFT) on the signal after the CP is removed, and extracts a signal in the frequency domain.
[0095] The baseband unit 13 performs an inverse fast Fourier transform (IFFT) on the uplink data to generate OFDM symbols, adds a CP to the generated OFDM symbols to generate a baseband digital signal, and converts the baseband digital signal into an analog signal. The baseband unit 13 outputs the converted analog signal to the RF unit 12.
[0096] The RF unit 12 uses a low-pass filter to remove unnecessary frequency components from the analog signal input from the baseband unit 13, up-converts the analog signal into a carrier frequency, and transmits it via the antenna unit 11. In addition, the RF unit 12 may also have a function of controlling the transmission power. The RF unit 12 is also called a transmission power control unit.
[0097] The following describes the physical signal (signal).
[0098] Physical signal is the general term for downlink physical channel, downlink physical signal, uplink physical channel and uplink physical channel. Physical channel is the general term for downlink physical channel and uplink physical channel. Physical signal is the general term for downlink physical signal and uplink physical signal.
[0099] An uplink physical channel may correspond to a set of resource elements used to transmit information generated in an upper layer. An uplink physical channel may be a physical channel used in an uplink component carrier. An uplink physical channel may be transmitted by a terminal device 1. An uplink physical channel may be received by a base station device 3. In a wireless communication system of one embodiment of the present invention, at least some or all of the following uplink physical channels may be used. PUCCH (Physical Uplink Control CHannel: Physical Uplink Control Channel) PUSCH (Physical Uplink Shared CHannel: Physical Uplink Shared Channel) PRACH (Physical Random Access CHannel)
[0100] PUCCH can be used to send uplink control information (UCI: Uplink Control Information). PUCCH can be sent to deliver, transmit, convey uplink control information. Uplink control information can be mapped to PUCCH. Terminal device 1 can send PUCCH configured with uplink control information. Base station device 3 can receive PUCCH configured with uplink control information.
[0101] The uplink control information (uplink control information bit, uplink control information sequence, uplink control information type) includes at least part or all of the channel state information (CSI: Channel State Information), scheduling request (SR: Scheduling Request), and HARQ-ACK (Hybrid Automatic Repeat request ACKnowledgement: Hybrid Automatic Repeat request ACKnowledgement) information.
[0102] 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.
[0103] The HARQ-ACK information may include at least a HARQ-ACK corresponding to a transport block (TB). HARQ-ACK may represent an ACK (acknowledgement) or a NACK (negative-acknowledgement) corresponding to the transport block. ACK may indicate that the decoding of the transport block has been successfully completed (has been decoded). NACK may indicate that the decoding of the transport block has not been successfully completed (has not been decoded). The HARQ-ACK information may also include a HARQ-ACK codebook containing one or more HARQ-ACK bits.
[0104] A transport block is an information bit sequence delivered from an upper layer. Here, the information bit sequence is also referred to as a bit sequence. Here, the transport block can be distributed via the UL-SCH (UpLink-Shared Channel) of the transport layer.
[0105] The HARQ-ACK for the transport block may be referred to as the HARQ-ACK for the PDSCH. In this case, the "HARQ-ACK for the PDSCH" means the HARQ-ACK for the transport block included in the PDSCH.
[0106] HARQ-ACK may also represent ACK or NACK corresponding to a CBG (Code Block Group) included in a transport block.
[0107] The scheduling request can be used at least to request the resources of the UL-SCH for the initial transmission (new transmission). The scheduling request bit can be used to indicate either a positive SR or a negative SR. The scheduling request bit indicating a positive SR is also referred to as "transmitting a positive SR". A positive SR can indicate that the resources of the UL-SCH for the initial transmission are requested by the terminal device 1. A positive SR can also indicate that the scheduling request is triggered by an upper layer. In the case of indicating that the scheduling request is sent by the upper layer, a positive SR can be transmitted. The scheduling request bit indicating a negative SR is also referred to as "a negative SR is sent". A negative SR can indicate that the resources of the UL-SCH for the initial transmission are not requested by the terminal device 1. A negative SR can also indicate that the scheduling request is not triggered by the upper layer. A negative SR can be transmitted without indicating that the scheduling request is sent by the upper layer.
[0108] The channel state information may include at least a part or all of a channel quality indicator (CQI: Channel Quality Indicator), a precoding matrix indicator (PMI: Precoder Matrix Indicator) and a rank indicator (RI: Rank Indicator). CQI is an indicator associated with the quality of a transmission path (e.g., transmission strength) or the quality of a physical channel, and PMI is an indicator associated with precoding. RI is an indicator associated with a transmission rank (or number of transmission layers).
[0109] The channel state information is an indicator of the reception state of a physical signal (e.g., CSI-RS) at least used for channel measurement. The value of the channel state information can be determined by the terminal device 1 based on the reception state assumed by the physical signal at least used for channel measurement. Channel measurement can include interference measurement.
[0110] PUCCH may correspond to a PUCCH format. PUCCH may be a set of resource elements used to transmit a PUCCH format. PUCCH may include a PUCCH format. PUCCH may be sent in a certain PUCCH format. It should be noted that a PUCCH format may be interpreted as an information format. In addition, a PUCCH format may also be interpreted as an information set set in a certain information format.
[0111] PUSCH can also be used to transmit one or both of a transport block and uplink control information. A transport block can be configured in PUSCH. A transport block distributed by UL-SCH can be configured in PUSCH. Uplink control information can be configured in PUSCH. Terminal device 1 can send a PUSCH configured with one or both of a transport block and uplink control information. Base station device 3 can receive a PUSCH configured with one or both of a transport block and uplink control information.
[0112] PRACH may also be sent to deliver a random access preamble. Terminal device 1 may send PRACH. Base station device 3 may receive PRACH. PRACH sequence x u,v (n) by x u,v (n) = x u (mod(n+C v ,L RA )) is defined. Here, x u is a ZC (Zadoff Chu) sequence. In addition, x u You can use x u =exp(-jπui(i+1) / L RA ). j is an imaginary unit. In addition, π is the circumference of a circle. In addition, C v corresponds to the cyclic shift of the PRACH sequence. RA Corresponds to the length of the PRACH sequence. In addition, L RA is 839 or 139. In addition, i is 0 to L RA An integer in the range of -1. In addition, u is the sequence index of the PRACH sequence.
[0113] 64 random access preambles are defined for each PRACH opportunity. The random access preamble is based on the cyclic shift C of the PRACH sequence. v The index may be added to each of the determined 64 random access preambles.
[0114] An uplink physical signal may correspond to a set of resource elements. An uplink physical signal may not be used to transmit information generated in an upper layer. It should be noted that an uplink physical signal may also be used to transmit information generated in a physical layer. An uplink physical signal may be a physical signal used in an uplink component carrier. The terminal device 1 may send an uplink physical signal. The base station device 3 may receive an uplink physical signal. In a wireless communication system of one embodiment of the present invention, 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)
[0115] UL DMRS is a general term for DMRS for PUSCH and DMRS for PUCCH.
[0116] The set of antenna ports for DMRS for PUSCH (DMRS associated with PUSCH, DMRS included in PUSCH, DMRS corresponding to PUSCH) may be given based on the set of antenna ports for the PUSCH. For example, the set of antenna ports for DMRS for PUSCH may be the same as the set of antenna ports for the PUSCH.
[0117] The transmission of a PUSCH and the transmission of a DMRS for the PUSCH may be represented (or scheduled) by one DCI format. The PUSCH and the DMRS for the PUSCH may be collectively referred to as a PUSCH. Transmitting a PUSCH may also be transmitting a PUSCH and a DMRS for the PUSCH.
[0118] The propagation path of the PUSCH can be estimated based on the DMRS used for the PUSCH.
[0119] The set of antenna ports for the DMRS of the PUCCH (DMRS associated with the PUCCH, DMRS included in the PUCCH, DMRS corresponding to the PUCCH) may be the same as the set of antenna ports of the PUCCH.
[0120] The transmission of the PUCCH and the transmission of the DMRS for the PUCCH may be indicated (or triggered) by a DCI format. One or both of the mapping of the PUCCH to resource elements and the mapping of the DMRS for the PUCCH to resource elements may be provided in a PUCCH format. The PUCCH and the DMRS for the PUCCH may be collectively referred to as the PUCCH. Transmitting the PUCCH may also be transmitting the PUCCH and the DMRS for the PUCCH.
[0121] The propagation path of the PUCCH can be estimated by the DMRS used for the PUCCH.
[0122] A downlink physical channel may correspond to a set of resource elements that transmit information generated in an upper layer. A downlink physical channel may be a physical channel used in a downlink component carrier. The base station device 3 may transmit a downlink physical channel. The terminal device 1 may receive a downlink physical channel. In a wireless communication system of one embodiment of the present invention, 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)
[0123] PBCH can be sent to transmit one or both of MIB (Master Information Block) and physical layer control information. Here, physical layer control information is information generated in the physical layer. MIB is a set of parameters configured in BCCH (Broadcast Control Channel), which is a logical channel of the MAC layer. The BCCH is configured in BCH, which is a channel of the transport layer. BCH can be configured (mapped) to PBCH. Terminal device 1 can receive PBCH configured with one or both of MIB and physical layer control information. Base station device 3 can send PBCH configured with one or both of MIB and physical layer control information.
[0124] For example, the physical layer control information may be composed of 8 bits. The physical layer control information may include at least a part or all of the following 0A to 0D. 0A) Wireless frame bits 0B) Half radio frame (half system frame, half frame) bit 0C) SS / PBCH block index bit 0D) Subcarrier offset bit
[0125] The radio frame bit is used to indicate the radio frame in which the PBCH is sent (including the radio frame of the time slot in which the PBCH is sent). The radio frame bit includes 4 bits. The radio frame bit can be composed of 4 bits in the 10-bit radio frame indicator. For example, the radio frame indicator can be used to determine at least the radio frames of index 0 to index 1023.
[0126] The half radio frame bit is used to indicate in which of the first half of the 5 subframes or the second half of the 5 subframes in the radio frame in which the PBCH is transmitted, the PBCH is transmitted. Here, the half radio frame may be configured to include 5 subframes. In addition, the half radio frame may be configured to include the first half of the 5 subframes of the 10 subframes included in the radio frame. In addition, the half radio frame may also be configured to include the second half of the 5 subframes of the 10 subframes included in the radio frame.
[0127] The SS / PBCH block index bit is used to indicate the SS / PBCH block index. The SS / PBCH block index bit includes 3 bits. The SS / PBCH block index bit may also be composed of 3 bits of the 6-bit SS / PBCH block index indicator. The SS / PBCH block index indicator may be used to determine at least SS / PBCH blocks with indexes 0 to 63. The SS / PBCH block may also be referred to as an SSB.
[0128] The subcarrier offset bit is used to indicate the subcarrier offset. The subcarrier offset can also be used to indicate the difference between the subcarrier at the start point of mapping the PBCH and the subcarrier at the start point of the control resource set with mapping index 0.
[0129] The PDCCH may be sent to transmit downlink control information (DCI: Downlink Control Information). The downlink control information may be configured (mapped) on the PDCCH. The terminal device 1 may receive the PDCCH configured with the downlink control information. The base station device 3 may send the PDCCH configured with the downlink control information.
[0130] The downlink control information may be sent with a DCI format. It should be noted that the DCI format may be interpreted as the format of the downlink control information. In addition, the DCI format may also be interpreted as a set of downlink control information set in a certain format of downlink control information.
[0131] DCI format 0_0, DCI format 0_1, DCI format 1_0, and DCI format 1_1 are DCI formats. The uplink 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.
[0132] DCI format 0_0 is used to configure at least PUSCH scheduling in a certain cell. DCI format 0_0 is configured to include at least a part or all of the fields 1A to 1E. 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 (MCS field: Modulation and Coding Scheme field: Modulation and Coding Scheme field)
[0133] The DCI format specific field may indicate whether the DCI format including the DCI format specific field is an uplink DCI format or a downlink DCI format. That is, the DCI format specific field may be included in each uplink DCI format and downlink DCI format. Here, the DCI format specific field included in DCI format 0_0 may represent 0.
[0134] The frequency domain resource allocation field included in DCI format 0_0 may be used to indicate frequency resource allocation for the PUSCH.
[0135] The time domain resource allocation field included in DCI format 0_0 may be used to indicate the time resource allocation of the PUSCH.
[0136] The frequency hopping flag field may be used to indicate whether frequency hopping is applied to the PUSCH.
[0137] The MCS field included in DCI format 0_0 may be used to indicate at least one or both of the modulation mode and the target coding rate of the PUSCH. The target coding rate may be a target coding rate of a transport block configured in the PUSCH. The size of the transport block (TBS: Transport Block Size) configured in the PUSCH may be determined based on one or both of the target coding rate and the modulation mode of the PUSCH.
[0138] DCI format 0_0 may not include a field for CSI request (CSI request).
[0139] DCI format 0_0 may also not include a carrier indicator field. That is, the service cell to which the uplink component carrier configured with the PUSCH scheduled by DCI format 0_0 belongs and the service cell to which the uplink component carrier configured with the PDCCH including the DCI format 0_0 belongs may be the same. The terminal device 1 may recognize that the PUSCH scheduled by the DCI format 0_0 is configured on the uplink component carrier of a certain service cell based on the detection of DCI format 0_0 in a certain downlink component carrier of the certain service cell.
[0140] DCI format 0_0 may not include a BWP field. Here, DCI format 0_0 may be a DCI format for scheduling PUSCH without changing the activated uplink BWP. The terminal device 1 may recognize that the PUSCH is sent without switching the activated uplink BWP based on detecting DCI format 0_0 for PUSCH scheduling.
[0141] DCI format 0_1 is used to configure at least PUSCH scheduling in a certain cell. DCI format 0_1 is configured to include at least a part or all of the fields 2A to 2H. 2A) DCI format specification field 2B) Frequency Domain Resource Allocation Field 2C) Time domain resource allocation field for uplink 2D) Frequency Hopping Flag Field 2E) MCS field 2F) CSI request field 2G)BWP field 2H) Carrier indicator field
[0142] The DCI format specific field included in DCI format 0_1 may represent 0.
[0143] The frequency domain resource allocation field included in DCI format 0_1 may be used to indicate frequency resource allocation for PUSCH.
[0144] The time domain resource allocation field included in DCI format 0_1 may be used to indicate time resource allocation for PUSCH.
[0145] The MCS field included in DCI format 0_1 may be used to indicate at least part or all of the modulation scheme and / or target coding rate for the PUSCH.
[0146] The BWP field of DCI format 0_1 can be used to indicate the uplink BWP configured with the PUSCH scheduled by the DCI format 0_1. That is, DCI format 0_1 can change according to the activation of the uplink BWP. The terminal device 1 can identify the uplink BWP configured with the PUSCH based on the detection of DCI format 0_1 for PUSCH scheduling.
[0147] DCI format 0_1 not including the BWP field may be a DCI format for scheduling PUSCH without changing the activated uplink BWP. Terminal device 1 is DCI format 0_1 for PUSCH scheduling, and can recognize that the PUSCH is sent without switching the activated uplink BWP based on detecting DCI format D0_1 not including the BWP field.
[0148] The BWP field is included in DCI format 0_1, but in the case where terminal device 1 does not support the function of switching BWP through DCI format 0_1, terminal device 1 can ignore the BWP field. That is, terminal device 1 that does not support the BWP switching function is DCI format 0_1 for PUSCH scheduling, and can recognize that the PUSCH is sent without switching the activated uplink BWP based on the detection of DCI format 0_1 including the BWP field. Here, in the case where terminal device 1 supports the BWP switching function, in the function information reporting process of the RRC layer, it can be reported that "terminal device 1 supports the BWP switching function".
[0149] The CSI request field is used to indicate a CSI report.
[0150] Alternatively, when the carrier indicator field is included in DCI format 0_1, the carrier indicator field is used to indicate the uplink component carrier configured with the PUSCH. Alternatively, when the carrier indicator field is not included in DCI format 0_1, the uplink component carrier configured with the PUSCH is the same as the uplink component carrier configured with the PDCCH including the DCI format 0_1 for scheduling the PUSCH. Alternatively, when the number of uplink component carriers set for the terminal device 1 in a certain service cell group is 2 or more (when uplink carrier aggregation is used in a certain service cell group), the number of bits of the carrier indicator field included in the DCI format 0_1 for scheduling the PUSCH configured for the certain service cell group is 1 bit or more (for example, 3 bits). It may also be that, when the number of uplink component carriers set for terminal device 1 in a certain service cell group is 1 (when uplink carrier aggregation is not used in a certain service cell group), the number of bits of the carrier indicator field included in the DCI format 0_1 used for scheduling of PUSCH configured for the certain service cell group is 0 (or the carrier indicator field is not included in the DCI format 0_1 used for scheduling of PUSCH configured for the certain service cell group).
[0151] DCI format 1_0 is used to configure at least PDSCH scheduling in a certain cell. DCI format 1_0 is configured to include at least a part or all of 3A to 3F. 3A) DCI format specification field 3B) Frequency Domain Resource Allocation Field 3C) Time Domain Resource Allocation Field 3D)MCS field 3E)PDSCH_HARQ feedback timing indicator field (PDSCH to HARQ feedback timing indicator field) 3F)PUCCH resource indicator field
[0152] The DCI format specific field included in DCI format 1_0 may represent 1.
[0153] The frequency domain resource allocation field included in DCI format 1_0 may be used at least to indicate allocation of frequency resources for PDSCH.
[0154] The time domain resource allocation field included in DCI format 1_0 may be used at least to indicate allocation of time resources for PDSCH.
[0155] The MCS field included in DCI format 1_0 may be used to indicate at least one or both of the modulation scheme and the target coding rate for the PDSCH. The target coding rate may be the target coding rate for the transport block configured in the PDSCH. The size of the transport block (TBS: Transport Block Size) configured in the PDSCH may be determined based on one or both of the target coding rate and the modulation scheme for the PDSCH.
[0156] The PDSCH_HARQ Feedback Timing Indication field may be used to indicate an offset from a slot including a last OFDM symbol of a PDSCH to a slot including an OFDM symbol of a start point of a PUCCH.
[0157] The PUCCH resource indication field may be a field indicating any index of one or more PUCCH resources included in a PUCCH resource set. The PUCCH resource set may include one or more PUCCH resources.
[0158] DCI format 1_0 may not include a carrier indicator field. That is, a downlink component carrier configured with a PDSCH scheduled by DCI format 1_0 may be the same as a downlink component carrier configured with a PDCCH including the DCI format 1_0. The terminal device 1 may recognize that the PDSCH scheduled by the DCI format 1_0 is configured on a downlink component carrier based on the detection of DCI format 1_0 in the downlink component carrier.
[0159] DCI format 1_0 may not include a BWP field. Here, DCI format 1_0 may be a DCI format for scheduling PDSCH without changing the activated downlink BWP. The terminal device 1 may recognize that the PDSCH is received without switching the activated downlink BWP based on the detection of DCI format 1_0 for PDSCH scheduling.
[0160] DCI format 1_1 is used at least for configuring PDSCH scheduling in a certain cell. DCI format 1_1 may include at least a part or all of 4A to 4I. 4A) DCI format specification field 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 indicator field 4H) BWP field 4I) Carrier Indicator Field
[0161] The DCI format specific field included in DCI format 1_1 may represent 1.
[0162] The frequency domain resource allocation field included in DCI format 1_1 may be used at least to indicate allocation of frequency resources for PDSCH.
[0163] The time domain resource allocation field included in DCI format 1_1 may be used at least to indicate allocation of time resources for PDSCH.
[0164] The MCS field included in DCI format 1_1 may be used to indicate at least one or both of a modulation scheme and a target coding rate for the PDSCH.
[0165] Alternatively, when the PDSCH_HARQ feedback timing indication field is included in the DCI format 1_1, the PDSCH_HARQ feedback timing indication field is at least used to indicate the offset from the time slot including the last OFDM symbol of the PDSCH to the time slot including the OFDM symbol of the starting point of the PUCCH. Alternatively, when the PDSCH_HARQ feedback timing indication field is not included in the DCI format 1_1, the offset from the time slot including the last OFDM symbol of the PDSCH to the time slot including the OFDM symbol of the starting point of the PUCCH is determined by the parameters of the upper layer.
[0166] The PUCCH resource indication field may be a field indicating any one index of one or more PUCCH resources included in a PUCCH resource set.
[0167] The BWP field of DCI format 1_1 can be used to indicate the downlink BWP configured with the PDSCH scheduled by the DCI format 1_1. That is, DCI format 1_1 can change according to the activation of the downlink BWP. The terminal device 1 can identify the downlink BWP configured with the PUSCH based on the detection of DCI format 1_1 for PDSCH scheduling.
[0168] The DCI format 1_1 not including the BWP field may be a DCI format for scheduling the PDSCH without changing the activated downlink BWP. The terminal device 1 is a DCI format 1_1 for PDSCH scheduling, and can recognize that the PDSCH is received without switching the activated downlink BWP based on detecting the DCI format 1_1 not including the BWP field.
[0169] The BWP field is included in DCI format 1_1, but in the case where terminal device 1 does not support the function of switching BWP through DCI format 1_1, terminal device 1 can ignore the BWP field. That is, terminal device 1 that does not support the BWP switching function is DCI format 1_1 for PDSCH scheduling, and can recognize that the PDSCH is received without switching the activated downlink BWP based on the detection of DCI format 1_1 including the BWP field. Here, in the case where terminal device 1 supports the BWP switching function, in the function information reporting process of the RRC layer, it can be reported that "terminal device 1 supports the BWP switching function".
[0170] Alternatively, when the carrier indicator field is included in the DCI format 1_1, the carrier indicator field is used to indicate the downlink component carrier configured with the PDSCH. Alternatively, when the carrier indicator field is not included in the DCI format 1_1, the downlink component carrier configured with the PDSCH is the same as the downlink component carrier configured with the PDCCH including the DCI format 1_1 for scheduling the PDSCH. Alternatively, when the number of downlink component carriers set for the terminal device 1 in a certain service cell group is 2 or more (when downlink carrier aggregation is used in a certain service cell group), the number of bits of the carrier indicator field included in the DCI format 1_1 for scheduling the PDSCH configured for the certain service cell group is 1 bit or more (for example, 3 bits). Alternatively, when the number of downlink component carriers set for terminal device 1 in a certain service cell group is 1 (when downlink carrier aggregation is not used in a certain service cell group), the number of bits of the carrier indicator field included in the DCI format 1_1 used for scheduling of PDSCH configured for the certain service cell group is 0 (or, the carrier indicator field is not included in the DCI format 1_1 used for scheduling of PDSCH configured for the certain service cell group).
[0171] The PDSCH may be sent for delivering a transport block. The PDSCH may also be used to send a transport block distributed by the DL-SCH. The PDSCH may be used to deliver a transport block. The transport block may be configured on the PDSCH. The transport block corresponding to the DL-SCH may also be configured on the PDSCH. The base station device 3 may send the PDSCH. The terminal device 1 may receive the PDSCH.
[0172] A downlink physical signal may correspond to a set of resource elements. A downlink physical signal may not carry information generated in an upper layer. A downlink physical signal may be a physical signal used in a downlink component carrier. A downlink physical signal may be sent by a base station device 3. A downlink physical signal may also be sent by a terminal device 1. In a wireless communication system of one embodiment of the present invention, 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)
[0173] The synchronization signal can be used to synchronize one or both of the frequency domain and the time domain of the downlink for the terminal device 1. The synchronization signal is a general term for PSS (Primary Synchronization Signal) and SSS (Secondary Synchronization Signal).
[0174] Figure 7 FIG. 1 is a diagram showing an example of the configuration of an SS / PBCH block according to one embodiment of the present invention. Figure 7 In the figure, the horizontal axis is the time axis (OFDM symbol index l sym ), the vertical axis represents the frequency domain. In addition, block 700 represents a set of resource elements for PSS. In addition, block 702 represents a set of resource elements for SSS. In addition, four blocks (blocks 710, 711, 712, and 713) represent a set of resource elements for PBCH and DMRS for the PBCH (DMRS associated with PBCH, DMRS included in PBCH, DMRS corresponding to PBCH).
[0175] like Figure 7As shown, the SS / PBCH block includes PSS, SSS and PBCH. In addition, the SS / PBCH block includes 4 consecutive OFDM symbols. The SS / PBCH block includes 240 subcarriers. PSS is configured on the 57th to 183rd subcarriers in the first OFDM symbol. SSS is configured on the 57th to 183rd subcarriers in the third OFDM symbol. The 1st to 56th subcarriers of the first OFDM symbol can be set to zero. The 184th to 240th subcarriers of the first OFDM symbol can also be set to zero. The 49th to 56th subcarriers of the third OFDM symbol can also be set to zero. The 184th to 192nd subcarriers of the third OFDM symbol can also be set to zero. PBCH is configured in the subcarriers that are the 1st to 240th subcarriers of the second OFDM symbol and are not configured with DMRS for PBCH. PBCH is configured in the subcarriers that are the 1st to 48th subcarriers of the third OFDM symbol and are not configured with DMRS for PBCH. The PBCH is configured in the subcarriers which are the 193rd to 240th subcarriers of the third OFDM symbol and to which the DMRS for the PBCH is not configured. The PBCH is configured in the subcarriers which are the 1st to 240th subcarriers of the fourth OFDM symbol and to which the DMRS for the PBCH is not configured.
[0176] The antenna ports of PSS, SSS, PBCH, and DMRS for PBCH may be the same.
[0177] A PBCH conveying a symbol of a PBCH in a certain antenna port may be estimated based on a DMRS for the PBCH that is configured to a slot in which the PBCH is mapped and that is included in a SS / PBCH block including the PBCH.
[0178] DL DMRS is a general term for DMRS for PBCH, DMRS for PDSCH, and DMRS for PDCCH.
[0179] The set of antenna ports for DMRS for PDSCH (DMRS associated with PDSCH, DMRS included in PDSCH, DMRS corresponding to PDSCH) can be given based on the set of antenna ports for the PDSCH. That is, the set of antenna ports for DMRS for PDSCH can be the same as the set of antenna ports for the PDSCH.
[0180] The transmission of the PDSCH and the transmission of the DMRS for the PDSCH may be indicated (or scheduled) by one DCI format. The PDSCH and the DMRS for the PDSCH may be collectively referred to as the PDSCH. Transmitting the PDSCH may also be transmitting the PDSCH and the DMRS for the PDSCH.
[0181] The transmission path of the PDSCH can be estimated based on the DMRS used for the PDSCH. If a set of resource elements that transmit symbols of a certain PDSCH and a set of resource elements that transmit symbols of the DMRS used for the certain PDSCH are included in the same precoding resource group (PRG: Precoding Resource Group), the PDSCH that transmits the symbols of the PDSCH in a certain antenna port can be estimated based on the DMRS used for the PDSCH.
[0182] The antenna port for the DMRS of the PDCCH (DMRS associated with the PDCCH, DMRS included in the PDCCH, DMRS corresponding to the PDCCH) may be the same as the antenna port for the PDCCH.
[0183] The PDCCH can be estimated based on the DMRS used for the PDCCH. That is, the transmission path of the PDCCH can be estimated based on the DMRS used for the PDCCH. If the same precoding is applied (assumed to be applied, assumed to be applied) in a set of resource elements that convey symbols of a certain PDCCH and a set of resource elements that convey symbols of the DMRS used for the certain PDCCH, then the PDCCH that conveys the symbols of the PDCCH in a certain antenna port can be estimated based on the DMRS used for the PDCCH.
[0184] 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).
[0185] The BCH of the transport layer is mapped to the PBCH of the physical layer. That is, the transport block of the BCH of the transport layer is distributed to the PBCH of the physical layer. In addition, the UL-SCH of the transport layer is mapped to the PUSCH of the physical layer. That is, the transport block of the UL-SCH of the transport layer is distributed to the PUSCH of the physical layer. In addition, the DL-SCH of the transport layer is mapped to the PDSCH of the physical layer. That is, the transport block of the DL-SCH of the transport layer is distributed to the PDSCH of the physical layer.
[0186] One UL-SCH and one DL-SCH may be provided for each serving cell. BCH may be provided by PCell. BCH may also not be provided by PSCell or SCell.
[0187] In the MAC layer, HARQ (Hybrid Automatic Repeat reQuest) control is performed on each transport block.
[0188] BCCH (Broadcast Control CHannel), CCCH (Common Control CHannel) and DCCH (Dedicated Control CHannel) are logical channels. For example, BCCH is a channel of the RRC layer for sending MIB or system information. In addition, CCCH (Common Control CHannel) can be used to send RRC messages that are common to multiple terminal devices 1. Here, CCCH can be used for terminal devices 1 that are not RRC connected, for example. In addition, DCCH (Dedicated Control CHannel) can be used at least to send RRC messages dedicated to terminal device 1. Here, DCCH can be used for terminal devices 1 that are RRC connected, for example.
[0189] For example, system information (SI) can be composed of MIB and several SIBs (System Information block). In addition, system information can be divided into minimum SI and other SI. Minimum SI may include basic information required for initial access. Moreover, minimum SI may also include information for obtaining other SI. Minimum SI may also be composed of MIB and SIB1. Other SI may also include all SIBs that are not broadcast in minimum SI. These SIBs may also be broadcast or sent in DL-SCH.
[0190] SIB1 can define the scheduling of other SI. SIB1 can include information required for initial access. SIB1 can also be called RMSI (Remaining Minimum SI). SIB1 can be placed periodically in DL-SCH. SIB1 can be sent to several UEs in RRC_CONNECTED state in a dedicated manner in DL-SCH.
[0191] The upper layer parameters shared by multiple terminal devices 1 are also referred to as common upper layer parameters. Here, the common upper layer parameters can be defined as parameters specific to a serving cell. Here, the parameters specific to a serving cell can be parameters shared by the terminal devices (e.g., terminal devices 1-A, B, C) that set the serving cell.
[0192] For example, the common upper layer parameters may be included in an RRC message distributed to the BCCH. For example, the common upper layer parameters may be included in an RRC message distributed to the DCCH.
[0193] In a certain upper layer parameter, an upper layer parameter different from a common upper layer parameter is also referred to as a dedicated upper layer parameter. Here, the dedicated upper layer parameter can provide a dedicated RRC parameter to the terminal device 1-A that sets the service cell. That is, the dedicated RRC parameter is an upper layer parameter that can provide a specific setting for each of the terminal devices 1-A, B, and C.
[0194] The BCCH of the logical channel can be mapped to the BCH or DL-SCH of the transport layer. For example, a transport block including MIB information is distributed to the BCH of the transport layer. In addition, a transport block including system information that is not MIB is distributed to the DL-SCH of the transport layer. In addition, CCCH is mapped to DL-SCH or UL-SCH. That is, the transport block mapped to CCCH is distributed to DL-SCH or UL-SCH. In addition, DCCH is mapped to DL-SCH or UL-SCH. That is, the transport block mapped to DCCH is distributed to DL-SCH or UL-SCH.
[0195] 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 RRC message may include the MIB. In addition, the RRC message may also include system information. In addition, the RRC message may also include a message corresponding to the CCCH. In addition, the RRC message may also include a message corresponding to the DCCH. The RRC message including a message corresponding to the DCCH is also referred to as a dedicated RRC message.
[0196] The upper layer parameters (upper layer parameters) are RRC parameters or parameters included in MAC CE (Medium Access Control Control Element: control element of media access control). That is, the upper layer parameters are a general term for MIB, system information, messages corresponding to CCCH, messages corresponding to DCCH, and parameters included in MAC CE. The parameters included in MAC CE are sent through MAC CE (Control Element: control element) commands.
[0197] The process performed by the terminal device 1 includes at least a part or all of the following 5A to 5C. 5A) Cell search 5B) Random access 5C) Data communication
[0198] Cell search is a process for synchronizing a cell in time and frequency domains and detecting a physical cell ID (physical cell identity) through the terminal device 1. That is, the terminal device 1 can synchronize with a cell in time and frequency domains and detect a physical cell ID through cell search.
[0199] The sequence of the PSS is given based on at least the physical cell ID. The sequence of the SSS is given based on at least the physical cell ID.
[0200] The SS / PBCH block candidates indicate resources for which transmission of SS / PBCH blocks is permitted (able to, reserved, set, specified, or possible).
[0201] The set of SS / PBCH block candidates in a half radio frame is also called an SS burst set. An SS burst set is also called a transmission window, an SS transmission window, or a DRS transmission window. An SS burst set is a general term for at least a first SS burst set and a second SS burst set.
[0202] The base station device 3 sends one or more indexed SS / PBCH blocks at a predetermined period. The terminal device 1 can detect at least any one of the one or more indexed SS / PBCH blocks and attempt to decode the PBCH included in the SS / PBCH block.
[0203] Random access is a process including at least part or all of message 1, message 2, message 3 and message 4.
[0204] Message 1 is a process of sending PRACH by terminal device 1. Terminal device 1 sends PRACH in a PRACH opportunity selected from one or more PRACH opportunities based at least on an index of an SS / PBCH block candidate, wherein the index of the SS / PBCH block candidate is detected based on a cell search. Each PRACH opportunity is defined based on at least a time domain resource and a frequency domain resource.
[0205] The terminal device 1 transmits one random access preamble selected from the PRACH opportunities corresponding to the index of the SS / PBCH block candidate for detecting the SS / PBCH block.
[0206] Message 2 is a process of attempting to detect DCI format 1_0 with CRC (Cyclic Redundancy Check) encrypted by RA-RNTI (Random Access-Radio Network Temporary Identifier) by terminal device 1. Terminal device 1 attempts to detect PDCCH including the DCI format in resources indicated based on the settings of control resource set and search area set, wherein the settings of control resource set and search area set are given based on MIB of PBCH included in SS / PBCH block detected based on cell search. Message 2 is also called random access response.
[0207] Message 3 is a process of transmitting a PUSCH scheduled by a random access response grant included in DCI format 1_0 detected by the process of message 2. Here, the random access response grant is indicated by a MAC CE included in a PDSCH scheduled by the DCI format 1_0.
[0208] The PUSCH scheduled based on the random access response grant is any one of the messages 3PUSCH or PUSCH. The message 3PUSCH includes a contention resolution identifier (MAC CE). The contention resolution identifier (MAC CE) includes the contention resolution ID.
[0209] The retransmission of message 3 PUSCH is scheduled by DCI format 0_0 with CRC scrambled based on TC-RNTI (Temporary Cell-Radio Network Temporary Identifier).
[0210] Message 4 is a process of attempting to detect DCI format 1_0 with CRC scrambled based on either C-RNTI (Cell-Radio Network Temporary Identifier) or TC-RNTI. Terminal device 1 receives PDSCH scheduled based on DCI format 1_0. The PDSCH may include a contention resolution ID.
[0211] Data communication is a general term for downlink communication and uplink communication.
[0212] In data communication, the terminal device 1 attempts to detect the PDCCH (monitor the PDCCH, monitor the PDCCH) in resources determined based on the control resource set and the search area set.
[0213] 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 can be composed of continuous resources (non-interleaved mapping) or dispersed resources (interleaver mapping).
[0214] The set of resource blocks constituting the control resource set may be represented by an upper layer parameter. The number of OFDM symbols constituting the control resource set may also be represented by an upper layer parameter.
[0215] A CORESET pool index may also be provided for one or more Control Resource Sets (CORESETs). For example, the CORESET pool index may be provided by an upper layer parameter. For example, when not provided by the upper layer parameter, the CORESET pool index may be 0. The value of the CORESET pool index may be 0 or 1. The CORESET pool index may also be referred to as an index of a CORESET resource pool. For example, the CORESET pool index may be provided in an activated downlink BWP of a serving cell. For example, a CORESET pool index having a value of 0 may be provided for a first plurality of CORESETs.
[0216] The terminal device 1 may apply a first process for reporting HARQ-ACK information associated with a first CORESETs and a second process for reporting HARQ-ACK information associated with a second CORESETs. The terminal device 1 may also apply the first process and the second process separately. The first CORESETs and the second CORESETs may be CORESETs in an activated downlink BWP of a serving cell. A CORESET pool index having a value of 0 may be provided for the first CORESETs. A CORESET pool index having a value of 1 may be provided for the second CORESETs. The first CORESETs may be the first one or more CORESETs. The second CORESETs may be the second one or more CORESETs.
[0217] The TCI state (Transmission Configuration Indication state: transmission setting indication state) can be provided by the DCI format. One or more TCI state setting configurations (or setting lists) can be provided by upper layer parameters for decoding PDSCH. For example, terminal device 1 can decode PDSCH according to the PDCCH to be decoded. A TCI state may include parameters for setting the QCL relationship between a downlink reference signal and a first antenna port. For example, the first antenna port may be a DMRS port of a PDSCH (an antenna port associated with a DMRS). The first antenna port may also be a DMRS port of a PDCCH. The first antenna port may also be a CSI-RS port of a CSI-RS resource. The QCL relationship can be set by upper layer parameters. For example, the QCL relationship can be set for the first downlink reference signal by the upper layer parameter qcl-Type1. For example, the QCL relationship can be set for the second downlink reference signal by the upper layer parameter qcl-Type2. For example, the QCL relationship between the first antenna port and the second antenna port may indicate that the first antenna port and the second antenna port are QCL. The downlink reference signal may be a CSI-RS or a SS / PBCH block.
[0218] The CORESET pool index of the first CORESET may be different from the CORESET pool index of the second CORESET. Two different values of the CORESET pool index may be set in different CORESETs by upper layer parameters. It may be assumed that the first antenna port and the first reference signal associated with a CORESET pool index of a serving cell are QCL.
[0219] Terminal device 1 attempts to detect PDCCH in the search area set. Here, attempting to detect PDCCH in the search area set may be attempting to detect PDCCH candidates in the search area set, or attempting to detect DCI formats in the search area set, or attempting to detect PDCCH in the control resource set, or attempting to detect PDCCH candidates in the control resource set, or attempting to detect DCI formats in the control resource set.
[0220] The search area set is defined as a set of PDCCH candidates. The search area set can be a CSS (Common Search Space) set or a USS (UE-specific Search Space) set. Terminal device 1 attempts to detect PDCCH candidates in part or all of a type 0 PDCCH common search space set, a type 0a PDCCH common search space set, a type 1 PDCCH common search space set, a type 2 PDCCH common search space set, a type 3 PDCCH common search space set, and / or a UE-specific PDCCH search space set.
[0221] The type 0 PDCCH common search region set may be used as the common search region set of index 0. The type 0 PDCCH common search region set may also be the common search region set of index 0.
[0222] The CSS set is a general term for type 0 PDCCH common search area set, type 0a PDCCH common search area set, type 1 PDCCH common search area set, type 2 PDCCH common search area set, and type 3 PDCCH common search area set. The USS set is also called a UE-specific PDCCH search area set.
[0223] A certain search area set is associated with (includes, corresponds to) a certain control resource set. The index of the control resource set associated with the search area set may be represented by an upper layer parameter.
[0224] For a certain search area set, at least a part or all of 6A to 6C may be represented by upper layer parameters. 6A)PDCCH monitoring periodicity 6B)PDCCH monitoring pattern within a slot 6C)PDCCH monitoring offset
[0225] A monitoring occasion of a certain search area set may correspond to an OFDM symbol configured with an OFDM symbol of a starting point of a control resource set associated with the certain search area set. A monitoring occasion of a certain search area set may also correspond to resources of the control resource set starting from an OFDM symbol of a starting point of a control resource set associated with the certain search area set. The monitoring occasion of the search area set is given based on at least a portion or all of a monitoring interval of a PDCCH, a monitoring mode of a PDCCH within a time slot, and a monitoring offset of a PDCCH.
[0226] Figure 8 FIG. 1 is a diagram showing an example of monitoring opportunities of a search area set according to one embodiment of the present invention. Figure 8 In the embodiment, 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 .
[0227] exist Figure 8 In the figure, the monochrome white blocks in the primary cell 301 represent the search area set 91, the monochrome black blocks in the primary cell 301 represent the search area set 92, the blocks in the secondary cell 302 represent the search area set 93, and the blocks in the secondary cell 303 represent the search area set 94.
[0228] The monitoring interval of search area set 91 is set to 1 time slot, the monitoring offset of search area set 91 is set to 0 time slots, and the monitoring pattern of search area set 91 is set to [1,0,0,0,0,0,0,1,0,0,0,0,0,0,0]. That is, the monitoring opportunities of search area set 91 correspond to the starting OFDM symbol (OFDM symbol #0) and the 8th OFDM symbol (OFDM symbol #7) in each time slot.
[0229] The monitoring interval of search area set 92 is set to 2 time slots, the monitoring offset of search area set 92 is set to 0 time slots, and the monitoring pattern of search area set 92 is set to [1,0,0,0,0,0,0,0,0,0,0,0,0,0]. That is, the monitoring opportunity of search area set 92 corresponds to the OFDM symbol (OFDM symbol #0) at the start point in each even time slot.
[0230] The monitoring interval of search area set 93 is set to 2 time slots, the monitoring offset of search area set 93 is set to 0 time slots, and the monitoring pattern of search area set 93 is set to [0,0,0,0,0,0,0,1,0,0,0,0,0,0,0]. That is, the monitoring opportunity of search area set 93 corresponds to the 8th OFDM symbol (OFDM symbol #7) in each even time slot.
[0231] The monitoring interval of search area set 94 is set to 2 time slots, the monitoring offset of search area set 94 is set to 1 time slot, and the monitoring pattern of search area set 94 is set to [1,0,0,0,0,0,0,0,0,0,0,0,0,0]. That is, the monitoring opportunity of search area set 94 corresponds to the OFDM symbol (OFDM symbol #0) at the start point in each odd time slot.
[0232] The type 0 PDCCH common search area set can be used at least for a DCI format that is accompanied by a CRC (Cyclic Redundancy Check) sequence that is scrambled by the SI-RNTI (System Information-Radio Network Temporary Identifier).
[0233] The type 0a PDCCH common search space set can be used at least for a DCI format with a CRC (Cyclic Redundancy Check) sequence scrambled by SI-RNTI (System Information-Radio Network Temporary Identifier).
[0234] The type 1 PDCCH common search area set can be used at least for a DCI format with a CRC sequence scrambled by RA-RNTI (Random Access-Radio Network Temporary Identifier) and / or a CRC sequence scrambled by TC-RNTI (Temporary Cell-Radio Network Temporary Identifier).
[0235] The type 2 PDCCH common search area set may be used for a DCI format with a CRC sequence scrambled by a P-RNTI (Paging-Radio Network Temporary Identifier).
[0236] The type 3 PDCCH common search area set may be used for a DCI format with a CRC sequence scrambled by a C-RNTI (Cell-Radio Network Temporary Identifier).
[0237] The UE-specific PDCCH search area set may be used at least for a DCI format to which a CRC sequence scrambled by a C-RNTI is attached.
[0238] In downlink communication, terminal device 1 detects a downlink DCI format. The detected downlink DCI format is used at least for resource allocation of PDSCH. The detected downlink DCI format is also referred to as a downlink assignment. Terminal device 1 attempts to receive the PDSCH. Based on the PUCCH resource, the HARQ-ACK corresponding to the PDSCH (the HARQ-ACK corresponding to the transport block included in the PDSCH) is reported to base station device 3, wherein the PUCCH resource is indicated based on the detected downlink DCI format.
[0239] In uplink communication, the terminal device 1 detects an uplink DCI format. The detected DCI format is used for at least resource allocation of a PUSCH. The detected uplink DCI format is also called an uplink grant. The terminal device 1 transmits the PUSCH.
[0240] In the configured grant, the uplink grant for scheduling PUSCH is configured for each transmission period of the PUSCH. When the PUSCH is scheduled by an uplink DCI format, part or all of the information indicated by the uplink DCI format may be indicated by the configured uplink grant in the configured scheduling.
[0241] A UL slot may be a slot consisting of UL symbols. A special slot may be a slot consisting of UL symbols, variable symbols, and DL symbols. A DL slot may be a slot consisting of DL symbols.
[0242] The UL symbol may be an OFDM symbol set or indicated for the uplink in time division duplex. The UL symbol may be an OFDM symbol set or indicated for PUSCH, PUCCH, PRACH, or SRS. The UL symbol may be provided by the upper layer parameter tdd-UL-DL-ConfigurationCommon. The UL symbol may also be provided by the upper layer parameter tdd-UL-DL-ConfigurationDedicated. The UL timeslot may be provided by the upper layer parameter tdd-UL-DL-ConfigurationCommon. The UL timeslot may also be provided by the upper layer parameter tdd-UL-DL-ConfigurationDedicated.
[0243] The DL symbol may be an OFDM symbol set or indicated for the downlink in time division duplex. The DL symbol may be an OFDM symbol set or indicated for the PDSCH or PDCCH. The DL symbol may be provided by the upper layer parameter tdd-UL-DL-ConfigurationCommon. The DL symbol may also be provided by the upper layer parameter tdd-UL-DL-ConfigurationDedicated. The DL time slot may be provided by the upper layer parameter tdd-UL-DL-ConfigurationCommon. The DL time slot may also be provided by the upper layer parameter tdd-UL-DL-ConfigurationDedicated.
[0244] The variable symbol may be an OFDM symbol that is not set or indicated as a UL symbol or a DL symbol in an OFDM symbol within a certain period. The certain period may be a period given by the upper layer parameter dl-UL-TransmissionPeriodicity. The variable symbol may be an OFDM symbol set or indicated for PDSCH, PDCCH, PUSCH, PUCCH or PRACH.
[0245] The upper layer parameter tdd-UL-DL-ConfigurationCommon may be a parameter for setting any one of a UL time slot, a DL time slot, and a special time slot for each of one or more time slots. The upper layer parameter tdd-UL-DL-ConfigurationDedicated may be a parameter for setting any one of a UL symbol, a DL symbol, and a variable symbol for a variable symbol in each of the one or more time slots. tdd-UL-DL-ConfigurationCommon may be a common upper layer parameter. tdd-UL-DL-ConfigurationDedicated may be a dedicated upper layer parameter.
[0246] Multiple TRPs (Transmission Reception Point or Transmit / Receive Point) may also be used. The base station device 3 may be composed of multiple TRPs (Multi-TRP). The terminal device 1 may be scheduled through two TRPs in one service cell. In multi-TRP, one of the action 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, downlink control may also be completed in the MAC layer and the physical layer. In single-DCI mode, the terminal device 1 may be scheduled through the same DCI for two TRPs. In multi-DCI mode, the terminal device 1 may be scheduled through independent DCI from each TRP. In multi-DCI mode, each TRP in the multiple TRPs may be determined by TRP information. That is, one TRP in the multiple TRPs may be identified by one TRP information. TRP information may be used to select a TRP. In addition, the index of the CORESET resource pool can be associated with a control resource set (CORESET: Control Resource Set). Terminal device 1 can send PUSCH based on the index of the CORESET resource pool. The TRP information can be a CORESET pool index. The TRP information can be associated with the index of the CORESET resource pool. For example, the first CORESET pool index can be associated with the first TRP, and the second CORESET pool index can be associated with the second TRP. The TRP information can be associated with a pool (or pool index) of a TCI state. The first one or more TCI states can be associated with the pool index of the first TCI state. The second one or more TCI states can be associated with the pool index of the second TCI state.
[0247] The value of the TA offset (Timing advance offset: timing advance offset) may be provided by an upper layer parameter. The timing advance (TA) may be determined based on at least the TA offset. One TA offset may be provided in one serving cell. Two TA offsets may also be provided in one serving cell. In the absence of an upper layer parameter, the terminal device 1 may determine the value of the TA offset. The terminal device 1 may also determine the values of two TA offsets in one serving cell. The value of the TA offset may be N TA,offset The upper layer parameter may be n-TimingAdvanceOffset. Determining the TA may be adjusting the uplink timing.
[0248] When two uplink carriers are set in one serving cell, one TA offset value can be applied to both uplink carriers. When two TRPs (Transmission Reception Points) are set in one serving cell, one TA offset value can be applied to both TRPs. When two TRPs are set in one serving cell, two TA offset values can be applied to each TRP.
[0249] The terminal device 1 can adjust the uplink timing. For example, the terminal device 1 can adjust the uplink timing in response to the reception of a TA command (Timing advance command). For example, the terminal device 1 can also adjust the uplink timing for PUSCH / SRS / PUCCH transmission in all service cells in a TAG (Timing advance group) in response to the reception of a TA command (Timing advance command) for a TAG. For example, the terminal device 1 can also adjust the uplink timing for PUSCH / SRS / PUCCH transmission in one or more service cells belonging to a TAG in response to the reception of a TA command for a TAG. For example, the terminal device 1 can adjust the uplink timing for PUSCH / SRS / PUCCH transmission in one or more service cells belonging to a TAG based on N TA,offet For all serving cells in a TAG, N TA,offset For all serving cells in a TAG, N TA,offset Alternatively, the terminal device 1 may be based on N TA,offset The uplink timing is adjusted based on the value of and one or both of the TA command. The uplink timing can be the same for all service cells in a TAG. The uplink timing can also be different for all service cells in a TAG. For example, the first uplink timing can be the same for the first part of the service cells in a TAG. For example, the second uplink timing can be the same for the second part of the service cells in a TAG. All service cells in a TAG can be divided into a first part and a second part. It can be the uplink timing for PUSCH / SRS / PUCCH transmission.
[0250] The terminal device 1 can determine the uplink timing based on at least a part or all of the TA command, the TA offset and the TRP information. The first uplink timing and the second uplink timing can be determined based on at least the TRP information. For example, the TRP (Transmission Reception Point) information can be information for determining one TRP in one or more TRPs. For example, the TRP information can also be an index for determining a TRP. For example, a TRP can be determined based on the TRP information. For example, the TRP information can also be information for determining one or more TRPs. The TRP information can be provided by upper layer parameters. The TRP information can be included in the random access response. The TRP information can also be included in the DCI format.
[0251] The first uplink timing may be determined based on a timing adjustment indication for one TAG from the MCG. The second uplink timing may be determined based on a timing adjustment indication for one TAG from the SCG.
[0252] The TA command may be changed based on the subcarrier spacing. For example, in the subcarrier spacing setting μ, one TA command for one TAG may indicate a change in uplink timing. For example, the uplink timing may be changed in 16*64*T c / 2 μ "*" can be a multiplication operator.
[0253] The TA (Timing advance) of the random access preamble can be 0.
[0254] The TA command may be included in the random access response. 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 in the case of a random access response or an Absolute Timing Advance Command MAC CE A N can be indicated for a TAG TA For example, T A It can be an integer from 0 to 3846. For example, N TA Can be T A *16*64 / 2 μ . N TAIt can be associated with the subcarrier spacing of a certain uplink transmission. For example, the certain uplink transmission can be an uplink transmission from the terminal device 1. For example, the certain uplink transmission can also be the first uplink transmission after receiving the random access response. For example, the certain uplink transmission can also be the first uplink transmission after receiving the absolute timing advance command MAC CE. A It can be an index value. The uplink transmission can also be an uplink channel transmission.
[0255] TA command T A The current N can be indicated for a TAG TA For example, the TA command T A Can indicate from N TA,old To N TA,new Adjustment. TA,new Can be N TA,old +(T A -31)*16*64 / 2 μ For example, T A It can be an integer from 0 to 63.
[0256] In the case where the terminal device has one or more activated uplink BWPs, the TA command (TA command value) may be associated with the maximum subcarrier spacing of the one or more activated 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 the first subcarrier spacing may be associated with the maximum subcarrier spacing of the one or more activated uplink BWPs. TA,new The value is rounded to match the TA granularity (timing advance granularity) for one uplink BWP with the first subcarrier spacing. The value may also be rounded to the mantissa of the value. For example, N may be rounded while maintaining the TA accuracy requirements. TA,new Rounding is performed.
[0257] N through positive values TA The adjustment of N can indicate the advancement of the uplink transmission timing (uplink timing) for a TAG (Timing advance group). TA The adjustment may indicate a delay in the uplink transmission timing for one TAG.
[0258] In case a TA command is received in the first time slot n, an adjustment of the uplink transmission timing may be applied starting from the start of the second time slot. The first time slot n may be an uplink time slot. The uplink time slot may be a time slot corresponding to an uplink frame. The second time slot may be n+k+1+2 μ *K offset That is, the second time slot may be k+1+2 from the first time slot n. μ *K offset The time slot after K offset It can be provided by the upper layer parameters. k can be ceil(N subframe ,μ slot ·(N T,1 +N T,2 +N TA,max +0.5) / T sf ). T,1 The unit can be millisecond. T,1 It may be a period of N1 symbols in milliseconds. N1 symbols may correspond to the PDSCH processing time. T,2 It may be a period of N2 symbols in milliseconds. N2 symbols may correspond to the PUSCH preparation time. TA,max It can be the maximum TA value (timing advance value) in milliseconds. TA,max It can be the maximum TA value that can be provided by the 12-bit TA command field. subframe,μ slot It can be the number of time slots in a subframe. sf It can be 1 millisecond. sf It can be the period of a subframe. offset Can be K cell,offset -K UE,offset . K cell,offset Can be provided by upper layer parameters. K UE,offset Can be provided by a MAC CE command. cell,offset Can be 0. K UE,offset It can be 0. One or both of N1 and N2 can be determined in association with the minimum subcarrier spacing (SCS). The minimum subcarrier spacing can also be the minimum subcarrier spacing among the subcarrier spacings of all downlink BWPs and all uplink BWPs. In the case of μ=0, N1 can be 14. The time slot n and N2 can be determined in association with the minimum subcarrier spacing.subframe,μ slot N can also be determined in association with the minimum subcarrier spacing. TA,max Time slot n may also be the last time slot of one or more time slots that overlap with the time slot of PDSCH reception. In PDSCH reception, it may be assumed that T TA = 0. A TA command may be received in the PDSCH. A PDSCH including a TA command may be received. A TA command may be provided by the PDSCH.
[0259] In the case where the terminal device 1 changes the activated uplink BWP, the terminal device 1 can determine the TA command (TA command value) based on the changed subcarrier spacing of the activated uplink BWP. For example, in the case where the terminal device 1 changes the activated uplink BWP between receiving the TA command and applying the adjustment for uplink transmission timing, the terminal device 1 can also determine the TA command based on the new subcarrier spacing of the activated uplink BWP. In the case of changing the activated uplink BWP after applying the adjustment for uplink transmission timing, the terminal device 1 can assume the same absolute timing advance command value (absolute timing advance command value: absolute timing advance commandMAC CE). That is, the first absolute timing advance command value before the activated uplink BWP is changed can be the same as the second absolute timing advance command value after the activated uplink BWP is changed.
[0260] When the downlink timing is changed and the downlink timing is not corrected, the terminal device 1 can change N TA When the downlink timing is changed and the downlink timing is partially corrected by uplink timing adjustment without a TA command, the terminal device 1 may change N TA The uplink timing adjustment may also be to determine or change the uplink timing.
[0261] In case two adjacent time slots are overlapped due to a TA command, the latter time slot may be reduced.
[0262] TAG (Timing advance group) can be a group of one or more service cells. One or more service cells can be set by RRC. One or more service cells can use one TA value. One or more service cells can also use a timing reference cell. PTAG (Primary TAG) can be a TAG that includes SpCell. STAG (Secondary TAG) can be a TAG that does not include SpCell. One or more service cells can also use two TA values.
[0263] A sub-TAG may be a group of one or more service cells. A sub-TAG may be a group of service cells using the same TA (TA value). For example, a sub-TAG may be associated with one TRP information. For example, a sub-TAG may also be associated with one TRP. A service cell associated with a sub-TAG may not be associated with a TAG. For example, a sub-TAG may also be set for a service cell. For example, a service cell associated with a sub-TAG may also be associated with a TAG. A sub-TAG may be a group of one or more TRPs. A sub-TAG may also be a group of TRPs using the same TA (TA value). For example, a sub-TAG may be associated with one service cell.
[0264] The RRC layer can set one or more upper layer parameters for maintenance of uplink time alignment. For example, the RRC layer can set a time alignment timer. For example, the time synchronization timer can be set by the upper layer parameter timeAlignmentTimer. The time synchronization timer can control the first time. The first time can be the time when the MAC entity regards multiple service cells as belonging to an associated TAG. For example, the time synchronization timer can be the time used for uplink time synchronization. That is, the time synchronization timer can also work to perform time synchronization. Performing time synchronization can also be determining (or adjusting) uplink timing. That is, the TA can also perform time synchronization.
[0265] The RRC layer may set one or more upper layer parameters for maintaining multiple uplink time synchronization. For example, the RRC layer may set multiple time synchronization timers. At least one of the multiple time synchronization timers may be associated with a sub-TAG. At least one of the multiple time synchronization timers may also be associated with a TAG.
[0266] The time synchronization timer may correspond to a sub-TAG. For example, the time synchronization timer may control the time at which the MAC entity considers one or more serving cells to belong to the sub-TAG. For example, the time synchronization timer may also control the time at which the MAC entity considers one or more TRPs to belong to the sub-TAG.
[0267] The MAC entity may perform part or all of the first to fourth processes.
[0268] In the first process, upon receiving the TA command MAC CE (Timing advance command MAC CE), and maintaining N in the indicated TAG TA In the case of, the MAC entity can apply the TA command for the indicated TA command. In the first process, after receiving the TA command MAC CE (Timing advance command MAC CE), and maintaining N in the indicated TAG TA In the case of a TA command, the MAC entity may start or restart a time synchronization timer associated with the indicated TA command. The time synchronization timer may be timeAlignmentTimer.
[0269] The second processing may be processing for a case where a TA command is received in a random access response (random access response message). The second processing may also be processing for a case where a TA command is received in a message B (MSGB). The second processing may also be processing in a service cell belonging to a TAG (or sub-TAG). The second processing may also be processing in a SpCell. In the second processing, without selecting a random access preamble from the preamble in CBRA (Contention-based random access), the MAC entity may apply a TA command for a TAG (or sub-TAG), or may start or restart a time synchronization timer associated with a TAG (or sub-TAG). The TA command may be received through a random access response.
[0270] In the second process, when the time synchronization timer associated with a TAG (or sub-TAG) is not running, the MAC entity may apply a TA command to the TAG (or sub-TAG) or start the time synchronization timer. Furthermore, if contention resolution is not successfully completed, the MAC entity may stop the time synchronization timer.
[0271] In the second process, in the case where the random access preamble is selected from the preambles in the CBRA and the time synchronization timer associated with one TAG (or sub-TAG) is running, the MAC entity may ignore the received TA command.
[0272] In the third process, when an Absolute Timing Advance Command (Absolute Timing Advance Command) is sent and received for message A (MSGA) including C-RNTI MAC CE, the MAC entity may apply the Absolute TA command for PTAG, and may also start or restart a time synchronization timer associated with PTAG.
[0273] The fourth process may be a process in the case where the time synchronization timer expires. In the fourth process, when the time synchronization timer is associated with the PTAG (or a sub-TAG associated with the first TRP), the MAC entity may perform part or all of the first to seventh sub-actions. The first sub-action may be to flush all HARQ buffers for all service cells. The second sub-action may be to notify the RRC to release the PUCCH for all service cells. The third sub-action may be to notify the RRC to release the SRS for all service cells. The fourth sub-action may be to clear the set downlink allocation and the set uplink authorization. The fifth sub-action may be to clear the PUSCH resources used for semi-persistent CSI reporting. The sixth sub-action may be to regard all time synchronization timers as expired. The seventh sub-action may be to maintain N for all TAGs (or sub-TAGs). TA That is, when the time synchronization timer expires (not running), the MAC entity may not change N TA. In the fourth process, when the time synchronization timer is associated with the STAG (or the sub-TAG associated with the second TRP), the MAC entity may perform part or all of the eighth to thirteenth sub-actions. The eighth sub-action may be to flush all HARQ buffers for the service cell belonging to the TAG (or the sub-TAG). The ninth sub-action may be to notify the RRC to release the PUCCH for the service cell belonging to the TAG (or the sub-TAG). The tenth sub-action may be to notify the RRC to release the SRS for the service cell belonging to the TAG (or the sub-TAG). The eleventh sub-action may be to clear the set downlink allocation and the set uplink authorization for the service cell belonging to the TAG (or the sub-TAG). The twelfth sub-action may be to clear the PUSCH resources for semi-static CSI reporting for the service cell belonging to the TAG (or the sub-TAG). The thirteenth sub-action may be to maintain the N of the TAG (or the sub-TAG). TA .
[0274] The HARQ buffer may store MAC PDUs for transmission. A HARQ buffer may be associated with a HARQ process. A HARQ process may correspond to a HARQ process ID. Refreshing the HARQ buffer may also be to empty the HARQ buffer. In the case where the HARQ entity requests an initial transmission (new transmission) for a transport block, the HARQ process may store the MAC PDU in the associated HARQ buffer.
[0275] In the case where the MAC entity stops uplink transmission for the SCell due to exceeding the maximum uplink transmission timing difference, the MAC entity may regard the time synchronization timer stop as expired. The time synchronization timer may be a time synchronization timer associated with the SCell.
[0276] In the case where the time synchronization timer expires, the MAC entity may also not perform uplink transmission. In the case where the time synchronization timer is not running, the MAC entity may also not perform uplink transmission. The uplink transmission may also not include random access preamble transmission. The uplink transmission may also not include message A transmission. The uplink transmission may also be an uplink transmission in a serving cell. The uplink transmission may also be an uplink transmission in a TRP. The time synchronization timer may be a time synchronization timer associated with a TAG to which a serving cell belongs. The time synchronization timer may also be a time synchronization timer associated with a sub-TAG to which a serving cell belongs. The time synchronization timer may also be a time synchronization timer associated with a sub-TAG to which a TRP belongs.
[0277] In the case where the time synchronization timer associated with a sub-TAG expires, the MAC entity may not perform uplink transmission on one or more TRPs included in the sub-TAG. The uplink transmission may also not include one or both of the random access preamble transmission and the message A transmission. For example, in the case where the time synchronization timer associated with a TRP expires, the MAC entity may not perform uplink transmission on the TRP.
[0278] When the time synchronization timer associated with PTAG is not working, the MAC entity may not perform uplink transmission in any serving cell. The uplink transmission may not include the random access preamble transmission in SpCell. The uplink transmission may not include the message A transmission in SpCell.
[0279] MAC PDU (Protocol Data Unit) can be a bit string arranged in 1 byte. MAC PDU can also be a transport block. For example, MAC PDU can be composed of one or more MAC sub-PDUs. Each MAC sub-PDU can be composed of a MAC sub-header. Each MAC sub-PDU can also be composed of a MAC sub-header and a MAC SDU (Service Data Unit). Each MAC sub-PDU can also be composed of a MAC sub-header and a MAC CE (Control Element). Each MAC sub-PDU can also be composed of a MAC header and padding. MAC SDU can be data from the upper layer. MAC SDU can also be data to the upper layer.
[0280] The TA command may be a MAC CE. In addition, the TA command may be included in the MAC CE. For example, the TA command may be included in the TA command MAC CE. The TA command MAC CE may be composed of a TAG ID and a TA command. The TAG ID may indicate one or both of a TAG and a sub-TAG. The TAG including the SpCell may correspond to TAG ID 0. The TAG ID may be indicated by 2 bits. The TAG ID may indicate a sub-TAG. The TAG ID may also indicate a TRP. The TA command may indicate T A . T A It can be an integer from 0 to 63. A Can be used to control the amount of timing adjustment. Timing adjustment can be applied by the MAC entity. TA command can also be indicated by 6 bits. The TA command MAC CE can be determined by a MAC subheader with a certain LCID (Logical channel ID). The certain LCID can be the LCID corresponding to index 61.
[0281] The TA command may be included in an absolute TA command MAC CE (absolute Timing advance command MAC CE). The absolute TA command MAC CE may consist of a reserved bit and a TA command. The TA command may indicate an index value T A . T A Can be used to control the amount of timing adjustment. The TA command can also be indicated by 12 bits. The reserved bits can be 4 bits. The reserved bits can be set to a value of 0. The absolute TA command MAC CE can be composed of at least a TAG ID. The TAG ID can indicate a sub-TAG. The TAG ID can also indicate a TRP. The absolute TA command MAC CE can be determined by a MAC subheader with a certain eLCID. The certain eLCID can be the eLCID corresponding to index 316.
[0282] 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 may indicate the index value T A . T ACan be used to control the amount of timing adjustment. The size of the TA command field can be 12 bits. The random access response can be composed of a TA command, an uplink grant, and a temporary C-RNTI (Temporary C-RNTI). The uplink grant can indicate the resources used in the uplink. The uplink grant field can be 27 bits. The temporary C-RNTI can indicate a temporary ID used by the MAC entity during random access. The temporary C-RNTI field can be 16 bits. The random access response can be a MAC RAR. For example, the random access response can be a fallbackRAR. The TA command can be included in message B (MSGB). For example, the TA command can be included in the MAC payload of message B. The TA command can also be included in the successRAR. In addition, the random access response can also include TRP information. For example, a TA corresponding to a TRP determined by the TRP information can be indicated by a TA command included in the random access response. As TRP information, the random access response can include an index to a CORSET resource pool.
[0283] In addition, multiple TA commands may also be indicated by one random access response. For example, in the case where two TA commands are sent by one random access response, the TA commands for each TRP may be indicated by a first TA command and a second TA command. At this time, the first TA command and the second TA command may also be indicated by different fields included in the random access response. In addition, the first TA command and the second TA command may also be indicated by a field included in the random access response, and the first TA command corresponding to the value of the field (bit string, index) is associated with the second TA command (joint coding). In addition, the second TA command may also be defined by the difference of the first TA command.
[0284] Random access (or random access procedure) can be initiated by the MAC entity. Random access can also be initiated by a PDCCH command (or PDCCH). Random access can also be initiated by RRC. Random access in SCell can be initiated by a PDCCH command. In addition, random access can also be triggered by a MAC entity. Random access can also be triggered by a PDCCH command. Random access can also be triggered by RRC.
[0285] For example, random access may also be triggered (started) by an event. For example, an event may be initial access from the RRC_IDLE state. For example, an event may also be an RRC connection re-establishment process. For example, an event may also be the arrival of uplink or downlink data in the RRC_CONNECTED state when the uplink synchronization state is 'non-synchronised'. For example, an event may also be the arrival of uplink data in the RRC_CONNECTED state when there are no PUCCH resources. For example, an event may also be the failure of a scheduling request. For example, an event may also be an RRC-based request in response to a handover. For example, an event may also be an RRC connection resume. For example, an event may also be the establishment of time alignment. For example, an event may also be the establishment of time synchronization for a STAG. For example, an event may also be the establishment of time synchronization for a TRP. For example, an event may also be a request for other SI. For example, an event may also be beam failure recovery. For example, a certain event may also be the acquisition of TA.
[0286] The random access (random access type) may be a 4-step random access (4-step random access type). The random access (random access type) may also be a 2-step random access (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 also support CFRA (Contention-free random access). That is, the random access may also be CFRA. For example, the random access may be a 4-step random access type CBRA. For example, the random access may also be a 4-step random access type CFRA. For example, the random access may also be a 2-step random access type CBRA. For example, the random access may also be a 2-step random access type CFRA.
[0287] In a 4-step random access type CBRA, the terminal device 1 can send message 1 (random access preamble), receive message 2 (random access response), send message 3, and receive message 4 (contention resolution). In a 2-step random access type CBRA, the terminal device 1 can send message A (random access preamble and PUSCH payload) and receive message B (contention resolution). In a 4-step random access type CFRA, the terminal device 1 can receive allocation of a random access preamble, send a random access preamble, and receive a random access response. In a 2-step random access type CFRA, the terminal device 1 can receive allocation of a random access preamble and PUSCH, send a random access preamble and PUSCH, and receive a random access response.
[0288] When CFRA resources are not set, the RSRP (Reference signal received power) threshold can be used to select one of the 2-step random access type and the 4-step random access type. When CFRA resources of the 4-step random access type are set, the terminal device 1 can perform random access of the 4-step random access type. When CFRA resources of the 2-step random access type are set, the terminal device 1 can perform random access of the 2-step random access type.
[0289] Message 1 may consist of a preamble in PRACH. After sending Message 1, the terminal device 1 may monitor a response (random access response) within a set window. In CFRA, a dedicated preamble may be allocated. In CFRA, the terminal device 1 may end the random access in response to the random access response reception. In CBRA, the terminal device 1 may send Message 3 in response to the random access response reception. For example, the terminal device 1 may send Message 3 using an uplink grant (random access response grant). In CBRA, the terminal device 1 may monitor Message 4 (contention resolution). In the event that contention resolution is unsuccessful after sending Message 3, the terminal device 1 may send Message 1.
[0290] Message A may include a preamble in the PRACH. In addition, message A may also include a payload in the PUSCH. After sending message A, the terminal device 1 may monitor for a response within a set window. In CFRA, dedicated preamble and PUSCH resources may be allocated for sending message A. In CFRA, the terminal device 1 may end the random access in response to the reception of a response. In CBRA, in the event of successful contention resolution, the terminal device 1 may end the random access. In the event of receiving a fallback indication in message B, the terminal device 1 may send message 3 based on the fallback indication to monitor contention resolution. In the event that contention resolution is unsuccessful after sending message 3, the terminal device 1 may send message A. In the event that random access of a 2-step random access type is not completed, the terminal device 1 may be set to switch to a 4-step random access type CBRA.
[0291] The random access that can be performed simultaneously in the MAC entity may be one. When the first random access is in progress and the second random access is triggered, the terminal device 1 can continue the first random access. When the first random access is in progress and the second random access is triggered, the terminal device 1 can start the second random access.
[0292] The RRC may set a part or all of the first to eighth upper layer parameters for random access. A first set of PRACH opportunities (PRACH Occasions) for sending message 1 (random access preamble) may be set by a first upper layer parameter. The first set may be used by message A PRACH. A second set of PRACH opportunities for sending random access preambles of message A may also be set by a second upper layer parameter. PRACH opportunities may also be referred to as RA opportunities. PRACH opportunities may also be referred to as RACH occasions.
[0293] The power of the random access preamble may be set by a third upper layer parameter. For example, the power of the first (initial) random access preamble may be set by a third upper layer parameter.
[0294] The RSRP threshold may be set by a fourth upper layer parameter. For example, the RSRP threshold may be an RSRP threshold for SS / PBCH block selection or CSI-RS selection. For example, the RSRP threshold may be an RSRP threshold for selection between two uplink carriers. The two uplink carriers may be NUL (Normal Uplink) and SUL (Supplementary Uplink).
[0295] The maximum number of times one or both of message 1 and / or message A are sent may be set by a fifth upper layer parameter. One or both of message 1 and message A may change the transmission power each time they are sent. 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 ramp factor.
[0296] The random access preamble may be set by the seventh upper layer parameter. For example, the index of the random access preamble used in the PRACH opportunity may be set by the seventh upper layer parameter. The seventh upper layer parameter may represent any value in the range of 0 to 63.
[0297] The number of SS / PBCH blocks mapped to each PRACH opportunity can be defined by an eighth upper layer parameter. In addition, the number of CBRA random access preambles mapped to each SS / PBCH block can also be defined by an eighth upper layer parameter. The CBRA random access preamble can be a contention-based random access preamble (Contention-based Random Access Preamble). The transmission of one or both of message 1 and message A can use the random access preamble corresponding to group A or group B. For example, terminal device 1 can perform message A transmission using random access preamble group A. For example, terminal device 1 can also perform message A transmission using random access preamble group B.
[0298] When random access (random access procedure) starts in a service cell, the MAC entity can flush the message 3 buffer, flush the message A buffer, select a carrier for performing random access, determine the random access type, and perform a random access resource selection procedure.
[0299] The MAC entity may determine the power for each random access type based on a counter. The MAC entity may calculate the RA-RNTI associated with the PRACH opportunity in which the random access preamble is sent. The MAC entity may instruct the physical layer to use the selected PRACH opportunity to send the random access preamble. The RA-RNTI associated with the PRACH opportunity may be calculated based on the index of the starting OFDM symbol of the PRACH opportunity, the index of the starting time slot of the PRACH opportunity in a system frame, the index of the PRACH opportunity in the frequency domain, and part or all of the uplink carriers in which the random access preamble is sent.
[0300] The MAC entity may start the first window from the end of the random access preamble transmission. The random access preamble may be a CFRA random access preamble (Contention-free Random Access Preamble: contention-free random access preamble). The random access preamble may also be a CBRA random access preamble (Contention-based Random Access Preamble: contention-based random access preamble). The MAC entity may monitor the PDCCH for random access response. For example, during the operation of the first window, the MAC entity may monitor the PDCCH. The PDCCH may be a PDCCH in a SpCell. Notification of the reception of the PDCCH may be received from the physical layer. The PDCCH transmission may be addressed to the C-RNTI. In the case where the CFRA random access preamble is sent by the MAC entity, the MAC entity may be deemed to have successfully completed the random access.
[0301] A valid downlink allocation may be received in a PDCCH corresponding to the RA-RNTI. A received transport block may be decoded. The random access response may include a certain MAC sub-PDU. The certain MAC sub-PDU may be accompanied by a random access preamble ID. The MAC entity may deem the reception of the random access response successful based at least on the random access response including a certain MAC sub-PDU.
[0302] The MAC entity may deem the reception of the random access response to be successful. The MAC entity may deem the random access to be successfully completed based at least on the deeming the reception of the random access response to be successful, and may also indicate the reception of an upper layer ACK (acknowledgement), and may also apply a received TA command. For example, the MAC entity may process the value of the received UL authorization. For example, the MAC entity may also indicate the UL authorization received by the physical layer.
[0303] In the case where the reception of a random access response is deemed to be successful and a random access preamble is sent in a serving cell, the MAC entity may apply (process) a TA command for one serving cell. The MAC entity may apply a TA command for one serving cell based at least on the reception of a random access response deemed to be successful and a random access preamble sent in a serving cell. The MAC entity may apply a TA command for one TRP based at least on the reception of a random access response deemed to be successful. For example, in the case where the MAC PDU includes a TA command (e.g., an absolute TA command MAC CE), the MAC entity may apply (process) a 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. For example, one or more MAC SDUs may be demultiplexed (demultiplexing) from a transport block.
[0304] Before the random access (physical random access procedure) starts, the physical layer may receive a set of SS / PBCH block indices from the upper layer, and may also provide a set of RSRP measurements to the upper layer. Before the random access starts, the physical layer may instruct the upper layer to perform type 1-random access. Before the random access starts, the physical layer may also instruct the upper layer to perform type 2-random access. Type 1-random access may be a random access of a 4-step random access type. Type 2-random access may be a random access of a 2-step random access type. Before the random access starts, the physical layer may receive one or more parameters from the upper layer. One or more parameters may include settings for PRACH transmission parameters. The PRACH transmission parameters may be a PRACH preamble format for PRACH transmission, or a time resource, or a frequency resource. One or more parameters may include parameters for determining a root sequence. One or more parameters may also include parameters for determining a cyclic shift in a PRACH preamble sequence (sequence of a random access preamble). One or more parameters may also include TRP information. For example, a random access preamble may be associated with a TRP.
[0305] Random access may include at least the transmission of message 1 and message 2 in PRACH. Random access may include the transmission of message 1 in PRACH, message 2, the transmission of PUSCH scheduled by random access response grant (Random access response uplink grant), and 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 with PDCCH / PDSCH attached. The random access procedure may also be referred to as random access.
[0306] The random access may include at least the transmission of message A and the reception of message B. The random access may also include the transmission of message A, the reception of message B, the transmission of PUSCH scheduled by the random access response grant, and the PDSCH for contention resolution. Message A may be a random access preamble and PUSCH in PRACH. Message B may be a random access response. For example, message B may be a random access response with PDCCH / PDSCH attached. The random access response grant may be a fallback random access response grant.
[0307] In the case where random access is started by a PDCCH command, the PRACH transmission (random access preamble transmission) can be accompanied by the same subcarrier spacing as the PRACH transmission started by the upper layer. In the case where two uplink carriers are set in a service cell, and the terminal device 1 detects the PDCCH command, the terminal device 1 can use the value of the UL / SUL indication field from the detected PDCCH command to determine an uplink carrier for PRACH transmission. In the case where N TRPs are set in a service cell, and the terminal device 1 detects the PDCCH command, the terminal device 1 can use a field (or the value of the field) of the detected PDCCH command to determine a TRP for PRACH transmission.
[0308] Random access can be triggered by an upper layer or PDCCH command in response to a request for PRACH transmission. The settings made by the upper layer for PRACH transmission may include settings for PRACH transmission, preamble index (index of random access preamble), preamble SCS (subcarrier spacing of random access preamble), RA-RNTI, PRACH resources, and part or all of TRP information.
[0309] The random access preamble may be a contention-based preamble. The random access preamble may also be a contention-free preamble. The number of contention-based preambles for each valid PRACH opportunity and each SS / PBCH block index may be set by an upper layer parameter. The PRACH opportunity may be valid. For example, the PRACH opportunity may be valid based on at least an OFDM symbol set for time division duplexing.
[0310] The terminal device 1 may attempt to decode a DCI format 1_0 with a CRC scrambled by the RA-RNTI. For example, the terminal device 1 may attempt to decode a DCI format 1_0 with a CRC scrambled by the RA-RNTI within a certain window in response to a PRACH transmission. A certain window may be started based on at least the starting OFDM symbol of the CORESET.
[0311] The terminal device 1 may pass the transport block to the upper layer at least based on the terminal device 1 detecting a DCI format 1_0 with a CRC encrypted by the RA-RNTI and the terminal device 1 receiving the transport block. For example, a transmission may be received in a PDSCH within a certain window. The upper layer may parse the transport block corresponding to the random access preamble identity (RAPID) associated with the PRACH transmission. When the upper layer identifies the RAPID in the random access response (message of the random access response), the upper layer may indicate an uplink grant (random access response grant) to the physical layer. The random access response may be a random access response for the transport block. The random access response grant may also be a random access response uplink grant.
[0312] In the case where the terminal device 1 does not detect DCI format 1_0 with a CRC encrypted by RA-RNTI within the window, or in the case where the transport block in the PDSCH is not received within the window, the upper layer may also instruct the physical layer to send PRACH. In addition, in the case where the upper layer does not identify the RAPID associated with the PRACH transmission, the upper layer may also instruct the physical layer to send PRACH. For example, the terminal device 1 can be expected to send PRACH from the last OFDM symbol of the window to a predetermined time. In addition, the terminal device 1 can also be expected to send PRACH from the last OFDM symbol received from the PDSCH to a specified time. Sending PRACH may also be sending a random access preamble.
[0313] A PDCCH command may trigger a CFRA (Contention-free random access procedure). For example, a PDCCH command may trigger a CFRA in one SpCell. A PDCCH command may start a PRACH transmission. In the case where the terminal device 1 attempts to detect a DCI format 1_0 with a CRC scrambled by the RA-RNTI in response to a PRACH transmission started by a PDCCH command, it may be assumed that the PDCCH including the DCI format 1_0 and the PDCCH have the same QCL characteristics of the DMRS antenna port. The QCL characteristics may be large-scale characteristics of the channel.
[0314] The random access response grant may be composed of one or more fields. For example, one or more fields may include a frequency hopping flag field. For example, one or more fields may also include a frequency domain resource allocation field (or a PUSCH frequency resource allocation field). For example, one or more fields may also include a time domain resource allocation field (or a PUSCH time resource allocation field). For example, one or more fields may also include a TPC (Transmission power control) command field. For example, one or more fields may also include a CSI request field. For example, one or more fields may also include a field with TRP information.
[0315] In order to increase the freedom of terminal position, reduce interference, expand coverage, etc., it is a problem that the terminal device 1 determines uplink timing for multiple transmission and reception locations. For example, solution 1 can be used to solve this problem.
[0316] Hereinafter, one aspect of the present embodiment, aspect 1, will be described.
[0317] The terminal device 1 may send a first random access preamble in a first random access. The terminal device 1 may also receive a first random access response in a first random access. The terminal device 1 may also send a second random access preamble in a second random access. The terminal device 1 may also receive a second random access response in a second random access. For example, in the case of starting (triggering) the first random access, the terminal device 1 may send a first random access preamble or receive a first random access response. In the case of starting (triggering) the second random access, the terminal device 1 may send a second random access preamble or receive a second random access response.
[0318] The terminal device 1 may send a first random access preamble based at least on the first TRP information. For example, the first random access preamble may correspond to the first TRP. The terminal device 1 may also receive a first random access response including the first TRP information. The terminal device 1 may also send a second random access preamble based at least on the second TRP information. For example, the second random access preamble may correspond to the second TRP. The terminal device 1 may also receive a second random access response including the second TRP information. For example, the first upper layer parameter may be used to indicate that the first random access preamble is to be sent to the first TRP. For example, the second upper layer parameter may be used to indicate that the second random access preamble is to be sent to the second TRP. The first upper layer parameter and the second upper layer parameter may be the same.
[0319] The random access response may include a TA command. For example, the first random access response may include a first TA command. For example, the second random access response may include a second TA command. The first TA command may be different from the second TA command. That is, the first TA command may be independent of the second TA command. The terminal device 1 may receive the first TA command. The terminal device 1 may also receive the second TA command.
[0320] The first TA may be determined based on the first TA command. That is, the first uplink timing may be determined based on the first TA command. The first uplink timing may be the uplink timing between the terminal device 1 and the first TRP. The second TA may be determined based on the second TA command. That is, the second uplink timing may be determined based on the second TA command. The second uplink timing may be the uplink timing between the terminal device 1 and the second TRP. The uplink timing may be a TA.
[0321] The first TRP and the second TRP may be different TRPs. The first TRP and the second TRP may be set by upper layer parameters. The first TRP and the second TRP may also be determined by upper layer parameters. In the case where the upper layer parameters are not set, it may be assumed that there is no second TRP. The first TRP may be determined by a first ID (or index). The second TRP may be determined by a second ID (or index). The first ID and the second ID may be set by upper layer parameters. The first ID and the second ID may be included in the DCI format. The first ID and the second ID may also be included in the random access response.
[0322] The base station device 3 may be composed of a first TRP and a second TRP. For example, the base station device 3 may have two transceiver points (base station device 3a and base station device 3b). In addition, the first TRP may be the transceiver point of the base station device 3a. The second TRP may be the transceiver point of the base station device 3b. The base station device 3a may have the functions of the base station device 3 or may be independent of the base station device 3b. The base station device 3b may have the functions of the base station device 3 or may be independent of the base station device 3a. For example, the base station device 3a may not be synchronized with the base station device 3b. The TRP information may be used to select one of the base station device 3a and the base station device 3b.
[0323] The first TA command and the second TA command may be applied to one serving cell. For example, the first TA command and the second TA command may be applied to one serving cell at the same time. For example, the first TA command and the second TA command may be received in one serving cell. For example, the first TA command and the second TA command may be TA commands for one serving cell. For example, the first TA command and the second TA command may also be TA commands for one TAG. For example, the first TA command and the second TA command may also be TA commands for one time synchronization timer. That is, the first TA command and the second TA command may be TA commands for one time synchronization timer associated with one TAG.
[0324] The first TA and the second TA may be applied to one serving cell. For example, the first TA and the second TA may be received in one serving cell. For example, the first TA and the second TA may be TAs for one serving cell. That is, the terminal device 1 may use the first TA and the second TA in one serving cell. The first TA may not be updated (changed) based on the second TA command. The second TA may not be updated (changed) based on the first TA command.
[0325] The first uplink timing and the second uplink timing can be applied to one serving cell. For example, the first uplink timing and the second uplink timing can be received in one serving cell. For example, the first uplink timing and the second uplink timing can be uplink timings for one serving cell. That is, the terminal device 1 can use the first uplink timing and the second uplink timing in one serving cell. The first uplink timing may not be updated (changed) based on the second TA command. The second uplink timing may not be updated (changed) based on the first TA command.
[0326] The terminal device 1 can switch the first uplink timing and the second uplink timing. For example, the terminal device 1 can use one of the first uplink timing and the second uplink timing for an uplink transmission in a service cell. For example, the terminal device 1 can also make one of the first uplink timing and the second uplink timing correspond to an uplink transmission based on the TRP information. For example, the terminal device 1 can also make one of the first uplink timing and the second uplink timing correspond to an uplink transmission based on the sub-TAG. For example, the terminal device 1 can also make one of the first uplink timing and the second uplink timing correspond to an uplink transmission based on an indication from an upper layer (such as a MAC layer). For example, the terminal device 1 can also select one of the first uplink timing and the second uplink timing. For example, the terminal device 1 can also select one of the first uplink timing and the second uplink timing based on certain information. The certain information can be any one of the TRP information and the sub-TAG. The terminal device 1 can receive certain information or a parameter including certain information. The parameter including certain information can be any one of an upper layer parameter and a DCI format.
[0327] The terminal device 1 can send a first uplink channel corresponding to a first uplink timing and a second uplink channel corresponding to a second uplink timing in one serving cell. The first uplink channel and the second uplink channel can be the same. For example, the first uplink channel transmission and the second uplink channel transmission can be the same. That is, the terminal device 1 can simultaneously send an uplink corresponding to the first uplink timing and the second uplink timing in one serving cell.
[0328] It may be that the first random access is CBRA, and the second random access is CFRA. For example, the second random access may be started (triggered) by a PDCCH command. One of the first random access and the second random access may be CFRA. One of the first random access and the second random access may be started by a PDCCH command. For example, in the case where the second random access is CFRA, the second random access response may correspond to the first TRP. For example, in the case where the second random access is CFRA, it may be that the second random access preamble corresponds to the second TRP, and the second random access response corresponds to the first TRP. That is, CFRA may be started to establish a second TA. That is, the CSS set may not be set for the second TRP.
[0329] The first random access may be the first CBRA, and the second random access may be the second CBRA. The first random access and the second random access may not be performed simultaneously. For example, the first random access may be based on a first SS / PBCH block index, a first SS / PBCH block, and a part or all of a first SS / PBCH candidate. The second random access may be based on a second SS / PBCH block index, a second SS / PBCH block, and a part or all of a second SS / PBCH candidate.
[0330] The first random access preamble may be sent to the first TRP. The second random access preamble may be sent to the second TRP. For example, the upper layer parameters may be used to indicate that the first random access preamble is sent to the first TRP. For example, the upper layer parameters may also be used to indicate that the second random access preamble is sent to the second TRP.
[0331] One or both of the first TA and the first uplink timing may be determined based at least on the first TA offset and the first TA command. One or both of the second TA and the second uplink timing may also be determined based at least on the second TA offset and the second TA command. The first TA offset and the second TA offset may be the same. For example, the first TA offset and the second TA offset may be set by an upper layer parameter. For example, in the absence of an upper layer parameter, the terminal device 1 may also determine the first TA offset and the second TA offset as one value.
[0332] The first TA command may control the amount of the first timing adjustment (the first uplink timing adjustment). The second TA command may control the amount of the second timing adjustment (the second uplink timing adjustment). That is, the first TA command may indicate the first T A The second TA command can indicate the second T A . First T A and the second T A Can be different.
[0333] The terminal device 1 can adjust (determine) the first uplink timing for the first uplink transmission in response to the reception of the first TA command. The terminal device 1 can also adjust (determine) the second uplink timing for the second uplink transmission in response to the reception of the second TA command. The uplink can be PUSCH, PUCCH, or SRS. The first uplink can be transmitted in one serving cell. The second uplink can also be transmitted in the one serving cell.
[0334] The following describes the processing of the media access control layer processing unit 35 and the radio resource control layer processing unit 36 in scheme 1.
[0335] The RRC layer can set a first time alignment timer and a second time synchronization timer. For example, the RRC layer can set a first time synchronization timer and a second time synchronization timer for a service cell. For example, the first time synchronization timer can be set by a first upper layer parameter. For example, the second time synchronization timer can be set 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 can control the first time. The first time can be the time when the MAC entity regards at least the first TRP as belonging to the first sub-TAG. The second time synchronization timer can control the second time. The second time can be the time when the MAC entity regards at least the second TRP as belonging to the second sub-TAG.
[0336] The first time synchronization timer may be started or restarted based on at least the first TA command. The first time synchronization timer may be associated with the first TRP. The first time synchronization timer may also be associated with the first sub-TAG. The first sub-TAG may determine the first TRP from one or more TRPs. The first sub-TAG may include the first TRP. For example, the first sub-TAG may include one or more TRPs corresponding to the first TA. The first time synchronization timer may be associated with the first TAG. That is, the first time synchronization timer may be associated with the first sub-TAG and the first TAG. The third time synchronization timer may be associated with the first TAG.
[0337] The second time synchronization timer may be started or restarted based on at least the second TA command. The second time synchronization timer may be associated with the second TRP. The second time synchronization timer may also be associated with the second sub-TAG. The second sub-TAG may determine the second TRP from one or more TRPs. The second sub-TAG may include the second TRP. For example, the second sub-TAG may include one or more TRPs corresponding to the second TA. The second time synchronization timer may be associated with the second TAG. That is, the second time synchronization timer may be associated with the second sub-TAG and the second TAG. The first TAG and the second TAG may be the same. That is, the third time synchronization timer may be associated with the first TAG. For example, the first sub-TAG and the second sub-TAG may correspond to a serving cell.
[0338] The first time synchronization timer may be different from the second time synchronization timer. That is, the first time synchronization timer may be independent of the second time synchronization timer. For example, the first upper layer parameter for setting the first time synchronization timer may be independent of the second upper layer parameter for setting the second time synchronization timer. The MAC entity may manage the first time synchronization timer and the second time synchronization timer in parallel.
[0339] The second TA command 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 determining any one of the second TRP and the second sub-TAG. That is, the TA command MAC CE may be composed of a part or all of the TA command, the TAG ID, the ID for the second sub-TAG, and the TRP information for the second TRP. The absolute TA command MAC CE may be composed of a part or all of the TA command, the TAG ID, the ID for the second sub-TAG, and the TRP information for the second TRP. The second TA may be determined based on at least the first TA and the second TA command.
[0340] Upon receiving the TA command MAC CE including the first TA command and maintaining the first N in the first sub-TAG TA In the case of, the MAC entity may apply the first TA command. Upon receiving the TA command MAC CE including the first TA command and maintaining the first N in the first sub-TAG TA In this case, the MAC entity may start or restart the first time synchronization timer associated with the first TA command.
[0341] Upon receiving the TA command MAC CE including the second TA command and maintaining the second N in the first sub-TAG TA In the case of, the MAC entity may apply the second TA command. Upon receiving the TA command MAC CE including the second TA command and maintaining the second N in the second sub-TAG TA In the case of, the MAC entity may start or restart the second time synchronization timer associated with the second TA command. The MAC entity may manage part or all of the first time synchronization timer, the second time synchronization timer, and the third time synchronization timer.
[0342] When the first time synchronization timer stops (not running), the MAC entity may apply the first TA command or start the first time synchronization timer. Furthermore, in the case where contention resolution in the first random access is not successfully completed, the MAC entity may stop the first time synchronization timer. When the second time synchronization timer stops (not running), the MAC entity may apply the second TA command or start the second time synchronization timer. Furthermore, in the case where contention resolution in the second random access is not successfully completed, the MAC entity may stop the second time synchronization timer. The first time synchronization timer and the second time synchronization timer may be working (running) simultaneously.
[0343] In the case where the first random access preamble is selected from the preamble in the CBRA and the first time synchronization timer is running, the MAC entity may ignore the first TA command. In the case where the second random access preamble is selected from the preamble in the CBRA and the second time synchronization timer is running, the MAC entity may ignore the second TA command.
[0344] The first time synchronization timer and the second time synchronization timer may correspond to one serving cell. In the event that the first time synchronization timer or the second time synchronization timer expires, the MAC entity may flush all HARQ buffers for one serving cell. In the event that the first time synchronization timer or the second time synchronization timer expires, the MAC entity may notify the RRC to release the PUCCH for one serving cell. In the event that the first time synchronization timer or the second time synchronization timer expires, the MAC entity may notify the RRC to release the SRS for one serving cell. In the event that the first time synchronization timer or the second time synchronization timer expires, the MAC entity may clear the set downlink allocation and the set uplink authorization. In the event that the first time synchronization timer or the second time synchronization timer expires, the MAC entity may clear the PUSCH resources used for semi-persistent CSI reporting. In the event that the first time synchronization timer or the second time synchronization timer expires, the MAC entity may regard that all time synchronization timers corresponding to one serving cell have expired. In the event that the first time synchronization timer expires, the MAC entity may maintain the first N TA When the second time synchronization timer expires, the MAC entity may maintain the second N TA .
[0345] In the case where the first time synchronization timer is not working (expired), the MAC entity may at least not perform the first uplink transmission for the first TRP. In the case where the second time synchronization timer is not working (expired), the MAC entity may at least not perform the second uplink transmission for the second TRP. 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.
[0346] The MAC entity may process a first TA command for a serving cell when at least the reception of the first random access response is successfully completed. The MAC entity may process a first TA command for one or both of a serving cell and a first TRP based at least on the successful reception of the first random access response and the sending of a first random access preamble for a serving cell.
[0347] The following, Fig. 9 Provide explanation.
[0348] exist Fig. 9 , the first TRP may be TRP3a (or base station device 3a). The second TRP may be TRP3b (or base station device 3b). The first TA command may be TA command 900. The second TA command may be TA command 901. The first uplink transmission may be uplink transmission 910. The second uplink transmission may be uplink transmission 911. One or both of the first TA and the first uplink timing may be uplink timing 920. One or both of the second TA and the second uplink timing may be uplink timing 921. A service cell may be service cell 920.
[0349] Fig. 9 9 is a diagram showing an example of two uplink channel transmissions in a service cell of a scheme of the present embodiment. The terminal device 1 may perform uplink transmission 910 in the service cell 930, or may perform uplink transmission 911. The terminal device 1 may adjust the uplink timing 920 for uplink transmission 910 in response to the reception of the TA command 900. The terminal device 1 may also adjust the uplink timing 921 for uplink transmission 911 in response to the reception of the TA command 901.
[0350] The terminal device 1 may receive a TA command 900 from TRP 3a. The terminal device 1 may also receive a TA command 901 from TRP 3a or TRP 3b. For example, the terminal device 1 may send a second random access preamble to TRP 3b, and receive a second random access response including a TA command 901 from TRP 3a. In this case, the random access corresponding to the second random access preamble and the second random access response may be CFRA. In addition, the terminal device 1 may also send a second random access preamble to TRP 3b, and receive a random access response including a TA command 901 from TRP3b. In this case, the random access corresponding to the second random access preamble and the second random access response may be CFRA or CBRA.
[0351] A first time synchronization timer and a second time synchronization timer may be set for the serving cell 920. When the first time synchronization timer or the second time synchronization timer expires, the MAC entity may flush all HARQ buffers for the serving cell 920. When the first time synchronization timer or the second time synchronization timer expires, the MAC entity may notify the RRC to release the PUCCH for the serving cell 920. When the first time synchronization timer or the second time synchronization timer expires, the MAC entity may notify the RRC to release the SRS for the serving cell 920.
[0352] Hereinafter, various device aspects of one aspect of the present embodiment will be described.
[0353] (1) In order to achieve the above-mentioned purpose, the scheme of the present invention adopts the following means. That is, the first scheme of the present invention is a terminal device, comprising: a sending unit, which sends a first random access preamble in a first random access and sends a second random access preamble in a second random access; and a receiving unit, which receives a first TA command in the first random access and receives a second TA command in the second random access, adjusts the first uplink timing in a service cell at least based on the first TA command, adjusts the second uplink timing in the one service cell at least based on the second TA command, and uses one of the first uplink timing and the second uplink timing based on certain information. In addition, it may be that the first random access is CBRA and the second random access is CFRA. In addition, it may be that the certain information is any one of the transceiver point TRP information and the sub-timing advance group TAG, and the receiving unit receives the certain information or a parameter including the certain information.
[0354] (2) A second scheme of the present invention is a base station device, comprising: a receiving unit, which receives a first random access preamble in a first random access and receives a second random access preamble in a second random access; and a sending unit, which sends a first TA command in the first random access and sends a second TA command in the second random access, adjusts a first uplink timing in a service cell at least based on the first TA command, adjusts a second uplink timing in the one service cell at least based on the second TA command, and uses one of the first uplink timing and the second uplink timing based on certain information.
[0355] (3) The third scheme of the present invention is a terminal device, comprising: a wireless resource control layer processing unit, which sets a first time synchronization timer and a second time synchronization timer for a service cell; and a media access control layer processing unit, which starts or restarts the first time synchronization timer at least based on receiving a first TA command, and starts or restarts the second time synchronization timer at least based on receiving a second TA command, and when the first time synchronization timer or the second time synchronization timer expires, the media access control layer processing unit refreshes all HARQ buffers used for the one service cell.
[0356] (4) The fourth scheme of the present invention is a base station device, comprising: a wireless resource control layer processing unit, which sets a first time synchronization timer and a second time synchronization timer for a service cell; and a media access control layer processing unit, which starts or restarts the first time synchronization timer at least based on receiving a first TA command, and starts or restarts the second time synchronization timer at least based on receiving a second TA command, and when the first time synchronization timer or the second time synchronization timer expires, the media access control layer processing unit refreshes all HARQ buffers used for the one service cell.
[0357] The program operating in the base station device 3 and the terminal device 1 involved in the present invention may be a program (a program that makes a computer function) that controls a CPU (Central Processing Unit) and the like to realize the functions of the above-mentioned embodiment involved in the present invention. Then, the information processed by these devices is temporarily stored in a RAM (Random Access Memory) when processing, and then stored in various ROMs such as a Flash ROM (Read Only Memory) and a HDD (Hard Disk Drive), and is read, modified, and written by the CPU as needed.
[0358] It should be noted that a part of the terminal device 1 and the base station device 3 of the above embodiment may also be implemented by a computer. In this case, the program for implementing the control function may be recorded in a computer readable recording medium, and the program recorded in the recording medium may be read into a computer system and executed.
[0359] It should be noted that the "computer system" mentioned here refers to a computer system built into the terminal device 1 or the base station device 3, and includes hardware such as an OS and external devices. In addition, "computer-readable recording medium" refers to removable media such as a floppy disk, a magneto-optical disk, a ROM, a CD-ROM, and a storage device such as a hard disk built into the computer system.
[0360] Furthermore, "computer-readable recording medium" may also include: a recording medium that stores a program dynamically for a short period of time, such as a communication line when the program is transmitted via a network such as the Internet or a communication line such as a telephone line; and a recording medium that stores a program for a fixed period of time, such as a volatile memory inside a computer system that serves as a server or client in this case. In addition, the above program may be a program for realizing a part of the above functions, or a program that can realize the above functions by combining with a program already recorded in a computer system.
[0361] In addition, the base station device 3 in the above-mentioned embodiment can also be implemented as an aggregate (device group) composed of multiple devices. Each device constituting the device group can have a part or all of the functions or functional blocks of the base station device 3 involved in the above-mentioned embodiment. As a device group, it is sufficient to have all the functions or functional blocks of the base station device 3. In addition, the terminal device 1 involved in the above-mentioned embodiment can also communicate with the base station device as an aggregate.
[0362] In addition, the base station device 3 of the above-mentioned embodiment may be EUTRAN (Evolved Universal Terrestrial Radio Access Network) and / or NG-RAN (NextGenRAN, NR RAN). In addition, the base station device 3 of the above-mentioned embodiment may also have part or all of the functions of the upper node for eNodeB and / or gNB.
[0363] In addition, part or all of the terminal device 1 and the base station device 3 of the above-mentioned embodiment may be implemented as an LSI, which is typically an integrated circuit, or as a chipset. Each functional block of the terminal device 1 and the base station device 3 may be individually chip-based, or part or all of the functional blocks may be integrated and chip-based. In addition, the method of integrated circuitization is not limited to LSI, and may be implemented by a dedicated circuit or a general-purpose processor. In addition, when a technology for integrated circuitization that replaces LSI emerges with the advancement of semiconductor technology, an integrated circuit based on the technology may also be used.
[0364] In addition, in the above-mentioned 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 fixed or non-movable electronic devices installed indoors and outdoors, such as AV equipment, kitchen equipment, cleaning / washing equipment, air-conditioning equipment, office equipment, vending machines and other life equipment and other terminal devices or communication devices.
[0365] The embodiments of the present invention are described in detail with reference to the accompanying drawings, but the specific configuration is not limited to the present embodiment, and also includes design changes within the scope of the gist of the present invention. In addition, the present invention can be variously modified within the scope indicated by the claims, and the embodiments obtained by appropriately combining the technical solutions disclosed in different embodiments are also included in the technical scope of the present invention. In addition, it also includes a configuration obtained by replacing the elements that have the same effect as the elements recorded in the above-mentioned embodiments with each other. Industrial Applicability
[0366] The present invention can be used, for example, in a communication system, a communication device (such as a mobile phone device, a base station device, a wireless LAN device, or a sensor device), an integrated circuit (such as a communication chip), a program, or the like. Description of Reference Numerals
[0367] 1(1A, 1B, 1C): Terminal device 3: Base station device 10, 30: Wireless transceiver 10a, 30a: Wireless transmission unit 10b, 30b: Wireless receiving unit 11, 31: Antenna 12, 32: RF department 13, 33: Baseband 14, 34: Upper processing unit 15, 35: Media access control layer processing unit 16, 36: Radio resource control layer processing unit 91, 92, 93, 94: Search area set 300: Component carrier 301: Main cell 302, 303: Auxiliary cells 700: A collection of resource elements for PSS 710, 711, 712, 713: resource element set for PBCH and DMRS for PBCH 720: A collection of resource elements for SSS 3000: points 3001, 3002: Resource grid 3003, 3004: BWP 3011, 3012, 3013, 3014: Offset 3100, 3200: Public resource block set 900, 901: TA command 910, 911: Uplink transmission 920, 921: Uplink timing 930: Service cell
Claims
1. A terminal device, comprising: a transmitting unit, configured to transmit a first random access preamble in a first random access, sending a second random access preamble in a second random access; and a receiving unit, receiving a first timing advance TA command in the first random access, receiving a second TA command in the second random access, adjusting a first uplink timing in a serving cell based at least on the first TA command, adjusting a second uplink timing in the one serving cell based at least on the second TA command, Based on certain information, one of the first uplink timing and the second uplink timing is used.
2. The terminal device according to claim 1, wherein: The first random access is a contention-based random access (CBRA), The second random access is contention-free random access CFRA.
3. The terminal device according to claim 1 or 2, wherein: The certain information is any one of the transceiver point TRP information and the sub-timing advance group TAG, The receiving unit receives the certain information or a parameter including the certain information.
4. A base station device, comprising: a receiving unit, receiving a first random access preamble in a first random access, receiving a second random access preamble in a second random access; and a sending unit, sending a first timing advance TA command in the first random access, sending a second TA command in the second random access, adjusting a first uplink timing in a serving cell based at least on the first TA command, adjusting a second uplink timing in the one serving cell based at least on the second TA command, Based on certain information, one of the first uplink timing and the second uplink timing is used.
5. A communication method, the communication method being a communication method for a terminal device, comprising the following steps: sending a first random access preamble in a first random access, sending a second random access preamble in a second random access; and receiving a first timing advance TA command in the first random access, receiving a second TA command in the second random access, adjusting a first uplink timing in a serving cell based at least on the first TA command, adjusting a second uplink timing in the one serving cell based at least on the second TA command, Based on certain information, one of the first uplink timing and the second uplink timing is used.
