Patent Description:
Next generation wireless communication systems are expected to be a unified network/system that is targeted to meet vastly different and sometimes conflicting performance dimensions and services. New Radio Access Technology (RAT) is expected to support a broad range of use cases including Enhanced Mobile Broadband (eMBB), Massive Machine Type Communication (mMTC), Mission Critical Machine Type Communication (uMTC), and similar service types operating in frequency ranges up to <NUM>. Relevant prior at can be found in the <NPL>", and the <NPL>".

It will nevertheless be understood that no limitation of the scope of the technology is thereby intended.

Before the present technology is disclosed and described, it is to be understood that this technology is not limited to the particular structures, process actions, or materials disclosed herein, but is extended to equivalents thereof as would be recognized by those ordinarily skilled in the relevant arts. It should also be understood that terminology employed herein is used for the purpose of describing particular examples only and is not intended to be limiting. The same reference numerals in different drawings represent the same element. Numbers provided in flow charts and processes are provided for clarity in illustrating actions and operations and do not necessarily indicate a particular order or sequence.

The power consumption of radio frequency (RF) converters, analog to digital (A/D) converters, and digital to analog (D/A) converters, as well as the power consumption of the digital front end, can scale with the RF bandwidth. As the RF bandwidth increases, the power consumption can increase. In addition, the baseband power consumption can scale with the bit rate. As the bit rate increases, the baseband power consumption can increase.

In New Radio (NR) there is an increasing demand for wide bandwidth operation. For example, in <NUM> communications, the maximum bandwidth of a component carrier is <NUM> megahertz. In 3GPP <NUM> communications systems, each component carrier may have a much greater maximum bandwidth. For example, a component carrier may have a bandwidth of <NUM> megahertz (MHz), <NUM>, <NUM>, or more. A wide bandwidth, such as <NUM>, can result in high power consumption not only at high data rates, when the full bandwidth is being utilized, but also at low data rates or during idling because of the power consumption used in monitoring the wide RF bandwidth for control channel and data communications.

Therefore, it can be desirable to scale the operating bandwidth with the data rate. A high data rate can still utilize a high operating bandwidth, but a low data rate can utilize a low operating bandwidth. Having the operating bandwidth adjustment depend on the data rate can reduce the user equipment (UE) power consumption at low data rates or during idling.

One way of addressing this problem is by using a bandwidth part (BWP). When a BWP is configured for a UE, then the UE can transmit and receive data within the BWP without transmitting or receiving data outside of the configured frequency range. This can scale the operating bandwidth with the data rate which can reduce the UE power consumption at low data rates or during idling.

<FIG> provides an example of a 3GPP LTE Release <NUM> frame structure. In particular, <FIG> illustrates a downlink radio frame structure type <NUM>. In the example, a radio frame <NUM> of a signal used to transmit the data can be configured to have a duration, Tf, of <NUM> milliseconds (ms). Each radio frame can be segmented or divided into ten subframes 110i that are each <NUM> long. Each subframe can be further subdivided into two slots 120a and 120b, each with a duration, Tslot, of <NUM>. The first slot (#<NUM>) 120a can include a legacy physical downlink control channel (PDCCH) <NUM> and/or a physical downlink shared channel (PDSCH) <NUM>, and the second slot (#<NUM>) 120b can include data transmitted using the 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, <NUM>, and 130n based on the CC frequency bandwidth. The CC can have a carrier frequency having a bandwidth and center frequency. Each subframe of the CC can include downlink control information (DCI) found in the legacy PDCCH. The legacy PDCCH in the control region can include one to three columns of the first Orthogonal Frequency Division Multiplexing (OFDM) symbols in each subframe or RB, when a legacy PDCCH is used. The remaining <NUM> to <NUM> OFDM symbols (or <NUM> OFDM symbols, when legacy PDCCH is not used) in the subframe may be allocated to the PDSCH for data (for short or normal cyclic prefix).

The control region can include physical control format indicator channel (PCFICH), physical hybrid automatic repeat request (hybrid-ARQ) indicator channel (PHICH), and the PDCCH. The control region has a flexible control design to avoid unnecessary overhead. The number of OFDM symbols in the control region used for the PDCCH can be determined by the control channel format indicator (CFI) transmitted in the physical control format indicator channel (PCFICH). The PCFICH can be located in the first OFDM symbol of each subframe. The PCFICH and PHICH can have priority over the PDCCH, so the PCFICH and PHICH are scheduled prior to the PDCCH.

Each RB (physical RB or PRB) 130i can include <NUM> - <NUM> kilohertz (kHz) subcarriers <NUM> (on the frequency axis) and <NUM> or <NUM> orthogonal frequency-division multiplexing (OFDM) symbols <NUM> (on the time axis) per slot. The RB can use seven OFDM symbols if a short or normal cyclic prefix is employed. The RB can use six OFDM symbols if an extended cyclic prefix is used. The resource block can be mapped to <NUM> resource elements (REs) 140i using short or normal cyclic prefixing, or the resource block can be mapped to <NUM> REs (not shown) using extended cyclic prefixing. The RE can be a unit of one OFDM symbol <NUM> by one subcarrier (i.e., <NUM>) <NUM>.

Each RE can transmit two bits 150a and 150b of information in the case of quadrature phase-shift keying (QPSK) modulation. Other types of modulation may be used, such as <NUM> quadrature amplitude modulation (QAM) or <NUM> 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.

This example of the 3GPP LTE Release <NUM> frame structure provides examples of the way in which data is transmitted, or the transmission mode. The example is not intended to be limiting. Many of the Release <NUM> features will evolve and change in <NUM> frame structures included in 3GPP LTE Release <NUM>, MulteFire Release <NUM>, and beyond. In such a system, the design constraint can be on co-existence with multiple <NUM> numerologies in the same carrier due to the coexistence of different network services, such as eMBB (enhanced Mobile Broadband) <NUM>, mMTC (massive Machine Type Communications or massive IoT) <NUM> and URLLC (Ultra Reliable Low Latency Communications or Critical Communications) <NUM>. The carrier in a <NUM> system can be above or below <NUM>. In one embodiment, each network service can have a different numerology.

In another example, as illustrated in <FIG>, a BWP can be configured <NUM>. The BWP can be configured via a higher layer signal (e.g. a radio resource control (RRC) signal) that includes BWP configuration information for one or more of downlink (DL) or uplink (UL) BWP configurations. The numerology of the BWP can include subcarrier spacing and/or slot duration and/or a cyclic prefix (CP). The subcarrier spacing can be defined in relation to a base subcarrier spacing. For example, the base subcarrier spacing can be <NUM> kilohertz (kHz). The slot duration can indicate the duration of time for each slot in the time domain. The slot duration can depend on the <NUM> numerology being used, such as eMBB, mMTC, URLLC, or another desired numerology. The CP can be a normal cyclic prefix or an extended cyclic prefix. A normal CP can be supported for all numerologies and slot formats. An extended CP may only be supported for <NUM> subcarrier spacing.

In another example, the frequency location <NUM> of the BWP and the bandwidth <NUM> of the BWP can be indicated in various ways. In one example, the center frequency <NUM> of the BWP and the bandwidth <NUM> of the BWP can be indicated. The center frequency <NUM> of the BWP can be indicated as the absolute frequency of the center of the BWP. The frequency location <NUM> of the BWP and the bandwidth <NUM> of the BWP can be indicated via a higher layer signal (e.g. an RRC signal) that includes BWP configuration information for one or more of downlink (DL) or uplink (UL) BWP configurations.

Alternatively, in another example, the center frequency of the BWP <NUM> can be indicated as a relative offset <NUM> from the reference frequency <NUM> of the component carrier. The reference frequency <NUM> can be the center of the component carrier, a direct current (DC) subcarrier location, either of the edges of the component carrier, or any other predetermined location. The DC subcarrier location can be located somewhere other than the center of the component carrier. The offset can be indicated in units of physical resource blocks (PRBs) or in units of bandwidth, e.g. hertz (Hz). The offset can be indicated via a higher layer signal (e.g. an RRC signal) that includes BWP configuration information for one or more of downlink (DL) or uplink (UL) BWP configurations.

In another example, the bandwidth <NUM> of the BWP can be indicated in units of physical resource blocks (PRBs) or in units of bandwidth, e.g. hertz (Hz). In one example, there can be a minimum bandwidth that can be signaled. For example, the minimum bandwidth can be <NUM>, <NUM>, or another desired minimum bandwidth. The bandwidth <NUM> of the BWP in units of PRBs or in units of bandwidth can be indicated via a higher layer signal (e.g. an RRC signal) that includes BWP configuration information for one or more of downlink (DL) or uplink (UL) BWP configurations.

In another example, both edges of the BWP can be indicated. In this example, each of the edge frequencies can be indicated in various ways. In one example, the absolute frequency of the center of the BWP can be indicated. In another example, each of the edge frequencies can be indicated as the relative offset from the reference frequency. The reference frequency <NUM> can be the center of the component carrier, a DC subcarrier location, either of the edges of the component carrier, or any other predetermined location. Each of the edge frequencies can be indicated via a higher layer signal (e.g. an RRC signal) that includes BWP configuration information for one or more of downlink (DL) or uplink (UL) BWP configurations.

In another example, the numerology, frequency location, and bandwidth of the BWP can be configured by a higher layer signal, such as radio resource control (RRC) signaling. The RRC signaling can be either UE specific or cell specific.

In another example, a UE can encode one or more of data or control information, using BWP configuration information, for transmission to a gNB. In another example, a UE can decode one or more of data or control information, using BWP configuration information, received from a gNB.

In another example, a gNB can decode one or more of data or control information, using BWP configuration information, received from a UE. In another example, a gNB can encode one or more of data or control information, using BWP configuration information, for transmission to a UE.

In another example, the number of BWPs that can be configured for a particular UE can be limited to a certain number, i.e. N configurations. Therefore, the number of BWPs for each UE can have a maximum number of configurations. This maximum number, N, can be a positive integer. In one example, N can be <NUM>, <NUM>, <NUM>, or <NUM>. Using a maximum number of BWP configurations can ease the design of the bandwidth part switching command because the number of bits used for BWP indication can be fixed at a particular value.

In another example, the BWP can be commonly applied (or jointly configured) to both the downlink (DL) and uplink (UL) in the case of unpaired spectrum or time division duplex (TDD). The BWP can be separately applied (or separately configured) to both the DL and the UL in the case of paired spectrum or frequency division duplex (FDD). In some cases, the BWP can be separately applied (or separately configured) to both the DL and the UL in the case of unpaired spectrum or TDD.

In another example, as illustrated in <FIG>, different BWPs can have overlapping frequency ranges. The frequency ranges of the different BWPs can partially overlap or entirely overlap. BWP <NUM> has a bandwidth of <NUM> and includes a subset of the component carrier bandwidth <NUM>. BWP <NUM> has a bandwidth of <NUM> and includes a subset of the component carrier bandwidth <NUM>. BWP <NUM> has a bandwidth of <NUM> and includes a subset of the component carrier bandwidth <NUM>. The frequency range of BWP <NUM> overlaps with the frequency range of BWP <NUM> and BWP <NUM>. The frequency range of BWP <NUM> overlaps with the frequency range of BWP <NUM> and BWP <NUM>. The frequency range of BWP <NUM> overlaps with the frequency range of BWP <NUM> and BWP <NUM>.

In another example, it can be advantageous to configure overlapping BWPs as opposed to disjoint BWPs because of reduced signaling overhead. In the case of disjoint BWPs, activation signaling for multiple bandwidth parts can be used. In the case of overlapping BWPs, a wide BWP can be RRC configured and activated with a single indication.

One example, as illustrated in <FIG>, shows a BWP adaptation operation <NUM>. When carriers are aggregated, then each carrier can be referred to as a component carrier (CC). The CC bandwidth <NUM>, as shown in the frequency domain, can be large for wide bandwidth operation. The slot duration <NUM> can indicate the duration of time for each slot in the time domain. The BWP <NUM> can include a subset of the bandwidth of the CC bandwidth <NUM> and a subset of the slot duration <NUM>. A bandwidth part adaptation command <NUM> can switch the BWP from BWP <NUM> to BWP <NUM> as shown in operation <NUM>. BWP <NUM> can include a subset of the bandwidth of the CC bandwidth <NUM> and a subset of the slot duration <NUM>. In this example, there are two slot durations during which the BWP has not switched. After the BWP <NUM> has been switched to BWP <NUM> in operation <NUM>, then the BWP <NUM> can be switched back to include the same frequency and time resources occupied by BWP <NUM> as shown in operation <NUM>.

In another example, as illustrated in <FIG>, BWP switching can involve the processing time of a bandwidth part switching command, the settling time of the RF retuning, the A/D conversion time, the D/A conversion time, the time used for automatic gain control (AGC), and other factors. The total amount of time can depend on each UE implementation.

In another example, the supported switching time can be a UE capability and the UE can signal to the gNB the supported switching time. In the example of <FIG>, the amount of processing time is within a configured slot duration, i.e. the operation <NUM> can be processed within a configured slot duration.

In another example, as illustrated in <FIG>, the supported switching time can be within the duration of two slots but greater than one slot duration. <FIG> shows a BWP adaptation operation <NUM>. The CC bandwidth <NUM>, as shown in the frequency domain, can be large for wide bandwidth operation. The slot duration <NUM> can indicate the duration of time for each slot in the time domain. The BWP <NUM> can include a subset of the bandwidth of the CC bandwidth <NUM> and a subset of the slot duration <NUM>. A bandwidth part adaptation command <NUM> can switch the BWP from BWP <NUM> to BWP <NUM> as shown in operation <NUM>. Operation <NUM> can be within the duration of two slots but greater than one slot duration. BWP <NUM> can include a subset of the bandwidth of the CC bandwidth <NUM> and a subset of the slot duration <NUM>. In this example, there are two slot durations during which the BWP has not switched. After the BWP <NUM> has been switched to BWP <NUM> in operation <NUM>, then the BWP <NUM> can be switched back to include the same frequency and time resources occupied by BWP <NUM> as shown in operation <NUM>.

In one example, the switching time can be defined as the number of slots used for BWP switching. A UE can have a default switching time, which can be the UE capability signaled switching time. A UE can also be configured via RRC signaling about the default switching time. A UE can also be dynamically indicated about the switching time and/or the bandwidth part switching command.

In another example, as illustrated in <FIG>, a UE can miss a switching command <NUM>. When a UE misses the switching command <NUM>, the UE can still assume that the same BWP <NUM> is in use within the frequency resources indicated by <NUM>. Under these circumstances, the gNB might assume that the UE has switched to a different BWP within the frequency resources indicated by <NUM>. As a result, the UE might not be able to receive any control messages. Without being able to receive the proper control messages from the gNB, the UE might not be able to receive any data.

The problem that arises when the UE and gNB are not able to properly communicate control information and data because each of the UE and the gNB are configured to use different BWPs can be addressed in various ways. In one example, a default BWP can be configured to be communicated by the gNB. The default BWP can be communicated via a higher layer signal, such as a radio resource control (RRC) signal. In this example, a UE can be configured to switch to a default BWP after failing to receive a message for a certain period of time, e.g. x milliseconds or n slots, wherein x is a positive number and n is a positive integer.

The gNB can be configured to communicate a switching timer to the UE. The switching timer can be communicated via a higher layer signal, such as an RRC signal. The switching timer can indicate whether a UE can switch to a default BWP. The switching timer can be started at the UE when the UE switches to an active BWP that is not a default BWP. The switching timer can be restarted at the UE, when the UE successfully decodes control information. The control information can comprise downlink control information (DCI) used to schedule a physical downlink shared channel (PDSCH) in the active DL BWP. An active BWP can be a BWP that is one of N BWP configurations, wherein N is a positive integer. The default BWP can be a BWP that is one of the N BWP configurations. The switching timer can expire after a certain period of time, e.g. x milliseconds or n slots, wherein x is a positive number and n is a positive integer. This switching timer value can be a fixed value or the switching timer value can be indicated along with the switching command. After the expiration of the switching timer, the UE can switch to default BWP. By switching to a default BWP when the switching timer expires, the problem that arises when the UE and gNB might not be able to properly communicate control information and data because each of the UE and the gNB are configured to use different BWPs can be resolved.

In another example, the simultaneous activation of different BWPs might not be supported. In this example, for the N BWP configurations, there can be one active downlink (DL) BWP configuration and one active uplink (UL) BWP configuration.

In another example, the simultaneous activation of different BWPs can be supported. However, in this example, if the BWPs have different numerology attributes, i.e. different subcarrier spacing and/or slot duration, then simultaneous activation may not be supported.

In another example, known as explicit signaling, downlink control information (DCI) can be used to indicate to the UE which BWP to switch to. In another example, known as implicit signaling, if the scheduled physical downlink shared channel (PDSCH) is assigned outside of the active BWP, then the UE can switch to a BWP that contains the scheduled PDSCH.

Another example provides functionality <NUM> of a user equipment (UE) operable for bandwidth part (BWP) configuration, as shown in <FIG>. The UE can comprise one or more processors. The one or more processors can be configured to decode, at the UE, a radio resource control (RRC) signal including BWP configuration information for one or more of downlink (DL) or uplink (UL) BWP configurations, wherein the BWP configuration information comprises: subcarrier spacing for the BWP, and location and bandwidth of the BWP, as in block <NUM>. The one or more processors can be configured to encode, at the UE, one or more of data or control information, using the BWP configuration information, for transmission to a next generation node B (gNB), as in block <NUM>. The one or more processors can be configured to decode, at the UE, one or more of data or control information, using the BWP configuration information, received from the gNB, as in block <NUM>. In addition, the UE can comprise a memory interface configured to send the BWP configuration information to a memory.

Another example provides functionality <NUM> of a next generation node B (gNB) operable for bandwidth part (BWP) configuration, as shown in <FIG>. The gNB can comprise one or more processors. The one or more processors can be configured to encode, at the gNB, a radio resource control (RRC) signal including BWP configuration information for one or more of downlink (DL) or uplink (UL) BWP configurations, wherein the BWP configuration information comprises: subcarrier spacing for the BWP, and location and bandwidth of the BWP, as in block <NUM>. The one or more processors can be configured to decode, at the gNB, one or more of data or control information, using the BWP configuration information, received from a user equipment (UE), as in block <NUM>. The one or more processors can be configured to encode, at the gNB, one or more of data or control information, using the BWP configuration information, for transmission to the UE, as in block <NUM>. In addition, the gNB can comprise a memory interface configured to send the BWP configuration information to a memory.

Another example provides at least one machine readable storage medium having instructions <NUM> embodied thereon for performing bandwidth part (BWP) configuration, as shown in <FIG>. 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 perform: decoding, at the UE, a radio resource control (RRC) signal including BWP configuration information for one or more of downlink (DL) or uplink (UL) BWP configurations, wherein the BWP configuration information comprises: subcarrier spacing for the BWP, and location and bandwidth of the BWP, as in block <NUM>. The instructions when executed perform: encoding, at the UE, one or more of data or control information, using the BWP configuration information, for transmission to a next generation node B (gNB), as in block <NUM>. The instructions when executed perform: decoding, at the UE, one or more of data or control information, using the BWP configuration information, received from the gNB, as in block <NUM>.

Another example provides functionality <NUM> of a user equipment (UE) operable for bandwidth part (BWP) switching, as shown in <FIG>. The UE can comprise one or more processors. The one or more processors can be configured to decode BWP configuration information via a radio resource control (RRC) signal, wherein the BWP configuration information includes a timer value and N BWP configurations, wherein N is a positive integer, as in block <NUM>. The one or more processors can be configured to identify a default BWP from the N BWP configurations, as in block <NUM>. The one or more processors can be configured to identify the timer value used to switch a user equipment (UE) from one of the N BWP configurations to the default (DL) BWP, as in block <NUM>. In addition, the UE can comprise a memory interface configured to send the BWP configuration information to a memory.

Another example provides functionality <NUM> of a next generation node B (gNB) operable for bandwidth part (BWP) switching, as shown in <FIG>. The gNB can comprise one or more processors. The one or more processors can be configured to identify BWP configuration information, wherein the BWP configuration information includes N BWP configurations, wherein N is a positive integer, as in block <NUM>. The one or more processors can be configured to identify a default downlink (DL) BWP from the N BWP configurations, as in block <NUM>. The one or more processors can be configured to determine a timer value used to switch a user equipment (UE) to the default DL BWP, as in block <NUM>. The one or more processors can be configured to encode a radio resource control (RRC) signal including BWP configuration information for the N BWP configurations, wherein the configuration information includes the default DL BWP and the timer value for the UE to switch to the default BWP, as in block <NUM>. In addition, the gNB can comprise a memory interface configured to send the BWP configuration information to a memory.

Another example provides at least one machine readable storage medium having instructions <NUM> embodied thereon for performing bandwidth part (BWP) switching, as shown in <FIG>. 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 perform: decoding BWP configuration information via a radio resource control (RRC) signal, wherein the BWP configuration information includes N BWP configurations, wherein N is a positive integer, as in block <NUM>. The instructions when executed perform: identifying a default BWP from the N BWP configurations, as in block <NUM>. The instructions when executed perform: identifying a timer value used to switch a user equipment (UE) from one of the N BWP configurations to the default (DL) BWP, as in block <NUM>.

Another example provides functionality <NUM> of a next generation node B (gNB) operable for bandwidth part (BWP) operation, as shown in <FIG>. The gNB can comprise one or more processors. The one or more processors can be configured to select, at the gNB, a predetermined location and bandwidth of the BWP, as in block <NUM>. The one or more processors can be configured to identify a subcarrier spacing for a predetermined numerology configured to be used in the BWP, as in block <NUM>. The one or more processors can be configured to encode, at the gNB, one or more of data or control information, using the BWP with the selected location and bandwidth and the identified subcarrier spacing, for transmission to a user equipment (UE), as in block <NUM>. In addition, the gNB can comprise a memory interface configured to send the subcarrier spacing to a memory.

Another example provides functionality <NUM> of a user equipment (UE) operable for bandwidth part (BWP) operation, as shown in <FIG>. The UE can comprise one or more processors. The one or more processors can be configured to decode, at the UE, a predetermined location and bandwidth of the BWP, as in block <NUM>. The one or more processors can be configured to decode, at the UE, a subcarrier spacing for a predetermined numerology configured to be used in the BWP, as in block <NUM>. The one or more processors can be configured to encode, at the UE for transmission to a next generation node B (gNB), one or more of data or control information, using the BWP with the decoded location and bandwidth and the decoded subcarrier spacing, as in block <NUM>. In addition, the UE can comprise a memory interface configured to send the subcarrier spacing to a memory.

Another example provides at least one machine readable storage medium having instructions <NUM> embodied thereon for performing bandwidth part (BWP) operation, as shown in <FIG>. 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 perform: decoding, at the UE, a predetermined location and bandwidth of the BWP, as in block <NUM>. The instructions when executed perform: decoding, at the UE, a subcarrier spacing for a predetermined numerology configured to be used in the BWP, as in block <NUM>. The instructions when executed perform: encoding, at the UE for transmission to a next generation node B (gNB), one or more of data or control information, using the BWP with the decoded location and bandwidth and the decoded subcarrier spacing, as in block <NUM>.

While examples have been provided in which a gNB has been specified, they are not intended to be limiting. An evolved node B (eNodeB) can be used in place of the gNB. Accordingly, unless otherwise stated, any example herein in which a gNB has been disclosed, can similarly be disclosed with the use of an eNodeB.

<FIG> illustrates an architecture of a system <NUM> of a network in accordance with some embodiments. The system <NUM> is shown to include a user equipment (UE) <NUM> and a UE <NUM>. The UEs <NUM> and <NUM> are 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.

In some embodiments, any of the UEs <NUM> and <NUM> can comprise an Internet of Things (IoT) UE, which can comprise a network access layer designed for low-power IoT applications utilizing short-lived UE connections. An IoT UE can utilize technologies such as machine-to-machine (M2M) or machine-type communications (MTC) for exchanging data with an MTC server or device via a public land mobile network (PLMN), Proximity-Based Service (ProSe) or device-to-device (D2D) communication, sensor networks, or IoT networks. The M2M or MTC exchange of data may be a machine-initiated exchange of data. An IoT network describes interconnecting IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-lived connections. The IoT UEs may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate the connections of the IoT network.

The UEs <NUM> and <NUM> may be configured to connect, e.g., communicatively couple, with a radio access network (RAN) <NUM> - the RAN <NUM> may 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 UEs <NUM> and <NUM> utilize connections <NUM> and <NUM>, respectively, each of which comprises a physical communications interface or layer (discussed in further detail below); in this example, the connections <NUM> and <NUM> are 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 (<NUM>) protocol, a New Radio (NR) protocol, and the like.

Some embodiments may use concepts for resource allocation for control channel information that are an extension of the above-described concepts. For example, some embodiments may utilize an enhanced physical downlink control channel (EPDCCH) that uses PDSCH resources for control information transmission. The EPDCCH may be transmitted using one or more enhanced the control channel elements (ECCEs). Similar to above, each ECCE may correspond to nine sets of four physical resource elements known as an enhanced resource element groups (EREGs). An ECCE may have other numbers of EREGs in some situations.

The RAN <NUM> is shown to be communicatively coupled to a core network (CN) <NUM> -via an S1 interface <NUM>. In embodiments, the CN <NUM> may be an evolved packet core (EPC) network, a NextGen Packet Core (NPC) network, or some other type of CN. In this embodiment the S1 interface <NUM> is split into two parts: the S1-U interface <NUM>, which carries traffic data between the RAN nodes <NUM> and <NUM> and the serving gateway (S-GW) <NUM>, and the S1-mobility management entity (MME) interface <NUM>, which is a signaling interface between the RAN nodes <NUM> and <NUM> and MMEs <NUM>.

<FIG> illustrates example components of a device <NUM> in accordance with some embodiments. In some embodiments, the device <NUM> may include application circuitry <NUM>, baseband circuitry <NUM>, Radio Frequency (RF) circuitry <NUM>, front-end module (FEM) circuitry <NUM>, one or more antennas <NUM>, and power management circuitry (PMC) <NUM> coupled together at least as shown. The components of the illustrated device <NUM> may be included in a UE or a RAN node. In some embodiments, the device <NUM> may include less elements (e.g., a RAN node may not utilize application circuitry <NUM>, and instead include a processor/controller to process IP data received from an EPC). In some embodiments, the device <NUM> may 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 baseband circuitry <NUM> may include one or more baseband processors or control logic to process baseband signals received from a receive signal path of the RF circuitry <NUM> and to generate baseband signals for a transmit signal path of the RF circuitry <NUM>. Baseband processing circuity <NUM> may interface with the application circuitry <NUM> for generation and processing of the baseband signals and for controlling operations of the RF circuitry <NUM>. For example, in some embodiments, the baseband circuitry <NUM> may include a third generation (<NUM>) baseband processor 1004a, a fourth generation (<NUM>) baseband processor 1004b, a fifth generation (<NUM>) baseband processor 1004c, or other baseband processor(s) 1004d for other existing generations, generations in development or to be developed in the future (e.g., second generation (<NUM>), sixth generation (<NUM>), etc.). The baseband circuitry <NUM> (e.g., one or more of baseband processors 1004a-d) may handle various radio control functions that enable communication with one or more radio networks via the RF circuitry <NUM>. In other embodiments, some or all of the functionality of baseband processors 1004a-d may be included in modules stored in the memory <NUM> and executed via a Central Processing Unit (CPU) 1004e. 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 circuitry <NUM> may include Fast-Fourier Transform (FFT), precoding, or constellation mapping/demapping functionality. In some embodiments, encoding/decoding circuitry of the baseband circuitry <NUM> may 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 circuitry <NUM> may include one or more audio digital signal processor(s) (DSP) 1004f. The audio DSP(s) 1004f may 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 circuitry <NUM> and the application circuitry <NUM> may be implemented together such as, for example, on a system on a chip (SOC).

In some embodiments, the receive signal path of the RF circuitry <NUM> may include mixer circuitry 1006a, amplifier circuitry 1006b and filter circuitry 1006c. In some embodiments, the transmit signal path of the RF circuitry <NUM> may include filter circuitry 1006c and mixer circuitry 1006a. RF circuitry <NUM> may also include synthesizer circuitry 1006d for synthesizing a frequency for use by the mixer circuitry 1006a of the receive signal path and the transmit signal path. In some embodiments, the mixer circuitry 1006a of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry <NUM> based on the synthesized frequency provided by synthesizer circuitry 1006d. The amplifier circuitry 1006b may be configured to amplify the down-converted signals and the filter circuitry 1006c may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals. Output baseband signals may be provided to the baseband circuitry <NUM> for further processing. In some embodiments, the output baseband signals may be zero-frequency baseband signals, although this is not a necessity. In some embodiments, mixer circuitry 1006a of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.

In some embodiments, the mixer circuitry 1006a of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 1006d to generate RF output signals for the FEM circuitry <NUM>. The baseband signals may be provided by the baseband circuitry <NUM> and may be filtered by filter circuitry 1006c.

In some embodiments, the mixer circuitry 1006a of the receive signal path and the mixer circuitry 1006a of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and upconversion, respectively. In some embodiments, the mixer circuitry 1006a of the receive signal path and the mixer circuitry 1006a of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection). In some embodiments, the mixer circuitry 1006a of the receive signal path and the mixer circuitry 1006a may be arranged for direct downconversion and direct upconversion, respectively. In some embodiments, the mixer circuitry 1006a of the receive signal path and the mixer circuitry 1006a of the transmit signal path may be configured for super-heterodyne operation.

In some embodiments, the synthesizer circuitry 1006d may be a fractional-N synthesizer or a fractional N/N+<NUM> synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable. For example, synthesizer circuitry 1006d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.

The synthesizer circuitry 1006d may be configured to synthesize an output frequency for use by the mixer circuitry 1006a of the RF circuitry <NUM> based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry 1006d may be a fractional N/N+<NUM> synthesizer.

In some embodiments, frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a necessity.

Synthesizer circuitry 1006d of the RF circuitry <NUM> may include a divider, a delay-locked loop (DLL), a multiplexer and a phase accumulator. In some embodiments, the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by either N or N+<NUM> (e.g., based on a carry out) to provide a fractional division ratio. In some example embodiments, the DLL may include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop. In these embodiments, the delay elements may be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

In some embodiments, synthesizer circuitry 1006d may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other. In some embodiments, the output frequency may be a LO frequency (fLO). In some embodiments, the RF circuitry <NUM> may include an IQ/polar converter.

While <FIG> shows the PMC <NUM> coupled only with the baseband circuitry <NUM>. However, in other embodiments, the PMC <NUM> may be additionally or alternatively coupled with, and perform similar power management operations for, other components such as, but not limited to, application circuitry <NUM>, RF circuitry <NUM>, or FEM <NUM>.

If there is no data traffic activity for an extended period of time, then the device <NUM> may transition off to an RRC_Idle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc. The device <NUM> goes into a very low power state and it performs paging where again it periodically wakes up to listen to the network and then powers down again. The device <NUM> may not receive data in this state, in order to receive data, it can transition back to RRC _Connected state.

<FIG> illustrates example interfaces of baseband circuitry in accordance with some embodiments. As discussed above, the baseband circuitry <NUM> of <FIG> may comprise processors 1004a-1004e and a memory <NUM> utilized by said processors. Each of the processors 1004a-1004e may include a memory interface, 1104a-1104e, respectively, to send/receive data to/from the memory <NUM>.

<FIG> provides an example illustration of the wireless device, such as a user equipment (UE), a mobile station (MS), a mobile wireless device, a mobile communication device, a tablet, a handset, or other type of wireless device. The wireless device can include one or more antennas configured to communicate with a node, macro node, low power node (LPN), or, transmission station, such as a base station (BS), an evolved Node B (eNB), a baseband processing unit (BBU), a remote radio head (RRH), a remote radio equipment (RRE), a relay station (RS), a radio equipment (RE), or other type of wireless wide area network (WWAN) access point. The wireless device can be configured to communicate using at least one wireless communication standard such as, but not limited to, 3GPP LTE, WiMAX, High Speed Packet Access (HSPA), Bluetooth, and WiFi. The wireless device can communicate using separate antennas for each wireless communication standard or shared antennas for multiple wireless communication standards. The wireless device can communicate in a wireless local area network (WLAN), a wireless personal area network (WPAN), and/or a WWAN. The wireless device can also comprise a wireless modem. The wireless modem can comprise, for example, a wireless radio transceiver and baseband circuitry (e.g., a baseband processor). The wireless modem can, in one example, modulate signals that the wireless device transmits via the one or more antennas and demodulate signals that the wireless device receives via the one or more antennas.

<FIG> also 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.

Various techniques, or certain aspects or portions thereof, may take the form of program code (i.e., instructions) embodied in tangible media, such as floppy diskettes, compact disc-read-only memory (CD-ROMs), hard drives, non-transitory computer readable storage medium, or any other machine-readable storage medium wherein, when the program code is loaded into and executed by a machine, such as a computer, the machine becomes an apparatus for practicing the various techniques. In the case of program code execution on programmable computers, 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. The volatile and non-volatile memory and/or storage elements may be a random-access memory (RAM), erasable programmable read only memory (EPROM), flash drive, optical drive, magnetic hard drive, solid state drive, or other medium for storing electronic data. The node and wireless device may also include a transceiver module (i.e., transceiver), a counter module (i.e., counter), a processing module (i.e., processor), and/or a clock module (i.e., clock) or timer module (i.e., timer). In one example, selected components of the transceiver module can be located in a cloud radio access network (C-RAN). One or more programs that may implement or utilize the various techniques described herein may use an application programming interface (API), reusable controls, and the like. Such programs may be implemented in a high level procedural or object oriented programming language to communicate with a computer system. However, the program(s) may be implemented in assembly or machine language, if desired. In any case, the language may be a compiled or interpreted language, and combined with hardware implementations.

It should be understood that many of the functional units described in this specification have been labeled as modules, in order to more particularly emphasize their implementation independence. For example, a module may be implemented as a hardware circuit comprising custom very-large-scale integration (VLSI) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components.

Modules may also be implemented in software for execution by various types of processors. An identified module of executable code may, for instance, comprise one or more physical or logical blocks of computer instructions, which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module may not be physically located together, but may comprise disparate instructions stored in different locations which, when joined logically together, comprise the module and achieve the stated purpose for the module.

Indeed, a module of executable code may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices. The operational data may be collected as a single data set, or may be distributed over different locations including over different storage devices, and may exist, at least partially, merely as electronic signals on a system or network. The modules may be passive or active, including agents operable to perform desired functions.

Reference throughout this specification to "an example" or "exemplary" means that a particular feature, structure, or characteristic described in connection with the example is included in at least one embodiment of the present technology. Thus, appearances of the phrases "in an example" or the word "exemplary" in various places throughout this specification are not necessarily all referring to the same embodiment.

In addition, various embodiments and example of the present technology may be referred to herein along with alternatives for the various components thereof. It is understood that such embodiments, examples, and alternatives are not to be construed as defacto equivalents of one another, but are to be considered as separate and autonomous representations of the present technology.

In the following description, numerous specific details are provided, such as examples of layouts, distances, network examples, etc., to provide a thorough understanding of embodiments of the technology. One skilled in the relevant art will recognize, however, that the technology can be practiced without one or more of the specific details, or with other methods, components, layouts, etc. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the technology.

Claim 1:
An apparatus of a user equipment, UE, operable for bandwidth part, BWP, configuration, the apparatus comprising:
one or more processors configured to:
decode, at the UE, a radio resource control, RRC, signal including BWP configuration information for one or more of downlink, DL, or uplink, UL, BWP configurations, wherein the DL BWP configurations are configured separately from the UL BWP configurations, and wherein the BWP configuration information comprises:
subcarrier spacing for the BWP, and
location and bandwidth of the BWP,
encode, at the UE, one or more of data or control information, using the BWP configuration information, for transmission to a base station; and
decode, at the UE, one or more of data or control information, received from the base station, using the BWP configuration information; and
a memory interface configured to send the BWP configuration information to a memory.