Enhancements to Bandwidth Part (BWP) Handover for Secondary Cell (SCELL)

Abstract

Systems, methods, and devices are provided that may include configuring one or more bandwidth parts of a secondary cell (SCell) for communication with a user equipment (UE). A base station transmits a first radio resource control (RRC) message to the UE, the RRC message including one or more configuration parameters for a first bandwidth part (BWP) associated with the secondary cell (SCell). The UE communicates the first message with the SCell via the first SCell BWP. The UE receives a second RRC message indicating a change from the first SCell BWP to a second SCell BWP to be used for SCell communication. The UE communicates a second message with the SCell via the second SCell BWP.

Description

Technical Field

[0001] The described aspects generally relate to bandwidth part (BWP) activation and deactivation in New Radio (NR). Background Art

[0002] A bandwidth part (BWP) refers to a subset or portion of the total allocated carrier bandwidth, forming a set of contiguous common resource blocks (CRBs) within the full carrier bandwidth. Summary of the Invention

[0003] The present disclosure relates to a communication network, and in particular, to BWP switching of a secondary cell (SCell) of a communication network. A BWP may start at a designated CRB and span a set of consecutive CRBs. According to some embodiments, methods, systems, and devices may configure one or more bandwidth parts for a secondary cell (SCell). In some embodiments, a user equipment (UE) may receive a first radio resource control (RRC) message including one or more configuration parameters for a first bandwidth part (BWP) associated with a secondary cell (SCell). The UE may communicate a first message with the SCell via the first SCell BWP. The UE may receive a second RRC message indicating a change from the first SCell BWP to a second SCell BWP to be used for SCell communication. The UE may communicate a second message with the SCell via the second SCell BWP.

[0004] In some embodiments, a UE includes: a transceiver configured to perform wireless communications over a wireless network; and one or more processors coupled to the transceiver. The one or more processors may be configured to: receive a first RRC message including one or more configuration parameters for a first BWP associated with an SCell; and communicate the first message with the SCell via the first SCell BWP using the transceiver. The one or more processors may be further configured to: receive a second RRC message indicating a change from the first SCell BWP to a second SCell BWP to be used for SCell communications; and communicate a second message with the SCell via the second SCell BWP using the transceiver.

[0005] In some embodiments, a non-transitory, tangible, computer-readable medium has instructions stored thereon that, when executed by a processor of a UE, cause the UE to perform operations. The operations may include: receiving a first RRC message including one or more configuration parameters for a first BWP associated with a secondary cell (SCell); processing the first RRC message including configuring the UE to communicate with the SCell using the first SCell BWP; communicating the first message with the SCell via the first SCell BWP; receiving a second RRC message indicating a change from the first SCell BWP to a second SCell BWP to be used for SCell communication; processing the second RRC message including reconfiguring the UE to communicate with the SCell using the second SCell BWP; and communicating a second message with the SCell via the second SCell BWP.

[0006] In some embodiments, the UE processing the first RRC message includes configuring the UE to communicate with the SCell using the first SCellBWP, and the UE processing the second RRC message includes reconfiguring the UE to communicate with the SCell using the second SCellBWP. In some embodiments, after the reconfiguration, the UE may receive an SCell deactivation message via a MAC CE and process the deactivation message by deactivating all BWPs associated with the SCell. In some embodiments, the first message and the second message each include at least one of the following: an uplink shared channel, a downlink shared channel, a control channel, a channel state information report, or a sounding reference signal. In some embodiments, the UE does not deactivate the SCell after processing the first RRC message and before processing the second RRC message.

[0007] In some embodiments, the UE communicates with a primary cell (PCell), wherein the SCell provides secondary radio resources that supplement the primary radio resources provided by the PCell, and wherein the UE receives the first RRC message from the PCell. In some embodiments, the UE may receive a third RRC message, the third RRC message including one or more configuration parameters for a first PCell BWP, and processing the third RRC message includes configuring the UE to communicate with the PCell using the first PCell BWP. The UE may receive a fourth RRC message indicating a change from the first PCell BWP to a second PCell BWP, and processing the fourth RRC message includes reconfiguring the UE to communicate with the PCell using the second PCell BWP.

[0008] According to some embodiments, enabling a UE to reconfigure one or more BWPs is performed without requiring deactivation of the SCell. For example, the UE may activate a previously inactive BWP and deactivate a previously active BWP for the SCell. This enables the UE to receive update and reconfiguration messages in the communication network to change the active BWP for the SCell while minimizing signaling and processing delays that would occur if the SCell had to be deactivated. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Figure 1 An example system is shown that implements a design for downlink (DL) and uplink (UL) BWP switching for SCells in accordance with some aspects of the present disclosure.

[0010] Figure 2 Spectra and sets of BWPs for implementing downlink (DL) and uplink (UL) messaging including BWP switching for SCells are shown in accordance with some aspects of the present disclosure.

[0011] Figure 3 A signaling diagram illustrating example operations of BWP switching according to aspects of the present disclosure.

[0012] Figure 4A and Figure 4B A signaling diagram illustrating alternative operation of BWP handover according to aspects described herein.

[0013] Figure 5 An example method 500 is shown for a system (eg, a base station) supporting mechanisms for downlink (DL) and uplink (UL) BWP switching, according to some aspects of the present disclosure.

[0014] Figure 6 A block diagram illustrating an example system of an electronic device implementing mechanisms for downlink (DL) and uplink (UL) BWP switching according to aspects of the present disclosure is shown.

[0015] Figure 7 An exemplary computer system for implementing various embodiments is depicted. DETAILED DESCRIPTION

[0016] Some aspects of the present disclosure include apparatus and methods for BWP handover, including reconfiguration of SCell communications for 3rd Generation Partnership Project (3GPP) releases such as Release 16 (Rel-16), Release 17 (Rel-17) and other current / future 3GPP standards.

[0017] Figure 1An exemplary system 100 is shown that implements a design for downlink (DL) and uplink (UL) BWP switching for SCells according to some aspects of the present disclosure. Exemplary system 100 is provided for illustrative purposes only and does not limit the disclosed aspects. System 100 may include, but is not limited to, a network node (e.g., a base station such as an eNB, gNB, etc.) 101, a network node 102, and an electronic device (e.g., a UE) 105. Electronic device 105 (hereinafter referred to as UE 105) may include an electronic device configured to operate based on a variety of wireless communication technologies. These technologies may include, but are not limited to, technologies based on Third Generation Partnership Project (3GPP) standards. For example, UE 105 may include an electronic device configured to operate using a 3GPP release, such as Release 17 (Rel-17), or other current or future 3GPP standards. UE 105 may include, but is not limited to, a wireless communication device, a smartphone, a laptop, a desktop computer, a tablet, a personal assistant, a monitor, a television, a wearable device, an Internet of Things (IoT), a vehicular communication device, and the like. The network node 101 may be a PCell base station 101 and the network node 102 may be an SCell base station 102, both of which may be configured to operate based on a variety of wireless communication technologies (such as, but not limited to, technologies based on 3GPP standards). For example, the PCell base station 101 and / or the SCell base station 102 may include nodes configured to operate using a 3GPP release (such as Rel-17) or other current or future 3GPP standards. The UE 105 may be connected to the PCell base station 101 and the SCell base station 102 and may communicate with these base stations using one or more communication links 107 and 108.

[0018] Some aspects of the present disclosure relate to new numerologies (e.g., μ values ​​in 3GPP Technical Specification (TS) 38.211) for operating in a frequency range above 52.6 GHz (e.g., one or more frequencies in a frequency range between approximately 52.6 GHz and approximately 71 GHz). Some aspects of the present disclosure relate to addressing the impact on physical signals / channels in a frequency range above 52.6 GHz. For example, some aspects of the present disclosure discuss timeline-related aspects applicable to each of the new numerologies, such as bandwidth part (BWP) and beam switching time, hybrid automatic repeat request (hybrid ARQ or HARQ) scheduling, UE processing, preparation and calculation time for physical downlink shared channel (PDSCH), physical uplink shared channel (PUSCH) / sounding reference signal (SRS), and channel state information (CSI), etc. Some aspects of the present disclosure relate to switching the BWP utilized by a user equipment (UE). In New Radio (NR), the total bandwidth of a cell may be divided into BWPs utilized by UEs, such as wireless devices, to reduce UE power consumption for UEs capable of receiving the maximum carrier bandwidth, or to allow a subset of the full bandwidth to be achieved by other UEs, where scanning the full NR bandwidth would consume excessive power.

[0019] A BWP may be activated to define the operating bandwidth of the UE within the operating bandwidth of the cell, while other BWPs may be configured but deactivated. Only one BWP in the downlink (DL) and one BWP in the uplink (UL) may be activated at a time. To reconfigure the active BWP for a secondary cell (SCell) in legacy NR, the SCell is first deactivated. Subsequently, the SCell is activated on the new BWP, and the waiting time / delay to reconfigure the active BWP includes the overhead of such deactivation / activation signaling and processing. Some aspects of the present disclosure relate to BWP switching for SCell enhancement / optimization of PDSCH / PUSCH, such as, but not limited to, supporting UL scheduling if frequency domain resource allocation with a granularity different from FR1 / 2 is supported (e.g., sub-physical resource blocks (PRBs) or more than one PRB). Some aspects of the present disclosure relate to time domain scheduling enhancements for PDSCH / PUSCH, such as, but not limited to, increasing the minimum time domain scheduling unit to be larger than one symbol, supporting multiple PDSCHs scheduled by one downlink control information (DCI), supporting one transport block (TB) mapped to multiple time slots (i.e., transmission time interval (TTI) bundling), etc. Some aspects of the present disclosure relate to enhancements and / or alternatives to the BWP switching mechanism to reduce the BWP switching latency due to SCell deactivation and reactivation overhead.

[0020] like Figure 2As shown, spectrum 200 is divided for use including cell band 210 and non-cell band 211. At least a portion of cell band 210 may be allocated for use by user equipment (UE) of a communication network. Cell band 210 may be subdivided into a plurality of cell bandwidths 220 (e.g., cell operating bandwidths 221, 222, and so on). The cell operating bandwidths may be used by a UE (e.g., UE 105) for communication between UE 105 and exemplary system 100 (e.g., PCell base station 101 and / or SCell base station 102).

[0021] The UE 105 may be configured to utilize a subset of the cell operating bandwidth. For example, the UE may be configured to utilize Figure 2 222 is shown. To minimize power consumption, the UE 105 may be further configured with multiple downlink BWPs (e.g., one to four DL BWPs 230 indexed as DL BWPs 0 to n) and multiple uplink BWPs (e.g., one to four UL BWPs 231 indexed as UL BWPs 0 to n) for each serving cell. In some embodiments, a cell may be configured with up to four additional uplink BWPs on a supplementary uplink (SUL) carrier (not shown). As described above, dividing the operating bandwidth into BWPs may minimize and / or reduce power consumption. For example, in an embodiment, to minimize UE power consumption, a single DL BWP and a single UL BWP may be active on an active serving cell at a given time.

[0022] The active BWP defines the UE's operating bandwidth (e.g., for DL ​​and UL) within the cell's operating bandwidth. All other configured BWPs may be deactivated so that the UE does not transmit or receive any data on the deactivated BWP. In some embodiments, the UE 105 may receive the Physical Downlink Shared Channel (PDSCH), Physical Downlink Control Channel (PDCCH), or Channel State Information Reference Signal (CSI-RS) within the active DL BWP. The UE 105 may also perform radio resource management (RRM) measurements outside the active DL BWP (e.g., via measurement gaps). In some embodiments, the UE 105 may transmit the Physical Uplink Shared Channel (PUSCH) and / or Physical Uplink Control Channel (PUCCH) within the active UL BWP. In some embodiments, for the active serving cell, the UE 105 does not transmit a Sounding Reference Signal (SRS) outside the active UL BWP.

[0023] In some embodiments, a BWP pair includes an active UL BWP and an active DL BWP with the same center frequency. The network can dynamically switch the UE to the desired BWP as needed. A BWP is formed by a set of contiguous resource blocks (e.g., RB1 to RBn for DL ​​BWP 1 and RB1 to RBn for UL BWP 1). In some embodiments, the UE 105 is configured to schedule communications only within active BWPs (such as DL BWP 1 and / or UL BWP 1). The UE 105 does not schedule communications on deactivated BWPs.

[0024] In some examples, a BWP indicator can be used to identify a specific BWP for resource allocation (which can be used for BWP switching). According to some aspects, the resource allocation type specifies how the scheduler allocates resource blocks for each transmission. For example, DL / UL resource allocation type 0 may indicate a set of allocated resource block groups (RBGs). In some examples, an RBG may be a set of contiguous virtual resource blocks (VRBs). In some examples, in resource allocation type 1, resources are allocated to one or more contiguous RBs. UE 105 may be configured by higher layers of the serving cell via parameters (e.g., DL-BWP) with a set of BWPs (e.g., a DL BWP group) for reception by UE 105 in the DL bandwidth. UE 105 may be configured with a set (e.g., four) of BWPs for transmissions by UE 105 in the UL bandwidth (e.g., a UL BWP group) via parameters for the serving cell (e.g., UL-BWP).

[0025] For example, if the UE 105 has a dedicated BWP configuration, the network (e.g., PCell base station 101) may provide the UE 105 (e.g., by higher layers) with parameters for the first active UL BWP for transmissions on the SCell. For example, the PCell base station 101 may provide the UE 105 with parameters such as Active-BWP-UL-Scell, firstActiveDownlinkBWP-Id, etc. to indicate the first active UL BWP for SCell transmissions. The higher layer parameter (e.g., firstActiveDownlinkBWP-Id) may indicate the first active DL BWP for reception. The UE 105 may be provided with a second higher layer parameter (e.g., firstActiveUplinkBWP-Id) that may indicate the first active UL BWP for transmissions on the primary cell.

[0026] RRC-based BWP switching (i.e., reconfiguration via RRC) is possible for both UL and DL. A single BWP identity (ID) is configured as active. For example, the UE may receive an indicator from the base station with the fields firstActiveDownlinkBWP-Id or firstActiveUplinkBWP-Id to identify the first active BWP for DL ​​and UL, respectively. Furthermore, the configured BWP ID may be reconfigured in the downlinkBWP-ToAddModList or uplinkBWP-ToAddModList.

[0027] More specifically, for SCell, Technical Specification (TS) 38.331 section 6.3.2 defines firstActiveDownlinkBWP-Id: If configured for SCell, this field contains the ID of the downlink bandwidth part to be used when activating the SCell. The initial bandwidth part is indicated by BWP-Id=0. Similarly, firstActiveUplinkBWP-Id is defined as containing the ID of the uplink bandwidth part to be used when activating the SCell. The initial bandwidth part is indicated by BandwidthPartId=0. In other words, for SCell, firstActiveDownlinkBWP-Id or firstActiveUplinkBWP-Id is only used when the SCell is activated. For RRC-based handover for Scell, firstActiveDownlinkBWP-Id or firstActiveUplinkBWP-Id cannot be changed by RRC reconfiguration unless SCell deactivation and reactivation are performed.

[0028] A BWP can be configured for a special cell (SpCell) or a secondary cell (SCell). An SpCell can refer to a primary cell (PCell) with which a UE establishes / reestablishes a connection in a master cell group (MCG). An SpCell can also refer to a primary SCG cell (PSCell) with which a UE performs random access for RRC reconfiguration in a secondary cell group (SCG). An SCell provides secondary radio resources that supplement the primary resources provided by an SpCell (such as a PCell or PSCell). Embodiments described herein disclose systems, methods, and devices for reconfiguring an SCell BWP (i.e., the active or first active BWP) using the firstActiveDownlinkBWP-Id or firstActiveUplinkBWP-Id fields without deactivating and reactivating the SCell.

[0029] Activating an inactive BWP and deactivating an active BWP is performed through BWP switching. According to some embodiments, for an SCell, when multiple BWP IDs are configured, BWP switching can be performed by changing the firstActiveDownlinkBWP-Id or firstActiveUplinkBWP-Id of one of the configured BWP-Ids. As mentioned above, it is not possible to activate more than one BWP at a time.

[0030] However, TS 38.331 describes that the PCell and PSCell are different, and the configurations firstActiveDownlinkBWP-Id and firstActiveUplinkBWP-Id indicate the ID of the DL / UL BWP to be used when activating the SCell. The initial DL BWP and initial UL BWP are used at least for initial access before a radio resource control (RRC) connection is established. In some implementations, the initial BWP has an index of zero and is referred to as BWP 0 (e.g., DL BWP 0 and UL BWP 0). During initialization, the UE performs a cell search based on a synchronization signal block (SSB) signal consisting of at least a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a physical broadcast channel (PBCH). To access the system, the UE needs to further read system information block 1 (SIB1) to obtain the initial DL / UL BWP configuration. SIB1 is transmitted on the PDSCH and is scheduled by downlink control information (DCI) on the PDCCH using a control resource set (CORESET#0) with an index of zero.

[0031] Before the UE reads SIB1, the UE's initial DL BWP has the same frequency range and numerology as CORESET#0. The UE then obtains the initial DL / UL BWP configuration in SIB1 to perform a random access procedure to request the establishment of an RRC connection. The first active DL and UL BWPs can be configured for a special cell (SpCell) or a secondary cell (SCell). The first active DL and UL BWPs are the active DL and UL BWPs at the time of RRC reconfiguration for the SpCell. The base station can configure the UE with a BWP inactivity timer for the SpCell. The expiration of this timer can, for example, indicate that the UE temporarily has no scheduled transmission and reception on the current active BWP. Therefore, the UE can switch its active BWP to a default BWP to save power. The default DL BWP can be configured. If not configured, the UE uses the initial DL BWP as the default DL BWP.

[0032] Figure 3is a signaling diagram of an exemplary process for BWP switching for SCell according to an embodiment of the present disclosure. As described above, SCell provides secondary radio resources that supplement the primary resources provided by SpCell (such as PCell or PSCell). Traditionally, the first active DL and UL BWPs are active DL and UL BWPs only when the SCell is activated. As described in more detail below, reference Figure 4A and Figure 4B This configuration may lead to latency and poor network performance. Specifically, by requiring deactivation of the SCell and reactivation of the SCell before setting the first active DL and UL BWPs, additional signaling and processing overhead is required for BWP switching in the SCell.

[0033] In order to avoid the increased signaling and processing overhead of SCell deactivation and activation, Figure 3 An exemplary embodiment is shown in which a UE is configured to activate a BWP based on SCell activation and perform BWP switching without deactivating and reactivating the SCell. Advantages are achieved by avoiding SCell deactivation and reactivation to change firstActiveDownlinkBWP-Id and firstActiveUplinkBWP-ID. Some embodiments described herein can reduce the total time required to switch BWPs. In the example shown, the proposed method can have a better performance than Figure 4A and Figure 4B The switching delay is shorter.

[0034] Reference Figure 3 UEs, such as wireless devices, can be configured to operate in the BWPs of the PCell and SCell. BWP configuration and BWP switching can be performed on the SCell. For SCell activation, in signal 310, the PCell base station 301 can send (e.g., transmit) one or more messages (e.g., one or more RRC messages) including an SCell activation message (e.g., via RRC) to the UE 305 to configure the BWP of the SCell. In some embodiments, the DL BWP and UL BWP can be switched separately. In other embodiments, paired DL BWP and UL BWP are switched together.

[0035] For example, the SCell activation message may include an indicator of firstActiveDownlinkBWP-ID that specifies the identifier of the first active downlink BWP. In this example, the PCell base station 301 instructs the UE to set firstActiveDownlinkBWP-ID to 1. Although not shown, additionally or alternatively, for example, the SCell activation message may include an indicator of firstActiveUpinkBWP-ID that specifies the identifier of the first active uplink BWP (i.e., firstActiveUpinkBWP-ID=1). The SCell activation message may configure multiple BWPs (e.g., multiple BWPs including DL BWP 0, DL BWP 1, DL BWP 2, DL BWP 3, UL BWP 0, UL BWP 1, UL BWP 2, and UL BWP 3). DL (and / or UL) BWP 0 may be a default BWP. DL (and / or UL) BWP 1 may be an initial active BWP (e.g., an initial DL BWP or an initial UL BWP). The UE 305 may determine a number of BWPs configured for the SCell, for example, based on the one or more messages 310m.

[0036] Upon receiving the SCell activation message 310, the UE 305 is enabled to receive PDSCH communications from the SCell base station 302 in signal 315. In this case, the UE 305 receives the PDSCH message from the SCell base station 302 on the first BWP (i.e., the BWP enumerated as DL BWP 1).

[0037] The PCell base station 301 or the SCell base station 302 may send a DL assignment. The DL assignment may be sent via DL BWP 1 (e.g., an initial DL BWP). The UE 305 may receive packets via DL BWP 1 (or another active DL BWP), for example, based on the DL assignment. The UE 305 may, for example, start a BWP inactivity timer after receiving a scheduled downlink packet.

[0038] Although not shown, additionally or alternatively, the PCell base station 301 or the SCell base station 302 may transmit an UL grant via UL BWP 1 (e.g., the first UL BWP or the initial DL BWP). The UE 305 may transmit a packet via UL BWP 1 (e.g., the first UL BWP or the initial UL BWP) based on the UL grant. The UE 305 may, for example, start a BWP inactivity timer after transmitting a scheduled uplink packet.

[0039] If it is determined to perform BWP switching for the SCell, the PCell base station 301 transmits an SCell reconfiguration message to the UE 305 via RRC to reconfigure the SCell BWP. For example, at operation 320, the PCell base station 301 may send an RRC reconfiguration message for BWP switching (e.g., BWP switching from DL BWP 1 to DL BWP 2). For example, the RRC reconfiguration message may be included in a DCI message. The SCell reconfiguration message may be sent via the active DL BWP 1. The SCell reconfiguration message may include an indicator, firstActiveDownlinkBWP-ID, indicating that the UE sets the firstActiveDownlinkBWP-ID for the SCell to 2. To perform the SCell BWP switching, the UE 305 may, for example, switch DL BWP 1 to DL BWP 2 based on the RRC reconfiguration message. The UE 305 may receive the RRC reconfiguration message, for example, by monitoring the PDCCH on the active DL BWP 1. The UE 305 may switch the DL BWP 1 to the DL BWP 2, for example, based on the RRC reconfiguration message 320m.

[0040] There may be a delay between the wireless device receiving the RRC reconfiguration message 320m and the wireless device switching to DL BWP 2. For example, after the BWP switch, the UE 305 may start and / or restart the BWP inactivity timer. The PCell base station 301 or the SCell base station 302 may resend the DL assignment. The DL assignment may be sent via DL BWP 2 (e.g., a second DL BWP or another BWP activated by the BWP switch). The UE 305 may receive packets via DL BWP 2 (or another active DL BWP), for example, based on the DL assignment.

[0041] For example, if the wireless device does not perform reception or transmission for a period of time, the BWP inactivity timer may expire. UE 305 may switch from DL BWP 2 to DL BWP 0 (e.g., the default BWP). Falling back to DL BWP 0 may occur, for example, after the BWP inactivity timer expires. There may be a delay between the expiration of the BWP inactivity timer and the wireless device switching to DL BWP 0. In some embodiments, PCell base station 301 may transmit an SCell deactivation message to UE 305. For example, a base station such as PCell base station 301 may transmit one or more signals including a deactivation message to UE 305. In some embodiments, the deactivation message may be transmitted in a Medium Access Control (MAC) Control Element (CE). For example, PCell base station 301 may send the deactivation message via a MAC CE, which triggers UE 305 to deactivate all BWPs or, alternatively, to use a default BWP (e.g., DL BWP 0 and / or UL BWP 0).

[0042] Figure 4A and Figure 4B FIG2 is a signaling diagram of an exemplary process for BWP switching of an SCell. As shown in the figure, the UE is configured to activate the BWP based on SCell activation and perform BWP switching through deactivation and reactivation of the SCell.

[0043] like Figure 4A As shown, for activation of the SCell, in signal 410, the PCell base station 401 may send (e.g., transmit) one or more messages (e.g., one or more RRC messages) including a SCell activation message (e.g., via RRC) to the UE 405 for configuring the BWP of the SCell.

[0044] For example, the SCell activation message may include an indicator of firstActiveDownlinkBWP-ID that specifies the identifier of the first active downlink BWP. In this example, the PCell base station 401 instructs the UE to set firstActiveDownlinkBWP-ID to 1. Although not shown, additionally or alternatively, for example, the SCell activation message may include an indicator of firstActiveUpinkBWP-ID that specifies the identifier of the first active uplink BWP (i.e., firstActiveUpinkBWP-ID=1). The SCell activation message may configure multiple BWPs (e.g., including DL BWP 0, DL BWP 1, DL BWP 2, DL BWP 3, UL BWP 0, UL BWP 1, UL BWP 2, and UL BWP 3 shown in Table 408). DL (and / or UL) BWP 0 may be a default BWP. DL (and / or UL) BWP 1 may be an initial active BWP (e.g., an initial DL BWP or an initial UL BWP). The UE 405 may determine a number of BWPs configured for the SCell, for example, based on the one or more messages 410m.

[0045] Upon receiving the SCell activation message, UE 405 is able to receive PDSCH communications from SCell base station 402 in signal 415. In this case, UE 405 receives the PDSCH message from SCell base station 402 on the first BWP (ie, the BWP enumerated as DL BWP 1).

[0046] PCell base station 401 or SCell base station 402 may send a DL assignment. The DL assignment may be sent via DL BWP 1 (e.g., an initial DL BWP). UE 405 may receive packets, for example, via DL BWP 1 or via another active DL BWP based on the DL assignment. UE 405 may start a BWP inactivity timer. UE 405 may start a BWP inactivity timer, for example, after receiving a scheduled downlink packet.

[0047] Although not shown, PCell base station 401 or SCell base station 402 may additionally or alternatively send an UL grant. The UL assignment may be sent via UL BWP 1 (e.g., the first UL BWP or the initial DL BWP). UE 405 may, for example, send a packet via UL BWP 1 (e.g., the first UL BWP or the initial UL BWP) based on the UL grant. UE 405 may start a BWP inactivity timer.

[0048] If a BWP switch for the SCell is determined to be performed, PCell base station 401 transmits an SCell reconfiguration message to UE 405 via RRC in signal 420 to reconfigure the SCell BWP. For example, in signal 420, the SCell reconfiguration message may include an indicator, firstActiveDownlinkBWP-ID, indicating that the UE sets the firstActiveDownlinkBWP-ID for the SCell to 2. In this regard, to perform the SCell BWP switch, UE 405 needs to deactivate and reactivate the SCell under the new BWP-ID. For example, rather than PCell base station 401 immediately reconfiguring the active BWP, base station 401 may first transmit an RRC reconfiguration message for a BWP switch (e.g., a BWP switch from DL BWP 1 to DL BWP 2) in signal 420 to indicate to UE 405 the upcoming BWP switch for the SCell. The RRC reconfiguration message may be included in a DCI message. The SCell reconfiguration message may be transmitted via active DL BWP 1.

[0049] Subsequently, at operation 430, to perform BWP switching for the SCell, the PCell base station 401 causes the UE to deactivate with respect to the SCell. In some embodiments, a base station, such as the PCell base station 401, may transmit one or more signals including a deactivation message to the UE 405. In some embodiments, the deactivation message is transmitted in a MAC CE. For example, the PCell base station 401 may send a deactivation message via a MAC CE, which triggers the UE 405 to deactivate all BWPs or, alternatively, to use a default BWP (e.g., DL BWP 0 and / or UL BWP 0).

[0050] Then, according to TS 38.331, at signal 440, PCell base station 401 sets a new first active BWP ID, activating (i.e., reactivating) the SCell. For example, PCell base station 401 transmits an SCell activation message to UE 405 via RRC to reactivate the SCell BWP. For example, at signal 440, the SCell reconfiguration message may include an indicator firstActiveDownlinkBWP-ID, indicating that the UE sets the firstActiveDownlinkBWP-ID for the SCell to 2. UE 405 may, for example, switch DL BWP 1 to DL BWP 2 based on RRC reconfiguration message 420m. UE 405 may, for example, receive the RRC reconfiguration message by monitoring the PDCCH on active DL BWP 1. UE 405 may, for example, switch DL BWP 1 to DL BWP 2 based on RRC reconfiguration message 420m.

[0051] Similarly, to perform an SCell BWP switch, the UE is required to deactivate the SCell. In some aspects, the UE 405 must wait for certain operations to be performed before deactivating the SCell. For example, the UE 405 may maintain BWP 1 to complete the DL scheduling grant, time based on the BWP inactivity timer, and / or other signaling delays, processing delays, etc. There may be a delay between the wireless device receiving DCI 420m and the wireless device switching to DL BWP 2. For example, after the BWP switch, the UE 405 may start and / or restart the BWP inactivity timer. For example, if the wireless device does not perform reception or transmission for a period of time, the BWP inactivity timer may expire. The UE 405 may switch DL BWP 2 to DL BWP 0 (e.g., the default BWP). Falling back to DL BWP 0 may occur, for example, after the BWP inactivity timer expires. There may be a delay between the expiration of the BWP inactivity timer and the wireless device switching to DL BWP 0.

[0052] Alternatively, if Figure 4B As shown, UE 405 is configured to activate the BWP for the SCell and perform BWP switching by deactivating and reactivating the SCell. In this embodiment, the BWP switching occurs by deactivating and reactivating the SCell without transmitting an RRC reconfiguration message, such as in signal 420. In this regard, in signal 450, the PCell base station 401 may send (e.g., transmit) one or more messages (e.g., one or more RRC messages) including an SCell activation message (e.g., via RRC) to the UE 405 for configuring the BWP of the SCell.

[0053] For example, the SCell activation message may include an indicator of firstActiveDownlinkBWP-ID that specifies the identifier of the first active downlink BWP. In this example, the PCell base station 401 instructs the UE to set firstActiveDownlinkBWP-ID to 1. Although not shown, additionally or alternatively, for example, the SCell activation message 450m may include an indicator of firstActiveUpinkBWP-ID that specifies the identifier of the first active uplink BWP (i.e., firstActiveUpinkBWP-ID=1). As described above, DL (and / or UL) BWP 0 may be the default BWP, and DL (and / or UL) BWP 1 may be the initial active BWP (e.g., the initial DL BWP or the initial UL BWP). Upon receiving the SCell activation message, in signal 455, the UE 405 is enabled to receive PDSCH communications from the SCell base station 402. The UE 405 may receive PDSCH messages from the SCell base station 402 on the first BWP (i.e., the BWP enumerated as DL BWP 1).

[0054] PCell base station 401 or SCell base station 402 may send a DL assignment. The DL assignment may be sent via DL BWP 1 (e.g., the initial DL BWP). UE 405 may receive packets, for example, based on the DL assignment, via DL BWP 1 or via another active DL BWP. As described above, the same applies to UL assignments. UE 405 may start a BWP inactivity timer. UE 405 may start the BWP inactivity timer, for example, after receiving a scheduled downlink packet.

[0055] If it is determined to perform BWP switching for the SCell, the PCell base station 401 deactivates the SCell at operation 460. For example, the PCell base station 401 may send a deactivation message (e.g., via a MAC CE) that triggers the UE 405 to deactivate all BWPs, or alternatively use a default BWP (e.g., DL BWP 0 and / or UL BWP 0).

[0056] As described above, at operation 480, PCell base station 401 sets a new first active BWP ID, activating (i.e., reactivating) the SCell. For example, PCell base station 401 transmits an SCell activation message to UE 405 via RRC to reactivate the SCell BWP. For example, at signal 420, the SCell reconfiguration message may include an indicator, firstActiveDownlinkBWP-ID, indicating that the UE sets the firstActiveDownlinkBWP-ID for the SCell to 2. UE 405 may, for example, switch DL BWP 1 to DL BWP 2 based on RRC configuration message 470m. UE 405 may receive the RRC reconfiguration message, for example, by monitoring the PDCCH on active DL BWP 1. UE 405 may, for example, switch DL BWP 1 to DL BWP 2 based on RRC configuration message 470m.

[0057] Similarly, to perform an SCell BWP switch, the UE is required to deactivate the SCell. In some aspects, the UE 405 must wait for certain operations to be performed before deactivating the SCell. For example, the UE 405 may remain in BWP 1 until the completion of a DL scheduling grant, the time according to a BWP inactivity timer, and / or other signaling delays, processing delays, etc. There may be a delay between the wireless device receiving the RRC configuration message 470m and the wireless device switching to DL BWP 2. For example, after the BWP switch, the UE 405 may start and / or restart the BWP inactivity timer. For example, if the wireless device does not perform reception or transmission for a period of time, the BWP inactivity timer may expire. The UE 405 may switch DL BWP 2 to DL BWP 0 (e.g., the default BWP). Falling back to DL BWP 0 may occur, for example, after the BWP inactivity timer expires. There may be a delay between the expiration of the BWP inactivity timer and the wireless device switching to DL BWP 0. The BWP is described as an example resource, and any wireless resource may be applicable to one or more of the procedures described herein.

[0058] Figure 5 An exemplary method 500 of a system (eg, a base station) for supporting a mechanism for downlink (DL) and uplink (UL) BWP switching for SCells according to some aspects of the present disclosure is shown. For convenience and not limitation, reference may be made to Figures 1 to 3 、 Figure 5 and Figure 6 Description of the elements Figure 5 The method 500 may be representative of an electronic device (eg, a method for implementing a mechanism for implementing downlink (DL) and uplink (UL) BWP switching for a SCell) Figure 1Method 500 may also be performed by Figure 6 However, the method 500 is not limited to the specific aspects depicted in those figures, and other systems may be used to perform the method, as will be understood by those skilled in the art. It should be understood that not all operations may be required, and that these operations may not be performed in the same manner as described above. Figure 5 Execute in the same order as shown.

[0059] At 502, the base station configures the UE for communication via the SCell. In some embodiments, the UE receives a message from the base station, such as a first RRC message, including one or more configuration parameters. These parameters may include configuration information for configuring multiple BWP IDs for the SCell for RRC-based handover. In some embodiments, the configuration parameters may include firstActiveDownlinkBWP-Id or firstActiveUplinkBWP-Id at 502, which may be used to indicate the first active BWP upon SCell activation. For example, the SCell activation message may include an indicator of firstActiveDownlinkBWP-ID, which specifies the identifier of the first active downlink BWP. Additionally or alternatively, for example, the SCell activation message may include an indicator of firstActiveUplinkBWP-ID, which specifies the identifier of the first active uplink BWP. The SCell activation message may configure one or more BWPs (e.g., multiple BWPs including DL BWP 0, DL BWP 1, DL BWP 2, DL BWP 3, UL BWP 0, UL BWP 1, UL BWP 2, and UL BWP 3). DL (and / or UL) BWP 0 may be a default BWP. As shown in message 310m, for example, DL (and / or UL) BWP 1 may be an initial active BWP (eg, an initial DL BWP or an initial UL BWP).

[0060] Upon receiving the SCell activation message, at 504, the UE is enabled to transmit and receive one or more communications with the SCell. The UE may thereby transmit and / or receive one or more communications. For example, the one or more communications may include an uplink shared channel, a downlink shared channel, a control channel, a channel state information report, a sounding reference signal, and the like. For example, the UE 305 is configured to receive messages (PUSCH, PDSCH, etc.) from the SCell base station 302 on a first BWP (i.e., the BWP enumerated as DL BWP 1). The PCell base station 301 or the SCell base station 302 may send DL or UL assignments via a DL BWP or a UL BWP, respectively. For example, the UE 305 may receive a DL assignment associated with DL BWP 1 and then receive packets based on the DL assignment via DL BWP 1 (or another active DL BWP). The UE 305 may start a BWP inactivity timer.

[0061] At 506, if it is determined that a BWP handover for the SCell is to be performed, the PCell 301 transmits an SCell reconfiguration message to the UE 305 via RRC to reconfigure the SCell BWP. In some embodiments, the UE receives a second RRC message from a base station, such as the PCell base station 301, including one or more configuration parameters. These parameters may include configuration information for changing the active BWP during an RRC-based BWP handover. In some embodiments, the configuration parameters may include the firstActiveDownlinkBWP-Id or firstActiveUplinkBWP-Id at 502, which may be used to indicate the first active BWP.

[0062] For example, in the Figure 3 At operation 320 discussed, the PCell base station 301 may send an RRC reconfiguration message for a BWP switch (e.g., a BWP switch from DL BWP 1 to DL BWP 2). For example, the RRC reconfiguration message may be included in a DCI message. The SCell reconfiguration message may be sent via the active DL BWP 1. The SCell reconfiguration message may include an indicator firstActiveDownlinkBWP-ID, indicating that the UE sets the firstActiveDownlinkBWP-ID for the SCell to 2. To perform the SCell BWP switch, the UE 305 may, for example, switch the DL BWP 1 to the DL BWP 2 based on the RRC reconfiguration message. The UE 305 may, for example, receive the RRC reconfiguration message by monitoring the PDCCH on the active DL BWP 1. The UE 305 may, for example, switch the DL BWP 1 to the DL BWP 2 based on the RRC reconfiguration message 320m.

[0063] For example, at 506, the base station configures and / or reconfigures the UE to perform BWP switching for the SCell. UE 305 receives one or more RRC reconfiguration messages from PCell base station 301 to cause the UE to perform a BWP switching operation. For example, UE 305 receives an RRC reconfiguration message from PCell base station 101 that includes an indicator of the firstActiveDownlinkBWP-Id or firstActiveUplinkBWP-Id for the SCell. This goes beyond the case where the base station transmits a configuration message that specifies the firstActiveDownlinkBWP-Id or firstActiveUplinkBWP-Id for the SCell that is only valid for SCell activation. Specifically, in method 500, the firstActiveDownlinkBWP-Id or firstActiveUplinkBWP-Id for the SCell can be valid for both SCell activation and for RRC-based switching via reconfiguration. If the SCell has been previously activated, the RRC reconfiguration message causes the UE to reconfigure firstActiveDownlinkBWP-Id or firstActiveUplinkBWP-Id to another configured BWP-Id to perform RRC-based BWP switching for the SCell. Figure 2 , the UE switches from DL BWP 1 to DL BWP 2, and / or from UL BWP 1 to UL BWP 2, and thus configures itself to communicate wirelessly on DL BWP 2 and / or UL BWP 2. BWP reconfiguration may include radio tuning and will be understood by those skilled in the art.

[0064] At 508, after receiving the SCell reconfiguration message, and without deactivating the SCell, the UE can transmit and receive one or more communications with the SCell over the changed BWP. The UE can thereby transmit and / or receive one or more communications. For example, the one or more communications may include uplink shared channels, downlink shared channels, control channels, channel state information reports, sounding reference signals, and the like. For example, the UE 305 is configured to receive messages (PUSCH, PDSCH, etc.) from the SCell base station 302 over the changed BWP (i.e., the BWP enumerated as DL BWP2). The PCell base station 301 or the SCell base station 302 may send DL or UL assignments via the reconfigured DL BWP or UL BWP, respectively. For example, the UE 305 may maintain the active SCell (i.e., without deactivating the SCell) and receive DL assignments associated with DL BWP 2. The UE 305 may then receive packets via DL BWP 2 (or another active DL BWP) based on the DL assignments, having previously communicated on the SCell via DL BWP 1. According to these embodiments, the channel may be active and remain on the new BWP without first deactivating the SCell.In some embodiments, the SCell may be subsequently deactivated, for example, if the UE receives a deactivation message from the PCell base station 301 via a MAC CE.

[0065] Figure 6 A block diagram of an exemplary system 600 of an electronic device implementing a mechanism for downlink (DL) and uplink (UL) BWP switching for an SCell according to some aspects of the present disclosure is shown. System 600 can be any electronic device in the electronic devices of system 100 (e.g., base station 101, UE 105). System 600 includes a processor 610, one or more transceivers 620, communication infrastructure 640, memory 650, an operating system 652, an application 654, and one or more antennas 660. The illustrated system is provided as an exemplary portion of system 600, and system 600 may include other circuits and subsystems. Moreover, although the system of system 600 is shown as a single component, aspects of the present disclosure may include any combination of these components, fewer components, or more components.

[0066] The memory 650 may include random access memory (RAM) and / or cache memory, and may include control logic components (e.g., computer software) and / or data. The memory 650 may include other storage devices or memories, such as, but not limited to, a hard drive and / or a removable storage device / unit. According to some examples, an operating system 652 may be stored in the memory 650. The operating system 652 may manage the transfer of data from the memory 650 and / or one or more application programs 654 to the processor 610 and / or one or more transceivers 620. In some examples, the operating system 652 supports one or more network protocol stacks (e.g., an Internet protocol stack and a cellular protocol stack, etc.), which may include several logical layers. At the corresponding layer of the protocol stack, the operating system 652 includes control mechanisms and data structures to perform the functions associated with that layer.

[0067] According to some examples, applications 654 may be stored in memory 650. Applications 654 may include applications used by wireless system 600 and / or a user of wireless system 600 (e.g., user applications). Applications in applications 654 may include applications such as, but not limited to, Siri, TM , FaceTime TM , radio streaming, video streaming, remote control and / or other user applications.

[0068] System 600 may also include a communication infrastructure 640. Communication infrastructure 640 provides, for example, communication between processor 610, one or more transceivers 620, and memory 650. In some implementations, communication infrastructure 640 may be a bus. Processor 610, together with instructions stored in memory 650, executes instructions that enable system 600 of system 100 to implement mechanisms for downlink (DL) and uplink (UL) scheduling for transmissions above 52.6 GHz, as described herein, including operations for switching from a first BWP to a second BWP for an SCell.

[0069] According to some aspects, one or more transceivers 620 may be coupled to an antenna 660. Antenna 660 may include one or more antennas that may be of the same or different types. One or more transceivers 620 allow the system 600 to communicate with other devices that may be wired and / or wireless. In some examples, one or more transceivers 620 may include circuits / devices such as a processor, a controller, a radio component, a socket, a plug, a buffer, etc. for connecting to and communicating on a network. According to some examples, one or more transceivers 620 include one or more circuits for connecting to and communicating on a wired and / or wireless network.

[0070] According to some aspects of the present disclosure, the one or more transceivers 620 may include a cellular subsystem, a WLAN subsystem, and / or a Bluetooth subsystem. TM The subsystems each include their own radio transceiver and protocols, as will be understood by those skilled in the art based on the discussion provided herein. In some implementations, the one or more transceivers 620 may include more or fewer systems for communicating with other devices.

[0071] In some examples, transceiver(s) 620 may include one or more circuits, including a WLAN transceiver, to enable connection and communication via a WLAN network, such as, but not limited to, a network based on the standards described in IEEE 802.11.

[0072] Additionally, or alternatively, the one or more transceivers 620 may include a processor for implementing a communication protocol based on, for example, Bluetooth. TM Protocol, Bluetooth TM Low Energy Protocol or Bluetooth TM One or more circuits for connection and communication with low-power long-range protocols (including Bluetooth TM For example, the transceiver 620 may include a Bluetooth TM transceiver.

[0073] Additionally, the one or more transceivers 620 may include one or more circuits (including cellular transceivers) for connecting to and communicating on a cellular network. Cellular networks may include, but are not limited to, 3G / 4G / 5G networks, such as Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), etc. For example, the one or more transceivers 220 may be configured to operate in accordance with a 3GPP release, such as Rel-16, Rel-17, or other current / future 3GPP standards.

[0074] According to some aspects of the present disclosure, the processor 610, alone or in combination with computer instructions stored in the memory 650 and / or one or more transceivers 620, implements the methods and mechanisms discussed herein. For example, the processor 610, alone or in combination with computer instructions stored in the memory 650 and / or one or more transceivers 620, implements a mechanism for switching the active BWP for an SCell, as described herein. For example, the processor 610, alone or in combination with computer instructions stored in the memory 650 and / or one or more transceivers 620, implements a mechanism for performing BWP switching for an SCell without intervening deactivation of the SCell, as described herein.

[0075] Figure 7 An exemplary computer system for implementing various embodiments is depicted.

[0076] For example, one or more well-known computer systems such as Figure 7 The computer system 700 shown implements various embodiments. For example, one or more computer systems 700 can be used to implement any of the embodiments described herein, as well as combinations and subcombinations of the embodiments.

[0077] Computer system 700 may include one or more processors (also called central processing units or CPUs), such as processor 704. Processor 704 may be connected to a communication infrastructure or bus 706.

[0078] The computer system 700 may also include user input / output devices 703 , such as a monitor, keyboard, pointing device, etc., that can communicate with the communication infrastructure 706 through the user input / output interface 702 .

[0079] One or more of processors 704 may be a graphics processing unit (GPU). In an embodiment, a GPU may be a processor that is a specialized electronic circuit designed to process mathematically intensive applications. A GPU may have an efficient parallel architecture for processing large blocks of data in parallel, such as mathematically intensive data commonly found in computer graphics applications, images, videos, and the like.

[0080] The computer system 700 may also include a main memory or primary storage 708, such as random access memory (RAM). The main memory 708 may include one or more levels of cache. The main memory 708 may store control logic components (i.e., computer software) and / or data therein.

[0081] The computer system 700 may also include one or more secondary storage devices or memories 710. The secondary storage 710 may include, for example, a hard disk drive 712 and / or a removable storage device or drive 714. The removable storage drive 714 may be a floppy disk drive, a tape drive, an optical disk drive, an optical storage device, a tape backup device, and / or any other storage device / drive.

[0082] The removable storage drive 714 can interact with a removable storage unit 718. The removable storage unit 718 may include a computer-usable or readable storage device having computer software (control logic) and / or data stored thereon. The removable storage unit 718 may be a floppy disk, a magnetic tape, an optical disk, a DVD, an optical storage disk, and / or any other computer data storage device. The removable storage drive 714 can read from and / or write to the removable storage unit 718.

[0083] Secondary memory 710 may include other devices, apparatuses, components, tools, or other means for allowing computer programs and / or other instructions and / or data to be accessed by computer system 700. Such devices, apparatuses, components, tools, or other means may include, for example, a removable storage unit 722 and an interface 720. Examples of removable storage unit 722 and interface 720 may include a program cartridge and cartridge interface (such as found in video game devices), a removable memory chip (such as an EPROM or PROM) and an associated socket, a memory stick and USB port, a memory card and an associated memory card slot, and / or any other removable storage unit and associated interface.

[0084] The computer system 700 may also include a communication or network interface 724. The communication interface 724 may enable the computer system 700 to communicate and interact with any combination of external devices, external networks, external entities, and the like (individually and collectively referenced by reference numeral 728). For example, the communication interface 724 may allow the computer system 700 to communicate with an external or remote device 728 via a communication path 726, which may be wired and / or wireless (or a combination thereof) and may include any combination of a LAN, a WAN, the Internet, and the like. Control logic components and / or data may be transferred to and from the computer system 700 via the communication path 726.

[0085] The computer system 700 may also be any of, to name a few non-limiting examples, a personal digital assistant (PDA), a desktop workstation, a laptop or notebook computer, a netbook, a tablet computer, a smartphone, a smartwatch or other wearable device, an appliance, part of the Internet of Things, and / or an embedded system, or any combination thereof.

[0086] The computer system 700 can be a client or server accessing or hosting any application and / or data through any delivery paradigm, including but not limited to: remote or distributed cloud computing solutions; local or on-premises software ("on-premises" cloud-based solutions); "as a service" models (e.g., Content as a Service (CaaS), Digital Content as a Service (DCaaS), Software as a Service (SaaS), Management Software as a Service (MSaaS), Platform as a Service (PaaS), Desktop as a Service (DaaS), Framework as a Service (FaaS), Backend as a Service (BaaS), Mobile Backend as a Service (MBaaS), Infrastructure as a Service (IaaS), etc.); and / or hybrid models including any combination of the foregoing examples or other services or delivery paradigms.

[0087] Any suitable data structures, file formats, and schemas in the computer system 700 may be derived from standards including, but not limited to, JavaScript Object Notation (JSON), Extensible Markup Language (XML), another markup language (YAML), Extensible Hypertext Markup Language (XHTML), Wireless Markup Language (WML), MessagePack, XML User Interface Language (XUL), or any other functionally similar representation, alone or in combination. Alternatively, proprietary data structures, formats, or schemas may be used alone or in combination with known or open standards.

[0088] In some embodiments, a tangible, non-transitory device or article of manufacture includes a tangible, non-transitory computer-usable or readable medium having control logic (software) stored thereon, which may also be referred to herein as a computer program product or program storage device. This includes, but is not limited to, computer system 700, main memory 708, secondary memory 710, and removable storage units 718 and 722, as well as tangible articles of manufacture embodying any combination of the foregoing. Such control logic, when executed by one or more data processing devices (such as computer system 700), may cause such data processing devices to operate as described herein.

[0089] Based on the teachings contained in this disclosure, it will be apparent to those skilled in the relevant art how to use Figure 7 The embodiments of the present disclosure may be made and used with data processing devices, computer systems, and / or computer architectures other than those shown. In particular, the embodiments may operate with software, hardware, and / or operating system implementations other than those described herein.

[0090] It should be understood that the Detailed Description section, and not the Summary and Abstract sections, is intended to be used to interpret the claims. The Summary and Abstract sections may set forth one or more, but not all, exemplary embodiments contemplated by the inventors, and thus, are not intended to limit the appended claims in any way.

[0091] The present disclosure has been described above with the aid of functional building blocks, which illustrate the implementation of specified functions and their relationships. For ease of description, the boundaries of these functional building blocks have been arbitrarily defined herein. As long as the specified functions and their relationships are properly performed, alternative boundaries may be defined.

[0092] The above description of specific embodiments will fully demonstrate the general nature of the present disclosure, so that others can easily modify and / or adjust the various applications of such specific embodiments by applying knowledge within the technical scope of the art without undue experimentation, without departing from the general concept of the present disclosure. Therefore, based on the teachings and guidance presented herein, such adjustments and modifications are intended to be within the meaning and scope of equivalents of the embodiments disclosed herein. It should be understood that the wording or terminology herein is for illustrative purposes only and not for limitation, so the terms or wording of this specification will be interpreted by the skilled person in accordance with the teachings and guidance.

[0093] As described above, various aspects of the present technology may include collecting and using data available from various sources to, for example, improve or enhance functionality. The present disclosure contemplates that, in some instances, these collected data may include personal information data that uniquely identifies or can be used to contact or locate a specific person. Such personal information data may include demographic data, location-based data, phone numbers, email addresses, Twitter IDs, home addresses, data or records related to the user's health or fitness level (e.g., vital sign measurements, medication information, exercise information), date of birth, or any other identifying information or personal information. The present disclosure recognizes that the use of such personal information data in the present technology can be used to benefit users.

[0094] This disclosure contemplates that entities responsible for collecting, analyzing, disclosing, transmitting, storing, or otherwise using such personal information will adhere to established privacy policies and / or practices. Specifically, such entities should implement and adhere to privacy policies and practices that are recognized as meeting or exceeding industry or government requirements for maintaining the privacy and security of personal information. Such policies should be easily accessible to users and updated as the collection and / or use of data changes. Personal information collected from users should be used for the entity's legitimate and reasonable purposes and not shared or sold beyond those legitimate uses. Furthermore, such collection / sharing should only be done with the user's informed consent. Furthermore, such entities should consider taking any necessary steps to safeguard and secure access to such personal information and ensure that others with access to the personal information adhere to their privacy policies and procedures. Furthermore, such entities may subject themselves to third-party assessments to demonstrate compliance with widely accepted privacy policies and practices. Furthermore, policies and practices should be tailored to the specific type of personal information collected and / or accessed, and to applicable laws and standards, including jurisdictional considerations. For example, in the United States, the collection or access of certain health data may be governed by federal and / or state laws, such as the Health Insurance Portability and Accountability Act (HIPAA); whereas health data in other countries may be subject to other regulations and policies and should be handled accordingly. Therefore, different privacy practices should be maintained for different types of personal data in each country.

[0095] Regardless of the foregoing, the present disclosure also contemplates implementation schemes in which users selectively block the use or access of personal information data. That is, the present disclosure contemplates providing hardware elements and / or software elements to prevent or block access to such personal information data. For example, the present technology can be configured to allow users to selectively “opt in” or “opt out” of collecting personal information data at any time, for example, during or after registration for a service. In addition to providing “opt in” and “opt out” options, the present disclosure also contemplates providing notifications related to access or use of personal information. For example, a user may be notified that their personal information data will be accessed when downloading an application, and then reminded again just before the personal information data is accessed by the application.

[0096] Furthermore, it is an object of the present disclosure that personal information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use. Risk can be minimized by limiting data collection and deleting data once it is no longer needed. In addition, and when applicable, including in certain health-related applications, data de-identification can be used to protect the privacy of users. De-identification can be facilitated by removing specific identifiers (e.g., date of birth, etc.), controlling the amount or specificity of stored data (e.g., collecting location data at the city level rather than the address level), controlling how data is stored (e.g., aggregating data across users), and / or other methods, where appropriate.

[0097] Thus, while the present disclosure broadly encompasses the use of personal information data to implement one or more of the various disclosed embodiments, the present disclosure also contemplates that various embodiments may be implemented without requiring access to such personal information data. That is, various embodiments of the present technology will not be unable to function properly due to the lack of all or a portion of such personal information data.

Claims

1. A method for wireless communication, the method comprising: Receiving, by a user equipment (UE), a radio resource control (RRC) message, the RRC message including one or more configuration parameters for a first secondary cell bandwidth part (SCell) BWP associated with a secondary cell (SCell), the RRC message including a first value assigned to at least one of a firstActiveDownlinkBWP-ID or a firstActiveUplinkBWP-ID; communicating a first message with the SCell via the first SCell BWP; receiving, by the UE, a downlink control information (DCI) message indicating a change from the first SCell BWP to a second SCell BWP to be used for SCell communication, the DCI message including a different second value assigned to the at least one of firstActiveDownlinkBWP-ID or firstActiveUplinkBWP-ID; activating, by the UE, the second SCell BWP as an active BWP based on the DCI message without deactivating the SCell; as well as A second message is communicated with the SCell via the second SCell BWP, wherein the second message includes at least one of a first physical uplink shared channel (PUSCH) message, a first physical downlink shared channel (PDSCH) message, or a first physical downlink control channel (PDCCH) message.

2. The method according to claim 1, further comprising: Processing the RRC message by the UE includes configuring the UE to communicate with the SCell using the first SCell BWP; as well as Processing the DCI message by the UE includes reconfiguring the UE to communicate with the SCell using the second SCell BWP.

3. The method according to claim 1, further comprising: Receiving, by the UE via the MAC CE, an SCell deactivation message after reconfiguring the UE; as well as The UE processes the SCell deactivation message by deactivating all BWPs associated with the SCell.

4. The method of claim 1 , wherein the first message comprises at least one of: Second PUSCH message; Second PDSCH message; Second PDCCH message; Channel State Information Report; or Probe reference signal. 5 . The method according to claim 1 , wherein the UE does not deactivate the SCell after processing the RRC message and before processing the DCI message.

6. The method according to claim 1, further comprising: The UE communicates with a primary cell (PCell), wherein the SCell provides secondary radio resources that supplement the primary radio resources provided by the PCell, and The receiving of the RRC message by the UE includes receiving the RRC message from the PCell.

7. The method according to claim 6, further comprising: Receiving, by the UE, a second RRC message including one or more configuration parameters of the first PCell BWP; Processing, by the UE, the second RRC message includes configuring the UE to communicate with the PCell using the first PCell BWP; Receiving, by the UE, a third RRC message, where the third RRC message indicates a change from the first PCell BWP to a second PCell BWP; as well as Processing the third RRC message by the UE includes reconfiguring the UE to communicate with the PCell using the second PCell BWP.

8. A user equipment (UE), comprising: a transceiver configured to perform wireless communications over a wireless network; one or more processors coupled to the transceiver and configured to: receiving a radio resource control (RRC) message including one or more configuration parameters for a first secondary cell bandwidth part (SCell) BWP associated with a secondary cell (SCell), the RRC message including a first value assigned to at least one of a firstActiveDownlinkBWP-ID or a firstActiveUplinkBWP-ID; communicating a first message with the SCell via the first SCell BWP using the transceiver; receiving a downlink control information (DCI) message indicating a change from the first SCell BWP to a second SCell BWP to be used for SCell communication, the DCI message including a different second value assigned to the at least one of firstActiveDownlinkBWP-ID or firstActiveUplinkBWP-ID; activating the second SCell BWP as an active BWP based on the DCI message without deactivating the SCell; as well as A second message is communicated with the SCell via the second SCell BWP using the transceiver, wherein the second message includes at least one of a first physical uplink shared channel (PUSCH) message, a first physical downlink shared channel (PDSCH) message, or a first physical downlink control channel (PDCCH) message.

9. The UE of claim 8, wherein the one or more processors are further configured to: Processing the RRC message includes configuring the UE to communicate with the SCell using the first SCell BWP; and Processing the DCI message includes reconfiguring the UE to communicate with the SCell using the second SCell BWP.

10. The UE of claim 8, wherein the one or more processors are further configured to: Receiving, by the UE via the MAC CE, an SCell deactivation message after reconfiguring the first SCell BWP; and The UE processes the SCell deactivation message by deactivating all BWPs associated with the SCell.

11. The UE according to claim 8, wherein the first message comprises at least one of the following: Second PUSCH message; Second PDSCH message; Second PDCCH message; Channel State Information Report; or Probing reference signal. 12 . The UE of claim 8 , wherein the one or more processors are further configured to not deactivate the SCell after processing the RRC message and before processing the DCI message.

13. The UE of claim 8, wherein the one or more processors further communicate with a primary cell (PCell) using the transceiver, wherein the SCell provides secondary radio resources that supplement the primary radio resources provided by the PCell, and wherein the one or more processors further receive the RRC message from the PCell.

14. The UE of claim 13, wherein the one or more processors are further configured to: receiving a second RRC message including one or more configuration parameters of the first PCell BWP; Processing the second RRC message includes configuring the UE to communicate with the PCell using the first PCell BWP; receiving a third RRC message indicating a change from the first PCell BWP to a second PCell BWP; as well as Processing the third RRC message includes reconfiguring the UE to communicate with the PCell using the second PCell BWP.

15. A non-transitory tangible computer-readable medium having instructions stored thereon that, when executed by a processor of user equipment (UE), cause the UE to perform operations comprising: receiving a radio resource control (RRC) message including one or more configuration parameters for a first secondary cell bandwidth part (SCell) BWP associated with a secondary cell (SCell), the RRC message including a first value assigned to at least one of a firstActiveDownlinkBWP-ID or a firstActiveUplinkBWP-ID; Processing the RRC message includes configuring the UE to communicate with the SCell using the first SCell BWP; communicating a first message with the SCell via the first SCell BWP; receiving a downlink control information (DCI) message indicating a change from the first SCell BWP to a second SCell BWP to be used for SCell communication, the DCI message including a different second value assigned to the at least one of firstActiveDownlinkBWP-ID or firstActiveUplinkBWP-ID; processing the DCI message, the processing comprising activating the second SCell BWP as an active BWP based on the DCI message without deactivating the SCell and reconfiguring the UE to communicate with the SCell using the second SCell BWP; as well as A second message is communicated with the SCell via the second SCell BWP, wherein the second message includes at least one of a first physical uplink shared channel (PUSCH) message, a first physical downlink shared channel (PDSCH) message, or a first physical downlink control channel (PDCCH) message.

16. The non-transitory tangible computer readable medium of claim 15, the operations further comprising: receiving, via the MAC CE, an SCell deactivation message after reconfiguring the active BWP; The SCell deactivation message is processed by deactivating all BWPs associated with the SCell.

17. The non-transitory tangible computer-readable medium of claim 15, wherein the first message comprises at least one of: Second PUSCH message; Second PDSCH message; Second PDCCH message; Channel State Information Report; or Probing reference signal. 18 . The non-transitory tangible computer-readable medium of claim 15 , wherein the UE does not deactivate the SCell after processing the RRC message and before processing the DCI message. 19 . The non-transitory tangible computer-readable medium of claim 15 , wherein the SCell provides secondary radio resources that supplement primary radio resources provided by a primary cell (PCell) communicating with a UE.

20. The non-transitory tangible computer readable medium of claim 19, the operations further comprising: receiving a second RRC message including one or more configuration parameters of the first PCell BWP; Processing the second RRC message includes configuring the UE to communicate with the PCell using the first PCell BWP; receiving a third RRC message indicating a change from the first PCell BWP to a second PCell BWP; as well as Processing the third RRC message includes reconfiguring the UE to communicate with the PCell using the second PCell BWP.

Images