TWI747853B - Systems and methods for mtc ues with scalable bandwidth support - Google Patents

Abstract

The present disclosure includes systems and methods that enable support of MTC UEs that can benefit from the device complexity and power complexity reductions of 3GPP Release 13 LC UEs but at the same time support higher data rates. An apparatus operates in a single narrowband (NB) mode where the apparatus supports communication over only a single NB. The single NB is included in a plurality of NBs within a system bandwidth (BW). A determination is made to switch from the single NB mode to an aggregated BW mode. The apparatus switches from the single NB mode to the aggregated BW mode. The apparatus supports communication over more than the single NB in the aggregated BW mode. The apparatus communicates with an evolved Node B (eNB) using an aggregated BW that includes the single NB and at least a portion of a second NB of the plurality of NBs.

Description

System and method for machine type communication user equipment (MTC UE) with adjustable bandwidth support

This disclosure relates to low complexity (LC) user equipment (UE) suitable for machine type communication (MTC) or Internet of Things (IoT) applications.

Wireless mobile communication technology uses various standards and protocols to transmit data between base stations and wireless mobile devices. Wireless communication system standards and protocols may include the Third Generation Partnership Project (3GPP) Long Term Evolution (LTE); the industry group is commonly known as the World Interoperability for Microwave Access (WiMAX) Institute of Electrical and Electronics Engineers (IEEE) 802.16 Standard; and the IEEE 802.11 standard commonly referred to as Wi-Fi by the industry group. In the 3GPP radio access network (RAN) in the LTE system, the base station may include an evolved universal terrestrial radio access network (E-UTRAN) node B (usually also denoted as evolved node B, enhanced node B, eNodeB, (Or eNB) and/or the radio network controller (RNC) in E-UTRAN, which communicates with a wireless communication device called user equipment (UE).

The system and method can support MTC UE, which can benefit from 3GPP The device complexity and power complexity of version 13 LC UE are reduced.

LC UEs (for example, 3GPP Release 13 LLC LC UEs) are characterized by their low complexity, low data rate requirements, higher tolerance for latency, higher sensitivity to power consumption, and enhanced coverage operations Support. The LC UE is usually configured to only support a limited bandwidth. For example, the LC UE may support a limited bandwidth of 1.4 MHz in both radio frequency (RF) and base frequency.

100‧‧‧Environment

105‧‧‧UE

110‧‧‧eNB

120‧‧‧Narrowband Access Link

115‧‧‧Huge cell coverage

200‧‧‧Figure

205‧‧‧Frame

210‧‧‧Sub Frame

215‧‧‧hour slot

220‧‧‧OFDM symbol

225‧‧‧Cycle forward

230‧‧‧Physical resource block

235‧‧‧Subcarrier

240‧‧‧Resource component

300‧‧‧Example

305A1-A2‧‧‧NB

305B1-B4‧‧‧NB

305C1-C8‧‧‧NB

305D1-D12‧‧‧NB

400‧‧‧Example

405‧‧‧M-PDCCH

410‧‧‧PDSCH

305F-4-305F-7‧‧‧NB

500‧‧‧Example

600‧‧‧Method

700‧‧‧Method

800‧‧‧Method

900‧‧‧Method

1000‧‧‧Electronic device circuit

1010‧‧‧Transmission circuit

1015‧‧‧Receiving circuit

1020‧‧‧Control circuit

1025‧‧‧antenna element

1100‧‧‧UE device

1105‧‧‧Application circuit

1110‧‧‧Baseband circuit

1115‧‧‧RF circuit

1120‧‧‧FEM circuit

1125‧‧‧antenna

1110A-1110D‧‧‧Baseband processor

1110E‧‧‧CPU

1110F‧‧‧Audio DSP

1110G‧‧‧Memory/Storage

1115A‧‧‧Mixer circuit

1115B‧‧‧Amplifier circuit

1115C‧‧‧Filter circuit

1115D‧‧‧Synthesizer circuit

Figure 1 shows an example of an environment in which this system and method may be implemented.

Figure 2 is a schematic diagram showing the structure of a long-term evolution (LTE) communication frame.

Figure 3 shows an example of how narrowband (NB) might be defined for a given system bandwidth (BW).

Figure 4 shows an example of DL resource allocation and M-PDCCH to PDSCH timing with dynamic indication of PDSCH BW and resources for a UE with adjustable BW support (for example, Cat Mplus UE).

Figure 5 shows the DL resource allocation and the M-PDCCH to PDSCH timing relationship for a UE with adjustable BW support (for example, Cat Mplus UE) for the semi-static RRC configuration of the largest PDSCH BW in which actual PDSCH resources are allocated Instance.

Figure 6 is a flowchart of a method for wireless communication performed by a UE that supports adjustable bandwidth.

Figure 7 is a flowchart of a method for wireless communication by a UE that supports adjustable bandwidth.

Figure 8 is a flow chart of the method of wireless communication performed by the eNB.

Figure 9 is a flowchart of a method for wireless communication by a UE that supports adjustable bandwidth.

FIG. 10 is a block diagram of an electronic device circuit that may be an eNB circuit, a UE circuit, a network node circuit, or some other type of circuit according to various embodiments.

Figure 11 is a block diagram showing exemplary components of a user equipment (UE) or mobile station (MS) device used in an embodiment.

[Content and Implementation of the Invention]

A detailed description of the system and method consistent with the embodiment of the present disclosure is presented below. Although several embodiments have been described, it should be understood that the present disclosure is not limited to any one embodiment, but includes many alternatives, modifications, and equivalents. In addition, although many specific details are set forth in the following description in order to provide a thorough understanding of the embodiments disclosed herein, some embodiments may be practiced without some or all of these details. In addition, for the sake of clarity, certain technical materials known in the related art are not described in detail to avoid unnecessarily obscuring the disclosure.

Wireless mobile communication technology uses various standards and protocols to transmit data between base stations and wireless mobile devices. Wireless communication system standards and agreements may include the Long Term Evolution of the Third Generation Partnership Project (3GPP) (LTE); the Institute of Electrical and Electronics Engineers (IEEE) 802.16 standard commonly known as Worldwide Interoperability for Microwave Access (WiMAX); and the IEEE 802.11 standard commonly known as Wi-Fi by the industrial group. In the 3GPP radio access network (RAN) in the LTE system, the base station may include an evolved universal terrestrial radio access network (E-UTRAN) node B (usually also denoted as evolved node B, enhanced node B, eNodeB, (Or eNB) and/or the radio network controller (RNC) in E-UTRAN, which communicates with a wireless communication device called user equipment (UE).

The system and method can support MTC UEs, which can benefit from the reduced device complexity and power complexity of 3GPP Release 13 LC UEs, but at the same time support higher data rates, such as in the downlink (DL) and uplink (UL) ), or the lower physical layer transmission or reception latency supported by adjustable bandwidth for real-time or near-real-time traffic. Specifically, the system and method support devices that can be nominally similar to 3GPP Release 13 LC MTC devices, but can also support larger bandwidth reception or transmission to receive or transmit using a bandwidth wider than 1.4 megahertz (MHz) Larger transmission block size (TBS) (ie, six long-term evolution (LTE) physical resource blocks (PRB)), which depends on the data rate or latency requirements from the application layer.

LC UEs (for example, 3GPP Release 13 LLC LC UEs) are characterized by their low complexity, low data rate requirements, higher tolerance for latency, higher sensitivity to power consumption, and enhanced coverage operations Support. The LC UE is usually configured to only support a limited bandwidth. For example, LC UE may support 1.4 in both radio frequency (RF) and baseband Limited bandwidth of MHz. As used herein, an LC UE that supports a limited bandwidth of 1.4 MHz in both the RF and the base frequency is identified as a "Cat M1" (Cat M1) UE.

The peak data rate supported by LC UEs (for example, Cat M1 UE) is limited by the maximum transmission block size (TBS) of 1000 bits and the maximum bandwidth limit of 6 PRBs. In addition, the use of cross-subframe scheduling (where the scheduling starts in the second effective LC/EC downlink (DL) subframe after the last subframe of the MTC physical downlink control channel (M-PDCCH)) The physical downlink shared channel (PDSCH) means that the UE can support a maximum data rate of approximately 800 kilobits per second (kbps) for full-duplex frequency division duplex (FD-FDD), and for half-duplex FDD (HD-FDD) UE can support a maximum data rate of about 300kbps.

This restriction on peak data rates can limit the applicability of these LC UEs to various IoT/MTC applications. Therefore, it is hoped to support MTC/IoT devices that can benefit from the low power consumption characteristics of 3GPP Release 13 LC UEs (this is facilitated by narrowband support and does not need to support broadband transmission reception, such as LTE physical downlink control channel (PDCCH), But at the same time, it can support higher DL and uplink (UL) data rates for more types of applications that may require higher data rates, at the expense of a slight increase in device complexity. Such feature enhancements can help The scope of MTC/IoT extends to certain wearable applications that require higher data rates.

Disclose technologies, devices, and methods for supporting MTC UEs, which can benefit from the reduction in device complexity and power complexity of 3GPP Release 13 LC UEs, and at the same time through adjustable bandwidth support (for example, for The bandwidth of 10MHz is ~10Mbps, and the bandwidth of 20MHz is ~20Mbps), which supports higher data rate or lower latency performance on DL and UL. Specifically, the disclosure is used to support operations that are nominally similar to 3GPP Release 13 LC MTC devices but can also support larger bandwidth reception or transmission to receive or transmit using more than 1.4MHz (ie, six LTE physical resource blocks (PRB) )) The details of devices with wider bandwidth and larger transmission block size (TBS) depend on the data rate requirements from the application layer. As used herein, these UEs are called Category Mplus (Cat Mplus) UEs. These UEs may also be referred to as Cat M2 devices or High Performance Enhanced Machine Type Communication (HeMTC) UEs. However, it should be noted that the use of UE categories in this work does not imply the introduction or not of any new UE categories. For example, instead of defining a new UE category Cat Mplus, a Cat M1 UE with support for adjustable BW for PDSCH and PUSCH can be identified through capability signaling.

Turning now to the drawings, Figure 1 shows an example of an environment 100 in which the system and method may be implemented. The environment 100 includes a part of a radio access network (RAN) system, which includes a cellular air interface (e.g., LTE/LTE advanced access link) provided between the eNB 110 and the UE 105 (ie, in a narrow frequency memory Take link 120). The UE 105 is located within the giant cell coverage 115 provided by the eNB 110.

The eNB 110 may designate a set of non-overlapping DL and/or UL narrowband (NB) for the LTE system BW. In some cases, the eNB 110 may designate a set of non-overlapping DL and/or UL NBs for each LTE system BW. Each NB may be six PRBs in size. UE 105 and eNB 110. Communication on the narrowband access link 120 may generally limit the maximum bandwidth of an NB (for example, six PRBs). Therefore, the UE 105 can benefit from the reduction in device complexity and power complexity of 3GPP Release 13 LC UEs. However, the UE 105 may also be configured for adjustable bandwidth support. In other words, the UE 105 may use more than a single NB (for example, more than six PRBs) to selectively support communication with the eNB 110. Therefore, the UE 105 can benefit from the reduced device complexity and power complexity of the 3GPP Release 13 LC UE, while still being able to support higher data rates as needed.

FIG. 2 is a schematic diagram 200 showing the structure of a long-term evolution (LTE) communication frame 205. The frame 205 has a duration of 10 milliseconds (ms). The frame 205 includes ten sub-frames 210, each having a duration of 1 ms. Each sub-frame 210 includes two time slots 215, each having a duration of 0.5 ms. Therefore, the frame 205 includes 20 time slots 215.

Each time slot 215 includes six or seven Orthogonal Frequency Division Multiplexing (OFDM) symbols 220. The number of OFDM symbols 220 in each time slot 215 is based on the size of the cyclic prefix (CP) 225. For example, the number 220 of OFDM symbols in the time slot 215 is 7 in the normal mode CP and 6 in the extended mode CP.

The smallest allocable unit for transmission is a resource block 230 (ie, a physical resource block (PRB) 230). The transmission is scheduled by PRB 230. In the duration of one time slot 215 (0.5 ms), the PRB 230 is composed of 12 consecutive sub-carriers 235 or 180 kHz. The resource element 240, which is the smallest defined unit, is composed of one OFDM subcarrier during one OFDM symbol interval. In the case of the normal mode CP, each PRB 230 consists of 12×7=84 resource elements 240. In the case of the extended mode CP, each PRB 230 is composed of 72 resource elements 240.

Figure 3 shows an example 300 of how narrowband (NB) might be defined for a given system bandwidth (BW). In the case of 3GPP Release 13 LC UE, each NB 305 has a defined size of six PRBs 230. Based on this defined size of NB 305, a set of non-overlapping DL and/or UL NB 305 is designated for each LTE system BW.

The 3MHz system BW includes 15 available PRBs 230. Therefore, a set of two non-overlapping NBs 305 A1-A2 constituting 12 PRBs 230 can be designated for the 3MHz system BW. The three remaining PRBs 230 may be divided within the 3MHz system BW, where two of the remaining PRBs 230 are evenly divided at both ends of the 3MHz system BW and the additional odd PRB 230 is located at the center of the 3MHz system BW.

The 5MHz system BW includes 25 available PRB 230. Therefore, a set of four non-overlapping NBs 305B1-B4 constituting 24 PRBs 230 can be designated for the 5MHz system BW. The additional odd remaining PRB 230 may be located in the center of the 5MHz system BW.

The 10MHz system BW includes 50 available PRBs 230. Therefore, a set of eight non-overlapping NBs 305 C1-C8 that constitute 48 PRBs 230 can be designated for the 10MHz system BW. The two remaining PRBs 230 can be evenly divided at both ends of the 10MHz system BW.

The 15 MHz system BW includes 75 available PRB 230. Therefore, a set of twelve non-overlapping NBs 305D1-D12 that constitute 72 PRBs 230 can be designated for the 15MHz system BW. Three remaining The PRB 230 may be divided within the 15 MHz system BW, where two of the remaining PRB 230 are evenly divided at both ends of the 15 MHz system BW and the additional odd PRB 230 is located at the center of the 15 MHz system BW.

The 20MHz system BW includes 100 available PRBs 230. Therefore, a set of sixteen non-overlapping NBs 305E1-E16 constituting 96 PRBs 230 can be designated for a 20MHz system BW. The four remaining PRBs 230 can be evenly divided at both ends of the 20MHz system BW.

The index of NB 305 may follow the index order of PRB 230. As shown in Figure 3, the total number of DL and/or UL NB in a specific system BW is respectively given by N _NB ^DL = floor(N _RB ^DL /6) and N _NB ^UL = floor(N _RB ^UL /6), The remaining PRBs are evenly divided at both ends of the system bandwidth, and additional odd-numbered PRBs (such as 3, 5, and 15 MHz) for the system BW are located at the center of the system BW (where N _NB ^DL = the number of DL NB and N _NB ^UL = the number of UL NB).

Although not shown, it should be noted that the 1.4 MHz system BW includes 6 available PRBs 230 (for example, a single NB 305). As used herein, NB may be referred to as 1.4MHz NB. 3GPP Release 13 LC UE may only support 1.4MHz bandwidth at RF and base frequency. Therefore, the 3GPP Release 13 LC UE supports reception/transmission on a single NB 305 (for example, six PRB 230, 1.4MHz bandwidth), and may be retuned from one NB 305 in the larger system BW to another NB 305. (For example, 3, 5, 10, 15, or 20 MHz).

As mentioned above, Cat Mplus UE (for example, UE 105) is conceived as an enhancement of Cat M1 UE (ie, 3GPP Release 13 LC UE) Version, which can support much higher data rates and/or support more relaxed latency performance on DL and UL compared to typically expected for 3GPP Release 13 LC UEs, such as voice over LTE (VoLTE) or video traffic It is required to achieve most of the benefits from 3GPP Release 13 LC UE's complexity and power consumption reduction and enhanced coverage features at the same time. Cat Mplus UE can achieve higher data rates by supporting wider bandwidth in RF and baseband. Since the support of a wider bandwidth brings additional power consumption, it is possible to enable or disable reception/transmission on a bandwidth wider than 1.4MHz according to data rate requirements (for example, from the application layer).

Therefore, unlike LTE UE category 0 and above, Cat Mplus UE does not need to support all LTE system bandwidth values, and does not expect to receive any LTE system BW such as PDCCH, Entity Control Format Indicator Channel (PCFICH), and entity Hybrid automatic repeat request (HARQ) indicator channel (PHICH) traditional broadband transmission. In contrast, under normal conditions (ie, when there is no high data rate or more stringent waiting time requirements), Cat Mplus UE behaves similarly to 3GPP Release 13 LC UE. However, Cat Mplus UE can adapt to support reception/transmission on a BW wider than 1.4 MHz by aggregating one or more PRBs 230 on multiple 1.4 MHz NB 305 in the LTE system BW according to the data rate requirement.

For example, when in radio resource control (RRC) idle mode, Cat Mplus UE behaves like 3GPP Release 13 LC UE, which can receive or transmit on six PRBs 230 that do not exceed the bandwidth, and has a larger system BW The ability to retune from one NB 305 to another NB 305. This This operation mode is referred to herein as "single NB mode".

The single narrowband mode enables the greatest benefit of the reduced power consumption features defined for 3GPP Release 13 LC UEs. For example, the UE does not monitor the entire system BW for PDCCH monitoring and so on.

In order to receive broadcast data, Cat Mplus UE behaves similarly to 3GPP Release 13 LC UE. It can receive or transmit on six PRBs 230 not exceeding the bandwidth, and has the ability to retune from one NB 305 to another in a larger system. The capability of NB 305 is BW. Therefore, in order to receive system information (SI), call, and RAR messages, Cat Mplus UE only supports a maximum single 1.4MHz BW and follows the behavior defined for 3GPP Release 13 LC UE.

Similar to the case of RRC IDLE mode, for RRC CONNECTED mode and/or RRC CONNECTED mode discontinuous reception (C-DRX), Cat Mplus UE behaves similarly to 3GPP Release 13 LC UE, which can operate in six PRBs that do not exceed the bandwidth. Receive or transmit on 230, with the ability to retune from one NB 305 to another NB 305 within a larger system BW. Or, during certain periods of the C-DRX cycle, depending on the need for high data rates for dynamic alignment of traffic or SPS traffic (for example, Voice over LTE (VoLTE)), Cat Mplus UE may support "aggregated BW Mode" operation. Note that this may also be referred to as "High Performance Mode" or "Higher Data Rate Mode".

In one embodiment, operation in the aggregate BW mode is supported in certain subframes during C-DRX. For example, Cat Mplus UE will support aggregate BW during the subframe period in the "onDuration" of C-DRX Mode, and fall back to single NB mode after the timer (e.g., drxInactivity Timer) expires.

In another embodiment, the Cat Mplus UE operates in a single NB mode until it receives an M-PDCCH instructing to dynamically switch to the aggregate BW mode. Upon receiving the M-PDCCH instructing to dynamically switch to the aggregated BW mode, the Cat Mplus UE switches to the aggregated BW mode. Subsequently, when operating in aggregate BW mode, Cat Mplus UE monitors Downlink Control Information (DCI), making it possible to schedule with frequency resources spanning more than a single 6-PRB NB 305. In one example, the Cat Mplus UE falls back to the single NB mode after a certain newly defined timer expires or after an existing timer (for example, onDuration/drxInactivityTimer) expires.

When there is no high data rate requirement for DL or UL for unicast reception or transmission, Cat Mplus UE follows the 3GPP Release 13 LC UE behavior limited to the narrowband support of 1.4MHz bandwidth, which may be from the larger system BW One NB 305 is retuned to another NB 305 (for example, 3, 5, 10, 15, or 20 MHz).

Selective switching to the aggregate BW mode enables the greatest benefit of power consumption reduction features defined for 3GPP Release 13 LC UEs, where Cat Mplus UE does not need to monitor the entire system BW for PDCCH monitoring, etc. Cat Mplus UE normally operates in single NB mode. However, when high data rate requirements for unicast reception or transmission are triggered for DL or UL, respectively, Cat Mplus UE supports reception/reception on frequency resources spanning a single 1.4MHz NB 305 with six PRBs 230, respectively. Transmission (respectively) (for example, operating in aggregate BW mode), affected by the maximum supported BW.

Aggregated BW mode is realized by aggregating PRB 230 belonging to one or more 1.4MHz NB 305. These NBs may or may not be adjacent to each other, but make these PRBs 230 appear in the frequency domain within the maximum supported BW for BW aggregation middle. Note that the maximum supported BW for BW aggregation is separated from the maximum LTE system BW (for example, 20 MHz) or the deployed LTE system BW.

In some cases, the maximum supported BW may be defined according to absolute BW (for example, 7.5MHz, 10MHz, 15MHz, etc.). In other cases, the maximum supported BW may be defined according to the number of consecutive NBs (for example, the maximum supported BW is given by the frequency spanned by 4, 6, 8, etc. consecutive NBs 305, each 1.4MHz (six PRB) wide ). In other cases, the maximum supported BW may be defined according to the number of consecutive PRBs 230 (for example, the maximum supported BW is given by the frequency spanned by "N" consecutive PRBs 230, where N=25, 40, 50, etc.).

Figure 4 shows an example 400 of DL resource allocation and M-PDCCH to PDSCH timing with dynamic indication of PDSCH BW and resources for a UE with adjustable BW support (for example, Cat Mplus UE). The M-PDCCH 405 is received in the NB 305F-6 used by the UE in single NB mode. In one example, the single NB 305F-6 used by the UE is the sixth NB 305F-6 of a group NB 305 designated by the eNB for the system BW. Since the system BW includes at least six NBs, it is assumed that the system BW is 10 MHz or more.

The M-PDCCH 405 includes dynamic intra-frequency signaling (for example, DCI) indicating the amount and location of aggregate BW allocated to the UE for the subsequent PDSCH 410. As in the case of cross-subframe scheduling, the scheduled PDSCH starts in the second valid LC/EC downlink (DL) subframe after the last subframe of the M-PDCCH. This timing enables the UE to decode the M-PDCCH before receiving the scheduled PDSCH 410 (e.g., in the M-PDCCH decoding time). The UE may decide to switch from the single NB mode to the aggregate BW mode based on the information (for example, DCI) received in the M-PDCCH 405. While operating in the aggregated BW mode, the UE may use an aggregate of 20 PRBs 230 including six PRBs 230 from each NB 305F-4, 305F-5, and 305F-6 and two PRBs 230f NB 305F-7 The BW receives the DL transmission via the PDSCH 410. Therefore, as shown in Figure 4, BW may be allocated by PRB 230 (for example, only a part of one or more NB 230 is allocated). The maximum PDSCH BW may be configured through RRC messages.

The 3GPP Release 13 LC UE does not expect to support simultaneous reception of multiple transport blocks (TB), which may be unicast, broadcast, or a mixture of the two. For the Cat Mplus UE, when operating in the aggregate BW mode, it is possible to map the two TBs to the PRB 230 that falls within the maximum supported BW by the Cat Mplus UE in the aggregate BW mode. However, in order not to increase device complexity and buffer management, in one embodiment, Cat Mplus UE is not expected to support simultaneous reception of multiple TBs, even when operating in aggregate BW mode.

Or, in another embodiment, Cat Mplus UE does not expect It is expected to support the reception of multiple broadcast TBs or a mixture of broadcast TB and unicast TB, but it is expected to support up to two unicast PDSCH TBs, which may be transmitted using PRB 230 in the maximum supported BW when operating in aggregate BW mode . In this case, when Cat Mplus UE is scheduled to receive multiple unicast PDSCH TBs, it generates HARQ-ACK feedback corresponding to each PDSCH TB transmitted using PUCCH format 1b, where PUCCH resources are derived and mapped To physical resources (including support for repeated transmission and frequency hopping) can follow the behavior defined in CE mode A for 3GPP Release 13 LC MTC UE.

The scheduling of PDSCH with multiple unicast TBs is similar to the traditional LTE DCI format 2/2A/2B/2C/2D, indicating modulation and coding architecture (MCS) and redundancy version (RV) for each TB. Index, and New Data Indicator (NDI) bits. If a new DCI format is introduced for DL scheduling in the aggregate BW mode, this option may be the most suitable (described below as option C). However, the change of the DCI design to support the scheduling of up to two transmission blocks can also be combined with the DCI design of the Option A category. In an embodiment, the frequency domain resource allocation given by the existing DCI format 6-1A corresponds to the resource for the first TB, and the second TB is mapped to the additional indicated NB 305. This method may be more suitable for scheduling up to two TBs of PDSCH after option A of scheduling the PDSCH in the aggregate BW mode.

For UL transmission, even when operating in aggregate BW mode, Cat Mplus UE only uses one or more consecutive PRBs 230 to transmit a single PUSCH TB, so that for the latter case, the PRB spans more than a single PUSCH TB. 1.4MHz BW. In addition, similar to 3GPP Release 13 LC UE, Cat Mplus UE does not support simultaneous transmission of PUSCH and PUCCH.

Currently, for broadcast and unicast DL and unicast UL, 3GPP Release 13 LC UE supports a maximum transmission block size (TBS) of 1000 bits. However, in order to fully realize the possible high data rate by supporting adjustable BW, for Cat Mplus UE, at least for DL and UL unicast reception/transmission, the TBS restriction may be removed.

Regarding the modulation order, in order to achieve a compromise between the achievable maximum data rate and the maximum BW support, in one embodiment, higher-level modulation may be supported, such as 64 quadrature amplitude modulation (QAM) for DL And 16 QAM for UL.

The number of Hybrid ARQ (HARQ) procedures for Cat Mplus UE may be the same as that defined for 3GPP Release 13 LC UE (ie, 8 HARQ procedures can be assumed for DL and UL in FDD system to define soft buffer requirements). For Cat Mplus UE, for DL and UL in the FDD system, the number of HARQ procedures may be fixed at 8, regardless of coverage conditions (ie, regardless of coverage extension (CE) mode A or CE mode B), while in TDD systems The number of HARQ procedures used for DL and UL can be given in Table 1 below, regardless of coverage conditions.

Note that for HD-FDD operation, due to cross-subframe scheduling and switching subframe considerations, only up to 3 HARQ procedures may be used to reduce the last subframe of M-PDCCH and the first subframe of scheduled PDSCH Timing between boxes.

On the other hand, for TDD systems, for DL and UL, the number of HARQ procedures will be higher than 8 procedures, depending on the TDD DL-UL configuration defined for 3GPP Release 13 LC UE. However, again, a maximum of 8 HARQ procedures similar to the LTE specification will still be assumed to determine the soft buffer requirement.

For reference, the number of HARQ procedures supported for 3GPP Release 13 LC UEs is provided. For FDD, if the UE operates in CE mode A, the maximum number of DL and UL HARQ procedures is the same as the Cat-0 UE in 3GPP Release 12. For TDD, if the UE operates in CE mode A, the maximum number of UL HARQ procedures is the same as that of Cat-0 UE in 3GPP Release 12, and the maximum number of DL HARQ procedures is shown in Table 1. For HD-FDD, FD-FDD, and TDD, if the UE With medium to large coverage enhancement operation, it is expected that the UE supports no more than N=2 DL HARQ procedures to receive unicast PDSCH, and it is expected that the UE supports no more than M=2 UL HARQ procedures to transmit PUSCH.

The adjustable BW feature can be aided by Cat Mplus UE that supports any of full-duplex FDD (FD-FDD), half-duplex FDD (HD-FDD), and TDD systems. In addition, these UEs can be assigned other enhancements that can help increase the maximum data rate that can be achieved. For example, for HD-FDD UEs, HARQ-ACK bundling can be supported in sequence, whereby the UE reports the bundling of multiple PDSCH transmission blocks (TB) corresponding to different DL subframes in a single PUCCH transmission HARQ-ACK feedback to maximize the scheduling opportunity within the round trip time (RTT) by avoiding the excessive number of guard subframes required for DL to UL or UL to DL retuning.

For 3GPP Release 13 LC UE, two coverage enhancement (CE) modes are defined: CE mode A and B, where CE mode A corresponds to UEs that do not use or use a small amount of various physical channels for transmission/reception. The CE mode B corresponds to the UE behavior corresponding to the repetition of various physical channels used for transmission/reception in use to a large amount. According to its coverage conditions, 3GPP Release 13 LC UEs can be configured via dedicated RRC signaling with one of the CE modes.

Devices with applications that require higher data rates can be expected to generally require only a limited amount of coverage enhancement, and rarely in deep coverage holes. Therefore, in an embodiment, the operation in the aggregate BW mode may be limited to CE mode A only. Therefore, in CE mode B, the UE may always operate in a single NB mode, and may not be expected to be configured for aggregate BW mode Mode.

In an embodiment, multiple types of UEs may be defined according to the maximum data rate and/or maximum BW supported by the UE. In another embodiment, support for different values of the maximum data rate and/or the maximum BW may be indicated to the network via capability signaling. This capability indication may be defined as being transmitted as part of the RRCConnectionRequest message (for example, this may be indicated in the Message3 transmission during the random access procedure). Or, in response to a capability indication request from the eNB, such information may be indicated to the network as an RRC message.

As described above, the UE (e.g., Cat Mplus UE) only operates in the aggregate BW mode when a higher data rate is required. Therefore, a higher data rate requires the use of reception/transmission on BWs greater than six PRBs 230. In an embodiment, the UE may switch between the single NB mode and the aggregate BW mode based on the configuration received from the eNB. Once triggered by the eNB or based on a request from the UE, the eNB may signal the switch between the two modes. In some cases, mode switching is separately configured for DL and UL.

Figure 5 shows the DL resource allocation and the M-PDCCH to PDSCH timing relationship for a UE with adjustable BW support (for example, Cat Mplus UE) for the semi-static RRC configuration of the largest PDSCH BW in which actual PDSCH resources are allocated的Instance 500. The M-PDCCH 405 is received in the NB 305F-6 used by the UE in single NB mode. In one example, the single NB 305F-6 used by the UE is the sixth NB 305F-6 of a group NB 305 designated by the eNB for the system BW. Because of The system BW includes at least six NBs, so it is assumed that the system BW is 10 MHz or greater.

For UEs with adjustable BW support (for example, Cat Mplus UE), when the eNodeB determines the need to support larger TBS and the When a larger number of PRBs are scheduled for PDSCH or PUSCH, the eNB may configure the UE in the aggregate BW mode. Once in the aggregate BW mode, the UE may switch back to the single NB mode depending on the scheduling decision or termination of the need for higher data rates. It may be signaled via dedicated RRC or media access control (MAC) control element (CE), or even indicated to/from the configuration of the aggregate BW mode via DCI.

For the option based on RRC or MAC CE configuration in aggregate BW mode, indicate the maximum aggregate BW that may schedule PDSCH in the RRC or MAC CE message. In this case, once the UE is configured with aggregate BW configuration, it already knows It is possible to schedule the bandwidth and frequency resources of the PDSCH. Therefore, the timing between M-PDCCH 405 and scheduled PDSCH 410 (the first subframe of scheduled PDSCH 410 defined for 3GPP Release 13 LC UE) may be from the first subframe after the last M-PDCCH 405 subframe. The second effective subframe is reduced to the first effective subframe after the last M-PDCCH 405 subframe (as shown in Figure 5). This is because, contrary to the case where the UE obtains the narrowband information for receiving PDSCH from the scheduled DCI (for the dynamic cross-narrowband scheduling) containing DL allocation, in this case, due to the half of the configuration Static characteristics (for dynamic scheduling), the UE does not need to be able to decode the M-PDCCH to know that it should monitor Receive the frequency resource or narrowband of scheduled PDSCH. Therefore, the UE can buffer the M-PDCCH in the subframe "n", and can retune to a different narrowband set ( Across the aggregation BW).

The UE may decide to switch from the single NB mode to the aggregate BW mode based on the RRC or MAC CE message. When operating in aggregate BW mode, the UE may use six PRBs 230 from each of NB 305F-4, 305F-5, and 305F-6, and 20 PRBs 230 from two PRBs 230f NB 305F-7 The aggregate BW receives DL transmission via PDSCH 410. Therefore, as shown in Figure 5, BW may be allocated by PRB 230 (for example, only a part of one or more NB 230 is allocated).

For the DCI-based signaling option used to configure to/from the aggregated BW mode, the mechanism can be similar to the semi-static scheduling (SPS) start and release instructions, where (for example, by defining a new adjustable BW-RNTI (SB -RNTI)) Use DL allocation or UL grant DCI together with scrambling of Cyclic Redundancy Check (CRC) with New Radio Network Temporary Identifier (RNTI) (ie, in this case, DCI can reuse the DCI format separately 6-1A or format 6-0A). If the DCI format 6-1A or 6-0A is reused, in one embodiment, the frequency hopping (FH) flag and resource allocation field can be reinterpreted to indicate to/from the configuration of the aggregate BW mode. In another embodiment, DCI is not only used to configure mode switching of the UE, but also used to provide actual DL allocation or UL grant to the UE. In this case, the FH flag may be used to switch the mode between the aggregate BW mode and the single NB mode; the application of FH is disabled, and when the CRC of the DCI is scrambled with SB-RNTI, the UE will The FH flag is interpreted as a toggle bit.

Alternatively, the configuration of the aggregate BW mode can be performed via dedicated RRC messages or via MAC CE messages, and the configuration from aggregate BW mode to single NB mode can be indicated via MAC CE messages or even DCI. Generally, the configuration and de-configuration can be sent to the UE via different sending paths.

Additionally or alternatively, the switching between the two modes may be configured by the eNB when receiving a request from the UE. Specifically, according to application requirements, the UE may send a request to configure it in the aggregate BW mode via obvious signaling or via a request for a larger BW or a higher data rate. Similarly, the UE may also send a request to return to single NB mode to optimize power consumption when the data rate requirement decreases. The request message from the UE can be defined as an RRC message or a MAC control element (CE) message, which has the option of instructing to switch to/from the aggregate BW mode only for DL, or only for UL, or both.

For UL, the switching between the two modes can be implicitly triggered based on the buffer status report (BSR) indication (ie, there is no explicit request from the UE). Therefore, in an embodiment, when the buffer size reported in the BSR or in multiple consecutive BSRs exceeds a certain threshold, the UE with adjustable BW support may be expected to be configured by the eNB to operate in the aggregate BW mode, and Switch back to single NB mode when the aggregate buffer size is below a certain threshold.

In an embodiment, the selection of the threshold can be implemented by the eNB, so it is transparent to the UE. However, in another embodiment, The exact rules for mode switching are defined in the specification, and the eNB can signal via public or dedicated RRC to indicate the threshold for mode switching in each direction. Therefore, the UE can autonomously switch between UL's aggregate BW mode and single NB mode according to the UL buffer status, and the eNB will also be able to know the mode switch based on the reported buffer size, thereby avoiding separate configuration messages from the eNB .

In an embodiment, for DL and UL, the eNB may also reconfigure the UE from an aggregate BW mode with a certain total BW to an aggregate BW mode with different total BW values, so as to achieve finer adjustment of the BW supported by the UE. (At least at the base frequency) to further optimize UE power consumption. For example, the total BW to be supported when in the aggregate BW mode can be indicated according to the number of 1.4MHz NB 305 or according to the number of PRB 230, and the number of NB 305 or PRB 230 can be indicated according to changes in the application QoS requirements, based on According to the scheduling decision and resource availability at the eNB (for example, affected by the maximum aggregate BW supported by the UE) or decrease. For example, if the eNB determines that it cannot allocate a UE with resources spanning more than a certain number of consecutive NBs for DL or UL, it may reconfigure the UE to a smaller aggregate BW value in order to help optimize device power consumption.

As mentioned above, it is assumed that the support of the aggregate BW mode may be limited to CE mode A. However, if the aggregate BW mode is supported for CE mode B, the solution described herein can also be applied to the corresponding DCI format (ie, based on DCI formats 6-0B and 6-1B).

For 3GPP Release 13 LC MTC UE, DCI format 6- 0A and 6-1A are used for UL scheduling (UL approval) and DL scheduling (DL allocation), respectively. For frequency domain resource allocation using DCI formats 6-0A and 6-1A, it is possible to support cross-narrowband (across-NB) scheduling by indicating the index of NB 305 and the PRB 230 allocated within NB 305, respectively. However, the existing mechanism only supports scheduling that spans no more than a single six PRB NB 305 resources.

As used herein, N _NB ^ABM_XL is defined as the maximum number of NBs supported by NB aggregation in DL or UL (here, XL=DL or UL). The value of N _NB ^ABM_XL may be fixed and specified as a function of the system BW, or may be indicated via MTC SIB (for example, the system information block for 3GPP Release 13 LC UE).

As a specific example of the first option above, N _NB ^ABM_XL = floor(N _RB ^XL /6) or N _NB ^ABM_XL = min{floor(N _RB ^XL /6), N _NB ^ABM_XL_UE }, where N _NB ^ABM_XL_UE is supported by UE The maximum number of consecutive NB 305. (i) When in aggregate BW mode in DL or UL (ie, N _NB ^ABM_XL_UE is the same for all UEs), all UEs that support aggregate BW mode support BW across N _NB ^ABM_XL continuous narrowband, or (ii) different UEs may In the aggregate BW mode, different maximum BWs are supported, and in this case, if N _NB ^ABM_XL is defined as N _NB ^ABM_XL =min{floor(N _RB ^XL /6), N _NB ^ABM_XL_UE }, then N _NB ^ABM_XL will be Interpreted as UE-specific parameters.

Although six PRB NB 305 are used to indicate the maximum BW in the above two paragraphs, it is also possible _{to indicate BW according to PRB 230 (ie, N RB} ^ABM_XL ), and the number of NB 305 can be calculated as N _NB ^ABM_XL = floor (N _RB ^ABM_XL /6) or N _NB ^ABM_XL =ceil(N _RB ^ABM_XL /6). Note: N _RB ^ABM_XL can also be defined as only a multiple of ρ, where ρ consecutive PRBs 230 are used to define the narrow frequency, where ρ=6 for 3GPP Release 13 LC UE.

Note that for all the signaling mechanisms described below, the NB 305 indicated by the most significant bit (MSB) indicated by _{the ceil(log2(floor(N RB} ^{XL /6))) field allocated by the resource block indicates additional} NB 305, if the indicated index for additional NB 305 falls _{outside the range given by [max(0, NB 0} -N _NB ^ABM_XL +1)], the UE shall consider that the DCI has inconsistent information (and Therefore, it should be discarded), where NB ₀ corresponds to the "reference NB" indicated by the ceil (log2 (floor(N _RB ^XL /6))) MSB of the resource block allocation field.

In an embodiment, the NB 305 monitored for the M-PDCCH is always included in the set _{of N NB} ^{ABM_DL NB 305 for receiving PDSCH.} In this case, the UE can always monitor the M-PDCCH allocation regardless of the allocated PDSCH BW. Therefore, unlike the 3GPP Release 13 LC UE, the scheduled PDSCH NB 305 does not include/compliance monitoring for M-PDCCH -In the case of NB 305 of PDCCH, UE does not apply prioritization to receive PDSCH. Alternatively, in another embodiment, this restriction is not applied to the NB 305 that may be used for PDSCH scheduling. In this case, if _{the set of N NB} ^ABM_DL NB used to receive PDSCH does not include NB 305 used for M-PDCCH monitoring in subframes, the UE prioritizes the scheduled one when monitoring M-PDCCH reception PDSCH reception.

Then describe the provision of support for DL and UL scheduling in order to distinguish Various embodiments of resources that span six PRB NB 305s. For convenience, these solutions are classified into three types of options based on how to send new scheduling information to the UE regarding the introduction of DCI sizes, new fields, or new DCI formats.

Option A introduces new resource allocation fields in the existing DCI formats 6-0A and 6-1A into the possible new DCI sizes. In one embodiment, a new resource allocation field is introduced into DCI formats 6-0A, 6-1A, and the UE will need to monitor DCI with a new size corresponding to the additional field when the UE is configured in aggregate BW mode Format 6-0A or 6-1A, and otherwise assume that the DCI format size corresponds to the situation where there is no new field. Therefore, the new field is located at a fixed position in the DCI (for example, as the first or last field in the DCI). In addition, in order to avoid increasing DCI blind decoding efforts, when the addition of new fields may cause the size difference between DL and UL DCI formats, padding bits may be added to DL and UL DCI formats 6-1A and 6- 0A.

The new field may indicate the most effective ceil(log2(floor(N _RB ^XL /6))) (XL=DL and UL for DCI 6-1A and 6-0A respectively) in addition to the fields allocated by the existing resource block One or more NB 305 indexes other than the NB 305 indicated by the bit (MSB). Next, we will describe further sending options in detail.

An option is used when a single additional NB 305 needs to be indicated and the aggregated NB 305 may not be frequency continuous. In one embodiment, the length of the new field is ceil(log2(floor(N _RB ^XL /6))), and indicates that in addition to the ceil(log2(floor (N _RB ^XL /6) )) An NB 305 other than the NB 305 indicated by the MSB. This kind of resource allocation indication can provide the greatest flexibility in allocating any two NBs 305 to the UE within the maximum supported BW _{for NB aggregation (N NB} ^{ABM_XL ), and is beneficial for DL scheduling flexibility.}

Another option is for when multiple additional NBs need to be indicated and the aggregated NB 305 may not be continuous in frequency. In one embodiment, a new _{bitmap of N NB} ^ABM_XL bit length may be used to indicate the allocated NB 305 to obtain maximum flexibility. In this case, it is possible to ignore _{the NB 305 indicated by the ceil (log2 (floor(N RB} ^XL /6))) MSB of the resource block allocation field in the DCI, and only use the new bitmap. Alternatively, the length of the resource block allocation field can be adjusted to (N _NB ^ABM_XL +5) bits, so that now N _NB ^ABM_XL bits indicate the NB allocation bitmap, and the remaining 5 bits are used for Indicates the location of PRB 230 within NB 305. As another option, the length of the resource block allocation field can be adjusted to N _NB ^ABM_XL bits to indicate the allocated NB 305, and it is assumed that all PRBs 230 in the designated NB 305 are allocated.

Another option is for when a single NB 305 or multiple additional NBs 305 need to be indicated and where the aggregated NB 305 is frequency continuous. In general, as described above, resource allocation options are available for DL and UL. Alternatively, for UL resource allocation, considering single carrier constraints, additional one or more NBs 305 can make the entire allocation span a set of continuous frequency resources. Therefore, the resource allocation indication mechanism can be adapted accordingly. In addition, the following options for UL scheduling may also be applied to DL at the expense of not being able to schedule any discontinuous NB 305 for DL scheduling flexibility. schedule.

N_NB ^ABM_XL-1)的長度ceil(log2(NNBABM_XL))之新欄位的第一(最低)或最後(最高)NB 305。 Assuming that only one additional NB 305 is indicated at most, a single bit field can indicate that the additional NB is relative to the ceil(log2(floor(N _RB ^XL /6)) MSB of the resource block allocation field using DCI 6-0A. Is the allocated NB 305 the previous or subsequent NB 305. As an alternative, the existing ceil(log2(floor(N _RB ^XL /6)) MSBs in the resource block allocation field of DCI 6-0A can be interpreted as having an indication A certain number of continuous frequencies after or before "Reference NB" 305 NB 305 (

N _NB ^ABM_XL -1) The first (lowest) or last (highest) NB 305 of the new column of length ceil (log2(NNBABM_XL)).

In some options, the PRB 230 within each NB 305 is indicated. In one embodiment, the PRB 230 indicated by 5 bits of the resource block allocation field of the DCI format 6-0A/6-1A is allocated in all allocated NBs 305. In another embodiment, it is assumed that all PRBs 230 in each indicated NB 305 are to be allocated. Therefore, for the latter option, the last 5 bits in the resource block allocation field in DCI can also be used to partially convey information about the NB 305 schedule by co-coding with the new field.

In one embodiment, when the UE is scheduled to use the PDSCH or PUSCH in the aggregate BW mode, the frequency hopping (FH) application is limited to the M-PDCCH. In this case, the FH flag in DCI can be fixed to indicate that FH is disabled for scheduling UEs in aggregate BW mode, or the FH flag can be used to allocate new or existing resource blocks The fields are jointly coded to partially convey information about the NB 305 schedule. In another embodiment, when FH is enabled, the same FH mode (that is, in the sub-frame The number and frequency of the frequency hopping offset (frequency hopping granularity) is applied to all allocated NB 305.

N_NB ^ABM_XL，則可使用此方法。FH的應用可遵循與上述選項A所述之類似的解決方案。 Option B reinterprets the existing resource allocation fields in the existing DCI formats 6-0A and 6-1A without changing the DCI size. In one option, the PRB indicator bit in the resource block allocation field is reinterpreted. In one embodiment, it is assumed that all six PRBs 230 in the allocated NB 305 are allocated, and the last 5 bits of the resource block allocation field in the DCI format 6-0A/6-1A are used to transmit one Attach NB 305. In another embodiment, it is assumed that all six PRBs 230 in the allocated NB 305 are allocated, and _{a resource block allocation of (ceil(log2(floor(N RB} ^XL /6)))+5) bits is used The field uses the N _NB ^ABM_XL bit-length bitmap to transmit the assigned NB 305 index. If N _NB ^ABM_XL is defined such that (ceil(log2(floor(N _RB ^XL /6)))+5)

N _NB ^ABM_XL , you can use this method. The application of FH can follow a similar solution as described in Option A above.

Another option is to reinterpret the NB indicator bit in the resource block allocation field. In one embodiment, for DL scheduling, the existing resource block allocation field in the DCI format 6-0A/6-1A is reinterpreted to support the allocation of up to two NB 305s. Specifically, an NB 305 of the allocated PDSCH is the same as the NB 305 used for scheduling M-PDCCH, and uses the ceil (log2(floor(NRBXL/6))) MSB indicated by the NB 305 in the resource block allocation field Can be interpreted as additional NB.

In the case of using frequency hopping to transmit the M-PDCCH, it is assumed that the NB 305 has the same NB allocation and frequency hopping mode for the first PDSCH. The second PDSCH NB 305 also follows the same frequency hopping pattern as the M-PDCCH (that is, the hopping granularity of the frequency hopping offset in the number of subframes and frequencies) to avoid the first and second PDSCH NB 305 Any possible conflicts between.

In this case, for option A, the PRB index in the allocated NB 305 may follow the allocation indicated by the 5 tail bits of the resource block allocation field, or all six PRBs 230 may be in aggregate BW mode Assigned to UE.

Option C introduces a new DCI format. According to this option type, a new DCI format that is different from DCI formats 6-0A and 6-1A and may have a different size is introduced. For this option, the solution described in option A above can be used to design a new DCI format. Additionally or alternatively, a new field for resource allocation can be introduced to signal the PRB 230 used separately in each NB 305-this option may only be limited to a small number of aggregated NB 305s that provide PRB allocation separately (For example, 2) is feasible.

As another option, only the continuous frequency NB 305 is indicated, and the resource allocation for the PRB 230 is indicated by using PDSCH resource allocation type 2 or PUSCH resource allocation type 0 on the set of PRB 230 across the allocated NB 305. When the maximum BW supported for the aggregated BW mode is given according to PRB 230 and N _NB ^ABM_XL = ceil (N _RB ^ABM_XL /6) is given to support the maximum number of NB 305 mappings, such an option may provide additional resources in resource allocation的flexibility.

Currently, considering the limited set of supported MCS, DCI The size of the modulation and coding framework (MCS) field in each of formats 6-1A and 6-0A is limited to 4 bits (ie, limited to 16QAM for DL and quadrature phase shift key for UL Control (QPSK)). If the UE supporting the aggregate BW mode (for example, Cat Mplus UE) supports higher-level modulation, the MCS field can be expanded to 5 bits, and the usual (non-LC/EC UE) MCS/TBS table can be used. Alternatively, the MCS field size can still be maintained at 4 bits; however, the 16 code points can now be remapped to include those corresponding to higher-order modulation architectures (such as 16QAM for UL and 64QAM for DL) Certain MCS and TBS values replace some of the lowest MCS/TBS values currently specified for LC/EC UEs.

When operating in aggregate BW mode for DL reception, certain enhancements to channel state information (CSI) measurement and feedback are also foreseen. Currently, for 3GPP Release 13 LC UEs in CE Mode A, the following CSI reporting modes are supported: Aperiodic CSI: Mode 2-0 (TM1,2 and 9) and Periodic CSI: Mode 1-0 (TM1,2 and 9) And mode 1-1 (TM6 and 9).

For sub-frequency CSI feedback (mode 2-0), for 3GPP Release 13 LC UE, the sub-frequency channel quality indicator (CQI) is replaced by narrow-band CQI. In addition, for the sub-frequency CSI feedback selected by the UE, the UE selects M better NBs 305 from the NB set 305 that is monitored for the M-PDCCH. For wideband CSI feedback (modes 1-0 and 1-1), for 3GPP Release 13 LC UE, use all NBs 305 for M-PDCCH monitoring to obtain wideband CQI. In addition, when the M-PDCCH is not configured with frequency hopping, the wideband CQI is the same as the NB CQI.

However, for Cat Mplus UEs, they can perform measurements on multiple NBs 305 within the _{largest aggregate BW (ie, N NB} ^{ABM_DL ).} Therefore, in one embodiment, for the sub-frequency CSI feedback selected by the UE, the UE is selected from the ^{union of the} _{NB 305 monitored for M-PDCCH and the N NB} ABM_DL NB 305 that spans the frequency range monitored for PDSCH reception. Choose M better NB 305. Similarly, in the embodiment, for wideband CSI feedback, use those NB 305 for M-PDCCH monitoring and all NBs 305 in the union _{of N NB} ^{ABM_DL NB 305 that spans the frequency range monitored for PDSCH reception to obtain broadband} CQI.

In some cases, the configuration of the UE in the aggregate BW mode for PUSCH transmission is constrained by the power headroom report (PHR) provided by the UE. Specifically, considering the importance of the available transmission power at the UE to achieve the benefits of larger PUSCH allocation, if the power headroom (PH) value reported in the PHR is small (that is, if the PH value is lower than the threshold), the UE It is not configured in the aggregate BW mode for PUSCH, or if the UE is already in aggregate BW mode, it is instructed to fall back to the single NB mode of operation for PUSCH transmission. Alternatively, the eNB may also use a smaller maximum BW to reconfigure the UE for PUSCH aggregate BW mode operation.

In some cases, when the UE calculates that the PH value is lower than the threshold, the UE autonomously performs the fallback to the single NB mode for the operation of the UE, where the threshold is specified or signaled by the eNB via a public or dedicated one (ie , UE-specific RRC signaling). Therefore, there is no need to de-configure from the eNB from the aggregate BW mode to the single NB mode, and once the UE is from the eNB When receiving a positive ACK indicating that the MAC control element (CE) carrying the PHR is successfully received at the eNB, the de-configuration is applied autonomously.

Currently, when in CE mode A, semi-static scheduling (SPS) is supported for 3GPP Release 13 LC UEs. When in the aggregate BW mode, SPS support for both DL and UL can also be maintained. Similar to the CE mode A operation, the DCI-based start/stop SPS is used, and the number of repetitions of the SPS PDSCH/PUSCH is indicated in the DCI carrying the start command. In addition, the DCI carrying the start command also provides the same frequency domain resource allocation information as in the case of the dynamically scheduled PDSCH or PUSCH. Alternatively, frequency resource allocation can be indicated via dedicated RRC signaling. The above describes in detail the enhancement required for the DCI format to support frequency resource allocation in the aggregate BW mode.

So far, the systems and methods described have considered the case of achieving higher data rates through aggregation of frequency resources spanning multiple narrowbands as defined for 3GPP Release 13 LC UEs, and at the same time, when high data is not required Limit the amount of BW monitored to allow lower power consumption. However, similar technologies can also be used in connection with "Cat.0" UEs. Therefore, it is also possible to achieve such a goal by considering Cat.0 UE, and specify the enhancements necessary for higher data rate support.

In an embodiment, the existing Cat 0 UE (which supports system BW up to 20 MHz) is defined as not monitoring the traditional wideband DL control channel including PDCCH, PCFICH, and PHICH. On the contrary, a DL control channel based on EPDCCH that is transmitted in the DL in a narrow frequency manner is defined. Similar to the behavior described for Cat Mplus UE, "Cat 0plus" UE (for example, UE 105) (For Cat Mplus, the definition of a new UE category is not implied here; this distinction may also be indicated by capability signaling) when operating in RRC idle mode or when higher data is not required When in CONNECTED mode, monitor no more than a limited set of PRBs (for example, six PRBs). Such a UE supports broadband operation across more than 6 PRB BWs configured by the eNB, or even when it is configured in a "high data rate mode" or a "wider BW mode", it is the same as the DL/UL system BW. In addition, the limitation of the maximum TBS of 1000 bits currently defined for Cat 0 UEs used for unicast transmission is also removed.

Similar to 3GPP Release 13 LC UE ("Cat M1" UE), these UEs (for example, Cat 0plus UE) can also support the reception of common control messages (for example, system information (SI), call, random access response (RAR)) ) To support narrowband operation and lack of traditional PDCCH monitoring for other UE procedures. For UL, the modification to PUCCH can be defined with or without support for frequency hopping in the subframe. However, compared with 3GPP Release 13 LC UEs, Cat 0plus UEs may not support repeated support to compensate for the reduced reception/transmission capabilities of Cat 1 UEs. Therefore, in an embodiment, all enhancements to the physical channels and procedures defined by 3GPP Release 13 LC UE can be adapted without supporting duplication. Compared to Cat 1 or even Cat 0 UE (the latter due to reduced BW operation), this can help simplify the physical layer procedures at the expense of some degradation in DL and UL coverage.

The possible solution for switching to "High Data Rate/Wide BW" mode/switching from "High Data Rate/Wide BW" mode can be achieved by targeting Cat The improvement of the solution described by Mplus UE is realized, which supports aggregate BW and single NB mode.

Fig. 6 is a flowchart of a method 600 for wireless communication performed by a UE supporting adjustable bandwidth. The method 600 is performed by the UE 105 shown in Figure 1. Although the operations of method 600 are shown as being performed in a particular order, it should be understood that the operations of method 600 may be reordered without departing from the scope of the method.

At 605, the UE operates in a single NB mode, where the device only supports communication on a single NB. A single NB is included in a plurality of NBs in the system BW. At 610, the UE decides to switch from the single NB mode to the aggregate BW mode. At 615, the UE switches from a single NB mode to an aggregate BW mode, where the device supports communication beyond a single NB in the aggregate BW mode. At 620, the UE uses an aggregate BW to communicate with the eNB, and the aggregate BW includes a single NB and at least a part of a second NB of a plurality of NBs.

The operation of the method 600 may be performed by a dedicated processor, a programmable dedicated integrated circuit (ASIC), a field programmable gate array (FPGA), and the like.

FIG. 7 is a flowchart of a method 700 for wireless communication performed by a UE supporting adjustable bandwidth. The method 700 is performed by the UE 105 shown in Figure 1. Although the operations of method 700 are shown as being performed in a particular order, it should be understood that the operations of method 700 may be reordered without departing from the scope of the method.

At 705, the UE operates in a single NB mode, where the device only supports communication on a single NB. Single NB is included in the system BW A plurality of NBs within. At 710, the UE obtains the configuration information received from the eNB. The configuration information is received in at least one of the RRC message, MAC CE, and DCI message. At 715, the UE decides to switch from the single NB mode to the aggregate BW mode based on the obtained configuration information. At 720, the UE switches from a single NB mode to an aggregate BW mode, where the device supports communication beyond a single NB in the aggregate BW mode. At 725, the UE uses an aggregate BW to communicate with the eNB, and the aggregate BW includes a single NB and at least a part of a second NB of a plurality of NBs. At 730, when operating in the aggregate BW mode, the UE obtains two or more unicast PDSCH TBs.

The operation of the method 700 may be performed by a dedicated processor, a programmable dedicated integrated circuit (ASIC), a field programmable gate array (FPGA), and the like.

Fig. 8 is a flowchart of a method 800 for wireless communication by an eNB. The method 800 is performed by the eNB 110 shown in Figure 1. Although the operations of method 800 are shown as being performed in a particular order, it should be understood that the operations of method 800 may be reordered without departing from the scope of the method.

At 805, the eNB uses the first NB to communicate with the UE. The first NB is one of a plurality of NBs in the system BW. At 810, the eNB determines that the UE should operate in aggregate BW mode. At 815, the eNB generates configuration information indicating that the UE is operating in the aggregated BW mode. At 820, the eNB uses an aggregate BW to communicate with the UE. The aggregate BW includes a single NB and at least a part of a second NB of a plurality of NBs.

The operation of method 800 may be a dedicated processor, programmable Dedicated integrated circuit (ASIC), field programmable gate array (FPGA) and so on.

FIG. 9 is a flowchart of a method 900 for wireless communication performed by a UE supporting adjustable bandwidth. The method 900 is performed by the UE 105 shown in Figure 1. Although the operations of method 900 are shown as being performed in a particular order, it should be understood that the operations of method 900 may be reordered without departing from the scope of the method.

At 905, the UE uses a single NB to communicate with the base station. A single NB is included in a plurality of NBs in the system BW. At 910, DCI is obtained on the M-PDCCH. At 915, scheduling information is determined based on the information included in one or more of the DCI fields. The scheduling information identifies one of a plurality of NBs allocated to the UE or multiple additional NBs. At 920, the UE communicates with the base station using an aggregate BW that includes a single NB and one or more additional NBs identified in the scheduling information.

The operation of the method 900 may be performed by a dedicated processor, a programmable dedicated integrated circuit (ASIC), a field programmable gate array (FPGA), and the like.

FIG. 10 is a block diagram of an electronic device circuit 1000 that may be an eNB circuit, a UE circuit, a network node circuit, or some other type of circuit according to various embodiments. In an embodiment, the electronic device circuit 1000 may be or may be incorporated or part of an eNB (for example, eNB 110), UE (for example, UE 105), mobile station (MS), BTS, network node, or some other type Electronic device. In an embodiment, the electronic device circuit 1000 may include a control circuit 1020 (For example, a baseband processor) wireless transmission circuit 1010 and reception circuit 1015. In an embodiment, the transmitting circuit 1010 and/or the receiving circuit 1015 may be components or modules of a transceiver circuit, as shown in the figure. In some embodiments, the control circuit 1020 may be in a device separate from the transmitting circuit 1010 and the receiving circuit 1015 (for example, a baseband processor shared by multiple antenna devices in a cloud-RAN (C-RAN) implementation) middle.

The electronic device circuit 1000 may be coupled to one or more antenna elements 1025 of one or more antennas. The electronic device circuit 1000 and/or the components of the electronic device circuit 1000 may be configured to perform operations similar to those described elsewhere in this disclosure.

In an embodiment where the electronic device circuit 1000 is or is incorporated into or is part of the UE, the transmitting circuit 1010 may transmit various information (eg, request to switch to/from the aggregate BW mode, BSR, CQI, etc.) to the eNB. The receiving circuit 1015 can receive various information (for example, RRC message, MAC CE message, DCI, configuration information, etc.) from the eNB.

In an embodiment in which the electronic device circuit 1000 is an eNB, a BTS, and/or a network node, or an eNB, BTS, and/or a network node that is incorporated or part of the eNB, BTS, and/or network node, the transmission circuit 1010 can transmit various information (such as , RRC message, MAC CE message, DCI, configuration information, etc.) to the UE. The receiving circuit 1015 can receive various information described above (for example, request to switch to/from the aggregate BW mode, BSR, CQI, etc.) from the UE. In some embodiments, the electronic device circuit 1000 shown in FIG. 10 is operable to perform one or more methods, such as the methods shown in FIGS. 6-9.

As used herein, the term "circuit" may refer to a part of it, or include dedicated integrated circuit (ASIC), electronic circuit, processor (shared, dedicated, or group), and/or memory (shared, dedicated, Or group), which executes one or more software or firmware programs, combinational logic circuits, and/or other appropriate hardware components that provide the functions described. In some embodiments, the circuit may be implemented in one or more software or firmware modules, or the functions associated with the circuit may be implemented in one or more software or firmware modules. In some embodiments, the circuit may include logic that is at least partially operable in hardware.

The embodiments described herein may be implemented in a system using any suitably configured hardware and/or software. Figure 11 is a block diagram showing exemplary components of a user equipment (UE) or mobile station (MS) device 1100 used in one embodiment. In some embodiments, the UE device 1100 may include an application circuit 1105, a baseband circuit 1110, a radio frequency (RF) circuit 1115, a front-end module (FEM) circuit 1120, and an application circuit 1105 coupled together as shown in FIG. 11 at least. One or more antennas 1125.

The application circuit 1105 may include one or more application processors. As a non-limiting example, the application circuit 1105 may include one or more single-core or multi-core processors. The processor may include any combination of general-purpose processors and special-purpose processors (eg, graphics processors, application processors, etc.). The processor may be operatively coupled to and/or include memory/storage, and may be configured to execute instructions stored in the memory/storage to enable various applications and/or operating systems to run on the system.

As a non-limiting example, the baseband circuit 1110 may include One or more single-core or multi-core processors. The baseband circuit 1110 may include one or more baseband processors and/or control logic. The baseband circuit 1110 may be configured to process the baseband signal received from the receive signal path of the RF circuit 1115. The baseband circuit 1110 may also be configured to generate a baseband signal for the transmission signal path of the RF circuit 1115. The baseband processing circuit 1110 may be connected to the application circuit 1105 for generating and processing baseband signals, and for controlling the operation of the RF circuit 1115.

As a non-limiting example, the baseband circuit 1110 may include a second-generation (2G) baseband processor 1110A, a third-generation (3G) baseband processor 1110B, a fourth-generation (4G) baseband processor 1110C, and At least one of other baseband processors 1110D of other current generations, generations under development, or generations to be developed in the future (for example, fifth generation (5G), 6G, etc.). The baseband circuit 1110 (for example, at least one of the baseband processors 1110A-1110D) may handle various wireless control functions, and it can communicate with one or more wireless networks via the RF circuit 1115. As a non-limiting example, wireless control functions may include signal modulation/demodulation, encoding/decoding, wireless frequency shifting, other functions, and combinations thereof. In some embodiments, the modulation/demodulation circuit of the baseband circuit 1110 may include fast Fourier transform (FFT), precoding, constellation mapping/demapping functions, other functions, and combinations thereof. In some embodiments, the encoding/decoding circuit of the baseband circuit 1110 may be programmed to perform convolution, tail convolution, turbo, Viterbi, low-density parity check (LDPC) encoder/decoder functions, other functions, and other functions. combination. The embodiments of modulation/demodulation and encoder/decoder functions are not limited to these examples, and may include other appropriate functions.

In some embodiments, the baseband circuit 1110 may include a stack of components. As a non-limiting example, the elements of the Evolved Universal Terrestrial Radio Access Network (EUTRAN) protocol include, for example, physical (PHY), medium access control (MAC), radio link control (RLC), and packetized data aggregation protocol (PDCP) , And/or Radio Resource Control (RRC) components. The central processing unit (CPU) 1110E of the baseband circuit 1110 may be programmed to run protocol stacking elements for PHY, MAC, RLC, PDCP, and/or RRC layer signaling. In some embodiments, the baseband circuit 1110 may include one or more audio digital signal processors (DSP) 1110F. Audio DSP 1110F may include components for compression/decompression and echo cancellation. The audio DSP 1110F may also include other appropriate processing elements.

The baseband circuit 1110 may also include memory/storage 1110G. The memory/storage 1110G may include data and/or instructions for operations performed by the processor of the baseband circuit 1110 stored thereon. In some embodiments, the memory/storage 1110G may include any combination of suitable volatile memory and/or non-volatile memory. Memory/storage 1110G may also include any combination of various levels of memory/storage, including but not limited to read-only memory (ROM) with embedded software instructions (for example, firmware), random access memory (For example, dynamic random access memory (DRAM)), cache, buffer, etc. In some embodiments, the memory/storage 1110G may be shared among various processors or dedicated to a specific processor.

The components of the baseband circuit 1110 may be appropriately combined in a single chip, a single chip group, or in some embodiments are arranged on the same circuit board superior. In some embodiments, some or all of the components of the baseband circuit 1110 and the application circuit 1105 may be implemented together, for example, on a system-on-a-chip (SOC).

In some embodiments, the baseband circuit 1110 may provide communication compatible with one or more wireless technologies. For example, in some embodiments, the baseband circuit 1110 may support and evolve the universal terrestrial radio access network (EUTRAN) and/or other wireless metropolitan area networks (WMAN), wireless local area networks (WLAN), wireless personal area Network (WPAN) communication. The embodiment in which the baseband circuit 1110 is configured to support wireless communication of more than one wireless protocol may be referred to as a multi-mode baseband circuit.

The RF circuit 1115 may be able to communicate with the wireless network using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuit 1115 may include a switch, a filter, an amplifier, etc. to facilitate communication with a wireless network. The RF circuit 1115 may include a receiving signal path, which may include a circuit that converts the RF signal received from the FEM circuit 1120 and provides a base frequency signal to the base frequency circuit 1110 using the following. The RF circuit 1115 may also include a transmission signal path, which may include a circuit for converting the baseband signal provided by the baseband circuit 1110 with the above and providing an RF output signal to the FEM circuit 1120 for transmission.

In some embodiments, the RF circuit 1115 may include a receiving signal path and a transmitting signal path. The receiving signal path of the RF circuit 1115 may include a mixer circuit 1115A, an amplifier circuit 1115B, and a filter circuit 1115C. The transmission signal path of the RF circuit 1115 may include a filter circuit 1115C and a mixer circuit 1115A. RF circuit 1115 can It can further include a synthesizer circuit 1115D configured to synthesize frequencies used by the mixer circuit 1115A of the receiving signal path and the transmitting signal path. In some embodiments, the mixer circuit 1115A of the receiving signal path may be configured to down-convert the RF signal received from the FEM circuit 1120 based on the synthesized frequency provided by the synthesizer circuit 1115D. The amplifier circuit 1115B may be configured to amplify the down-conversion signal.

The filter circuit 1115C may include a low-pass filter (LPF) or a band-pass filter (BPF) configured to remove unnecessary signals from the down-converted signal to generate an output fundamental frequency signal. The output baseband signal may be provided to the baseband circuit 1110 for further processing. In some embodiments, the output fundamental frequency signal may be a zero frequency fundamental frequency signal, although this is not necessary. In some embodiments, the mixer circuit 1115A of the receiving signal path may include a passive mixer, although the scope of the embodiment is not limited to this aspect.

In some embodiments, the mixer circuit 1115A of the transmission signal path may be configured to up-convert the input fundamental frequency signal based on the synthesized frequency provided by the synthesizer circuit 1115D to generate the RF output signal for the FEM circuit 1120. The baseband signal may be provided by the baseband circuit 1110 and may be filtered by the filter circuit 1115C. The filter circuit 1115C may include a low-pass filter (LPF), although the scope of the embodiment is not limited to this aspect. In some embodiments, the mixer circuit 1115A of the receiving signal path and the mixer circuit 1115A of the transmitting signal path may include two or more mixers, and may be configured for quadrature down conversion and/or up conversion, respectively. In some embodiments, the mixer circuit of the receive signal path 1115A and the mixer circuit 1115A of the transmission signal path may include two or more mixers, and may be configured for image suppression (for example, Hartley image suppression). In some embodiments, the mixer circuit 1115A and the mixer circuit 1115A of the receiving signal path may be configured for direct down conversion and/or direct up conversion, respectively. In some embodiments, the mixer circuit 1115A of the receiving signal path and the mixer circuit 1115A of the transmitting signal path may be configured for superheterodyne operation.

In some embodiments, the output fundamental frequency signal and the input fundamental frequency signal may be analog fundamental frequency signals, although the scope of the embodiment is not limited to this aspect. In some alternative embodiments, the output fundamental frequency signal and the input fundamental frequency signal may be digital fundamental frequency signals. In the above embodiment, the RF circuit 1115 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuits, and the baseband circuit 1110 may include a digital baseband interface to communicate with the RF circuit 1115.

In some dual-mode embodiments, an independent radio IC circuit may be provided for processing signals for each spectrum, although the scope of the embodiment is not limited to this aspect.

In some embodiments, the synthesizer circuit 1115D may include one or more fractional N synthesizers or fractional N/N+1 synthesizers, although the scope of the embodiments is not limited to this aspect, because other types of frequency synthesizers May be appropriate. For example, the synthesizer circuit 1115D may include a delta-sigma synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider, other synthesizers, and combinations thereof.

Synthesizer circuit 1115D may be configured to input based on frequency The sum frequency divider control input is used to synthesize the output frequency used by the mixer circuit 1115A of the RF circuit 1115. In some embodiments, the synthesizer circuit 1115D may be a fractional N/N+1 synthesizer.

In some embodiments, the frequency input may be provided by a voltage controlled oscillator (VCO), although this is not necessary. The frequency divider control input may be provided by the baseband circuit 1110 or the application processor 1105 depending on the desired output frequency. In some embodiments, the divider control input (eg, N) may be determined from a lookup table based on the channel indicated by the application processor 1105.

The synthesizer circuit 1115D of the RF circuit 1115 may include a frequency divider, a delay locked loop (DLL), a multiplexer, and a phase accumulator. In some embodiments, the frequency divider may include a dual modulus divider (DMD), and the phase accumulator may include a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by N or N+1 (e.g., based on carry) to provide a fractional division ratio. In some exemplary embodiments, the DLL may include a series of tunable delay elements, a phase detector, a charge pump, and a D-type flip-flop. In these embodiments, the delay element may be configured to break the VCO cycle into Nd equal packets in phase, where Nd is the number of delay elements in the delay line. In this way, the DLL may provide negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

In some embodiments, the synthesizer circuit 1115D may be configured to generate a carrier frequency as the output frequency. In some embodiments, the output frequency may be a multiple of the carrier frequency (for example, twice the carrier frequency, Four times the wave frequency, etc.), and used in combination with a quadrature generator and frequency divider circuit to generate multiple signals at carrier frequencies with multiple different phases from each other. In some embodiments, the output frequency may be the LO frequency (fLO). In some embodiments, the RF circuit 1115 may include an IQ/polarity converter.

The FEM circuit 1120 may include a receive signal path, which may include a configuration to operate on the RF signal received from one or more antennas 1125, amplify the received signal, and provide an amplified version of the received signal to the RF circuit 1115 for further processing The circuit. The FEM circuit 1120 may also include a transmission signal path, which may include a circuit configured to amplify the signal for transmission provided by the RF circuit 1115 for transmission by at least one of the one or more antennas 1125.

In some embodiments, the FEM circuit 1120 may include a TX/RX switch configured to switch between transmission mode and reception mode operation. The FEM circuit 1120 may include a receiving signal path and a transmitting signal path. The received signal path of the FEM circuit 1120 may include a low noise amplifier (LNA) to amplify the received RF signal and provide the amplified received RF signal as an output (for example, to the RF circuit 1115). The transmission signal path of the FEM circuit 1120 may include a power amplifier (PA) to amplify the input RF signal (for example, provided by the RF circuit 1115), and one or more filters configured to generate the RF signal for subsequent transmission (for example, by By one or more of one or more antennas 1125).

In some embodiments, the MS device 1100 may include additional components, such as memory/storage, display, camera, one or more sensors, input/output (I/O) interfaces, other components, and combinations thereof combine.

In some embodiments, the MS device 1100 may be configured to perform one or more procedures, techniques, and/or methods, or parts thereof, as described herein.

Instance

The following examples relate to further embodiments.

Example 1 is a user equipment (UE) device for wireless communication. The device includes one or more processors. One or more processors operate in a single narrowband (NB) mode, where the device only supports communication on a single NB, where a single NB is included in a plurality of NBs within the system bandwidth (BW), and it is determined from a single NB Mode switch to aggregate BW mode, switch from single NB mode to aggregate BW mode, in which the device supports communication on more than a single NB in aggregate BW mode, and uses aggregate BW to communicate with evolved node B (eNB), aggregate BW includes single NB and at least a part of the second NB of the plurality of NBs.

In Example 2, the device of Example 1 or any of the examples described herein can optionally determine to switch from the single NB mode to the aggregate BW mode when the data rate requirement meets the threshold.

Example 3 is the device of Example 2 or any of the examples described herein, wherein when the data rate requirement of unicast traffic is greater than the support data rate of a single NB, the data rate requirement meets the threshold.

Example 4 is the device of example 2 or any of the examples described herein, wherein when at least one of the UEs is in radio resource control (RRC) idle When the UE is receiving broadcast data including public control messages, and the UE is in RRC CONNECTED mode and the data rate requirement of unicast traffic is less than or equal to the support data rate of a single NB, the data rate requirement does not meet the threshold.

Example 5 is the device of example 4 or any of the examples described herein, wherein the RRC CONNECTED mode optionally includes connected mode discontinuous reception (C-DRX).

In Example 6, the device of Example 1 or any of the examples described herein may optionally receive configuration information from the eNB, wherein the decision to switch from the single NB mode to the aggregate BW mode is based at least in part on the configuration information received from the eNB.

Example 7 is the device of example 6 or any of the examples described herein, wherein the configuration information is in at least one of RRC messages, medium access control (MAC) control elements (CE), and downlink control information (DCI) messages Received in the person.

Example 8 is the device of example 7 or any of the examples described herein, wherein the DCI message is received on the machine type communication (MTC) physical downlink control channel (M-PDCCH).

In Example 9, the device of Examples 1, 2, or 6, or any of the examples described herein may optionally be based on scheduling, expiration of timers, configuration information from the eNB, uplink buffer status, and At least one of the switching from the RRC connected mode to the RRC idle mode determines the switch from the aggregate BW mode to the single NB mode, and the switch from the aggregate BW mode to the single NB mode.

In Example 10, the device of Example 1, 2, or 6, or any of the examples described herein can optionally generate an aggregate BW configuration request for the eNB, and the aggregate BW configuration request requests the eNB to configure the device to switch to the aggregate BW mode .

Example 11 is the device of Example 1 or any of the examples described herein, wherein the communication includes uplink (UL) communication.

In Example 12, the apparatus of Example 11 or any of the examples described herein may optionally generate an indication of the uplink buffer status for the eNB, wherein the decision to switch from single NB mode to aggregate BW mode is based at least in part on the uplink Road buffer status.

Example 13 is the device of example 12 or any of the examples described herein, wherein the indication of the uplink buffer status includes a buffer status report (BSR).

Example 14 is the device of Example 1 or any of the examples described herein, wherein the communication includes downlink (DL) communication.

In Example 15, the device of Example 14 or any of the examples described herein may optionally obtain two or more unicast physical downlink shared channel (PDSCH) transmission blocks (TB) when operating in aggregate BW mode .

Example 16 is the device of Example 1, 11, or 14, or any of the examples described herein, wherein the aggregate BW is used to communicate with the eNB using a transport block size (TBS) exceeding 1000 bits.

Example 17 is the device of Example 1 or any of the examples described herein, wherein each of the plurality of NBs spans six physical resource blocks (PRB) spans a BW of 1.4 megahertz (MHz).

Example 18 is the device of example 1 or any of the examples described herein, wherein the system BW is 3 MHz, 5 MHz, 10 MHz, 15 MHz, or 20 MHz.

Example 19 is the device of Example 1 or any of the examples described herein, in which one or more NBs are aggregated to the maximum supported BW, where the maximum supported BW is different from the system BW.

Example 20 is the device of Example 1 or any of the examples described herein, wherein the maximum supported BW is defined as absolute BW, the number of consecutive NBs, or the number of consecutive PRBs.

Example 21 is the device of Example 1 or any of the examples described herein, where the device switches from single NB mode to aggregate BW mode for a specific subframe during C-DRX, where the specific subframe is in the C-DRX cycle. Those sub-frames that occur within "onDuration", and the device falls back to single NB mode after the expiration of drx-InactivityTimer.

Example 22 is the apparatus of example 1 or any of the examples described herein, wherein the UE is a low complexity (LC) UE, a category M1 UE, or a category 0 UE.

Example 23 is an evolved Node B (eNB) device for wireless communication. The device includes one or more processors. One or more processors use the first narrowband (NB) to communicate with the user equipment (UE), where the first NB is one of a plurality of NBs in the system bandwidth (BW), and it is determined that the UE should be in the aggregate BW mode In operation, generate configuration information for the UE, the configuration information instructs the UE to operate in the aggregate BW mode, and use the package The aggregated BW including the first NB and at least a part of the second NB of the plurality of NBs communicates with the UE.

Example 24 is the device of example 23 or any of the examples described herein, wherein the determination that the UE should operate in the aggregate BW mode is based at least in part on the need for higher data rates.

In Example 25, the device of Example 23 or 24, or any of the examples described herein, can optionally obtain an aggregate BW configuration request from the UE, and the aggregate BW configuration request requests the device to configure the UE in the aggregate BW mode, where it is determined that the UE should Operating in the aggregate BW mode is based at least in part on the obtained aggregate BW configuration request.

In Example 26, the apparatus of Example 23 or any of the other examples described herein may optionally obtain an indication of the uplink buffer status from the UE, wherein determining that the UE should operate in aggregate BW mode is based at least in part on obtaining An indication of the status of the uplink buffer.

Example 27 is the device of example 26 or any of the other examples described herein, wherein the indication of uplink buffer status includes a buffer status report (BSR).

Example 28 is the device of Example 23 or any of the other examples described herein, wherein the configuration information is in the radio resource control (RRC) message, the medium access control (MAC) control element (CE), and the downlink Send in at least one of the control information (DCI) messages.

Example 29 is the device of example 28 or any of the other examples described herein, wherein the DCI message is sent on a machine type communication (MTC) physical downlink control channel (M-PDCCH).

Example 30 is the device of example 23 or any of the other examples described herein, wherein communication with the UE includes downlink (DL) communication.

In example 31, the device of example 30 or any of the other examples described herein may optionally provide two or more unicast physical downlink shared channel (PDSCH) transmission blocks (TB) on the aggregate BW To UE.

Example 32 is the device of example 23 or any of the other examples described herein, wherein the communication includes uplink (UL) communication.

Example 33 is the device of Example 23 or any of the other examples described herein, wherein the device uses a transport block size (TBS) exceeding 1000 bits to communicate with the UE through an aggregate BW.

Example 34 is the device of example 23 or any of the other examples described herein, wherein each NB of the plurality of NBs spans a BW of 1.4 megahertz (MHz) across six physical resource blocks (PRBs).

Example 35 is the device of example 23 or any of the other examples described herein, wherein the system BW is 3 MHz, 5 MHz, 10 MHz, 15 MHz, or 20 MHz.

Example 36 is the apparatus of example 23 or any of the other examples described herein, wherein the UE is a low complexity (LC) UE, a category M1 UE, or a category 0 UE.

Example 37 is a user equipment (UE) device. The device includes one or more processors. One or more processors use a single NB to communicate with the base station, where the single NB is included in the system bandwidth (BW). Among several NBs, the downlink control information (DCI) is obtained on the machine type communication (MTC) physical downlink control channel (M-PDCCH), based on the information included in one or more fields of the DCI Determine the schedule information, the schedule information identifies one or more additional NBs of multiple NBs allocated to the UE, and communicates with the base station using an aggregate BW including a single NB and one or more additional NBs identified in the schedule information .

Example 38 is the device of example 37 or any of the other examples described herein, wherein the scheduling information enables the UE to operate in aggregate BW mode.

Example 39 is the device of example 37 or any of the other examples described herein, wherein DCI uses at least one of DCI format 6-0A and DCI format 6-1A.

Example 40 is the device of example 39 or any of the other examples described herein, wherein the scheduling information is included in one or more new resource allocation fields of DCI, one or more other than any existing DCI fields Multiple new resource allocation fields.

Example 41 is the device of example 39 or any of the other examples described herein, wherein the scheduling information is included in one or more existing DCI fields that have been reformatted into one or more resource allocation fields .

Example 42 is the device of example 37 or any of the other examples described herein, wherein the DCI uses a new DCI format that indicates operation in aggregate BW mode.

Example 43 is a method for wireless communication. The method includes operating in a single narrowband (NB) mode, where the device only supports A communication on an NB, where a single NB is included in a plurality of NBs within the system bandwidth (BW), it is determined to switch from a single NB mode to an aggregate BW mode, and from a single NB mode to an aggregate BW mode, where the device supports the aggregation In the BW mode, more than a single NB is used to communicate and an aggregate BW is used to communicate with an evolved node B (eNB). The aggregate BW includes a single NB and at least a part of the second NB of a plurality of NBs.

In Example 44, the method of Example 43 or any of the other examples described herein may optionally include determining to switch from the single NB mode to the aggregate BW mode when the data rate requirement meets the threshold.

Example 45 is the method of example 44 or any of the other examples described herein, wherein when the data rate requirement of unicast traffic is greater than the support data rate of a single NB, the data rate requirement meets the threshold.

Example 46 is the method of example 44 or any of the other examples described herein, wherein when at least one of the UEs is in radio resource control (RRC) idle mode, the UE is receiving broadcast data including common control messages, and the UE is in When the RRC CONNECTED mode and the data rate requirement of unicast traffic is less than or equal to the support data rate of a single NB, the data rate requirement does not meet the threshold. The RRC CONNECTED mode includes connected mode discontinuous reception (C-DRX).

In Example 47, the method of Example 43 or any of the other examples described herein may optionally include receiving configuration information from an eNB, wherein the decision to switch from single NB mode to aggregate BW mode is based at least in part on receiving from the eNB Configuration information, where the configuration information is in the RRC message, media access control (MAC) control element (CE), and At least one of downlink control information (DCI) messages is received, and the DCI message is received on a machine type communication (MTC) physical downlink control channel (M-PDCCH).

In Example 48, the method of Example 43 or any of the other examples described herein may optionally include scheduling based, timer expiration, configuration information from the eNB, uplink buffer status, and At least one of the switching from the RRC connected mode to the RRC idle mode determines the switch from the aggregate BW mode to the single NB mode, and the switch from the aggregate BW mode to the single NB mode.

In Example 49, the method of Example 43 or any of the other examples described herein may optionally include generating an aggregate BW configuration request for the eNB, the aggregate BW configuration request requesting the eNB to configure the device to switch to the aggregate BW mode .

In Example 50, the method of Example 43 or any of the other examples described herein may optionally include generating an indication of the uplink buffer status for the eNB, where it is determined to switch from single NB mode to aggregate BW mode Based at least in part on the uplink buffer status, where the indication of the uplink buffer status includes a buffer status report (BSR).

In Example 51, the method of Example 43 or any of the other examples described herein may optionally include obtaining two or more unicast entity downlink shared channels (PDSCH) when operating in aggregate BW mode Transmission block (TB).

Example 52 is one of Example 43 or other examples described herein Either method, in which the device switches from single NB mode to aggregate BW mode for a specific subframe during C-DRX, where the specific subframes are those that occur within the "onDuration" of the C-DRX cycle , And after the expiration of the drx-InactivityTimer, the device returns to the single NB mode.

Example 53 is a method for wireless communication. The method includes using a first narrowband (NB) to communicate with a user equipment (UE), where the first NB is one of a plurality of NBs in the system bandwidth (BW), determining that the UE should operate in aggregate BW mode, and generating Configuration information for the UE, the configuration information instructs the UE to operate in the aggregate BW mode and communicate with the UE using the aggregate BW including the first NB and at least a part of the second NB of the plurality of NBs.

Example 54 is the method of example 53, or any of the other examples described herein, wherein determining that the UE should operate in aggregate BW mode is based at least in part on the need for higher data rates.

In Example 55, the method of Example 53 or any of the other examples described herein may optionally include obtaining an aggregate BW configuration request from the UE, and the aggregate BW configuration request requesting apparatus configures the UE in an aggregate BW mode, wherein The decision that the UE should operate in the aggregate BW mode is based at least in part on the obtained aggregate BW configuration request.

In Example 56, the method of Example 53, or any of the other examples described herein, may optionally include obtaining an indication of uplink buffer status from the UE, where it is determined that the UE should operate in aggregate BW mode, at least in part Based on the obtained indication of the uplink buffer status, where The indication of the uplink buffer status includes a buffer status report (BSR).

Example 57 is the method of Example 53 or any of the other examples described herein, wherein the configuration information is in the radio resource control (RRC) message, the medium access control (MAC) control element (CE), and the downlink The control information (DCI) message is sent in at least one of the messages, wherein the DCI message is sent on the machine type communication (MTC) physical downlink control channel (M-PDCCH).

In Example 58, the method of Example 53, or any of the other examples described herein, may optionally include providing two or more Unicast Physical Downlink Shared Channel (PDSCH) transmission blocks on the aggregate BW ( TB) to UE.

Example 59 is a method for scheduling wireless communication. The method includes using a single NB to communicate with the base station, where the single NB is included in a plurality of NBs within the system bandwidth (BW), and the downlink is obtained on the machine type communication (MTC) physical downlink control channel (M-PDCCH) Link control information (DCI), scheduling information is determined based on the information included in one or more of the DCI fields, the scheduling information identifies one or more additional NBs of a plurality of NBs allocated to the UE, and the use includes The aggregate BW of a single NB and one or more additional NBs identified in the schedule information communicates with the base station.

Example 60 is the method of example 59 or any of the other examples described herein, wherein the scheduling information enables the UE to operate in aggregate BW mode.

Example 61 is the method of example 59 or any of the other examples described herein, wherein DCI uses at least one of DCI format 6-0A and DCI format 6-1A.

Example 62 is the method of Example 61 or any of the other examples described herein, wherein the scheduling information is included in one or more new resource allocation fields of the DCI, in addition to any existing DCI fields, or Multiple new resource allocation fields.

Example 63 is the method of Example 61 or any of the other examples described herein, wherein the scheduling information is included in one or more existing DCI fields that have been reformatted into one or more resource allocation fields .

Example 64 is the method of example 59 or any of the other examples described herein, wherein the DCI uses a new DCI format that indicates operation in the aggregate BW mode.

Example 65 is a system and method for supporting user equipment. Compared with category 0 or version 13 LC UE, the user equipment supports the adjustable bandwidth for reception or transmission according to the need for higher data rate. When a high data rate for DL or UL is required, it supports narrowband reception and transmission, and when a higher data rate is required, it supports a single narrowband that is wider than for DL reception or UL transmission.

Example 66 is the UE of example 65 or any of the other examples described herein, where a single narrowband (NB) spans a 1.4 MHz bandwidth across 6 PRBs.

Example 67 is the UE of example 66 or any of the other examples described herein, where the UE is similar to supporting no more than a single NB. The 3GPP Release 13 LC UE operates in a single narrowband mode and has the ability to retune from one narrowband to another within a larger system BW during the time when there is no high data rate requirement.

Example 68 is the UE of example 67 or any of the other examples described herein, where the time when there is no high data rate requirement corresponds to when the UE is in RRC IDLE mode, or when it is receiving broadcast data including public control messages When it is in CONNECTED mode in C-DRX or non-DRX CONNECTED mode with unicast traffic without high data requirements.

Example 69 is the UE of example 66 or any of the other examples described herein, where the UE is operating in aggregate BW mode, where the UE supports reception on frequency resources spanning more than a single 1.4MHz NB with 6 PRBs /Transmission (respectively), subject to the maximum supported BW for BW aggregation, when a high data rate request is triggered for DL or UL, it is used for unicast reception or transmission, respectively.

Example 70 is the UE of example 69 or any of the other examples described herein, where the aggregate BW mode is implemented by aggregating PRBs belonging to one or more 1.4MHz NBs, which may or may not be adjacent to each other, but These PRBs appear in the frequency domain within the maximum supported BW for BW aggregation.

Example 71 is the UE of example 69 or 70 or any of the other examples described herein, where the maximum supported BW for BW aggregation is separated from the maximum LTE system BW (eg, 20 MHz) or the deployed LTE system BW.

Example 72 is the UE of example 68 or any of the other examples described herein, wherein the UE supports the aggregated BW mode in connected DRX (C-DRX) during certain times of the C-DRX cycle, depending on the intended use For the high data rate requirements of dynamic scheduling flow or SPS flow.

Example 73 is the UE of example 72 or any of the other examples described herein, wherein the UE supports the aggregate BW mode in a specific subframe (which may be a subframe within "onDuration") during C-DRX, and After the expiration of the drx-InactivityTimer, the UE falls back to the single NB mode.

Instance 74 is the UE of instance 72 or any of the other instances described herein, wherein the UE uses a single NB mode until it receives an MTC (MPDCCH) instruction for dynamic switching to aggregate BW mode when switching to aggregate BW mode The entity DL controls the channel so far, and then falls back to the single NB mode after a certain newly defined timer expires or after an existing timer (for example, onDuration/drxInactivityTimer) expires.

Example 75 is the UE of example 71 or any of the other examples described herein, wherein the maximum supported BW for BW aggregation is defined according to absolute BW (for example, 7.5MHz, 10MHz, 15MHz, etc.), or according to continuous narrowness The maximum supported BW is defined by the number of NBs. For example, the maximum supported BW is given by the frequency spanned by 4, 6, 8, etc. continuous NBs, each 1.4MHz (6 PRBs) wide, or defined according to the number of continuous PRBs, For example, the maximum supported BW is given by the frequency spanned by "N" consecutive PRBs, where N=25, 40, 50, etc.

Example 76 is one of Example 66 or other examples described herein Any UE, where the UE is not expected to support simultaneous reception of multiple transmission blocks, even when operating in aggregate BW mode.

Example 77 is the UE of example 66 or any of the other examples described herein, where the UE is not expected to support receiving multiple broadcast TBs or a mixture of broadcast and unicast TBs, but the UE is expected to support up to two unicasts PDSCH TB, which may be transmitted using PRBs within the maximum supported BW when operating in aggregate BW mode.

Example 78 is the UE of example 77 or any of the other examples described herein, where the UE generates HARQ-ACK feedback corresponding to each PDSCH transmission block (TB) transmitted using PUCCH format 1b, where the PUCCH resources Exporting and mapping to physical resources (including support for repeated transmission and frequency hopping) can follow the behavior defined in Coverage Enhancement (CE) Mode A for 3GPP Release 13 LC MTC UE.

Example 79 is the UE of example 77 or any of the other examples described herein, in which the scheduling of PDSCH with multiple unicast TBs is similar to the traditional LTE DCI format 2/2A/2B/2C/2D, for Each TB indicates MCS, RV index, and NDI bits respectively.

Example 80 is the UE of example 77 or any of the other examples described herein, wherein the frequency domain resource allocation given by the existing DCI format 6-1A corresponds to the resources for the first TB, and the second TB is mapped To the NB with additional instructions.

Example 81 is the UE of example 66 or any of the other examples described herein, where for UL transmission, the UE uses only one or more consecutive PRBs to transmit a single PUSCH TB, so that for the latter case, when When operating in aggregate BW mode, the PRB spans more than a single 1.4MHz BW.

Example 82 is the UE of example 81 or any of the other examples described herein, where the UE does not support simultaneous transmission of PUSCH and PUCCH.

Example 83 is the UE of example 66 or any of the other examples described herein, wherein the UE supports a transmission block size (TBS) value greater than 1000 bits for unicast reception or transmission in DL or UL, respectively.

Example 84 is the UE of example 66 or any of the other examples described herein, where the UE supports a modulation order higher than 16 QAM for DL and higher than QPSK for UL, which is when the UE is converging BW When operating in the mode, they are used for receiving and transmitting respectively.

Example 85 is the UE of example 66 or any of the other examples described herein, wherein the UE supports a half-duplex-FDD (HD-FDD) operation mode, wherein the HARQ-ACK wrapped in response to PDSCH reception is supported, thereby The UE reports the wrapped HARQ-ACK feedback corresponding to multiple PDSCH transmission blocks (TB) on different DL subframes in a single PUCCH transmission.

Example 86 is the UE of example 66 or any of the other examples described herein, where operation in the aggregate BW mode is limited to CE mode A only.

Example 87 is the UE of example 66 or any of the other examples described herein, wherein different types of UEs are defined according to the maximum data rate supported by the UE or the maximum BW for BW aggregation supported by the UE.

Example 88 is the UE of example 66 or any of the other examples described herein, in which the maximum data rate supported or the maximum BW for the supported BW aggregation is indicated to the eNodeB by capability signaling.

Instance 89 is the UE of instance 88 or any of the other instances described herein, wherein the capability signaling is carried as part of the RRCConnectionRequest message, that is, indicated in the transmission of Message 3 during the random access procedure, or as a response to The RRC message of the capability indication request from the eNodeB is indicated to the eNodeB.

Instance 90 is the UE of instance 66 or any of the other instances described herein, wherein the UE switches between single NB mode and aggregate BW mode based on the configuration received from the eNodeB.

Instance 91 is the UE of instance 90 or any of the other instances described herein, wherein the switching between the two modes is signaled by the eNodeB once triggered by the eNodeB or based on a request from the UE.

Example 92 is the UE of example 90 or any of the other examples described herein, where switching between the two modes is separately configured for DL and UL.

Instance 93 is the UE of instance 90 or any of the other instances described herein, where the eNodeB determines that it needs to support a larger TBS and use it according to the QoS requirements for MT or MO traffic, respectively. When a larger number of PRBs are scheduled for PDSCH or PUSCH, it is configured in the aggregate BW mode.

Example 94 is the UE of example 90 or any of the other examples described herein, where the UE depends on scheduling decision or termination of the Switch back to the single NB mode as required by the material rate.

Example 95 is the UE of example 90 or any of the other examples described herein, where signaling via dedicated RRC or MAC CE or via DCI indicates to/from the configuration of the aggregated BW mode.

Example 96 is the UE of example 95 or any of the other examples described herein, wherein for the RRC or MAC CE-based configuration of the aggregate BW mode, the maximum aggregate BW that may schedule the PDSCH is indicated in the RRC or MAC CE message .

Example 97 is the UE of example 96 or any of the other examples described herein, wherein the timing between the MPDCCH and the scheduled PDSCH is reduced from the second valid subframe after the last MPDCCH subframe (to carry the scheduled The first sub-frame of the PDSCH of the process is defined for Release 13 LC UE) to the first valid sub-frame after the last MPDCCH sub-frame.

Example 98 is the UE of example 95 or any of the other examples described herein, in which for the option based on DCI signaling, the mechanism is similar to the SPS start and release indication, in which, for example, by defining a new adjustable BW-RNTI ( SB-RNTI) uses DL allocation or UL grant DCI together with scrambling of CRC with new RNTI (ie, in this case, DCI format 6-1A or format 6-0A, respectively).

Example 99 is the UE of example 95 or any of the other examples described herein, in which the configuration and de-configuration of the aggregated BW mode can be signaled to the UE via different signalling paths.

Example 100 is one of example 90 or other examples described herein Any UE, where depending on application requirements, the UE sends a request to configure it in the aggregate BW mode via obvious signaling or via a request for a larger BW or a higher data rate.

Example 101 is the UE of example 90 or any of the other examples described herein, where the UE sends a request to the eNodeB to return to single NB mode to optimize power consumption when the data rate requirement decreases.

Instance 102 is the UE of instance 100 or 101 or any of the other instances described herein, wherein the request message from the UE is defined as an RRC message or a MAC control element (CE) message, which has instructions to switch to/from the aggregate BW The mode is only used for DL, or only UL, or both options.

Instance 103 is the UE of instance 90 or any of the other instances described herein, where based on a buffer status report (BSR) indication, a switch between the two modes can be triggered implicitly.

Instance 104 is the UE of instance 103 or any of the other instances described herein, wherein when the buffer size reported in the BSR or in multiple consecutive BSRs exceeds a certain threshold, the UE is configured by the eNodeB to operate in aggregate BW mode Medium operation, and switch back to single NB mode when the aggregate buffer size is below a certain threshold.

Instance 105 is the UE of instance 104 or any of the other instances described herein, where the rules for mode switching are defined in the specification, and the threshold for mode switching in each direction is determined by the eNodeB via public or dedicated RRC Send a letter to indicate, and the UE autonomously switches between the UL aggregate BW mode and the single NB mode according to the UL buffer status Change.

Example 106 is the UE of example 90 or any of the other examples described herein, wherein the UE is reconfigured from an aggregate BW mode with a certain total BW to an aggregate BW mode with a different total BW value.

Example 107 is the UE of example 66 or any of the other examples described herein, where the maximum number of NB support for NB aggregation in DL or UL (here, XL=DL or UL) is given _{by N NB} ^ABM_XL It is fixed and specified as a function of the system BW, or can even be indicated via MTC SIB (System Information Block for 3GPP Release 13 LC UE).

Example 108 is the UE of example 107 or any of the other examples described herein, wherein N _NB ^ABM_XL = floor(N _RB ^XL /6) or N _NB ^ABM_XL = min{floor(N _RB ^XL /6), N _NB ^ABM_XL_UE }, where N _NB ^ABM_XL_UE is the maximum number of consecutive NBs supported by the UE.

Example 109 is the UE of example 108 or any of the other examples described herein, where N _NB ^ABM_XL_UE is a common value for all UEs supporting adjustable BW and aggregate BW modes, or where N _NB ^ABM_XL_UE is UE-specific .

Example 110 is the UE of example 107 or any of the other examples described herein, where the maximum BW (N _NB ^ABM_XL ) is indicated in terms of 6-PRB narrowband or in terms of the number of PRBs.

Instance 111 is the UE of instance 107 or any of the other instances described herein, where the NB monitored for MPDCCH is always included in the set _{of N NB} ^{ABM_DL NB for receiving PDSCH.}

Example 112 is the UE of example 107 or any of the other examples described herein, where _{the set of N NB} ^ABM_DL NB for receiving PDSCH does not need to include the NB used for MPDCCH monitoring in the subframe, and if used ^If the set of N _NB ABM_DL NB receiving PDSCH does not include the NB used for MPDCCH monitoring in the subframe, the UE prioritizes the scheduled PDSCH reception when monitoring MPDCCH reception.

Example 113 is the UE of example 66 or any of the other examples described herein, where it is performed by introducing new resource allocation fields in existing DCI formats 6-0A, 6-1A with possible new DCI sizes It is used for resource allocation of DL and UL in the aggregated BW mode, where the existence of the new field depends on the operation mode (aggregated BW mode or single NB mode).

Example 114 is the UE of example 113 or any of the other examples described herein, where the new field is placed at a known position in the DCI, where the known position is at the beginning or end of the DCI.

Example 115 is the UE of example 66 or any of the other examples described herein, wherein when the UE is in aggregate BW mode without changing the DCI size, the existing resource allocation in the existing DCI formats 6-0A, 6-1A is reinterpreted Field.

Instance 116 is the UE of instance 67 or any of the other instances described herein, where a new DCI format is introduced, which is monitored when the UE is in aggregate BW mode.

Example 117 is the UE of example 84 or any of the other examples described herein, in which the MCS field is extended to 5 bits, and the usual (Non-LC/EC UE) MCS/TBS table.

Example 118 is the UE of example 84 or any of the other examples described herein, where the MCS field size is 4 bits; and 16 code points are remapped to include corresponding to higher-order modulation architectures (for example, for Some MCS and TBS values of 16QAM for UL and 64QAM for DL) replace some of the lowest MCS/TBS values currently specified for LC/EC UEs.

Example 119 is the UE of example 66 or any of the other examples described herein, wherein for the sub-frequency CSI feedback selected by the UE, the UE is monitored from the NB monitored for MPDCCH and the frequency range that spans the frequency range monitored for PDSCH reception. Select M better NBs in the union of N _NB ^{ABM_DL NB.}

Example 120 is the UE of example 66 or any of the other examples described herein, where for wideband CSI feedback, one of those NBs used for MPDCCH monitoring and N _NB ^ABM_DL NBs spanning the frequency range monitored for PDSCH reception is used All NBs in the union get broadband CQI.

Example 121 is the UE of example 66 or any of the other examples described herein, wherein the configuration of the UE in the aggregate BW mode for PUSCH transmission is constrained by the power headroom report (PHR) provided by the UE.

Instance 122 is the UE of instance 121 or any of the other instances described herein, wherein when the UE calculates that the power headroom (PH) value is lower than the threshold, the UE autonomously performs the fallback for the operation of the UE to one An NB mode in which the threshold is specified or signaled by the eNodeB via public or dedicated (ie, UE-specific RRC signalling).

Instance 123 is the UE of instance 122 or any of the other instances described herein, wherein the UE autonomously applies the release group upon receiving a positive ACK from the eNodeB indicating the successful reception of the MAC control element (CE) carrying the PHR at the eNodeB state.

Example 124 is the UE of example 66 or any of the other examples described herein, where the UE supports SPS for DL and UL when in aggregate BW mode, where DCI-based start/stop SPS is used, and the bearer starts The DCI of the command indicates the number of repetitions of the SPS PDSCH/PUSCH, and the frequency domain resource allocation information is indicated in the activation of the DCI or via dedicated RRC signaling.

Example 125 is the UE of example 66 or any of the other examples described herein, where the UE is based on Cat 0 UE, so that it is undesirable to monitor traditional broadband DL control channels including PDCCH, PCFICH, and PHICH.

Example 126 is the UE of example 125 or any of the other examples described herein, where the UE uses a wider BW to receive or transmit only when a high data rate is required.

Example 127 is the UE of example 126 or any of the other examples described herein, where the 1000-bit TBS limit for unicast traffic of Cat 0 UEs is removed for the UE.

Instance 128 is an apparatus for UE, including tools for performing any operation, method, or program described herein.

Instance 129 is a device for eNB, including tools for performing any operation, method, or program described herein.

Example 130 is a machine-readable storage medium that includes machine-readable instructions, which when executed, cause one or more processors to implement any of operations, methods, or programs, or to implement any of the operations, methods, or programs described herein. Device.

The embodiments and implementations of the systems and methods described herein may include various operations, which may be embodied in machine-executable instructions to be executed by a computer system. The computer system may include one or more general-purpose or special-purpose computers (or other electronic devices). The computer system may include hardware components that include specific logic for operations, or may include a combination of hardware, software, and/or firmware.

The computer system and the computers in the computer system may be connected via a network. Appropriate networks for configuration and/or use as described herein include one or more local area networks, wide area networks, metropolitan area networks, and/or Internet or IP networks, such as the World Wide Web, Private Internet, secure Internet, value-added network, virtual private network, extranet, intranet, or even independent machines that communicate with other machines through physical transmission of media. In particular, an appropriate network may be formed by part or all of two or more other networks, including networks that use different hardware and network communication technologies.

An appropriate network includes a server and one or more clients; other appropriate networks may include other combinations of servers, clients, and/or peer-to-peer nodes, and a given computer system may act as both a client and As a server. Each network includes at least two computers or computer systems System, such as server and/or client. Computer systems may include workstations, laptops, detachable mobile computers, servers, mainframes, clusters, so-called "network computers" or "thin clients", tablets, smart phones, personal digital assistants, or other handheld computers. Computing devices, "smart" consumer electronic devices or appliances, medical devices, or combinations thereof.

Appropriate networks may include communications or networking software, such as software that may be obtained from Novell®, Microsoft®, and other vendors, and may use TCP/IP, SPX, IPX, and through twisted pair, coaxial, or fiber optic cables , Telephone lines, radio waves, satellites, microwave relays, modulated AC power lines, physical media transmission, and/or other data transmission "wires" known to those skilled in the art. Networks may include smaller networks and/or may be connected to other networks through gateways or similar mechanisms.

Various technologies, or some aspects or parts thereof, may be adopted on tangible media (such as floppy disks, CD-ROMs, hard drives, magnetic or optical cards, solid-state memory devices, non-transitory computer-readable storage media, or any The form of program code (ie, instructions) implemented in other machine-readable storage media), where when the program code is loaded into and executed by a machine (such as a computer), the machine becomes a device for implementing various technologies . When the code is executed on a programmable computer, the computing device may include a processor, a storage medium readable by the processor (including volatile and non-volatile memory and/or storage elements), at least one input device, and At least one output device. Volatile and non-volatile memory and/or storage components may be RAM, EPROM, flash drives, optical drives, magnetic hard drives, or used to store electronic Information on other media. The eNB (or other base station) and UE (or other mobile station) may also include transceiver components, counter components, processing components, and/or clock components or timer components. One or more programs that may implement or utilize the various technologies described herein may use application programming interfaces (APIs), reusable controls, and so on. Such programs may be implemented in high-level programs or object-oriented programming languages to communicate with computer systems. However, if necessary, the program may be implemented in combination or machine language. In any case, the language may be a compiled or translated language, combined with hardware implementation.

Each computer system includes one or more processors and/or memory; the computer system may also include various input devices and/or output devices. The processor may include general-purpose devices such as Intel®, AMD®, or other "off-the-shelf" microprocessors. The processor may include a dedicated processing device, such as ASIC, SoC, SiP, FPGA, PAL, PLA, FPLA, PLD, or other custom or programmable devices. Memory may include static RAM, dynamic RAM, flash memory, one or more flip-flops, ROM, CD-ROM, DVD, floppy disk, magnetic tape, or magnetic, optical, or other computer storage media. Input devices may include keyboards, mice, touch screens, light pens, tablets, microphones, sensors, or other hardware with attached firmware and/or software. Output devices may include screens or other displays, printers, voice or text synthesizers, switches, signal cables, or other hardware with attached firmware and/or software.

It should be understood that many functional units described in this specification may be implemented as one or more components. This is to more specifically emphasize that they are independent. Stand-alone term. For example, the device may be implemented as a hardware circuit containing custom very large integrated circuit (VLSI) circuits or gate arrays, or off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. Components may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices, or the like.

Components may also be implemented in software to be executed by various types of processors. The identification element of the executable code may, for example, include one or more physical or logical blocks of computer instructions, which may be organized into objects, programs, or functions, for example. However, the executable codes for identifying the components do not need to be physically placed together, but may include different instructions stored in different locations. When they are logically combined, they include the components and achieve the stated purpose for the components.

In fact, the components of the executable code may be a single instruction or many instructions, and may even be distributed on several different code segments, between different programs, and across several memory devices. Similarly, the operating data may be identified and drawn in the components in this document, and may be implemented in any appropriate form and organized in any appropriate type of data structure. The operating data may be collected as a single data set, or may be distributed in different locations (including on different storage devices), and may at least partially exist only as electronic signals on the system or the Internet. Components may be passive or active, including agents that are operable to perform the desired function.

Several aspects of the described embodiments will be shown as software modules or components. As used herein, a software module or body may include any type of computer instructions or computer executable code located in a memory device. soft The body module may, for example, include one or more physical or logical blocks of computer commands, which may be organized into routines, programs, objects, components, data structures, etc., which perform one or more tasks or implement specific data types. It should be understood that instead of or in addition to software, software modules may be implemented in hardware and/or firmware. One or more functional modules described herein may be divided into sub-modules and/or combined into a single or a smaller number of modules.

In some embodiments, a specific software module may include different commands stored in a memory device, different memory devices, or different locations in different computers, which together implement the functions of the module. In fact, a module may include a single instruction or many instructions, and may be distributed on several different code segments, between different programs, and across several memory devices. Some embodiments may be implemented in a distributed computing environment, where tasks are performed by remote processing devices linked through a communication network. In a distributed computing environment, software modules may be located in local and/or remote memory storage devices. In addition, the data bound or presented together in the database records may reside in the same memory device or across several memory devices, and may be linked together in the fields of the records in the database across the network.

The "example" mentioned throughout this specification means that a specific feature, structure, or characteristic described in combination with the example is included in at least one embodiment of the present disclosure. Therefore, the expressions "in the examples" appearing in various places throughout this specification do not necessarily all refer to the same embodiment.

As used herein, for convenience, a plurality of items, structural elements, constituent elements, and/or materials may be presented in a common list. However, these lists should be interpreted as if each component of the list is Don’t recognize it as a separate and unique component. Therefore, none of the individual components of the above list should be interpreted as the actual equivalent of any other components of the same list based on their presentation in the common group without contrary instructions. In addition, various embodiments and examples of the present technology may be referred to herein along with alternatives to various elements thereof. It is understood that the above-mentioned embodiments, examples, and alternatives are not interpreted as actual equivalents to each other, but are regarded as independent and autonomous representations of the present disclosure.

Furthermore, in one or more embodiments, the described features, structures, or characteristics may be combined in any suitable manner. In the following description, many specific details (such as examples of material, frequency, size, length, width, shape, etc.) are proposed to provide a comprehensive understanding of the embodiments of the present disclosure. However, those skilled in the art will understand that the present disclosure may be implemented without one or more specific details, or with other methods, elements, materials, etc. In other cases, well-known structures, materials, or operations are not shown or described in detail so as not to obscure the aspect of the disclosure.

It should be recognized that the system described herein includes a description of specific embodiments. These embodiments can be combined into a single system, partially combined into other systems, divided into multiple systems, or separated or combined in other ways. In addition, it is expected that the parameters/attributes/aspects/etc. of one embodiment can be used in another embodiment. For the sake of clarity, only parameters/attributes/aspects/etc. are described in one or more embodiments, and it is recognized that parameters/attributes/aspects/etc. can be combined with or substituted for parameters/attributes/etc., unless This article explicitly denies it.

Although the foregoing has been described in considerable detail for the sake of clarity, it is obvious that it can be used without departing from its principles. Some changes and modifications can be made. It should be noted that there are many alternative ways of implementing the programs and devices described herein. Therefore, the present embodiment is considered to be illustrative rather than restrictive, and the present disclosure is not limited to the details given herein, but may be modified within the scope and equivalents of the attached patent application.

Those skilled in the art will understand that many changes may be made to the details of the above-mentioned embodiments without departing from the basic principles of this disclosure. Therefore, the scope of this disclosure should only be determined by the scope of the following patent applications.

600‧‧‧Method

Claims (22)

A user equipment (UE) device for wireless communication. The device includes: one or more processors for: operating in a single narrowband (NB) mode, wherein the device only supports communication on a single NB , Where the single NB is included in a plurality of NBs in the system bandwidth (BW); it is determined to switch from the single NB mode to the aggregate BW mode; from the single NB mode to the aggregate BW mode, and the device supports the In the aggregate BW mode, communication is performed on more than the single NB; and an aggregate BW is used to communicate with an evolved node B (eNB), and the aggregate BW includes at least a part of the single NB and a second NB of the plurality of NBs. In the device described in item 1 of the scope of patent application, when the data rate requirement meets a threshold, the one or more processors determine to switch from the single NB mode to the aggregate BW mode. For the device described in item 2 of the scope of patent application, when the data rate requirement of unicast traffic is greater than the support data rate of the single NB, the data rate requirement meets the threshold. The device described in claim 2, wherein at least one of the following: (i) the UE is in radio resource control (RRC) idle mode, (ii) the UE is receiving broadcast data including public control messages, or (iii) The UE is in RRC CONNECTED mode and unicast When the data rate requirement of the traffic is less than or equal to the support data rate of the single NB, the data rate requirement does not meet the threshold, and the RRC CONNECTED mode includes connected mode discontinuous reception (C-DRX). For the device described in claim 1, wherein the one or more processors are further used to: receive configuration information from the eNB, wherein the decision to switch from the single NB mode to the aggregate BW mode is based at least in part on the slave The configuration information received by the eNB, where the configuration information is received in at least one of an RRC message, a medium access control (MAC) control element (CE), and a downlink control information (DCI) message, and wherein The DCI message is received on the machine type communication (MTC) physical downlink control channel (M-PDCCH). For the device described in claim 1, wherein the one or more processors are further used for: scheduling based, expiration of timers, configuration information from the eNB, uplink buffer status, and At least one of the switching from the RRC connected mode to the RRC idle mode is determined to switch from the aggregate BW mode to the single NB mode; and switch from the aggregate BW mode to the single NB mode. For the device described in claim 1, wherein the one or more processors are further used to: generate an aggregate BW configuration request for the eNB, and the aggregate BW configuration request requests the eNB to configure the device to switch to The aggregation BW mode. For the device described in item 1 of the scope of patent application, the one or The multiple processors are further used to generate an indication of the uplink buffer status for the eNB, wherein the decision to switch from the single NB mode to the aggregate BW mode is based at least in part on the uplink buffer status, and wherein The indication of the uplink buffer status includes a buffer status report (BSR). The device described in claim 1, wherein the one or more processors are further used to: obtain two or more unicast physical downlink shared channels (PDSCH) when operating in the aggregate BW mode Transmission block (TB). For the device described in the first item of the patent application, one or more NBs are aggregated to the maximum supported BW, where the maximum supported BW is different from the system BW. The device described in claim 1, wherein the device switches from the single NB mode to the aggregate BW mode for a specific sub-frame during C-DRX, wherein the specific sub-frame is in the C-DRX period Those sub-frames that occurred within the "onDuration" of the device, and the device will fall back to the single NB mode after the expiration of the drx-InactivityTimer. An evolved node B (eNB) device for wireless communication. The device includes: one or more processors for: using a first narrowband (NB) to communicate with a user equipment (UE), wherein the first NB is one of multiple NBs in the system bandwidth (BW); it is determined that the UE should operate in aggregate BW mode; Generating configuration information for the UE, the configuration information instructing the UE to operate in the aggregate BW mode; and using the aggregate BW and the UE including at least a part of the first NB and the second NB of the plurality of NBs communication. For the device described in item 12 of the scope of patent application, the determination that the UE should operate in the aggregate BW mode is based at least in part on the need for a higher data rate. For the device described in item 12 of the scope of patent application, the one or more processors are further used to: obtain an aggregate BW configuration request from the UE, and the aggregate BW configuration request requests the device to group in the aggregate BW mode State the UE, wherein the decision to configure the UE to operate in the aggregate BW mode is based at least in part on the obtained aggregate BW configuration request. A device for a user equipment (UE), comprising: one or more processors, used for communicating with a base station using a single NB, wherein the single NB is included in a plurality of NBs within a system bandwidth (BW); Obtain downlink control information (DCI) on the machine type communication (MTC) physical downlink control channel (M-PDCCH); determine scheduling information based on the information included in one or more fields of the DCI , The scheduling information identifies one or more additional NBs of the plurality of NBs allocated to the UE; and using an aggregate BW including the single NB and the one or more additional NBs identified in the scheduling information to communicate with The base station communication. As the device described in item 15 of the scope of patent application, the row The process information enables the UE to operate in aggregate BW mode. A non-transitory computer-readable medium having instructions stored thereon that, when executed by a computing device, causes the computing device to: operate in a single narrowband (NB) mode, where the device only supports Communicate on a single NB, where the single NB is included in a plurality of NBs within the system bandwidth (BW); determine to switch from the single NB mode to the aggregate BW mode; switch from the single NB mode to the aggregate BW mode, wherein The device supports communication on more than the single NB in the aggregate BW mode; and uses aggregate BW to communicate with an evolved node B (eNB). The aggregate BW includes the single NB and the second NB of the plurality of NBs. At least part of it. For example, the computer-readable medium described in claim 17, wherein the instructions further enable the computing device to: receive configuration information from the eNB, and determine whether to switch from the single NB mode to the aggregate BW mode, at least in part Ground based on the configuration information received from the eNB, where the configuration information is received in at least one of RRC messages, medium access control (MAC) control elements (CE), and downlink control information (DCI) messages , And the DCI message is received on the machine type communication (MTC) physical downlink control channel (M-PDCCH). Such as the computer-readable medium described in claim 17, wherein the instructions further enable the computing device to: Based on at least one of scheduling, expiration of timers, configuration information from the eNB, uplink buffer status, and switching from RRC connected mode to RRC idle mode, it is determined to switch from the aggregate BW mode to the Single NB mode; and switching from the aggregate BW mode to the single NB mode. For example, the computer-readable medium described in claim 17, wherein the instructions further enable the computing device to: generate an aggregate BW configuration request for the eNB, and the aggregate BW configuration request requests the eNB to configure the The device can switch to the aggregate BW mode. The computer-readable medium described in claim 17, wherein the instructions further enable the computing device to: generate an indication of the status of the uplink buffer for the eNB, wherein it is determined to switch from the single NB mode The aggregate BW mode is based at least in part on the uplink buffer status, wherein the indication of the uplink buffer status includes a buffer status report (BSR). The computer-readable medium described in claim 17, wherein the instructions further enable the computing device to: obtain two or more unicast entity downlink shared channels when operating in the aggregate BW mode (PDSCH) Transmission block (TB).

Images