Patent Grant
11115980
This disclosure relates to a base station and a radio terminal for mobile communication system.
Recently, studies have been made with respect to a radio terminal which is used in a Machine Type Communication (MTC) service where communication is performed without requiring human intervention. Such a radio terminal is requested to realize the reduction of a cost, providing a broader coverage, and the reduction of power consumption.
In a 3rd Generation Partnership Project (3GPP) which is a standardization project of a mobile communication system, a new radio terminal category is prescribed where a transmission/reception bandwidth is limited to only a portion of a system transmission/reception band.
In such a radio terminal which adopts the new category, a frequency bandwidth used for transmission and reception of a radio signal is limited. Accordingly, the radio terminal performs radio communication using a narrow frequency band which forms a part of a system transmission/reception band. The narrow frequency band has, for example, a frequency bandwidth of 1.08 MHz (that is, a frequency bandwidth of 6 resource blocks).
Under such circumstances, it is considered that there is a need in using an MTC not only to a sensor where only data communication of small capacity is expected but also to a wearable terminal or the like where data communication having larger capacity than the sensor is expected. To satisfy such a need, it is desirable to increase a throughput of the MTC.
A base station according to one embodiment performs radio communication with a radio terminal using at least one narrow frequency band where the number of resource blocks is limited to a predetermined resource block number. The base station comprises a transmitter configured to transmit, to the radio terminal, configuration information for frequency hopping where the radio communication is performed while switching the narrow frequency band; and a controller configured to allocate, to the radio terminal, a first frequency band of the frequency hopping and a frequency band of a hopping destination. The first frequency band and the frequency band of the hopping destination respectively include the narrow frequency band and fraction resource blocks. The fraction resource blocks are resource blocks, the number of which is smaller than the predetermined resource block number. The controller is configured to make the number of the fraction resource blocks included in the frequency band of the hopping destination equal to the number of the fraction resource blocks included in the first frequency band.
A user terminal according to one embodiment performs radio communication with a base station using at least one narrow frequency band where the number of resource blocks is limited to a predetermined resource block number. The user terminal a receiver configured to receive, from the base station, configuration information for performing frequency hopping where the radio communication is performed while switching the narrow frequency band, and allocation information relating to allocation of a first frequency band of the frequency hopping and a frequency band of a hopping destination, and a controller configured to control the radio communication using the frequency hopping based on the configuration information and the allocation information. The first frequency band and the frequency band of the hopping destination respectively include the narrow frequency band allocated from the base station. One frequency band out of the first frequency band and the frequency band of the hopping destination further includes the fraction resource blocks allocated from the base station. The fraction resource blocks are resource blocks, the number of which is smaller than the predetermined resource block number. The controller is configured to decide whether or not the fraction resource blocks are to be used in the radio communication with respect to the other frequency band out of the first frequency band and the frequency band of the hopping destination.
(Configuration of Mobile Communication System)
The configuration of a mobile communication system according to an embodiment is described.
As illustrated in
The UE 100 is a mobile communication apparatus, and performs radio communication with an eNB 200 which manages a cell (serving cell) in which the UE 100 per se exists.
The E-UTRAN 10 includes the base stations (eNBs: evolved Node-Bs) 200. The eNBs 200 are interconnected with each other via X2 interfaces. The eNB 200 manages one or a plurality of cells, and performs radio communication with the UE 100 which establishes connection with the own cell. The eNB 200 has a radio resource management (RRM) function, a routing function of user data (hereinafter, simply referred to as “data”), a measurement control function for a mobility control and scheduling and the like. “Cell” is used as a term indicating a minimum unit of a radio communication area, and is also used as a term indicating a function or a resource for performing radio communication with the UE 100.
The EPC 20 includes mobility management entities (MMEs) and serving gateways (S-GWs) 300. The MME applies various mobility controls and the like to the UE 100. The S-GW performs a data transmission control. The MMEs and the S-GWs are connected to the eNBs 200 via S1 interfaces.
The receiver 110 performs various receptions under a control of the controller 130. The receiver 110 includes an antenna and a reception device. The reception device outputs a radio signal which the antenna receives to the controller 130 after converting the radio signal into a baseband signal (reception signal).
The transmitter 120 performs various transmissions under a control of the controller 130. The transmitter 120 includes an antenna and a transmission device. The transmission device transmits a baseband signal (transmission signal) which the controller 130 outputs from the antenna after converting the baseband signal into a radio signal.
The controller 130 performs various controls in the UE 100. The controller 130 includes at least one processor and a memory. The memory stores programs executed by the processor and information used in processing performed by the processor. The processor may include a baseband processor which performs modulation/demodulation, coding/decoding and the like of the baseband signal, and a Central Processing Unit (CPU) which performs various processing by executing programs stored in the memory. The processor performs processing described later.
The transmitter 210 performs various transmissions under a control of the controller 230. The transmitter 210 includes an antenna and a transmission device. The transmission device transmits a baseband signal (transmission signal) which the controller 230 outputs from the antenna after converting the baseband signal into a radio signal.
The receiver 220 performs various receptions under a control of the controller 230. The receiver 220 includes an antenna and a reception device. The reception device outputs a radio signal which the antenna received to the controller 230 after converting the radio signal into a baseband signal (reception signal).
The controller 230 performs various controls in the eNB 200. The controller 230 includes at least one processor and a memory. The memory stores programs executed by the processor and information used for processing performed by the processor. The processor may include a baseband processor which performs modulation/demodulation and coding/decoding and the like of the baseband signal, and a CPU which performs various processing by executing programs stored in the memory. The processor performs processing described later.
The backhaul communication part 240 is connected to the neighboring eNB via the X2 interface, and is connected to the MME/S-GW 300 via the S1 interface. The backhaul communication part 240 is used for communication performed on the X2 interface, communication performed on the S1 interface and the like.
The PHY layer performs coding/decoding, modulation/demodulation, antenna mapping/demapping, and resource mapping/demapping. Data and control information are transmitted between the PHY layer of the UE 100 and the PHY layer of the eNB 200 via a physical channel.
The MAC layer performs a priority control of data, retransmission processing by a hybrid ARQ (HARQ), a random access procedure and the like. Data and control information are transmitted between the MAC layer of the UE 100 and the MAC layer of the eNB 200 via a transport channel. The MAC layer of the eNB 200 includes a scheduler which decides a transport format (a transport block size, a modulation/coding method (MCS)) of an uplink and a downlink and an allocation resource block to the UE 100.
The RLC layer transmits data to the RLC layer on a reception side using functions of the MAC layer and the PHY layer. Data and control information are transmitted between the RLC layer of the UE 100 and the RLC layer of the eNB 200 via a logical channel.
A PDCP layer performs header compression/expansion and ciphering/deciphering.
The RRC layer is defined only on a control plane where control information is handled. RRC signaling for various establishment is transmitted between the RRC layer of the UE 100 and the RRC layer of the eNB 200. The RRC layer controls a logical channel, a transport channel, and a physical channel in response to the establishment, the re-establishment and the release of a radio bearer. When the connection (RRC connection) is established between the RRC of the UE 100 and the RRC of the eNB 200, the UE 100 is in an RRC connected mode. On the other hand, when such connection is not established, the UE 100 is in an RRC idle mode.
A NAS layer positioned at a higher level of the RRC layer performs a session control, a mobility control and the like. NAS signaling is transmitted between the NAS layer of the UE 100 and the NAS layer of the MME 300C.
(Operation According to Embodiment)
The operation according to the embodiment is described.
As illustrated in
As illustrated in
In the MTC, repeated transmission is adopted for enhancing reachability of a signal from a transmission side to a reception side. For example, in uplink communication, as illustrated in
Under such a background, there is considered a need for using a MTC not only in a sensor where only data communication having a small capacity is estimated but also in a wearable terminal or the like where data communication having a larger capacity than the sensor is estimated. To satisfy such a need, the increase of throughput in the MTC is desirable. Accordingly, in this embodiment, for increasing throughput in the MTC, a case is estimated where the MTC UE 100 performs uplink communication using a frequency bandwidth wider than a bandwidth of the NB.
The MTC UE 100 according to the embodiment performs uplink communication while switching the NBs by frequency hopping. To be more specific, the MTC UE 100 performs transmission of a PUSCH while switching the NBs at a predetermined cycle.
As illustrated in
Transmitted at subframe #1:NB #1
Transmitted at subframe #2:NB #3
Transmitted at subframe #3:NB #5
Transmitted at subframe #4:NB #7
Transmitted at subframe #5:NB #1
In this specific example, the case is estimated a case where a frequency bandwidth of 10 MHz is used in place of a frequency bandwidth of 5 MHz illustrated in
As another example, assume a case where the hopping number is 3, the offset is 1, and the hopping interval is 1. The respective transmissions in frequency hopping are performed in accordance with the following subframes and NBs.
Transmitted at subframe #1:NB #1
Transmitted at subframe #2:NB #2
Transmitted at subframe #3:NB #3
Transmitted at subframe #4:NB #1
The RRC message may be a UE individual RRC message (for example, an RRC connection reconfiguration message). The RRC message may further include a parameter indicating a frequency band of 5 MHz. The UE 100 which receives the RRC message stores parameters included in the RRC message.
In step S2, the eNB 200 transmits an M-PDCCH to the MTC UE 100. The M-PDCCH includes allocation information indicating a frequency band of an uplink allocated to the MTC UE 100 from the eNB 200. Such allocation information may be also referred to as an uplink grant. Allocation information is information which indicates NBs and/or RBs allocated to the MTC UE 100 from the eNB 200. Information indicating the NBs and/or the RBs may be indexes of the NBs and/or the RBs, or information indicating the combination or a range of the NBs and/or the RBs. The M-PDCCH includes information indicating the number of times of repeated transmission of the PUSCH. The M-PDCCH includes a hopping flag indicating the start of application of frequency hopping. The MTC UE 100 which receives the M-PDCCH recognizes a frequency band allocated to the MTC UE 100. Further, the MTC UE 100 determines that frequency hopping is applied to the PUSCH transmission based on the hopping flag.
In step S3, the MTC UE 100, after a lapse of a predetermined subframe from a subframe in which MTC UE 100 receives an M-PDCCH, transmits a PUSCH to the eNB 200 using a frequency band allocated to the MTC UE 100. The PUSCH transmission in step S3 is first transmission of frequency hopping. A first frequency band of frequency hopping may be a frequency band explicitly designated in accordance with an M-PDCCH.
In step S4, the MTC UE 100 transmits a PUSCH to the eNB 200 using a frequency band of the hopping destination. The frequency band of the hopping destination is set based on a first frequency band and an RRC parameter. In step S4, data transmitted on the PUSCH may be data equal to data transmitted on the PUSCH in step S3.
In step S5, the MTC UE 100 transmits a PUSCH to the eNB 200 using a frequency band of next hopping destination. With respect to succeeding steps (step S5, step S6, . . . ), the MTC UE 100 performs PUSCH transmission the number of times which corresponds to the number of times of repeated transmission.
In such an operation, an RRC parameter for frequency hopping configures frequency hopping at an NB unit. On the other hand, a fraction RB which is smaller than 1NB (for example, 1RB illustrated in
In the operation pattern 1, the first allocation of the PUSCH and the allocation of the hopping destination (hopping) respectively include the fraction RB.
In the operation pattern 2, the first allocation of PUSCH includes the fraction RB. On the other hand, the allocation of the hopping destination (hopping) does not include the fraction RB.
In the operation pattern 3, the first allocation of the PUSCH does not include the fraction RB. On the other hand, the allocation of the hopping destination (hopping) includes the fraction RB.
Operation Pattern 1
In the operation pattern 1, the eNB 200 performs uplink communication with the MTC UE 100 which uses at least one NB limited to a predetermined RB number (6RB). The transmitter 210 of the eNB 200 transmits configuration information (RRC parameter) for frequency hopping where uplink communication is performed while switching an NB to the MTC UE 100. The controller 230 of the eNB 200 allocates the first frequency band of frequency hopping and a frequency band of the hopping destination to the MTC UE 100. The first frequency band and the frequency band of the hopping destination respectively include at least one NB and a fraction RB. The fraction RB is RBs, the number of which is smaller than a predetermined RB number (6RB). The controller 230 of the eNB 200 makes the number of fraction RBs included in the frequency band of the hopping destination agree with the number of fraction RBs included in the first frequency band.
In this manner, according to the operation pattern 1, a bandwidth of the first frequency band of the frequency hopping and a bandwidth of the frequency band of the hopping destination can be made equal to each other. Accordingly, PHY layer parameters which are respectively applied to the bandwidth of the first frequency band and the bandwidth of the frequency band of the hopping destination can be made equal to each other.
In the operation pattern 1, a fraction RB which the eNB 200 allocates to the MTC UE 100 is positioned adjacently to at least one NB which the eNB 200 allocates to the MTC UE 100. Accordingly, continuity of the RB can be ensured. Further, in the operation pattern 1, the controller 230 of the eNB 200 may allocate an RB to the MTC UE 100 such that the frequency positional relationship between an NB in the frequency band of the hopping destination and the fraction RB and the frequency positional relationship between an NB in the first frequency band and the fraction RB become opposite to each other.
As illustrated in
In
Operation Pattern 2
The operation pattern 2 is described mainly with respect to the difference between the operation pattern 2 and the operation pattern 1. In the operation pattern 2, the MTC UE 100 performs uplink communication with the eNB 200 using at least one NB limited to a predetermined RB number. The receiver 110 of the MTC UE 100 receives configuration information (RRC parameter) for frequency hopping where uplink communication is performed while switching an NB, and allocation information relating to allocation of a first frequency band of frequency hopping and a frequency band of a hopping destination from the eNB 200. The controller 130 of the MTC UE 100 controls uplink communication which uses frequency hopping based on configuration information and allocation information. The first frequency band and the frequency band of the hopping destination respectively include at least one NB allocated from the eNB 200. The first frequency band further includes a fraction RB allocated from the eNB 200. The controller 130 of the MTC UE 100 decides whether or not a fraction RB is to be used in uplink communication with respect to the frequency band of the hopping destination. In the same manner as the operation pattern 1, the fraction RB is an RB positioned adjacently to the NB.
The controller 130 of the MTC UE 100 decides whether or not a fraction RB is to be used in uplink communication with respect to a frequency band of the hopping destination based on a preset rule. For example, when the first frequency band includes a fraction RB, the controller 130 of the MTC UE 100 may determine that the fraction RB is allocated with respect to a frequency band of the hopping destination even when the fraction RB is not explicitly allocated to the frequency band of the hopping destination. Alternatively, when the first frequency band includes a fraction RB and the frequency band of the hopping destination does not include a fraction RB, the controller 130 of the MTC UE 100 may determine that the fraction RB is not allocated with respect to the frequency band of the hopping destination.
The controller 130 of the MTC UE 100 decides whether or not a fraction RB is to be used in uplink communication with respect to the frequency band of the hopping destination based on notification from the eNB 200. In this case, the receiver 110 of the MTC UE 100 receives notification information indicating whether or not a fraction RB is to be used in uplink communication with respect to the frequency band of the hopping destination from the eNB 200. Based on the notification information, the controller 130 of the MTC UE 100 decides whether or not a fraction RB is to be used in uplink communication with respect to the frequency band of the hopping destination. The notification information may be transmitted in the form of an RRC message (step S1 in
When the preset rule is used, notification from the eNB 200 becomes unnecessary and hence, signaling can be reduced. On the other hand, when notification from the eNB 200 is used, the eNB 200 can control whether or not a fraction RB is to be used in uplink communication with respect to the frequency band of the hopping destination.
Next, an operation when a fraction RB is not used at the hopping destination and an operation when a fraction RB is used at the hopping destination are described respectively.
As illustrated in
In this manner, when the fraction RB is not used at the hopping destination, the RB number of the first PUSCH transmission band and the RB number of the PUSCH transmission band of the hopping destination do not agree with each other. To be more specific, the RB number of the first PUSCH transmission band is larger than the RB number of the PUSCH transmission band of the hopping destination by an amount of a fraction RB. In this case, the RB number is linked with a transport block size (TBS) and hence, it is necessary to decide the TBS by taking into account the difference in RB number.
The controller 130 of the MTC UE 100 applies the TBS which corresponds to the RB number of the PUSCH transmission band of the hopping destination to both of the first PUSCH transmission band and the PUSCH transmission band of the hopping destination. In this case, the RB number of the PUSCH transmission band of the hopping destination is the RB number from which a fraction RB is excluded. That is, the controller 130 of the MTC UE 100 decides the TBS corresponding to the RB number from which the fraction RB is excluded, and applies the decided TBS to both of the first PUSCH transmission and the PUSCH transmission at the hopping destination. On the other hand, the controller 130 of the MTC UE 100 sets a coding rate applied to the first PUSCH transmission lower than a coding rate applied to the PUSCH transmission at the hopping destination. In other words, an amount of redundancy bits added to a transport block transmitted in accordance with the first PUSCH is increased compared to an amount of redundancy bits added to a transport block transmitted in accordance with a PUSCH at the hopping destination. The first PUSCH transmission and the PUSCH transmission at the hopping destination may adopt the same modulation system (modulation order).
Alternatively, the controller 130 of the MTC UE 100 may apply the TBS used in the first PUSCH transmission band to both of the first PUSCH transmission band and the PUSCH transmission band of the hopping destination. In this case, the eNB 200 decides an MCS such that the TBS becomes a TBS within a range where the TBS can be transmitted at the RB number of the PUSCH transmission band of the hopping destination (having no fraction RB) at the time of allocating the PUSCH, and notifies the decided MCS to the UE 100 in the form of an MPDCCH.
As illustrated in
Operation Pattern 3
The operation pattern 3 is described mainly with respect to a point which makes the operation pattern 3 different from the operation pattern 2. In the operation pattern 3, a first frequency band and a frequency band of a hopping destination respectively include an NB allocated from the eNB 200. The frequency band of the hopping destination further includes a fraction RB allocated from the eNB 200. The MTC UE 100 (controller 130) determines whether or not the fraction RB is to be used in uplink communication with respect to the first frequency band.
The controller 130 of the MTC UE 100 decides whether or not the fraction RB is to be used in the uplink communication with respect to the first frequency band based on the preset rule. For example, when the frequency band of the hopping destination includes the fraction RB, the controller 130 of the MTC UE 100 may determine that the fraction RB is allocated with respect to the first frequency band even when the fraction RB is not explicitly allocated to the first frequency band. Alternatively, when the frequency band of the hopping destination includes the fraction RB and the first frequency band does not include the fraction RB, the controller 130 of the MTC UE 100 may determine that the fraction RB is not allocated with respect to the first frequency band.
Further, the controller 130 of the MTC UE 100 decides whether or not the fraction RB is to be used in uplink communication with respect to the first frequency band based on notification from the eNB 200. In this case, the receiver 110 of the MTC UE 100 receives notification information indicating whether or not the fraction RB is to be used in uplink communication with respect to the first frequency band from the eNB 200. Based on the notification information, the controller 130 of the MTC UE 100 decides whether or not the fraction RB is to be used in uplink communication with respect to the first frequency band based on the notification information. The notification information may be transmitted in the form of an RRC message (step S1 in
Next, an operation when a fraction RB is not used in the first PUSCH transmission and an operation when a fraction RB is used in the first PUSCH transmission are described respectively.
As illustrated in
In this manner, when the fraction RB is not used in the first PUSCH transmission, the RB number in the first PUSCH transmission band and the RB number in the PUSCH transmission band of the hopping destination do not agree with each other. The controller 130 of the MTC UE 100 adopts a TBS which corresponds to the RB number of the first PUSCH transmission band in both of the first PUSCH transmission band and the PUSCH transmission band of the hopping destination. In this case, the RB number in the first PUSCH transmission band is an RB number from which a fraction RB is excluded. That is, the controller 130 of the MTC UE 100 decides a TBS which corresponds to the RB number from which the fraction RB is excluded, and adopts the decided TBS in both of the first PUSCH transmission and the PUSCH transmission at the hopping destination. The controller 130 of the MTC UE 100 sets a coding ratio which the first PUSCH transmission adopts lower than a coding ratio which the PUSCH transmission at the hopping destination adopts. The first PUSCH transmission and the PUSCH transmission at the hopping destination may adopt the same modulation method (modulation order).
On the other hand, when a fraction RB is used in the first PUSCH transmission, the controller 130 of the MTC UE 100 expands the first PUSCH transmission band in a specified frequency direction by an amount of the fraction RB. The eNB 200 may instruct the MTC UE 100 whether the first PUSCH transmission band is to be expanded in a low frequency direction or in a high frequency direction. Such an instruction may be transmitted in the form of an RRC message or in the form of an M-PDCCH. When a fraction RB is used in the first PUSCH transmission, the RB number in the first PUSCH transmission band and the RB number in the PUSCH transmission band of the hopping destination agree with each other and hence, it is unnecessary to take into account the difference in RB number.
Other operation examples in the operation pattern 3 are described. In the MTC UE 100, a fraction RB is not allocated from the eNB 200 to the first PUSCH transmission, and the fraction number RB is allocated from the eNB 200 to PUSCH transmission at the hopping destination. On the premise of such a configuration, the controller 130 of the MTC UE 100 reduces RBs in use in the NB by an amount of the fraction RB at the time of performing the PUSCH transmission at the hopping destination.
As an example, assume a case where 2NB (12RB) is allocated to the first PUSCH transmission, and the 2NB (12RB) and a fraction RB (1RB) sandwiched between the 2NB are allocated to the PUSCH transmission at the hopping destination. To be more specific, in the example illustrated in
In this manner, by reducing the RBs in use in the NB by an amount of a fraction RB in the operation pattern 3, the RB number can be set to the same number 12 between the first PUSCH transmission and the PUSCH transmission at the hopping destination while ensuring continuity of the RB.
In the PUSCH transmission at the hopping destination, RB which is not used in the PUSCH transmission (that is, RB to be reduced) may be decided based on a preset rule (for example, a rule where RB having the lowest frequency or RB having the highest frequency among allocated RBs in the NB is not used). Alternatively, the RB to be reduced may be explicitly designated from the eNB 200 to the UE 100. Such designation may be either dynamic designation or static designation.
(Modification)
With respect to the operation patterns 2 and 3, one example has been described where the TBS is decided corresponding to the RB number from which a fraction RB is excluded, and the decided TBS is adopted by both of the first PUSCH transmission and the PUSCH transmission at the hopping destination. Such a TBS decision method can be also used in the operation pattern 1. That is, the TBS may be decided corresponding to the RB number from which a fraction RB is excluded in a case where allocation in the first PUSCH transmission includes the fraction RB and the allocation in the PUSCH transmission at the hopping destination also include the fraction RB.
A fraction RB may not be counted in the number at the time of calculating the TBS regardless of the presence or the absence of a neighboring fraction RB.
In the embodiment, a scenario where allocation is made in terms of an NB unit is mainly estimated. However, a scenario may be estimated where only some RBs in the NB are used. For example, in a case where 2NBs are used within 1 subframe time, a scenario may be estimated where 8RBs in total is transmitted using RBs #3, 4, 5, 6 in the first NB and RBs #1, 2, 3, 4 in the second NB. Further, in such a scenario, 9RBs are transmitted when a fraction number RB is included between the first NB and the second NB. In these scenarios, it is necessary to read “NB and a fraction RB are positioned adjacently to each other” as “the RB which is actually allocated in the NB and the fraction RB are positioned adjacently to each other”.
In the embodiment, firstly, the first UE to which a fraction RB is not allocated (for example, the UE to which the 6RB is allocated) may decide a hopping destination resource of its own (first UE) such that a hopping destination resource which the second UE to which the fraction RB is allocated (for example, the UE to which the 7RB is allocated) uses is not selected in a frequency direction. In such a hopping control, a rule for calculating the hopping destination resource may be changed in response to the presence or the absence of execution of allocation of the fraction RB. The eNB 200 may notify the first UE whether or not the fraction RB is allocated (or a change in a resource calculation rule) to (other) UEs. The notification may be also transmitted in the form of EPDCCH.
In the embodiment, the description has been made mainly with respect to the case where the MTC is uplink communication. However, the embodiment is not limited to such a case. The embodiment is also applicable to a case where the MTC is downlink communication. For example, operations according to the embodiment may be applied to frequency hopping of a physical downlink shared channel (PDSCH).
In the embodiment, the description has been made mainly with respect to unicast transmission. However, the operations according to the embodiment may be applied to multicast/broadcast transmission. For example, the operations according to the embodiment may be applied to an SC-PTM where multicast transmission is performed using a PDSCH.
Although not specifically described in the embodiment, programs may be provided for allowing a computer to perform various processing which the MTC UE 100 and the eNB 200 perform. The programs may be recorded in a computer readable medium. The programs can be installed in the computer using the computer readable medium. The computer readable medium in which the programs are recorded may be a nonvolatile recording medium. Although the nonvolatile recording medium may not be particularly limited, the nonvolatile recording medium may be a recording medium such as a CD-ROM or a DVD-ROM.
Alternatively, a chip set may be provided where the chip set is formed of: a memory which stores programs for executing various processing which the MTC UE 100 and the eNB 200 perform; and a processor which executes the programs stored in the memory.
In the embodiment, the LTE system has been described as one example of a mobile communication system. However, the embodiment is not limited to the LTE system. The mobile communication system may be a system other than the LTE system.
(Note 1)
(Preface)
In RANP #72, approved is a further reinforced MTC for an LTE WI which includes a task for supporting a data rate higher than 1 Mbps for a voice compatible wearable device and a health monitoring device. In this specification, inventors of the present invention study problems still remaining in frequency hopping which requires a larger maximum bandwidth for acquiring a higher data rate.
The agreement was made on the following in RAN1 conference.
Agreed:
Agreed:
Agreed:
Frequency hopping at a higher data rate is agreed, and a Rel-13 frequency hopping RRC parameter is reused. The RRC parameter has a hopping offset and a hopping interval. When a frequency hopping flag during a DCI is in an ON state, hopping set using the RRC parameter is applied. Resource allocation of the frequency hopping is based on initial resource allocation instructed by the DCI.
With respect to PDSCH frequency hopping, resource allocation of a PDSCH is merely positioned within Rel-13NBs (narrowband) and hence, when Rel-13 frequency hopping follows a conventional RRC parameter, there arises no problem except for wrapping around. On the other hand, with respect to a PUSCH, the agreement was made that at least a PRB at the center which does not form a part of Rel-13 is supported. However, how to handle an RB at the center which does not form a part of an NB has not been decided. The PRB which does not form a part of the NB depends on a system bandwidth described in the following Table 2, and the following Table 3 describes how the state is divided into three cases.
The case 1 means that initial resource allocation includes PRB which does not form a part of Rel-13NB and PRB positioned adjacently to the PRB, and resource allocation after frequency hopping includes PRB which does not form a part of Rel-13NB or the PRB positioned adjacently to the PRB in the same manner. In this case, the UE has a chance of making use of both PRBs without additional instruction. However, the resource allocation after the frequency hopping is slightly changed from resource allocation instructed by the DCI.
Proposal 1: When the initial resource allocation includes the PRB which does not form a part of the Rel-13NB, the PRB which does not form a part of the Rel-13NB should be used for resource allocation after frequency hopping.
With respect to the case 2 and the case 3, only one of the initial resource allocation and the resource allocation after the frequency hopping does not have the PRB which does not form a part of the Rel-13NB. Accordingly, how to handle the PRB which does not form a part of the Rel-13NB should be decided. Inventors of the present invention propose the following two methods:
(1) PRB expansion in Rel-13NB
(2) The number of PRBs is adjusted in response to a presence of a PRB which does not form a part of an NB but is included in initial resource allocation or a PRB positioned adjacently to the PRB.
(1. PRB Expansion in Rel-13NB)
As illustrated in
(2. The Number of PRBs is Adjusted in Response to a Presence of a PRB which does not Form a Part of an NB but is Included in Initial Resource Allocation or a PRB Positioned Adjacently to the PRB.)
As illustrated in
To compare two methods, the PRB expansion in Rel-13NB may lower system efficiency because of the restriction imposed on scheduling for avoiding a collision. On the other hand, the second method can adjust a coding rate without affecting a conventional eMTC UE. Accordingly, the inventors of the present invention prefer that the second method is adopted in the Rel-14. From other point of view, it is not yet decided whether or not the PRB positioned at the end which does not form a part of the NB is to be supported. However, the second method is applicable to the case where the PRB at the end is supported for FeMTC transmission in the same manner.
Proposal 2: When the number of PRBs differs between initial resource allocation and frequency hopping resource allocation, the number of PRBs is adjusted in response to the presence of a PRB which does not form a part of an NB but is included in the resource allocation or a PRB positioned adjacently to the PRB.
(Note 2)
(1. Preface)
An RANP #72 includes a task for supporting a data rate higher than 1 Mbps for a voice compatible wearable device and a health monitoring device. A further reinforced MTC is approved for an LTE WI. In this specification, the inventors of the present invention study assignment of RBs for obtaining a higher data rate.
Agreed:
Agreed:
Agreed:
With respect to a Rel-14 non-BL UE configured with a PDSCH channel bandwidth having 20 MHz at maximum, continuous and non-continuous resource allocations are supported.
(2. Problems which Still Remain in Resource Allocation)
In the previous conference, the agreement was made that, in the RAN1, the BL and non-BL UE can support the following bandwidths described in the following Table 4. However, the detail of the resource allocation was not yet decided. It is necessary for the inventors of the present invention to study the resource allocation between a CE mode and a DL/UL mode separately. In this section, the inventors of the present invention have studied their observation with respect to the respective resource allocations one by one.
(2.1. Resource Allocation in BL/CE UE)
(2.1.1. CE Mode A)
In the RAN1 #87, proposals have been made by many enterprises with respect to various candidate resource allocation methods relating to a DL and a UL having a channel bandwidth of 5 MHz. The candidate methods are classified between a distributed type/localized type and an exclusive localized type. The distributed type/localized type means the combination of continuous and non-continuous resource allocations including the non-MTC UE. On the other hand, the exclusive localized type means only the continuous resource allocation. In this section, the inventors of the present invention described our observation share our observation based on the above-mentioned candidate resource allocation method.
(2.1.1.1. PDSCH)
In the RAN1, the agreement was made that “continuous and non-continuous resource allocations are supported with respect to the Rel-14 BL/CE UE configured with a PDSCH channel bandwidth having a maximum channel bandwidth of 5 MHz”. Accordingly, the agreement was made on the combination of the distributed type and localized type resource mappings with respect to a PDSCH. A resource allocation method of an exclusive localized type is excluded from candidates. The followings are selective resource allocations corresponding to the continuous and non-continuous resource allocations.
RAN1 #87 proposal
The alternative-1 and the alternative-2 have two types of instructions consisting of a start narrowband index and a wideband index. To compare these two instructions, a tradeoff exists between a bit size and scheduling flexibility. As shown in
Proposal 1: In RAN1, a start narrowband index is to be supported for multiplexing with a conventional UE.
Further, in a bandwidth having 5 MHz width or less, the carrier arrangement requires no indexing except for a case where narrowband indexing is used.
Opinion 1: The start narrowband index is used with respect to a system bandwidth having a bandwidth larger than 5 MHz such as 20 MHz.
The inventors of the present invention have studied three alternatives from viewpoints of scheduling flexibility, a bit size, and complexity of multiplexing with a conventional UE.
Alternative-1: Start Narrowband Index+NB Bit Map+Resource Allocation within Existing Narrowband
Alternative-2: Start Narrowband Index+Bit Map of RBG in 5 MHz Wideband
Alternative-3: Wideband Index+Distributed Type Allocation Based on Resource Allocation Type 2 within Wideband (Including Localized Type/Distributed Type Flag)
The summary of characteristics of these alternatives is described in the following Table 5. To take into account scheduling flexibility, a bit size, and multiplexing, the alternative-2 is most rational. Further, it is desirable that an RBG size be 2 or 3.
Proposal 2: With respect to a PDSCH in a CE mode A, a start narrowband index+a bit map of RBG within a 5 MHz wideband are to be supported. It is desirable that RBG size be 2 or 3.
*1 Case where only one resource allocation is instructed within existing narrowband
(2.1.1.2. PUCCH)
As described in Table 4, the BL/CE UE in a CE mode A supports 5 MHz PUSCH transmission. Further, in the RAN1, the agreement is made that “the PUSCH allocation to a FeMTC UE having a larger BW may include at least fixed PRBs which do not form a part of a narrowband prescribed in the LTE release 13”. This agreement means that, 25 PRBs are used with respect to the UL in a 5 MHz system bandwidth for continuous resource allocation and hence, a lower PAPR can be achieved. Accordingly, it is desirable that PUSCH resource allocation adopt continuous mapping with respect to a BL/CE UE in a CE mode A, and the following 5 candidates be listed up in the RAN1 87 with respect to continuous resource allocation.
RAN1 #87 proposal
Firstly, the existing PUSCH type 0 where the RIV is limited means that the RIV instructs a start RB position which changes from 0 to (system bandwidth−1) and a length limited by 25 PRBs. On the other hand, the alternative-C can instruct the start RB position and the length including a case where a bit size is larger than that of the alternative-B without optimization in the same manner. When the optimization is adopted, the bit size in the alternative-C is equal to the bit size in the alternative-B. Accordingly, the inventors of the present invention assume that the alternative-B and the alternative-C are equal and, hereinafter, the inventors of the present invention take into account only the alternative-B in remaining part of this section.
To compare scheduling flexibility among the above-mentioned five alternatives, a start point and granularity of resource allocation are based on RB granularity and hence, the alternative-B has the highest scheduling flexibility. The alternative-A and the alternative-E can instruct the NB start point+RB based on granularity of the resource allocation. Accordingly, scheduling flexibilities of the alternative-A and the alternative-E are lower than scheduling flexibility of the alternative-B. The alternative-D has granularity based on NBs and hence, the alternative-D has the lowest scheduling flexibility.
From a viewpoint of complexity of multiplexing of the UE with a conventional UE, none of alternatives have a problem. However, the difference exists from a viewpoint of the use of the resource. For example, in the alternative-B, multiplexing with the conventional UE can be realized using the same NBs. However, in the alternative-E, multiplexing with the conventional UE cannot be realized within the start NB. In the alternative-A, although no restriction is imposed on multiplexing with the conventional UE within the start NB, the number of RBs which can be allocated is decreased compared to the alternative-B. In the alternative-D, multiplexing can be made with the conventional UE within resource allocation which is neither the resource allocation of the start NB nor the resource allocation of the finish NB.
To take into account a higher data rate, the alternative-B is most desirable with respect to the BL/CE UE PUSCH in a CE mode A.
Proposal 3: With respect to the PUSCH in a CE mode A, an existing PUSCH type 0 is to be supported.
(2.1.2. CE Mode B with Respect to PDSCH)
In the previous conference, a maximum PDSCH which is further increased with respect to a CE mode B was adopted in the Rel-14, and a 5 MHz PDSCH was supported. To take into account resource allocation based on a conventional DCI6-1B used with respect to a PDSCH CE mode B, in most cases where resource allocation is repeated, large scheduling flexibility is unnecessary for the resource allocation. Accordingly, the DCI6-1B resource allocation has only 1 bit which means 4 PRBs or 6 PRBs with which the instruction of the NB index is expected. In addition to the above, even when fine resource allocation is supported, a scheduling gain is not large. Accordingly, a bit size is a most important factor with respect to a CE mode B. A small bit length can hold a DCI coding rate at a low level. Accordingly, the inventors of the present invention support the instruction “start NB index+NB bit map” with respect to a PDSCH in a CE mode B. For example, the start NB index and the NB bit map are formed of 8 bits (4 bits+4 bits) with respect to a 20 MHz system bandwidth.
Proposal 4: A start NB index+an NB bit map are to be supported with respect to a PDSCH in a CE mode B.
(2.2. Allocation of RBs with Respect to Non-BL UE)
(2.2.1. CE Mode A)
(2.2.1.1. PDSCH)
As described in Table 4, the non-BL UE in a CE mode A can support 5 MHz and 20 MHz. To take into account the reduction of efforts for standardization and the reduction of complexity, it is desirable that the same RB assigning method is adopted by both a BL/CE UE and a non-BL UE. Accordingly, the inventors of the present invention support “start narrowband index+bit map of RBG”. However, the non-BL UE is configured to receive 20 MHz and hence, a start narrowband index becomes unnecessary.
Proposal 5: A start narrowband index+a bit map of RBG are to be supported with respect to a PDSCH of a non-BL UE in a CE mode A. When the non-BL UE operates a 20 MHz PDSCH, a start narrowband index is to be excluded.
(2.2.1.2. PUSCH)
A PUSCH with respect to a non-BL UE in a CE mode A supports the same 5 MHz as a PUSCH of a BL/CE UE in a CE mode A. Accordingly, it is unnecessary for the inventors of the present invention to support an additional new resource allocation method. The inventors of the present invention support the same method which is an existing PUSCH type 0.
Proposal 6: An existing PUSCH type 0 is to be supported with respect to a non-BL UE which operates a 5 MHz PUSCH in a CE mode A.
(2.2.2. CE Mode B)
(2.2.2.1. PDSCH)
With respect to a non-BL UE PDSCH in a CE mode B, a UE is established at 1.4 MHz, 5 MHz, or 20 MHz. To take into account the reduction of efforts for standardization and the reduction of complexity, it is desirable to adopt the same RB assigning method. A 1.4 MHz channel bandwidth is equal to a channel bandwidth of a conventional eMTC. Accordingly, a conventional resource allocation method (a narrowband index+1 bit) can be reused. On the other hand, with respect to 5 MHz and 20 MHz, resource allocation is to be based on a 5 MHz BL/CE UE. This means that a start NB index+an NB bit map is to be supported. However, when the UE is established at 20 MHz, the BL/CE UE performs reception over the entire bandwidth and hence, a start NB index becomes unnecessary.
Proposal 7: Resource allocation (a narrowband index and 1 bit) of a Rel-13eMTC with respect to a PDSCH in a CE mode B is to be reused with respect to a non-BL UE PDSCH in a CE mode B within 1.4 MHz bandwidth.
Proposal 8: A narrowband index+an NB bit map are to be supported with respect to a non-BL UE PDSCH in a CE mode B at 5 MHz and 20 MHz. When a non-BL UE operates a 20 MHz PDSCH, a start narrowband index is to be excluded.
(2.2.2.2. PUSCH)
A PUSCH with respect to a non-BL UE in a CE mode B supports 1.4 MHz which is the same bandwidth as Rel-13eMTC resource allocation. Accordingly, it is unnecessary for the inventors of the present invention to support an additional new resource allocation method. The inventors of the present invention support the same method which is a narrowband index+3 bits.
Proposal 9: resource allocation (a narrowband index and 3 bits) of a Rel-13eMTC with respect to a PUSCH in a CE mode B is to be reused with respect to a non-BL UE PUSCH in a CE mode B within 1.4 MHz bandwidth.
The whole contents of the U.S. provisional application 62/454,193 (filed on Feb. 3, 2017) is incorporated in this specification by reference.
The present invention is useful in a mobile communication field.
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/JP2018/002140 | 1/24/2018 | WO | 00 |
| Publishing Document | Publishing Date | Country | Kind |
|---|---|---|---|
| WO2018/143033 | 8/9/2018 | WO | A |
| Number | Name | Date | Kind |
|---|---|---|---|
| 20170347268 | Chen | Nov 2017 | A1 |
| 20180092101 | Xia | Mar 2018 | A1 |
| 20180152924 | Ouchi | May 2018 | A1 |
| 20180219576 | Bhattad | Aug 2018 | A1 |
| 20180309551 | Baldemair | Oct 2018 | A1 |
| 20190028247 | Liu | Jan 2019 | A1 |
| 20190230739 | Ookubo | Jul 2019 | A1 |
| Number | Date | Country |
|---|---|---|
| 2016186044 | Nov 2016 | WO |
| Entry |
|---|
| Nokia et al.; “Frequency Hopping Support for FeMTC”; 3GPP TSG RAN WG1 Meeting #87; R1-1611481; Nov. 14-18, 2016; pp. 1-2; Reno, NV, USA. |
| Number | Date | Country | |
|---|---|---|---|
| 20200008198 A1 | Jan 2020 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62454193 | Feb 2017 | US |
