Bandwidth fraction configuration and operation for New Radio (NR) broadband user equipment (UE)

Abstract

The present disclosure relates to bandwidth part configuration and operation for New Radio (NR) broadband user equipment (UE). Techniques for user equipment (UE) operable for bandwidth part (BWP) configuration are disclosed. The UE may decode a radio resource control (RRC) signal including BWP configuration information for one or more downlink (DL) or uplink (UL) BWP configurations, where the BWP configuration information includes: subcarrier spacing of the BWP, and the location and bandwidth of the BWP. The UE may utilize the BWP configuration information to encode one or more items of data or control information for transmission to a next-generation Node B (gNB). The UE may utilize the BWP configuration information to decode one or more items of data or control information received from the gNB.

Description

[0001] Related application citations

[0002] This application is a divisional application of the invention patent application with international application number PCT / US2018 / 031251, international application date May 4, 2018, entry into the Chinese national phase date November 5, 2019, Chinese national application number 201880029948.6, and invention name “Bandwidth Partial Configuration and Operation for New Radio (NR) Broadband User Equipment (UE)”. Technical Field

[0003] The present application relates to the field of communications. Background Art

[0004] A wireless system typically includes multiple user equipment (UE) devices communicatively coupled to one or more base stations (BSs). The one or more BSs may be Long Term Evolved (LTE) evolved NodeBs (eNBs) or New Radio (NR) NodeBs (gNBs) or next generation NodeBs (gNBs) capable of communicatively coupling to one or more UEs over a Third-Generation Partnership Project (3GPP) network.

[0005] The next generation of wireless communication systems is expected to be a unified network / system that targets very different and sometimes conflicting performance dimensions and services. New Radio Access Technology (RAT) is expected to support a wide 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 100 GHz. BRIEF DESCRIPTION OF THE DRAWINGS

[0006] By combining the following Figure 1 The features and advantages of the present disclosure will become apparent from the following detailed description which illustrates, by way of example, the features of the present disclosure; in the accompanying drawings:

[0007] Figure 1illustrates a block diagram of an Orthogonal Frequency Division Multiple Access (OFDMA) frame structure according to an example;

[0008] Figure 2 illustrates a bandwidth part (BWP) configuration according to an example;

[0009] Figure 3 illustrates an overlapping bandwidth part (BWP) configuration according to an example;

[0010] Figure 4a illustrates a bandwidth part (BWP) adaptation operation according to an example;

[0011] Figure 4b illustrates bandwidth part (BWP) switching time according to an example;

[0012] Figure 5 illustrates a missed bandwidth part (BWP) handover command according to an example;

[0013] Figure 6a Depicting functionality of a user equipment (UE) operable for bandwidth part (BWP) configuration according to an example;

[0014] Figure 6b Depicting functionality of a next generation Node B (gNB) operable for bandwidth part (BWP) configuration according to an example;

[0015] Figure 6c depicts a flow diagram of a machine-readable storage medium having embodied thereon instructions for performing bandwidth part (BWP) configuration according to an example;

[0016] Figure 7a Depicting functionality of a user equipment (UE) operable for bandwidth part (BWP) handover according to an example;

[0017] Figure 7b Depicting functionality of a next generation Node B (gNB) operable for bandwidth part (BWP) handover according to an example;

[0018] Figure 7c depicts a flow diagram of a machine-readable storage medium having embodied thereon instructions for performing bandwidth part (BWP) switching according to an example;

[0019] Figure 8a Depicting functionality of a next generation Node B (gNB) operable for bandwidth part (BWP) operation according to an example;

[0020] Figure 8b Depicting functionality of a user equipment (UE) operable for bandwidth part (BWP) operation according to an example;

[0021] Figure 8c depicts a flow diagram of a machine-readable storage medium having instructions embodied thereon for performing bandwidth part (BWP) operations according to an example;

[0022] Figure 9 illustrates an architecture of a wireless network according to an example;

[0023] Figure 10 A diagram illustrating a wireless device (e.g., UE) according to an example is illustrated;

[0024] Figure 11 illustrates an interface of a baseband circuit according to an example; and

[0025] Figure 12 A diagram of a wireless device (eg, UE) according to an example is illustrated.

[0026] Reference will now be made to the exemplary embodiments illustrated, and specific language will be used herein to describe the same. However, it will be understood that this is not intended to limit the scope of the technology. DETAILED DESCRIPTION

[0027] Before disclosing and describing the present technology, it is to be understood that the present technology is not limited to the specific structures, process actions, or materials disclosed herein, but extends to equivalents thereof that would be recognized by persons of ordinary skill in the relevant art. It should also be understood that the terminology employed herein is used to describe specific examples only and is not intended to be limiting. The same reference numerals in different figures represent the same elements. The numbers provided in the flow charts and processes are provided for clarity of illustration of the actions and operations and do not necessarily indicate a particular order or sequence.

[0028] Example Embodiments

[0029] The following provides an initial overview of the technology embodiments, followed by a more detailed description of specific technology embodiments. This initial overview is intended to help readers more quickly understand the technology, but is not intended to identify the key features or essential features of the technology, nor is it intended to limit the scope of the claimed subject matter.

[0030] The power consumption of the radio frequency (RF) converter, analog-to-digital (A / D) converter, and digital-to-analog (D / A) converter, 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. Furthermore, baseband power consumption can scale with the bit rate. As the bit rate increases, the baseband power consumption can increase.

[0031] In New Radio (NR), there is an increasing demand for wide bandwidth operation. For example, in 4G communications, the maximum bandwidth of a component carrier is 20 MHz. In 3GPP 5G communication systems, each component carrier may have a much larger maximum bandwidth. For example, a component carrier may have a bandwidth of 100 MHz, 200 MHz, 400 MHz, or more. A wide bandwidth such as 400 MHz may not only result in high power consumption at high data rates when the entire bandwidth is utilized, but also may result in high power consumption at low data rates or during idle periods due to the power consumption used to monitor the wide RF bandwidth for control channels and data communications.

[0032] Therefore, it may be desirable to scale the operating bandwidth with the data rate. High data rates can still utilize a high operating bandwidth, but low data rates can utilize a low operating bandwidth. Making the operating bandwidth adjustment dependent on the data rate can reduce user equipment (UE) power consumption at low data rates or during idle periods.

[0033] One way to address this problem is to use bandwidth parts (BWPs). When a UE is configured with a BWP, it can send and receive data within that BWP and not outside the configured frequency range. This allows the operating bandwidth to scale with the data rate, which can reduce UE power consumption at low data rates or during idle periods.

[0034] Figure 1 An example of a 3GPP LTE Release 8 frame structure is provided. Specifically, Figure 1 A downlink radio frame structure type 2 is shown. In this example, a radio frame 100 for transmitting a signal for data may be configured to have a duration T of 10 milliseconds (ms). f Each radio frame can be divided or partitioned into ten subframes, each subframe is 1 ms long. Each subframe can be further subdivided into two time slots 120a and 120b, each time slot has a duration T of 0.5 ms. slot The first time slot (#0) 120a may include a conventional physical downlink control channel (PDCCH) and / or a physical downlink shared channel (PDSCH), and the second time slot (#1) 120b may include data transmitted using the PDSCH.

[0035] Each time slot of a component carrier (CC) used by nodes and wireless devices may include multiple resource blocks (RBs) 130a, 130b, 130i, 130m, and 130n based on the CC frequency bandwidth. The CCC may have a carrier frequency having a bandwidth and a center frequency. Each subframe of the CC may include downlink control information (DCI) present in a traditional PDCCH. When traditional PDCCH is used, the traditional PDCCH in the control region may include one to three columns of the first orthogonal frequency division multiplexing (OFDM) symbol in each subframe or RB. The remaining 11 to 13 OFDM symbols in the subframe (or 14 OFDM symbols when traditional PDCCH is not used) may be allocated to PDSCH for data (for short or normal cyclic prefix).

[0036] The control region may include a physical control format indicator channel (PCFICH), a physical hybrid-ARQ indicator channel (PHICH), and a PDCCH. The control region may have a flexible control design to avoid unnecessary overhead. The number of OFDM symbols used for PDCCH in the control region may be determined by a control channel format indicator (CFI) sent in a physical control format indicator channel (PCFICH). The PCFICH may be located in the first OFDM symbol of each subframe. The PCFICH and PHICH may have a higher priority than the PDCCH, so the PCFICH and PHICH are scheduled before the PDCCH.

[0037] Each RB (physical RB or PRB) 130i may include 12-15 kilohertz (kHz) subcarriers 136 (on the frequency axis) and 6 or 7 orthogonal frequency division multiplexing (OFDM) symbols 132 (on the time axis) per time slot. If a short or normal cyclic prefix is ​​used, the RB may use seven OFDM symbols. If an extended cyclic prefix is ​​used, the RB may use six OFDM symbols. A resource block may be mapped to 84 resource elements (REs) 140i using a short or normal cyclic prefix, or to 72 REs (not shown) using an extended cyclic prefix. An RE may be a unit of one OFDM symbol 142 x one subcarrier (i.e., 15 kHz) 146.

[0038] Each RE can transmit two bits of information 150a and 150b using quadrature phase-shift keying (QPSK) modulation. Other types of modulation, such as 16-bit amplitude modulation (QAM) or 64-QAM, can be used to transmit a larger number of bits per RE, or bi-phase shift keying (BPSK) modulation can be used to transmit a smaller number of bits (a single bit) per RE. RBs can be configured for downlink transmissions from the eNodeB to the UE, or for uplink transmissions from the UE to the eNodeB.

[0039] This example of a 3GPP LTE Release 8 frame structure provides an example of a way to send data or a transmission mode. This example is not intended to be limiting. Many Release 8 features will evolve and change in the 5G frame structure included in 3GPP LTE Release 15, MulteFire Release 1.1 and later. In such a system, due to the coexistence of different network services, such as eMBB (enhanced mobile broadband), mMTC (massive machine type communication or massive IoT) and URLLC (ultra-reliable low latency communication or critical communication), design constraints may coexist with multiple 5G parameter sets (numerologies) in the same carrier. Carriers in a 5G system may be above or below 6 GHz. In one embodiment, each network service may have a different parameter set.

[0040] In another example, Figure 2 As shown in , a BWP may be configured 200. The BWP may be configured via a higher layer signal (e.g., a radio resource control (RRC) signal) including one or more BWP configuration information for a downlink (DL) or uplink (UL) BWP configuration. A parameter set for the BWP may include subcarrier spacing and / or slot duration and / or a cyclic prefix (CP). The subcarrier spacing may be defined relative to a basic subcarrier spacing. For example, the basic subcarrier spacing may be 15 kilohertz (kHz). The slot duration may indicate the duration of each slot in the time domain. The slot duration may depend on the 5G parameter set used, such as eMBB, mMTC, URLLC, or another desired parameter set. The CP may be a normal cyclic prefix or an extended cyclic prefix. Normal CP may be supported for all parameter sets and slot formats. Extended CP may only be supported for 60 kHz subcarrier spacing.

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

[0042] Alternatively, in another example, the center frequency 210 of the BWP can be indicated as a relative offset 208 from a reference frequency 206 of the component carrier. The reference frequency 206 can be the center of the component carrier, the direct current (DC) subcarrier position, any edge of the component carrier, or any other predetermined position. The DC subcarrier position 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 the downlink (DL) or uplink (UL) BWP configurations.

[0043] In another example, the bandwidth 204 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 may be a minimum bandwidth that can be signaled. For example, the minimum bandwidth may be 5 MHz, 1.4 MHz, or another desired minimum bandwidth. The bandwidth 204 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 one or more BWP configuration information for a downlink (DL) or uplink (UL) BWP configuration.

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

[0045] In another example, the parameter set, frequency location and bandwidth of the BWP may be configured by higher layer signals, such as radio resource control (RRC) signaling. The RRC signaling may be UE-specific or cell-specific.

[0046] In another example, the UE may utilize the BWP configuration information to encode one or more of the data or control information for transmission to the gNB. In another example, the UE may utilize the BWP configuration information to decode one or more of the data or control information received from the gNB.

[0047] In another example, the gNB may utilize the BWP configuration information to decode one or more of the data or control information received from the UE. In another example, the gNB may utilize the BWP configuration information to encode one or more of the data or control information for transmission to the UE.

[0048] In another example, the number of configurable BWPs for a particular UE may be limited to a certain number, namely, N configurations. Therefore, the number of BWPs per UE may have a maximum number of configurations. This maximum number, N, may be a positive integer. In one example, N may be 2, 4, 8, or 16. Using a maximum number of BWP configurations can simplify the design of bandwidth part switching commands because the number of bits used for the BWP indication can be fixed to a specific value.

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

[0050] In another example, Figure 3As shown in FIG, different BWPs may have overlapping frequency ranges. The frequency ranges of different BWPs may partially overlap or completely overlap. BWP 310 has a bandwidth of 308 and includes a subset of component carrier bandwidth 302. BWP 312 has a bandwidth of 306 and includes a subset of component carrier bandwidth 302. BWP 314 has a bandwidth of 304 and includes a subset of component carrier bandwidth 302. The frequency range of BWP 310 overlaps with the frequency ranges of BWP 312 and BWP 314. The frequency range of BWP 312 overlaps with the frequency ranges of BWP 310 and BWP 314. The frequency range of BWP 314 overlaps with the frequency ranges of BWP 310 and BWP 312.

[0051] In another example, configuring overlapping BWPs rather than separate BWPs may be advantageous due to reduced signaling overhead. In the case of separate BWPs, activation signaling for multiple bandwidth portions may be used. In the case of overlapping BWPs, a wide BWP may be configured by RRC and activated with a single indication.

[0052] like Figure 4a An example is shown illustrating a BWP adaptation operation 400. When carriers are aggregated, each carrier may be referred to as a component carrier (CC). CC bandwidth 402, as shown in the frequency domain, may be larger for wide bandwidth operation. Slot duration 404 may indicate the duration of each slot in the time domain. BWP 406 may include a subset of the bandwidth of CC bandwidth 402 and a subset of slot duration 404. Bandwidth fraction adaptation command 410 may switch the BWP from BWP 406 to BWP 408, as shown in operation 412. BWP 408 may include a subset of the bandwidth of CC bandwidth 402 and a subset of slot duration 404. In this example, there are two slot durations during which the BWP is not switched. After BWP 406 is switched to BWP 408 in operation 412, BWP 408 may be switched back to the same frequency and time resources occupied by BWP 406, as shown in operation 414.

[0053] In another example, Figure 4b As shown in , BWP switching may involve processing time for bandwidth part switching commands, stabilization time for RF retuning, A / D conversion time, D / A conversion time, time for automatic gain control (AGC), and other factors. The total amount of time may depend on each UE implementation.

[0054] In another example, the supported switching time may be a UE capability and the UE may signal the supported switching time to the gNB. Figure 4aIn the example of , the amount of processing time is within the configured time slot duration, ie, operation 412 can be processed within the configured time slot duration.

[0055] In another example, Figure 4b As shown in , the supported switching time can be within the duration of two time slots, but greater than the duration of one time slot. Figure 4b BWP adaptation operation 450 is shown. CC bandwidth 452, as shown in the frequency domain, may be larger for wide bandwidth operation. Slot duration 454 may indicate the duration of each time slot in the time domain. BWP 456 may include a subset of the bandwidth of CC bandwidth 452 and a subset of slot duration 454. Bandwidth fraction adaptation command 460 may switch the BWP from BWP 456 to BWP 458, as shown in operation 462. Operation 462 may be within the duration of two time slots, but greater than one time slot duration. BWP 458 may include a subset of the bandwidth of CC bandwidth 452 and a subset of slot duration 454. In this example, there are two time slot durations during which the BWP is not switched. After BWP 456 is switched to BWP 458 in operation 462, BWP 458 may be switched back to the same frequency and time resources occupied by BWP 456, as shown in operation 464.

[0056] In one example, the switching time can be defined as the number of time slots used for BWP switching. The UE may have a default switching time, which may be a switching time signaled by the UE capability. The default switching time may also be configured via RRC signaling. The UE may also be dynamically instructed regarding the switching time and / or bandwidth fraction switching command.

[0057] In another example, Figure 5 As shown in FIG5 , the UE may miss the handover command 510. When the UE misses the handover command 510, the UE may still assume that the same BWP 512 is in use within the frequency resources indicated by 506. In these cases, the gNB may assume that the UE has switched to a different BWP within the frequency resources indicated by 508. As a result, the UE may not be able to receive any control messages. Without being able to receive appropriate control messages from the gNB, the UE may not be able to receive any data.

[0058] The problem that occurs when a UE and a gNB are unable to properly communicate control information and data because each is configured to use a different BWP 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 higher-layer signals such as radio resource control (RRC) signals. In this example, the UE can be configured to switch to the default BWP after failing to receive a message for a certain period of time, such as x milliseconds or n time slots, where x is a positive number and n is a positive integer.

[0059] The gNB can be configured to communicate a handover timer to the UE. This handover timer can be communicated via higher-layer signals such as RRC signals. The handover timer can indicate whether the UE can switch to the default BWP. The handover timer can be started at the UE when the UE switches to an active BWP that is not the default BWP. The handover timer can be restarted at the UE when the UE successfully decodes control information. The control information may include downlink control information (DCI) for scheduling the Physical Downlink Shared Channel (PDSCH) in the active DL BWP. The active BWP can be one of N BWP configurations, where N is a positive integer. The default BWP can be one of N BWP configurations. The handover timer can expire after a certain period of time, such as x milliseconds or n time slots, where x is a positive number and n is a positive integer. The handover timer value can be a fixed value or can be indicated with the handover command. After the handover timer expires, the UE can switch to the default BWP. By switching to the default BWP when the switching timer expires, a problem that occurs when the UE and the gNB may not be able to properly communicate data of control information because each of the UE and the gNB is configured to use a different BWP can be solved.

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

[0061] In another example, simultaneous activation of different BWPs may be supported. However, in this example, if the BWPs have different parameter set properties, i.e., different subcarrier spacing and / or time slot duration, simultaneous activation may not be supported.

[0062] In another example, known as explicit signaling, downlink control information (DCI) may be used to indicate to the UE which BWP to switch to. In another example, known as implicit signaling, if a scheduled physical downlink shared channel (PDSCH) is assigned outside of an active BWP, the UE may switch to the BWP containing the scheduled PDSCH.

[0063] Another example provides functionality 600 of a user equipment (UE) operable for bandwidth part (BWP) configuration, such as Figure 6a As shown in . The UE may include one or more processors. The one or more processors may be configured to decode, at the UE, a radio resource control (RRC) signal including BWP configuration information for one or more of a downlink (DL) or uplink (UL) BWP configuration, wherein the BWP configuration information includes: a subcarrier spacing of the BWP, and a location and bandwidth of the BWP, as shown in block 605. The one or more processors may be configured to encode, at the UE, one or more of data or control information for transmission to a next-generation Node B (gNB), using the BWP configuration information, as shown in block 610. The one or more processors may be configured to decode, at the UE, one or more of data or control information received from the gNB using the BWP configuration information, as shown in block 615. Furthermore, the UE may include a memory interface configured to send the BWP configuration information to a memory.

[0064] Another example provides functionality 620 of a next generation Node B (gNB) operable for bandwidth part (BWP) configuration, such as Figure 6b The gNB may include one or more processors. The one or more processors may be configured to encode, at the gNB, a radio resource control (RRC) signal including BWP configuration information for one or more of a downlink (DL) or uplink (UL) BWP configuration, wherein the BWP configuration information includes: a subcarrier spacing of the BWP, and a location and bandwidth of the BWP, as shown in block 625. The one or more processors may be configured to decode, at the gNB, one or more of data or control information received from a user equipment (UE) using the BWP configuration information, as shown in block 630. The one or more processors may be configured to encode, at the gNB, one or more of the data or control information using the BWP configuration information for transmission to the UE, as shown in block 635. Furthermore, the gNB may include a memory interface configured to send the BWP configuration information to a memory.

[0065] Another example provides at least one machine-readable storage medium having embodied thereon instructions 640 for performing bandwidth part (BWP) configuration, such as Figure 6c6. The instructions are executable on a machine, wherein the instructions are included on at least one computer-readable medium or a non-transitory machine-readable storage medium. When executed, the instructions perform: decoding, at a UE, a radio resource control (RRC) signal including BWP configuration information for one or more downlink (DL) or uplink (UL) BWP configurations, wherein the BWP configuration information includes: a subcarrier spacing of the BWP, and a location and bandwidth of the BWP, as shown in block 645. When executed, the instructions perform: encoding, at the UE, one or more of data or control information for transmission to a next-generation Node B (gNB) using the BWP configuration information, as shown in block 650. When executed, the instructions perform: decoding, at the UE, one or more of data or control information received from the gNB using the BWP configuration information, as shown in block 655.

[0066] Another example provides functionality 700 of a user equipment (UE) operable for bandwidth part (BWP) switching, such as Figure 7a As shown in . The UE may include one or more processors. The one or more processors may 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, where N is a positive integer, as shown in block 705. The one or more processors may be configured to identify a default BWP from the N BWP configurations, as shown in block 710. The one or more processors may be configured to identify a timer value for switching a user equipment (UE) from one of the N BWP configurations to a default (DL) BWP, as shown in block 715. In addition, the UE may include a memory interface configured to send the BWP configuration information to a memory.

[0067] Another example provides functionality 720 of a next generation Node B (gNB) operable for bandwidth part (BWP) switching, such as Figure 7bAs shown in . The gNB may include one or more processors. The one or more processors may be configured to identify BWP configuration information, wherein the BWP configuration information includes N BWP configurations, where N is a positive integer, as shown in block 725. The one or more processors may be configured to identify a default downlink (DL) BWP from the N BWP configurations, as shown in block 730. The one or more processors may be configured to determine a timer value for switching a user equipment (UE) to the default DL BWP, as shown in block 735. The one or more processors may 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 a timer value for the UE to switch to the default BWP, as shown in block 740. In addition, the gNB may include a memory interface configured to send the BWP configuration information to a memory.

[0068] Another example provides at least one machine-readable storage medium having embodied thereon instructions 750 for performing bandwidth part (BWP) switching, such as Figure 7c . These instructions may be executed on a machine, wherein the instructions are included on at least one computer-readable medium or a non-transitory machine-readable storage medium. When executed, these instructions perform: decoding BWP configuration information via a radio resource control (RRC) signal, wherein the BWP configuration information includes N BWP configurations, where N is a positive integer, as shown in block 755. When executed, these instructions perform: identifying a default BWP from the N BWP configurations, as shown in block 760. When executed, these instructions perform: identifying a timer value for switching a user equipment (UE) from one of the N BWP configurations to a default (DL) BWP, as shown in block 765.

[0069] Another example provides functionality 800 of a next generation Node B (gNB) operable for bandwidth part (BWP) operation, such as Figure 8a . The gNB may include one or more processors. The one or more processors may be configured to select, at the gNB, a predetermined location and bandwidth of a BWP, as shown in block 805. The one or more processors may be configured to identify a subcarrier spacing of a predetermined parameter set configured for use in the BWP, as shown in block 810. The one or more processors may be configured to encode, at the gNB, one or more of data or control information for transmission to a user equipment (UE) using the BWP having the selected location and bandwidth and the identified subcarrier spacing, as shown in block 815. Additionally, the gNB may include a memory interface configured to send the subcarrier spacing to a memory.

[0070] Another example provides functionality 820 of a user equipment (UE) operable for bandwidth part (BWP) operation, such as Figure 8b . The UE may include one or more processors. The one or more processors may be configured to decode, at the UE, a predetermined position and bandwidth of the BWP, as shown in block 825. The one or more processors may be configured to decode, at the UE, a subcarrier spacing of a predetermined parameter set configured for use in the BWP, as shown in block 830. The one or more processors may be configured to encode, at the UE, one or more of data or control information for transmission to a next generation Node B (gNB) using the BWP having the decoded position and bandwidth and the decoded subcarrier spacing, as shown in block 835. Furthermore, the UE may include a memory interface configured to send the subcarrier spacing to a memory.

[0071] Another example provides at least one machine-readable storage medium having embodied thereon instructions 840 for performing bandwidth part (BWP) operations, such as Figure 8c 845. The instructions, when executed, perform: decoding, at the UE, a predetermined position and bandwidth of the BWP, as shown in block 846. The instructions, when executed, perform: decoding, at the UE, a subcarrier spacing of a predetermined parameter set configured for use in the BWP, as shown in block 850. The instructions, when executed, perform: encoding, at the UE, one or more of data or control information for transmission to a next generation Node B (gNB) using the BWP having the decoded position and bandwidth and the decoded subcarrier spacing, as shown in block 855.

[0072] While examples are provided in which gNBs are specified, they are not intended to be limiting. An evolved NodeB (eNodeB) can be used in place of a gNB. Therefore, unless otherwise stated, any examples herein that disclose a gNB can be similarly disclosed using an eNodeB.

[0073] Figure 9 The architecture of a system 900 of a network according to some embodiments is illustrated. System 900 is shown as including user equipment (UE) 901 and UE 902. UE 901 and 902 are shown as smartphones (e.g., handheld touchscreen mobile computing devices that can connect to one or more cellular networks), but may also include any mobile or non-mobile computing device, such as a personal data assistant (PDA), a pager, a laptop computer, a desktop computer, a wireless handset, or any computing device that includes a wireless communication interface.

[0074] In some embodiments, any one of UEs 901 and 902 may include an Internet of Things (IoT) UE, which may include a network access layer designed for low-power IoT applications that utilize short-term UE connections. The IoT UE may utilize technologies such as machine-to-machine (M2M) or machine-type communications (MTC) to exchange data with an MTC server or device via a public land mobile network (PLMN), proximity-based services (ProSe), or device-to-device (D2D) communications, a sensor network, or an IoT network. M2M or MTC data exchanges may be machine-initiated data exchanges. The IoT network description utilizes short-term connections to interconnect IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure). The IoT UE may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate connectivity to the IoT network.

[0075] UEs 901 and 902 may be configured to be connected (e.g., communicatively coupled) to a radio access network (RAN) 910—the RAN 910 may be, for example, an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), a Next Generation RAN (NG RAN), or some other type of RAN. UEs 901 and 902 utilize connections 903 and 904, respectively, each of which includes a physical communication interface or layer (discussed in more detail below); in this example, connections 903 and 904 are shown as air interfaces to enable communication coupling and may conform to cellular communication protocols, such as Global System for Mobile Communications (GSM) protocols, code-division multiple access (CDMA) network protocols, Push-to-Talk (PTT) protocols, PTT over Cellular (POC) protocols, Universal Mobile Telecommunications System (UMTS) protocols, 3GPP Long Term Evolution (LTE) protocols, fifth generation (5G) protocols, New Radio (NR) protocols, and the like.

[0076] In this embodiment, the UEs 901 and 902 may also directly exchange communication data via a ProSe interface 905. The ProSe interface 905 may also be referred to as a side interface including 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).

[0077] UE 902 is shown as being configured to access an access point (AP) 906 via a connection 907. Connection 907 may include a local wireless connection, such as one compliant with any IEEE 802.15 protocol, where AP 906 would include Wi-Fi. In this example, AP 906 is shown connected to the Internet, but not to the core network of the wireless system (described in more detail below).

[0078] The RAN 910 may include one or more access nodes that enable connections 903 and 904. These access nodes (ANs) may be referred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs), next-generation NodeBs (gNBs), RAN nodes, etc., and may include ground stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographic area (e.g., a cell). The RAN 910 may include one or more RAN nodes for providing macro cells, such as a macro RAN node 911, and one or more RAN nodes for providing femto cells or pico cells (e.g., cells with smaller coverage areas, smaller user capacity, or higher bandwidth than macro cells), such as a low power (LP) RAN node 912.

[0079] Either of the RAN nodes 911 and 912 may terminate the air interface protocol and may be the first point of contact for the UEs 901 and 902. In some embodiments, either of the RAN nodes 911 and 912 may perform various logical functions for the RAN 910, including 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.

[0080] According to some embodiments, UEs 901 and 902 may be configured to communicate with each other or with any of RAN nodes 911 and 912 using Orthogonal Frequency-Division Multiplexing (OFDM) communication signals over multi-carrier communication channels according to various communication technologies, such as, but not limited to, Orthogonal Frequency-Division Multiple Access (OFDMA) communication technology (e.g., for downlink communication) or Single Carrier Frequency Division Multiple Access (SC-FDMA) communication technology (e.g., for uplink and ProSe or sideband communication), although the scope of the embodiments is not limited in this regard. The OFDM signal may include multiple orthogonal subcarriers.

[0081] In some embodiments, a downlink resource grid can be used for downlink transmissions from either RAN node 911 or 912 to UEs 901 and 902, while uplink transmissions can utilize similar techniques. This grid can be a time-frequency grid, referred to as a resource grid or time-frequency resource grid, representing the physical resources in the downlink within each time slot. This time-frequency plane representation is common in OFDM systems, making it intuitive for radio resource allocation. Each column and row of the resource grid corresponds to an OFDM symbol and an OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to a time slot in a radio frame. The smallest time-frequency unit in the resource grid is represented as a resource element. Each resource grid includes several resource blocks, which describe the mapping of specific physical channels to resource elements. Each resource block includes a collection of resource elements; in the frequency domain, this represents the minimum number of resources currently allocable. There are several different physical downlink channels that are carried using these resource blocks.

[0082] The physical downlink shared channel (PDSCH) can carry user data and higher-layer signaling to UEs 901 and 902. The physical downlink control channel (PDCCH) can carry information about, among other things, the transport format and resource allocation associated with the PDSCH channel. It can also inform UEs 901 and 902 about the transport format, resource allocation, and H-ARQ (Hybrid Automatic Repeat Request) information associated with the uplink shared channel. Typically, downlink scheduling (assigning control and shared channel resource blocks to UEs 902 within a cell) can be performed at either RAN node 911 or 912 based on channel quality information fed back from either UE 901 or 902. Downlink resource assignment information can be sent on the PDCCH for (e.g., assigned to) each of UEs 901 and 902.

[0083] PDCCH can use control channel elements (CCE) to carry control information. Before being mapped to resource elements, PDCCH complex symbols can first be organized into quadruplets, which can then be transposed using a sub-block interleaver for rate matching. Each PDCCH can be sent using one or more of these CCEs, where each CCE can correspond to nine sets of four physical resource elements called resource element groups (REGs). Four Quadrature Phase Shift Keying (QPSK) symbols can be mapped to each REG. Depending on the size of the downlink control information (DCI) and the channel conditions, one or more CCEs can be used to send PDCCH. Four or more different PDCCH formats can be defined in LTE, with different numbers of CCEs (e.g., aggregation levels L = 1, 2, 4, or 8).

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

[0085] RAN 910 is shown as being communicatively coupled to a core network (CN) 920 via an S1 interface 913. In embodiments, CN 920 may be an evolved packet core (EPC) network, a next-generation packet core (NPC) network, or some other type of CN. In this embodiment, S1 interface 913 is split into two parts: an S1-U interface 914, which carries traffic data between RAN nodes 911 and 912 and a serving gateway (S-GW) 922; and an S1 mobility management entity (MME) interface 915, which is a signaling interface between RAN nodes 911 and 912 and MME 921.

[0086] In this embodiment, CN 920 includes MME 921, S-GW 922, Packet Data Network (PDN) Gateway (P-GW) 923, and Home Subscriber Server (HSS) 924. MME 921 may be functionally similar to the control plane of a conventional Serving GPRS Support Node (SGSN). MME 921 may manage mobility aspects of access, such as gateway selection and tracking area list management. HSS 924 may include a database for network users, including subscription-related information, to support network entities in handling communication sessions. CN 920 may include one or more HSSs 924, depending on the number of mobile subscribers, device capacity, network organization, etc. For example, HSS 924 may provide support for routing / roaming, authentication, authorization, naming / addressing resolution, location compliance, etc.

[0087] The S-GW 922 can terminate the S1 interface 913 towards the RAN 910 and route data packets between the RAN 910 and the CN 920. In addition, the S-GW 922 can be the local mobility anchor point for handovers between RAN nodes and can also provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful interception, charging, and some policy enforcement.

[0088] The P-GW 923 may terminate the SGi interface toward the PDN. The P-GW 923 may route data packets between the EPC network 923 and external networks, such as a network including an application server 930 (or application function (AF)), via an Internet Protocol (IP) interface 925. Generally speaking, the application server 930 may be an element that provides applications that utilize IP bearer resources with the core network (e.g., UMTS Packet Service (PS) domain, LTE PS data services, etc.). In this embodiment, the P-GW 923 is shown as being communicatively coupled to the application server 930 via the IP communication interface 925. The application server 930 may 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 UEs 901 and 902 via the CN 920.

[0089] The P-GW 923 can also be a node for policy enforcement and charging data collection. The Policy and Charging Rules Function (PCRF) 926 is the policy and charging control element of the CN 920. In a non-roaming scenario, there can be a single PCRF in the Home Public Land Mobile Network (HPLMN) associated with the UE's Internet Protocol Connectivity Access Network (IP-CAN) session. In a roaming scenario with local routing of traffic, there can be two PCRFs associated with the UE's IP-CAN session: the Home PCRF (H-PCRF) in the HPLMN and the Visited PCRF (V-PCRF) in the Visited Public Land Mobile Network (VPLMN). The PCRF 926 can be communicatively coupled to the application server 930 via the P-GW 923. The application server 930 may signal the PCRF 926 to indicate the new service flow and select appropriate Quality of Service (QoS) and charging parameters. The PCRF 926 may configure this rule to the Policy and Charging Enforcement Function (PCEF) (not shown) using the appropriate traffic flow template (TFT) and QoS class of identifier (QCI), which initiates the QoS and charging specified by the application server 930.

[0090] Figure 10Example components of device 1000 are illustrated according to some embodiments. In some embodiments, device 1000 may include application circuitry 1002, baseband circuitry 1004, radio frequency (RF) circuitry 1006, front-end module (FEM) circuitry 1008, one or more antennas 1010, and power management circuitry (PMC) 1012, coupled together at least as shown. The illustrated components of device 1000 may be included in a UE or a RAN node. In some embodiments, device 1000 may include fewer elements (e.g., a RAN node may not utilize application circuitry 1002 but instead include a processor / controller to process IP data received from an EPC). In some embodiments, device 1000 may include additional elements, such as memory / storage, a display, a camera, sensors, or input / output (I / O) interface elements. In other embodiments, the components described below may be included in more than one device (e.g., for a cloud RAN (C-RAN) implementation, the circuitry may be split and included in more than one device).

[0091] Application circuitry 1002 may include one or more application processors. For example, application circuitry 1002 may 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 specialized processors (e.g., graphics processors, application processors, etc.). The processor(s) may be coupled to or include a memory / storage device and may be configured to execute instructions stored in the memory / storage device to enable various applications or operating systems to run on device 1000. In some embodiments, the processor(s) of application circuitry 1002 may process IP data packets received from the EPC.

[0092] The baseband circuitry 1004 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The baseband circuitry 1004 may include one or more baseband processors or control logic to process baseband signals received from the receive signal path of the RF circuitry 1006 and generate baseband signals for the transmit signal path of the RF circuitry 1006. The baseband processing circuitry 1004 may interface with the application circuitry 1002 to generate and process baseband signals and control the operation of the RF circuitry 1006. For example, in some embodiments, the baseband circuitry 1004 may include a third-generation (3G) baseband processor 1004a, a fourth-generation (4G) baseband processor 1004b, a fifth-generation (5G) baseband processor 1004c, or other baseband processor(s) 1004d for other current generations, generations in development, or generations to be developed in the future (e.g., second generation (2G), sixth generation (6G), etc.). Baseband circuitry 1004 (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 RF circuitry 1006. In other embodiments, some or all of the functions of baseband processors 1004a-d may be included in modules stored in memory 1004g and executed via central processing unit (CPU) 1004e. Radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, radio frequency offset, and the like. In some embodiments, the modulation / demodulation circuitry of baseband circuitry 1004 may include fast Fourier transform (FFT), precoding, or constellation mapping / demapping functions. In some embodiments, the encoding / decoding circuitry of baseband circuitry 1004 may include convolution, tail-biting, turbo, Viterbi, or low-density parity check (LDPC) encoder / decoder functions. Embodiments of the modulation / demodulation and encoder / decoder functions are not limited to these examples and may include other suitable functions in other embodiments.

[0093] In some embodiments, the baseband circuit 1004 may include one or more audio digital signal processors (DSPs) 1004f. The audio DSP(s) 1004f may include elements for compression / decompression and echo cancellation, and in other embodiments may include other appropriate processing elements. The components of the baseband circuit may be appropriately combined in a single chip, a single chipset, or, in some embodiments, arranged on the same circuit board. In some embodiments, some or all of the components of the baseband circuit 1004 and the application circuit 1002 may be implemented together, for example, on a system on a chip (SOC).

[0094] In some embodiments, baseband circuitry 1004 can provide communications compatible with one or more radio technologies. For example, in some embodiments, baseband circuitry 1004 can support communications with the Evolved Universal Terrestrial Radio Access Network (E-UTRAN) or other wireless metropolitan area networks (WMANs), wireless local area networks (WLANs), and wireless personal area networks (WPANs). Embodiments in which baseband circuitry 1004 is configured to support radio communications using more than one wireless protocol may be referred to as multi-mode baseband circuitry.

[0095] RF circuitry 1006 can enable communication with a wireless network using modulated electromagnetic radiation via a non-solid medium. In various embodiments, RF circuitry 1006 can include switches, filters, amplifiers, and the like to facilitate communication with the wireless network. RF circuitry 1006 can include a receive signal path that can include circuitry to down-convert RF signals received from FEM circuitry 1008 and provide a baseband signal to baseband circuitry 1004. RF circuitry 1006 can also include a transmit signal path that can include circuitry to up-convert baseband signals provided by baseband circuitry 1004 and provide an RF output signal to FEM circuitry 1008 for transmission.

[0096] In some embodiments, the receive signal path of RF circuitry 1006 may include mixer circuitry 1006a, amplifier circuitry 1006b, and filter circuitry 1006c. In some embodiments, the transmit signal path of RF circuitry 1006 may include filter circuitry 1006c and mixer circuitry 1006a. RF circuitry 1006 may also include synthesizer circuitry 1006d for synthesizing frequencies for use by mixer circuitry 1006a in the receive and transmit signal paths. In some embodiments, mixer circuitry 1006a in the receive signal path may be configured to downconvert the RF signal received from FEM circuitry 1008 based on the synthesized frequency provided by synthesizer circuitry 1006d. Amplifier circuitry 1006b may be configured to amplify the downconverted signal, and filter circuitry 1006c may be a low-pass filter (LPF) or a band-pass filter (BPF) configured to remove unwanted signals from the downconverted signal to generate an output baseband signal. The output baseband signal may be provided to baseband circuitry 1004 for further processing. In some embodiments, the output baseband signal may be a zero-frequency baseband signal, although this is not required. In some embodiments, mixer circuitry 1006a of the receive signal path may include a passive mixer, although the scope of the embodiments is not limited in this regard.

[0097] In some embodiments, mixer circuit 1006a of the transmit signal path may be configured to upconvert an input baseband signal based on a synthesized frequency provided by synthesizer circuit 1006d to generate an RF output signal for FEM circuit 1008. The baseband signal may be provided by baseband circuit 1004 and may be filtered by filter circuit 1006c.

[0098] In some embodiments, the mixer circuit 1006a of the receive signal path and the mixer circuit 1006a of the transmit signal path may include two or more mixers and may be arranged for quadrature down-conversion and up-conversion, respectively. In some embodiments, the mixer circuit 1006a of the receive signal path and the mixer circuit 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 circuit 1006a of the receive signal path and the mixer circuit 1006a of the transmit signal path may be arranged for direct down-conversion and direct up-conversion, respectively. In some embodiments, the mixer circuit 1006a of the receive signal path and the mixer circuit 1006a of the transmit signal path may be configured for superheterodyne operation.

[0099] In some embodiments, the output baseband signal and the input baseband signal may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternative embodiments, the output baseband signal and the input baseband signal may be digital baseband signals. In these alternative embodiments, RF circuitry 1006 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry, and baseband circuitry 1004 may include a digital baseband interface to communicate with RF circuitry 1006.

[0100] In some dual-mode embodiments, separate radio IC circuitry may be provided to process signals for each spectrum, although the scope of the embodiments is not limited in this respect.

[0101] In some embodiments, synthesizer circuit 1006 d may be a fractional-N synthesizer or a fractional-N / N+1 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 circuit 1006 d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider.

[0102] Synthesizer circuit 1006d may be configured to synthesize an output frequency based on the frequency input and the divider control input for use by mixer circuit 1006a of RF circuit 1006. In some embodiments, synthesizer circuit 1006d may be a fractional-N / N+1 synthesizer.

[0103] In some embodiments, the frequency input may be provided by a voltage controlled oscillator (VCO), although this is not required. Depending on the desired output frequency, the divider control input may be provided by baseband circuitry 1004 or application processor 1002. In some embodiments, the divider control input (e.g., N) may be determined from a lookup table based on the channel indicated by application processor 1002.

[0104] The synthesizer circuit 1006d of the RF circuit 1006 may include a frequency divider, a delay-locked loop (DLL), a multiplexer, and a phase accumulator. In some embodiments, the frequency 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 N or N+1 (e.g., based on a carry output) to provide a fractional division ratio. In some example embodiments, the DLL may include a cascaded set of 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 decompose a VCO cycle into Nd equal phase packets, 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.

[0105] In some embodiments, synthesizer circuit 1006d can be configured to generate a carrier frequency as an output frequency, while in other embodiments, the output frequency can be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with a quadrature generator and divider circuit to generate multiple signals at the carrier frequency with multiple phases. In some embodiments, the output frequency can be an LO frequency (fLO). In some embodiments, RF circuit 1006 can include an IQ / polar converter.

[0106] The FEM circuitry 1008 may include a receive signal path that may include circuitry configured to operate on RF signals received from one or more antennas 1010, amplify the received signals, and provide an amplified version of the received signals to the RF circuitry 1006 for further processing. The FEM circuitry 1008 may also include a transmit signal path that may include circuitry configured to amplify signals provided for transmission by the RF circuitry 1006 for transmission by one or more of the one or more antennas 1010. In various embodiments, amplification by the transmit or receive path may be performed only in the RF circuitry 1006, only in the FEM 1008, or in both the RF circuitry 1006 and the FEM 1008.

[0107] In some embodiments, the FEM circuit 1008 may include a TX / RX switch to switch between transmit and receive modes of operation. The FEM circuit may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuit may include an LNA to amplify a received RF signal and provide an amplified receive RF signal as an output (e.g., to the RF circuit 1006). The transmit signal path of the FEM circuit 1008 may include a power amplifier (PA) to amplify an input RF signal (e.g., provided by the RF circuit 1006) and one or more filters to generate an RF signal for subsequent transmission (e.g., by one or more of the one or more antennas 1010).

[0108] In some embodiments, PMC 1012 can manage the power provided to baseband circuitry 1004. Specifically, PMC 1012 can control power source selection, voltage scaling, battery charging, or DC-to-DC conversion. When device 1000 is capable of being battery-powered, such as when the device is included in a UE, PMC 1012 is often included. PMC 1012 can increase power conversion efficiency while providing a desired implementation size and heat dissipation characteristics.

[0109] Although Figure 10 PMC 1012 is shown coupled only to baseband circuitry 1004. However, in other embodiments, PMC 1012 may additionally or alternatively be coupled to other components, such as, but not limited to, application circuitry 1002, RF circuitry 1006, or FEM 1008, and perform similar power management operations for the other components.

[0110] In some embodiments, the PMC 1012 may control or otherwise function as part of various power-saving mechanisms for the device 1000. For example, if the device 1000 is in the RRC_Connected state, where it remains connected to a RAN node in anticipation of receiving traffic soon, it may enter a state known as Discontinuous Reception Mode (DRX) after a period of inactivity. During this state, the device 1000 may power down for brief intervals and thereby conserve power.

[0111] If there is no data traffic activity for a long period of time, the device 1000 may transition to the RRC_Idle state, in which it is disconnected from the network and does not perform operations such as channel quality feedback, handover, etc. The device 1000 enters a very low power state and performs paging, in which it wakes up periodically again to listen to the network, and then powers down again. The device 1000 may not receive data in this state, and in order to receive data, it may transition back to the RRC_Connected state.

[0112] An additional power-saving mode allows a device to be unavailable to the network for periods longer than the paging interval (ranging from a few seconds to several hours). During this time, the device is completely unreachable by the network and can be completely powered off. Any data sent during this time is subject to significant delays, and it is assumed that this delay is acceptable.

[0113] The processor of the application circuitry 1002 and the processor of the baseband circuitry 1004 may be configured to execute elements of one or more instances of a protocol stack. For example, the processor of the baseband circuitry 1004 may be configured, individually or in combination, to execute layer 3, layer 2, or layer 1 functions, while the processor of the application circuitry 1004 may utilize data received from these layers (e.g., packet data) and further execute layer 4 functions (e.g., the transmission communication protocol (TCP) and user datagram protocol (UDP) layers). For purposes herein, layer 3 may include a radio resource control (RRC) layer, which is described in more detail below. For purposes herein, layer 2 may include a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer, which are described in more detail below. For purposes herein, layer 1 may include a physical (PHY) layer of a UE / RAN node, which is described in more detail below.

[0114] Figure 11 An example interface of a baseband circuit is illustrated according to some embodiments. As described above, Figure 10 The baseband circuit 1004 may include processors 1004a-1004e and a memory 1004g utilized by the processors. Each of the processors 1004a-1004e may include a memory interface 1104a-1104e, respectively, to send / receive data to / from the memory 1004g.

[0115] The baseband circuit 1004 may also include one or more interfaces to communicatively couple to other circuits / devices, such as a memory interface 1112 (e.g., an interface for sending / receiving data to / from a memory external to the baseband circuit 1004), an application circuit interface 1114 (e.g., an interface for sending / receiving data to / from a memory external to the baseband circuit 1004), and an application circuit interface 1115 (e.g., an interface for sending / receiving data to / from a memory external to the baseband circuit 1004). Figure 10 application circuit 1002 to send / receive data), RF circuit interface 1116 (eg, to / from Figure 10 RF circuit 1006 sends / receives data), wireless hardware connectivity interface 1118 (e.g., to / from Near Field Communication (NFC) components, Components (e.g., low energy ), components and other communication components to send / receive data) and a power management interface 1120 (for example, an interface for sending / receiving power or control signals to / from the PMC 1012).

[0116] Figure 12An example illustration of a wireless device is provided, such as a user equipment (UE), a mobile station (MS), a mobile wireless device, a mobile communication device, a tablet device, a mobile phone, or other type of wireless device. The wireless device may include one or more antennas configured to communicate with a node, macro node, low power node (LPN), or transmitting station, such as a base station (BS), an evolved Node B (eNB), a baseband processing unit (BBU), a remote radio head (RRH), remote radio equipment (RRE), a relay station (RS), radio equipment (RE), or other type of wireless wide area network (WWAN) access point. The wireless device may 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. A wireless device can communicate by utilizing a separate antenna for each wireless communication standard or by utilizing a shared antenna for multiple wireless communication standards. A wireless device can communicate in a wireless local area network (WLAN), a wireless personal area network (WPAN), and / or a WWAN. A wireless device can also include a wireless modem. A wireless modem can, for example, include a wireless radio transceiver and baseband circuitry (e.g., a baseband processor). In one example, a wireless modem can modulate signals transmitted by the wireless device via one or more antennas and demodulate signals received by the wireless device via one or more antennas.

[0117] Figure 12Also provided are diagrams 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 another 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 the user. The non-volatile memory port can also be used to expand the memory capacity 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.

[0118] Example

[0119] The following examples relate to specific technical embodiments and indicate specific features, elements, or acts that may be used or otherwise combined in implementing such embodiments.

[0120] Example 1 includes 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 comprising BWP configuration information for one or more of a downlink (DL) or uplink (UL) BWP configuration, wherein the BWP configuration information comprises: a subcarrier spacing of the BWP, and a location and bandwidth of the BWP; encode, at the UE, one or more of data or control information for transmission to a next generation node B (gNB); and decode, at the UE, one or more of data or control information received from the gNB using the BWP configuration information; and a memory interface configured to send the BWP configuration information to a memory.

[0121] Example 2 includes the apparatus of Example 1, wherein the one or more processors are further configured to: decode, at the UE, the RRC signal including the BWP configuration information, wherein the BWP configuration information includes N BWP configurations, where N is a positive integer.

[0122] Example 3 includes the apparatus of Example 2, wherein for the N BWP configurations, there is one active DL BWP and one active UL BWP.

[0123] Example 4 includes the apparatus of Example 2, wherein N is a maximum number of DL BWP configurations and a maximum number of UL BWP configurations.

[0124] Example 5 includes the apparatus of Example 4, wherein N is 4.

[0125] Example 6 includes an apparatus as described in Example 2, wherein the one or more processors are further configured to: decode the RRC signal including the position and bandwidth of the BWP at the UE, wherein the position and bandwidth include a number of physical resource blocks (PRBs) relative to an absolute frequency position.

[0126] Example 7 includes the apparatus of any one of Examples 1 to 4, wherein the one or more processors are further configured to: decode the RRC signal at the UE, wherein the RRC signal includes a cyclic prefix (CP).

[0127] Example 8 includes an apparatus as described in any one of Examples 1-4, wherein the one or more processors are further configured to: decode an RRC signal at the UE including BWP configuration information for one or more of the DL BWP configurations or the UL BWP configurations, wherein the one or more DL BWP configurations are configured separately from the one or more UL BWP configurations.

[0128] Example 9 includes the apparatus of Example 2, wherein for the N BWP configurations, a frequency range of one BWP configuration overlaps with a frequency range of another BWP configuration.

[0129] Example 10 includes an apparatus of a next generation node B (gNB) operable for bandwidth part (BWP) configuration, the apparatus comprising: one or more processors configured to: encode, at the gNB, a radio resource control (RRC) signal comprising BWP configuration information for one or more of a downlink (DL) or uplink (UL) BWP configuration, wherein the BWP configuration information comprises: a subcarrier spacing of the BWP, and a location and bandwidth of the BWP; decode, at the gNB, one or more of data or control information received from a user equipment (UE); and encode, at the gNB, one or more of the data or control information for transmission to the UE using the BWP configuration information; and a memory interface configured to send the BWP configuration information to a memory.

[0130] Example 11 includes the apparatus of Example 10, wherein the one or more processors are further configured to: encode the RRC signal including the BWP configuration information at the gNB, wherein the BWP configuration information includes N BWP configurations, where N is a positive integer.

[0131] Example 12 includes the apparatus of Example 11, wherein for the N BWP configurations, there is one active DLBWP and one active UL BWP.

[0132] Example 13 includes the apparatus of Example 11, wherein N is a maximum number of DL BWP configurations and a maximum number of UL BWP configurations.

[0133] Example 14 includes the apparatus of Example 13, wherein N is 4.

[0134] Example 15 includes the apparatus of Example 10, wherein the one or more processors are further configured to encode, at the gNB, the RRC signal comprising the location and bandwidth of the BWP, wherein the location and bandwidth comprise a number of physical resource blocks (PRBs) relative to an absolute frequency location.

[0135] Example 16 includes the apparatus of any one of Examples 10 to 15, wherein the one or more processors are further configured to: encode the RRC signal at the gNB, wherein the RRC signal includes a cyclic prefix (CP).

[0136] Example 17 includes an apparatus as described in any one of Examples 10 to 15, wherein the one or more processors are further configured to: encode an RRC signal at the gNB including BWP configuration information for one or more of the DL BWP configurations or the UL BWP configurations, wherein the one or more DL BWP configurations are configured separately from the one or more ULBWP configurations.

[0137] Example 18 includes at least one machine-readable storage medium having instructions embodied thereon for performing bandwidth part (BWP) configuration, the instructions, when executed by one or more processors at a UE, performing the following operations: decoding a radio resource control (RRC) signal at the UE including BWP configuration information for one or more downlink (DL) or uplink (UL) BWP configurations, wherein the BWP configuration information includes: a subcarrier spacing of the BWP, and a location and bandwidth of the BWP; and encoding one or more of data or control information at the UE for transmission to a next generation node B (gNB); and decoding one or more of data or control information received from the gNB at the UE using the BWP configuration information.

[0138] Example 19 includes at least one machine-readable storage medium as described in Example 18, further comprising instructions that, when executed, perform the following operations: decode the RRC signal including the BWP configuration information at the UE, wherein the BWP configuration information includes N BWP configurations, where N is a positive integer.

[0139] Example 20 includes the at least one machine-readable storage medium of Example 19, wherein for the N BWP configurations, there is one active DL BWP and one active UL BWP.

[0140] Example 21 includes at least one machine-readable storage medium as described in Example 19, wherein N is a maximum number of DL BWP configurations and a maximum number of UL BWP configurations.

[0141] Example 22 includes the apparatus of Example 21, wherein N is 4.

[0142] Example 23 includes at least one machine-readable storage medium as described in any one of Examples 18 to 21, further comprising instructions that, when executed, perform the following operations: decode the RRC signal at the UE, wherein the RRC signal includes a cyclic prefix (CP).

[0143] Example 24 includes at least one machine-readable storage medium as described in any one of Examples 18 to 21, further including instructions that, when executed, perform the following operations: decoding the RRC signal including BWP configuration information for one or more of the DL BWP configurations or the UL BWP configurations at the UE, wherein the one or more DL BWP configurations are configured separately from the one or more UL BWP configurations.

[0144] Example 25 includes an apparatus of a user equipment (UE) operable for bandwidth part (BWP) switching, the apparatus comprising: one or more processors configured to: decode BWP configuration information via a radio resource control (RRC) signal, wherein the BWP configuration information comprises a timer value and N BWP configurations, where N is a positive integer; identify a default BWP from the N BWP configurations; and identify the timer value for switching the user equipment (UE) from one of the N BWP configurations to the default (DL) BWP; and a memory interface configured to send the configuration information to a memory.

[0145] Example 26 includes the apparatus of Example 25, further comprising a transceiver configured to receive the configuration information via the RRC signal.

[0146] Example 27 includes the apparatus of Example 25, wherein the one or more processors are further configured to start a handover timer at the UE when the UE switches to an active DL BWP that is not the default DL BWP.

[0147] Example 28 includes the apparatus of Example 25, wherein the one or more processors are further configured to switch the active DL BWP to a default DL BWP upon expiration of the switch timer.

[0148] Example 29 includes the apparatus of Example 27, wherein the one or more processors are further configured to restart the handover timer at the UE when the UE successfully decodes the control information.

[0149] Example 30 includes the apparatus of Example 29, wherein the control information comprises downlink control information (DCI) for scheduling a physical downlink shared channel (PDSCH) in the active DL BWP.

[0150] Example 31 includes the apparatus of Example 25, wherein the one or more processors are further configured to determine an active DL BWP at the UE.

[0151] Example 32 includes the apparatus of Example 25, wherein the UE comprises an antenna, a touch-sensitive display, a speaker, a microphone, a graphics processor, an application processor, internal memory, a non-volatile memory port, or a combination thereof.

[0152] Example 33 includes an apparatus of a next generation node B (gNB) operable for bandwidth part (BWP) switching, the apparatus comprising: one or more processors configured to: identify BWP configuration information, wherein the BWP configuration information includes N BWP configurations, where N is a positive integer; identify a default downlink (DL) BWP from the N BWP configurations; determine a timer value for switching a user equipment (UE) to the default DL BWP; 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; and a memory interface configured to send the configuration information to a memory.

[0153] Example 34 includes the apparatus of Example 33, further comprising a transceiver configured to transmit the configuration information via the RRC signal.

[0154] Example 35 includes the apparatus of Example 33, wherein the one or more processors are further configured to start a handover timer at the gNB when the gNB switches to an active DL BWP that is not the default DL BWP.

[0155] Example 36 includes the apparatus of Example 35, wherein the one or more processors are further configured to switch from encoding the data or control information for transmission in the active DL BWP to encoding the data or the control information for transmission in the default DL BWP upon expiration of the switching timer.

[0156] Example 37 includes the apparatus of Example 33, wherein the one or more processors are further configured to: determine an active DL BWP at the gNB.

[0157] Example 38 includes at least one machine-readable storage medium having embodied thereon instructions for performing bandwidth part (BWP) switching, the instructions, when executed by one or more processors at a user equipment (UE), performing the following operations: decoding BWP configuration information via a radio resource control (RRC) signal, wherein the BWP configuration information includes N BWP configurations, where N is a positive integer; identifying a default BWP from the N BWP configurations; and identifying a timer value for switching the user equipment (UE) from one of the N BWP configurations to the default (DL) BWP.

[0158] Example 39 includes the at least one machine-readable storage medium of Example 38, further comprising instructions that, when executed, start a handover timer at the UE when the UE switches to an active DL BWP that is not the default DL BWP.

[0159] Example 40 includes the at least one machine-readable storage medium of Example 39, further comprising instructions that, when executed, switch the active DL BWP to a default DL BWP upon expiration of the switch timer.

[0160] Example 41 includes at least one machine-readable storage medium as described in Example 39, further comprising instructions that, when executed, perform the following operations: restart the switching timer at the UE when the UE successfully decodes downlink control information (DCI) for scheduling a physical downlink shared channel (PDSCH) in the active DL BWP.

[0161] Example 42 includes the at least one machine-readable storage medium of Example 38, further comprising instructions that, when executed, determine an active DL BWP at the UE.

[0162] Example 43 includes an apparatus of a next generation Node B (gNB) operable for bandwidth part (BWP) operation, the apparatus comprising: one or more processors configured to: select, at the gNB, a predetermined location and bandwidth of the BWP; identify a subcarrier spacing for a predetermined parameter set configured for use in the BWP, and encode, at the gNB, one or more of data or control information for transmission to a user equipment (UE) using the BWP having the selected location and bandwidth and the identified subcarrier spacing; and a memory interface configured to send the subcarrier spacing to a memory.

[0163] Example 44 includes the apparatus of Example 43, further comprising a transceiver configured to receive data or control information in the BWP.

[0164] Example 45 includes the apparatus of Example 43, wherein the one or more processors are further configured to select the location and bandwidth, wherein the location is an offset of a number of physical resource blocks (PRBs) relative to an absolute frequency location.

[0165] Example 46 includes the apparatus of Example 45, wherein the bandwidth is a number of physical resource blocks (PRBs).

[0166] Example 47 includes the apparatus of Example 43, wherein the one or more processors are further configured to select predetermined locations and bandwidths and subcarrier spacings for a plurality of BWP configurations.

[0167] Example 48 includes the apparatus of Example 47, wherein, for the plurality of BWP configurations, a frequency range of one BWP configuration overlaps with a frequency range of another BWP configuration.

[0168] Example 49 includes the apparatus of Example 43, wherein the one or more processors are further configured to select a cyclic prefix (CP) length based on the subcarrier spacing.

[0169] Example 50 includes an apparatus as described in Example 43, wherein the one or more processors are further configured to: encode a radio resource control (RRC) signal at the gNB including BWP configuration information for one or more downlink (DL) or one or more uplink (UL) BWP configurations.

[0170] Example 51 includes an apparatus as described in Example 50, wherein the one or more processors are further configured to: encode the RRC signal at the gNB, wherein the BWP configuration information includes a location and a bandwidth of the BWP, wherein the location and bandwidth include a number of physical resource blocks (PRBs) relative to an absolute frequency position.

[0171] Example 52 includes an apparatus of a user equipment (UE) operable for bandwidth part (BWP) operation, the apparatus comprising: one or more processors configured to: decode, at the UE, a predetermined position and bandwidth of the BWP; decode, at the UE, a subcarrier spacing for a predetermined parameter set configured for use in the BWP, and encode, at the UE, one or more of data or control information for transmission to a next generation Node B (gNB) using the BWP having the decoded position and bandwidth and the decoded subcarrier spacing; and a memory interface configured to send the subcarrier spacing to a memory.

[0172] Example 53 includes the apparatus of Example 52, further comprising a transceiver configured to transmit data or control information in the BWP.

[0173] Example 54 includes the apparatus of Example 52, wherein the one or more processors are further configured to decode offsets of a number of physical resource blocks (PRBs) relative to an absolute frequency position to determine the position.

[0174] Example 55 includes the apparatus of Example 54, wherein the bandwidth is a number of physical resource blocks (PRBs).

[0175] Example 56 includes the apparatus of Example 52, wherein the one or more processors are further configured to decode the predetermined position and bandwidth and the subcarrier spacing for multiple BWP configurations.

[0176] Example 57 includes the apparatus of Example 56, wherein, for the plurality of BWP configurations, a frequency range of one BWP configuration overlaps with a frequency range of another BWP configuration.

[0177] Example 58 includes the apparatus of Example 52, wherein the one or more processors are further configured to decode a cyclic prefix (CP) length, wherein the CP length is based on the subcarrier spacing.

[0178] Example 59 includes an apparatus as described in Example 52, wherein the one or more processors are further configured to: decode a radio resource control (RRC) signal at the UE including BWP configuration information for one or more downlink (DL) or one or more uplink (UL) BWP configurations.

[0179] Example 60 includes an apparatus as described in Example 59, wherein the one or more processors are further configured to: decode the RRC signal at the UE, wherein the BWP configuration information includes a location and bandwidth of the BWP, wherein the location and bandwidth include a number of physical resource blocks (PRBs) relative to an absolute frequency position.

[0180] Example 61 includes at least one machine-readable storage medium having embodied thereon instructions for performing bandwidth part (BWP) operations, the instructions, when executed by one or more processors at a next generation Node B (gNB), performing the following operations: decoding, at the UE, a predetermined position and bandwidth of the BWP; decoding, at the UE, a subcarrier spacing for a predetermined parameter set configured for use in the BWP, and encoding, at the UE, one or more of data or control information for transmission to a next generation Node B (gNB) using the BWP having the decoded position and bandwidth and the decoded subcarrier spacing;

[0181] Example 62 includes the at least one machine-readable storage medium of Example 61, further comprising instructions that, when executed, perform the following operations: sending data or control information in the BWP.

[0182] Example 63 includes at least one machine-readable storage medium as described in Example 61, further comprising instructions that, when executed, perform the following operations: decode the offsets of several physical resource blocks (PRBs) relative to the absolute frequency positions to determine the positions.

[0183] Example 64 includes the at least one machine-readable storage medium of Example 63, wherein the bandwidth is a number of physical resource blocks (PRBs).

[0184] Example 65 includes the at least one machine-readable storage medium of Example 61, further comprising instructions that, when executed, decode the predetermined position and bandwidth and the subcarrier spacing for a plurality of BWP configurations.

[0185] Example 66 includes the at least one machine-readable storage medium of Example 65, wherein, for the plurality of BWP configurations, a frequency range of one BWP configuration overlaps with a frequency range of another BWP configuration.

[0186] Example 67 includes at least one machine-readable storage medium as described in Example 61, further comprising instructions that, when executed, perform the following operations: decode a cyclic prefix (CP) length, wherein the CP length is based on the subcarrier spacing.

[0187] Example 68 includes at least one machine-readable storage medium as described in Example 61, further comprising instructions that, when executed, perform the following operations: decoding a radio resource control (RRC) signal including BWP configuration information for one or more downlink (DL) or one or more uplink (UL) BWP configurations at the UE.

[0188] Example 69 includes at least one machine-readable storage medium as described in Example 68, further including instructions that, when executed, perform the following operations: decode the RRC signal at the UE, wherein the BWP configuration information includes the location and bandwidth of the BWP, wherein the location and bandwidth include a number of physical resource blocks (PRBs) relative to an absolute frequency position.

[0189] The various techniques or some aspects or portions thereof may take the form of program code (i.e., instructions) embodied in a tangible medium, such as a floppy disk, a compact disc read-only memory (CD-ROM), a hard drive, a non-transitory computer-readable storage medium, or any other machine-readable storage medium, wherein when the program code is loaded into a machine such as a computer and executed by the machine, the machine becomes an apparatus for implementing the various techniques. In the case of program code execution on a programmable computer, the computing device may include a processor, a storage medium (including volatile and non-volatile memory and / or storage elements) readable by the processor, at least one input device, and at least one output device. The volatile and non-volatile memory and / or storage elements may be random-access memory (RAM), erasable programmable read-only memory (EPROM), a flash drive, an optical drive, a magnetic hard drive, a solid-state drive, or other media for storing electronic data. The nodes and wireless devices may also include a transceiver module (i.e., a transceiver), a counter module (i.e., a counter), a processing module (i.e., a processor), and / or a clock module (i.e., a clock) or a timer module (i.e., a timer). In one example, selected components of the transceiver module may 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 application programming interfaces (APIs), 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, if desired, the program(s) may be implemented in assembly or machine language. In any case, the language may be a compiled or interpreted language and combined with a hardware implementation.

[0190] As used herein, the term "circuit" may refer to, be a part of, or include an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or grouped) and / or memory (shared, dedicated, or grouped) that executes one or more software or firmware programs, combinational logic circuitry, and / or other appropriate hardware components that provide the described functionality. In some embodiments, the circuit may be implemented in one or more software or firmware modules, or the functionality associated with the circuit may be implemented by one or more software or firmware modules. In some embodiments, the circuit may include logic that is at least partially operable in hardware.

[0191] It should be understood that many of the functional units described in this specification have been labeled as modules to more clearly emphasize their implementation independence. For example, a module can be implemented as a hardware circuit, including a custom very-large-scale integration (VLSI) circuit or gate array, an off-the-shelf semiconductor such as a logic chip, a transistor, or other discrete components. A module can also be implemented in a programmable hardware device, such as a field programmable gate array, programmable array logic, a programmable logic device, and the like.

[0192] Modules may also be implemented in software for execution by various types of processors. An identified module of executable code may, for example, comprise one or more physical or logical blocks of computer instructions, which may, for example, be organized as objects, procedures, or functions. However, the executable files of an identified module may not be physically located together, but may comprise different instructions stored in different locations that, when logically joined together, constitute the module and implement the module's stated purpose.

[0193] In fact, the module of executable code can be a single instruction, or many instructions, and can even be distributed on several different code segments, distributed between different programs and distributed on several memory devices. Similarly, operational data can be identified and illustrated in the module here, and can be embodied in any appropriate form and organized in the data structure of any appropriate type. Operational data can be gathered into a single data set, or can be distributed in different locations, including being distributed on different storage devices, and can only exist as an electronic signal on a system or network in part. Modules can be passive or active, including agents that can be operated to perform the desired function.

[0194] References throughout this specification to "example" or "exemplary" mean 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, the appearances of the phrase "in an example" or the word "exemplary" in various places throughout this specification are not necessarily all referring to the same embodiment.

[0195] As used herein, multiple items, structural elements, constituent elements, and / or materials may be presented in a common list for convenience. However, these lists should be interpreted as if each member of the list is individually identified as a separate and unique member. Thus, in the absence of contrary indications, individual members of such a list should not be interpreted as equivalent to any other member of the same list simply based on their presentation in a common group. In addition, various embodiments and examples of the present technology may be mentioned herein together with replacements for their various components. It is to be understood that such embodiments, examples, and replacements should not be interpreted as factual equivalents of each other, but rather are to be considered as separate and autonomous representations of the present technology.

[0196] In addition, the features, structures or characteristics described may be combined in any appropriate manner in one or more embodiments. In the following description, many specific details are provided, such as examples of layout, distance, network examples, etc., to provide a thorough understanding of the embodiments of the present technology. However, those skilled in the art will recognize that the present technology may be implemented without one or more of these specific details or utilizing other methods, components, layouts, etc. In other cases, known structures, materials or operations are not shown or described in detail to avoid blurring the various aspects of the present technology.

[0197] While the foregoing examples illustrate the principles of the present technology in one or more specific applications, it will be apparent to those skilled in the art that many modifications in form, use, and implementation details may be made without exercising creativity and without departing from the principles and concepts of the present technology. Therefore, it is not intended that the present technology be limited except as set forth in the claims below.

Claims

1. A user equipment (UE) operable for bandwidth part (BWP) configuration, the UE comprising: One or more processors configured to: decoding, at the UE, a radio resource control (RRC) signal, the RRC signal including BWP configuration information for one or more downlink (DL) BWP configurations or one or more uplink (UL) BWP configurations, wherein the one or more DL BWP configurations are configured separately from the one or more UL BWP configurations, and wherein the BWP configuration information includes: the subcarrier spacing of the BWP, and the location and bandwidth of the BWP; encoding, at the UE, one or more of data or control information using the BWP configuration information for transmission to a base station; and decoding, 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 is configured to send the BWP configuration information to a memory.

2. The UE according to claim 1, wherein The one or more processors are further configured to: The RRC signal including the BWP configuration information is decoded at the UE, wherein the BWP configuration information includes N BWP configurations, where N is a positive integer.

3. The UE according to claim 2, wherein: For the N BWP configurations, there is one active DL BWP and one active UL BWP.

4. The UE according to claim 2, wherein: N is the maximum number of DL BWP configurations and the maximum number of UL BWP configurations. The UE according to claim 4 , wherein N is 4.

6. The UE according to claim 2, wherein: The one or more processors are further configured to decode, at the UE, the RRC signal comprising a location and a bandwidth of the BWP, wherein the location and the bandwidth comprise a number of physical resource blocks (PRBs) relative to an absolute frequency location.

7. The UE according to any one of claims 1 to 4, wherein: The one or more processors are further configured to: The RRC signal is decoded at the UE, wherein the RRC signal includes a cyclic prefix (CP).

8. The UE according to claim 2, wherein: For the N BWP configurations, a frequency range of one BWP configuration overlaps with a frequency range of another BWP configuration.

9. A base station operable for bandwidth part (BWP) configuration, the base station comprising: One or more processors configured to: encoding, at the base station, a radio resource control (RRC) signal, the RRC signal including BWP configuration information for one or more downlink (DL) BWP configurations or one or more uplink (UL) BWP configurations, wherein the one or more DL BWP configurations are configured separately from the one or more UL BWP configurations, and wherein the BWP configuration information includes: the subcarrier spacing of the BWP, and The location and bandwidth of the BWP, decoding, at the base station, one or more of data or control information received from a user equipment (UE) using the BWP configuration information; and encoding, at the base station, one or more of data or control information using the BWP configuration information for transmission to the UE; and A memory interface is configured to send the BWP configuration information to a memory.

10. The base station according to claim 9, wherein: The one or more processors are further configured to: The RRC signal including the BWP configuration information is encoded at the base station, wherein the BWP configuration information includes N BWP configurations, where N is a positive integer. The base station according to claim 10 , wherein: For the N BWP configurations, there is one active DL BWP and one active UL BWP.

12. The base station according to claim 10, wherein: N is the maximum number of DL BWP configurations and the maximum number of UL BWP configurations.

13. The base station according to claim 12, wherein: N is 4.

14. The base station according to claim 9, wherein: The one or more processors are further configured to: The RRC signal comprising the position and bandwidth of the BWP is encoded at the base station, wherein the position and the bandwidth comprise a number of physical resource blocks (PRBs) relative to an absolute frequency position.

15. The base station according to any one of claims 9 to 14, wherein: The one or more processors are further configured to: The RRC signal is encoded at the base station, wherein the RRC signal includes a cyclic prefix (CP).

Images