Long term evolution (LTE) control region for downlink transmissions for enhanced machine type communications (eMTC)

Technology for an eNodeB operable to perform downlink (DL) transmissions using a Long Term Evolution (LTE) control region of a subframe for enhanced machine type communication (eMTC) is disclosed. The eNodeB can encode a system information block type 1 bandwidth reduced (SIB1-BR) for transmission 5 to a bandwidth reduced low complexity or coverage enhancement (BL/CE) user equipment (UE). The SIB1-BR can include an indication that the LTE control region in the subframe includes information for at least one of a machine type communication (MTC) physical downlink control channel (MPDCCH) transmission or a physical downlink shared channel (PDSCH) transmission. 10 The eNodeB can encode at least one of the MPDCCH transmission or the PDSCH transmission for delivery in a downlink over the LTE control region in the subframe to the BL/CE UE.

BACKGROUND

Wireless systems typically include multiple User Equipment (UE) devices communicatively coupled to one or more Base Stations (BS). The one or more BSs may be Long Term Evolved (LTE) evolved NodeBs (eNB) or New Radio (NR) next generation NodeBs (gNB) that can be communicatively coupled to one or more UEs by a Third-Generation Partnership Project (3GPP) network.

Reference will now be made to the exemplary embodiments illustrated, and specific language will be used herein to describe the same. It will nevertheless be understood that no limitation of the scope of the technology is thereby intended.

DETAILED DESCRIPTION

Definitions

As used herein, the term “User Equipment (UE)” refers to a computing device capable of wireless digital communication such as a smart phone, a tablet computing device, a laptop computer, a multimedia device such as an iPod Touch®, or other type computing device that provides text or voice communication. The term “User Equipment (UE)” may also be referred to as a “mobile device,” “wireless device,” of “wireless mobile device.”

As used herein, the term “Base Station (BS)” includes “Base Transceiver Stations (BTS),” “NodeBs,” “evolved NodeBs (eNodeB or eNB),” “New Radio Base Stations (NR BS)” and/or “next generation NodeBs (gNodeB or gNB),” and refers to a device or configured node of a mobile phone network that communicates wirelessly with UEs.

As used herein, the term “cellular telephone network,” “4G cellular,” “Long Term Evolved (LTE),” “5G cellular” and/or “New Radio (NR)” refers to wireless broadband technology developed by the Third Generation Partnership Project (3GPP).

EXAMPLE EMBODIMENTS

FIG.1provides an example of a 3GPP frame structure. In particular,FIG.1illustrates a downlink radio frame structure. In the example, a radio frame100of a signal used to transmit the data can be configured to have a duration, Tf, of 10 milliseconds (ms). Each radio frame can be segmented or divided into ten subframes110ithat are each 1 ms long. Each subframe can be further subdivided into one or multiple slots120a,120i, and120x, each with a duration, Tslot, of 1/μ ms, where μ=1 for 15 kHz subcarrier spacing, μ=2 for 30 kHz, μ=4 for 60 kHz, μ=8 for 120 kHz, and μ=16 for 240 kHz. Each slot can include a physical downlink control channel (PDCCH) and/or a physical downlink shared channel (PDSCH).

Each slot for a component carrier (CC) used by the node and the wireless device can include multiple resource blocks (RBs)130a,130b,130i,130m, and130nbased on the CC frequency bandwidth. The CC can have a carrier frequency having a bandwidth. Each slot of the CC can include downlink control information (DCI) found in the PDCCH. The PDCCH is transmitted in control channel resource set (CORESET) which can include one, two or three Orthogonal Frequency Division Multiplexing (OFDM) symbols and multiple RBs.

Each RB (physical RB or PRB) can include 12 subcarriers (on the frequency axis) and 14 orthogonal frequency-division multiplexing (OFDM) symbols (on the time axis) per slot. The RB can use 14 OFDM symbols if a short or normal cyclic prefix is employed. The RB can use 12 OFDM symbols if an extended cyclic prefix is used. The resource block can be mapped to 168 resource elements (REs) using short or normal cyclic prefixing, or the resource block can be mapped to 144 REs (not shown) using extended cyclic prefixing. The RE can be a unit of one OFDM symbol 142 by one subcarrier (i.e., 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz) 146.

Each RE140ican transmit two bits150aand150bof information in the case of quadrature phase-shift keying (QPSK) modulation. Other types of modulation may be used, such as 16 quadrature amplitude modulation (QAM) or 64 QAM to transmit a greater number of bits in each RE, or bi-phase shift keying (BPSK) modulation to transmit a lesser number of bits (a single bit) in each RE. The RB can be configured for a downlink transmission from the eNodeB to the UE, or the RB can be configured for an uplink transmission from the UE to the eNodeB.

In one configuration, a standalone deployment or standalone mode can be optimized for Release 16 enhanced MTC (eMTC). For example, LTE control region can be used for a downlink (DL) transmission, such as in an MTC physical downlink control channel (PDCCH) (MPDCCH) or a physical downlink shared channel (PDSCH), and the DL transmission can be to bandwidth reduced low complexity or coverage enhancement (BL/CE) UEs. This standalone deployment/mode can also be used to support legacy operations for legacy BL/CE UEs.

In one example, in the previous eMTC system, a starting symbol can be at least 1 when a number of DL physical resource blocks (PRBs) in the eMTC system is more than 10, and can be at least 2 when a number of DL PRBs in the eMTC system is less than or equal to 10. The symbols before the starting symbol for eMTC can be reserved for the LTE control channel region, for coexistence with LTE in-band operation. On the other hand, for the standalone deployment/mode, the symbols reserved for the LTE control channel region can be exploited to improve DL resource utilization.

In one configuration, a design to enable use of the LTE control channel region for MPDCCH and PDSCH transmission(s) is described herein. In other words, the LTE control region can be utilized for the MPDCCH and PDSCH transmission(s). The design described herein includes applicable cases for using the LTE control region, e.g., unicast and/or common MPDCCH/PDSCH transmissions. Further, a technique for configuring the LTE control region, and using the LTE control region for unicast/common MPDCCH/PDSCH transmissions are described in further detail below.

In one configuration, with respect to the applicable cases, use of the LTE control region can apply only to unicast MPDCCH/PDSCH. Alternatively, use of the LTE control region can apply to both unicast and common DL transmissions. The common DL transmission can include a physical broadcast channel (PBCH), system information block1bandwidth reduced (SIB1-BR), system information block X bandwidth reduced (SIBx-BR) with x>1, MPDCCH/PDSCH for random access response/message4(RAR/Msg4) and/or paging.

In one configuration, with respect to configuration and UE capability, for configuration of use of the LTE control region, system information such as a master information block (MIB), SIB1-BR or SIBx-BR (x>1) can indicate whether UEs are expected to receive a MPDCCH/PDSCH with a starting symbol equal to symbol #0 of a subframe. For example, one reserved bit in the MIB can be used to indicate use of the LTE control region, which can allow use of the LTE control region for a PDSCH carrying a SIB1-BR and/or a PDSCH carrying other SIBs (if supported) and/or a MPDCCH and PDSCH associated with paging and random access procedures, in addition to unicast DL transmission(s). As another example, the SIB1-BR can carry an indication of whether the LTE control region is used, which can allow use of the LTE control region for a PDSCH carrying a SIBx-BR with x>1 (if supported) and/or a MPDCCH and PDSCH associated with paging and random access procedures and unicast DL transmission(s).

In one example, use of the LTE control region (e.g., a starting symbol of symbol #0) can be configured by dedicated radio resource control (RRC) signaling, which can be used for unicast DL transmission.

In one example, with respect to UE capability, a UE supporting use of the LTE control region for DL transmission(s) can be defined as an optional UE capability. A configuration for use of the LTE control region can depend on the UE capability. In one example, a UE can report the capability to a network, similar to a legacy capability reporting mechanism.

Alternatively, physical random access channel (PRACH) partitioning can be used for UE capability reporting regarding the support of LTE control region utilization, which can be used to optimize the RAR/Msg4during the random access procedure.

In one configuration, with respect to use of the LTE control region for unicast MPDCCH/PDSCH transmission(s), for unicast MPDCCH/PDSCH transmission(s), rate matching can be used for the unicast MPDCCH/PDSCH when use of the LTE control region is enabled, where resource element (RE) mapping can take into account symbols in the LTE control region. The symbols among the first N symbols which carry a cell specific reference signal (CRS) in legacy systems can still carry the CRS on the same REs.

In one example, for unicast MPDCCH/PDSCH transmission(s), when use of the LTE control region is enabled, any N symbols (e.g., the first N symbols, or last N symbols, which can be defined in the 3GPP LTE specification) from the last 14-N symbols can be copied to the LTE control region, where N is the number of symbols in the LTE control region that corresponds to a minimum duration that is reserved for a legacy LTE PDCCH. In a specific example, N=1 for a DL system bandwidth (BW) greater than or equal to 10 PRBs, while N=2 for a DL system BW less than 10 PRBs. This approach can provide a realization of a lower code rate, as well as can enable frequency offset tracking using copies of two symbols. With respect to the frequency offset tracking using the copies of two symbols, in order to limit an amount of equivalent phase rotation caused by the frequency offset, the N symbols (which can be equal to 1 and 2, respectively) can be copied from symbol #1 to symbol #0, and from symbols {#2, #3} to symbols {#0, #1} for a DL system BW greater than or equal to 10 PRBs and less than 10 PRBs respectively.

In one example, for unicast MPDCCH/PDSCH transmission(s), when use of the LTE control region is enabled, the first N symbols can be used to carry reference signals, e.g., demodulation reference signals (DMRS) or CRS, or a new reference signal or preamble, which can improve a channel estimation performance, and can also benefit a frequency offset estimation for cases with N>1.

In one example, a frequency domain mapping of the DMRS/CRS can be the same as one of the symbols carrying a DMRS/CRS in a last 14-N symbols, and remaining REs can be left empty to facilitate possible power boosting. Further, in such cases, a relative DL power (such as an energy per resource element, or EPRE) for the DMRS/CRS REs within the first N symbols of the subframe to that for the DMRS/CRS REs in the last 14-N symbols of the subframe can be indicated to the UE. For example, the relative DL power can be indicated to the UE via a broadcast (SIB1-BR or other SI messages) or via UE-specific RRC signaling.

In an alternative example, all of the REs in the first N symbols can be used to carry the reference signals. For example, the DMRS/CRS can be repeated in a frequency domain, or alternatively, a new sequence can be defined to map to all REs within the first N symbols, with the exception of REs used for CRS transmission(s) that are still used for CRS transmissions, as in the legacy LTE DL control region. Whether to repeat the DMRS or CRS in remaining REs (other than the already-present CRS REs) of the first N symbols of the subframe can be implicitly linked to the RS associated with the transmission in the particular subframe, e.g., for the MPDCCH and PDSCH using a DMRS-based transmission scheme, a DMRS pattern can be repeated, while for a PDSCH using a CRS-based transmission scheme, CRS REs can be repeated in frequency.

In one configuration, with respect to use of the LTE control region for common MPDCCH/PDSCH transmission(s), a number of symbols in the LTE control region can be denoted as N. For common MPDCCH/PDSCH transmission(s), to keep backward compatibility, a transmission in the last 14-N symbols in the subframe can be kept the same.

In one example, for broadcast/common MPDCCH/PDSCH transmission(s), when use of the LTE control region is enabled, any N symbols (e.g., the first N symbols, or last N symbols, which can be defined in the 3GPP LTE specification) from the last 14-N symbols can be copied to the LTE control region, where N is the number of symbols in the LTE control region. In a specific example, N=1 for a DL system BW greater than or equal to 10 PRBs, while N=2 for a DL system BW less than 10 PRBs. This approach can provide a realization of a lower code rate, as well as can enable frequency offset tracking using copies of two symbols. With respect to the frequency offset tracking using the copies of two symbols, in order to limit an amount of equivalent phase rotation caused by the frequency offset, the N symbols (which can be equal to 1 and 2, respectively) can be copied from symbol #1 to symbol #0, and from symbols {#2, #3} to symbols {#0, #1} for a DL system BW greater than or equal to 10 PRBs and less than 10 PRBs respectively.

In an alternative example, for broadcast/common MPDCCH/PDSCH transmission(s), when use of the LTE control region is enabled, the first N symbols can be used to carry reference signals, e.g., DMRS/CRS, which can improve a channel estimation performance, and can also benefit a frequency offset estimation for cases with N>1.

In one example, a frequency domain mapping of a DMRS/CRS can be the same as one of the symbols carrying a DMRS/CRS in a last 14-N symbols, and remaining REs can be left empty to facilitate possible power boosting. Further, in such cases, a relative DL power (such as an EPRE) for the DMRS/CRS REs within the first N symbols of the subframe to that for DMRS/CRS REs in the last 14-N symbols of the subframe can be indicated to the UE via broadcast (SIB1-BR or other SI messages) or via UE-specific RRC signaling.

In an alternative example, all the REs in the first N symbols can be used to carry the reference signals. For example, the DMRS/CRS can be repeated in a frequency domain, or alternatively, a new sequence can be defined to map to all REs within the first N symbols, with the exception of the REs used for CRS transmission(s) that are still used for CRS transmissions, as in the legacy LTE DL control region. Whether to repeat DMRS or CRS in remaining REs (other than the already-present CRS REs) of the first N symbols of the subframe can be implicitly linked to the RS associated with the transmission in the particular subframe, e.g., for the MPDCCH and PDSCH using a DMRS-based transmission scheme, a DMRS pattern can be repeated, while for a PDSCH using a CRS-based transmission scheme, CRS REs can be repeated in frequency.

In one configuration, with respect to paging, UEs can be grouped such that UEs associated to a same paging occasion (PO) can include all the UEs supporting use of the LTE control region, when use of the LTE control region is enabled for the corresponding paging transmission. This approach can necessitate changes in a UE grouping for the PO, which can depend on a UE ID in current systems.

In one configuration, with respect to the RAR/Msg4, when a UE capability report, e.g., via PRACH partitioning, is supported such that a base station is aware of a UE capability before the RAR transmission, rate matching (similar to that used for unicast MPDCCH/PDSCH transmissions, as described above) can be applied, where an RE mapping can take into account the REs available in the first N symbols for the RAR/Msg4transmission. In addition, symbols among the first N symbols which carry a CRS in legacy systems can still carry the CRS on the same REs.

In one example, paging and random access related DL transmissions can be transmitted by transmitting copies of the first N of the set of last 14-N symbols in the subframe (e.g., symbols #1 or #2 and #3) in the first N symbols of the subframe. Alternatively, existing CRS REs or DMRS REs associated with MPDCCH CSS Types 1 or 2 can be copied in frequency to fill up the REs in the first N symbols of the subframe. However, for either option, the base station may not be aware of whether the UE is capable of utilizing the additional copies of OFDM symbols or CRS REs.

In one example, for a base station indicating use of an entire LTE DL control channel region (e.g., use of the first N symbols in a subframe), a current indication of the starting symbol for the MPDCCH and PDSCH can only indicate a starting symbol equal to symbol #1 for a system BW greater than or equal to 10 PRBs, and a starting symbol equal to symbol #2 for a DL system BW less than 10 PRBs.

In one configuration, a design of using an LTE control region for DL transmission(s) is described herein. In one example, system information such as a MIB, a SIB1-BR or a SIBx-BR (x>1) can be used to indicate whether UEs are expected to receive a MPDCCH/PDSCH with a starting symbol equal to symbol #0 of a subframe. In another example, use of the LTE control region (e.g., starting symbol of symbol #0) can be configured using dedicated RRC signaling.

In one example, for a unicast MPDCCH/PDSCH transmission, when use of the LTE control region is enabled, rate matching can be used for the unicast MPDCCH/PDSCH, where an RE mapping takes into account symbols in the LTE control region. In another example, for a unicast MPDCCH/PDSCH transmission, when use of the LTE control region is enabled, any N symbols (e.g., the first N symbols, or last N symbols) from the last 14-N symbols of a subframe can be copied to the LTE control region, where N is the number of symbols in the LTE control region that corresponds to a minimum duration that is reserved for a legacy LTE PDCCH. In a further example, for a unicast MPDCCH/PDSCH transmission, when use of LTE control region is enabled, the first N symbols can be used to carry reference signals, e.g., DMRS/CRS, or a new reference signal or preamble.

In one example, for a broadcast/common MPDCCH/PDSCH transmission, when use of the LTE control region is enabled, any N symbols (e.g., the first N symbols, or last N symbols) from the last 14-N symbols of a subframe can be copied to the LTE control region, where N is the number of symbols in the LTE control region that corresponds to a minimum duration that is reserved for a legacy LTE PDCCH. In another example, for a broadcast/common MPDCCH/PDSCH transmission, when use of the LTE control region is enabled, the first N symbols can be used to carry reference signals, e.g., DMRS/CRS, or a new reference signal or preamble.

FIG.2illustrates an example of signaling between a user equipment (UE)210and an eNodeB220for unicast machine type communication (MTC) physical downlink control channel (MPDCCH) and physical downlink shared channel (PDSCH) transmissions. The eNodeB220can perform DL transmissions using an LTE control region of a subframe for enhanced machine type communication (eMTC). For example, the UE210can transmit a UE capability message to the eNodeB220, wherein the capability message can indicate that the UE210is capable of receiving an MPDCCH/PDSCH transmission over the LTE control region in the subframe. Further, the eNodeB220can transmit a system information block type1bandwidth reduced (SIB1-BR) to the UE210, wherein the SIB1-BR can include an indication that the LTE control region in the subframe supports the MPDCCH/PDSCH transmission. Further, the eNodeB220can deliver the MPDCCH/PDSCH transmission, such as a unicast MPDCCH/PDSCH transmission in a downlink over the LTE control region in the subframe to the UE210.

FIG.3illustrates an example of signaling between multiple user equipment (UE) and an eNodeB340for common MPDCCH and PDSCH transmissions, where the multiple UEs include a first UE (UE1)310, a second UE (UE2)320and a third UE (UE3)330. The eNodeB340can perform DL transmissions using an LTE control region of a subframe for enhanced machine type communication (eMTC). For example, the multiple UEs310,320,330can transmit respective UE capability messages to the eNodeB340, wherein the capability message can indicate that the multiple UEs310,320,330are capable of receiving MPDCCH/PDSCH transmissions over the LTE control region in the subframe. Further, the eNodeB340can transmit a system information block type1bandwidth reduced (SIB1-BR) to the multiple UEs310,320,330, wherein the SIB1-BR can include an indication that the LTE control region in the subframe supports the MPDCCH/PDSCH transmission. Further, the eNodeB340can deliver the MPDCCH/PDSCH transmission, such as a common or broadcast MPDCCH/PDSCH transmission in a downlink over the LTE control region in the subframe to the multiple UEs310,320,330.

Another example provides functionality400of an eNodeB operable to perform downlink (DL) transmissions using a Long Term Evolution (LTE) control region of a subframe for enhanced machine type communication (eMTC), as shown inFIG.4. The eNodeB can comprise one or more processors configured to encode, at the eNodeB, a system information block type1bandwidth reduced (SIB1-BR) for transmission to an eMTC user equipment (UE), wherein the SIB1-BR includes an indication that the LTE control region in the subframe includes information for at least one of a machine type communication (MTC) physical downlink control channel (MPDCCH) transmission or a physical downlink shared channel (PDSCH) transmission, as in block410. The eNodeB can comprise one or more processors configured to encode, at the eNodeB, at least one of the MPDCCH transmission or the PDSCH transmission for delivery in a downlink over the LTE control region in the subframe to the eMTC UE, as in block420. In addition, the eNodeB can comprise a memory interface configured to retrieve from a memory the indication to be included in the SIB1-BR.

Another example provides functionality500of an enhanced machine type communication (eMTC) user equipment (UE) operable to decode downlink (DL) transmissions received from an eNodeB over a Long Term Evolution (LTE) control region of a subframe, as shown inFIG.5. The eMTC UE can comprise one or more processors configured to decode, at the eMTC UE, a system information block type1bandwidth reduced (SIB1-BR) received from the eNodeB, wherein the SIB1-BR includes an indication that the LTE control region in the subframe includes information for at least one of a machine type communication (MTC) physical downlink control channel (MPDCCH) transmission or a physical downlink shared channel (PDSCH) transmission, as in block510. The eMTC UE can comprise one or more processors configured to decode, at the eMTC UE, at least one of the MPDCCH transmission or the PDSCH transmission received from the eNodeB in a downlink over the LTE control region in the subframe, as in block520. In addition, the eMTC UE can comprise a memory interface configured to send to a memory the indication in the SIB1-BR.

Another example provides at least one machine readable storage medium having instructions600embodied thereon for performing downlink (DL) transmissions using a Long Term Evolution (LTE) control region of a subframe for enhanced machine type communication (eMTC), as shown inFIG.6. The instructions can be executed on a machine, where the instructions are included on at least one computer readable medium or one non-transitory machine readable storage medium. The instructions when executed by one or more processors of an eNodeB perform: encoding, at the eNodeB, a system information block type1bandwidth reduced (SIB1-BR) for transmission to an eMTC user equipment (UE), wherein the SIB1-BR includes an indication that the LTE control region in the subframe includes information for at least one of a machine type communication (MTC) physical downlink control channel (MPDCCH) transmission or a physical downlink shared channel (PDSCH) transmission, as in block610. The instructions when executed by one or more processors of the eNodeB perform: encoding, at the eNodeB, at least one of the MPDCCH transmission or the PDSCH transmission for delivery in a downlink over the LTE control region in the subframe to the eMTC UE, as in block620.

FIG.7illustrates an architecture of a system700of a network in accordance with some embodiments. The system700is shown to include a user equipment (UE)701and a UE702. The UEs701and702are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks), but may also comprise any mobile or non-mobile computing device, such as Personal Data Assistants (PDAs), pagers, laptop computers, desktop computers, wireless handsets, or any computing device including a wireless communications interface.

The UEs701and702may be configured to connect, e.g., communicatively couple, with a radio access network (RAN)710—the RAN710may be, for example, an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), a NextGen RAN (NG RAN), or some other type of RAN. The UEs701and702utilize connections703and704, respectively, each of which comprises a physical communications interface or layer (discussed in further detail below); in this example, the connections703and704are illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols, such as a Global System for Mobile Communications (GSM) protocol, a code-division multiple access (CDMA) network protocol, a Push-to-Talk (PTT) protocol, a PTT over Cellular (POC) protocol, a Universal Mobile Telecommunications System (UMTS) protocol, a 3GPP Long Term Evolution (LTE) protocol, a fifth generation (5G) protocol, a New Radio (NR) protocol, and the like.

In this embodiment, the UEs701and702may further directly exchange communication data via a ProSe interface705. The ProSe interface705may alternatively be referred to as a sidelink interface comprising one or more logical channels, including but not limited to a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Discovery Channel (PSDCH), and a Physical Sidelink Broadcast Channel (PSBCH).

The UE702is shown to be configured to access an access point (AP)706via connection707. The connection707can comprise a local wireless connection, such as a connection consistent with any IEEE 802.15 protocol, wherein the AP706would comprise a wireless fidelity (WiFi®) router. In this example, the AP706is shown to be connected to the Internet without connecting to the core network of the wireless system (described in further detail below).

The RAN710can include one or more access nodes that enable the connections703and704. These access nodes (ANs) can be referred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs), next Generation NodeBs (gNB), RAN nodes, and so forth, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell). The RAN710may include one or more RAN nodes for providing macrocells, e.g., macro RAN node711, and one or more RAN nodes for providing femtocells or picocells (e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells), e.g., low power (LP) RAN node712.

Any of the RAN nodes711and712can terminate the air interface protocol and can be the first point of contact for the UEs701and702. In some embodiments, any of the RAN nodes711and712can fulfill various logical functions for the RAN710including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.

In accordance with some embodiments, the UEs701and702can be configured to communicate using Orthogonal Frequency-Division Multiplexing (OFDM) communication signals with each other or with any of the RAN nodes711and712over a multicarrier communication channel in accordance various communication techniques, such as, but not limited to, an Orthogonal Frequency-Division Multiple Access (OFDMA) communication technique (e.g., for downlink communications) or a Single Carrier Frequency Division Multiple Access (SC-FDMA) communication technique (e.g., for uplink and ProSe or sidelink communications), although the scope of the embodiments is not limited in this respect. The OFDM signals can comprise a plurality of orthogonal subcarriers.

The physical downlink shared channel (PDSCH) may carry user data and higher-layer signaling to the UEs701and702. The physical downlink control channel (PDCCH) may carry information about the transport format and resource allocations related to the PDSCH channel, among other things. It may also inform the UEs701and702about the transport format, resource allocation, and H-ARQ (Hybrid Automatic Repeat Request) information related to the uplink shared channel. Typically, downlink scheduling (assigning control and shared channel resource blocks to the UE702within a cell) may be performed at any of the RAN nodes711and712based on channel quality information fed back from any of the UEs701and702. The downlink resource assignment information may be sent on the PDCCH used for (e.g., assigned to) each of the UEs701and702.

The RAN710is shown to be communicatively coupled to a core network (CN)720—via an S1interface713. In embodiments, the CN720may be an evolved packet core (EPC) network, a NextGen Packet Core (NPC) network, or some other type of CN. In this embodiment the S1interface713is split into two parts: the S1-U interface714, which carries traffic data between the RAN nodes711and712and the serving gateway (S-GW)722, and the S1-mobility management entity (MME) interface715, which is a signaling interface between the RAN nodes711and712and MMEs721.

In this embodiment, the CN720comprises the MMEs721, the S-GW722, the Packet Data Network (PDN) Gateway (P-GW)723, and a home subscriber server (HSS)724. The MMEs721may be similar in function to the control plane of legacy Serving General Packet Radio Service (GPRS) Support Nodes (SGSN). The MMEs721may manage mobility aspects in access such as gateway selection and tracking area list management. The HSS724may comprise a database for network users, including subscription-related information to support the network entities' handling of communication sessions. The CN720may comprise one or several HSSs724, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc. For example, the HSS724can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc.

The S-GW722may terminate the S1interface713towards the RAN710, and routes data packets between the RAN710and the CN720. In addition, the S-GW722may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.

The P-GW723may terminate an SGi interface toward a PDN. The P-GW723may route data packets between the EPC network and external networks such as a network including the application server730(alternatively referred to as application function (AF)) via an Internet Protocol (IP) interface725. Generally, the application server730may be an element offering applications that use IP bearer resources with the core network (e.g., UMTS Packet Services (PS) domain, LTE PS data services, etc.). In this embodiment, the P-GW723is shown to be communicatively coupled to an application server730via an IP communications interface725. The application server730can also be configured to support one or more communication services (e.g., Voice-over-Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UEs701and702via the CN720.

The P-GW723may further be a node for policy enforcement and charging data collection. Policy and Charging Enforcement Function (PCRF)726is the policy and charging control element of the CN720. In a non-roaming scenario, there may be a single PCRF in the Home Public Land Mobile Network (HPLMN) associated with a UE's Internet Protocol Connectivity Access Network (IP-CAN) session. In a roaming scenario with local breakout of traffic, there may be two PCRFs associated with a UE's IP-CAN session: a Home PCRF (H-PCRF) within a HPLMN and a Visited PCRF (V-PCRF) within a Visited Public Land Mobile Network (VPLMN). The PCRF726may be communicatively coupled to the application server730via the P-GW723. The application server730may signal the PCRF726to indicate a new service flow and select the appropriate Quality of Service (QoS) and charging parameters. The PCRF726may provision this rule into a Policy and Charging Enforcement Function (PCEF) (not shown) with the appropriate traffic flow template (TFT) and QoS class of identifier (QCI), which commences the QoS and charging as specified by the application server730.

FIG.8illustrates example components of a device800in accordance with some embodiments. In some embodiments, the device800may include application circuitry802, baseband circuitry804, Radio Frequency (RF) circuitry806, front-end module (FEM) circuitry808, one or more antennas810, and power management circuitry (PMC)812coupled together at least as shown. The components of the illustrated device800may be included in a UE or a RAN node. In some embodiments, the device800may include less elements (e.g., a RAN node may not utilize application circuitry802, and instead include a processor/controller to process IP data received from an EPC). In some embodiments, the device800may include additional elements such as, for example, memory/storage, display, camera, sensor, or input/output (I/O) interface. In other embodiments, the components described below may be included in more than one device (e.g., said circuitries may be separately included in more than one device for Cloud-RAN (C-RAN) implementations).

The application circuitry802may include one or more application processors. For example, the application circuitry802may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor(s) may include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.). The processors may be coupled with or may include memory/storage and may be configured to execute instructions stored in the memory/storage to enable various applications or operating systems to run on the device800. In some embodiments, processors of application circuitry802may process IP data packets received from an EPC.

The baseband circuitry804may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The baseband circuitry804may include one or more baseband processors or control logic to process baseband signals received from a receive signal path of the RF circuitry806and to generate baseband signals for a transmit signal path of the RF circuitry806. Baseband circuitry804may interface with the application circuitry802for generation and processing of the baseband signals and for controlling operations of the RF circuitry806. For example, in some embodiments, the baseband circuitry804may include a third generation (3G) baseband processor804a, a fourth generation (4G) baseband processor804b, a fifth generation (5G) baseband processor804c, or other baseband processor(s)804dfor other existing generations, generations in development or to be developed in the future (e.g., second generation (2G), sixth generation (6G), etc.). The baseband circuitry804(e.g., one or more of baseband processors804a-d) may handle various radio control functions that enable communication with one or more radio networks via the RF circuitry806. In other embodiments, some or all of the functionality of baseband processors804a-dmay be included in modules stored in the memory804gand executed via a Central Processing Unit (CPU)804e. The radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc. In some embodiments, modulation/demodulation circuitry of the baseband circuitry804may include Fast-Fourier Transform (FFT), precoding, or constellation mapping/demapping functionality. In some embodiments, encoding/decoding circuitry of the baseband circuitry804may include convolution, tail-biting convolution, turbo, Viterbi, or Low Density Parity Check (LDPC) encoder/decoder functionality. Embodiments of modulation/demodulation and encoder/decoder functionality are not limited to these examples and may include other suitable functionality in other embodiments.

In some embodiments, the baseband circuitry804may include one or more audio digital signal processor(s) (DSP)804f. The audio DSP(s)804fmay be include elements for compression/decompression and echo cancellation and may include other suitable processing elements in other embodiments. Components of the baseband circuitry may be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some embodiments. In some embodiments, some or all of the constituent components of the baseband circuitry804and the application circuitry802may be implemented together such as, for example, on a system on a chip (SOC).

In some embodiments, the mixer circuitry806aof the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry806dto generate RF output signals for the FEM circuitry808. The baseband signals may be provided by the baseband circuitry804and may be filtered by filter circuitry806c.

The synthesizer circuitry806dmay be configured to synthesize an output frequency for use by the mixer circuitry806aof the RF circuitry806based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry806dmay be a fractional N/N+1 synthesizer.

In some embodiments, frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a requirement. Divider control input may be provided by either the baseband circuitry804or the application circuitry802depending on the desired output frequency. In some embodiments, a divider control input (e.g., N) may be determined from a look-up table based on a channel indicated by the application circuitry802.

FEM circuitry808may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas810, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry806for further processing. FEM circuitry808may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry806for transmission by one or more of the one or more antennas810. In various embodiments, the amplification through the transmit or receive signal paths may be done solely in the RF circuitry806, solely in the FEM circuitry808, or in both the RF circuitry806and the FEM circuitry808.

In some embodiments, the FEM circuitry808may include a TX/RX switch to switch between transmit mode and receive mode operation. The FEM circuitry may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry may include an LNA to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry806). The transmit signal path of the FEM circuitry808may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry806), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas810).

In some embodiments, the PMC812may manage power provided to the baseband circuitry804. In particular, the PMC812may control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion. The PMC812may often be included when the device800is capable of being powered by a battery, for example, when the device is included in a UE. The PMC812may increase the power conversion efficiency while providing desirable implementation size and heat dissipation characteristics.

WhileFIG.8shows the PMC812coupled only with the baseband circuitry804. However, in other embodiments, the PMC812may be additionally or alternatively coupled with, and perform similar power management operations for, other components such as, but not limited to, application circuitry802, RF circuitry806, or FEM circuitry808.

In some embodiments, the PMC812may control, or otherwise be part of, various power saving mechanisms of the device800. For example, if the device800is in an RRC Connected state, where it is still connected to the RAN node as it expects to receive traffic shortly, then it may enter a state known as Discontinuous Reception Mode (DRX) after a period of inactivity. During this state, the device800may power down for brief intervals of time and thus save power.

FIG.9illustrates example interfaces of baseband circuitry in accordance with some embodiments. As discussed above, the baseband circuitry804ofFIG.8may comprise processors804a-804eand a memory804gutilized by said processors. Each of the processors804a-804emay include a memory interface,904a-904e, respectively, to send/receive data to/from the memory804g.

The baseband circuitry804may further include one or more interfaces to communicatively couple to other circuitries/devices, such as a memory interface912(e.g., an interface to send/receive data to/from memory external to the baseband circuitry804), an application circuitry interface914(e.g., an interface to send/receive data to/from the application circuitry802ofFIG.8), an RF circuitry interface916(e.g., an interface to send/receive data to/from RF circuitry806ofFIG.8), a wireless hardware connectivity interface918(e.g., an interface to send/receive data to/from Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components), and a power management interface920(e.g., an interface to send/receive power or control signals to/from the PMC812.

FIG.10also provides an illustration of a microphone and one or more speakers that can be used for audio input and output from the wireless device. The display screen can be a liquid crystal display (LCD) screen, or other type of display screen such as an organic light emitting diode (OLED) display. The display screen can be configured as a touch screen. The touch screen can use capacitive, resistive, or another type of touch screen technology. An application processor and a graphics processor can be coupled to internal memory to provide processing and display capabilities. A non-volatile memory port can also be used to provide data input/output options to a user. The non-volatile memory port can also be used to expand the memory capabilities of the wireless device. A keyboard can be integrated with the wireless device or wirelessly connected to the wireless device to provide additional user input. A virtual keyboard can also be provided using the touch screen.

EXAMPLES

The following examples pertain to specific technology embodiments and point out specific features, elements, or actions that can be used or otherwise combined in achieving such embodiments.

Example 1 includes an apparatus of an eNodeB operable to perform downlink (DL) transmissions using a Long Term Evolution (LTE) control region of a subframe for enhanced machine type communication (eMTC), the apparatus comprising: one or more processors configured to: encode, at the eNodeB, a system information block type1bandwidth reduced (SIB1-BR) for transmission to a bandwidth reduced low complexity or coverage enhancement (BL/CE) user equipment (UE), wherein the SIB1-BR includes an indication that the LTE control region in the subframe includes information for at least one of a machine type communication (MTC) physical downlink control channel (MPDCCH) transmission or a physical downlink shared channel (PDSCH) transmission; and encode, at the eNodeB, at least one of the MPDCCH transmission or the PDSCH transmission for delivery in a downlink over the LTE control region in the subframe to the BL/CE UE; and a memory interface configured to retrieve from a memory the indication to be included in the SIB1-BR.

Example 2 includes the apparatus of Example 1, further comprising a transceiver configured to: transmit the SIB1-BR including the indication to the BL/CE UE.

Example 3 includes the apparatus of any of Examples 1 to 2, wherein: the MPDCCH transmission includes a unicast MPDCCH transmission or a common MPDCCH transmission; and the PDSCH transmission includes a unicast PDSCH transmission or a common PDSCH transmission.

Example 4 includes the apparatus of any of Examples 1 to 3, wherein a first N symbols of the LTE control region in the subframe are used to carry a demodulation reference signal (DMRS) or a cell-specific reference signal (CRS), when the MPDCCH transmission or the PDSCH transmission is a unicast transmission and use of the LTE control region for at least one of the MPDCCH transmission or the PDSCH transmission is enabled, wherein a frequency domain mapping of the DMRS/CRS in the LTE control region of the subframe matches a frequency domain mapping of a DMRS/CRS in a last 14-N symbols of the subframe, wherein N is a positive integer and denotes a number of symbols in the LTE control region.

Example 5 includes the apparatus of any of Examples 1 to 4, wherein any consecutive N symbols from a last 14-N symbols of the subframe are copied to the LTE control region in the subframe, when the MPDCCH transmission or the PDSCH transmission is a common transmission and use of the LTE control region for at least one of the MPDCCH transmission or the PDSCH transmission is enabled.

Example 6 includes the apparatus of any of Examples 1 to 5, wherein the any consecutive N symbols include a first N symbols or a last N symbols from the last 14-N symbols of the subframe, wherein N is a positive integer and denotes a number of symbols in the LTE control region.

Example 7 includes the apparatus of any of Examples 1 to 6, wherein the one or more processors are further configured to decode a capability message received from the BL/CE UE, wherein the capability message indicates that the BL/CE UE is capable of receiving at least one of the MPDCCH transmission or the PDSCH transmission over the LTE control region in the subframe.

Example 8 includes the apparatus of any of Examples 1 to 7, wherein a starting symbol of at least one of the MPDCCH transmission or the PDSCH transmission in the subframe is symbol #0 in the subframe.

Example 9 includes an apparatus of a bandwidth reduced low complexity or coverage enhancement (BL/CE) user equipment (UE) operable to decode downlink (DL) transmissions received from an eNodeB over a Long Term Evolution (LTE) control region of a subframe, the apparatus comprising: one or more processors configured to: decode, at the BL/CE UE, a system information block type1bandwidth reduced (SIB1-BR) received from the eNodeB, wherein the SIB1-BR includes an indication that the LTE control region in the subframe includes information for at least one of a machine type communication (MTC) physical downlink control channel (MPDCCH) transmission or a physical downlink shared channel (PDSCH) transmission; and decode, at the BL/CE UE, at least one of the MPDCCH transmission or the PDSCH transmission received from the eNodeB in a downlink over the LTE control region in the subframe; and a memory interface configured to send to a memory the indication in the SIB1-BR.

Example 10 includes the apparatus of Example 9, wherein: the MPDCCH transmission includes a unicast MPDCCH transmission or a common MPDCCH transmission; and the PDSCH transmission includes a unicast PDSCH transmission or a common PDSCH transmission.

Example 11 includes the apparatus of any of Examples 9 to 10, wherein a first N symbols of the LTE control region in the subframe are used to carry a demodulation reference signal (DMRS) or a cell-specific reference signal (CRS), when the MPDCCH transmission or the PDSCH transmission is a unicast transmission and use of the LTE control region for at least one of the MPDCCH transmission or the PDSCH transmission is enabled, wherein a frequency domain mapping of the DMRS/CRS in the LTE control region of the subframe matches a frequency domain mapping of a DMRS/CRS in a last 14-N symbols of the subframe, wherein N is a positive integer and denotes a number of symbols in the LTE control region.

Example 12 includes the apparatus of any of Examples 9 to 11, wherein N symbols from a last 14-N symbols of the subframe are copied to the LTE control region in the subframe, when the MPDCCH transmission or the PDSCH transmission is a common transmission and use of the LTE control region for at least one of the MPDCCH transmission or the PDSCH transmission is enabled.

Example 13 includes the apparatus of any of Examples 9 to 12, wherein the one or more processors are further configured to encode a capability message for transmission to the eNodeB, wherein the capability message indicates that the BL/CE UE is capable of receiving at least one of the MPDCCH transmission or the PDSCH transmission over the LTE control region in the subframe.

Example 14 includes the apparatus of any of Examples 9 to 13, wherein a starting symbol of at least one of the MPDCCH transmission or the PDSCH transmission in the subframe is symbol #0 in the subframe.

Example 15 includes at least one machine readable storage medium having instructions embodied thereon for performing downlink (DL) transmissions using a Long Term Evolution (LTE) control region of a subframe for enhanced machine type communication (eMTC), the instructions when executed by one or more processors at an eNodeB perform the following: encoding, at the eNodeB, a system information block type1bandwidth reduced (SIB1-BR) for transmission to a bandwidth reduced low complexity or coverage enhancement (BL/CE) user equipment (UE), wherein the SIB1-BR includes an indication that the LTE control region in the subframe includes information for at least one of a machine type communication (MTC) physical downlink control channel (MPDCCH) transmission or a physical downlink shared channel (PDSCH) transmission; and encoding, at the eNodeB, at least one of the MPDCCH transmission or the PDSCH transmission for delivery in a downlink over the LTE control region in the subframe to the BL/CE UE.

Example 16 includes the at least one machine readable storage medium of Example 15, wherein: the MPDCCH transmission includes a unicast MPDCCH transmission or a common MPDCCH transmission; and the PDSCH transmission includes a unicast PDSCH transmission or a common PDSCH transmission.

Example 17 includes the at least one machine readable storage medium of any of Examples 15 to 16, wherein a first N symbols of the LTE control region in the subframe are used to carry a demodulation reference signal (DMRS) or a cell-specific reference signal (CRS), when the MPDCCH transmission or the PDSCH transmission is a unicast transmission and use of the LTE control region for at least one of the MPDCCH transmission or the PDSCH transmission is enabled, wherein a frequency domain mapping of the DMRS/CRS in the LTE control region of the subframe matches a frequency domain mapping of a DMRS/CRS in a last 14-N symbols of the subframe, wherein N is a positive integer and denotes a number of symbols in the LTE control region.

Example 18 includes the at least one machine readable storage medium of any of Examples 15 to 17, wherein N symbols from a last 14-N symbols of the subframe are copied to the LTE control region in the subframe, when the MPDCCH transmission or the PDSCH transmission is a common transmission and use of the LTE control region for at least one of the MPDCCH transmission or the PDSCH transmission is enabled, wherein the N symbols include a first N symbols or a last N symbols from the last 14-N symbols of the subframe, wherein N is a positive integer and denotes a number of symbols in the LTE control region.

Example 19 includes the at least one machine readable storage medium of any of Examples 15 to 18, further comprising instructions when executed perform the following: decoding a capability message received from the BL/CE UE, wherein the capability message indicates that the BL/CE UE is capable of receiving at least one of the MPDCCH transmission or the PDSCH transmission over the LTE control region in the subframe.

Example 20 includes the at least one machine readable storage medium of any of Examples 15 to 19, wherein a starting symbol of at least one of the MPDCCH transmission or the PDSCH transmission in the subframe is symbol #0 in the subframe.