WO2014174877A1 - 通信制御装置、通信制御方法、無線通信システム及び端末装置 - Google Patents
通信制御装置、通信制御方法、無線通信システム及び端末装置 Download PDFInfo
- Publication number
- WO2014174877A1 WO2014174877A1 PCT/JP2014/053348 JP2014053348W WO2014174877A1 WO 2014174877 A1 WO2014174877 A1 WO 2014174877A1 JP 2014053348 W JP2014053348 W JP 2014053348W WO 2014174877 A1 WO2014174877 A1 WO 2014174877A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- band
- component carrier
- communication control
- extension band
- extension
- Prior art date
Links
- 238000004891 communication Methods 0.000 title claims abstract description 289
- 238000000034 method Methods 0.000 title claims description 34
- 238000013468 resource allocation Methods 0.000 claims description 33
- 230000008859 change Effects 0.000 claims description 7
- 230000008054 signal transmission Effects 0.000 claims description 3
- 230000005540 biological transmission Effects 0.000 description 60
- 238000010586 diagram Methods 0.000 description 25
- 230000008569 process Effects 0.000 description 15
- 238000012545 processing Methods 0.000 description 14
- 101000631695 Homo sapiens Succinate dehydrogenase assembly factor 3, mitochondrial Proteins 0.000 description 10
- 102100028996 Succinate dehydrogenase assembly factor 3, mitochondrial Human genes 0.000 description 10
- 239000000969 carrier Substances 0.000 description 10
- 230000007246 mechanism Effects 0.000 description 9
- 230000002776 aggregation Effects 0.000 description 7
- 238000004220 aggregation Methods 0.000 description 7
- 230000004044 response Effects 0.000 description 6
- 101100533652 Homo sapiens SLIRP gene Proteins 0.000 description 5
- 101150039363 SIB2 gene Proteins 0.000 description 5
- 102100025491 SRA stem-loop-interacting RNA-binding protein, mitochondrial Human genes 0.000 description 5
- 230000006866 deterioration Effects 0.000 description 4
- 238000005070 sampling Methods 0.000 description 4
- 230000015556 catabolic process Effects 0.000 description 3
- 238000006243 chemical reaction Methods 0.000 description 3
- 238000006731 degradation reaction Methods 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 230000002146 bilateral effect Effects 0.000 description 2
- 239000004065 semiconductor Substances 0.000 description 2
- 230000001629 suppression Effects 0.000 description 2
- 101150096310 SIB1 gene Proteins 0.000 description 1
- 230000002411 adverse Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000010267 cellular communication Effects 0.000 description 1
- 125000004122 cyclic group Chemical group 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 230000000116 mitigating effect Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000009467 reduction Effects 0.000 description 1
- 230000011664 signaling Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 239000002699 waste material Substances 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/04—Wireless resource allocation
- H04W72/044—Wireless resource allocation based on the type of the allocated resource
- H04W72/0453—Resources in frequency domain, e.g. a carrier in FDMA
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04J—MULTIPLEX COMMUNICATION
- H04J11/00—Orthogonal multiplex systems, e.g. using WALSH codes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04J—MULTIPLEX COMMUNICATION
- H04J11/00—Orthogonal multiplex systems, e.g. using WALSH codes
- H04J11/0023—Interference mitigation or co-ordination
- H04J11/005—Interference mitigation or co-ordination of intercell interference
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04J—MULTIPLEX COMMUNICATION
- H04J11/00—Orthogonal multiplex systems, e.g. using WALSH codes
- H04J11/0069—Cell search, i.e. determining cell identity [cell-ID]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/0001—Arrangements for dividing the transmission path
- H04L5/0003—Two-dimensional division
- H04L5/0005—Time-frequency
- H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/0001—Arrangements for dividing the transmission path
- H04L5/0003—Two-dimensional division
- H04L5/0005—Time-frequency
- H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
- H04L5/001—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT the frequencies being arranged in component carriers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/003—Arrangements for allocating sub-channels of the transmission path
- H04L5/0044—Arrangements for allocating sub-channels of the transmission path allocation of payload
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/003—Arrangements for allocating sub-channels of the transmission path
- H04L5/0058—Allocation criteria
- H04L5/006—Quality of the received signal, e.g. BER, SNR, water filling
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/003—Arrangements for allocating sub-channels of the transmission path
- H04L5/0058—Allocation criteria
- H04L5/0069—Allocation based on distance or geographical location
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/14—Two-way operation using the same type of signal, i.e. duplex
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/20—Control channels or signalling for resource management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/50—Allocation or scheduling criteria for wireless resources
- H04W72/535—Allocation or scheduling criteria for wireless resources based on resource usage policies
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W74/00—Wireless channel access
- H04W74/08—Non-scheduled access, e.g. ALOHA
- H04W74/0866—Non-scheduled access, e.g. ALOHA using a dedicated channel for access
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/02—Terminal devices
Definitions
- the present disclosure relates to a communication control device, a communication control method, a wireless communication system, and a terminal device.
- LTE Long Term Evolution
- 3GPP Third Generation Partnership Project
- the bandwidth used for wireless communication is 1.4 MHz, 3 MHz, 5 MHz, 10 MHz, 15 MHz, and 20 MHz.
- Six options are defined (for example, see Non-Patent Document 1 below).
- LTE-A Long Term Evolution-Advanced
- LTE-Advanced which is an extension of LTE, introduces a technology called carrier aggregation that enables multiple component carriers each having one of the above-mentioned bandwidths to be used in an integrated manner. Is done. For example, when two component carriers each having a bandwidth of 20 MHz are used at the same time, a radio channel of 40 MHz in total can be formed.
- the frequency band assigned to the telecommunications carrier in each country does not necessarily conform to the bandwidth defined in LTE (hereinafter, the term LTE includes LTE-A). Therefore, when a telecommunications carrier operates an LTE system, there is a possibility that an excessive frequency band remains unused. Therefore, the following Non-Patent Document 2 sets up an extension band in an extra frequency band adjacent to a component carrier in order to improve the use efficiency of frequency resources, and the band filling (Band -Filling) is proposed.
- 3GPP “3GPP TS 36.104 V11.4.0”, March 22, 2013 AT & T, “NCT and Band Filling”, R1-130665, 3GPP TSG RAN WG1 Meeting # 728, January 28-February 1, 2013
- a communication control unit that controls wireless communication performed by one or more terminal devices on a component carrier having a basic bandwidth, the communication control unit is located above or below the component carrier A communication control device is provided that sets an extension band added to the component carrier only in any one of the surplus frequency bands.
- a communication control method including setting an extension band added to the component carrier only.
- a wireless communication system including one or more terminal devices and a communication control device, wherein the communication control device is either an upper side or a lower side of a component carrier having a basic bandwidth.
- the communication control device is either an upper side or a lower side of a component carrier having a basic bandwidth.
- a radio communication system in which an extension band added to the component carrier is set only in the surplus frequency band, and at least one of the terminal devices performs radio communication on the extension band.
- a communication control apparatus that controls wireless communication performed on a component carrier having a basic bandwidth, and only in an excess frequency band on either the upper side or the lower side of the component carrier,
- a wireless communication unit that communicates with the communication control device that sets an extension band to be added to the component carrier; and the wireless communication unit configured to transmit the wireless signal on the set extension band when the extension band is set by the communication control device.
- a control unit that causes the communication unit to perform wireless communication.
- FIG. 6B is an explanatory diagram for describing setting of an extension band in resource block units related to the example of FIG. 6A. It is explanatory drawing which shows an example of the expansion zone
- FIG. 1 is an explanatory diagram for explaining the outline of the LTE system.
- the LTE system 1 includes one or more base stations 10, one or more terminal devices 12, and a core network (CN) 16.
- CN core network
- the base station 10 is a communication control device that is also called eNB (evolved Node B) in LTE.
- the base station 10 provides a wireless communication service to the terminal device 12 located inside the cell 11.
- the base station 10 is connected to the core network 16.
- the terminal device 12 is a wireless communication device that is also called a UE (User Equipment) in LTE.
- the terminal device 12 is connected to the base station 10 and performs wireless communication.
- the base station currently connected by the terminal device 12 is called a serving base station of the terminal device 12.
- the serving base station performs various controls such as scheduling, rate control, retransmission control, and transmission power control for each terminal device 12.
- the core network 16 is also called EPC (Evolved Packet Core) in LTE, and various control nodes (not shown) such as MME (Mobility Management Entity), P-GW (PDN-Gateway), and S-GW (Serving-Gateway).
- MME Mobility Management Entity
- P-GW Packet Data Network
- S-GW Serving-Gateway
- A The MME manages the mobility of the terminal device 12.
- the S-GW is a gateway that transfers user plane packets for the terminal device 12.
- the P-GW is a gateway located at a connection point between the core network 16 and the packet data network (PDN) 17.
- PDN 17 may include IP networks such as the Internet and corporate networks.
- the radio link from the base station 10 to the terminal device 12 is a downlink (DL).
- the radio link from the terminal device 12 to the base station 10 is an uplink (UL).
- DL downlink
- UL uplink
- a group of frequency bands including various control channels and data channels defined for realizing a wireless communication service is called a component carrier.
- FDD frequency division duplex
- uplink CC uplink component carrier
- TDD time division duplex
- FIG. 2 is an explanatory diagram for explaining an example of the configuration of the downlink resource.
- one radio frame having a length of 10 msec is shown.
- One radio frame is composed of 10 subframes each having a length of 1 msec.
- One subframe includes two 0.5 ms slots.
- One 0.5 ms slot typically includes 7 OFDM symbols in the time direction (6 when extended cyclic prefix is used).
- One resource block is composed of one OFDM symbol and twelve subcarriers in the frequency direction.
- a resource for transmitting a synchronization signal and a broadcast channel (BCH) are arranged in six resource blocks located in the center of the component carrier in the frequency direction.
- BCH broadcast channel
- a resource for transmitting a synchronization signal is referred to as a synchronization resource.
- the terminal device receives the primary synchronization signal and the secondary synchronization signal on the synchronization resource in order to establish synchronization with the base station.
- the broadcast channel is used to broadcast a MIB (Master Information Block).
- the MIB carries static broadcast information such as component carrier bandwidth and base station antenna count.
- the dynamic broadcast information is carried by SIB (System Information Block) on DL-SCH (downlink shared channel).
- SIB System Information Block
- FIG. 3 is an explanatory diagram for explaining an example of the configuration of the uplink resource.
- one radio frame is composed of 10 subframes each having a length of 1 msec.
- One subframe includes two 0.5 ms slots.
- a reference sequence used by the base station to demodulate the uplink signal is arranged in the center in the time direction of each 0.5 ms slot.
- the random access channel PRACH
- PRACH is used by the terminal device to transmit a random access signal (random access preamble) to the base station.
- the terminal apparatus knows to which resource block the random access channel is assigned by receiving SIB (more specifically, SIB2 of SIB1 to SIB8).
- the physical uplink control channel (PUCCH) is used by the terminal device to transmit an uplink control signal.
- the physical uplink shared channel (PUSCH) is used by the terminal device to transmit an uplink data signal.
- the PUCCH is arranged at the band edge of the component carrier. Thereby, it is avoided that the peak-to-average power ratio (PAPR) of the uplink data signal is increased and the power efficiency is deteriorated.
- PAPR peak-to-average power ratio
- one radio frame is composed of 10 subframes each having a length of 1 msec. However, some of the 10 subframes are downlink subframes, and some are uplink subframes.
- the base station controls radio communication performed by the terminal device on a resource block basis. This is the same not only in FDD but also in TDD.
- the resource allocation information transmitted from the base station to the terminal device identifies the allocated resource block using a resource block number unique in the frequency domain.
- the resource allocation information may include scheduling information indicating resource allocation (DL allocation and UL grant) for data transmission, and channel allocation information indicating control channel allocation.
- the channel arrangement information is information indicating, for example, the above-described PRACH arrangement to the terminal device.
- Non-Patent Document 1 defines six options for the component carrier bandwidth in LTE. According to that definition, the bandwidth of the component carrier is 1.4 MHz, 3 MHz, 5 MHz, 10 MHz, 15 MHz or 20 MHz. These bandwidths are referred to herein as basic bandwidths. However, the frequency band allocated to the telecommunications carrier in each country does not necessarily match these basic bandwidths.
- FIG. 4A is an explanatory diagram for describing a first example of arrangement of component carriers in the frequency domain.
- the frequency band of 4 MHz can be used by the operator. Note that only one link direction is considered here for simplicity of explanation.
- an excess band having a bandwidth of 1 MHz remains. However, since the bandwidth of 1 MHz is less than any basic bandwidth, this surplus bandwidth is not utilized.
- FIG. 4B is an explanatory diagram for describing a second example of the arrangement of component carriers in the frequency domain.
- a 12 MHz frequency band can be used by the operator. If an operator sets four component carriers C11, C12, C13, and C14 each having a basic bandwidth of 3 MHz in an available frequency band and applies carrier aggregation to these component carriers, no excess band is generated. .
- this solution seems to be optimal in terms of frequency resource utilization efficiency.
- not all terminal apparatuses support carrier aggregation and terminal apparatuses that do not support carrier aggregation can use only one component carrier. Therefore, the solution of FIG. 4B actually includes a waste of resources (terminal devices that do not support carrier aggregation cannot use the 9 MHz bandwidth).
- LTE-A carrier aggregation has a restriction that the interval between the center frequencies of a plurality of CCs must be an integral multiple of 300 kHz, so that an optimal component carrier arrangement can be realized only in a limited case. .
- FIG. 4C is an explanatory diagram for describing a third example of the arrangement of component carriers in the frequency domain. Also in the third example, a 12 MHz frequency band can be used for the operator. Unlike the second example, when the carrier sets the component carrier C10 having a basic bandwidth of 10 MHz, the terminal device can use the component carrier C10 regardless of whether the carrier aggregation is supported. However, the solution of FIG. 4C leaves an extra band with a bandwidth of 2 MHz.
- Band-Filling is a concept for utilizing the surplus frequency band as illustrated in FIGS. 4A and 4C as an extension band that extends the bandwidth of the component carrier.
- FIGS. 4A and 4C there are some problems with band filling.
- Control signal overhead The bandwidth of the surplus frequency band is normally assumed to be smaller than the basic bandwidth. Therefore, if control resources (for example, synchronization resources, broadcast channels, and channels for other control signals) for causing the terminal device to use the extension band are arranged in the extension band, the resource for the control signal The overhead ratio is relatively large.
- extension bandwidth For the component carrier and the extension band added to the component carrier are handled as one frequency band, the total bandwidth is almost always six specified basic bandwidths. Not applicable.
- the bandwidth information broadcast to the terminal device in the existing MIB can only indicate one of the six basic bandwidths. Modifying the bandwidth information hinders normal operation of a terminal device (hereinafter referred to as a legacy terminal) that does not support wireless communication on the extended band. Therefore, it is possible to introduce a new information element for notifying the terminal device of the bandwidth of the extension band (hereinafter referred to as the extension bandwidth) without modifying the bandwidth information for the basic bandwidth in the MIB. desirable. However, if the extension bandwidth can take an arbitrary value, the number of bits of the new information element can be excessively large.
- the resource allocation information transmitted from the base station to the terminal apparatus identifies individual resources in units of resource blocks.
- resource block numbers are assigned to resource blocks in order from the lowest frequency.
- an extension band is set below the component carrier (lower frequency side) and a resource block number smaller than that of the component carrier is assigned to a resource block in the extension band, the legacy terminal There is a possibility of misunderstanding that the resource block number indicates a resource block in the component carrier.
- the transceiver of the device receiving the LTE radio signal can handle these six basic bandwidths. Need only be designed. Specifically, circuit parameters such as sampling rate, low-pass filter cutoff frequency, and FFT (Fast Fourier Transform) size may depend on the transmission / reception band (and its bandwidth). However, if the extension bandwidth is set to an arbitrary value, it is necessary to design a transmitter / receiver that operates correctly for every setting value of the extension band, which significantly increases the implementation cost of the apparatus. .
- the terminal device can detect the synchronization signal with a clue that the synchronization signal is transmitted in the center of the band of the downlink CC.
- the synchronization signal does not always exist in the center of the band including the downlink CC and the extension band. If the position of the synchronization signal becomes unknown, the terminal device must search for the synchronization signal blindly, and the time until detection becomes longer.
- the radio signal may cause inter-cell interference in an adjacent cell.
- the LTE base station has a mechanism called ICIC (Inter-Cell Interference Coordination) for suppressing inter-cell interference, but since the current ICIC is not designed in consideration of band filling, a cell caused by an extension band is used. It is beneficial to introduce additional mechanisms to suppress inter-interference.
- ICIC Inter-Cell Interference Coordination
- the PUCCH used for the terminal apparatus to transmit the uplink control signal allocates more continuous resource blocks to the terminal apparatus in the PUSCH. In order to make it possible, it is arranged at the band edge of the component carrier. However, when the extension band is set outside the band of the component carrier, the PUSCH of the component carrier and the channel in the extension band become discontinuous with the PUCCH interposed therebetween.
- the technology according to the present disclosure is for solving or alleviating at least one of the problems assumed in relation to band filling as described herein.
- [1-4. Extended bandwidth setting pattern] 5A to 5C are explanatory diagrams respectively showing three setting patterns for the extension band. These setting patterns are distinguished by the positional relationship between the component carrier and the extension band added to the component carrier.
- the first setting pattern is a one-sided setting
- the second setting pattern is a two-sided symmetric setting
- the third setting pattern is a two-sided asymmetric setting.
- FIG. 5A shows an example of one-side setting.
- the extension band is added to the component carrier only in the surplus frequency band on either the upper side or the lower side of the component carrier.
- downlink CC DC11 is arranged in the band from frequency F11 to frequency F12
- uplink CC UC14 is arranged in the band from frequency F15 to frequency F16.
- the extension band EB13 is an extension band added to the downlink CC DC11.
- the extension band EB13 occupies a band from the frequency F13 to the frequency F14 on the upper side of the downlink CC DC11.
- the extension band EB15 is an extension band added to the uplink CC UC14.
- the extension band EB15 occupies a band from the frequency F16 to the frequency F17 on the upper side of the uplink CC UC14.
- the gap between the upper end frequency F12 of the downlink CC DC11 and the lower end frequency F13 of the extension band EB13 is used as a guard band GB12.
- the guard band no radio signal is transmitted.
- the transceiver of the legacy terminal can suppress noise or interference caused by a radio signal on the extension band using, for example, a filter.
- the guard band is a band that is not used for radio signal transmission, the arrangement of the guard band has a negative effect from the viewpoint of resource utilization efficiency.
- the one-side setting is an effective setting pattern that realizes an appropriate balance between avoidance of deterioration of reception quality of the legacy terminal and resource utilization efficiency.
- the one-side setting is also a setting pattern that allows more continuous shared channels to be arranged in the uplink extension band than the two-side setting described later. Since the base station that receives the uplink signal knows the existence of the extension band, the protection band does not have to be arranged between the uplink CC UC14 and the extension band EB15.
- the extension band is set to have an extension bandwidth that is an integral multiple of the size of the resource block.
- one resource block has 12 subcarriers in the frequency direction. Since the subcarriers are arranged at a frequency interval of 15 kHz, the size of one resource block in the frequency direction (hereinafter referred to as RB size) is 180 kHz.
- the extension bandwidth can be expressed by the number of resource blocks.
- the extended bandwidth is transmitted to the terminal device with a small number of bits. Notification can be made.
- the guard band may be arranged in resource block units (ie, having a bandwidth that is an integral multiple of the RB size) or, for example, in units of subcarriers (ie, having a bandwidth that is an integral multiple of 15 kHz). ) May be arranged.
- the setting of the guard band may be explicitly notified to the terminal device. Instead, the notification of the protection band setting may be omitted, for example, by specifying the bandwidth in advance.
- the bandwidth of the protection band may be a part of the extended bandwidth notified to the terminal device.
- the base station does not schedule downlink transmission on the guard band, so that the terminal device does not substantially notice the existence of the guard band.
- a guard band can be realized.
- the overhead of information required for notification of the guard band can be reduced.
- FIG. 6A shows an example of bilateral symmetry setting.
- the extension band is added symmetrically to the component carrier in the upper and lower surplus frequency bands of the component carrier.
- downlink CC DC23 is arranged in a band from frequency F22 to frequency F23
- uplink CC UC27 is arranged in a band from frequency F27 to frequency F28.
- the extension band EB21 is a lower extension band added to the downlink CC DC23.
- the extension band EB21 occupies a band from the frequency F20 to the frequency F21.
- a guard band GB22 is arranged between the extension band EB21 and the downlink CC DC23.
- the extension band EB25 is an upper extension band added to the downlink CC DC23.
- the extension band EB25 occupies a band from the frequency F24 to the frequency F25.
- a guard band GB24 is arranged between the downlink CC DC23 and the extension band EB25.
- the extension band EB26 is a lower extension band added to the uplink CC UC27.
- the extension band EB26 occupies a band from the frequency F26 to the frequency F27.
- the extension band EB28 is an upper extension band added to the uplink CC UC27.
- the extension band EB28 occupies a band from the frequency F28 to the frequency F29.
- the guard band may not be arranged.
- the extension band is set to have an extension bandwidth that is an integral multiple of the size of the resource block.
- the extension bands EB21 and EB25 occupy 6 resource blocks in the frequency direction.
- the guard bands GB22 and G24 occupy two resource blocks in the frequency direction.
- the extension bands EB26 and EB28 occupy 8 resource blocks in the frequency direction.
- the guard bands may be symmetrically arranged in resource block units, or may be symmetrically arranged in subcarrier units, for example.
- the setting of the protection band may be explicitly notified to the terminal device or may not be notified to the terminal device.
- the bandwidth of the guard band is not explicitly notified to the terminal device, for example, the base station substantially does not schedule downlink transmission on the guard band.
- a guard band may be implemented, thereby reducing the information overhead required to notify the guard band and facilitating the base station to dynamically change the bandwidth of the guard band.
- FIG. 7A shows an example of both-side asymmetric setting.
- the extension band is asymmetrically added to the component carrier in the upper and lower surplus frequency bands of the component carrier.
- downlink CC DC33 is arranged in a band from frequency F32 to frequency F33
- uplink CC UC37 is arranged in a band from frequency F37 to frequency F38.
- the extension band EB31 is a lower extension band added to the downlink CC DC33.
- the extension band EB31 occupies a band from the frequency F30 to the frequency F31.
- a guard band GB32 is arranged between the extension band EB31 and the downlink CC DC33.
- the extension band EB35 is an upper extension band added to the downlink CC DC33.
- the extension band EB35 occupies a band from the frequency F34 to the frequency F35.
- a guard band GB34 is arranged between the downlink CC DC33 and the extension band EB35.
- the extension band EB36 is a lower extension band added to the uplink CC UC37.
- the extension band EB36 occupies a band from the frequency F36 to the frequency F37.
- the extension band EB38 is an upper extension band added to the uplink CC UC37.
- the extension band EB38 occupies a band from the frequency F38 to the frequency F39.
- the guard band may not be arranged.
- the extension band is set to have an extension bandwidth that is an integral multiple of the size of the resource block.
- the extension band EB31 occupies four resource blocks in the frequency direction.
- the guard bands GB32 and GB34 occupy two resource blocks in the frequency direction.
- the extension band EB35 occupies 8 resource blocks in the frequency direction.
- the extension band EB36 occupies 6 resource blocks in the frequency direction.
- the extension band EB38 occupies 10 resource blocks in the frequency direction.
- one-side setting is the best in terms of resource utilization efficiency, overhead reduction and uplink resource continuity. Therefore, in an embodiment described later, one-side setting is adopted as an extension band setting pattern.
- FIG. 8 is an explanatory diagram for explaining an example of arrangement of synchronization resources and broadcast channels in one-side setting.
- an extension band EB13 on the upper side of the downlink CC DC11 and the downlink CC DC11 is shown.
- Synchronization resources for transmitting the primary synchronization signal and the secondary synchronization signal are arranged in the six resource blocks in the center of the downlink CC DC11.
- This synchronization resource of the downlink CC DC11 is also used to synchronize the terminal device with the extension band EB13.
- both the legacy terminal and the non-legacy terminal can search for the synchronization signal on the synchronization resource of the component carrier in the cell search procedure.
- a non-legacy terminal can be implemented without changing the implementation of the existing cell search procedure. Further, even when the extension bandwidth is less than the minimum basic bandwidth, it is possible to appropriately synchronize the terminal device with the extension band by using the synchronization resource arranged in the component carrier instead of the extension band. .
- a physical broadcast channel (PBCH) for transmitting broadcast information is arranged in a resource block at the same frequency position as the synchronization resource.
- PBCH is a physical channel corresponding to BCH.
- Band filling (BF) setting information indicating an extended bandwidth or the like may be broadcast in, for example, an MIB on the PBCH. Further, the BF setting information may be broadcast in the SIB on the PDSCH. Instead, the BF setting information may be transmitted to individual terminal apparatuses on the PDCCH.
- the non-legacy terminal first receives the setting information on the component carrier after establishing synchronization with the downlink CC.
- the setting of the extension band can be acquired. Thereby, it is possible to smoothly shift the operation from the operation state in which the band filling is not performed to the operation state in which the band filling is performed.
- scheduling information for resource blocks in the extension band may be transmitted to the terminal device on the PDCCH of the downlink CC DC11 together with scheduling information for resource blocks in the component carrier.
- scheduling information for resource blocks in the extension band may be transmitted to the terminal device on the PDCCH of the downlink CC DC11 together with scheduling information for resource blocks in the component carrier.
- the PUCCH used for the terminal apparatus to transmit the uplink control signal is arranged at the band edge of the uplink CC.
- a terminal apparatus transmits a data signal it is desirable that as many consecutive resource blocks as possible in the PUSCH are allocated to the terminal apparatus in order to avoid an increase in PAPR.
- the legacy terminals that cannot use the extension band are used. It becomes difficult to allocate consecutive resource blocks in the PUSCH.
- the transmission of uplink non-data signals of non-legacy terminals is preferentially assigned to the extension band.
- FIG. 9 is an explanatory diagram for explaining an example of the arrangement of the uplink control channel in the one-side setting.
- an uplink CC UC14 and an extension band EB15 on the upper side of the uplink CC UC14 are shown.
- a physical uplink control channel (PUCCH) Ch11 is arranged at the band edge of the uplink CC UC14.
- a PUCCH Ch12 can be arranged at the band edge of the extension band EB15.
- Legacy terminals can use only the uplink CC UC14.
- a physical random access channel (PRACH) Ch13 for the legacy terminal is assigned to a resource block in the uplink CC UC14.
- PRACH physical random access channel
- PUSCH resource blocks other than PUCCH Ch11 and PRACH Ch13 in the uplink CC UC14 can be used for transmission of data signals by legacy terminals.
- a separate PRACH Ch14 for a non-legacy terminal is allocated to a resource block in the extension band EB15. This leaves more available (and continuous) PUSCH resource blocks in the uplink CC UC 14 for legacy terminals.
- the PRACH arrangement for non-legacy terminals described with reference to FIG. 9 can be notified to the legacy terminals separately from the channel arrangement information carried in SIB2 regarding the arrangement of the PRACH for legacy terminals.
- This new channel arrangement information may be broadcast using, for example, a new information element of the SIB in the downlink CC illustrated in FIG. 8, or may be transmitted to individual terminal apparatuses on the PDCCH.
- ACK / NACK for downlink transmission on the downlink CC and the downlink extension band may be transmitted to the base station after being processed and combined by the same HARQ process in the terminal device. Thereby, the resource overhead required for transmission of ACK / NACK can be reduced. Note that ACK / NACK for downlink transmission may be transmitted on PUCCH or PUSCH.
- each resource uses the resource block number assigned to the resource block in order from the lowest frequency. Identified.
- the extension band is added to the component carrier, it is desirable that the resource block number is unique through the component carrier and the extension band.
- the extension band is set in the lower band of the component carrier, if numbers are assigned to the resource blocks in order from the lowest frequency, the numbers given to the resource blocks in the lower extension band are It becomes smaller than the number given to the resource block in the carrier.
- FIG. 10A shows an example of such a situation.
- the extension band EB41 includes six resource blocks each having a resource block number from “0” to “5”.
- the downlink CC DC43 includes 16 resource blocks each having a resource block number from “6” to “21”. Note that the number of resource blocks in each of the component carrier and the extension band described here is merely an example for explanation. Each band may include more resource blocks or fewer resource blocks.
- the resource block number assigned to the resource block in the component carrier changes depending on the bandwidth of the extension band below the component carrier.
- the legacy terminal may misunderstand that the small resource block number given to the resource block in the extension band EB41 indicates the resource block in the component carrier DC43. If the legacy terminal misinterprets the resource block number, wireless communication by the legacy terminal will not operate normally. Therefore, in an embodiment, a resource block number is uniquely assigned to each resource block through the component carrier and the extension band, but any resource block included in the component carrier has a resource block number smaller than the resource block included in the extension band. The numbering rule of giving is adopted. Thereby, the risk that the legacy terminal misunderstands the meaning of the resource block number can be eliminated.
- FIG. 10B is an explanatory diagram for describing a first example of a new numbering rule for resource block numbers.
- a downlink CC DC43 and an extension band EB41 below the downlink CC DC43 are shown.
- a protection band GB42 exists between the extension band EB41 and the downlink CC DC43.
- a resource block number is assigned to one or more resource blocks in the downlink CC DC43 from zero in order from the lowest frequency.
- resource block numbers from “0” to “15” are assigned to the 16 resource blocks in the downlink CC DC43, respectively.
- resource block numbers from “16” to “21” are assigned to the resource blocks in the extension band EB41, respectively.
- the existence of the guard band is not considered in the resource block number numbering.
- FIG. 10C is an explanatory diagram for describing a second example of a new numbering rule for resource block numbers.
- resource block numbers are assigned to one or more resource blocks in the downlink CC DC43 from zero in order from the lowest frequency.
- resource block numbers from “0” to “15” are assigned to the 16 resource blocks in the downlink CC DC43, respectively.
- resource block numbers from “16” to “23” are assigned to the resource blocks in the extension band EB41 and the protection band GB42, respectively.
- the second example of the numbering rule can be used, for example, in a case where the bandwidth of the protection band is not explicitly notified to the terminal device. In this case, the terminal device can recognize the resource block in the guard band as a part of the extension band.
- the legacy terminal uses the resource block numbers from “0” to “15” to identify resource blocks in the downlink CC DC43. These resource block numbers do not change depending on whether or not an extension band is set and the bandwidth of the extension band. Therefore, the risk that the legacy terminal misunderstands the meaning of the resource block number is eliminated, and the backward compatibility of the numbering rule can be ensured.
- FIG. 11 is an explanatory diagram for explaining an example of BF setting information assumed for three setting patterns.
- the BF setting information is control information for notifying the non-legacy terminal of the extension band setting.
- the BF setting information includes six data items of “extension direction”, “bandwidth 1”, “bandwidth 2”, “protection bandwidth”, and “channel arrangement”.
- Extension direction is a category for identifying an extension band setting pattern.
- the value “0” or “1” of “extension direction” indicates one-side setting. If the value “0”, the extension band is above the component carrier, and if the value “1”, the extension band is below the component carrier. Is set.
- a value “2” of “extension direction” indicates a bilaterally symmetric setting.
- a value “3” of “extension direction” indicates a two-sided asymmetric setting. If only one-side setting can be selected as a system restriction, the “extension direction” may be a 1-bit flag indicating a value “0” or “1”. When only the bilaterally symmetric setting can be selected as a system constraint, the BF setting information may not include “extension direction” as an information element.
- “Bandwidth 1” is information indicating the bandwidth of the first extension band.
- “Bandwidth 2” is information indicating the bandwidth of the second extension band.
- “bandwidth 2” is omitted.
- bandwidth 2” is omitted, and two extension bands each having the extension bandwidth indicated by “bandwidth 1” are set on both sides of the component carrier.
- these “bandwidth 1” and “bandwidth 2” are indices based on the number of resource blocks corresponding to the extended bandwidth.
- the extension bandwidth is 180 kHz ⁇ N EB (N EB is an integer equal to or greater than 1)
- “Bandwidth 1” or “Bandwidth 2” may indicate N EB .
- the code is mapped to N EB, or may indicate some value that is calculated from the N EB.
- the BF setting information may include “extension direction”, “bandwidth 1”, and “bandwidth 2” for the downlink and uplink, respectively.
- “Protected bandwidth” is information indicating the bandwidth of the protected bandwidth arranged between the downlink CC and the extended bandwidth.
- the “protection bandwidth” may be an index based on the number of resource blocks corresponding to the protection bandwidth.
- the “protection bandwidth” may be an index based on the number of subcarriers corresponding to the protection bandwidth.
- the BF setting information may not include “protection bandwidth” as an information element.
- Channel arrangement is channel information indicating the arrangement of one or more control channels for non-legacy terminals.
- the channel information may indicate, for example, the arrangement of PUCCH and PRACH for non-legacy terminals that are arranged separately from the channels for legacy terminals. If a separate control channel is not allocated for a non-legacy terminal, the BF setting information may not include such channel allocation information.
- the number of data items of the BF setting information indicating the extension band setting is smaller than that when the two-sided asymmetric setting is adopted, and the two-sided symmetric setting is adopted.
- a 1-bit flag (“extension direction" indicating upper side or lower side) is only added.
- a base station transmits the resource allocation information produced
- the channel arrangement information described with reference to FIG. 11 is an example of resource allocation information.
- Another example of the resource allocation information is scheduling information indicating resource blocks allocated to each terminal device for data transmission.
- the scheduling information identifies the allocated resource block by specifying the start number and the number of blocks of the set of resource blocks allocated to the terminal device.
- the non-legacy terminal is designed to handle a start number that exceeds the number of resource blocks included in the component carrier and a number of blocks that exceeds the number of resource blocks. This makes it possible to identify resource blocks whose scheduling information for non-legacy terminals is included in the extended band. For example, assuming the example of FIG. 10B, when the scheduling information indicates the start number “16” and “number of blocks” 2, the two resource blocks at the lower end of the extension band EB41 are identified.
- the scheduling information identifies a set of resource blocks assigned to the terminal device in a bitmap format.
- a non-legacy terminal is designed to handle a bitmap up to a resource block number larger than scheduling information transmitted to the legacy terminal. This makes it possible to identify resource blocks whose scheduling information for non-legacy terminals is included in the extended band.
- the scheduling information transmitted to the legacy terminal is generated in the form of a 16-bit bitmap in the case where the bitmap with the highest granularity is selected.
- the scheduling information transmitted to the non-legacy terminal is generated in the form of an N-bit (N> 16) bitmap in the same case.
- the scheduling information is encoded using a terminal-specific ID (Identifier) and then transmitted to each terminal apparatus.
- PRACH placement information indicating the placement of PRACH is included in SIB2.
- PRACH is a physical channel that is used by a terminal device to transmit a random access preamble to a base station.
- the random access preamble is transmitted by a terminal device that connects to the base station for the first time, a terminal device that recovers from the sleep mode, or a terminal device that accesses the target base station in a handover procedure, for example, to estimate a timing offset specific to the terminal device used.
- the PRACH arrangement information includes a frequency offset indicating the arrangement of the PRACH in the frequency direction (for example, refer to “3GPP TS 36.211 V11.2.0”, 3GPP, February, 2013).
- the base station allocates the PRACH for the non-legacy terminal to the resource block in the extension band separately from the PRACH for the legacy terminal.
- a base station produces
- positioning information which shows arrangement
- the PRACH arrangement information for non-legacy terminals may indicate a frequency offset that exceeds the number of resource blocks included in the uplink CC.
- Non-legacy terminals are designed to handle PRACH placement information for such non-legacy terminals. Thereby, it becomes possible to identify the resource block in which the PRACH arrangement information for the non-legacy terminal is included in the extension band.
- channel arrangement information indicating the arrangement of channels other than the PRACH may be generated based on the resource block number assigned to each resource block according to the new numbering rule described above.
- FIG. 12 is an explanatory diagram for explaining a first example of a mechanism for suppressing noise or interference.
- the component carrier and the extension band added to the component carrier are set so that the arrangement of the synchronization resources is shifted between cells that overlap each other or are adjacent to each other.
- the extension band EB52 is set above the downlink CC DC51 in the cell C1, while the extension band EB54 is set below the downlink CC DC53 in the adjacent cell C2. (That is, the positional relationship between the component carrier and the extension band is reversed).
- the downlink CC DC51 has a synchronization resource and a broadcast channel in a band from the center frequency F51 to F52 in the frequency direction.
- the downlink CC DC53 has a resource for synchronization and a broadcast channel in a band from the center frequency F53 to F54 in the frequency direction.
- the arrangement of these synchronization resources and broadcast channels is shifted between adjacent cells in the frequency direction.
- FIG. 13 is an explanatory diagram for explaining a second example of a mechanism for suppressing noise or interference.
- resource blocks in the downlink extension band are allocated for downlink transmission of terminal equipment closer to the center of the cell.
- a cell 11a operated by the base station 10a and a cell 11b operated by the base station 10b are shown.
- the cells 11a and 11b are adjacent to each other.
- the terminal device 12a is a non-legacy terminal located inside the central region L1 of the cell 11a.
- the terminal device 12b is a non-legacy terminal located near the cell edge of the cell 11a.
- the terminal device 12c is a legacy terminal located in the cell 11a.
- the terminal device 12d is a legacy terminal located near the cell edge of the cell 11b.
- the base station 10a preferentially allocates resource blocks in the extension band to the terminal device 12a. Since the distance between the base station 10a and the terminal device 12a is relatively short, in the downlink transmission to the terminal device 12a, sufficient reception quality can be ensured even if the transmission power is small. If the transmission power is small, the downlink transmission does not adversely affect the legacy terminal 12c in the serving cell 11a and the legacy terminal 12d in the adjacent cell 11b (see arrows A1 and A2). On the other hand, the base station 10a preferentially allocates resource blocks in the downlink CC to the terminal device 12b. Since the distance between the base station 10a and the terminal device 12b is relatively long, high transmission power may be required in downlink transmission to the terminal device 12b.
- legacy terminals may recognize downlink transmissions on the extended band as noise or interference.
- downlink transmission is performed on the downlink CC instead of the extension band, interference caused by the downlink transmission is suppressed in a general reception circuit, or existing interference such as HII (High Interference Indicator) is used.
- HII High Interference Indicator
- the interference can be controlled using a control mechanism.
- the base station 100 may be a macro cell base station or a small cell base station.
- the small cell is a concept including a femtocell, a nanocell, a picocell, a microcell, and the like. Also, some of the functions of the base station 100 described here may be implemented in a control node in the core network 16 illustrated in FIG.
- FIG. 14 is a block diagram illustrating an example of the configuration of the base station 100.
- the base station 100 includes a wireless communication unit 110, a network communication unit 120, a storage unit 130, and a communication control unit 140.
- the radio communication unit 110 is a radio communication interface (or radio transceiver) that performs radio communication with one or more terminal devices.
- the wireless communication unit 110 transmits and receives a wireless signal on a frequency band set by the communication control unit 140 described later.
- the wireless communication unit 110 transmits and receives wireless signals to and from both legacy terminals and non-legacy terminals on a component carrier having a basic bandwidth.
- the wireless communication unit 110 transmits and receives wireless signals to and from non-legacy terminals on the extension band added to the component carrier.
- the downlink signal transmitted by the wireless communication unit 110 may include a primary synchronization signal and a secondary synchronization signal, a broadcast signal, a downlink control signal addressed to each terminal device, and a downlink data signal.
- the primary synchronization signal and the secondary synchronization signal for synchronizing the terminal device to the component carrier are typically transmitted on synchronization resources arranged in the six resource blocks in the center of the component carrier.
- the wireless communication unit 110 synchronizes the frame timing of the extension band with the frame timing of the component carrier.
- the non-legacy terminal can receive the primary synchronization signal and the secondary synchronization signal on the synchronization resource of the component carrier, and can also establish the synchronization for the extension band.
- the wireless communication unit 110 can transmit the setting information related to the extension band including the BF setting information described with reference to FIG. 11 not on the extension band but on the component carrier.
- the BF setting information may be broadcast to the terminal device, for example, in the MIB on the PBCH of the component carrier or the SIB on the PDSCH. Instead, the BF configuration information may be signaled to individual terminal apparatuses on the PDCCH of the component carrier.
- the radio communication unit 110 can transmit scheduling information (DL allocation and UL permission) related to the extension band on the PDCCH of the component carrier instead of the extension band. Thereby, it is possible to integrate the scheduling information for the component carrier and the scheduling information for the extension band into a single piece of information (for example, a set of a start number and the number of blocks, or a bitmap).
- the radio communication unit 110 may transmit ACK / NACK for uplink transmission on the uplink extension band on the PHICH of the component carrier instead of the extension band. Further, the radio communication unit 110 may receive ACK / NACK for downlink transmission on the downlink extension band on the PUCCH or PUSCH of the component carrier instead of the extension band.
- the network communication unit 120 is a communication interface connected to the core network 16 illustrated in FIG.
- the network communication unit 120 relays the communication packet included in the uplink signal received by the wireless communication unit 110 to the core network 16. Further, the network communication unit 120 receives a communication packet to be transmitted from the core network 16 using a downlink signal. Further, the network communication unit 120 can exchange control signals with a control node (for example, an MME) on the core network 16.
- the network communication unit 120 can exchange control signals with a base station of an adjacent cell, for example, via an X2 interface.
- the storage unit 130 stores a program and data for the operation of the base station 100 using a storage medium such as a hard disk or a semiconductor memory.
- the data stored by the storage unit 130 may include, for example, identification information (such as a terminal ID) and capability information for each terminal device connected to the base station 100.
- the capability information indicates whether each terminal device is a non-legacy terminal or a legacy terminal.
- Location information (which can be dynamically updated) for each of the terminal devices may be stored in the storage unit 130.
- the communication control unit 140 controls the overall operation of the base station 100 using a processor such as a CPU (Central Processing Unit) or a DSP (Digital Signal Processor).
- a processor such as a CPU (Central Processing Unit) or a DSP (Digital Signal Processor).
- the communication control unit 140 sets a component carrier (CC) having a basic bandwidth selected from six options of 1.4 MHz, 3 MHz, 5 MHz, 10 MHz, 15 MHz, and 20 MHz to an available frequency band. .
- CC component carrier
- the communication control unit 140 controls wireless communication performed by the legacy terminal and the non-legacy terminal on the component carrier in units of resource blocks.
- the communication control unit 140 adds the extension band added to the component carrier only to either the upper frequency band or the lower frequency band of the component carrier when the surplus frequency band exists.
- the bandwidth of the extension band may be an integer multiple of the RB size, for example.
- the extension band is added to the component carrier and extends the bandwidth of the component carrier.
- the communication control unit 140 generates BF setting information for notifying the terminal device of the extension band setting when setting the extension band.
- the BF setting information may include a flag for identifying the extension direction and bandwidth information indicating the extension bandwidth.
- the bandwidth information may be an index based on the number of resource blocks corresponding to the extended bandwidth.
- the communication control unit 140 sets a protection band in which no radio signal is transmitted between the downlink CC and the extension band. Thereby, the degradation of the reception quality in the legacy terminal due to the transmission of the downlink signal on the extension band is alleviated.
- the communication control unit 140 may explicitly notify the terminal device of the bandwidth of the protected bandwidth, for example, by including information indicating the protected bandwidth in the BF setting information. Instead, the communication control unit 140 may not explicitly notify the terminal device of the bandwidth of the protection band.
- the communication control unit 140 treats a part of the extension band as a protection band (in this case, the bandwidth of the protection band is also an integer multiple of the RB size), and transmits a downlink signal to the radio communication unit 110 on the protection band.
- the communication control unit 140 may dynamically change the bandwidth of the guard band according to the reception quality reported from the terminal device. On the other hand, the communication control unit 140 does not set a protection band between the uplink CC and the extension band added to the uplink CC.
- FIG. 15 is an explanatory diagram illustrating an example of setting an extension band set by the communication control unit 140.
- the extension band setting pattern is one-sided setting. Available frequency bands are 704 MHz to 716 MHz and 734 to 746 MHz.
- the communication control unit 140 sets the downlink CC DC61 having a basic bandwidth of 10 MHz to a band of 734.6 MHz to 743.6 MHz, and uplink CC UC64 having the same basic bandwidth of 10 MHz to 704.6 MHz to 713. Set to 6 MHz band respectively.
- the basic bandwidth is 10 MHz
- a channel gap is provided at both ends of the component carrier. Therefore, the effective bandwidth is 9 MHz, and the bandwidth includes 50 resource blocks in the frequency direction.
- the communication control unit 140 sets the extension band EB63 added to the downlink CC DC61 in the excess frequency band on the upper side of the downlink CC DC61.
- the extension band EB63 has an extension bandwidth of 1.44 MHz (743.96 MHz to 745.4 MHz) and includes eight resource blocks in the frequency direction.
- a protection band GB62 having a bandwidth corresponding to two resource blocks is set.
- the communication control unit 140 sets the extension band EB65 added to the uplink CC UC64 in the surplus frequency band on the upper side of the uplink CC UC64.
- the extension band EB65 has an extension bandwidth of 1.8 MHz (713.6 MHz to 715.4 MHz) and includes 10 resource blocks in the frequency direction. No guard band is set between the uplink CC UC64 and the extension band EB65.
- the extension band setting shown in FIG. 15 is merely an example for explanation.
- the communication control unit 140 may set the bandwidths of the component carrier, the extension band, and the protection band to values different from the above-described example. Further, the communication control unit 140 may set a different number of component carriers, extension bands, and guard bands from the above-described example. Further, as described with reference to FIG. 12, the communication control unit 140 is configured so that the positional relationship between the component carrier and the extension band in the frequency direction overlaps with each other or is inverted between adjacent cells. A carrier and an extension band may be set.
- the terminal device that communicates with the base station 100 includes a non-legacy terminal (first group of terminal devices) that supports wireless communication on the extended band and a legacy terminal (second group of terminals that does not support wireless communication on the extended band). Terminal device).
- the communication control unit 140 generates resource allocation information for legacy terminals that does not depend on whether or not an extension band is set and the extension bandwidth, and transmits the generated resource allocation information from the radio communication unit 110.
- the resource allocation information may include channel arrangement information indicating the arrangement of control channels such as PRACH. Further, the resource allocation information may include scheduling information indicating resource blocks allocated to each terminal device for data transmission. In such resource allocation information, each resource block is identified by using a resource block number uniquely assigned to each resource block through a component carrier and an extension band.
- a resource block number included in the component carrier is assigned a resource block number smaller than that of the resource block included in the extension band.
- the communication control unit 140 may generate resource allocation information for non-legacy terminals separately from resource allocation information for legacy terminals.
- the PRACH for non-legacy terminals can be arranged separately from the PRACH for legacy terminals.
- the communication control unit 140 may cause the PRACH arrangement information for the non-legacy terminal to be transmitted from the radio communication unit 110 for the non-legacy terminal separately from the PRACH arrangement information for the legacy terminal carried by the SIB2. Good.
- the communication control unit 140 may preferentially assign transmission of uplink control signals (for example, ACK / NACK for downlink transmission, CQI (Channel Quality Indicator), etc.) of non-legacy terminals to the extension band. . Also in this case, since the ratio of the resources used by the non-legacy terminal among the resources of the uplink CC is reduced, more continuous resource blocks can be allocated to the legacy terminal in the PUSCH.
- uplink control signals for example, ACK / NACK for downlink transmission, CQI (Channel Quality Indicator), etc.
- the communication control unit 140 may generate scheduling information for non-legacy terminals in a format different from the scheduling information for legacy terminals.
- the scheduling information for a non-legacy terminal is designed to handle a start number that exceeds the number of resource blocks included in the component carrier and a number of blocks that exceeds the number of resource blocks.
- scheduling information for non-legacy terminals is designed to handle bitmaps up to resource block numbers larger than scheduling information transmitted to legacy terminals. Thereby, the scheduling information about the component carrier and the scheduling information about the extension band can be integrated into a single piece of information.
- the communication control unit 140 allocates downlink transmission in the extended band for non-legacy terminals closer to the center of the cell, and performs downlink transmission in the downlink CC for legacy terminals and non-legacy terminals closer to the cell edge. It may be assigned. Thereby, since it is avoided that large transmission power is used in the downlink extension band, it is possible to suppress noise or interference generated in the legacy terminal due to the downlink signal transmitted in the extension band.
- the terminal device 200 may be an arbitrary type of wireless communication terminal such as a smartphone, a PC (Personal Computer), a PDA (Personal Digital Assistants), a PND (Portable Navigation Device), or a game terminal.
- the terminal device 200 is a non-legacy terminal that supports wireless communication on an extended band.
- FIG. 16 is a block diagram illustrating an example of the configuration of the terminal device 200.
- the terminal device 200 includes a wireless communication unit 210, a storage unit 220, and a control unit 230.
- the radio communication unit 210 is a radio communication interface (or radio transceiver) that performs radio communication with the base station 100.
- the radio communication unit 210 transmits a radio signal to the base station 100 and receives a radio signal from the base station 100 on a component carrier having a basic bandwidth.
- the wireless communication unit 210 transmits a radio signal to the base station 100 and receives a radio signal from the base station 100 on the extended band according to control by the communication control unit 234 described later.
- the radio communication unit 210 establishes synchronization with the downlink CC by detecting a primary synchronization signal and a secondary synchronization signal transmitted from the base station 100, for example.
- the radio communication unit 210 can establish synchronization with the extension band together with the downlink CC.
- the radio communication unit 210 receives broadcast information transmitted on the PBCH of the downlink CC.
- the broadcast information may include, for example, bandwidth information indicating the basic bandwidth of the component carrier.
- the wireless communication unit 210 further receives BF setting information indicating settings related to the extension band.
- the radio communication unit 210 may receive the BF setting information in the MIB on the PBCH, in the SIB on the PDSCH, or in individual signaling on the PDCCH.
- the parameters of the wireless communication unit 210 depending on the band are set according to some indexes included in the BF setting information.
- FIG. 17 is a block diagram illustrating an example of a detailed configuration of the wireless communication unit 210 illustrated in FIG.
- the wireless communication unit 210 includes a front end 211, a quadrature demodulation unit 212, a reception baseband unit 213, a transmission baseband unit 214, and a quadrature modulation unit 215.
- the front end 211 includes one or more transmit / receive antennas (ANT), a filter (FIL), an amplifier (AMP) and a bandpass filter (BPF) in the reception branch, a variable gain amplifier (VGA) in the transmission branch, a bandpass A filter (BPF), an amplifier (AMP), and an isolator (ISO) are included.
- ANT transmit / receive antennas
- FIL filter
- AMP amplifier
- BPF bandpass filter
- VGA variable gain amplifier
- BPF bandpass A filter
- AMP amplifier
- ISO isolator
- the quadrature demodulator 212 decomposes the received signal input from the front end 211 into an I component and a Q component at a frequency adjusted by a frequency synthesizer, and filters the I component and the Q component with a low-pass filter (LPF), respectively. .
- the low-pass filter removes out-of-band noise and aliasing noise that may be caused by AD conversion.
- the reception baseband unit 213 includes an analog-digital converter (A / D), a serial-parallel converter (S / P), a discrete Fourier transformer (DFT), a parallel-serial converter (P / S), and a demapper including.
- the analog-to-digital converter converts the received analog signal into a digital signal at a sampling rate corresponding to the reception band.
- the discrete Fourier transformer converts a frequency domain digital signal for each subcarrier input from the serial-parallel converter into a time domain digital signal.
- the transmission baseband unit 214 includes a mapper, a serial-parallel converter (S / P), an inverse discrete Fourier transformer (iDFT), a parallel-serial converter (P / S), and a digital-analog converter (D / A). )including.
- the inverse discrete Fourier transformer converts the time domain digital signal for each subcarrier input from the serial-parallel converter into a frequency domain digital signal.
- the digital-analog converter converts a digital signal into a transmission analog signal at a sampling rate corresponding to the transmission band.
- the orthogonal modulation unit 215 filters the I component and the Q component of the transmission analog signal input from the transmission baseband unit 214 with a low-pass filter (LPF), respectively, and modulates the signal to a radio frequency transmission signal at a frequency adjusted by a frequency synthesizer. To do. Then, the transmission signal generated by the orthogonal modulation unit 215 is output to the front end 211.
- LPF low-pass filter
- the cut-off frequency of the low-pass filter illustrated in FIG. 17, the sampling rate of A / D conversion and D / A conversion, and the FFT size of DFT and inverse DFT are adjusted depending on the transmission / reception band (and its bandwidth).
- Circuit parameter to be done These circuit parameters can be set according to a band setting signal generated by a communication control unit 234 described later based on an index included in the BF setting information.
- the wireless communication unit 210 can transmit and receive wireless signals on the extended band.
- the storage unit 220 stores a program and data for the operation of the terminal device 200 using a storage medium such as a hard disk or a semiconductor memory.
- the data stored by the storage unit 220 can include, for example, bandwidth information indicating a basic bandwidth and BF setting information.
- Control Unit 230 controls the overall operation of the terminal device 200 using a processor such as a CPU or DSP.
- the control unit 230 includes an application unit 232 and a communication control unit 234.
- Application section 232 implements higher layer applications.
- the application unit 232 generates data traffic to be transmitted to another device, and outputs the generated data traffic to the wireless communication unit 210.
- the application unit 232 processes data traffic received by the wireless communication unit 210 from another device.
- the communication control unit 234 controls wireless communication executed by the wireless communication unit 210 in accordance with a control signal received from the base station 100.
- Wireless communication between the terminal device 200 and the base station 100 is typically controlled in units of resource blocks.
- the communication control unit 234 sets the circuit parameters of the wireless communication unit 210 depending on the band in accordance with the basic bandwidth indicated by the broadcast information received by the wireless communication unit 210.
- the wireless communication unit 210 can transmit and receive wireless signals on the component carrier.
- the communication control unit 234 depends on the band in accordance with the extension bandwidth indicated by the BF setting information received by the wireless communication unit 210.
- the circuit parameters of the wireless communication unit 210 to be reset are reset (adjusted).
- the wireless communication unit 210 can transmit and receive wireless signals on the extension band in addition to the component carrier.
- the extension band is set to have an extension bandwidth that is an integral multiple of the RB size
- the BF setting information received by the wireless communication unit 210 is small based on the number of resource blocks corresponding to the extension bandwidth.
- the extended bandwidth can be expressed by the number of bits.
- the BF setting information may include a flag indicating whether the extension band is set on the upper side or the lower side of the component carrier.
- the communication control unit 234 causes the wireless communication unit 210 to perform wireless communication according to the resource allocation information received by the wireless communication unit 210.
- the resource allocation information may include channel arrangement information indicating the arrangement of control channels such as PRACH.
- the radio communication unit 210 connects to the base station 100 by transmitting a random access signal to the base station 100 on the legacy terminal PRACH indicated by the channel assignment information.
- a PRACH for a non-legacy terminal can be allocated to a resource block in an extension band, unlike a PRACH for a legacy terminal notified in SIB2.
- the radio communication unit 210 can transmit uplink control signals such as ACK / NACK and CQI for downlink transmission to the base station 100 on the PUCCH indicated by the channel assignment information.
- the resource allocation information may include scheduling information indicating resource blocks allocated to the terminal device 200 for data transmission.
- the radio communication unit 210 receives a downlink signal or transmits an uplink signal in a resource block indicated by scheduling information.
- the resource allocation information described above is generated based on the resource block number uniquely assigned to each resource block through the component carrier and the extension band.
- a resource block number included in the component carrier is assigned a resource block number smaller than that of the resource block included in the extension band. Therefore, the format of the resource allocation information received by the terminal device 200 that is a non-legacy terminal may be different depending on whether or not an extended band is set. For example, when the extension band is not set, the maximum value of the resource block number that can be specified by the resource allocation information corresponds to the number of resource blocks of the component carrier.
- the maximum value of the resource block number that can be specified by the resource allocation information is the number of resource blocks of the component carrier and the number of resource blocks of the extension band (which may include the protection band).
- the size of the scheduling information expressed in the bitmap format is larger when the extended band is set than when the extended band is not set.
- the communication control unit 234 interprets the resource allocation information according to the extension band setting, and controls the wireless communication executed by the wireless communication unit 210.
- the format of the resource allocation information received by the legacy terminal does not change depending on whether or not the extension band is set as a result of adopting the above-described new numbering rule.
- FIG. 18 is a flowchart illustrating an example of the bandwidth setting process executed by the base station 100.
- the communication control unit 140 of the base station 100 sets one or more component carriers in an available frequency band (step S1).
- the communication control unit 140 determines whether there is an excessive frequency band (step S2). If there is no surplus frequency band, the subsequent processing shown in FIG. 18 is skipped. If there is a surplus frequency band, the process proceeds to step S3.
- step S3 the communication control unit 140 sets an extension band in the surplus frequency band above or below the component carrier (step S3).
- the extension band set here is added to the component carrier and extends the basic bandwidth of the component carrier.
- the communication control unit 140 sets a band adjacent to the downlink CC as a protected band (step S4).
- the guard band may be treated as part of the extension band.
- the communication control unit 140 assigns a unique resource block number to the component carrier and the resource block in the extension band added to the component carrier according to the new numbering rule (step S5).
- the communication control unit 140 determines the arrangement of several channels (step S6). For example, the synchronization resource and the broadcast channel are arranged in the central resource block of the downlink CC.
- the PRACH for legacy terminals is arranged in a part of the PUSCH of the uplink CC.
- the PRACH for non-legacy terminals is arranged in the uplink extension band.
- the communication control unit 140 generates BF setting information including an index indicating the setting of the extension band (Step S7).
- the band setting process described here may be executed when the base station 100 initializes the operation of the cell, or during the operation (for example, periodically) to dynamically update the extension band setting. ) May be executed.
- FIGS. 19A and 19B are sequence diagrams illustrating an example of a flow of communication control processing according to an embodiment.
- the base station 100 sets one or more component carriers and one or more extension bands in an available frequency band by executing the band setting process described with reference to FIG. (Step S10).
- the base station 100 transmits the primary synchronization signal and the secondary synchronization signal on the synchronization resource arranged in the central resource block of the downlink CC (step S11).
- the terminal device 200 which is a non-legacy terminal, establishes synchronization with the base station 100 by receiving such a synchronization signal (step S13).
- the base station 100 transmits broadcast information including bandwidth information indicating the basic bandwidth on the broadcast channel of the downlink CC (step S15).
- the communication control unit 234 of the terminal device 200 sets the circuit parameters of the wireless communication unit 210 depending on the bandwidth in accordance with the basic bandwidth indicated by the received broadcast information (step S17). Note that the legacy terminal also receives these synchronization signals and broadcast information from the base station 100.
- the terminal device 200 transmits a connection request to the base station 100 on the uplink CC (step S19).
- the base station 100 transmits a connection permission to the terminal device 200 (step S21).
- the base station 100 transmits an inquiry signal for inquiring about the capability of the terminal device 200 to the terminal device 200 on the downlink CC (step S23).
- the terminal device 200 transmits a capability response to the base station 100 as a response to the inquiry signal from the base station 100 (step S25).
- the capability response transmitted here includes capability information indicating that the terminal device 200 is a non-legacy terminal, that is, supports wireless communication on an extended band.
- the base station 100 transmits BF setting information including an index indicating the setting of the extension band to the terminal device 200 (step S27).
- the communication control unit 234 of the terminal device 200 adjusts the circuit parameters of the wireless communication unit 210 depending on the bandwidth in accordance with the extension bandwidth (or the sum of the basic bandwidth and the extension bandwidth) indicated by the received BF setting information. Is adjusted (step S29).
- the terminal device 200 transmits a BF setting completion report to the base station 100 (step S31).
- the sequence moves to FIG. 19B.
- the base station 100 allocates downlink transmission to the terminal device 200 to the resource block in the extension band added to the downlink CC or the downlink CC. (Step S35).
- the base station 100 transmits scheduling information indicating downlink allocation to the terminal device 200, for example, on the PDCCH of the downlink CC (step S37).
- the base station 100 transmits downlink data to the terminal device 200 using the allocated resource block (step S39).
- the terminal device 200 transmits a scheduling request to the base station 100 (step S43).
- the base station 100 allocates uplink transmission from the terminal device 200 to the resource block in the extension band added to the uplink CC or uplink CC (step S45).
- the base station 100 transmits scheduling information indicating uplink permission to the terminal apparatus 200, for example, on the PDCCH of the downlink CC (step S47).
- the terminal device 200 transmits uplink data to the base station 100 using the allocated resource block (step S49).
- the base station 100 transmits the BF setting information to the terminal device 200 after the base station 100 confirms the capability of the terminal device 200 has been described.
- the base station 100 may broadcast, for example, BF setting information in the cell.
- FIG. 20 is a flowchart illustrating an example of a flow of scheduling processing executed by the base station 100.
- the communication control unit 140 of the base station 100 recognizes the necessity for scheduling (step S61).
- the communication control unit 140 can recognize the necessity of scheduling by recognizing that downlink data addressed to a certain terminal device has arrived or by receiving a scheduling request for uplink data from the terminal device.
- the communication control unit 140 determines the capability of the terminal device (step S62).
- the capability information of each terminal device may be acquired in advance through a response to the capability inquiry and stored in the storage unit 130 of the base station 100.
- the communication control unit 140 further determines the position of the non-legacy terminal (step S64).
- the position of the terminal may be measured using a GPS signal at the terminal and reported to the base station 100, or may be measured at the base station 100.
- the communication control unit 140 allocates a resource block in the extension band to the non-legacy terminal (step S66). .
- the communication control unit 140 allocates the resource block in the component carrier to the non-legacy terminal (step S67). Note that step S64 and step S65 may be omitted for the uplink. In that case, the uplink transmission of the non-legacy terminal is preferentially assigned to the resource block in the extension band.
- the communication control unit 140 allocates a resource block in the component carrier to the legacy terminal (step S67).
- the communication control part 140 produces
- the format of scheduling information for non-legacy terminals may be different from the format of scheduling information for legacy terminals.
- processing flow described with reference to FIGS. 18 to 20 is merely an example.
- the order of the processing steps may be changed, some processing steps may be omitted, or additional processing steps may be introduced.
- the extension band added to the component carrier is set only in the excess frequency band above or below the component carrier having the basic bandwidth. Therefore, for example, in the downlink, by setting one protection band between the component carrier and the extension band, it is possible to avoid deterioration of reception quality in the legacy terminal. Thereby, it is possible to realize an appropriate balance between avoidance of reception quality degradation and resource utilization efficiency. Also, in the uplink, it is possible to allow non-legacy terminals to perform uplink transmission with good power efficiency by ensuring a wide continuous bandwidth for the extension band.
- a synchronization resource for transmitting a synchronization signal for synchronizing a non-legacy terminal to both the component carrier and the extension band is allocated to the center of the downlink CC.
- the arrangement of the synchronization resources is the same as the arrangement when the extension band is not set. Therefore, the cell search procedure of the legacy terminal is not affected by whether or not the extension band is set. Further, since it is not necessary to arrange synchronization resources in an extension band having a relatively narrow bandwidth, it is possible to avoid an increase in the ratio of resource overhead.
- a broadcast channel may also be assigned to the center of the downlink CC.
- a cell caused by transmission on the extension band is configured by setting the positional relationship between the component carrier in the frequency direction and the extension band so as to overlap each other or to be inverted between adjacent cells. Interference can also be suppressed.
- a series of control processing by each device described in this specification may be realized using any of software, hardware, and a combination of software and hardware.
- the program constituting the software is stored in advance in a storage medium (non-transitory medium) provided inside or outside each device.
- Each program is read into a RAM (Random Access Memory) at the time of execution and executed by a processor such as a CPU.
- a communication control unit that controls wireless communication performed by one or more terminal devices on a component carrier having a basic bandwidth, The communication control unit sets an extension band added to the component carrier only in an excess frequency band on either the upper side or the lower side of the component carrier.
- Communication control device (2) The wireless communication is performed by a frequency division duplex (FDD) method, The component carrier is a downlink component carrier; The communication control unit sets a protection band in which a radio signal is not transmitted between the downlink component carrier and the extension band; The communication control device according to (1). (3) The communication control device according to (2), wherein the communication control unit does not set the protection band between an uplink component carrier and an extension band added to the uplink component carrier.
- FDD frequency division duplex
- the communication control unit allocates, in the center of the component carrier, a resource for transmitting a synchronization signal for synchronizing the terminal apparatus to both the component carrier and the extension band.
- the communication control apparatus according to any one of claims.
- Communication control device. The communication control device according to (5), wherein the communication control unit notifies the terminal device of the setting of the extension band using an index based on the number of resource blocks corresponding to the bandwidth of the extension band.
- the communication control unit sets the component carrier and the extension band so that a positional relationship between the component carrier and the extension band in the frequency direction overlaps each other or is inverted between adjacent cells.
- the communication control device includes: A wireless communication unit for transmitting setting information related to the extension band on the component carrier;
- the communication control device includes: A wireless communication unit for transmitting scheduling information related to the extension band to the terminal device on the component carrier;
- the one or more terminal devices include a first group of terminal devices that support wireless communication on the extended band and a second group of terminal devices that do not support wireless communication on the extended band,
- the communication control unit transmits resource allocation information that does not change depending on whether or not the extension band is set for the terminal devices of the second group.
- the communication control apparatus according to any one of (1) to (9).
- the resource allocation information is generated based on a resource block number uniquely assigned to each resource block through the component carrier and the extension band, The resource block included in the component carrier has the resource block number smaller than the resource block included in the extension band, regardless of whether the extension band is set on the upper side or the lower side of the component carrier. Granted, The communication control device according to (10).
- the wireless communication is performed by a frequency division duplex (FDD) method,
- the component carrier is an uplink component carrier, The communication control device according to (1).
- FDD frequency division duplex
- the communication control unit according to (13), wherein the uplink non-data signal transmission of the first group of terminal devices supporting wireless communication on the extension band is preferentially assigned to the extension band.
- Communication control device (15) The communication control device according to (14), wherein the non-data signal is a random access signal.
- (16) The communication control unit allocates a first random access channel for the terminal device of the first group to a resource block in the extension band, and performs radio communication on the extension band to a resource block in the component carrier.
- the communication control device according to (15), wherein a second random access channel for a second group of terminal devices that are not supported is allocated.
- a wireless communication system including one or more terminal devices and a communication control device, The communication control device sets an extension band added to the component carrier only in an excess frequency band on either the upper side or the lower side of the component carrier having a basic bandwidth, At least one of the terminal devices performs wireless communication on the extension band; Wireless communication system.
- a communication control apparatus for controlling wireless communication performed on a component carrier having a basic bandwidth, wherein the extension is added to the component carrier only in an excess frequency band on either the upper side or the lower side of the component carrier
- a wireless communication unit that communicates with the communication control device for setting a bandwidth
- a control unit that causes the wireless communication unit to execute wireless communication on the set extended band when the extended band is set by the communication control device
- a terminal device comprising: (20) The control unit sets parameters of the wireless communication unit depending on a band according to an index indicating the setting of the extension band received from the communication control device, The indicator indicates whether the extension band is set on the upper side or the lower side of the component carrier.
- Communication control device base station 110 wireless communication unit 140 communication control unit 200 terminal device (non-legacy terminal) 210 Wireless communication unit 234 Communication control unit
Landscapes
- Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Databases & Information Systems (AREA)
- Quality & Reliability (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
1.システムの概要
1-1.システムを構成するノード
1-2.リソースの構成
1-3.バンドフィリング
1-4.拡張帯域の様々な設定
1-5.主なチャネルの配置
1-6.リソースの識別
1-7.ノイズ又は干渉の抑制
3.基地局の構成例
4.端末装置の構成例
5.処理の流れ
5-1.帯域設定処理
5-2.通信制御処理
5-3.スケジューリング処理
6.まとめ
まず、図1~図3を用いて、LTEシステムの概要を説明する。
図1は、LTEシステムの概要について説明するための説明図である。図1を参照すると、LTEシステム1は、1つ以上の基地局10、1つ以上の端末装置12及びコアネットワーク(CN)16を含む。
基地局10から端末装置12への無線リンクは、ダウンリンク(DL)である。端末装置12から基地局10への無線リンクは、アップリンク(UL)である。LTEにおいて、無線通信サービスを実現するために定義される様々な制御チャネル及びデータチャネルを含むひとまとまりの周波数帯域を、コンポーネントキャリアという。LTEシステムが周波数分割複信(FDD)方式で動作する場合、ダウンリンクのコンポーネントキャリア(ダウンリンクCC)とアップリンクのコンポーネントキャリア(アップリンクCC)とは別々の周波数帯域である。LTEシステムが時間分割複信(TDD)方式で動作する場合、1つのコンポーネントキャリアにおいてダウンリンク送信及びアップリンク送信の双方が行われる。
非特許文献1のテーブル5.6-1は、LTEにおけるコンポーネントキャリアの帯域幅の6通りの選択肢を定義している。その定義によれば、コンポーネントキャリアの帯域幅は、1.4MHz、3MHz、5MHz、10MHz、15MHz又は20MHzである。これら帯域幅を、本明細書では基本帯域幅という。しかし、各国で通信事業者に割当てられている周波数帯域は、必ずしもこれら基本帯域幅に適合するわけではない。
余剰の周波数帯域の帯域幅は、通常、基本帯域幅よりも小さいと想定される。従って、拡張帯域を端末装置に利用させるための制御用リソース(例えば、同期用リソース、ブロードキャストチャネル、及びその他の制御信号のためのチャネル)を拡張帯域内に配置すると、制御信号のためのリソースのオーバヘッドの割合は相対的に大きくなる。
コンポーネントキャリアと当該コンポーネントキャリアに付加される拡張帯域とを1つの周波数帯域として扱う場合、その総帯域幅は、ほとんどの場合、仕様化された6通りの基本帯域幅に該当しない。一方で、既存のMIBにおいて端末装置へブロードキャストされる帯域幅情報は、6通りの基本帯域幅のいずれかを示すことしかできない。この帯域幅情報を改変することは、拡張帯域上での無線通信をサポートしない端末装置(以下、レガシー端末という)の正常な動作を阻害する。従って、MIB内の基本帯域幅のための帯域幅情報を改変することなく、拡張帯域の帯域幅(以下、拡張帯域幅という)を端末装置へ通知するための新たな情報要素を導入することが望ましい。但し、拡張帯域幅が任意の値を取り得るとすれば、新たな情報要素のビット数は過剰に大きくなり得る。
上述したように、基地局から端末装置へ送信されるリソース割当て情報は、リソースブロック単位で個々のリソースを識別する。通常は、周波数の低い方から順にリソースブロックにリソースブロック番号が付与される。しかし、コンポーネントキャリアの下側(より周波数の低い側)に拡張帯域が設定された場合にコンポーネントキャリアよりも小さいリソースブロック番号が拡張帯域内のリソースブロックに付与されるとすると、レガシー端末は、そのリソースブロック番号がコンポーネントキャリア内のリソースブロックを指していると誤解する恐れがある。
LTEでは基本帯域幅の選択肢が6通りのみであるため、LTEの無線信号を受信する装置の送受信機は、これら6通りの基本帯域幅を扱うことができるようにのみ設計されればよい。具体的には、サンプリングレート、ローパスフィルタのカットオフ周波数及びFFT(Fast Fourier Transform)サイズなどの回路パラメータが、送受信帯域(及びその帯域幅)に依存し得る。しかし、拡張帯域幅が任意の値に設定されるとすれば、拡張帯域のあらゆる設定値について正しく動作するような送受信機の設計が求められることになり、これは装置の実装コストを著しく増加させる。
ダウンリンクCCに隣接する余剰の周波数帯域に拡張帯域が設定される場合、レガシー端末にとっては、拡張帯域上で受信される信号がノイズとして認識される。レガシー端末の送受信機のローパスフィルタは、所望信号に近い周波数で受信されるこのノイズを完全には除去できない。そのため、拡張帯域上での無線信号の送信は、レガシー端末における受信品質を劣化させる恐れがある。
既存のセルサーチの手続によれば、端末装置は、ダウンリンクCCの帯域中央において同期信号が送信されることを手掛かりに同期信号を検出することができる。しかし、拡張帯域が設定される場合、ダウンリンクCCと拡張帯域とを含む帯域の中央に同期信号が存在するとは限らない。同期信号の位置が不明となれば、端末装置は盲目的に同期信号をサーチせざるを得ず、検出までの時間が長期化する。
あるセルにおいて拡張帯域上で無線信号が送信されると、その無線信号が隣接セルにおいてセル間干渉を引き起こし得る。LTEの基地局はセル間干渉を抑制するためのICIC(Inter-Cell Interference Coordination)と呼ばれる仕組みを有するが、現在のICICはバンドフィリングを考慮して設計されていないため、拡張帯域に起因するセル間干渉を抑制するための追加的な仕組みを導入することは有益である。
上述したように、端末装置がアップリンク制御信号を送信するために利用されるPUCCHは、PUSCHにおいてより多くの連続的なリソースブロックを端末装置に割当てることを可能とするために、コンポーネントキャリアの帯域端に配置される。しかし、コンポーネントキャリアの帯域の外側に拡張帯域が設定されると、コンポーネントキャリアのPUSCHと拡張帯域内のチャネルとはPUCCHを挟んで不連続になる。
図5A~図5Cは、拡張帯域の3通りの設定パターンをそれぞれ示す説明図である。これら設定パターンは、コンポーネントキャリアと当該コンポーネントキャリアに付加される拡張帯域との間の位置関係によって区別される。第1の設定パターンは片側設定、第2の設定パターンは両側対称設定、第3の設定パターンは両側非対称設定である。
図5Aは、片側設定の一例を示している。片側設定によれば、拡張帯域は、コンポーネントキャリアの上側又は下側のいずれかの余剰の周波数帯域においてのみ、コンポーネントキャリアに付加される。図5Aを参照すると、周波数F11から周波数F12までの帯域にダウンリンクCC DC11が、周波数F15から周波数F16までの帯域にアップリンクCC UC14がそれぞれ配置されている。拡張帯域EB13は、ダウンリンクCC DC11に付加される拡張帯域である。拡張帯域EB13は、ダウンリンクCC DC11の上側において周波数F13から周波数F14までの帯域を占める。拡張帯域EB15は、アップリンクCC UC14に付加される拡張帯域である。拡張帯域EB15は、アップリンクCC UC14の上側において周波数F16から周波数F17までの帯域を占める。
図6Aは、両側対称設定の一例を示している。両側対称設定によれば、拡張帯域は、コンポーネントキャリアの上側及び下側の余剰の周波数帯域においてコンポーネントキャリアに対称的に付加される。図6Aを参照すると、周波数F22から周波数F23までの帯域にダウンリンクCC DC23が、周波数F27から周波数F28までの帯域にアップリンクCC UC27がそれぞれ配置されている。拡張帯域EB21は、ダウンリンクCC DC23に付加される下側の拡張帯域である。拡張帯域EB21は、周波数F20から周波数F21までの帯域を占める。拡張帯域EB21とダウンリンクCC DC23との間には、保護帯域GB22が配置される。拡張帯域EB25は、ダウンリンクCC DC23に付加される上側の拡張帯域である。拡張帯域EB25は、周波数F24から周波数F25までの帯域を占める。ダウンリンクCC DC23と拡張帯域EB25との間には、保護帯域GB24が配置される。拡張帯域EB26は、アップリンクCC UC27に付加される下側の拡張帯域である。拡張帯域EB26は、周波数F26から周波数F27までの帯域を占める。拡張帯域EB28は、アップリンクCC UC27に付加される上側の拡張帯域である。拡張帯域EB28は、周波数F28から周波数F29までの帯域を占める。アップリンクにおいては、保護帯域は配置されなくてよい。
図7Aは、両側非対称設定の一例を示している。両側非対称設定によれば、拡張帯域は、コンポーネントキャリアの上側及び下側の余剰の周波数帯域においてコンポーネントキャリアに非対称的に付加される。図7Aを参照すると、周波数F32から周波数F33までの帯域にダウンリンクCC DC33が、周波数F37から周波数F38までの帯域にアップリンクCC UC37がそれぞれ配置されている。拡張帯域EB31は、ダウンリンクCC DC33に付加される下側の拡張帯域である。拡張帯域EB31は、周波数F30から周波数F31までの帯域を占める。拡張帯域EB31とダウンリンクCC DC33との間には、保護帯域GB32が配置される。拡張帯域EB35は、ダウンリンクCC DC33に付加される上側の拡張帯域である。拡張帯域EB35は、周波数F34から周波数F35までの帯域を占める。ダウンリンクCC DC33と拡張帯域EB35との間には、保護帯域GB34が配置される。拡張帯域EB36は、アップリンクCC UC37に付加される下側の拡張帯域である。拡張帯域EB36は、周波数F36から周波数F37までの帯域を占める。拡張帯域EB38は、アップリンクCC UC37に付加される上側の拡張帯域である。拡張帯域EB38は、周波数F38から周波数F39までの帯域を占める。アップリンクにおいては、保護帯域は配置されなくてよい。
(1)ダウンリンク
いずれの設定パターンが選択される場合においても、拡張帯域に端末装置を同期させるためにコンポーネントキャリアの同期用リソースを使用することにより、同期信号の送信に要するリソースのオーバヘッドの増加を回避することができる。この場合、基地局は、コンポーネントキャリアと当該コンポーネントキャリアに付加される拡張帯域とを、時間的に同期させて運用する。さらに、端末装置が拡張帯域を利用するために参照するブロードキャスト情報などの制御情報もまた、拡張帯域ではなくコンポーネントキャリア上で送信されてよい。
上述したように、端末装置がアップリンク制御信号を送信するために利用されるPUCCHは、アップリンクCCの帯域端に配置される。端末装置がデータ信号を送信する際には、PAPRの上昇を回避するために、可能な限り多くのPUSCH内の連続的なリソースブロックが端末装置に割当てられることが望ましい。しかし、仮に非レガシー端末による制御信号及びランダムアクセス信号(以下、これらを非データ信号と総称する)の送信のためにPUSCH内のリソースの多くが使用されると、拡張帯域を利用できないレガシー端末にPUSCH内の連続的なリソースブロックを割当てることは難しくなる。そこで、ある実施例において、非レガシー端末のアップリンクの非データ信号の送信は、拡張帯域に優先的に割当てられる。
(1)付番ルール
上述したように、通常、基地局から端末装置へ送信されるリソース割当て情報において、個々のリソースは、周波数の低い方から順にリソースブロックに付与されるリソースブロック番号を用いて識別される。コンポーネントキャリアに拡張帯域が付加される場合、コンポーネントキャリア及び拡張帯域を通じてリソースブロック番号が一意であることが望ましい。しかし、コンポーネントキャリアの下側の帯域に拡張帯域が設定される場合、周波数の低い方から順にリソースブロックに番号を付与すると、当該下側の拡張帯域内のリソースブロックに付与される番号は、コンポーネントキャリア内のリソースブロックに付与される番号よりも小さくなる。図10Aは、そうした状況の一例を示している。図10Aの例において、拡張帯域EB41は、「0」から「5」までのリソースブロック番号をそれぞれ有する6つのリソースブロックを含む。ダウンリンクCC DC43は、「6」から「21」までのリソースブロック番号をそれぞれ有する16個のリソースブロックを含む。なお、ここで説明するコンポーネントキャリア及び拡張帯域の各々のリソースブロック数は、説明のための例に過ぎない。各帯域は、より多くのリソースブロック又はより少ないリソースブロックを含んでもよい。
図11は、3通りの設定パターンについて想定されるBF設定情報の一例について説明するための説明図である。図8を用いて説明したように、BF設定情報は、拡張帯域の設定を非レガシー端末へ通知するための制御情報である。図11を参照すると、BF設定情報は、「拡張方向」、「帯域幅1」、「帯域幅2」、「保護帯域幅」及び「チャネル配置」という6つのデータ項目を含む。
ある実施例において、基地局は、上述した新たな付番ルールに従って各リソースブロックに付与されるリソースブロック番号に基づいて生成されるリソース割当て情報を、端末装置へ送信する。図11を用いて説明したチャネル配置情報は、リソース割当て情報の一例である。リソース割当て情報の他の例は、データ送信のために各端末装置に割当てられたリソースブロックを示すスケジューリング情報である。
非レガシー端末は、レガシー端末へ送信されるスケジューリング情報よりも大きいリソースブロック番号までのビットマップを扱い得るように設計される。それにより、非レガシー端末のためのスケジューリング情報が拡張帯域に含まれるリソースブロックを識別することが可能となる。例えば、図10Bの例を前提とすると、レガシー端末へ送信されるスケジューリング情報は、最も粒度の高いビットマップが選択されるケースにおいて、16ビットのビットマップの形式で生成される。一方、非レガシー端末へ送信されるスケジューリング情報は、同じケースにおいて、Nビット(N>16)のビットマップの形式で生成される。なお、いずれの形式においても、スケジューリング情報は、端末固有のID(Identifier)を用いて符号化された上で、各端末装置へ送信される。
本節では、拡張帯域に起因するノイズ又は干渉を抑制するための追加的な仕組みについて説明する。
本節では、一実施形態に係る基地局100の構成の一例について説明する。基地局100は、マクロセル基地局であってもよく、又はスモールセル基地局であってもよい。スモールセルは、フェムトセル、ナノセル、ピコセル及びマイクロセルなどを含む概念である。また、ここで説明する基地局100の機能の一部は、図1に例示したコアネットワーク16内の制御ノードにおいて実装されてもよい。
無線通信部110は、1つ以上の端末装置との無線通信を実行する無線通信インタフェース(あるいは、無線送受信機)である。無線通信部110は、後述する通信制御部140により設定される周波数帯域上で無線信号を送信し及び受信する。無線通信部110は、例えば、基本帯域幅を有するコンポーネントキャリア上で、レガシー端末及び非レガシー端末の双方と無線信号を送受信する。また、無線通信部110は、コンポーネントキャリアに付加される拡張帯域上で、非レガシー端末と無線信号を送受信する。
ネットワーク通信部120は、図1に例示したコアネットワーク16と接続される通信インタフェースである。ネットワーク通信部120は、無線通信部110により受信されるアップリンク信号に含まれる通信パケットを、コアネットワーク16へ中継する。また、ネットワーク通信部120は、ダウンリンク信号を用いて送信されるべき通信パケットをコアネットワーク16から受信する。また、ネットワーク通信部120は、コアネットワーク16上の制御ノード(例えば、MME)との間で制御信号を交換し得る。ネットワーク通信部120は、隣接セルの基地局との間で、例えばX2インタフェースを介して制御信号を交換し得る。
記憶部130は、ハードディスク又は半導体メモリなどの記憶媒体を用いて、基地局100の動作のためのプログラム及びデータを記憶する。記憶部130により記憶されるデータは、例えば、基地局100と接続する端末装置の各々についての識別情報(端末IDなど)及びケイパビリティ情報を含み得る。ケイパビリティ情報は、各端末装置が非レガシー端末及びレガシー端末のいずれであるかを示す。端末装置の各々についての(動的に更新され得る)位置情報が記憶部130により記憶されてもよい。
通信制御部140は、CPU(Central Processing Unit)又はDSP(Digital Signal Processor)などのプロセッサを用いて、基地局100の動作全般を制御する。
本節では、一実施形態に係る端末装置200の構成の一例について説明する。端末装置200は、例えばスマートフォン、PC(Personal Computer)、PDA(Personal Digital Assistants)、PND(Portable Navigation Device)又はゲーム端末などの任意の種類の無線通信端末であってよい。端末装置200は、拡張帯域上での無線通信をサポートする非レガシー端末である。
無線通信部210は、基地局100との間で無線通信を実行する無線通信インタフェース(あるいは、無線送受信機)である。無線通信部210は、基本帯域幅を有するコンポーネントキャリア上で、基地局100へ無線信号を送信し、及び基地局100から無線信号を受信する。また、無線通信部210は、後述する通信制御部234による制御に従って、拡張帯域上で、基地局100へ無線信号を送信し、及び基地局100から無線信号を受信する。無線通信部210は、例えば、基地局100から送信されるプライマリ同期信号及びセカンダリ同期信号を検出することにより、ダウンリンクCCとの同期を確立する。基地局100により拡張帯域が設定される場合、拡張帯域のフレームタイミングはコンポーネントキャリアのフレームタイミングと同期される。従って、この場合、無線通信部210は、ダウンリンクCCと共に拡張帯域との同期をも確立し得る。
記憶部220は、ハードディスク又は半導体メモリなどの記憶媒体を用いて、端末装置200の動作のためのプログラム及びデータを記憶する。記憶部220により記憶されるデータは、例えば、基本帯域幅を示す帯域幅情報、及びBF設定情報を含み得る。
制御部230は、CPU又はDSPなどのプロセッサを用いて、端末装置200の動作全般を制御する。本実施形態において、制御部230は、アプリケーション部232及び通信制御部234を有する。
本節では、図18~図20を用いて、上述した基地局100と端末装置200とにより構成される無線通信システムにおける処理の流れについて説明する。
図18は、基地局100により実行される帯域設定処理の流れの一例を示すフローチャートである。
図19A及び図19Bは、一実施形態に係る通信制御処理の流れの一例を示すシーケンス図である。
図20は、基地局100により実行されるスケジューリング処理の流れの一例を示すフローチャートである。
ここまで、本開示に係る技術の実施形態について詳細に説明した。上述した実施形態によれば、基本帯域幅を有するコンポーネントキャリアの上側又は下側のいずれかの余剰の周波数帯域にのみ、当該コンポーネントキャリアに付加される拡張帯域が設定される。従って、例えば、ダウンリンクにおいては、コンポーネントキャリアと拡張帯域との間に保護帯域を1つ設定することにより、レガシー端末における受信品質の劣化を回避することができる。それにより、受信品質の劣化の回避とリソース利用効率との間の適度なバランスを実現することができる。また、アップリンクにおいては、可能な限り広い連続的な帯域幅を拡張帯域のために確保することにより、非レガシー端末に良好な電力効率でアップリンク送信を行わせることができる。
(1)
基本帯域幅を有するコンポーネントキャリア上で1つ以上の端末装置により行われる無線通信を制御する通信制御部、を備え、
前記通信制御部は、前記コンポーネントキャリアの上側又は下側のいずれかの余剰の周波数帯域にのみ、前記コンポーネントキャリアに付加される拡張帯域を設定する、
通信制御装置。
(2)
前記無線通信は、周波数分割複信(FDD)方式で行われ、
前記コンポーネントキャリアは、ダウンリンクコンポーネントキャリアであり、
前記通信制御部は、前記ダウンリンクコンポーネントキャリアと前記拡張帯域との間に無線信号の送信されない保護帯域を設定する、
前記(1)に記載の通信制御装置。
(3)
前記通信制御部は、アップリンクコンポーネントキャリアと当該アップリンクコンポーネントキャリアに付加される拡張帯域との間に、前記保護帯域を設定しない、前記(2)に記載の通信制御装置。
(4)
前記通信制御部は、前記コンポーネントキャリア及び前記拡張帯域の双方に前記端末装置を同期させるための同期信号が送信されるリソースを、前記コンポーネントキャリアの中央に割当てる、前記(1)~(3)のいずれか1項に記載の通信制御装置。
(5)
前記通信制御部は、リソースブロック単位で前記無線通信を制御し、前記拡張帯域の帯域幅をリソースブロックのサイズの整数倍に設定する、前記(1)~(4)のいずれか1項に記載の通信制御装置。
(6)
前記通信制御部は、前記拡張帯域の帯域幅に対応するリソースブロック数に基づく指標を用いて、前記拡張帯域の設定を前記端末装置へ通知する、前記(5)に記載の通信制御装置。
(7)
前記通信制御部は、周波数方向の前記コンポーネントキャリアと前記拡張帯域との間の位置関係が、互いに重複し又は隣接するセルの間で反転するように、前記コンポーネントキャリア及び前記拡張帯域を設定する、前記(4)に記載の通信制御装置。
(8)
前記通信制御装置は、
前記拡張帯域に関連する設定情報を、前記コンポーネントキャリア上で送信する無線通信部、
をさらに備える、前記(1)~(7)のいずれか1項に記載の通信制御装置。
(9)
前記通信制御装置は、
前記拡張帯域に関連するスケジューリング情報を、前記コンポーネントキャリア上で前記端末装置へ送信する無線通信部、
をさらに備える、前記(1)~(8)のいずれか1項に記載の通信制御装置。
(10)
前記1つ以上の端末装置は、前記拡張帯域上での無線通信をサポートする第1グループの端末装置と前記拡張帯域上での無線通信をサポートしない第2グループの端末装置とを含み、
前記通信制御部は、前記拡張帯域が設定されるか否かに依存して変化しないリソース割当て情報を、前記第2グループの端末装置のために送信する、
前記(1)~(9)のいずれか1項に記載の通信制御装置。
(11)
前記リソース割当て情報は、前記コンポーネントキャリア及び前記拡張帯域を通じて各リソースブロックに一意に付与されるリソースブロック番号に基づいて生成され、
前記コンポーネントキャリアに含まれるリソースブロックには、前記拡張帯域が前記コンポーネントキャリアの上側又は下側のいずれに設定されるかに関わらず、前記拡張帯域に含まれるリソースブロックよりも小さい前記リソースブロック番号が付与される、
前記(10)に記載の通信制御装置。
(12)
前記リソース割当て情報は、前記コンポーネントキャリア上で送信されるチャネル配置情報及びスケジューリング情報のうち少なくとも1つを含む、前記(10)又は前記(11)に記載の通信制御装置。
(13)
前記無線通信は、周波数分割複信(FDD)方式で行われ、
前記コンポーネントキャリアは、アップリンクコンポーネントキャリアである、
前記(1)に記載の通信制御装置。
(14)
前記通信制御部は、前記拡張帯域上での無線通信をサポートする第1グループの端末装置のアップリンクの非データ信号の送信を、前記拡張帯域に優先的に割当てる、前記(13)に記載の通信制御装置。
(15)
前記非データ信号は、ランダムアクセス信号である、前記(14)に記載の通信制御装置。
(16)
前記通信制御部は、前記拡張帯域内のリソースブロックに前記第1グループの端末装置のための第1のランダムアクセスチャネルを割当て、前記コンポーネントキャリア内のリソースブロックに前記拡張帯域上での無線通信をサポートしない第2グループの端末装置のための第2のランダムアクセスチャネルを割当てる、前記(15)に記載の通信制御装置。
(17)
基本帯域幅を有するコンポーネントキャリア上で1つ以上の端末装置により行われる無線通信を制御することと、
前記コンポーネントキャリアの上側又は下側のいずれかの余剰の周波数帯域にのみ、前記コンポーネントキャリアに付加される拡張帯域を設定することと、
を含む通信制御方法。
(18)
1つ以上の端末装置と通信制御装置とを含む無線通信システムであって、
前記通信制御装置は、基本帯域幅を有するコンポーネントキャリアの上側又は下側のいずれかの余剰の周波数帯域にのみ、前記コンポーネントキャリアに付加される拡張帯域を設定し、
少なくとも1つの前記端末装置は、前記拡張帯域上で無線通信を実行する、
無線通信システム。
(19)
基本帯域幅を有するコンポーネントキャリア上で行われる無線通信を制御する通信制御装置であって、前記コンポーネントキャリアの上側又は下側のいずれかの余剰の周波数帯域にのみ、前記コンポーネントキャリアに付加される拡張帯域を設定する当該通信制御装置、と通信する無線通信部と、
前記通信制御装置により前記拡張帯域が設定された場合に、設定された前記拡張帯域上で前記無線通信部に無線通信を実行させる制御部と、
を備える端末装置。
(20)
前記制御部は、前記通信制御装置から受信される前記拡張帯域の設定を示す指標に従って、帯域に依存する前記無線通信部のパラメータを設定し、
前記指標は、前記拡張帯域が前記コンポーネントキャリアの上側又は下側のいずれに設定されたかを示す、
前記(19)に記載の端末装置。
110 無線通信部
140 通信制御部
200 端末装置(非レガシー端末)
210 無線通信部
234 通信制御部
Claims (20)
- 基本帯域幅を有するコンポーネントキャリア上で1つ以上の端末装置により行われる無線通信を制御する通信制御部、を備え、
前記通信制御部は、前記コンポーネントキャリアの上側又は下側のいずれかの余剰の周波数帯域にのみ、前記コンポーネントキャリアに付加される拡張帯域を設定する、
通信制御装置。 - 前記無線通信は、周波数分割複信(FDD)方式で行われ、
前記コンポーネントキャリアは、ダウンリンクコンポーネントキャリアであり、
前記通信制御部は、前記ダウンリンクコンポーネントキャリアと前記拡張帯域との間に無線信号の送信されない保護帯域を設定する、
請求項1に記載の通信制御装置。 - 前記通信制御部は、アップリンクコンポーネントキャリアと当該アップリンクコンポーネントキャリアに付加される拡張帯域との間に、前記保護帯域を設定しない、請求項2に記載の通信制御装置。
- 前記通信制御部は、前記コンポーネントキャリア及び前記拡張帯域の双方に前記端末装置を同期させるための同期信号が送信されるリソースを、前記コンポーネントキャリアの中央に割当てる、請求項1に記載の通信制御装置。
- 前記通信制御部は、リソースブロック単位で前記無線通信を制御し、前記拡張帯域の帯域幅をリソースブロックのサイズの整数倍に設定する、請求項1に記載の通信制御装置。
- 前記通信制御部は、前記拡張帯域の帯域幅に対応するリソースブロック数に基づく指標を用いて、前記拡張帯域の設定を前記端末装置へ通知する、請求項5に記載の通信制御装置。
- 前記通信制御部は、周波数方向の前記コンポーネントキャリアと前記拡張帯域との間の位置関係が、互いに重複し又は隣接するセルの間で反転するように、前記コンポーネントキャリア及び前記拡張帯域を設定する、請求項4に記載の通信制御装置。
- 前記通信制御装置は、
前記拡張帯域に関連する設定情報を、前記コンポーネントキャリア上で送信する無線通信部、
をさらに備える、請求項1に記載の通信制御装置。 - 前記通信制御装置は、
前記拡張帯域に関連するスケジューリング情報を、前記コンポーネントキャリア上で前記端末装置へ送信する無線通信部、
をさらに備える、請求項1に記載の通信制御装置。 - 前記1つ以上の端末装置は、前記拡張帯域上での無線通信をサポートする第1グループの端末装置と前記拡張帯域上での無線通信をサポートしない第2グループの端末装置とを含み、
前記通信制御部は、前記拡張帯域が設定されるか否かに依存して変化しないリソース割当て情報を、前記第2グループの端末装置のために送信する、
請求項1に記載の通信制御装置。 - 前記リソース割当て情報は、前記コンポーネントキャリア及び前記拡張帯域を通じて各リソースブロックに一意に付与されるリソースブロック番号に基づいて生成され、
前記コンポーネントキャリアに含まれるリソースブロックには、前記拡張帯域が前記コンポーネントキャリアの上側又は下側のいずれに設定されるかに関わらず、前記拡張帯域に含まれるリソースブロックよりも小さい前記リソースブロック番号が付与される、
請求項10に記載の通信制御装置。 - 前記リソース割当て情報は、前記コンポーネントキャリア上で送信されるチャネル配置情報及びスケジューリング情報のうち少なくとも1つを含む、請求項10に記載の通信制御装置。
- 前記無線通信は、周波数分割複信(FDD)方式で行われ、
前記コンポーネントキャリアは、アップリンクコンポーネントキャリアである、
請求項1に記載の通信制御装置。 - 前記通信制御部は、前記拡張帯域上での無線通信をサポートする第1グループの端末装置のアップリンクの非データ信号の送信を、前記拡張帯域に優先的に割当てる、請求項13に記載の通信制御装置。
- 前記非データ信号は、ランダムアクセス信号である、請求項14に記載の通信制御装置。
- 前記通信制御部は、前記拡張帯域内のリソースブロックに前記第1グループの端末装置のための第1のランダムアクセスチャネルを割当て、前記コンポーネントキャリア内のリソースブロックに前記拡張帯域上での無線通信をサポートしない第2グループの端末装置のための第2のランダムアクセスチャネルを割当てる、請求項15に記載の通信制御装置。
- 基本帯域幅を有するコンポーネントキャリア上で1つ以上の端末装置により行われる無線通信を制御することと、
前記コンポーネントキャリアの上側又は下側のいずれかの余剰の周波数帯域にのみ、前記コンポーネントキャリアに付加される拡張帯域を設定することと、
を含む通信制御方法。 - 1つ以上の端末装置と通信制御装置とを含む無線通信システムであって、
前記通信制御装置は、基本帯域幅を有するコンポーネントキャリアの上側又は下側のいずれかの余剰の周波数帯域にのみ、前記コンポーネントキャリアに付加される拡張帯域を設定し、
少なくとも1つの前記端末装置は、前記拡張帯域上で無線通信を実行する、
無線通信システム。 - 基本帯域幅を有するコンポーネントキャリア上で行われる無線通信を制御する通信制御装置であって、前記コンポーネントキャリアの上側又は下側のいずれかの余剰の周波数帯域にのみ、前記コンポーネントキャリアに付加される拡張帯域を設定する当該通信制御装置、と通信する無線通信部と、
前記通信制御装置により前記拡張帯域が設定された場合に、設定された前記拡張帯域上で前記無線通信部に無線通信を実行させる制御部と、
を備える端末装置。 - 前記制御部は、前記通信制御装置から受信される前記拡張帯域の設定を示す指標に従って、帯域に依存する前記無線通信部のパラメータを設定し、
前記指標は、前記拡張帯域が前記コンポーネントキャリアの上側又は下側のいずれに設定されたかを示す、
請求項19に記載の端末装置。
Priority Applications (6)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
BR112015026364A BR112015026364A2 (pt) | 2013-04-23 | 2014-02-13 | dispositivo de controle de comunicação, método de controle de comunicação, sistema de comunicação sem fio, e, dispositivo terminal |
JP2015513589A JP6468184B2 (ja) | 2013-04-23 | 2014-02-13 | 通信制御装置、通信制御方法、無線通信システム及び端末装置 |
EP14788039.7A EP2991421B8 (en) | 2013-04-23 | 2014-02-13 | Efficient lte commuication using bandwidth extension techniques |
CN201480021655.5A CN105144818B (zh) | 2013-04-23 | 2014-02-13 | 通信控制设备、通信控制方法、无线电通信系统和终端设备 |
RU2015144673A RU2643673C2 (ru) | 2013-04-23 | 2014-02-13 | Устройство и способ управления передачей данных, система радиосвязи и устройство терминала |
US14/785,343 US9736842B2 (en) | 2013-04-23 | 2014-02-13 | Communication control apparatus, communication control method, radio communication system and terminal apparatus for an extension band added to the component carrier to an excess frequency band either on an upper side or on a lower side of the component carrier |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2013-090285 | 2013-04-23 | ||
JP2013090285 | 2013-04-23 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2014174877A1 true WO2014174877A1 (ja) | 2014-10-30 |
Family
ID=51791462
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2014/053348 WO2014174877A1 (ja) | 2013-04-23 | 2014-02-13 | 通信制御装置、通信制御方法、無線通信システム及び端末装置 |
Country Status (8)
Country | Link |
---|---|
US (1) | US9736842B2 (ja) |
EP (1) | EP2991421B8 (ja) |
JP (1) | JP6468184B2 (ja) |
CN (1) | CN105144818B (ja) |
BR (1) | BR112015026364A2 (ja) |
RU (1) | RU2643673C2 (ja) |
TW (1) | TWI662844B (ja) |
WO (1) | WO2014174877A1 (ja) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPWO2017131065A1 (ja) * | 2016-01-29 | 2018-11-22 | 株式会社Nttドコモ | ユーザ端末及び無線通信方法 |
US20220070680A1 (en) * | 2018-12-27 | 2022-03-03 | Sony Group Corporation | Communication control apparatus, communication apparatus, and proxy apparatus |
Families Citing this family (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2014216698A (ja) * | 2013-04-23 | 2014-11-17 | ソニー株式会社 | 通信制御装置、通信制御方法、無線通信システム及び端末装置 |
US10264581B1 (en) * | 2016-12-09 | 2019-04-16 | Sprint Spectrum L.P. | Providing cellular service on partially-overlapping carriers |
JP6913750B2 (ja) * | 2017-01-06 | 2021-08-04 | パナソニック インテレクチュアル プロパティ コーポレーション オブ アメリカPanasonic Intellectual Property Corporation of America | 制御情報の送信 |
WO2018151565A1 (ko) * | 2017-02-15 | 2018-08-23 | 엘지전자 주식회사 | 협대역 사물 인터넷을 지원하는 무선 통신 시스템에서 단말과 기지국 간 신호 송수신 방법 및 이를 지원하는 장치 |
US10264464B1 (en) | 2017-02-16 | 2019-04-16 | Sprint Spectrum L.P. | Providing cellular service on a guest carrier fully encompassed by a host carrier |
CN114142982A (zh) * | 2018-07-12 | 2022-03-04 | 维沃移动通信有限公司 | 调度参数的确定方法、配置方法、终端和网络侧设备 |
CN111278160B (zh) * | 2019-03-29 | 2022-05-20 | 维沃移动通信有限公司 | 一种映射方法、终端设备及网络侧设备 |
EP3965490A4 (en) * | 2019-04-30 | 2022-05-11 | Fujitsu Limited | RESOURCE DETERMINATION METHOD, RESOURCE PROGRAMMING METHOD AND APPARATUS |
KR20210071470A (ko) * | 2019-12-06 | 2021-06-16 | 삼성전자주식회사 | 무선 통신 시스템에서 신호를 송수신하는 방법 및 장치 |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2011093093A1 (ja) * | 2010-01-28 | 2011-08-04 | パナソニック株式会社 | 制御情報送信装置、制御情報受信装置、及び制御情報送信方法 |
JP2013509843A (ja) * | 2009-11-02 | 2013-03-14 | クゥアルコム・インコーポレイテッド | 異種ネットワークにおけるスペクトル解釈 |
Family Cites Families (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7006482B1 (en) * | 1999-10-02 | 2006-02-28 | Samsung Electronics Co., Ltd. | Apparatus and method for gating data on a control channel in a CDMA communication system |
IL160921A (en) * | 2004-03-18 | 2009-09-01 | Veraz Networks Ltd | Method and device for quality management in communication networks |
US8989105B2 (en) * | 2009-03-17 | 2015-03-24 | Htc Corporation | Method of establishing multiple links with multiple component carriers and related communication device |
JP2011211619A (ja) * | 2010-03-30 | 2011-10-20 | Sony Corp | 通信制御装置、端末装置、無線通信システム、無線通信方法およびプログラム |
CN102595425B (zh) * | 2011-01-11 | 2015-06-10 | 上海贝尔股份有限公司 | 抗tdd和fdd频带间干扰的方法及通信方法和设备 |
US20140098785A1 (en) * | 2011-07-04 | 2014-04-10 | Telefonaktiebolaget L M Ericsson (Publ) | Methods and apparatuses for an extended bandwidth carrier |
CN103733560B (zh) * | 2011-08-12 | 2017-08-11 | 交互数字专利控股公司 | 用于无线系统中灵活的带宽操作的下行链路资源分配 |
US9209955B2 (en) * | 2011-10-11 | 2015-12-08 | Qualcomm Incorporated | Extension carrier as a bandwidth extension |
US9247542B2 (en) * | 2012-01-31 | 2016-01-26 | Apple Inc. | Methods and apparatus for efficient spectral usage in extensible carrier deployments |
-
2014
- 2014-02-13 CN CN201480021655.5A patent/CN105144818B/zh not_active Expired - Fee Related
- 2014-02-13 US US14/785,343 patent/US9736842B2/en active Active
- 2014-02-13 JP JP2015513589A patent/JP6468184B2/ja active Active
- 2014-02-13 BR BR112015026364A patent/BR112015026364A2/pt not_active Application Discontinuation
- 2014-02-13 RU RU2015144673A patent/RU2643673C2/ru not_active IP Right Cessation
- 2014-02-13 WO PCT/JP2014/053348 patent/WO2014174877A1/ja active Application Filing
- 2014-02-13 EP EP14788039.7A patent/EP2991421B8/en active Active
- 2014-04-14 TW TW103113543A patent/TWI662844B/zh not_active IP Right Cessation
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2013509843A (ja) * | 2009-11-02 | 2013-03-14 | クゥアルコム・インコーポレイテッド | 異種ネットワークにおけるスペクトル解釈 |
WO2011093093A1 (ja) * | 2010-01-28 | 2011-08-04 | パナソニック株式会社 | 制御情報送信装置、制御情報受信装置、及び制御情報送信方法 |
Non-Patent Citations (7)
Title |
---|
"NCT and Band Filling", RL-130665, 3GPP TSG RAN WG1 MEETING #728, 28 January 2013 (2013-01-28) |
3GPP TS 36.104 VI 1.4.0, 22 March 2013 (2013-03-22) |
3GPP TS 36.211 VII.2.0, February 2013 (2013-02-01) |
HUAWEI: "HiSilicon, On improved bandwidth scalability for CA enhancement", 3GPP TSG-RAN WG4#61, R4-115939, 18 November 2011 (2011-11-18), XP050567286 * |
KDDI: "Clarification for the Scope of First Phase NCT", 3GPP TSG-RAN WG1#72, R1-130203, XP050663364 * |
KDDI: "Views on Use Cases of New Carrier Type", REL-12, 3GPP TSG-RAN WG1#71, RL-125024, 16 November 2012 (2012-11-16), XP050662694 * |
See also references of EP2991421A4 |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPWO2017131065A1 (ja) * | 2016-01-29 | 2018-11-22 | 株式会社Nttドコモ | ユーザ端末及び無線通信方法 |
US20220070680A1 (en) * | 2018-12-27 | 2022-03-03 | Sony Group Corporation | Communication control apparatus, communication apparatus, and proxy apparatus |
Also Published As
Publication number | Publication date |
---|---|
TW201446022A (zh) | 2014-12-01 |
JP6468184B2 (ja) | 2019-02-13 |
BR112015026364A2 (pt) | 2017-07-25 |
EP2991421B1 (en) | 2020-06-17 |
US20160095118A1 (en) | 2016-03-31 |
RU2643673C2 (ru) | 2018-02-06 |
EP2991421A4 (en) | 2016-12-14 |
EP2991421A1 (en) | 2016-03-02 |
RU2015144673A (ru) | 2017-04-21 |
EP2991421B8 (en) | 2020-08-05 |
JPWO2014174877A1 (ja) | 2017-02-23 |
TWI662844B (zh) | 2019-06-11 |
US9736842B2 (en) | 2017-08-15 |
CN105144818A (zh) | 2015-12-09 |
CN105144818B (zh) | 2019-05-28 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP6468184B2 (ja) | 通信制御装置、通信制御方法、無線通信システム及び端末装置 | |
WO2014174878A1 (ja) | 通信制御装置、通信制御方法、無線通信システム及び端末装置 | |
JP6380383B2 (ja) | 通信制御装置、通信制御方法、無線通信システム及び端末装置 | |
US11825497B2 (en) | Frequency domain resource allocation for frequency division multiplexing schemes with single downlink control information associated with multiple transmission configuration indication states | |
WO2014174879A1 (ja) | 通信制御装置、通信制御方法、無線通信システム及び端末装置 | |
KR101971212B1 (ko) | 무선 통신 네트워크들에서 효율적인 자원 할당을 위한 시스템들 및 방법들 | |
US11051144B2 (en) | V2X communication method performed by V2X terminal in wireless communication system and terminal using same method | |
CN115349240A (zh) | 全双工时隙的频带配置 | |
Singh et al. | Improvement in SE for D2D communication: A review | |
WO2017202333A1 (zh) | 参考信号的传输方法及装置、网络设备和用户设备 | |
EP4147407B1 (en) | Sidelink shared channel demodulation reference signal configuration schemes |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 201480021655.5 Country of ref document: CN |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 14788039 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2015513589 Country of ref document: JP Kind code of ref document: A |
|
ENP | Entry into the national phase |
Ref document number: 2015144673 Country of ref document: RU Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2014788039 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 14785343 Country of ref document: US |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
REG | Reference to national code |
Ref country code: BR Ref legal event code: B01A Ref document number: 112015026364 Country of ref document: BR |
|
ENP | Entry into the national phase |
Ref document number: 112015026364 Country of ref document: BR Kind code of ref document: A2 Effective date: 20151016 |