Patent Application
20240422753
The present invention relates to a terminal device, a base station device, and a communication method.
In the 3rd Generation Partnership Project (3GPP), a radio access method and a radio network for cellular mobile communications (hereinafter, referred to as Long Term Evolution, or Evolved Universal Terrestrial Radio Access) have been studied. In LTE (Long Term Evolution), a base station device is also referred to as an evolved NodeB (eNodeB), and a terminal device is also referred to as a User Equipment (UE). LTE is a cellular communication system in which multiple areas are deployed in a cellular structure, with each of the multiple areas being covered by a base station device. A single base station device may manage multiple cells. Evolved Universal Terrestrial Radio Access is also referred as E-UTRA.
In the 3GPP, the next generation standard (New Radio: NR) has been studied in order to make a proposal to the International-Mobile-Telecommunication-2020 (IMT-2020) which is a standard for the next generation mobile communication system defined by the International Telecommunications Union (ITU). NR has been expected to satisfy a requirement considering three scenarios of enhanced Mobile BroadBand (eMBB), massive Machine Type Communication (mMTC), and Ultra Reliable and Low Latency Communication (URLLC), in a single technology framework.
For example, wireless communication devices may communicate with one or more devices using a communication structure. However, the communication structure used may only offer limited flexibility and/or efficiency. As illustrated by this discussion, systems and methods that improve communication flexibility and/or efficiency may be beneficial.
floor (CX) may be a floor function for real number CX. For example, floor (CX) may be a function that provides the largest integer within a range that does not exceed the real number CX. ceil (DX) may be a ceiling function to a real number DX. For example, ceil (DX) may be a function that provides the smallest integer within the range not less than the real number DX. mod (EX, FX) may be a function that provides the remainder obtained by dividing EX by FX. mod (EX, FX) may be a function that provides a value which corresponds to the remainder of dividing EX by FX. It is exp (GX)=e{circumflex over ( )}GX. Here, e is Napier number. (HX){circumflex over ( )}(IX) indicates IX to the power of HX.
In a wireless communication system according to one aspect of the present embodiment, at least OFDM (Orthogonal Frequency Division Multiplex) is used. An OFDM symbol is a unit of time domain of the OFDM. The OFDM symbol includes at least one or more subcarriers. An OFDM symbol is converted to a time-continuous signal in baseband signal generation. In downlink, at least CP-OFDM (Cyclic Prefix-Orthogonal Frequency Division Multiplex) is used. In uplink, either CP-OFDM or DFT-s-OFDM (Discrete Fourier Transform-spread-Orthogonal Frequency Division Multiplex) is used. DFT-s-OFDM may be given by applying transform precoding to CP-OFDM. CP-OFDM is OFDM using CP (Cyclic Prefix).
The OFDM symbol may be a designation including a CP added to the OFDM symbol. That is, an OFDM symbol may be configured to include the OFDM symbol and a CP added to the OFDM symbol.
The base station device 3 may be configured to include one or more transmission devices (or transmission points, transmission devices, reception devices, transmission points, reception points). When the base station device 3 is configured by a plurality of transmission devices, each of the plurality of transmission devices may be arranged at a different position.
The base station device 3 may provide one or more serving cells. A serving . . . cell may be defined as a set of resources used for wireless communication. A serving cell is also referred to as a cell.
A serving cell may be configured to include at least one downlink component carrier (downlink carrier) and/or one uplink component carrier (uplink carrier). A serving cell may be configured to include at least two or more downlink component carriers and/or two or more uplink component carriers. A downlink component carrier and an uplink component carrier are also referred to as component carriers (carriers).
For example, one resource grid may be provided for one component carrier. For example, one resource grid may be provided for one component carrier and a subcarrier-spacing configuration u. A subcarrier-spacing configuration u is also referred to as numerology. A resource grid includes Nsize, ugrid, xNRBsc subcarriers. The resource grid starts from a common resource block with index Nstart, ugrid. The common resource block with the index Nstart, ugrid is also referred to as a reference point of the resource grid. The resource grid includes Nsubframe, usymb OFDM symbols. The subscript x indicates the transmission direction, and indicates either downlink or uplink. One resource grid is provided for an antenna port p, a subcarrier-spacing configuration u, and a transmission direction x.
Resource grid is also referred to as carrier.
Nsize, ugrid, x and Nstart, ugrid are given based at least on a higher-layer parameter (e.g. referred to as higher-layer parameter CarrierBandwidth). The higher-layer parameter is used to define one or more SCS (SubCarrier-Spacing) specific carriers. One resource grid corresponds to one SCS specific carrier. One component carrier may comprise one or more SCS specific carriers. The SCS specific carrier may be included in a system information block (SIB). For each SCS specific carrier, a subcarrier-spacing configuration u may be provided.
In the wireless communication system according to an aspect of the present embodiment, a time unit Tc may be used to represent the length of the time domain. The time unit Tc is Tc=1/(dfmax*Nf). It is dfmax=480 kHz. It is Nf=4096. The constant k is k=dfmax*Nf/(dfrefNf, ref)=64. dfref is 15 kHz. Nf, ref is 2048.
Transmission of signals in the downlink and/or transmission of signals in the uplink may be organized into radio frames (system frames, frames) of length Tf. It is Tf=(dfmax Nf/100)*Ts=10 ms. One radio frame is configured to include ten subframes. The subframe length is Tsf=(dfmaxNf/1000) Ts=1 ms. The number of OFDM symbols per subframe is Nsubframe, usymb=NslotsymbNsubframe, uslot.
For a subcarrier-spacing configuration u, the number of slots included in a subframe and indexes may be given. For example, slot index nus may be given in ascending order with an integer value ranging from 0 to Nsubframe,uslot−1 in a subframe. For subcarrier-spacing configuration u, the number of slots included in a radio frame and indexes of slots included in the radio frame may be given. Also, the slot index nus, f may be given in ascending order with an integer value ranging from 0 to Nframe,uslot−1 in the radio frame. Consecutive Nslotsymb OFDM symbols may be included in one slot. It is Nslotsymb=14.
The component carrier 300 is a band having a predetermined width in the frequency domain.
Point (Point) 3000 is an identifier for identifying a subcarrier. Point 3000 is also referred to as point A. The common resource block (CRB: Common resource block) set 3100 is a set of common resource blocks for the subcarrier-spacing configuration u1.
Among the common resource block-set 3100, the common resource block including the point 3000 (the block indicated by the upper right diagonal line in
The offset 3011 is an offset from the reference point of the common resource block-set 3100 to the reference point of the resource grid 3001. The offset 3011 is indicated by the number of common resource blocks which is relative to the subcarrier-spacing configuration-u1. The resource-grid 3001 includes Nsize,ugrid1,x common resource blocks starting from the reference point of the resource grid 3001.
The offset 3013 is an offset from the reference point of the resource grid 3001 to the reference point (Nstart,uBWP,il) of the BWP (Band Width Part) 3003 of the index i1.
Common resource block-set 3200 is a set of common resource blocks with respect to subcarrier-spacing configuration u2.
A common resource block including the point 3000 (a block indicated by a upper left diagonal line in
The offset 3012 is an offset from the reference point of the common resource block-set 3200 to the reference point of the resource grid 3002. The offset 3012 is indicated by the number of common resource blocks for subcarrier-spacing configuration u=u2. The resource grid 3002 includes Nsize,ugrid2,x common resource blocks starting from the reference point of the resource grid 3002.
The offset 3014 is an offset from the reference point of the resource grid 3002 to the reference point (Nstart,uBWP,i2) of the BWP 3004 with index i2.
A resource block (RB: Resource Block) includes NRBsc consecutive subcarriers. A resource block is a generic name of a common resource block, a physical resource block (PRB: Physical Resource Block), and a virtual resource block (VRB: Virtual Resource Block). It is NRBsc=12.
A resource block unit is a set of resources that corresponds to one OFDM symbol in one resource block. That is, one resource block unit includes 12 resource elements which corresponds to one OFDM symbol in one resource block.
Common resource blocks for a subcarrier-spacing configuration u are indexed in ascending order from 0 in the frequency domain in a common resource block-set. The common resource block with index 0 for the subcarrier-spacing configuration u includes (or collides with, matches) the point 3000. The index nuCRB of the common resource block with respect to the subcarrier-spacing configuration u satisfies the relationship of nuCRB=ceil (ksc/NRBsc). The subcarrier with ksc=0 is a subcarrier with the same center frequency as the center frequency of the subcarrier which corresponds to the point 3000.
Physical resource blocks for a subcarrier-spacing configuration u are indexed in ascending order from 0 in the frequency domain in a BWP. The index nuPRB of the physical resource block with respect to the subcarrier-spacing configuration u satisfies the relationship of nuCRB=nuPRB+Nstart,uBWP,i. The Nstart,uBWP,i indicates the reference point of BWP with index i.
A BWP is defined as a subset of common resource blocks included in the resource grid. The BWP includes Nsize,uBWP,i common resource blocks starting from the reference points Nstart,uBWP,i. A BWP for the downlink component carrier is also referred to as a downlink BWP. A BWP for the uplink component carrier is also referred to as an uplink BWP.
An antenna port is defined such that the channel over which a symbol on the antenna port is conveyed can be inferred from the channel over which another symbol on the same antenna port is conveyed. For example, the channel may correspond to a physical channel. For example, the symbols may correspond to OFDM symbols. For example, the symbols may correspond to resource block units. For example, the symbols may correspond to resource elements.
Two antenna ports are said to be QCL (Quasi Co-Located) if the large-scale properties of the channel over which a symbol on one antenna port is conveyed can be inferred from the channel over which a symbol on the other antenna port is conveyed. The large-scale properties include one or more of delay spread, Doppler spread, Doppler shift, average gain, average delay, and spatial Rx parameters.
Carrier aggregation may be communication using a plurality of aggregated serving cells. Carrier aggregation may be communication using a plurality of aggregated component carriers. Carrier aggregation may be communication using a plurality of aggregated downlink component carriers. Carrier aggregation may be communication using a plurality of aggregated uplink component carriers.
The wireless transmission/reception unit 30 includes at least a part of or all of a wireless transmission unit 30a and a wireless reception unit 30b. The configuration of the baseband unit 33 included in the wireless transmission unit 30a and the configuration of the baseband unit 33 included in the wireless reception unit 30b may be the same or different. The configuration of the RF unit 32 included in the wireless transmission unit 30a and the configuration of the RF unit 32 included in the wireless reception unit 30b may be the same or different. The configuration of the antenna unit 31 included in the wireless transmission unit 30a and the configuration of the antenna unit 31 included in the wireless reception unit 30b may be the same or different.
The higher-layer processing unit 34 provides downlink data (a transport block) to the wireless transmission/reception unit 30 (or the wireless transmission unit 30a). The higher-layer processing unit 34 performs processing of a medium access control (MAC) layer, a packet data convergence protocol layer (PDCP layer), a radio link control layer (RLC layer) and/or an RRC layer.
The medium access control layer processing unit 35 included in the higher-layer processing unit 34 performs processing of the MAC layer.
The radio resource control layer processing unit 36 included in the higher-layer processing unit 34 performs the process of the RRC layer. The radio resource control layer processing unit 36 manages various configuration information/parameters (RRC parameters) of the terminal device 1. The radio resource control layer processing unit 36 configures an RRC parameter based on the RRC message received from the terminal-device 1.
The wireless transmission/reception unit 30 (or the wireless transmission unit 30a) performs processing such as encoding and modulation. The wireless transmission/reception unit 30 (or the wireless transmission unit 30a) generates a physical signal by encoding and modulating the downlink data. The wireless transmission/reception unit 30 (or the wireless transmission unit 30a) converts OFDM symbols in the physical signal to a baseband signal by conversion to a time-continuous signal. The wireless transmission/reception unit 30 (or the wireless transmission unit 30a) transmits the baseband signal (or the physical signal) to the terminal device 1 via radio frequency. The wireless transmission/reception unit 30 (or the wireless transmission unit 30a) may arrange the baseband signal (or the physical signal) on a component carrier and transmit the baseband signal (or the physical signal) to the terminal device 1.
The wireless transmission/reception unit 30 (or the wireless reception unit 30b) performs processing such as demodulation and decoding. The wireless transmission/reception unit 30 (or the wireless reception unit 30b) separates, demodulates and decodes the received physical signal, and provides the decoded information to the higher-layer processing unit 34. The wireless transmission/reception unit 30 (or the wireless reception unit 30b) may perform the channel access procedure prior to the transmission of the physical signal.
The RF unit 32 demodulates the physical signal received via the antenna unit 31 into a baseband signal (down convert), and/or removes extra frequency components. The RF unit 32 provides the processed analog signal to the baseband unit 33.
The baseband unit 33 converts an analog signal (signals on radio frequency) input from the RF unit 32 into a digital signal (a baseband signal). The baseband unit 33 separates a portion which corresponds to CP (Cyclic Prefix) from the digital signal. The baseband unit 33 performs Fast Fourier Transformation (FFT) on the digital signal from which the CP has been removed. The baseband unit 33 provides the physical signal in the frequency domain.
The baseband unit 33 performs Inverse Fast Fourier Transformation (IFFT) on downlink data to generate an OFDM symbol, adds a CP to the generated OFDM symbol, generates a digital signal (baseband signal), and convert the digital signal into an analog signal. The baseband unit 33 provides the analog signal to the RF unit 32.
The RF unit 32 removes extra frequency components from the analog signal (signals on radio frequency) input from the baseband unit 33, up-converts the analog signal to a radio frequency, and transmits it via the antenna unit 31. The RF unit 32 may have a function of controlling transmission power. The RF unit 32 is also referred to as a transmission power control unit.
At least one or more serving cells (or one or more component carriers, one or more downlink component carriers, one or more uplink component carriers) may be configured for the terminal device 1.
Each of the serving cells set for the terminal device 1 may be any of PCell (Primary cell), PSCell (Primary SCG cell), and SCell (Secondary Cell).
A PCell is a serving cell included in a MCG (Master Cell Group). A PCell is a cell (implemented cell) which performs an initial connection establishment procedure or a connection re-establishment procedure by the terminal device 1.
A PSCell is a serving cell included in a SCG (Secondary Cell Group). A PSCell is a serving cell in which random-access is performed by the terminal device 1 in a reconfiguration procedure with synchronization (Reconfiguration with synchronization).
A SCell may be included in either a MCG or a SCG.
The serving cell group (cell group) is a designation including at least MCG and SCG. The serving cell group may include one or more serving cells (or one or more component carriers). One or more serving cells (or one or more component carriers) included in the serving cell group may be operated by carrier aggregation.
One or more downlink BWPs may be configured for each serving cell (or each downlink component carrier). One or more uplink BWPs may be configured for each serving cell (or each uplink component carrier).
Among the one or more downlink BWPs set for the serving cell (or the downlink component carrier), one downlink BWP may be set as an active downlink BWP (or one downlink BWP may be activated). Among the one or more uplink BWPs set for the serving cell (or the uplink component carrier), one uplink BWP may be set as an active uplink BWP (or one uplink BWP may be activated).
A PDSCH, a PDCCH, and a CSI-RS may be received in the active downlink BWP. The terminal device 1 may receive the PDSCH, the PDCCH, and the CSI-RS in the active downlink BWP. A PUCCH and a PUSCH may be sent on the active uplink BWP. The terminal device 1 may transmit the PUCCH and the PUSCH in the active uplink BWP. The active downlink BWP and the active uplink BWP are also referred to as active BWP.
The PDSCH, the PDCCH, and the CSI-RS may not be received in downlink BWPs (inactive downlink BWPs) other than the active downlink BWP. The terminal device 1 may not receive the PDSCH, the PDCCH, and the CSI-RS in the downlink BWPs which are other than the active downlink BWP. The PUCCH and the PUSCH do not need to be transmitted in uplink BWPs (inactive uplink BWPs) other than the active uplink BWP. The terminal device 1 may not transmit the PUCCH and the PUSCH in the uplink BWPs which is other than the active uplink BWP. The inactive downlink BWP and the inactive uplink BWP are also referred to as inactive BWP.
Downlink BWP switching deactivates an active downlink BWP and activates one of inactive downlink BWPs which are other than the active downlink BWP. The downlink BWP switching may be controlled by a BWP field included in a downlink control information. The downlink BWP switching may be controlled based on higher-layer parameters.
Uplink BWP switching is used to deactivate an active uplink BWP and activate any inactive uplink BWP which is other than the active uplink BWP. Uplink BWP switching may be controlled by a BWP field included in a downlink control information. The uplink BWP switching may be controlled based on higher-layer parameters.
Among the one or more downlink BWPs set for the serving cell, two or more downlink BWPs may not be set as active downlink BWPs. For the serving cell, one downlink BWP may be active at a certain time.
Among the one or more uplink BWPs set for the serving cell, two or more uplink BWPs may not be set as active uplink BWPs. For the serving cell, one uplink BWP may be active at a certain time.
The wireless transmission/reception unit 10 includes at least a part of or all of a wireless transmission unit 10a and a wireless reception unit 10b. The configuration of the baseband unit 13 included in the wireless transmission unit 10a and the configuration of the baseband unit 13 included in the wireless reception unit 10b may be the same or different. The configuration of the RF unit 12 included in the wireless transmission unit 10a and the RF unit 12 included in the wireless reception unit 10b may be the same or different. The configuration of the antenna unit 11 included in the wireless transmission unit 10a and the configuration of the antenna unit 11 included in the wireless reception unit 10b may be the same or different.
The higher-layer processing unit 14 provides uplink data (a transport block) to the wireless transmission/reception unit 10 (or the wireless transmission unit 10a). The higher-layer processing unit 14 performs processing of a MAC layer, a packet data integration protocol layer, a radio link control layer, and/or an RRC layer.
The medium access control layer processing unit 15 included in the higher-layer processing unit 14 performs processing of the MAC layer.
The radio resource control layer processing unit 16 included in the higher-layer processing unit 14 performs the process of the RRC layer. The radio resource control layer processing unit 16 manages various configuration information/parameters (RRC-parameters) of the terminal device 1. The radio resource control layer processing unit 16 configures RRC parameters based on the RRC message received from the base station device 3.
The wireless transmission/reception unit 10 (or the wireless transmission unit 10a) performs processing such as encoding and modulation. The wireless transmission/reception unit 10 (or the wireless transmission unit 10a) generates a physical signal by encoding and modulating the uplink data. The wireless transmission/reception unit 10 (or the wireless transmission unit 10a) converts OFDM symbols in the physical signal to a baseband signal by conversion to a time-continuous signal. The wireless transmission/reception unit 10 (or the wireless transmission unit 10a) transmits the baseband signal (or the physical signal) to the base station device 3 via radio frequency. The wireless transmission/reception unit 10 (or the wireless transmission unit 10a) may arrange the baseband signal (or the physical signal) on a BWP (active uplink BWP) and transmit the baseband signal (or the physical signal) to the base station device 3.
The wireless transmission/reception unit 10 (or the wireless reception unit 10b) performs processing such as demodulation and decoding. The wireless transmission/reception unit 10 (or the wireless reception unit 10b) may receive a physical signal in a BWP (active downlink BWP) of a serving cell. The wireless transmission/reception unit 10 (or the wireless reception unit 10b) separates, demodulates and decodes the received physical signal, and provides the decoded information to the higher-layer processing unit 14. The wireless transmission/reception unit 10 (or the wireless reception unit 10b) may perform the channel access procedure prior to the transmission of the physical signal.
The RF unit 12 demodulates the physical signal received via the antenna unit 11 into a baseband signal (down convert), and/or removes extra frequency components. The RF unit 12 provides the processed analog signal to the baseband unit 13.
The baseband unit 13 converts an analog signal (signals on radio frequency) input from the RF unit 12 into a digital signal (a baseband signal). The baseband unit 13 separates a portion which corresponds to CP from the digital signal, performs fast Fourier transformation on the digital signal from which the CP has been removed, and provides the physical signal in the frequency domain.
The baseband unit 13 performs inverse fast Fourier transformation on uplink data to generate an OFDM symbol, adds a CP to the generated OFDM symbol, generates a digital signal (baseband signal), and convert the digital signal into an analog signal. The baseband unit 13 provides the analog signal to the RF unit 12.
The RF unit 12 removes extra frequency components from the analog signal (signals on radio frequency) input from the baseband unit 13, up-converts the analog signal to a radio frequency, and transmits it via the antenna unit 11 The RF unit 12 may have a function of controlling transmission power. The RF unit 12 is also referred to as a transmission power control unit.
Hereinafter, physical signals (signals) will be described.
Physical signal is a generic term for downlink physical channels, downlink physical signals, uplink physical channels, and uplink physical channels. The physical channel is a generic term for downlink physical channels and uplink physical channels.
An uplink physical channel may correspond to a set of resource elements that carry information originating from the higher-layer and/or uplink control information. The uplink physical channel may be a physical channel used in an uplink component carrier. The uplink physical channel may be transmitted by the terminal device 1. The uplink physical channel may be received by the base station device 3. In the wireless communication system according to one aspect of the present embodiment, at least part or all of PUCCH (Physical Uplink Control CHannel), PUSCH (Physical Uplink Shared CHannel), and PRACH (Physical Random Access CHannel) may be used.
A PUCCH may be used to transmit uplink control information (UCI: Uplink Control Information). The PUCCH may be sent to deliver (transmission, convey) uplink control information. The uplink control information may be mapped to (or arranged in) the PUCCH. The terminal device 1 may transmit PUCCH in which uplink control information is arranged. The base station device 3 may receive the PUCCH in which the uplink control information is arranged.
Uplink control information (uplink control information bit, uplink control information sequence, uplink control information type) includes at least part or all of channel state information (CSI: Channel State Information), scheduling request (SR: Scheduling Request), and HARQ-ACK (Hybrid Automatic Repeat request ACKnowledgement).
Channel state information is conveyed by using channel state information bits or a channel state information sequence. Scheduling request is also referred to as a scheduling request bit or a scheduling request sequence. HARQ-ACK information is also referred to as a HARQ-ACK information bit or a HARQ-ACK information sequence.
HARQ-ACK information may include HARQ-ACK status which corresponds to a transport block (TB: Transport block, MAC PDU: Medium Access Control Protocol Data Unit, DL-SCH: Downlink-Shared Channel, UL-SCH: Uplink-Shared Channel, PDSCH: Physical Downlink Shared CHannel, PUSCH: Physical Uplink Shared CHannel). The HARQ-ACK status may indicate ACK (acknowledgement) or NACK (negative-acknowledgement) corresponding to the transport block. The ACK may indicate that the transport block has been successfully decoded. The NACK may indicate that the transport block has not been successfully decoded. The HARQ-ACK information may include a HARQ-ACK codebook that includes one or more HARQ-ACK status (or HARQ-ACK bits).
For example, the correspondence between the HARQ-ACK information and the transport block may mean that the HARQ-ACK information and the PDSCH used for transmission of the transport block correspond.
HARQ-ACK status may indicate ACK or NACK which correspond to one CBG (Code Block Group) included in the transport block.
The scheduling request may at least be used to request PUSCH (or UL-SCH) resources for new transmission. The scheduling request may be used to indicate either a positive SR or a negative SR. The fact that the scheduling request indicates a positive SR is also referred to as “a positive SR is sent”. The positive SR may indicate that the PUSCH (or UL-SCH) resource for initial transmission is requested by the terminal device 1. A positive SR may indicate that a higher-layer is to trigger a scheduling request. The positive SR may be sent when the higher-layer instructs to send a scheduling request. The fact that the scheduling request bit indicates a negative SR is also referred to as “a negative SR is sent”. A negative SR may indicate that the PUSCH (or UL-SCH) resource for initial transmission is not requested by the terminal device 1. A negative SR may indicate that the higher-layer does not trigger a scheduling request. A negative SR may be sent if the higher-layer is not instructed to send a scheduling request.
The channel state information may include at least part or all of a channel quality indicator (CQI), a precoder matrix indicator (PMI), and a rank indicator (RI). CQI is an indicator related to channel quality (e.g., propagation quality) or physical channel quality, and PMI is an indicator related to a precoder. RI is an indicator related to transmission rank (or the number of transmission layers).
Channel state information may be provided at least based on receiving one or more physical signals (e.g., one or more CSI-RSs) used at least for channel measurement. The channel state information may be selected by the terminal device 1 at least based on receiving one or more physical signals used for channel measurement. Channel measurements may include interference measurements.
A PUCCH may correspond to a PUCCH format. A PUCCH may be a set of resource elements used to convey a PUCCH format. A PUCCH may include a PUCCH format. A PUCCH format may include UCI.
A PUSCH may be used to transmit uplink data (a transport block) and/or uplink control information. A PUSCH may be used to transmit uplink data (a transport block) corresponding to a UL-SCH and/or uplink control information. A PUSCH may be used to convey uplink data (a transport block) and/or uplink control information. A PUSCH may be used to convey uplink data (a transport block) corresponding to a UL-SCH and/or uplink control information. Uplink data (a transport block) may be arranged in a PUSCH. Uplink data (a transport block) corresponding to UL-SCH may be arranged in a PUSCH. Uplink control information may be arranged to a PUSCH. The terminal device 1 may transmit a PUSCH in which uplink data (a transport block) and/or uplink control information is arranged. The base station device 3 may receive a PUSCH in which uplink data (a transport block) and/or uplink control information is arranged.
A PRACH may be used to transmit a random-access preamble. The PRACH may be used to convey a random-access preamble. The sequence Xu, v (n) of the PRACH is defined by Xu, v (n)=xu (mod(n+Cv, LRA)). The xu may be a ZC sequence (Zadoff-Chu sequence). The xu may be defined by xu=exp(−jpui (i+1)/LRA). The j is an imaginary unit. The p is the circle ratio. The Cv corresponds to cyclic shift of the PRACH. LRA corresponds to the length of the PRACH. The LRA may be 839 or 139 or another value. The i is an integer in the range of 0 to LRA−1. The u is a sequence index for the PRACH. The terminal device 1 may transmit the PRACH. The base station device 3 may receive the PRACH.
For a given PRACH opportunity, 64 random-access preambles are defined. The random-access preamble is specified (determined, given) at least based on the cyclic shift Cv of the PRACH and the sequence index u for the PRACH.
An uplink physical signal may correspond to a set of resource elements. The uplink physical signal may not carry information generated in the higher-layer. The uplink physical signal may be a physical signal used in the uplink component carrier. The terminal device 1 may transmit an uplink physical signal. The base station device 3 may receive the uplink physical signal. In the radio communication system according to one aspect of the present embodiment, at least a part or all of UL DMRS (UpLink Demodulation Reference Signal), SRS (Sounding Reference Signal), UL PTRS (UpLink Phase Tracking Reference Signal) may be used.
UL DMRS is a generic name of a DMRS for a PUSCH and a DMRS for a PUCCH.
A set of antenna ports of a DMRS for a PUSCH (a DMRS associated with a PUSCH, a DMRS included in a PUSCH, a DMRS which corresponds to a PUSCH) may be given based on a set of antenna ports for the PUSCH. That is, the set of DMRS antenna ports for the PUSCH may be the same as the set of antenna ports for the PUSCH.
Transmission of a PUSCH and transmission of a DMRS for the PUSCH may be indicated (or scheduled) by one DCI format. The PUSCH and the DMRS for the PUSCH may be collectively referred to as a PUSCH. Transmission of the PUSCH may be transmission of the PUSCH and the DMRS for the PUSCH.
A PUSCH may be estimated from a DMRS for the PUSCH. That is, propagation path of the PUSCH may be estimated from the DMRS for the PUSCH.
A set of antenna ports of a DMRS for a PUCCH (a DMRS associated with a PUCCH, a DMRS included in a PUCCH, a DMRS which corresponds to a PUCCH) may be identical to a set of antenna ports for the PUCCH.
Transmission of a PUCCH and transmission of a DMRS for the PUCCH may be indicated (or triggered) by one DCI format. The arrangement of the PUCCH in resource elements (resource element mapping) and/or the arrangement of the DMRS in resource elements for the PUCCH may be provided at least by one PUCCH format. The PUCCH and the DMRS for the PUCCH may be collectively referred to as PUCCH. Transmission of the PUCCH may be transmission of the PUCCH and the DMRS for the PUCCH.
A PUCCH may be estimated from a DMRS for the PUCCH. That is, propagation path of the PUCCH may be estimated from the DMRS for the PUCCH.
A downlink physical channel may correspond to a set of resource elements that carry information originating from the higher-layer and/or downlink control information. The downlink physical channel may be a physical channel used in the downlink component carrier. The base station device 3 may transmit the downlink physical channel. The terminal device 1 may receive the downlink physical channel. In the wireless communication system according to one aspect of the present embodiment, at least a part or all of PBCH (Physical Broadcast Channel), PDCCH (Physical Downlink Control Channel), and PDSCH (Physical Downlink Shared Channel) may be used.
The PBCH may be used to transmit a MIB (Master Information Block) and/or physical layer control information. The physical layer control information is a kind of downlink control information. The PBCH may be sent to deliver the MIB and/or the physical layer control information. A BCH may be mapped (or corresponding) to the PBCH. The terminal device 1 may receive the PBCH. The base station device 3 may transmit the PBCH. The physical layer control information is also referred to as a PBCH payload and a PBCH payload related to timing. The MIB may include one or more higher-layer parameters.
Physical layer control information includes 8 bits. The physical layer control information may include at least part or all of 0A to 0D. The 0A is radio frame information. The 0B is half radio frame information (half system frame information). The 0C is SS/PBCH block index information. The 0D is subcarrier offset information.
The radio frame information is used to indicate a radio frame in which the PBCH is transmitted (a radio frame including a slot in which the PBCH is transmitted). The radio frame information is represented by 4 bits. The radio frame information may be represented by 4 bits of a radio frame indicator. The radio frame indicator may include 10 bits. For example, the radio frame indicator may at least be used to identify a radio frame from index 0 to index 1023.
The half radio frame information is used to indicate whether the PBCH is transmitted in first five subframes or in second five subframes among radio frames in which the PBCH is transmitted. Here, the half radio frame may be configured to include five subframes. The half radio frame may be configured by five subframes of the first half of ten subframes included in the radio frame. The half radio frame may be configured by five subframes in the second half of ten subframes included in the radio frame.
The SS/PBCH block index information is used to indicate an SS/PBCH block index. The SS/PBCH block index information may be represented by 3 bits. The SS/PBCH block index information may consist of 3 bits of an SS/PBCH block index indicator. The SS/PBCH block index indicator may include 6 bits. The SS/PBCH block index indicator may at least be used to identify an SS/PBCH block from index 0 to index 63 (or from index 0 to index 3, from index 0 to index 7, from index 0 to index 9, from index 0 to index 19, etc.).
The subcarrier offset information is used to indicate subcarrier offset. The subcarrier offset information may be used to indicate the difference between the first subcarrier in which the PBCH is arranged and the first subcarrier in which the control resource set with index 0 is arranged.
A PDCCH may be used to transmit downlink control information (DCI). A PDCCH may be transmitted to deliver downlink control information. Downlink control information may be mapped to a PDCCH. The terminal device 1 may receive a PDCCH in which downlink control information is arranged. The base station device 3 may transmit the PDCCH in which the downlink control information is arranged.
Downlink control information may correspond to a DCI format. Downlink control information may be included in a DCI format. Downlink control information may be arranged in each field of a DCI format.
DCI format is a generic name for DCI format 0_0, DCI format 0_1, DCI format 1_0, and DCI format 1_1. Uplink DCI format is a generic name of the DCI format 0_0 and the DCI format 0_1. Downlink DCI format is a generic name of the DCI format 1_0 and the DCI format 1_1.
The DCI format 0_0 is at least used for scheduling a PUSCH for a cell (or a PUSCH arranged on a cell). The DCI format 0_0 includes at least a part or all of fields 1A to IE. The 1A is a DCI format identification field (Identifier field for DCI formats). The 1B is a frequency domain resource assignment field (FDRA field). The 1C is a time domain resource assignment field (TDRA field). The 1D is a frequency-hopping flag field. The 1E is an MCS field (Modulation-and-Coding-Scheme field).
The DCI format identification field may indicate whether the DCI format including the DCI format identification field is an uplink DCI format or a downlink DCI format. The DCI format identification field included in the DCI format 0_0 may indicate 0 (or may indicate that the DCI format 0_0 is an uplink DCI format).
The frequency domain resource assignment field included in the DCI format 0_0 may be at least used to indicate the assignment (allocation) of frequency resources for a PUSCH. The frequency domain resource assignment field included in the DCI format 0_0 may be at least used to indicate the assignment (allocation) of frequency resources for a PUSCH scheduled by the DCI format 0_0.
The time domain resource assignment field included in the DCI format 0_0 may be at least used to indicate the assignment of time resources for a PUSCH. The time domain resource assignment field included in the DCI format 0_0 may be at least used to indicate the assignment of time resources for a PUSCH scheduled by the DCI format 0_0.
The frequency-hopping flag field may be at least used to indicate whether frequency-hopping is applied to a PUSCH. The frequency-hopping flag field may be at least used to indicate whether frequency-hopping is applied to a PUSCH scheduled by the DCI format 0_0.
The MCS field included in the DCI format 0_0 may be at least used to indicate a modulation scheme for a PUSCH and/or a part or all of a target coding rate for the PUSCH. The MCS field included in the DCI format 0_0 may be at least used to indicate a modulation scheme for a PUSCH scheduled by the DCI format 0_0 and/or a part or all of a target coding rate for the PUSCH. A size of a transport block (TBS: Transport Block Size) of a PUSCH may be given based at least on a target coding rate and a part or all of a modulation scheme for the PUSCH.
The DCI format 0_0 may not include fields used for a CSI request. That is, CSI may not be requested by the DCI format 0_0.
The DCI format 0_0 may not include a carrier indicator field. An uplink component carrier on which a PUSCH scheduled by the DCI format 0_0 is arranged may be the same as an uplink component carrier on which a PDCCH including the DCI format 0_0 is arranged.
The DCI format 0_0 may not include a BWP field. An uplink BWP on which a PUSCH scheduled by the DCI format 0_0 is arranged may be the same as an uplink BWP on which a PDCCH including the DCI format 0_0 is arranged.
The DCI format 0_1 is at least used for scheduling of a PUSCH for a cell (or arranged on a cell). The DCI format 0_1 includes at least a part or all of fields 2A to 2H. The 2A is a DCI format identification field. The 2B is a frequency domain resource assignment field. The 2C is a time domain-resource assignment field. The 2D is a frequency-hopping flag field. The 2E is an MCS field. The 2F is a CSI request field. The 2G is a BWP field. The 2H is a carrier indicator field.
The DCI format identification field included in the DCI format 0_1 may indicate 0 (or may indicate that the DCI format 0_1 is an uplink DCI format).
The frequency domain resource assignment field included in the DCI format 0_1 may be at least used to indicate the assignment of frequency resources for a PUSCH. The frequency domain resource assignment field included in the DCI format 0_1 may be at least used to indicate the assignment of frequency resources for a PUSCH scheduled by the DCI format.
The time domain resource assignment field included in the DCI format 0_1 may be at least used to indicate the assignment of time resources for a PUSCH. The time domain resource assignment field included in DCI format 0_1 may be at least used to indicate the assignment of time resources for a PUSCH scheduled by the DCI format 0_1.
The frequency-hopping flag field may be at least used to indicate whether frequency-hopping is applied to a PUSCH scheduled by the DCI format 0_1.
The MCS field included in the DCI format 0_1 may be at least used to indicate a modulation scheme for a PUSCH and/or a part or all of a target coding rate for the PUSCH. The MCS field included in the DCI format 0_1 may be at least used to indicate a modulation scheme for a PUSCH scheduled by the DCI format and/or part or all of a target coding rate for the PUSCH.
When the DCI format 0_1 includes the BWP field, the BWP field may be used to indicate an uplink BWP on which a PUSCH scheduled by the DCI format 0_1 is arranged. When the DCI format 0_1 does not include the BWP field, an uplink BWP on which a PUSCH is arranged may be the active uplink BWP. When the number of uplink BWPs configured in the terminal device 1 in a uplink component carrier is two or more, the number of bits for the BWP field included in the DCI format 0_1 used for scheduling a PUSCH arranged on the uplink component carrier may be one or more. When the number of uplink BWPs configured in the terminal device 1 in a uplink component carrier is one, the number of bits for the BWP field included in the DCI format 0_1 used for scheduling a PUSCH arranged on the uplink component carrier may be zero.
The CSI request field is at least used to indicate CSI reporting.
If the DCI format 0_1 includes the carrier indicator field, the carrier indicator field may be used to indicate an uplink component carrier (or a serving cell) on which a PUSCH is arranged. When the DCI format 0_1 does not include the carrier indicator field, a serving cell on which a PUSCH is arranged may be the same as the serving cell on which a PDCCH including the DCI format 0_1 used for scheduling of the PUSCH is arranged. When the number of uplink component carriers (or the number of serving cells) configured in the terminal device 1 in a serving cell group is two or more (when uplink carrier aggregation is operated in a serving cell group), or when cross-carrier scheduling is configured for the serving cell group, the number of bits for the carrier indicator field included in the DCI format 0_1 used for scheduling a PUSCH arranged on the serving cell group may be one or more (e.g., 3). When the number of uplink component carriers (or the number of serving cells) configured in the terminal device 1 in a serving cell group is one (or when uplink carrier aggregation is not operated in a serving cell group), or when the cross-carrier scheduling is not configured for the serving cell group, the number of bits for the carrier indicator field included in the DCI format 0_1 used for scheduling of a PUSCH arranged on the serving cell group may be zero.
The DCI format 1_0 is at least used for scheduling of a PDSCH for a cell (arranged on a cell). The DCI format 1_0 includes at least a part or all of fields 3A to 3F. The 3A is a DCI format identification field. The 3B is a frequency domain resource assignment field. The 3C is a time domain resource assignment field. The 3D is an MCS field. The 3E is a PDSCH-to-HARQ-feedback indicator field. The 3F is a PUCCH resource indicator field.
The DCI format identification field included in the DCI format 1_0 may indicate 1 (or may indicate that the DCI format 1_0 is a downlink DCI format).
The frequency domain resource assignment field included in the DCI format 1_0 may be at least used to indicate the assignment of frequency resources for a PDSCH. The frequency domain resource assignment field included in the DCI format 1_0 may be at least used to indicate the assignment of frequency resources for a PDSCH scheduled by the DCI format 1_0.
The time domain resource assignment field included in the DCI format 1_0 may be at least used to indicate the assignment of time resources for a PDSCH. The time domain resource assignment field included in the DCI format 1_0 may be at least used to indicate the assignment of time resources for a PDSCH scheduled by the DCI format 1_0.
The MCS field included in the DCI format 1_0 may be at least used to indicate a modulation scheme for a PDSCH and/or a part or all of a target coding rate for the PDSCH. The MCS field included in the DCI format 1_0 may be at least used to indicate a modulation scheme for a PDSCH scheduled by the DCI format 1_0 and/or a part or all of a target coding rate for the PDSCH. A size of a transport block (TBS: Transport Block Size) of a PDSCH may be given based at least on a target coding rate and a part or all of a modulation scheme for the PDSCH.
The PDSCH-to-HARQ-feedback timing indicator field may be at least used to indicate the offset (K1) from a slot in which the last OFDM symbol of a PDSCH scheduled by the DCI format 1_0 is included to another slot in which the first OFDM symbol of a PUCCH triggered by the DCI format 1_0 is included.
The PUCCH resource indicator field may be a field indicating an index of any one or more PUCCH resources included in the PUCCH resource set for a PUCCH transmission. The PUCCH resource set may include one or more PUCCH resources. The PUCCH resource indicator field may trigger PUCCH transmission with a PUCCH resource indicated at least based on the PUCCH resource indicator field.
The DCI format 1_0 may not include the carrier indicator field. A downlink component carrier on which a PDSCH scheduled by the DCI format 1_0 is arranged may be the same as a downlink component carrier on which a PDCCH including the DCI format 1_0 is arranged.
The DCI format 1_0 may not include the BWP field. A downlink BWP on which a PDSCH scheduled by a DCI format 1_0 is arranged may be the same as a downlink BWP on which a PDCCH including the DCI format 1_0 is arranged.
The DCI format 1_1 is at least used for scheduling of a PDSCH for a cell (or arranged on a cell). The DCI format 1_1 includes at least a part or all of fields 4A to 4H. The 4A is a DCI format identification field. The 4B is a frequency domain resource assignment field. The 4C is a time domain resource assignment field. The 4D is an MCS field. The 4E is a PDSCH-to-HARQ-feedback indicator field. The 4F is a PUCCH resource indicator field. The 4G is a BWP field. The 4H is a carrier indicator field.
The DCI format identification field included in the DCI format 1_1 may indicate 1 (or may indicate that the DCI format 1_1 is a downlink DCI format).
The frequency domain resource assignment field included in the DCI format 1_1 may be at least used to indicate the assignment of frequency resources for a PDSCH. The frequency domain resource assignment field included in the DCI format 1_0 may be at least used to indicate the assignment of frequency resources for a PDSCH scheduled by the DCI format 1_1.
The time domain resource assignment field included in the DCI format 1_1 may be at least used to indicate the assignment of time resources for a PDSCH. The time domain resource assignment field included in the DCI format 1_1 may be at least used to indicate the assignment of time resources for a PDSCH scheduled by the DCI format 1_1.
The MCS field included in the DCI format 1_1 may be at least used to indicate a modulation scheme for a PDSCH and/or a part or all of a target coding rate for the PDSCH. The MCS field included in the DCI format 1_1 may be at least used to indicate a modulation scheme for a PDSCH scheduled by the DCI format 1_1 and/or a part or all of a target coding rate for the PDSCH.
When the DCI format 1_1 includes a PDSCH-to-HARQ-feedback timing indicator field, the PDSCH-to-HARQ-feedback timing indicator field indicates an offset (K1) from a slot including the last OFDM symbol of a PDSCH scheduled by the DCI format 1_1 to another slot including the first OFDM symbol of a PUCCH triggered by the DCI format 1_1. When the DCI format 1_1 does not include the PDSCH-to-HARQ-feedback timing indicator field, an offset from a slot in which the last OFDM symbol of a PDSCH scheduled by the DCI format 1_1 is included to another slot in which the first OFDM symbol of a PUCCH triggered by the DCI format 1_1 is identified by a higher-layer parameter.
When the DCI format 1_1 includes the BWP field, the BWP field may be used to indicate a downlink BWP on which a PDSCH scheduled by the DCI format 1_1 is arranged. When the DCI format 1_1 does not include the BWP field, a downlink BWP on which a PDSCH is arranged may be the active downlink BWP. When the number of downlink BWPs configured in the terminal device 1 in a downlink component carrier is two or more, the number of bits for the BWP field included in the DCI format 1_1 used for scheduling a PDSCH arranged on the downlink component carrier may be one or more. When the number of downlink BWPs configured in the terminal device 1 in a downlink component carrier is one, the number of bits for the BWP field included in the DCI format 1_1 used for scheduling a PDSCH arranged on the downlink component carrier may be zero.
If the DCI format 1_1 includes the carrier indicator field, the carrier indicator field may be used to indicate a downlink component carrier (or a serving cell) on which a PDSCH is arranged. When the DCI format 1_1 does not include the carrier indicator field, a downlink component carrier (or a serving cell) on which a PDSCH is arranged may be the same as a downlink component carrier (or a serving cell) on which a PDCCH including the DCI format 1_1 used for scheduling of the PDSCH is arranged. When the number of downlink component carriers (or the number of serving cells) configured in the terminal device 1 in a serving cell group is two or more (when downlink carrier aggregation is operated in a serving cell group), or when cross-carrier scheduling is configured for the serving cell group, the number of bits for the carrier indicator field included in the DCI format 1_1 used for scheduling a PDSCH arranged on the serving cell group may be one or more (e.g., 3). When the number of downlink component carriers (or the number of serving cells) configured in the terminal device 1 in a serving cell group is one (or when downlink carrier aggregation is not operated in a serving cell group), or when the cross-carrier scheduling is not configured for the serving cell group, the number of bits for the carrier indicator field included in the DCI format 1_1 used for scheduling of a PDSCH arranged on the serving cell group may be zero.
A PDSCH may be used to transmit one or more transport blocks. A PDSCH may be used to transmit one or more transport blocks which corresponds to a DL-SCH. A PDSCH may be used to convey one or more transport blocks. A PDSCH may be used to convey one or more transport blocks which corresponds to a DL-SCH. One or more transport blocks may be arranged in a PDSCH. One or more transport blocks which corresponds to a DL-SCH may be arranged in a PDSCH. The base station device 3 may transmit a PDSCH. The terminal device 1 may receive the PDSCH.
Downlink physical signals may correspond to a set of resource elements. The downlink physical signals may not carry the information generated in the higher-layer. The downlink physical signals may be physical signals used in the downlink component carrier. A downlink physical signal may be transmitted by the base station device 3. The downlink physical signal may be transmitted by the terminal device 1. In the wireless communication system according to one aspect of the present embodiment, at least a part or all of an SS (Synchronization signal), DL DMRS (DownLink DeModulation Reference Signal), CSI-RS (Channel State Information-Reference Signal), and DL PTRS (DownLink Phase Tracking Reference Signal) may be used.
The synchronization signal may be used at least for the terminal device 1 to synchronize in the frequency domain and/or time domain for downlink. The synchronization signal is a generic name of PSS (Primary Synchronization Signal) and SSS (Secondary Synchronization Signal).
As shown in
The antenna ports of a PSS, an SSS, a PBCH, and a DMRS for the PBCH in an SS/PBCH block may be identical.
A PBCH may be estimated from a DMRS for the PBCH. For the DM-RS for the PBCH, the channel over which a symbol for the PBCH on an antenna port is conveyed can be inferred from the channel over which another symbol for the DM-RS on the antenna port is conveyed only if the two symbols are within a SS/PBCH block transmitted within the same slot, and with the same SS/PBCH block index.
DL DMRS is a generic name of DMRS for a PBCH, DMRS for a PDSCH, and DMRS for a PDCCH.
A set of antenna ports for a DMRS for a PDSCH (a DMRS associated with a PDSCH, a DMRS included in a PDSCH, a DMRS which corresponds to a PDSCH) may be given based on the set of antenna ports for the PDSCH. The set of antenna ports for the DMRS for the PDSCH may be the same as the set of antenna ports for the PDSCH.
Transmission of a PDSCH and transmission of a 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 PDSCH. Transmitting a PDSCH may be transmitting a PDSCH and a DMRS for the PDSCH.
A PDSCH may be estimated from a DMRS for the PDSCH. For a DM-RS associated with a PDSCH, the channel over which a symbol for the PDSCH on one antenna port is conveyed can be inferred from the channel over which another symbol for the DM-RS on the antenna port is conveyed only if the two symbols are within the same resource as the scheduled PDSCH, in the same slot, and in the same PRG (Precoding Resource Group).
Antenna ports for a DMRS for a PDCCH (a DMRS associated with a PDCCH, a DMRS included in a PDCCH, a DMRS which corresponds to a PDCCH) may be the same as an antenna port for the PDCCH.
A PDCCH may be estimated from a DMRS for the PDCCH. For a DM-RS associated with a PDCCH, the channel over which a symbol for the PDCCH on one antenna port is conveyed can be inferred from the channel over which another symbol for the DM-RS on the same antenna port is conveyed only if the two symbols are within resources for which the UE may assume the same precoding being used (i.e. within resources in a REG bundle).
A BCH (Broadcast CHannel), a UL-SCH (Uplink-Shared CHannel) and a DL-SCH (Downlink-Shared CHannel) are transport channels. A channel used in the MAC layer is called a transport channel. A unit of transport channel used in the MAC layer is also called transport block (TB) or MAC PDU (Protocol Data Unit). In the MAC layer, control of HARQ (Hybrid Automatic Repeat request) is performed for each transport block. The transport block is a unit of data delivered by the MAC layer to the physical layer. In the physical layer, transport blocks are mapped to codewords and modulation processing is performed for each codeword.
One UL-SCH and one DL-SCH may be provided for each serving cell. BCH may be given to PCell. BCH may not be given to PSCell and SCell.
A BCCH (Broadcast Control CHannel), a CCCH (Common Control CHannel), and a DCCH (Dedicated Control CHannel) are logical channels. The BCCH is a channel of the RRC layer used to deliver MIB or system information. The CCCH may be used to transmit a common RRC message in a plurality of terminal devices 1. The CCCH may be used for the terminal device 1 which is not connected by RRC. The DCCH may be used at least to transmit a dedicated RRC message to the terminal device 1. The DCCH may be used for the terminal device 1 that is in RRC-connected mode.
The RRC message includes one or more RRC parameters (information elements). For example, the RRC message may include a MIB. For example, the RRC message may include system information (SIB: System Information Block, MIB). SIB is a generic name for various type of SIBs (e.g., SIB1, SIB2). For example, the RRC message may include a message which corresponds to a CCCH. For example, the RRC message may include a message which corresponds to a DCCH. RRC message is a general term for common RRC message and dedicated RRC message.
The BCCH in the logical channel may be mapped to the BCH or the DL-SCH in the transport channel. The CCCH in the logical channel may be mapped to the DL-SCH or the UL-SCH in the transport channel. The DCCH in the logical channel may be mapped to the DL-SCH or the UL-SCH in the transport channel.
The UL-SCH in the transport channel may be mapped to a PUSCH in the physical channel. The DL-SCH in the transport channel may be mapped to a PDSCH in the physical channel. The BCH in the transport channel may be mapped to a PBCH in the physical channel.
A higher-layer parameter is a parameter included in an RRC message or a MAC CE (Medium Access Control Control Element). The higher-layer parameter is a generic name of information included in a MIB, system information, a message which corresponds to CCCH, a message which corresponds to DCCH, and a MAC CE.
A higher-layer parameter may be a cell-specific parameter or a UE-specific parameter. A cell-specific parameter is a parameter including a common configuration in a cell. A UE-specific parameter is a parameter including a configuration that may be configured differently for each UE.
The base station device may indicate change of cell-specific parameters by reconfiguration with random-access. The UE may change cell-specific parameters before triggering random-access. The base station device may indicate change of UE-specific parameters by reconfiguration with or without random-access. The UE may change UE-specific parameters before or after random-access.
The procedure performed by the terminal device 1 includes at least a part or all of the following 5A to 5C. The 5A is cell search. The 5B is random-access. The 5C is data communication.
The cell search is a procedure used by the terminal device 1 to synchronize with a cell in the time domain and/or the frequency domain and to detect a physical cell identity. The terminal device 1 may detect the physical cell ID by performing synchronization of time domain and/or frequency domain with a cell by the cell search.
A sequence of a PSS is given based at least on a physical cell ID. A sequence of an SSS is given based at least on the physical cell ID.
An SS/PBCH block candidate indicates a resource for which transmission of the SS/PBCH block may exist. An SS/PBCH block may be transmitted at a resource indicated as the SS/PBCH block candidate. The base station device 3 may transmit an SS/PBCH block at an SS/PBCH block candidate. The terminal device 1 may receive (detect) the SS/PBCH block at the SS/PBCH block candidate.
A set of SS/PBCH block candidates in a half radio frame is also referred to as an SS-burst-set. The SS-burst-set is also referred to as a transmission window, a SS transmission window, or a DRS transmission window (Discovery Reference Signal transmission window). The SS-burst-set is a generic name that includes at least a first SS-burst-set and a second SS-burst-set.
The base station device 3 transmits SS/PBCH blocks of one or more indexes at a predetermined cycle. The terminal device 1 may detect an SS/PBCH block of at least one of the SS/PBCH blocks of the one or more indexes. The terminal device 1 may attempt to decode the PBCH included in the SS/PBCH block.
The random-access is a procedure including at least a part or all of message 1 (msg1), message 2 (msg2), message 3 (msg3), and message 4 (msg4).
The message 1 is a procedure in which the terminal device 1 transmits a PRACH. The terminal device 1 transmits the PRACH in one PRACH occasion selected from among one or more PRACH occasions based on at least the index of the SS/PBCH block candidate detected based on the cell search.
The message 2 is a procedure in which the terminal device 1 attempts to detect a DCI format 1_0 with CRC (Cyclic Redundancy Check) scrambled by an RA-RNTI (Random Access-Radio Network Temporary Identifier). The terminal device 1 may attempt to detect the DCI format 1_0 in a search-space-set.
The message 3 is a procedure for transmitting a PUSCH scheduled by a random-access response grant included in the DCI format 1_0 detected in the message 2 procedure. The random-access response grant is indicated by the MAC CE included in the PDSCH scheduled by the DCI format 1_0.
The PUSCH scheduled based on the random-access response grant is either a message 3 PUSCH or a PUSCH. The message 3 PUSCH contains a contention resolution identifier MAC CE. The contention resolution ID MAC CE includes a contention resolution ID.
Retransmission of the message 3 PUSCH is scheduled by DCI format 0_0 with CRC scrambled by a TC-RNTI (Temporary Cell-Radio Network Temporary Identifier).
The message 4 is a procedure that attempts to detect a DCI format 1_0 with CRC scrambled by either a C-RNTI (Cell-Radio Network Temporary Identifier) or a TC-RNTI. The terminal device 1 receives a PDSCH scheduled based on the DCI format 1_0. The PDSCH may include a collision resolution ID.
Data communication is a generic term for downlink communication and uplink communication.
In data communication, the terminal device 1 attempts to detect a PDCCH (attempts to monitor a PDCCH, monitors a PDCCH). in a resource identified at least based on one or all of a control resource set and a search-space-set. It's also called as “the terminal device 1 attempts to detect a PDCCH in a control resource set”, “the terminal device 1 attempts to detect a PDCCH in a search-space-set”, “the terminal device 1 attempts to detect a PDCCH candidate in a control resource set”, “the terminal device 1 attempts to detect a PDCCH candidate in a search-space-set”, “the terminal device 1 attempts to detect a DCI format in a control resource set”, or “the terminal device 1 attempts to detect a DCI format in a search-space-set”. Monitoring a PDCCH may be equivalent as monitoring a DCI format in the PDCCH.
The control resource set is a set of resources configured by the number of resource blocks and a predetermined number of OFDM symbols in a slot.
The set of resources for the control resource set may be indicated by higher-layer parameters. The number of OFDM symbols included in the control resource set may be indicated by higher-layer parameters.
A PDCCH may be also called as a PDCCH candidate.
A search-space-set is defined as a set of PDCCH candidates. A search-space-set may be a Common Search Space (CSS) set or a UE-specific Search Space (USS) set.
The CSS set is a generic name 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, and a type-3 PDCCH common search-space-set. The USS set may be also called as UE-specific PDCCH search-space-set.
The type-0 PDCCH common search-space-set may be used as a common search-space-set with index 0. The type-0 PDCCH common search-space-set may be an common search-space-set with index 0.
A search-space-set is associated with (included in, corresponding to) a control resource set. The index of the control resource set associated with the search-space-set may be indicated by higher-layer parameters.
For a search-space-set, a part or all of 6A to 6C may be indicated at least by higher-layer parameters. The 6A is PDCCH monitoring period. The 6B is PDCCH monitoring pattern within a slot. The 6C is PDCCH monitoring offset.
A monitoring occasion of a search-space-set may correspond to one or more OFDM symbols in which the first OFDM symbol of the control resource set associated with the search-space-set is allocated. A monitoring occasion of a search-space-set may correspond to resources identified by the first OFDM symbol of the control resource set associated with the search-space-set. A monitoring occasion of a search-space-set is given based at least on a part or all of PDCCH monitoring periodicity, PDCCH monitoring pattern within a slot, and PDCCH monitoring offset.
In
In
In
In
In
The type-0 PDCCH common search-space-set may be at least used for a DCI format with a cyclic redundancy check (CRC) sequence scrambled by an SI-RNTI (System Information-Radio Network Temporary Identifier).
The type-0a PDCCH common search-space-set may be used at least for a DCI format with a cyclic redundancy check sequence scrambled by an SI-RNTI.
The type-1 PDCCH common search-space-set may be used at least for a DCI format with a CRC sequence scrambled by an RA-RNTI (Random Access-Radio Network Temporary Identifier) or a CRC sequence scrambled by a TC-RNTI (Temporary Cell-Radio Network Temporary Identifier).
The type-2 PDCCH common search-space-set may be used for a DCI format with a CRC sequence scrambled by P-RNTI (Paging-Radio Network Temporary Identifier).
The type-3 PDCCH common search-space-set may be used for a DCI format with a CRC sequence scrambled by a C-RNTI (Cell-Radio Network Temporary Identifier).
The UE-specific search-space-set may be used at least for a DCI format with a CRC sequence scrambled by a C-RNTI.
In downlink communication, the terminal device 1 may detect a downlink DCI format. The detected downlink DCI format is at least used for resource assignment for a PDSCH. The detected downlink DCI format is also referred to as downlink assignment. The terminal device 1 attempts to receive the PDSCH. Based on a PUCCH resource indicated based on the detected downlink DCI format, an HARQ-ACK corresponding to the PDSCH (HARQ-ACK corresponding to a transport block included in the PDSCH) may be reported to the base station device 3.
In uplink communication, the terminal device 1 may detect an uplink DCI format. The detected uplink DCI format is at least used for resource assignment for a PUSCH. The detected uplink DCI format is also referred to as uplink grant. The terminal device 1 transmits the PUSCH.
Region indicated by 9000 includes a set of region 9001, 9002 and 9003. Region 9000 may be configured based on a slot configuration. For example, a slot configuration may include at least a downlink region, a flexible region and an uplink region. For example, a slot configuration may be configured such that the slot configuration starts at one UL-to-DL switching point. Further, the slot configuration may be configured such that the slot configuration ends at another UL-to-DL switching point. For example, a UL-to-DL switching point may be a point where a uplink region ends and a downlink region starts.
For example, a slot configuration may be repeated in the time domain. In
9011 indicates a downlink region. Further, 9012 indicates a flexible region. Further, 9013 indicates an uplink region.
For example, a slot configuration may be represented by a combination of ‘D’, ‘U’ and ‘S’. ‘D’ indicates that a slot is a downlink slot. A downlink slot is a slot with downlink region. In
‘U’ indicates that a slot is an uplink slot. An uplink slot is a slot with uplink region. In
‘S’ indicates that a slot is a special slot. A special slot is a slot with at least two or more of a downlink regions, a flexible region and an uplink region. In
In
A configuration of special slot may be represented by “XDYFZU”. Here, X is the number of downlink symbols, Y is the number of flexible symbols and Z is the number of uplink symbols. For example, “10D2F2U” indicates that a special slot comprises 10 downlink symbols, 2 flexible symbols and 2 uplink symbols.
A downlink symbol is an OFDM symbol in a downlink region. A flexible symbol is an OFDM symbol in a flexible region. An uplink symbol is an OFDM symbol in an uplink region.
A slot configuration may be provided by RRC parameters. For example, a slot configuration may be configured by a common parameter included in system information such as SIB1. The common parameter may be also referred to as tdd-UL-DL-ConfigurationCommon.
For example, terminal device 1 may determine a reference subcarrier-spacing configuration uref and a first TDD pattern from the common parameter. The first TDD pattern includes one or more of T1 to T5. T1 is a configuration period P in milliseconds provided by referenceSubcarrierSpacing. T2 is the number dslots of slots indicating consecutive downlink slots provided by nrofDownlinkSlots. T3 is the number dsym of consecutive downlink symbols provided by nrofDownlinkSymbols. T4 is the number uslots of consecutive uplink slots provided by nrofUplinkSlots. T5 is the number usym of consecutive uplink symbols provided by nrofUplinkSymbols.
A slot configuration may be modified by a UE-specific parameter. The UE-specific parameter may be also referred to as tdd-UL-DL-ConfigurationDedicated.
If the UE-specific parameter is provided to terminal device 1, the UE-specific parameter may modify (or reconfigure) the slot configuration provided by the common parameter. For example, the UE-specific parameter may modify (or reconfigure) flexible region in the slot configuration.
For example, terminal device 1 may determine a list including a set of slot reconfigurations by the UE-specific parameter. In each slot reconfiguration in the set, at least one or both of an index of a slot and an indication of TDD pattern of the slot may be provided. The indication may indicate one out of ‘all DL’, ‘all UL’ and ‘explicit’. In a case that ‘all DL’ is indicated for the slot, the slot configuration in the slot is reconfigured as downlink region. In a case that ‘all UL’ is indicated for the slot, the slot configuration in the slot is reconfigured as uplink region. In a case that ‘explicit’ is indicated for the slot, the slot configuration in the slot is reconfigured by explicit indication corresponding to ‘explicit’. Indication ‘explicit’ corresponds to information indicating a TDD pattern in a slot. The information includes information indicating the number of downlink symbols starting at the beginning of the slot and information indicating the number of uplink symbols ending at the end of the slot. The remaining OFDM symbols between downlink symbols and uplink symbols are flexible symbols.
Terminal device 1 may receive a physical signal if terminal device 1 is configured by a higher layer or indicated by a DCI format to receive the physical signal in the downlink region.
Terminal device 1 may transmit a physical signal if terminal device 1 is configured by a higher layer or indicated by a DCI format to transmit the physical signal in the uplink region.
In a case that monitoring of DCI format 2_0 is not configured by a higher layer, terminal device 1 may receive a physical signal if terminal device 1 is indicated by a DCI format scheduling the physical channel to receive in the downlink region or the flexible region.
In a case that monitoring of DCI format 2_0 is not configured by a higher layer, terminal device 1 may transmit a physical signal if terminal device 1 is indicated by a DCI format scheduling the physical signal to transmit in the uplink region or the flexible region.
In a case that monitoring of DCI format 2_0 is configured by a higher layer, terminal device 1 may determine whether to receive a physical signal or not at least based on indication in the DCI format 2_0.
In a case that monitoring of DCI format 2_0 is configured by a higher layer, terminal device 1 may determine whether to transmit a physical signal or not at least based on indication in the DCI format 2_0.
Configuration regarding monitoring of DCI format 2_0 may include at least one or more of S1 to S3. S1 is an identifier of a serving cell. S2 is information indicating bit location of field for index of a slot format indicator. S3 is a set of slot format combinations. Here, each slot format combination may include one or more slot formats. Each of slot format combination may include an index of a slot format indicator. Each slot format may indicate a TDD pattern within a slot. For example, slot format #0 indicates that all OFDM symbols in a slot are downlink symbol. For example, slot format #1 indicates that all OFDM symbols in a slot are uplink symbol. For example, one slot format indicates that first 9 OFDM symbols in a slot are downlink symbol, next 3 OFDM symbols in the slot are flexible symbol and remaining 2 OFDM symbols are uplink symbol. For example, one slot format indicates that terminal device 1 interpret as if monitoring of DCI format 2_0 is not configured. Other TDD patterns in a slot are not precluded.
In a case that terminal device 1 detects a DCI format 2_0 in a first slot, terminal device 1 applies a slot format combination indicated through an index of slot format indicator in the DCI format 2_0. For example, the slot format combination may be applied to slots starting at the first slot.
At least based on an indication in DCI format 2_0, behavior of PUSCH transmission may be controlled. For example, a PUSCH transmission may be repetition of a PUSCH instance where the PUSCH instance is defined within a slot.
A PUSCH instance may be a unit of baseband signal generation. Here, the baseband signal generation may be performed by the baseband unit 13.
A transport block may be provided to Encoder 12000 from a higher layer. For example, a transport block may be provided to Encoder 12000 through UL-SCH from MAC layer processing unit 15. Encoder 12000 processes the transport block into a sequence b of coded bits. The sequence of the coded bits may be provided to Scrambler 11001. An element in position k of the sequence b may be referred to as b(k). The position k is in the range from 0 to Mbit−1. The position k is represented by an integer number. The Mbit represents the length of the sequence b.
For example, Scrambler 11001 may scramble the sequence b of the coded bits by using a pseudo-random code c. For example, the element b(k) may be scrambled by an element c(k) in position k of the pseudo-random code c. For example, Scrambler 11001 may output a sequence ba by calculating ba(k)=mod(b(k)+c(k), 2). The ba(k) is an element in position k of the sequence ba. In a case that the baseband unit 13 doesn't include Scrambler 11001, the sequence b of the coded bits may be input to the ba.
The pseudo-random code c may be a sequence of bits generated by Scrambler 11001. For example, the pseudo-random code c may be generated by an equation with initialization variable. The initialization variable may determine or control an output from the equation. The initialization variable may be determined at least based on RNTI used for scheduling an uplink transmission conveying the transport block.
For example, Modulator 11002 may perform a modulation to the sequence ba and generate a sequence d of complex-valued symbols. An element in position j of the sequence d is referred to as d (j). The position j is in the range from 0 to Msymb−1. The position j is represented by an integer number. The Msymb-represents the length of the sequence d. In a case that the baseband unit 13 doesn't include Modulator 12002, the sequence ba of the coded bits may be input to the d.
For example, the modulation may be 2/pi BPSK (Binary Phase Shift Keying), QPSK (Quadrature Phase Shift Keying), 16QAM (Quadrature Amplitude Modulation), 64QAM or 256QAM.
For example, Layer mapper 11003 may perform layer mapping to the sequence d. After layer mapping, Nv sequences each with length Mlayersymb are generated. The Nv is the number of layers for the PUSCH. The vth sequence in the Nv sequences is referred to as x(v). An element in position h of the sequence x(v) is referred to as x(v)(h). The position h is in the range from 0 to Mlayersymb−1. The position h is represented by an integer number. In a case that the number Nv is 1, Layer mapper 11003 may not perform layer mapping. In a case that the layer mapping is not performed to the sequence d, the sequence d may be input to x(0).
For example, Transform precoder 11004 may perform a transform precoding to the sequence x(v) and generate a sequence y(v). In a case that the transform precoding is not performed to the sequence x(v), the sequence x(v) may be input to the sequence y(v).
For example, Precoder 11005 may perform a precoding to the sequence y(v) After the precoding, Np sequences each with length Mlayersymb are generated. The Np is the number of antenna ports for the PUSCH. The pth sequence in the Np sequences is referred to as z(p). An element in position h of the sequence z(p) is referred to as z(p)(h). In a case that the number Np is 1, Precoder 11005 may not perform the precoding. In a case that the precoding is not performed to the sequence y(v), the sequence y(v) may be input to z(p).
For example, Resource element mapper 11006 may perform a RE mapping. In a RE mapping, a group of elements z(h)=[z(0)(h), . . . , z(Np−1)(h)] is mapped to a resource element.
For example, Time-continuous signal generator 11007 may perform a time-continuous signal generation based on contents in the resource elements. The contents in the resource elements are determined based on the RE mapping. The time-continuous signal generated by Time-continuous signal generator 11007 is provided to RF unit 12.
The baseband unit 33 may include corresponding components for reception of the PUSCH as the baseband unit 13.
For example, a transport block input to Encoder 12000 is an input to CRC addition unit 12001. In CRC addition unit 12001, a CRC sequence is added to the transport block. A bit sequence after CRC sequence addition is input to Code block segmentation unit 12002. In a case that a CRC sequence is not added to the transport block, the transport block is input to Code block segmentation unit 12002.
For example, a sequence input to Code block segmentation unit 12002 is segmented into multiple code blocks in a case that the length of the sequence is larger than a certain value. In a case that the sequence is segmented into multiple code blocks, a CRC sequence is added to each code block. Each code block after the CRC sequence addition is input to Encoding unit 12003. In a case that the sequence is not segmented into multiple code blocks, a single code block is input to Encoding unit 12003. In a case that the sequence is not segmented into multiple code blocks, a CRC sequence is not added to the single code block. In a case that the sequence is not segmented into multiple code blocks, the single code block without addition of a CRC sequence is input to Encoding unit 12003.
For example, a code block with index r (code block #r) input to Encoding unit 12003 is encoded by LDPC coding such as QC-LDPC (Quasi-Cyclic Low Density Parity Check) coding. The index r is in the range from 0 to C-1. The C is the number of code blocks determined in Code block segmentation unit 12002. Coded bits dr for the code block #r after LDPC coding is input to Rate matching unit 12004.
For example, Rate matching unit 12004 performs a bit-selection procedure. In the bit-selection procedure, the coded bits dr for the code block r is written into a circular buffer of length Ncb.
Here, the rate matching output sequence length Er represents the number of available bits for transmission of the code block #r. For example, the rate matching output sequence length Er for code block #r may be calculated at least based on a part or all of modulation order Qm, the number Nv of layers for the PUSCH, the number C′ and the number G. For example, the rate matching output sequence length E, for code block r may be calculated by Er=NLQmfloor(G/(NLQmC′)) or Er=NLQmceil(G/(NLQmC′)).
Here, the number C′ represents the number of code blocks. The number G represents the number of available bits for transmission of UL-SCH. For example, the number G may represent the number of available bits for transmission of UL-SCH in the PUSCH instance.
In Step 2, Rate matching unit 12004 checks if dr(mod(k0+j, Ncb)) is not <NULL>. If dr(mod(k0+j, Ncb)) is not <NULL>, Rate matching unit 12004 goes to Step 3. If dr(mod(k0+j, Ncb)) is <NULL>, Rate matching unit 12004 goes to Step 5.
Here, “dr(mod(k0+j, Ncb)) is <NULL>” means <NULL> is set to dr(mod(k0+j, Ncb)). <NULL> may be set to some elements of dr when an element corresponds to a filler bit for LDPC coding.
Here, an element in position k of dr is referred to as dr(k).
In Step 3, Rate matching unit 12004 sets a value in dr(mod(k0+j, Ncb)) to e (k). The sequence e is a rate matching output sequence. An element in position k of the sequence e is referred to as e (k).
Here, k0 represents a starting point for the circular buffer.
In Step 4, Rate matching unit 12004 increments a value k by one.
Step 5 is a sign of the end of Step 2.
In Step 6, Rate matching unit 12004 increments a value j by one.
Step 7 is a sign of the end of Step 1. Rate matching unit 12004 goes back to Step 1.
In the bit-selection procedure, bits in the circular buffer are read out starting at the starting point k0 with length Er. The bits read out from the circular buffer are written into the rate matching output sequence e.
The starting point k0 is determined based on the redundancy version indicated or determined by a redundancy version field in an uplink DCI format for dynamic scheduling.
For example, the starting point k0 may be determined based on the redundancy version and an identification of an instance. For example, in a case that one DCI format schedules a repetition of a PUSCH, terminal device 1 may transmit multiple instances. For each instance, the starting point k0 may be determined. For example, in a case that 8 instances (instance #0, instance #1, instance #2, instance #3, instance #4, instance #5, instance #6, instance #7) are scheduled by one DCI format, the starting point k0 may be determined 8 times.
For example, a sequence of RV (redundancy version) may be provided to the terminal device 1. In a case that a sequence of RV is provided, a RV is allocated to each instance in the multiple instances based on the sequence. For example, in a case that the sequence [0, 2, 3, 1] of length Ns is provided, (mod(n, Ns)+1)th value in the sequence may be allocated to nth instance. The starting point k0 of nth instance may be determined based on the allocated RV for nth instance.
A TDRA field in the DCI format may provide a value S and a value L.
In
In a first type repetition, multiple instances for a PUSCH may be allocated on Krep continuous slots starting at a slot determined by a DCI format scheduling the PUSCH. For example, in a case that a DCI format scheduling the PUSCH includes a TDRA field, the TDRA field may provide a value K for determining the starting slot for the PUSCH. For example, the value K is in unit of slots. For example, the terminal device 1 may determine the starting slot as slot #(n+K) in a case that a PDCCH including the DCI format is detected in slot #n. In a case that the DCI format doesn't include a TDRA field, the value K may be provided by a RRC layer through a RRC parameter.
A sequence of RV for the first type repetition may be provided to the terminal device 1. For example, the sequence may be provided by a RRC layer through a RRC parameter. In a case that a sequence of RV is provided for the first type repetition, (mod (n, Ns)+1)th value in the sequence may be allocated to nth instance. Here, an index may be provided to each instance for the PUSCH in ascending order in the time domain.
For a first type repetition, in a case that an instance overlaps with a downlink symbol determined by a slot configuration, transmission of the instance may be omitted (or dropped, cancelled, not transmitted).
For a first type repetition, in a case that an instance overlaps with a downlink symbol determined by a slot format, transmission of the instance may be omitted.
For a first type repetition, in a case that an instance overlaps with another uplink signal with a higher priority than the priority for the PUSCH, transmission of the instance may be omitted. For example, the uplink signal may be a second PUSCH with higher priority than the priority of the PUSCH. For example, the priority for a PUSCH may be provided by a DCI format scheduling the PUSCH.
In
In a second type repetition, the multiple instances for a PUSCH may be allocated on Krep continuous available slots starting at a slot determined by a DCI format scheduling the PUSCH. For example, in a case that a DCI format scheduling the PUSCH includes a TDRA field, the TDRA field may provide a value K for determining the starting slot for the PUSCH. For example, the value K is in unit of slots. For example, in a case that the terminal device 1 may determine the starting slot as slot #(n+K). In a case that the DCI format doesn't include a TDRA field, the value K may be provided by a RRC layer through a RRC parameter.
In a second type repetition, Krep continuous available slots may be determined by a slot configuration. For example, a slot may be available in a case that a set of OFDM symbols allocated for an instance in the slot doesn't overlap with any downlink symbol which is determined by a slot configuration. For example, a slot may be available in a case that a set of OFDM symbols determined by a value S and a value L in the slot doesn't overlap with any downlink symbol which is determined by a slot configuration. The value S and the value L may be provided by the TDRA field in the DCI format. In
A sequence of RV may be provided for the second type repetition to the terminal device 1. For example, the sequence may be provided by a RRC layer through a RRC parameter. In a case that a sequence of RV is provided for the second type repetition, (mod(n, Ns)+1)th value in the sequence may be allocated to nth instance. Here, an index may be provided to each instance for the PUSCH in ascending order in the time domain.
For example, a first sequence of RV and a second sequence of RV may be provided to the terminal device 1. For example, the first sequence may be used for a first type repetition. For example, the second sequence may be used for a second type repetition.
For example, the first sequence may be provided by a RRC layer through a first RRC parameter. For example, the second sequence may be provided by a RRC layer through a second RRC parameter which is different from the first RRC parameter.
For a second type repetition, in a case that an instance overlaps with a downlink symbol determined by a slot configuration, transmission of the instance may be omitted. On the other hand, For a second type repetition, there may be no case that an instance overlaps with a downlink symbol determined by a slot configuration since the collision handling with the downlink symbol by the slot configuration may have been done already in a procedure of determining the Krep continuous available slots. Therefore, for a second type repetition, transmission of the instance may not be omitted based on the slot configuration. For example, for a second type repetition, the terminal device 1 may not determine, based on the slot configuration, whether an instance is omitted or not. For example, the terminal device 1 may not perform a process of determining, based on the slot configuration, whether an instance is omitted or not.
For a second type repetition, in a case that an instance overlaps with a downlink symbol determined by a slot format, transmission of the instance may be omitted.
For a second type repetition, in a case that an instance overlaps with another uplink signal with a higher priority than the priority for the PUSCH, transmission of the instance may be omitted. For example, the uplink signal may be a second PUSCH with higher priority than the priority of the PUSCH. For example, the priority for a PUSCH may be provided by a DCI format scheduling the PUSCH.
A third type repetition is described with
In a third type repetition, multiple instances for a PUSCH may be allocated on continuous available slots starting at a slot determined by a DCI format scheduling the PUSCH.
In a third type repetition, the continuous available slots may be determined by a slot configuration. For example, a slot may be available in a case that a set of OFDM symbols allocated for an instance in the slot doesn't overlap with any downlink symbol which is determined by a slot configuration. For example, a slot may be available in a case that a set of OFDM symbols determined by a value S and a value L provided by the TDRA field in the DCI format in the slot doesn't overlap with any downlink symbol which is determined by a slot configuration. In
A sequence of RV may be provided for the third type repetition to the terminal device 1. For example, the sequence may be provided by a RRC layer through a RRC parameter. In a case that a sequence of RV is provided for the third type repetition, (mod (n, Ns)+1)th value in the sequence may be allocated to nth instance. For example, a first sequence of RV and a third sequence of RV may be provided to the terminal device 1. For example, the first sequence may be used for a first type repetition. For example, the third sequence may be used for a third type repetition.
For example, the first sequence may be provided by a RRC layer through a first RRC parameter. For example, the third sequence may be provided by a RRC layer through a third RRC parameter which is different from the first RRC parameter.
For a third type repetition, in a case that an instance overlaps with a downlink symbol determined by a slot configuration, transmission of the instance may be omitted. On the other hand, For a third type repetition, there may be no case that an instance overlaps with a downlink symbol determined by a slot configuration since the collision handling with the downlink symbol by the slot configuration may have been done already in a procedure of determining the continuous available slots. Therefore, for a third type repetition, transmission of the instance may not be omitted based on the slot configuration. For example, for a third type repetition, the terminal device 1 may not determine, based on the slot configuration, whether an instance is omitted or not. For example, the terminal device 1 may not perform a process of determining, based on the slot configuration, whether an instance is omitted or not.
For a third type repetition, in a case that an instance overlaps with a downlink symbol determined by a slot format, transmission of the instance may be omitted.
For a third type repetition, in a case that an instance overlaps with another uplink signal with a higher priority than the priority for the PUSCH, transmission of the instance may be omitted. For example, the uplink signal may be a second PUSCH with higher priority than the priority of the PUSCH. For example, the priority for a PUSCH may be provided by a DCI format scheduling the PUSCH.
For a third type repetition, first Krep instances are determined for the PUSCH transmission. For example, in a case that no instances are omitted, the terminal device may determine that the instance 16001, 16002, and 16003 as the first Krep instances. For example, in a case that the instance 16002 is omitted due to the collision with the high priority signal, the terminal device determines that the instance 16001, 16003 and 16004 as the first Krep instances. For example, in a case that the instance 16003 is omitted due to the collision with the high priority signal, the terminal device determines that the instance 16001, 16002 and 16004 as the first Krep instances.
A fourth type repetition is described with
In a fourth type repetition, multiple instances for a PUSCH may be allocated on continuous available slots starting at a slot determined by a DCI format scheduling the PUSCH.
In a fourth type repetition, the continuous available slots may be determined by a slot configuration. For example, a slot may be available in a case that a set of OFDM symbols allocated for an instance in the slot doesn't overlap with any downlink symbol which is determined by a slot configuration. For example, a slot may be available in a case that a set of OFDM symbols determined by a value S and a value L provided by the TDRA field in the DCI format in the slot doesn't overlap with any downlink symbol which is determined by a slot configuration. In
Before determining a RV for each instance, the terminal device 1 may determine whether one or more instances are omitted or not. For example, in a case that no instances are omitted, the terminal device may determine that the instance 16001, 16002, and 16003 as the first Krep instances. For example, in a case that the instance 16002 is omitted due to the collision with the high priority signal, the terminal device determines that the instance 16001, 16003 and 16004 as the first Krep instances. For example, in a case that the instance 16003 is omitted due to the collision with the high priority signal, the terminal device determines that the instance 16001, 16002 and 16004 as the first Krep instances.
A sequence of RV may be provided for the fourth type repetition to the terminal device 1. For example, the sequence may be provided by a RRC layer through a RRC parameter. In a case that a sequence of RV is provided for the fourth type repetition, (mod(n, Ns)+1)th value in the sequence may be allocated to nth instance within the first Krep instances. For example, a first sequence of RV and a fourth sequence of RV may be provided to the terminal device 1. For example, the first sequence may be used for a first type repetition. For example, the fourth sequence may be used for a fourth type repetition.
For example, the first sequence may be provided by a RRC layer through a first RRC parameter. For example, the fourth sequence may be provided by a RRC layer through a fourth RRC parameter which is different from the first RRC parameter.
For a fourth type repetition, in a case that an instance overlaps with a downlink symbol determined by a slot configuration, transmission of the instance may be omitted. On the other hand, for a fourth type repetition, there may be no case that an instance overlaps with a downlink symbol determined by a slot configuration since the collision handling with the downlink symbol by the slot configuration may have been done already in a procedure of determining the continuous available slots. Therefore, for a fourth type repetition, transmission of the instance may not be omitted based on the slot configuration. For example, for a fourth type repetition, the terminal device 1 may not determine, based on the slot configuration, whether an instance is omitted or not. For example, the terminal device 1 may not perform a process of determining, based on the slot configuration, whether an instance is omitted or not.
For a fourth type repetition, in a case that an instance overlaps with a downlink symbol determined by a slot format, transmission of the instance may be omitted.
For a fourth type repetition, in a case that an instance overlaps with another uplink signal with a higher priority than the priority for the PUSCH, transmission of the instance may be omitted. For example, the uplink signal may be a second PUSCH with higher priority than the priority of the PUSCH. For example, the priority for a PUSCH may be provided by a DCI format scheduling the PUSCH.
For a fourth type repetition, the first Krep instances are transmitted for the PUSCH transmission.
Here, the PUSCH is associated with the period 17010. Also, the PUSCH is associated with the instances 17001 to 17006.
For example, a value S and a value L may be provided by a RRC layer via a RRC parameter. For example, a value S and a value L may be provided by a TDRA field in a DCI format which activates a configured grant operation.
17007 indicates an instance of another PUSCH. The instance 17007 is not a part of repetitions for the PUSCH within the period 17010. The instance 17007 is a first instance for another PUSCH within the period 17011. Here, a period may define a time occasion which includes a number of repetitions for a single PUSCH. For example, if two instances are included in different periods, the two instances are associated with different PUSCH.
Here, another PUSCH is associated with the period 17011. Also, another PUSCH is associated with the instances 17001 to 17006.
A PUSCH with instances which occur within a period is associated with the period. The PUSCH is associated with the instances.
In
In a first type repetition, multiple instances for a PUSCH may be allocated on Krep continuous slots starting at a slot including a starting OFDM symbol of a period.
In
For example, for a second type repetition, a set of instances for a PUSCH associated with a period may be determined based on the number Krep and the period associated with the PUSCH. For example, in a case that an instance for a PUSCH is out of the period associated with the PUSCH, the instance may be excluded from the set of instances for the PUSCH. For example, the number Krep indicates a maximum value for the number of instances for a PUSCH and instances are mapped within the period such that the number of the instances doesn't exceed the number Krep.
In
In a second type repetition, the multiple instances for a PUSCH may be allocated on continuous available slots starting at a slot including a starting OFDM symbol of a period associated with the PUSCH.
A third type repetition is described with
In a third type repetition, multiple instances for a PUSCH may be allocated on continuous available slots starting at a slot including a starting OFDM symbol of the period associated with the PUSCH.
For example, for a third type repetition, a set of instances for a PUSCH associated with a period may be determined based on the number Krep and the period associated with the PUSCH. For example, in a case that an instance for a PUSCH is out of the period associated with the PUSCH, the instance may be excluded from the set of instances for the PUSCH. For example, the number Krep indicates a maximum value for the number of instances for a PUSCH and instances are mapped within the period such that the number of the instances doesn't exceed the number Krep.
A fourth type repetition is described with
For example, for a fourth type repetition, a set of instances for a PUSCH associated with a period may be determined based on the number Krep and the period associated with the PUSCH. For example, in a case that an instance for a PUSCH is out of the period associated with the PUSCH, the instance may be excluded from the set of instances for the PUSCH. For example, the number Krep indicates a maximum value for the number of instances for a PUSCH and instances are mapped within the period such that the number of the instances doesn't exceed the number Krep.
In a fourth type repetition, multiple instances for a PUSCH may be allocated on continuous available slots starting at a slot including a starting OFDM symbol of the period associated with the PUSCH.
In a case that a first type repetition is applied to a msg3 PUSCH, the terminal device 1 may be required to determine mapping of DMRS for the msg3 PUSCH. Msg3 PUSCH is a PUSCH for msg3 procedure.
For example, in a case that a first type repetition is applied to a msg3 PUSCH, the terminal device 1 may determine that a parameter for determining mapping of DMRS for the msg3 PUSCH has a value ‘pos2’. Here, the value ‘pos2’ may imply that up to 2 additional DMRS symbols can be transmitted with each instance of the msg3 PUSCH.
For example, in a case that a first type repetition is applied to a msg3 PUSCH, the terminal device 1 may determine that a parameter for determining mapping of DMRS for the msg3 PUSCH has a value ‘pos1’. Here, the value ‘pos1’ implies that up to 1 additional DMRS symbol can be transmitted with each repetition of the msg3 PUSCH.
For example, in a case that a first type repetition is not applied to a msg3 PUSCH, the terminal device 1 may determine that a parameter for determining mapping of DMRS for the msg3 PUSCH has a value ‘pos1’ in a case that frequency hopping is enabled for the msg3 PUSCH.
For example, in a case that a first type repetition is not applied to a msg3 PUSCH, the terminal device 1 may determine that a parameter for determining mapping of DMRS for the msg3 PUSCH has a value ‘pos2’ in a case that frequency hopping is not enabled for the msg3 PUSCH.
As explained above, the terminal device 1 may determine a value of a parameter for determining mapping of DMRS for the msg3 PUSCH based on whether a first type repetition is applied to the msg3 PUSCH or not.
For example, the terminal device 1 may determine that a parameter for determining mapping of DMRS for the msg3 PUSCH has a value ‘pos2’ regardless of whether frequency hopping is enabled or not in a case that a first type repetition is applied to the msg3 PUSCH.
For example, the terminal device 1 may determine that a parameter for determining mapping of DMRS for the msg3 PUSCH has a value ‘pos2’ based on that a first type repetition is applied to the msg3 PUSCH.
For example, the terminal device 1 may determine that a parameter for determining mapping of DMRS for the msg3 PUSCH has a value ‘pos1’ regardless of whether frequency hopping is enabled or not in a case that a first type repetition is applied to the msg3 PUSCH.
For example, the terminal device 1 may determine that a parameter for determining mapping of DMRS for the msg3 PUSCH has a value ‘pos1’ based on that a first type repetition is applied to the msg3 PUSCH.
For example, the terminal device 1 may determine that a parameter for determining mapping of DMRS for the msg3 PUSCH has a value ‘pos1’ or ‘pos2’ based on whether frequency hopping is enabled or not in a case that a first type repetition is not applied to the msg3 PUSCH.
The terminal device 1 may consider the number Krep of repetitions on top of whether a first type repetition is applied or not for determining a value of the parameter for determining mapping of DMRS for a msg3 PUSCH.
For example, in a case that a first type repetition with Krep>1 is applied to a msg3 PUSCH, the terminal device 1 may determine that a parameter for determining mapping of DMRS for the msg3 PUSCH has a value ‘pos2’.
For example, in a case that a first type repetition with Krep>1 is applied to a msg3 PUSCH, the terminal device 1 may determine that a parameter for determining mapping of DMRS for the msg3 PUSCH has a value ‘pos1’.
For example, in a case that a first type repetition with Krep=1 is applied to a msg3 PUSCH, the terminal device 1 may determine that a parameter for determining mapping of DMRS for the msg3 PUSCH has a value ‘pos1’ in a case that frequency hopping is enabled for the msg3 PUSCH.
For example, in a case that a first type repetition with Krep=1 is applied to a msg3 PUSCH, the terminal device 1 may determine that a parameter for determining mapping of DMRS for the msg3 PUSCH has a value ‘pos2’ in a case that frequency hopping is not enabled for the msg3 PUSCH.
As explained above, the terminal device 1 may determine a value of a parameter for determining mapping of DMRS for the msg3 PUSCH based on whether the first type repetition with Krep>1 is applied or not.
For example, the terminal device 1 may determine that a parameter for determining mapping of DMRS for the msg3 PUSCH has a value ‘pos2’ regardless of whether frequency hopping is enabled or not in a case that a first type repetition with Krep>1 is applied to the msg3 PUSCH.
For example, the terminal device 1 may determine that a parameter for determining mapping of DMRS for the msg3 PUSCH has a value ‘pos2’ based on that a first type repetition with Krep>1 is applied to the msg3 PUSCH.
For example, the terminal device 1 may determine that a parameter for determining mapping of DMRS for the msg3 PUSCH has a value ‘pos1’ regardless of whether frequency hopping is enabled or not in a case that a first type repetition with Krep>1 is applied to the msg3 PUSCH.
For example, the terminal device 1 may determine that a parameter for determining mapping of DMRS for the msg3 PUSCH has a value ‘pos1’ based on that a first type repetition with Krep>1 is applied to the msg3 PUSCH.
For example, the terminal device 1 may determine that a parameter for determining mapping of DMRS for the msg3 PUSCH has a value ‘pos1’ or ‘pos2’ based on whether frequency hopping is enabled or not in a case that a first type repetition with Krep=1 is applied to the msg3 PUSCH.
In a case that a second type repetition is applied to a msg3 PUSCH, the terminal device 1 may be required to determine mapping of DMRS for the msg3 PUSCH. Msg3 PUSCH is a PUSCH for msg3 procedure.
For example, in a case that a second type repetition is applied to a msg3 PUSCH, the terminal device 1 may determine that a parameter for determining mapping of DMRS for the msg3 PUSCH has a value ‘pos2’. Here, the value ‘pos2’ may imply that up to 2 additional DMRS symbols can be transmitted with each instance of the msg3 PUSCH.
For example, in a case that a second type repetition is applied to a msg3 PUSCH, the terminal device 1 may determine that a parameter for determining mapping of DMRS for the msg3 PUSCH has a value ‘pos1’. Here, the value ‘pos1’ implies that up to 1 additional DMRS symbol can be transmitted with each repetition of the msg3 PUSCH.
For example, in a case that a second type repetition is not applied to a msg3 PUSCH, the terminal device 1 may determine that a parameter for determining mapping of DMRS for the msg3 PUSCH has a value ‘pos1’ in a case that frequency hopping is enabled for the msg3 PUSCH.
For example, in a case that a second type repetition is not applied to a msg3 PUSCH, the terminal device 1 may determine that a parameter for determining mapping of DMRS for the msg3 PUSCH has a value ‘pos2’ in a case that frequency hopping is not enabled for the msg3 PUSCH.
As explained above, the terminal device 1 may determine a value of a parameter for determining mapping of DMRS for the msg3 PUSCH based on whether a second type repetition is applied to the msg3 PUSCH or not.
For example, the terminal device 1 may determine that a parameter for determining mapping of DMRS for the msg3 PUSCH has a value ‘pos2’ regardless of whether frequency hopping is enabled or not in a case that a second type repetition is applied to the msg3 PUSCH.
For example, the terminal device 1 may determine that a parameter for determining mapping of DMRS for the msg3 PUSCH has a value ‘pos2’ based on that a second type repetition is applied to the msg3 PUSCH.
For example, the terminal device 1 may determine that a parameter for determining mapping of DMRS for the msg3 PUSCH has a value ‘pos1’ regardless of whether frequency hopping is enabled or not in a case that a second type repetition is applied to the msg3 PUSCH.
For example, the terminal device 1 may determine that a parameter for determining mapping of DMRS for the msg3 PUSCH has a value ‘pos1’ based on that a second type repetition is applied to the msg3 PUSCH.
For example, the terminal device 1 may determine that a parameter for determining mapping of DMRS for the msg3 PUSCH has a value ‘pos1’ or ‘pos2’ based on whether frequency hopping is enabled or not in a case that a second type repetition is not applied to the msg3 PUSCH.
The terminal device 1 may consider the number Krep of repetitions on top of whether a second type repetition is applied or not for determining a value of the parameter for determining mapping of DMRS for a msg3 PUSCH.
For example, in a case that a second type repetition with Krep>1 is applied to a msg3 PUSCH, the terminal device 1 may determine that a parameter for determining mapping of DMRS for the msg3 PUSCH has a value ‘pos2’.
For example, in a case that a second type repetition with Krep>1 is applied to a msg3 PUSCH, the terminal device 1 may determine that a parameter for determining mapping of DMRS for the msg3 PUSCH has a value ‘pos1’.
For example, in a case that a second type repetition with Krep=1 is applied to a msg3 PUSCH, the terminal device 1 may determine that a parameter for determining mapping of DMRS for the msg3 PUSCH has a value ‘pos1’ in a case that frequency hopping is enabled for the msg3 PUSCH.
For example, in a case that a second type repetition with Krep=1 is applied to a msg3 PUSCH, the terminal device 1 may determine that a parameter for determining mapping of DMRS for the msg3 PUSCH has a value ‘pos2’ in a case that frequency hopping is not enabled for the msg3 PUSCH.
As explained above, the terminal device 1 may determine a value of a parameter for determining mapping of DMRS for the msg3 PUSCH based on whether the second type repetition with Krep>1 is applied or not.
For example, the terminal device 1 may determine that a parameter for determining mapping of DMRS for the msg3 PUSCH has a value ‘pos2’ regardless of whether frequency hopping is enabled or not in a case that a second type repetition with Krep>1 is applied to the msg3 PUSCH.
For example, the terminal device 1 may determine that a parameter for determining mapping of DMRS for the msg3 PUSCH has a value ‘pos2’ based on that a second type repetition with Krep>1 is applied to the msg3 PUSCH.
For example, the terminal device 1 may determine that a parameter for determining mapping of DMRS for the msg3 PUSCH has a value ‘pos1’ regardless of whether frequency hopping is enabled or not in a case that a second type repetition with Krep>1 is applied to the msg3 PUSCH.
For example, the terminal device 1 may determine that a parameter for determining mapping of DMRS for the msg3 PUSCH has a value ‘pos1’ based on that a second type repetition with Krep>1 is applied to the msg3 PUSCH.
For example, the terminal device 1 may determine that a parameter for determining mapping of DMRS for the msg3 PUSCH has a value ‘pos1’ or ‘pos2’ based on whether frequency hopping is enabled or not in a case that a second type repetition with Krep=1 is applied to the msg3 PUSCH.
Determination of mapping of DMRS for a msg3 PUSCH includes determination of a set of OFDM symbol indices for the mapping of DMRS for the msg3 PUSCH. In a case that repetition (first type repetition, second type repetition, third type repetition or fourth type repetition) is applied to the msg3 PUSCH, the DMRS may be mapped to OFDM symbols corresponding to the set of OFDM symbol indices for each instance. In a case that intra-frequency hopping is applied to the msg3 PUSCH, the DMRS may be mapped to OFDM symbols corresponding to the set of OFDM symbol indices for each hop. In intra-slot frequency hopping, the PUSCH may be transmitted in a first hop and a second hop for each instance.
Mapping of DMRS for a msg3 PUSCH may be determined by a value of a parameter for determining mapping of DMRS for the msg3 PUSCH and a value L indicating the number of OFDM symbols allocated for each instance.
For example, in a case that a value of a parameter for determining mapping of DMRS for the msg3 PUSCH is ‘pos1’ and a value L is 14 and intra-slot frequency hopping is disabled, a set of OFDM symbol indices may include l0, 11. Here, l0 may be an OFDM symbol index of mapping of front-loaded DMRS. For example, l0 may be 2 or 3. For example, l0 may be indicated by MIB.
For example, in a case that a value of a parameter for determining mapping of DMRS for the msg3 PUSCH is ‘pos2’ and a value L is 14 and intra-slot frequency hopping is disabled, a set of OFDM symbol indices may include l0, 7, 11.
For example, in a case that a value of a parameter for determining mapping of DMRS for the msg3 PUSCH is ‘pos1’ and a value L is 12 and intra-slot frequency hopping is disabled, a set of OFDM symbol indices may include l0, 9.
For example, in a case that a value of a parameter for determining mapping of DMRS for the msg3 PUSCH is ‘pos2’ and a value L is 12 and intra-slot frequency hopping is disabled, a set of OFDM symbol indices may include l0, 6, 9.
For example, in a case that a value of a parameter for determining mapping of DMRS for the msg3 PUSCH is ‘pos1’ and a value L is 14 and intra-slot frequency hopping is enabled, a set of OFDM symbol indices for a first hop may include 2, 6 and a set of OFDM symbol indices for a second hop may include 0, 4.
For example, in a case that a value of a parameter for determining mapping of DMRS for the msg3 PUSCH is ‘pos1’ and a value L is 12 and intra-slot frequency hopping is enabled, a set of OFDM symbol indices for a first hop may include 2 and a set of OFDM symbol indices for a second hop may include 0, 4.
To accomplish the object described above, aspects of the present invention are contrived to provide the following measures. Specifically, the terminal device 1 comprising reception circuitry configured to receive a random-access response grant included in a PDSCH, and transmission circuitry configured to transmit a msg3 PUSCH scheduled by the random-access response grant, wherein a parameter for determining mapping of DMRS for the msg3 PUSCH is determined as a value regardless of whether frequency hopping is enabled or not in a case that repetition is applied to the msg3 PUSCH, the parameter is determined as ‘pos1’ or ‘pos2’ based on whether frequency hopping is enabled or not in a case that repetition is not applied to the msg3 PUSCH.
Furthermore, the base station device 3 comprising transmission circuitry configured to transmit a random-access response grant included in a PDSCH, and reception circuitry configured to receive a msg3 PUSCH scheduled by the random-access response grant, wherein a parameter for determining mapping of DMRS for the msg3 PUSCH is determined as a value regardless of whether frequency hopping is enabled or not in a case that repetition is applied to the msg3 PUSCH, the parameter is determined as ‘pos1’ or ‘pos2’ based on whether frequency hopping is enabled or not in a case that repetition is not applied to the msg3 PUSCH.
Each of a program running on the base station device 3 and the terminal device 1 according to an aspect of the present invention may be a program that controls a Central Processing Unit (CPU) and the like, such that the program causes a computer to operate in such a manner as to realize the functions of the above-described embodiment according to the present invention. The information handled in these devices is transitorily stored in a Random-Access-Memory (RAM) while being processed. Thereafter, the information is stored in various types of Read-Only-Memory (ROM) such as a Flash ROM and a Hard-Disk-Drive (HDD), and when necessary, is read by the CPU to be modified or rewritten.
Note that the terminal device 1 and the base station device 3 according to the above-described embodiment may be partially achieved by a computer. In this case, this configuration may be realized by recording a program for realizing such control functions on a computer-readable recording medium and causing a computer system to read the program recorded on the recording medium for execution.
Note that it is assumed that the “computer system” mentioned here refers to a computer system built into the terminal device 1 or the base station device 3, and the computer system includes an OS and hardware components such as a peripheral device. Furthermore, the “computer-readable recording medium” refers to a portable medium such as a flexible disk, a magneto-optical disk, a ROM, a CD-ROM, and the like, and a storage device built into the computer system such as a hard disk.
Moreover, the “computer-readable recording medium” may include a medium that dynamically retains a program for a short period of time, such as a communication line that is used to transmit the program over a network such as the Internet or over a communication line such as a telephone line, and may also include a medium that retains a program for a fixed period of time, such as a volatile memory within the computer system for functioning as a server or a client in such a case. Furthermore, the program may be configured to realize some of the functions described above, and also may be configured to be capable of realizing the functions described above in combination with a program already recorded in the computer system.
Furthermore, the base station device 3 according to the above-described embodiment may be achieved as an aggregation (an device group) including multiple devices. Each of the devices configuring such an device group may include some or all of the functions or the functional blocks of the base station device 3 according to the above-described embodiment. The device group may include each general function or each functional block of the base station device 3. Furthermore, the terminal device 1 according to the above-described embodiment can also communicate with the base station device as the aggregation.
Furthermore, the base station device 3 according to the above-described embodiment may serve as an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) and/or NG-RAN (Next Gen RAN, NR-RAN). Furthermore, the base station device 3 according to the above-described embodiment may have some or all of the functions of a node higher than an eNodeB or the gNB.
Furthermore, some or all portions of each of the terminal device 1 and the base station device 3 according to the above-described embodiment may be typically achieved as an LSI which is an integrated circuit or may be achieved as a chip set. The functional blocks of each of the terminal device 1 and the base station device 3 may be individually achieved as a chip, or some or all of the functional blocks may be integrated into a chip. Furthermore, a circuit integration technique is not limited to the LSI, and may be realized with a dedicated circuit or a general-purpose processor. Furthermore, in a case that with advances in semiconductor technology, a circuit integration technology with which an LSI is replaced appears, it is also possible to use an integrated circuit based on the technology.
Furthermore, according to the above-described embodiment, the terminal device has been described as an example of a communication device, but the present invention is not limited to such a terminal device, and is applicable to a terminal device or a communication device of a fixed-type or a stationary-type electronic device installed indoors or outdoors, for example, such as an Audio-Video (AV) device, a kitchen device, a cleaning or washing machine, an air-conditioning device, office equipment, a vending machine, and other household devices.
The embodiments of the present invention have been described in detail above referring to the drawings, but the specific configuration is not limited to the embodiments and includes, for example, an amendment to a design that falls within the scope that does not depart from the gist of the present invention. Furthermore, various modifications are possible within the scope of one aspect of the present invention defined by claims, and embodiments that are made by suitably combining technical means disclosed according to the different embodiments are also included in the technical scope of the present invention. Furthermore, a configuration in which constituent elements, described in the respective embodiments and having mutually the same effects, are substituted for one another is also included in the technical scope of the present invention.
| Number | Date | Country | Kind |
|---|---|---|---|
| 2021-169633 | Oct 2021 | JP | national |
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/JP2022/039203 | 10/14/2022 | WO |
