A timing parameter management method and device for bandwidth part switching

Abstract

Bandwidth part (BWP) switching can be beneficial for wireless communications systems. Such BWP switching can include an indication of one or more timing parameters for time domain resource allocation. For example, the timing parameters can be indicated based on an index to a lookup table (e.g., a bit field in a control transmission). In some cases, one or more tables can be configured for a given BWP, and different tables can contain different numbers of rows. The size of the bit field indexing the table can in turn depend on the number of rows. When switching from a first BWP to a second BWP, the size of the bit field can be based on the table for the first BWP, but the bit field can index the table for the second BWP. Techniques are discussed herein that support improved timing parameter management during BWP switching.

Description

[0001] This application is a divisional application of the application filed on April 3, 2019, with application number 201980023096.4 and entitled "A method and apparatus for managing timing parameters for partial bandwidth switching".

[0002] Cross-referencing

[0003] This patent application claims priority to the following applications: U.S. Patent Application No. 16 / 373,512, filed April 2, 2019, entitled “TIMING PARAMETER MANAGEMENT FOR BANDWIDTH PART SWITCHING”, by ANG et al.; and U.S. Provisional Patent Application No. 62 / 653,510, filed April 5, 2018, entitled “Timing Parameter Management For Bandwidth Part Switching”, each of which is assigned to the assignee of this application, and the entire contents of each of which are expressly incorporated herein by reference. Technical Field

[0004] In summary, the following text deals with wireless communication, and more specifically, with the management of timing parameters for bandwidth portion switching. Background Technology

[0005] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, and broadcasting. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth-generation (4G) systems (such as Long Term Evolution (LTE) systems, improved LTE (LTE-A) systems, or LTE-APro systems) and fifth-generation (5G) systems (which may be referred to as New Radio (NR) systems). These systems can employ technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), or Discrete Fourier Transform Spread Spectrum OFDM (DFT-s-OFDM). Wireless multiple access communication systems can include multiple base stations or network access nodes, each supporting communication with multiple communication devices (which may also be referred to as User Equipment (UE)) simultaneously.

[0006] In some wireless communication systems, wireless devices can operate within different portions of a channel or carrier. For example, a UE can operate within one or more bandwidth portions (BWPs) of a channel used for wireless communication. In such cases, the UE can be able to handover between different BWPs, for example, to save energy by tuning the radio unit to a smaller BWP (e.g., compared to other BWPs). The handover between these respective BWPs can be controlled via downlink signaling (such as downlink control information (DCI)), which can implement various schemes for resource allocation and for triggering BWP handover. Therefore, technologies supporting efficient BWP handover may be desirable. Summary of the Invention

[0007] The described technology relates to improved methods, systems, devices, and apparatuses for supporting timing parameter management for bandwidth portion (BWP) handover. In summary, the described technology provides consideration for time-domain resource allocation associated with bandwidth portion (BWP) handover. For example, a device (e.g., a user equipment (UE)) can be configured (e.g., via Radio Resource Control (RRC) signaling) to support one or more BWPs. For example, a BWP can allow the UE to operate in a smaller frequency range (e.g., compared to component carrier bandwidth). In some cases, the UE can be configured to have multiple BWPs with different frequency locations, bandwidths, digital schemes (e.g., communication parameters), combinations thereof, etc. Due to the differences between the configured BWPs, ambiguity may arise during or after BWP handover. For example, the UE can be triggered to handover from a first BWP to a second BWP (e.g., via downlink control information (DCI) received from a base station). In some cases, the DCI used to indicate switching can be formatted at least in part based on the first BWP, which may limit its flexibility when the format is applied to the second BWP (meaning, for example, when the format of the DCI corresponding to the first BWP is used to indicate parameter values ​​associated with the second BWP).

[0008] For example, a second BWP may be associated with a table (e.g., a timing parameter table) that is larger than the corresponding table associated with the first BWP. In some cases, the DCI used to indicate the switchover may contain a bit field whose size is set according to the first BWP table. For example, if the first BWP table contains four rows, the bit field may be a two-bit long field used to index the rows. However, if the second BWP table differs in size from the first BWP table, it may create difficulties in indexing the rows of the second BWP table. For example, if the second BWP table contains eight rows, only the first four rows may be addressable via a two-bit long field in the DCI. This paper describes considerations for efficient BWP switchover. Such considerations include the layout of the BWP table (e.g., a timing parameter table), DCI format and timing considerations, and other considerations.

[0009] A method for wireless communication is described. The method may include: identifying a set of timing parameter tables for one or more potential values ​​of custom timing parameters associated with timing between the reception of a DCI from a base station and subsequent communication with the base station based on the DCI; the set of timing parameter tables including at least a first timing parameter table associated with a first BWP and a second timing parameter table associated with a second BWP; receiving a DCI transmission on the first BWP for activating the second BWP, the DCI transmission including a resource allocation bit field indexed to at least a subset of the second timing parameter table, wherein the size of the resource allocation bit field is based on a configuration of the first BWP; identifying values ​​for the timing parameters based on the second timing parameter table and the size of the resource allocation bit field; and communicating with the base station on the second BWP based on the values ​​for the timing parameters.

[0010] An apparatus for wireless communication is described. The apparatus may include: a processor; a memory coupled to the processor; and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: identify a set of timing parameter tables for one or more potential values ​​of custom timing parameters associated with timing between the reception of a DCI from a base station and subsequent communication with the base station based on the DCI; the set of timing parameter tables including at least a first timing parameter table associated with a first BWP and a second timing parameter table associated with a second BWP; receive on the first BWP a DCI transmission for activating the second BWP, the DCI transmission including a resource allocation bit field indexed to at least a subset of the second timing parameter table, wherein the size of the resource allocation bit field is based on the configuration of the first BWP; identify a value for the timing parameter based on the second timing parameter table and the size of the resource allocation bit field; and communicate with the base station on the second BWP based on the value for the timing parameter.

[0011] Another apparatus for wireless communication is described. The apparatus may include: a set of timing parameter tables that identify one or more potential values ​​for various custom timing parameters associated with timing between the reception of a DCI from a base station and subsequent communication with the base station based on the DCI; the set of timing parameter tables including at least a first timing parameter table associated with a first BWP and a second timing parameter table associated with a second BWP; receiving on the first BWP a DCI transmission for activating the second BWP, the DCI transmission including a resource allocation bit field indexed to at least a subset of the second timing parameter table, wherein the size of the resource allocation bit field is based on a configuration of the first BWP; identifying a value for the timing parameter based on the second timing parameter table and the size of the resource allocation bit field; and communicating with the base station on the second BWP based on the value for the timing parameter.

[0012] A non-transitory computer-readable medium is described, storing code for wireless communication. The code may include processor-executable instructions to: identify a set of timing parameter tables for one or more potential values ​​of custom timing parameters associated with timing between the reception of a DCI from a base station and subsequent communication with the base station based on the DCI; the set of timing parameter tables includes at least a first timing parameter table associated with a first BWP and a second timing parameter table associated with a second BWP; receive on the first BWP a DCI transmission for activating the second BWP, the DCI transmission including a resource allocation bit field indexed to at least a subset of the second timing parameter table, wherein the size of the resource allocation bit field is based on the configuration of the first BWP; identify values ​​for the timing parameters based on the second timing parameter table and the size of the resource allocation bit field; and communicate with the base station on the second BWP based on the values ​​for the timing parameters.

[0013] In some examples of the methods, apparatuses and non-transitory computer-readable media described herein, the first timing parameter table includes a first set of rows, and the second timing parameter table includes a second set of rows, each row in the first and second set of rows indicating a potential value for the timing parameter, and wherein the size of the resource allocation bit field may be based on the number of rows in the first set of rows.

[0014] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the first row set may include operations, features, units, or instructions for: identifying a subset of bits in the resource allocation bit field, the subset of bits being used to index rows in the second row set; and determining the value for the timing parameter based on the indexed rows in the second row set.

[0015] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the first set of rows may include operations, features, units, or instructions for: identifying a subset of the second set of rows that may be addressable via the resource allocation bit field; identifying rows in the subset of the second set of rows that are indexed via the resource allocation bit field; and determining the value for the timing parameter based on the indexed rows.

[0016] In some examples of the methods, apparatuses and non-transitory computer-readable media described herein, the subset of the second row set includes the row with the lowest index in the second row set, the row with the lowest index corresponding to a preferred value of the timing parameter used to switch to the second BWP.

[0017] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the subset of the second set of rows includes the maximum value among the potential values ​​for the timing parameter from the second plurality of rows.

[0018] In some examples of the methods, apparatuses and non-transitory computer-readable media described herein, the subset of the second set of rows includes at least one row corresponding to a preferred value of the timing parameter used for communication in the second BWP.

[0019] In some examples of the methods, apparatuses and non-transitory computer-readable media described herein, the preferred values ​​of the timing parameters include a first value for wake-up communication, a second value for data communication, or a third value for micro-sleep communication.

[0020] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the first timing parameter table may be associated with uplink transmissions on the first BWP, and the set of timing parameter tables may also include a third timing parameter table associated with downlink transmissions on the first BWP.

[0021] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the first BWP may have a first tone interval, and the second BWP may have a second tone interval, wherein the potential values ​​for the timing parameters in the first timing parameter table are based on the first tone interval, and the potential values ​​for the timing parameters in the second timing parameter table are based on the second tone interval.

[0022] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may include operations, features, units, or instructions for adjusting the minimum value of the timing parameters based on switching communication from the first BWP to the second BWP.

[0023] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, identifying the set of timing parameter tables may include operations, features, units, or instructions for receiving at least one timing parameter table from the set of timing parameter tables via RRC signaling from the base station.

[0024] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, communicating with the base station based on the value of the timing parameter may include operations, features, elements, or instructions for receiving PDSCH transmissions.

[0025] In some examples of the methods, apparatuses and non-transitory computer-readable media described herein, communicating with the base station based on the value of the timing parameter may include operations, features, units or instructions for sending a PUSCH transmission.

[0026] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for: identifying a format for the DCI transmission; and selecting a second timing parameter table from a set of timing parameter tables based on the format of the DCI transmission.

[0027] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the DCI transmission includes a BWP identification field for activating the second BWP.

[0028] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the first BWP may be associated with a lower transmission power compared to the second BWP.

[0029] A method for wireless communication is described. The method may include: identifying a set of custom timing parameter tables for one or more potential values ​​of timing parameters, the timing parameters being associated with timing between a transmission of DCI to a UE and subsequent communication with the UE based on the DCI, the set of timing parameter tables including at least a first timing parameter table associated with a first BWP and a second timing parameter table associated with a second BWP; selecting a value for the timing parameter based on the second timing parameter table; transmitting a DCI transmission on the first BWP to activate the second BWP, the DCI transmission including a resource allocation bit field indicating the value of the timing parameter, wherein the size of the resource allocation bit field is based on a configuration of the first BWP; and communicating with the UE on the second BWP based on the value of the timing parameter.

[0030] An apparatus for wireless communication is described. The apparatus may include: a processor; a memory coupled to the processor; and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: identify a set of custom timing parameter tables for one or more potential values ​​of timing parameters associated with the timing of a transmission of DCI to a UE and subsequent communication with the UE based on the DCI; the set of timing parameter tables including at least a first timing parameter table associated with a first BWP and a second timing parameter table associated with a second BWP; select a value for the timing parameter based on the second timing parameter table; transmit a DCI transmission on the first BWP to activate the second BWP, the DCI transmission including a resource allocation bit field indicating the value of the timing parameter, wherein the size of the resource allocation bit field is based on the configuration of the first BWP; and communicate with the UE on the second BWP based on the value of the timing parameter.

[0031] Another apparatus for wireless communication is described. The apparatus may include: a set of timing parameter tables that identify one or more potential values ​​for various custom timing parameters associated with the timing of a transmission of DCI to a UE and subsequent communication with the UE based on the DCI; the set of timing parameter tables including at least a first timing parameter table associated with a first BWP and a second timing parameter table associated with a second BWP; selecting a value for the timing parameter based on the second timing parameter table; transmitting a DCI transmission on the first BWP to activate the second BWP, the DCI transmission including a resource allocation bit field indicating the value for the timing parameter, wherein the size of the resource allocation bit field is based on a configuration of the first BWP; and communicating with the UE on the second BWP based on the value for the timing parameter.

[0032] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include processor-executable instructions to: identify a set of custom timing parameter tables for one or more potential values ​​of timing parameters associated with the timing of a transmission of DCI to a UE and subsequent communication with the UE based on the DCI; the set of timing parameter tables including at least a first timing parameter table associated with a first BWP and a second timing parameter table associated with a second BWP; selecting a value for the timing parameter based on the second timing parameter table; transmitting a DCI transmission on the first BWP to activate the second BWP, the DCI transmission including a resource allocation bit field indicating the value of the timing parameter, wherein the size of the resource allocation bit field is based on the configuration of the first BWP; and communicating with the UE on the second BWP based on the value of the timing parameter.

[0033] In some examples of the methods, apparatuses and non-transitory computer-readable media described herein, the first timing parameter table includes a first set of rows, and the second timing parameter table includes a second set of rows, each row in the first and second set of rows indicating a potential value for the timing parameter, and wherein the size of the resource allocation bit field may be based on the number of rows in the first set of rows.

[0034] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the first set of rows may include operations, features, units, or instructions for zero-padding the resource allocation bit field.

[0035] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the first row set may include operations, features, units, or instructions for: identifying a subset of the second row set that is addressable via the resource allocation bit field; and selecting the value for the timing parameter based on the subset of the second row set.

[0036] In some examples of the methods, apparatuses and non-transitory computer-readable media described herein, the subset of the second row set includes the row with the lowest index in the second row set, the row with the lowest index corresponding to a preferred value of the timing parameter used to switch to the second BWP.

[0037] In some examples of the methods, apparatuses and non-transitory computer-readable media described herein, the subset of the second set of rows includes the set of rows with the lowest index among a second plurality of rows, the set of rows with the lowest index corresponding to the set of values ​​of the timing parameter, wherein the values ​​of the timing parameter are sorted from the maximum value of the timing parameter used for switching to the second BWP to the minimum value of the timing parameter used for switching to the second BWP.

[0038] In some examples of the methods, apparatuses and non-transitory computer-readable media described herein, the subset of the second set of rows includes at least one row corresponding to a preferred value of the timing parameter used for communication in the second BWP.

[0039] In some examples of the methods, apparatuses and non-transitory computer-readable media described herein, the preferred values ​​of the timing parameters include a first value for wake-up communication, a second value for data communication, or a third value for micro-sleep communication.

[0040] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the first timing parameter table may be associated with uplink transmissions on the first BWP, and the set of timing parameter tables may also include a third timing parameter table associated with downlink transmissions on the first BWP.

[0041] In some examples of the methods, apparatuses and non-transitory computer-readable media described herein, the first BWP may have a first tone interval, and the second BWP may have a second tone interval, the potential values ​​for the timing parameters in the first timing parameter table are based on the first tone interval, and the potential values ​​for the timing parameters in the second timing parameter table are based on the second tone interval.

[0042] In some examples of the methods, apparatuses and non-transitory computer-readable media described herein, operations, features, units or instructions may be included for adjusting the minimum value of the timing parameters based on switching communication from the first BWP to the second BWP.

[0043] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for transmitting at least one timing parameter table from the set of timing parameter tables to the UE via RRC signaling.

[0044] In some examples of the methods, apparatuses and non-transitory computer-readable media described herein, communicating with the UE based on the value of the timing parameter may include operations, features, elements or instructions for transmitting a PDSCH transmission.

[0045] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, communicating with the UE based on the value of the timing parameter may include operations, features, elements, or instructions for receiving PUSCH transmissions.

[0046] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for: identifying a trigger for switching communication with the UE from the first BWP to the second BWP; and identifying the format for the DCI transmission based on the trigger.

[0047] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the DCI transmission includes a BWP identification field for activating the second BWP.

[0048] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the first BWP may be associated with a lower transmission power compared to the second BWP. Attached Figure Description

[0049] Figure 1 An example of a wireless communication system that supports timing parameter management for bandwidth partial switching, in accordance with various aspects of this disclosure, is shown.

[0050] Figure 2 An example of a wireless communication system that supports timing parameter management for bandwidth partial switching, in accordance with various aspects of this disclosure, is shown.

[0051] Figure 3 An example of a communication graph supporting timing parameter management for bandwidth partial switching is shown, according to various aspects of this disclosure.

[0052] Figures 4 to 6 An exemplary transmission scheme is shown that supports timing parameter management for bandwidth partial switching in accordance with various aspects of this disclosure.

[0053] Figure 7 An example of a process flow supporting timing parameter management for bandwidth partial switching is shown, based on various aspects of this disclosure.

[0054] Figure 8 and Figure 9A block diagram of a device supporting timing parameter management for bandwidth partial switching, in accordance with various aspects of this disclosure, is shown.

[0055] Figure 10 A block diagram of a device supporting timing parameter management for bandwidth partial switching, in accordance with various aspects of this disclosure, is shown.

[0056] Figure 11 A diagram of a system including a device that supports timing parameter management for bandwidth portion switching, according to various aspects of this disclosure, is shown.

[0057] Figure 12 and Figure 13 A block diagram of a device supporting timing parameter management for bandwidth partial switching, in accordance with various aspects of this disclosure, is shown.

[0058] Figure 14 A block diagram of a device supporting timing parameter management for bandwidth partial switching, in accordance with various aspects of this disclosure, is shown.

[0059] Figure 15 A diagram of a system including a device that supports timing parameter management for bandwidth portion switching, according to various aspects of this disclosure, is shown.

[0060] Figure 16 and Figure 17 A flowchart illustrating a method for managing timing parameters for bandwidth partial switching, in accordance with various aspects of this disclosure, is shown. Detailed Implementation

[0061] In some wireless communication systems, the size (e.g., bit length) of one or more downlink control information (DCI) bit fields can be based on the size (e.g., bandwidth) of an associated bandwidth portion (BWP). During a BWP handover event, DCI signaling can be used to control and facilitate handover between a current BWP of a first size and a target BWP of a second size. Handover between respective BWPs can be controlled via downlink signaling such as DCI, which can implement various schemes for resource allocation and for triggering BWP handover.

[0062] In some cases, cross-slot scheduling and cross-BWP scheduling can help accommodate latency during handover between narrow and wide BWPs. For example, DCI signaling can be used to control handover from a narrow BWP format in a first time slot to a wide BWP format in a second time slot, and vice versa, where different BWP formats have different DCI field sizes. In some cases, the base station can signal to the user equipment (UE) the transmission delays (e.g., timing parameters) associated with downlink and uplink transmissions. Examples of such timing parameters include k0 and k2 values. The k0 value can, for example, correspond to the delay between downlink grant (e.g., the first time slot containing the DCI) and downlink data assignment (e.g., the second time slot containing the Physical Downlink Shared Channel (PDSCH) transmission). Similarly, the k2 value can correspond to the delay between downlink grant and uplink data assignment (e.g., the second time slot containing the Physical Uplink Shared Channel (PUSCH) transmission). In some examples, k0 and k2 can represent the number of time slots (e.g., or some other suitable time interval). In some cases, timing parameters can be transmitted via signaling through the DCI bit field. For example, the DCI bit field may contain an index to a table configured for the current BWP (e.g., via Radio Resource Control (RRC) signaling).

[0063] The size of one or more DCI bit fields can be determined based on the current BWP. For example, the size of the bit field indexing a configured table can be based on the number of rows in that table. However, during a BWP switch (e.g., from a first BWP with a table containing four rows to a second BWP with a table containing eight rows), the DCI bit fields (e.g., those based on the configuration of the first BWP) can be large enough only to index the four rows of the second BWP table. This paper discusses considerations for timing parameter management for BWP switchovers.

[0064] The various aspects of this disclosure are first described in the context of a wireless communication system. Then, they are described in the context of communication diagrams, process flows, and transmission schemes. The various aspects of this disclosure are further illustrated and described with reference to apparatus diagrams, system diagrams, and flowcharts relating to the management of timing parameters for bandwidth portion switching.

[0065] Figure 1An example of a wireless communication system 100 supporting timing parameter management for bandwidth partial switching according to various aspects of this disclosure is shown. The wireless communication system 100 includes a base station 105, a user interface device (UE) 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an improved LTE (LTE-A) network, an LTE-APro network, or a New Radio (NR) network. In some cases, the wireless communication system 100 may support enhanced broadband communication, ultra-reliable (e.g., mission-critical) communication, low-latency communication, or communication with low-cost and low-complexity devices.

[0066] Base station 105 can wirelessly communicate with UE 115 via one or more base station antennas. Base station 105 described herein may include, or may be referred to by those skilled in the art as, a base transceiver, radio base station, access point, radio transceiver, Node B, evolved Node B (eNB), next-generation Node B, or gigabit Node B (any of which may be referred to as gNB), home Node B, home evolved Node B, or some other suitable term. Wireless communication system 100 may include different types of base stations 105 (e.g., macro cell base stations or small cell base stations). UE 115 described herein can be able to communicate with various types of base stations 105 and network devices (including macro eNBs, small cell eNBs, gNBs, relay base stations, etc.).

[0067] Each base station 105 may be associated with a specific geographic coverage area 110 in which communication with each UE 115 is supported. Each base station 105 may provide communication coverage to its respective geographic coverage area 110 via a communication link 125, and the communication link 125 between the base station 105 and the UE 115 may utilize one or more carriers. The communication link 125 shown in the wireless communication system 100 may include an uplink transmission from the UE 115 to the base station 105, or a downlink transmission from the base station 105 to the UE 115. The downlink transmission may also be referred to as a forward link transmission, and the uplink transmission may also be referred to as a reverse link transmission.

[0068] The geographic coverage area 110 for base station 105 can be divided into sectors, each sector constituting only a part of the geographic coverage area 110, and each sector can be associated with a cell. For example, each base station 105 can provide communication coverage for macro cells, small cells, hotspots, or other types of cells, or various combinations thereof. In some examples, base station 105 can be mobile, and therefore provide communication coverage for mobile geographic coverage areas 110. In some examples, different geographic coverage areas 110 associated with different technologies can overlap, and overlapping geographic coverage areas 110 associated with different technologies can be supported by the same base station 105 or different base stations 105. Wireless communication system 100 can include, for example, heterogeneous LTE / LTE-A / LTE-APro or NR networks, wherein different types of base stations 105 provide coverage for individual geographic coverage areas 110.

[0069] The term "cell" refers to a logical communication entity used for communication with base station 105 (e.g., on a carrier), and can be associated with identifiers (e.g., Physical Cell Identifier (PCID), Virtual Cell Identifier (VCID)) used to distinguish neighboring cells operating via the same or different carriers. In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., Machine-Type Communication (MTC), Narrowband Internet of Things (NB-IoT), Enhanced Mobile Broadband (eMBB), or other protocol types) that can provide access for different types of devices. In some cases, the term "cell" may refer to a portion (e.g., a sector) of the geographical coverage area 110 on which the logical entity operates.

[0070] UE 115 can be distributed throughout the wireless communication system 100, and each UE 115 can be stationary or mobile. UE 115 can also be referred to as a mobile device, wireless device, remote device, handheld device, or subscriber device, or some other suitable term, wherein "device" can also be referred to as a unit, station, terminal, or client. UE 115 can also be a personal electronic device, such as a cellular phone, personal digital assistant (PDA), tablet computer, laptop computer, or personal computer. In some examples, UE 115 can also refer to a wireless local loop (WLL) station, Internet of Things (IoT) device, Internet of Everything (IoE) device, or MTC device, which can be implemented in various items such as appliances, vehicles, instruments, etc.

[0071] Some UE 115 devices (such as MTC or IoT devices) can be low-cost or low-complexity devices that can provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC can refer to data communication technologies that allow devices to communicate with each other or with base station 105 without human intervention. In some examples, M2M communication or MTC can include communication from devices that integrate sensors or meters to measure or capture information and relay that information to a central server or application that can utilize that information or present it to humans interacting with that program or application. Some UE 115 devices can be designed to collect information or enable automated machine behavior. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, climate and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based billing.

[0072] Some UEs 115 can be configured to operate in reduced-power modes, such as half-duplex communication (e.g., a mode that supports unidirectional communication via either transmission or reception, rather than simultaneous transmission and reception). In some examples, half-duplex communication may be performed at a reduced peak rate. Other power-saving techniques for UE 115 include entering a power-saving "deep sleep" mode when not engaged in active communication or operating on limited bandwidth (e.g., according to narrowband communication). In some cases, UE 115 may be designed to support critical functions (e.g., mission-critical functions), and the wireless communication system 100 may be configured to provide ultra-reliable communication for these functions.

[0073] In some cases, UE 115 may also be able to communicate directly with other UE 115s (e.g., using peer-to-peer (P2P) or device-to-device (D2D) protocols). One or more UE 115s in a group utilizing D2D communication may be within the geographic coverage area 110 of base station 105. Other UE 115s in such a group may be outside the geographic coverage area 110 of base station 105, or otherwise unable to receive transmissions from base station 105. In some cases, multiple groups of UE 115s communicating via D2D communication may utilize a one-to-many (1:M) system, wherein each UE 115 transmits to every other UE 115 in the group. In some cases, base station 105 facilitates the scheduling of resources for D2D communication. In other cases, D2D communication is performed between UE 115s without involving base station 105.

[0074] Base station 105 can communicate with core network 130 and with each other. For example, base station 105 can interface with core network 130 via backhaul link 132 (e.g., via S1 or other interfaces). Base station 105 can communicate with each other directly (e.g., directly between base stations 105) or indirectly (e.g., via core network 130) on backhaul link 134 (e.g., via X2 or other interfaces).

[0075] Core network 130 can provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. Core network 130 may be an evolved packet core (EPC), which may include at least one Mobility Management Entity (MME), at least one Serving Gateway (S-GW), and at least one Packet Data Network (PDN) Gateway (P-GW). The MME can manage non-access stratum (e.g., control plane) functions, such as mobility, authentication, and bearer management for UE 115 served by base station 105 associated with the EPC. User IP packets can be transmitted via the S-GW, which itself may be connected to the P-GW. The P-GW can provide IP address allocation and other functions. The P-GW may be connected to network operator IP services. Operator IP services may include access to the Internet, intranets, IP Multimedia Subsystem (IMS), or packet-switched (PS) streaming services.

[0076] At least some of the network devices (such as base station 105) may include sub-components such as access network entities, which may be examples of access node controllers (ANCs). Each access network entity may communicate with UE 115 through multiple other access network transport entities (which may be referred to as radio headends, smart radio headends, or transmit / receive points (TRPs)). In some configurations, the various functions of each access network entity or base station 105 may be distributed across various network devices (e.g., radio headends and access network controllers) or combined into a single network device (e.g., base station 105).

[0077] Wireless communication system 100 can operate using one or more frequency bands (typically in the range of 300 MHz to 300 GHz). The region from 300 MHz to 3 GHz is often referred to as the Ultra High Frequency (UHF) region or decimeter band because the wavelength range extends from approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features. However, the waves may be sufficient to penetrate structures for macrocell service to UE 115 located indoors. Transmission of UHF waves can be associated with smaller antennas and shorter distances (e.g., less than 100 km) compared to the transmission of smaller frequencies and longer waves in the lower 300 MHz portion of the spectrum, such as the High Frequency (HF) or Very High Frequency (VHF) portions.

[0078] The wireless communication system 100 can also operate in the ultra-high frequency (SHF) region using a frequency band from 3 GHz to 30 GHz (also known as the centimeter band). The SHF region includes frequency bands such as the 5 GHz industrial, scientific, and medical (ISM) band, which can be used opportunistically by devices capable of tolerating interference from other users.

[0079] The wireless communication system 100 can also operate in the extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz) (also referred to as the millimeter band). In some examples, the wireless communication system 100 can support millimeter-wave (mmW) communication between the UE 115 and the base station 105, and the EHF antennas of the respective devices can be even smaller and more closely spaced compared to UHF antennas. In some cases, this can facilitate the use of antenna arrays within the UE 115. However, propagation to EHF transmissions may suffer even greater atmospheric attenuation and shorter distances compared to SHF or UHF transmissions. The techniques disclosed herein can be employed across transmissions using one or more different frequency regions, and the designated use of frequency bands across these frequency regions may vary depending on the country or regulatory authority.

[0080] In some cases, wireless communication system 100 may utilize both licensed and unlicensed radio frequency spectrum bands. For example, wireless communication system 100 may employ Licensed Assisted Access (LAA), LTE Unlicensed (LTE-U) radio access technology, or NR technology in unlicensed frequency bands (such as the 5 GHz ISM band). When operating in unlicensed radio frequency spectrum bands, wireless devices (such as base station 105 and UE 115) may employ a Listen-Before-Speak (LBT) procedure before transmitting data to ensure that the frequency channel is idle. In some cases, operation in unlicensed frequency bands may be based on a CA configuration that combines CC operation in licensed frequency bands (e.g., LAA). Operation in unlicensed spectrum may include downlink transmission, uplink transmission, peer-to-peer transmission, or a combination of these. Duplexing in unlicensed spectrum may be based on Frequency Division Duplex (FDD), Time Division Duplex (TDD), or a combination of both.

[0081] In some examples, base station 105 or UE 115 may be equipped with multiple antennas, which can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. For example, wireless communication system 100 may use a transmission scheme between a transmitting device (e.g., base station 105) and a receiving device (e.g., UE 115), wherein the transmitting device is equipped with multiple antennas, and the receiving device is equipped with one or more antennas. MIMO communication may employ multipath signal propagation to improve spectral efficiency by transmitting or receiving multiple signals via different spatial layers (this may be referred to as spatial multiplexing). For example, the transmitting device may transmit multiple signals via different antennas or different combinations of antennas. Similarly, the receiving device may receive multiple signals via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry bits associated with the same data stream (e.g., the same codeword) or different data streams. Different spatial layers may be associated with different antenna ports used for channel measurement and reporting. MIMO technology includes single-user MIMO (SU-MIMO) (where multiple spatial layers are sent to the same receiving device) and multi-user MIMO (MU-MIMO) (where multiple spatial layers are sent to multiple devices).

[0082] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting or receiving device (e.g., base station 105 or UE 115) to form or guide an antenna beam (e.g., a transmit beam or a receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals transmitted via antenna elements of an antenna array such that signals propagating relative to a specific orientation of the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to the signals transmitted via the antenna elements can include applying certain amplitude and phase offsets to the signals carried by each antenna element in the antenna elements associated with the transmitting or receiving device. The adjustments associated with each antenna element can be defined by a set of beamforming weights associated with a specific orientation (e.g., relative to the antenna array of the transmitting or receiving device, or relative to some other orientation).

[0083] In one example, base station 105 may use multiple antennas or antenna arrays to perform beamforming operations for directional communication with UE 115. For example, base station 105 may transmit signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) multiple times in different directions, these signals may include signals transmitted according to different sets of beamforming weights associated with different transmission directions. Transmissions in different beam directions can be used (e.g., by base station 105 or receiving device (such as UE 115)) to identify the beam direction for subsequent transmissions and / or receptions by base station 105. Base station 105 may transmit signals (such as data signals associated with a specific receiving device) in a single beam direction (e.g., the direction associated with the receiving device (such as UE 115)). In some examples, the beam direction associated with transmissions along a single beam direction may be determined at least in part based on the signals transmitted in different beam directions. For example, UE 115 may receive one or more signals transmitted by base station 105 in different directions, and UE 115 may report to base station 105 an indication of the signal it received that has the highest signal quality or another acceptable signal quality. Although these techniques are described with reference to signals transmitted by base station 105 in one or more directions, UE 115 may employ similar techniques to transmit signals multiple times in different directions (e.g., to identify beam directions for subsequent transmissions or receptions by UE 115) or to transmit signals in a single direction (e.g., to transmit data to a receiving device).

[0084] When receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from base station 105, a receiving device (e.g., UE 115, which may be an example of an mmW receiving device) can attempt multiple receive beams. For example, the receiving device can attempt multiple receive directions by receiving via different antenna subarrays, by processing the received signals according to different antenna subarrays, by receiving according to different sets of receive beamforming weights applied to the signals received at multiple antenna elements of the antenna array, or by processing the received signals according to different sets of receive beamforming weights applied to the signals received at multiple antenna elements of the antenna array (any of the above operations can be referred to as "listening" according to different receive beams or receive directions). In some examples, the receiving device can use a single receive beam to receive along a single beam direction (e.g., when receiving data signals). A single receiving beam can be aligned on a beam direction determined at least in part based on listening to different receiving beam directions (e.g., a beam direction determined at least in part based on listening to multiple beam directions to have the highest signal strength, highest signal-to-noise ratio, or otherwise acceptable signal quality).

[0085] In some cases, the antennas of base station 105 or UE 115 may be located within one or more antenna arrays that can support MIMO operation or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly (such as an antenna tower). In some cases, the antennas or antenna arrays associated with base station 105 may be located in a variety of geographical locations. Base station 105 may have antenna arrays with multiple rows and columns of antenna ports that base station 105 can use to support beamforming for communication with UE 115. Similarly, UE 115 may have one or more antenna arrays that can support various MIMO or beamforming operations.

[0086] In some cases, the wireless communication system 100 may be a packet-based network operating according to a layered protocol stack. In the user plane, communication at the bearer or Packet Data Convergence Protocol (PDCP) layer may be IP-based. In some cases, the Radio Link Control (RLC) layer may perform packet segmentation and reassembly for communication on logical channels. The Media Access Control (MAC) layer may perform priority handling and multiplexing of logical channels to transport channels. The MAC layer may also use Hybrid Automatic Repeat Request (HARQ) to provide retransmissions at the MAC layer to improve link efficiency. In the control plane, the Radio Resource Control (RRC) protocol layer may provide the establishment, configuration, and maintenance of RRC connections (which support radio bearers for user plane data) between the UE 115 and the base station 105 or core network 130. At the physical (PHY) layer, transport channels may be mapped to physical channels.

[0087] In some cases, UE 115 and base station 105 can support data retransmission to increase the likelihood of successful data reception. HARQ feedback is a technique to increase the likelihood of correct data reception on communication link 125. HARQ may include a combination of error detection (e.g., using Cyclic Redundancy Check (CRC)), forward error correction (FEC), and retransmission (e.g., Automatic Repeat Request (ARQ)). HARQ can improve throughput at the MAC layer under poor radio conditions (e.g., signal and noise conditions). In some cases, the radio device can support same-slot HARQ feedback, where the device can provide HARQ feedback for data received in a previous symbol within a specific time slot. In other cases, the device can provide HARQ feedback in subsequent time slots or according to some other time interval.

[0088] It can be in the basic unit of time (which can, for example, refer to T) s The time interval in LTE or NR is expressed as a multiple of a sampling period of 1 / 30,720,000 seconds. The time interval of communication resources can be organized according to radio frames, each with a duration of 10 milliseconds (ms), where the frame period can be expressed as T. f =307,200T sRadio frames can be identified by System Frame Numbers (SFNs) ranging from 0 to 1023. Each frame may include 10 subframes numbered from 0 to 9, and each subframe may have a duration of 1 ms. Subframes may be further divided into two time slots, each with a duration of 0.5 ms, and each time slot may contain 6 or 7 modulation symbol periods (e.g., depending on the length of the cyclic prefix added before each symbol period). Excluding the cyclic prefix, each symbol period may contain 2048 sampling periods. In some cases, a subframe may be the minimum scheduling unit of the wireless communication system 100, and may be referred to as a Transmission Time Interval (TTI). In other cases, the minimum scheduling unit of the wireless communication system 100 may be shorter than a subframe or may be dynamically selected (e.g., in a burst of shortened TTIs (sTTIs) or in selected component carriers using sTTIs).

[0089] In some wireless communication systems, time slots can be further divided into multiple mini-slots containing one or more symbols. In some instances, the symbol or mini-slot of a mini-slot can be the smallest scheduling unit. The duration of each symbol can vary depending on, for example, the subcarrier spacing or the frequency band of operation. Furthermore, some wireless communication systems can implement time slot aggregation, where multiple time slots or mini-slots are aggregated together and used for communication between UE 115 and base station 105.

[0090] The term "carrier" refers to a set of radio frequency spectrum resources having a defined physical layer structure for supporting communication on communication link 125. For example, a carrier of communication link 125 may include a portion of the radio frequency spectrum band that operates according to physical layer channels for a given radio access technology. Each physical layer channel may carry user data, control information, or other signaling. Carriers may be associated with predefined frequency channels (e.g., E-UTRA Absolute Radio Channel Number (EARFCN)) and may be positioned according to a channel grid for discovery by UE 115. A carrier may be downlink or uplink (e.g., in FDD mode), or may be configured to carry both downlink and uplink communication (e.g., in TDD mode). In some examples, the signal waveform transmitted on a carrier may consist of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques such as OFDM or DFT-s-OFDM).

[0091] The carrier organization structure can vary depending on the radio access technology (e.g., LTE, LTE-A, LTE-APro, NR, etc.). For example, communication on a carrier can be organized according to a Time Interval (TTI) or time slot, each of which can include user data and control information or signaling to support the decoding of the user data. A carrier can also include dedicated acquisition signaling (e.g., synchronization signals or system information) and control signaling to coordinate operations on the carrier. In some examples (e.g., in a carrier aggregation configuration), a carrier can also have acquisition signaling or control signaling to coordinate operations on other carriers.

[0092] Physical channels can be multiplexed on a carrier using various techniques. For example, time division multiplexing (TDM), frequency division multiplexing (FDM), or hybrid TDM-FDM techniques can be used to multiplex physical control channels and physical data channels on a downlink carrier. In some examples, control information transmitted in the physical control channel can be distributed in a concatenated manner between different control regions (e.g., between a common control region or common search space and one or more UE-specific control regions or UE-specific search spaces).

[0093] A carrier can be associated with a specific bandwidth of the radio frequency spectrum, and in some examples, the carrier bandwidth can be referred to as the carrier or the “system bandwidth” of the wireless communication system 100. For example, the carrier bandwidth can be one of several predetermined bandwidths for a carrier specific to a particular radio access technology (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 MHz). In some examples, each served UE 115 can be configured to operate on a portion or all of the carrier bandwidth. In other examples, some UEs 115 can be configured to operate using a narrowband protocol type associated with a predefined portion or range within the carrier (e.g., a set of subcarriers or RBs) (e.g., “in-band” deployment of a narrowband protocol type).

[0094] In systems employing MCM technology, a resource element can consist of a symbol period (e.g., the duration of a modulation symbol) and a subcarrier, where the symbol period and subcarrier spacing are inversely related. The number of bits carried by each resource element can depend on the modulation scheme (e.g., the order of the modulation scheme). Therefore, the more resource elements UE 115 receives and the higher the order of the modulation scheme, the higher the data rate can be for UE 115. In MIMO systems, wireless communication resources can refer to a combination of radio frequency spectrum resources, temporal resources, and spatial resources (e.g., spatial layers), and the use of multiple spatial layers can further increase the data rate used for communication with UE 115.

[0095] The devices of the wireless communication system 100 (e.g., base station 105 or UE 115) may have a hardware configuration that supports communication on a specific carrier bandwidth, or may be configurable to support communication on one carrier bandwidth in a set of carrier bandwidths. In some examples, the wireless communication system 100 may include base station 105 and / or UE 115, which are capable of supporting simultaneous communication via carriers associated with more than one different carrier bandwidth.

[0096] The wireless communication system 100 can support communication with the UE 115 on multiple cells or carriers (a feature that may be referred to as carrier aggregation (CA) or multi-carrier operation). Depending on the carrier aggregation configuration, the UE 115 can be configured with multiple downlink CCs and one or more uplink CCs. Carrier aggregation can be used in conjunction with both FDD and TDD component carriers.

[0097] In some cases, the wireless communication system 100 may utilize enhanced component carriers (eCC). eCC can be characterized by one or more features including: a wider carrier or frequency channel bandwidth, a shorter symbol duration, a shorter TTI duration, or a modified control channel configuration. In some cases, eCC may be associated with carrier aggregation or dual connectivity configurations (e.g., when multiple serving cells have suboptimal or non-ideal backhaul links). eCC can also be configured for use in unlicensed or shared spectrum (e.g., where more than one operator is permitted to use the spectrum). eCC characterized by a wide carrier bandwidth may include one or more segments that can be used by a UE 115 that cannot monitor the entire carrier bandwidth or is otherwise configured to use a limited carrier bandwidth (e.g., to save power).

[0098] In some cases, eCC can utilize a different symbol duration than other CCs, which may include using a reduced symbol duration compared to other CCs. A shorter symbol duration can be associated with increased spacing between adjacent subcarriers. Devices utilizing eCC (such as UE 115 or base station 105) can transmit wideband signals (e.g., based on frequency channels or carrier bandwidths of 20, 40, 60, 80 MHz, etc.) with a reduced symbol duration (e.g., 16.67 microseconds). The TTI in eCC can consist of one or more symbol periods. In some cases, the TTI duration (i.e., the number of symbol periods in the TTI) can be variable.

[0099] Wireless communication systems (such as NR systems) can utilize any combination of licensed, shared, and unlicensed spectrum bands. The flexibility in eCC symbol duration and subcarrier spacing allows for the use of eCC across multiple spectrums. In some examples, NR spectrum sharing can improve spectrum utilization and efficiency, especially through dynamic vertical (e.g., across the frequency domain) and horizontal (e.g., across the time domain) sharing of resources.

[0100] In some cases, the wireless communication system 100 may support BWPs, which may allow UE 115 to operate in a frequency range smaller than the CC bandwidth. In some cases, UE 115 may be configured to have multiple BWPs (e.g., each BWP has a different frequency location, bandwidth, timing parameters, digital scheme, etc.). Control information (e.g., DCI) may be used to trigger BWP handover for a given UE 115. For example, each UE 115 may support at most one active BWP per serving cell (e.g., although UE 115 may be configured to have multiple BWPs per serving cell). The DCI may contain a BWP identifier (ID) field, which indicates the BWP that should be activated within the scheduled time slots (e.g., k0 or k2 time slots after receiving the DCI). Once activated, a BWP may remain active until another BWP is activated (e.g., or until a timer expires). If the BWP ID field in the DCI is different from the currently active BWP, a BWP handover may be triggered (e.g., causing a cross-BWP scheduling to trigger a BWP handover).

[0101] The size (e.g., bit length) of one or more fields in the DCI can be based on the currently active BWP. For example, the size of the time-domain resource allocation field can be based on the number of timing parameter (e.g., k0, k2) values ​​supported by the currently active BWP. If the BWP ID field indicates another BWP that supports a different number of potential timing parameter values ​​(e.g., a BWP different from the currently active BWP), the time-domain resource allocation field based on the currently active BWP may not be large enough (e.g., or may be too large) for the newly indicated BWP. In some cases, the base station can zero-padded bit fields that are too small for the newly indicated BWP, and can truncate bit fields that are too large for the newly indicated BWP.

[0102] That is, for cross-BWP scheduling, one or more bit fields in DCI transmission (e.g., the time-domain resource allocation field) can be sized based on the current BWP, but can be indexed to a new BWP table (e.g., the PDSCH symbol allocation table, PUSCH symbol allocation table, etc.). When the number of bits in the time-domain resource allocation field is insufficient to address all rows in the new BWP table, UE 115 may interpret the field as referencing only the lower index rows in the table (e.g., starting from the first row and continuing to the last addressable row). It should be understood that in some cases, UE 115 may interpret the field as referencing only the higher index rows in the table (e.g., starting from the last row and continuing upwards to the last addressable row), a subset of some inner rows in the table, etc.

[0103] When the number of bits in the time-domain resource allocation field is too large for the new BWP table, UE 115 may expect only the lower bits (e.g., the least significant bit) in the bit field to be used for addressing rows in the new BWP table (e.g., so that truncation can start from the most significant bit). It is to be understood that, without departing from the scope of this disclosure, truncation may alternatively start from the least significant bit. For cross-BWP scheduling where BWPs have different digitization schemes (e.g., the first BWP uses a longer symbol period compared to the second BWP), the digitization scheme of the new BWP can be used to interpret timing parameters (e.g., k0 and k2 for DCI formats 1-1 or 0-1, respectively). For example, using the digitization scheme of the new BWP can provide consistency with cross-carrier scheduling (e.g., for carrier aggregation) utilizing different digitization schemes for timing parameters.

[0104] Figure 2 Examples of a wireless communication system 200 supporting timing parameter management for bandwidth partial switching according to various aspects of this disclosure are shown. In some examples, the wireless communication system 200 may implement aspects of the wireless communication system 100. The wireless communication system 200 may include a base station 105-a and a UE 115-a, which may communicate using a carrier 205. The wireless communication system 200 may be configured to use one or more BWPs 210 to transmit information over the overall carrier 205.

[0105] BWP 210 can be a contiguous set of Physical Resource Blocks (PRBs). The bandwidth of BWP 210 can be equal to or less than the maximum bandwidth capability supported by UE 115-a or the bandwidth of the overall carrier 205. In some cases, the bandwidth of BWP 210 can be at least as large as the bandwidth of the synchronization signal (SS) block.

[0106] In some cases, BWP 210 may be a dynamically configured (or semi-statically configured) part of the overall carrier 205. BWP 210 may include multiple dynamically (or semi-statically) configurable parameters. Examples of such parameters may include frequency location (e.g., center frequency), bandwidth (e.g., number of PRBs), digital scheme (e.g., subcarrier spacing and / or cyclic prefix type), or combinations thereof. The parameters of BWP 210 may be transmitted using DCI, Media Access Control (MAC) control elements (CE), RRC signaling, and / or time patterns (e.g., in discontinuous reception scenarios). The granularity of some parameters may be one PRB in size (e.g., bandwidth granularity may be 1 PRB and frequency location granularity may be 1 PRB).

[0107] BWP 210 can be configured for both downlink and uplink. BWP 210 can be configured independently for each cell (e.g., primary cell (PCell) and / or secondary cell (SCell)). In such cases, if the SCell is deactivated, the BWP for that cell can also be deactivated. In some cases, UE 115-a can be configured to communicate using one or more downlink BWPs and / or one or more uplink BWPs simultaneously. In some cases, at a given time, there can be at most one active downlink BWP and at most one active uplink BWP for the serving cell. PCell can be the cell handling the RRC connection between UE 115-a and base station 105-a, and SCell can be any other serving cell established between UE 115-a and base station 105-a.

[0108] BWP 210 can be used in both paired and unpaired spectrum. In paired spectrum, a first frequency spectrum band can be allocated (e.g., dedicated to) downlink communication, and a second frequency spectrum band can be allocated (e.g., dedicated to) uplink communication. Paired spectrum can be used with an FDD system to establish bidirectional communication between nodes. In unpaired spectrum, the same frequency spectrum band can be used for both uplink and downlink communication. Unpaired spectrum can be used with a TDD system to establish bidirectional communication between nodes. In some cases, for paired spectrum, the maximum number of BWPs configured can be four downlink BWPs and four uplink BWPs. In some cases, for unpaired spectrum, the maximum number of BWPs configured can be four downlink / uplink BWP pairs. In some cases, for FDD, BWPs for downlink and BWPs for uplink can be configured independently on a per-component carrier (CC) basis. In some cases, for TDD, a joint set of downlink and uplink BWPs can be configured on a per-CC basis.

[0109] In some cases, the active BWP 210 of UE 115-a may not span a frequency spectrum band larger than the bandwidth of the CC of UE 115-a. Configuration for a downlink BWP may include at least one control resource set (coreset). In some cases, at least one configured downlink BWP may include a coreset with a control search space (CSS) in the primary component carrier (PCC). In some cases, a CSS may be configured in each BWP 210 within the PCell for UE 115-a. In some cases, for the case of a single active BWP, at a given time, each configured downlink BWP may include at least one coreset with a UE-specific search space (UE-SS). In some cases, if the active downlink BWP does not include a CSS, UE 115-a may not monitor the CSS. The CSS may include communication resources in which the UE is configured to search for a physical downlink control channel (PDCCH) carrying downlink control information (DCI) as its payload.

[0110] When establishing an RRC connection, UE 115-a or base station 105-a may activate the default configuration of one or more BWP 210s (e.g., downlink BWP and uplink BWP). UE 115-a and base station 105-a may use those default BWP 210s until the BWP 210s are explicitly configured or reconfigured.

[0111] The wireless communication system 200 can also support BWP handover events. In some cases, UE 115-a (or base station 105-a) can be configured to use one BWP 210 on carrier 205 at a time. In such cases, if UE 115-a (or base station 105-a) wants to use a different BWP on carrier 205, UE 115-a (or base station 105-a) can reconfigure its BWP 210. As part of a BWP handover event, UE 115-a (or base station 105-a) can hand over the active BWP to a target BWP within a given serving cell. A DCI can be used to send BWP handover events via signaling. In some cases, downlink scheduling DCI can be used to hand over downlink BWP 210, and uplink scheduling DCI can be used to hand over uplink BWP 210. In some cases, either downlink DCI or uplink DCI can be used to hand over either downlink BWP or uplink BWP. In some cases, the wireless communication system 200 may support a timer for time-based switching of the active BWP. In such a time-based configuration, BWP 210 may switch from the active BWP 210 to the default BWP 210 based on the timer expiring.

[0112] As described herein, various techniques can be used for efficient BWP handover in a wireless communication system 200. For example, BWP handover may include time-domain resource allocation (e.g., to allow transitions between BWPs 210). Aspects of this disclosure relate to support for such time-domain resource allocation, including considerations for timing parameter tables, timing parameter interpretation, BWP signaling, etc.

[0113] Figure 3 An example of a communication diagram 300 supporting timing parameter management for bandwidth partial switching according to various aspects of this disclosure is shown. In some examples, the communication diagram 300 may implement various aspects of the wireless communication system 100. The communication diagram includes a base station 105-b and a UE 115-b, each of which may be a reference. Figure 1 Examples of the corresponding devices described.

[0114] Base station 105-b and UE 115-b can establish communication on the PCC, as shown in the reference. Figure 2As described. For example, base station 105-b can configure UE 115-b via RRC signaling to have one or more BWPs (including BWP 305), wherein each BWP can be associated with one or more timing parameter tables 325 (e.g., one table per BWP for uplink; and one table per BWP for downlink). Each timing parameter table 325 can, for example, contain up to sixteen rows, wherein each row can be configured to have an index of a table or equation with k0 (for downlink timing parameter table 325) or k2 (for uplink timing parameter table 325), a valid combination of capture start symbol and symbol length (e.g., which can be jointly encoded), and a mapping type (e.g., a PDSCH mapping type for downlink timing parameter table 325, or a PUSCH mapping type for uplink timing parameter table 325). In this example, base station 105-b can configure UE 115-b to have timing parameter table 325-a for downlink communication in BWP 305 and timing parameter table 325-b for downlink communication in another BWP (e.g., for which k0 and PDSCH mapping type, along with PDSCH start symbol and symbol length are configured). Although described in the context of downlink communication, similar techniques can be used for uplink communication (e.g., using a BWP for which k2 and PUSCH mapping type, along with PUSCH start symbol and symbol length are configured).

[0115] In some cases, the device may subsequently communicate via BWP 305 (e.g., which may be an example of BWP 210). In some cases, communication on BWP 305 may be supported via DCI 310. For example, DCI 310 may be used for downlink resource allocation (e.g., DCI format 1_1), uplink resource allocation (e.g., DCI format 0_1), etc. DCI 310 may include multiple bit fields, including a BWP ID field 315 and a resource allocation field 320 (e.g., which may be alternatively referred to as a time-domain resource allocation field 320). As described above, one or more bit fields of DCI 310 may be sized at least in part based on BWP 305.

[0116] For example, the resource allocation field 320 may have a single bit for distinguishing between rows 330-a of timing parameter table 325-a. However, timing parameter management can support BWP handover when the BWP ID field 315 indicates another BWP (e.g., for which a BWP is configured in timing parameter table 325-b). Because the resource allocation field 320 contains a single bit, only row 330-b of timing parameter table 325-b can be addressable via DCI 310 (e.g., making row 330-c potentially unavailable for BWP handover). Aspects of this disclosure relate to considerations for the format of timing parameter table 325-b for supporting BWP handover (e.g., making row 330-b contain timing parameters that support efficient BWP handover).

[0117] Although described in the context of two timing parameter tables 325, in some cases, BWP handover can be supported by a single timing parameter table 325 (e.g., a table configured for BWP handover events via RRC signaling). Such a table can be supported, for example, by a DCI 310 with a set (e.g., pre-configured, negotiated, etc.) length of a resource allocation field 320 that indicates BWP handover.

[0118] Figure 4 Examples of a transmission scheme 400 supporting timing parameter management for bandwidth portion switching according to various aspects of this disclosure are shown. In some examples, the transmission scheme 400 may implement various aspects of the wireless communication system 100. For example, the transmission scheme 400 may illustrate various aspects of communication between base station 105 and UE 115 on multiple (e.g., three) BWPs. For example, base station 105 may configure UE 115 to have a timing parameter table 420-a for BWP 405 (e.g., starting BWP), a timing parameter table 420-b for BWP 410 (e.g., which may support data communication), and a timing parameter table 420-c for BWP 415 (e.g., default BWP).

[0119] Although described in the context of three BWPs, it is to be understood that the techniques described using reference transmission scheme 400 can support any suitable number of BWPs. Similarly, the size and contents of timing parameter table 420 are included for illustrative purposes rather than to limit the scope. For example, although described in the context of k0 timing parameters, it is to be understood that similar techniques can be used for k2 timing parameter management. Additionally, in some cases, timing parameter table 420 may contain up to sixteen (e.g., or more) rows. At least some rows in a given timing parameter table may share common k0 or k2 values ​​(e.g., but may be distinguished by mapping type and / or symbol length indicator value (SLIV)). For illustrative purposes, it is assumed that the rows of timing parameter table 420 are distinguished based on k0 values.

[0120] In this example, base station 105 can transmit DCI during time slot 425-a on BWP 405. For example, the DCI in time slot 425-a can be a reference Figure 3 An example of the described DCI 310. Because the DCI in time slot 425-a is transmitted on BWP 405, it can have a resource allocation field with a bit length of zero bits (e.g., because timing parameter table 420-a contains a single row). However, the DCI in time slot 425-a can include a BWP ID field (e.g., a field indicating BWP 410) to indicate BWP handover. That is, the DCI in time slot 425-a can be scheduled for PDSCH transmission on BWP 410. Therefore, the resource allocation field of the DCI in time slot 425-a can be used by the UE 115 receiving the DCI to understand and index the timing parameter table 420-b (e.g., the timing parameter table 420 corresponding to the BWP indicated in the BWP ID field). Because the resource allocation field of the DCI in time slot 425-a may not be addressable in the second or third row of timing parameter table 420-b, UE 115 can identify the value of k0=4 for BWP handover. For example, k0=4 could mean a duration 430 of four time slots (e.g., or some other appropriate time interval) between the PDSCH transmission scheduled in time slot 425-a and time slot 425-b.

[0121] UE 115-b can receive PDSCH transmissions scheduled in slot 425-b of BWP 410. In some cases, UE 115-b can receive DCIs in slot 425-c, where PDSCH transmissions are scheduled on BWP 410. That is, because the resource allocation field of the DCI in slot 425-c can be sized based on timing parameter table 420-b (e.g., it can have a length of two bits), all rows in timing parameter table 420-b can be addressed via the DCI in slot 425-b. Accordingly, the DCI in slot 425-c can indicate a value of k0 = 0 (e.g., a zero-slot delay between the DCI used to schedule the PDSCH transmission and the PDSCH transmission itself). Accordingly, UE 115-b can receive PDSCH transmissions in slot 425-c.

[0122] Following time slot 425-c, BWP timer 435 may run (e.g., within a configured, negotiated number of time slots 425). Although shown as containing five time slots 425, it is to be understood that in some cases, BWP timer 435 may contain more or fewer than five time slots 425. BWP timer 435 can run as long as UE 115 is not receiving data. Therefore, the device can still monitor BWP 410 (e.g., as shown by BWP 410-b) even when not receiving data (e.g., this can reduce the device's power consumption compared to time slots 425-b and 425-c shown by BWP 410-a). Therefore, it is to be understood that BWP 410-a and BWP 410-b may refer to the same BWP (e.g., the same PRB set), but may represent different power consumption on that BWP based on whether data is being transmitted.

[0123] When BWP timer 435 expires, UE 115 may switch to BWP 415 (e.g., which could be an example of the default BWP). Alternatively, the switch to BWP 415 may be based on explicit DCI signaling (e.g., within a time slot included in BWP timer 435) rather than on the expiration of BWP timer 435. In some cases, the switch to BWP 415 may occupy a duration 440, which is based on an indicated (e.g., in the case of explicit DCI signaling) or understood (e.g., in the case of timer expiration) value of k0. For example, if the explicit DCI signaling indicates k0 = 2 (e.g., since all rows of timing parameter table 420-b are addressable via DCI sent in BWP 410), then duration 440 may last for two time slots (e.g., during which time UE 115 does not expect to receive downlink signals from base station 105).

[0124] In some cases, UE 115 may receive a DCI in time slot 425-d indicating k0=1 (e.g., indexing the third row of timing parameter table 420-c). For example, such a k0 configuration (e.g., a small non-zero k0 value) may support micro-sleep operation for UE 115. Accordingly, UE 115 may receive PDSCH transmissions in time slot 425-e based on the scheduling received via the DCI in time slot 425-d. In time slot 425-f, the UE may receive a DCI indicating k0=2 (e.g., indexing the second row of timing parameter table 420-b) and indicating BWP handover (e.g., handover to BWP 410). Since timing parameter tables 420-b and 420-c have the same size, transformations for the DCI (e.g., truncation or zero-padding) may not be necessary. Based on the DCI in time slot 425-f, the UE can receive PDSCH in time slot 425-g (e.g., following two time slots indicated by the DCI and represented by duration 445).

[0125] In some cases, support for a minimum k0 (e.g., k2) value can be considered in the layout of timing parameter table 420. For example, for PDCCH to PDSCH modem wake-up, the wireless communication system can benefit from a timing parameter table 420 with a large k0 (e.g., k0 = 4) associated with waking up the BWP (e.g., BWP 405). Similarly, for low-latency access during data scheduling, the wireless communication system can benefit from a timing parameter table 420 with a small k0 (e.g., k0 = 0). Finally, for micro-sleep operation as described above, the wireless communication system can benefit from a timing parameter table with a small non-zero k0 (e.g., k0 = 1). Therefore, a minimum k0 value may be important for power savings at UE 115 (e.g., by providing flexibility in PDSCH modem activation and maintenance). According to various aspects of this disclosure, one or more timing parameter tables 420 can be configured such that the lowest-indexed row (e.g., a row addressable via a shorter resource allocation field) can contain important k0 values ​​for one or more of the operations described above. In some examples, the lowest-indexed row (e.g., a row addressable via a shorter resource allocation field) can include k0 values ​​that can be sorted from larger k0 values ​​in the accessible portion of the timing parameter table to lower k0 values ​​further down the timing parameter table. In some examples, the minimum k0 (e.g., or k2) value can be adjusted when switching communication from a first BWP to a second BWP.

[0126] Figure 5Examples of a transmission scheme 500 supporting timing parameter management for bandwidth partial switching according to various aspects of this disclosure are shown. In some examples, transmission scheme 500 may implement various aspects of wireless communication system 100. For example, transmission scheme 400 may illustrate various aspects of communication between base station 105 and UE 115 on multiple (e.g., two) BWPs. For example, base station 105 may configure UE 115 to have a timing parameter table 515-a for BWP 505 (e.g., a low-power BWP) and a timing parameter table 515-b for BWP 510 (e.g., a high-power BWP). For example, BWP 510 may be associated with a wider bandwidth compared to BWP 505. Alternatively, BWP 510 and BWP 505 may have the same bandwidth, and power savings for BWP 505 may be adapted based on k0 (e.g., or k2).

[0127] Aspects of this example may involve support for two-stage wake-up and efficient microsleep operations. Supplementally or alternatively, aspects of this example may involve support for three minimum k0 values ​​on two BWPs (e.g., with reference to...). Figure 4 (Compared to the support of the three minimum k0 values ​​on the three BWPs described). Figure 4 Similarly, the following aspects are included for the purpose of explanation rather than limitation.

[0128] UE 115 can wake up during time slot 520-a (e.g., based on discontinuous reception cycles, wake-up signals, etc.) and receive DCI on BWP 505. DCI may include the BWP ID of BWP 510 (e.g., cross-BWP scheduling) and a resource allocation field (e.g., a zero-bit resource allocation field) sized according to timing parameter table 515-a. Due to cross-BWP scheduling, the resource allocation field can be indexed to timing parameter table 515-b. Accordingly, UE 115 can determine k0 = 4 such that the duration 425 between receiving DCI in time slot 520-a and receiving PDSCH in time slot 520-b can last for four time slots. For example, such a relatively large k0 can allow sufficient time for PDCCH-PDSCH modem wake-up (e.g., thereby supporting power savings for UE 115).

[0129] Once BWP 510 becomes the active BWP, the resource allocation field of the DCI can be sized according to timing parameter table 515-b (e.g., making k0 = 0 addressable for data scheduling). Accordingly, the DCI received in time slot 520-c can indicate the same time slot PDSCH scheduling (e.g., k0 = 0). BWP timer 525 can be a reference Figure 4An example of the described BWP timer 435. Therefore, BWP timer 525 could be an example of the duration during which UE 115 monitors transmission on BWP 510-b (e.g., this could represent lower transmission power compared to BWP 510-a during timeslots 520-b and 520-c, because PDSCH is absent). When BWP timer 525 expires (e.g., or based on explicit DCI signaling), UE 115 can switch to BWP 505 (e.g., after duration 530). For example, duration 530 could be based on timing parameter table 515-a (e.g., due to the transition to BWP 505). Therefore, k0 = 1 and duration 530 could represent a timeslot. Once BWP 505 becomes the active BWP, k0 can be set to a timeslot (e.g., k0 = 1) to support micro-sleep operation.

[0130] UE 115 can switch between BWP 505 and BWP 510 based on scheduling. For example, BWP 505 can be used to support micro-sleep operation (e.g., low-power BWP), and BWP 510 can be used for data scheduling activities (e.g., where k0 = 0 once BWP 510 becomes the active BWP).

[0131] Within the scope of this disclosure are considerations regarding support for timing parameter management for devices with two BWPs. For example, during normal operation (e.g., non-wake-up operation), a handover from BWP 505 to BWP 510 can cause a large k0 delay (e.g., even if the modem has been woken up). Such a limitation can be addressed, for example, by allowing UE 115 to schedule DCIs across BWPs in an active mode (e.g., allowing UE 115 to derive k0 = 1). Alternatively, aspects of this disclosure can be supported by scheduling restrictions that allow only cross-BWP scheduling within wake-up slots (e.g., slots at the beginning of a discontinuous reception cycle, such as slot 520-a). Otherwise, based on timing parameter table 515-a, UE 115 might have to prepare for scheduling the same BWP with a smaller k0 (e.g., k0 = 1) (e.g., unless k0 is also configured to be large for timing parameter table 515-a).

[0132] The aspects of DCI transmission described above can be applied to non-backoff DCI operation (e.g., because only non-backoff DCI can be used to support BWP handover). If backoff DCI is supported in a wake-up slot (e.g., slot 520-a), then the backoff DCI (e.g., at least for the Cellular Radio Network Temporary Identifier (C-RNTI)) must also share the same timing parameter table 515 as the non-backoff DCI. Otherwise, UE 115 may have to prepare for scheduling using a different set of k0 parameters (e.g., if the backoff DCI uses a table where {1,2,3,…8} are possible k0 values), making power savings impractical. Another way to address the use of backoff DCI is to not configure a common search space at all (e.g., and, in the case of non-backoff DCI support, only a user-specific search space).

[0133] Figure 6 Examples of a transmission scheme 600 supporting timing parameter management for bandwidth portion switching according to various aspects of this disclosure are shown. In some examples, transmission scheme 600 may implement various aspects of wireless communication system 100. For example, transmission scheme 600 may illustrate various aspects of communication between base station 105 and UE 115 on multiple (e.g., three) BWPs. For example, base station 105 may configure UE 115 to have timing parameter table 620-a for BWP 605 (e.g., default BWP, narrowband BWP), timing parameter table 620-b for BWP 610 (e.g., for supporting wideband BWPs with the same time slot scheduling), and timing parameter table 620-c for BWP 615 (e.g., for supporting wideband BWPs with cross-time slot scheduling).

[0134] Base station 105 can transmit DCI on BWP 605 during time slot 625-a, where the DCI can indicate BWP 610 in the BWP ID bit field (e.g., across BWP scheduling). Because the resource allocation field of the DCI in time slot 625-a can be sized according to timing parameter table 620-a, the third row of timing parameter table 620-b (e.g., k0 = 0) may not be addressable via the resource allocation field. In some examples, k0 = 2 can be selected from timing parameter table 620-b (e.g., such that the duration 630 between time slots 625-a and 625-b can be two time slots). UE 115, used to receive the DCI, can then receive PDSCH on BWP 610 in time slot 625-b. Subsequently (e.g., in time slot 625-c), k0 = 0 can be selected (e.g., because all rows of timing parameter table 620-b can be addressable). Accordingly, UE 115 can receive both the DCI for scheduling PDSCH and the PDSCH itself on BWP 610 in time slot 625-c. Therefore, BWP 610 can support scheduling in the same time slot.

[0135] In time slot 625-d, UE 115 can receive a DCI (e.g., a DCI containing a BWP ID field indicating BWP 615) on BWP 610. The DCI in time slot 625-d can be indexed in timing parameter table 620-c. Since the resource allocation field of the DCI can contain two bits (e.g., based on timing parameter table 620-b containing three rows), UE 115 can discard the most significant bit of the resource allocation field when interpreting it. That is, UE 115 can use the least significant bit of the resource allocation field to distinguish between two rows in timing parameter table 620-c. In this example, the resource allocation field can indicate k0 = 1, causing UE 115 to determine that the PDSCH on BWP 615 is included in time slot 625-e. BWP 615 can support cross-slot scheduling (e.g., k0=2 or k0=1), and therefore, BWP 615 can be associated with lower transmission power costs compared to BWP 610. A DCI transmitted on BWP 615 in slot 625-f can instruct BWP 605 and select k0=2 (e.g., such that duration 635 includes both slots 625). Subsequently, UE 115 can receive PDSCH on BWP 605 in slot 625-g based on the scheduling DCI received in slot 625-f. Since timing parameter tables 620-a and 620-c have the same size, when switching between BWP 605 and BWP 615, transformations to the resource allocation fields (e.g., truncation or zero-padding) may not be required.

[0136] Figure 7 An example of a process flow 700 supporting timing parameter management for bandwidth partial switching according to various aspects of this disclosure is shown. In some examples, process flow 700 may implement various aspects of wireless communication system 100. For example, process flow 700 includes UE 115-c and base station 105-c, each of which may be a reference Figure 1 Examples of the corresponding devices described.

[0137] At 705, UE 115-c (e.g., and base station 105-c) can identify a set of timing parameter tables for one or more potential values ​​of various custom timing parameters (e.g., k0, k2), which are associated with the timing between the last symbol of the DCI transmission and the time slot of the data communication contained between the devices. For example, the set of timing parameter tables may include a first timing parameter table associated with a first BWP and a second timing parameter table associated with a second BWP. In some cases, the set of timing parameter tables may be identified based on signaling of configuration tables (e.g., RRC signaling).

[0138] In some cases, the first timing parameter table has a first number of rows, and the second timing parameter table has a different number of rows. In some cases, when the first timing parameter table is associated with an uplink transmission on the first BWP, the set of timing parameter tables also includes a third timing parameter table associated with a downlink transmission on the first BWP. In some cases, the first BWP has a first digital scheme (e.g., a first tone interval), and the second BWP has a second digital scheme (e.g., a different tone interval), and the potential values ​​for timing parameters indicated by the timing parameter tables may be at least partially based on the corresponding tone intervals. That is, the tone interval can affect the duration of the time slot, which in turn can affect the interpretation of the timing parameters.

[0139] At 710, base station 105-c can identify a trigger for switching communication with UE 115-c from a first BWP to a second BWP. It should be understood that prior to 710, the first BWP may represent the currently active BWP (e.g., wake-up BWP, default BWP, etc.). In some cases, the trigger may include the data type to be sent, the amount of data to be sent, the traffic volume associated with one or both of the BWPs, etc.

[0140] At 715, base station 105-c can select values ​​for timing parameters based at least in part on triggering and a second timing parameter table. That is, base station 105-c can configure the DCI to include a BWP handover indication (e.g., a BWP ID for a second BWP) and a resource allocation field indicating values ​​for timing parameters from the second timing parameter table. In some cases, the size of the resource allocation field (e.g., and therefore the value selected from the second timing parameter table) can be based in part on the number of rows in the first timing parameter table.

[0141] At 720, base station 105-c can transmit DCI on the first BWP (e.g., and UE 115-c can receive DCI on the first BWP). DCI can activate the second BWP and includes a resource allocation bit field indicating the value for timing parameters.

[0142] At 725, UE 115-c can identify values ​​for timing parameters based on the resource allocation bit field and the second timing parameter table. For example, the resource allocation bit field can provide an index to the second timing parameter table, as described above. Figure 4 and Figure 5 As described.

[0143] At 730, UE 115-c and base station 105-c can communicate on the second BWP based on values ​​for timing parameters. For example, UE 115-c can receive PDSCH transmissions from base station 105-c (e.g., or send PUSCH transmissions to base station 105-c), where the timing of the transmissions can be based on values ​​for timing parameters.

[0144] Figure 8 A block diagram 800 illustrates a device 805 supporting timing parameter management for bandwidth partial switching according to various aspects of this disclosure. The wireless device 805 may be an example of various aspects of the UE 115 as described herein. The device 805 may include a receiver 810, a communications manager 815, and a transmitter 820. The device 805 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0145] Receiver 810 can receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to timing parameter management for bandwidth segment switching). It can transmit this information to other components of device 805. Receiver 810 can be a reference... Figure 11 Examples of various aspects of the transceiver 1120 described. The receiver 810 may utilize a single antenna or a set of antennas.

[0146] Communication manager 815 can identify a set of timing parameter tables for one or more potential values ​​of custom timing parameters associated with timing between the reception of DCI from a base station and subsequent communication with the base station. The set of timing parameter tables includes at least a first timing parameter table associated with a first BWP and a second timing parameter table associated with a second BWP. Communication manager 815 can receive DCI transmissions on the first BWP to activate the second BWP. The DCI transmissions include a resource allocation bit field indexed to at least a subset of the second timing parameter table, wherein the size of the resource allocation bit field is based on the configuration of the first BWP. Communication manager 815 can identify values ​​for timing parameters based on the second timing parameter table and the size of the resource allocation bit field. Communication manager 815 can communicate with the base station on the second BWP based on the values ​​for the timing parameters. Communication manager 815 can be an example of various aspects of communication manager 1110 described herein.

[0147] The communication manager 815 or its sub-components may be implemented in hardware, processor-executable code (e.g., software or firmware), or any combination thereof. If implemented in processor-executable code, the functionality of the communication manager 815 or its sub-components may be performed by a general-purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware component, or any combination thereof designed to perform the functions described in this disclosure.

[0148] The communication manager 815 or its subcomponents may be physically located at various locations, including being distributed such that some functions are implemented by one or more physical components at different physical locations. In some examples, according to various aspects of this disclosure, the communication manager 815 or its subcomponents may be separate and distinct components. In some examples, according to various aspects of this disclosure, the communication manager 815 or its subcomponents may be combined with one or more other hardware components, including but not limited to input / output (I / O) components, transceivers, network servers, other computing devices, one or more other components described in this disclosure, or combinations thereof.

[0149] Transmitter 820 can transmit signals generated by other components of device 805. In some examples, transmitter 820 can be co-located with receiver 810 in a transceiver module. For example, transmitter 820 can be a reference... Figure 11 Examples of various aspects of the transceiver 1120 described. The transmitter 820 may utilize a single antenna or a set of antennas.

[0150] Figure 9A block diagram 900 illustrates a device 905 supporting timing parameter management for bandwidth partial switching according to various aspects of this disclosure. Device 905 may be an example of aspects of device 805 or UE 115 as described herein. Device 905 may include a receiver 910, a communication manager 915, and a transmitter 940. Device 905 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0151] Receiver 910 can receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to timing parameter management for bandwidth segment switching). This information can be passed to other components of device 905. Receiver 910 can be a reference... Figure 11 Examples of various aspects of the transceiver 1120 are described. The receiver 910 may utilize a single antenna or a set of antennas.

[0152] Communication manager 915 may be an example of aspects of communication manager 815 as described herein. Communication manager 915 may include table manager 920, control manager 925, parameter manager 930, and data manager 935. Communication manager 915 may be an example of aspects of communication manager 1110 as described herein.

[0153] Table manager 920 can identify a set of timing parameter tables for one or more potential values ​​of custom timing parameters associated with timing between the reception of DCI from the base station and subsequent communication with the base station. The set of timing parameter tables includes at least a first timing parameter table associated with a first BWP and a second timing parameter table associated with a second BWP. Control manager 925 can receive DCI transmissions on the first BWP to activate the second BWP. These DCI transmissions include a resource allocation bit field indexed to at least a subset of the second timing parameter table, wherein the size of the resource allocation bit field is based on the configuration of the first BWP. Parameter manager 930 can identify values ​​for timing parameters based on the second timing parameter table and the size of the resource allocation bit field. Data manager 935 can communicate with the base station on the second BWP based on the values ​​for the timing parameters.

[0154] Transmitter 940 can transmit signals generated by other components of device 905. In some examples, transmitter 940 can be co-located with receiver 910 in a transceiver module. For example, transmitter 940 can be a reference... Figure 11 Examples of various aspects of the transceiver 1120 are described. The transmitter 940 may utilize a single antenna or a set of antennas.

[0155] Figure 10 A block diagram 1000 illustrates a communication manager 1005 supporting timing parameter management for bandwidth partial switching according to various aspects of this disclosure. The communication manager 1005 may be an example of aspects of the communication manager 815, communication manager 915, or communication manager 1110 described herein. The communication manager 1005 may include a table manager 1010, a control manager 1015, a parameter manager 1020, and a data manager 1025. Each of these modules may communicate with each other directly or indirectly (e.g., via one or more buses).

[0156] Table manager 1010 can identify a set of timing parameter tables, each containing one or more potential values ​​for a custom timing parameter associated with the timing of a DCI reception from a base station and subsequent communication with the base station. The set of timing parameter tables includes at least a first timing parameter table associated with a first BWP and a second timing parameter table associated with a second BWP. In some examples, table manager 1010 can receive at least one timing parameter table from the set of timing parameter tables via RRC signaling. In some cases, the first timing parameter table includes a first set of rows, and the second timing parameter table includes a second set of rows, each row in the first and second sets indicating a potential value for the timing parameter. In some such cases, the size of the resource allocation bit field is based on the number of rows in the first set of rows.

[0157] In some cases, a first timing parameter table is associated with uplink transmissions on the first BWP, and the set of timing parameter tables also includes a third timing parameter table associated with downlink transmissions on the first BWP. In some cases, the first BWP has a first tone interval, and the second BWP has a second tone interval, wherein the potential values ​​for timing parameters in the first timing parameter table are based on the first tone interval, and the potential values ​​for timing parameters in the second timing parameter table are based on the second tone interval. In some cases, the first BWP is associated with lower transmission power compared to the second BWP.

[0158] Control manager 1015 can receive a DCI transmission on a first BWP for activating a second BWP. The DCI transmission includes a resource allocation bit field indexed to at least a subset of a second timing parameter table, wherein the size of the resource allocation bit field is based on the configuration of the first BWP. In some examples, control manager 1015 can identify the format for the DCI transmission. In some examples, control manager 1015 can select a second timing parameter table from a set of timing parameter tables based on the format of the DCI transmission. In some cases, the DCI transmission includes a BWP identifier field for activating the second BWP.

[0159] The parameter manager 1020 can identify values ​​for timing parameters based on the size of the second timing parameter table and the resource allocation bit field. In some examples, the parameter manager 1020 can identify a subset of bits in the resource allocation bit field used to index rows in the second row set. In some examples, the parameter manager 1020 can determine the value for the timing parameter based on the indexed rows in the second row set. In some examples, the parameter manager 1020 can identify a subset of the second row set that is addressable via the resource allocation bit field. In some examples, the parameter manager 1020 can identify rows indexed via the resource allocation bit field within a subset of the second row set. In some examples, the parameter manager 1020 can determine the value for the timing parameter based on the indexed rows. In some cases, the subset of the second row set includes the row with the lowest index in the second row set, and the row with the lowest index corresponds to a preferred value for the timing parameter used to switch to the second BWP. In some cases, a subset of the second set includes the maximum value among the potential values ​​for the timing parameters from the second set of multiple sets, wherein the values ​​of the timing parameters are sorted from the larger values ​​of the timing parameters used to switch to the second BWP to the smaller values ​​of the timing parameters used to switch to the second BWP.

[0160] In some cases, a subset of the second set includes at least one row corresponding to preferred values ​​of timing parameters used for communication in the second BWP. In some cases, preferred values ​​of timing parameters include a first value for wake-up communication, a second value for data communication, or a third value for micro-sleep communication.

[0161] Data Manager 1025 can communicate with the base station on the second BWP based on the values ​​of timing parameters. In some examples, Data Manager 1025 can receive PDSCH transmissions. In some examples, Data Manager 1025 can send PUSCH transmissions.

[0162] Figure 11 A diagram of a system 1100 including device 1105 supporting timing parameter management for bandwidth portion switching, according to various aspects of this disclosure, is shown. Device 1105 may be an example of device 805, device 905, or UE 115 as described herein, or a component including device 805, device 905, or UE 115. Device 1105 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, including a communication manager 1110, an I / O controller 1115, a transceiver 1120, an antenna 1125, a memory 1130, and a processor 1140. These components may communicate electronically via one or more buses (e.g., bus 1145).

[0163] Communication manager 1110 can identify a set of timing parameter tables for one or more potential values ​​of custom timing parameters associated with timing between the reception of DCI from a base station and subsequent communication with the base station. The set of timing parameter tables includes at least a first timing parameter table associated with a first BWP and a second timing parameter table associated with a second BWP. Communication manager 1110 can receive DCI transmissions on the first BWP to activate the second BWP. The DCI transmissions include a resource allocation bit field indexed to at least a subset of the second timing parameter table, wherein the size of the resource allocation bit field is based on the configuration of the first BWP. Communication manager 1110 can identify values ​​for timing parameters based on the second timing parameter table and the size of the resource allocation bit field. Communication manager 1110 can communicate with the base station on the second BWP according to the values ​​for the timing parameters.

[0164] I / O controller 1115 can manage input and output signals for device 1105. I / O controller 1115 can also manage peripheral devices not integrated into device 1105. In some cases, I / O controller 1115 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 1115 can utilize, for example... MS- MS- OS / The operating system may be a known operating system. In other cases, the I / O controller 1115 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 1115 may be implemented as part of the processor. In some cases, a user may interact with the device 1105 via the I / O controller 1115 or via hardware components controlled by the I / O controller 1115.

[0165] Transceiver 1120 can communicate bidirectionally via one or more antennas, wired or wireless links as described above. For example, transceiver 1120 can represent a wireless transceiver and can communicate bidirectionally with another wireless transceiver. Transceiver 1120 may also include a modem for modulating packets and providing the modulated packets to the antenna for transmission, and demodulating packets received from the antenna. In some cases, the wireless device may include a single antenna 1125. However, in some cases, the device may have more than one antenna 1125, which may be able to transmit or receive multiple wireless transmissions simultaneously.

[0166] Memory 1130 may include RAM and ROM. Memory 1130 may store computer-readable, computer-executable code 1135, which includes instructions that, when executed, cause the processor to perform the various functions described herein. In some cases, memory 1130 may contain a BIOS, which controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0167] Processor 1140 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, processor 1140 may be configured to use a memory controller to operate a memory array. In other cases, the memory controller may be integrated into processor 1140. Processor 1140 may be configured to execute computer-readable instructions stored in memory (e.g., memory 1130) to cause device 1105 to perform various functions (e.g., functions or tasks supporting timing parameter management for bandwidth partial switching).

[0168] Code 1135 may include instructions for implementing various aspects of this disclosure, including instructions for supporting wireless communication. Code 1135 may be stored in a non-transitory computer-readable medium, such as system memory or other types of memory. In some cases, code 1135 may not be directly executable by processor 1140, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein.

[0169] Figure 12 A block diagram 1200 illustrates a device 1205 supporting timing parameter management for bandwidth partial switching according to various aspects of this disclosure. Device 1205 may be an example of various aspects of base station 105 as described herein. Device 1205 may include a receiver 1210, a communication manager 1215, and a transmitter 1220. Device 1205 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0170] Receiver 1210 can receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to timing parameter management for bandwidth portion switching). This information can be passed to other components of device 1205. Receiver 1210 can be a reference... Figure 15 Examples of various aspects of the transceiver 1520 described. The receiver 1210 may utilize a single antenna or a set of antennas.

[0171] Communication manager 1215 can identify a set of timing parameter tables for one or more potential values ​​of custom timing parameters associated with the timing of a DCI transmission to the UE and subsequent communication with the UE. The set of timing parameter tables includes at least a first timing parameter table associated with a first BWP and a second timing parameter table associated with a second BWP. Communication manager 1215 can identify triggers for switching communication with the UE from the first BWP to the second BWP. Communication manager 1215 can select values ​​for the timing parameters based on the triggers and the second timing parameter tables. Communication manager 1215 can send a DCI transmission on the first BWP to activate the second BWP. The DCI transmission includes a resource allocation bit field indicating the value of the timing parameter, wherein the size of the resource allocation bit field is based on the configuration of the first BWP. Communication manager 1215 can communicate with the UE on the second BWP according to the value of the timing parameter. Communication manager 1215 can be an example of various aspects of communication manager 1510 described herein.

[0172] The communication manager 1215 or its sub-components may be implemented in hardware, processor-executable code (e.g., software or firmware), or any combination thereof. If implemented in processor-executable code, the functionality of the communication manager 1215 or its sub-components may be performed by a general-purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware component, or any combination thereof designed to perform the functions described in this disclosure.

[0173] The communication manager 1215 or its subcomponents may be physically located at various locations, including being distributed such that some functions are implemented by one or more physical components at different physical locations. In some examples, according to various aspects of this disclosure, the communication manager 1215 or its subcomponents may be separate and distinct components. In some examples, according to various aspects of this disclosure, the communication manager 1215 or its subcomponents may be combined with one or more other hardware components, including but not limited to input / output (I / O) components, transceivers, network servers, other computing devices, one or more other components described in this disclosure, or combinations thereof.

[0174] Transmitter 1220 can transmit signals generated by other components of device 1205. In some examples, transmitter 1220 may be co-located with receiver 1210 in a transceiver module. For example, transmitter 1220 may be a reference... Figure 15 Examples of various aspects of the transceiver 1520 described. The transmitter 1220 may utilize a single antenna or a set of antennas.

[0175] Figure 13 A block diagram 1300 illustrates a device 1305 supporting timing parameter management for bandwidth partial switching according to various aspects of this disclosure. Device 1305 may be an example of aspects of device 1205 or base station 115 as described herein. Device 1305 may include a receiver 1310, a communication manager 1315, and a transmitter 1345. Device 1305 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0176] Receiver 1310 can receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to timing parameter management for bandwidth portion switching). This information can be passed to other components of device 1305. Receiver 1310 can be a reference... Figure 15 Examples of various aspects of the transceiver 1520 described. The receiver 1310 may utilize a single antenna or a set of antennas.

[0177] Communication manager 1315 may be an example of aspects of communication manager 1215 as described herein. Communication manager 1315 may include table controller 1320, switching manager 1325, parameter controller 1330, control manager 1335, and data manager 1340. Communication manager 1315 may be an example of aspects of communication manager 1510 as described herein.

[0178] Table controller 1320 can identify a set of timing parameter tables for one or more potential values ​​of custom timing parameters associated with the timing of a DCI transmission to the UE and subsequent communication with the UE. The set of timing parameter tables includes at least a first timing parameter table associated with a first BWP and a second timing parameter table associated with a second BWP. Handover manager 1325 can identify triggers for switching communication with the UE from the first BWP to the second BWP. Parameter controller 1330 can select values ​​for the timing parameters based on the triggers and the second timing parameter tables. Control manager 1335 can send a DCI transmission on the first BWP to activate the second BWP. The DCI transmission includes a resource allocation bit field indicating the value of the timing parameter, wherein the size of the resource allocation bit field is based on the configuration of the first BWP. Data manager 1340 can communicate with the UE on the second BWP based on the value of the timing parameter.

[0179] Transmitter 1345 can transmit signals generated by other components of device 1305. In some examples, transmitter 1345 may be co-located with receiver 1310 in a transceiver module. For example, transmitter 1345 may be a reference... Figure 15Examples of various aspects of the transceiver 1520 are described. The transmitter 1345 can utilize a single antenna or a set of antennas.

[0180] Figure 14 A block diagram 1400 illustrates a communication manager 1405 supporting timing parameter management for bandwidth portion switching according to various aspects of this disclosure. The communication manager 1405 may be an example of aspects of the communication manager 1215, communication manager 1315, or communication manager 1510 described herein. The communication manager 1405 may include a table controller 1410, a switching manager 1415, a parameter controller 1420, a control manager 1425, and a data manager 1430. Each of these modules may communicate directly or indirectly with each other (e.g., via one or more buses).

[0181] Table controller 1410 can identify a set of timing parameter tables, each with one or more potential values ​​for a custom timing parameter associated with the timing of a transmission to the UE for DCI and subsequent communication with the UE. The set of timing parameter tables includes at least a first timing parameter table associated with a first BWP and a second timing parameter table associated with a second BWP. In some examples, table controller 1410 can send at least one timing parameter table from the set of timing parameter tables to the UE via RRC signaling. In some cases, the first timing parameter table includes a first set of rows, and the second timing parameter table includes a second set of rows, each row in the first and second sets indicating a potential value for the timing parameter. In some cases, the size of the resource allocation bit field is based on the number of rows in the first set of rows. In some cases, the first timing parameter table is associated with an uplink transmission on the first BWP, and the set of timing parameter tables also includes a third timing parameter table associated with a downlink transmission on the first BWP. In some cases, the first BWP has a first tone interval, and the second BWP has a second tone interval. In some cases, the potential values ​​for timing parameters in the first timing parameter table are based on the first tone interval, and the potential values ​​for timing parameters in the second timing parameter table are based on the second tone interval. In some cases, the first BWP is associated with lower transmission power compared to the second BWP.

[0182] The handover manager 1415 can identify triggers for switching communication with the UE from a first BWP to a second BWP. The parameter controller 1420 can select values ​​for timing parameters based on triggers and a second timing parameter table. In some examples, the parameter controller 1420 can identify a subset of the second row set addressable via the resource allocation bit field. In some examples, the parameter controller 1420 can select values ​​for timing parameters based on a subset of the second row set. In some cases, the subset of the second row set includes the row with the lowest index in the second row set, and the row with the lowest index corresponds to a preferred value of the timing parameter used for switching to the second BWP. In some cases, the subset of the second row set includes a set of rows with the lowest index in a second plurality of rows, the set of rows with the lowest index corresponding to a set of timing parameter values, wherein the values ​​of the timing parameters are ordered from the maximum value of the timing parameter used for switching to the second BWP to the minimum value of the timing parameter used for switching to the second BWP.

[0183] In some cases, a subset of the second set includes at least one row corresponding to preferred values ​​of timing parameters used for communication in the second BWP. In some cases, preferred values ​​of timing parameters include a first value for wake-up communication, a second value for data communication, or a third value for micro-sleep communication.

[0184] Control manager 1425 can send a DCI transmission on the first BWP to activate the second BWP. The DCI transmission includes a resource allocation bit field indicating the value of a timing parameter, wherein the size of the resource allocation bit field is based on the configuration of the first BWP. In some examples, control manager 1425 can zero-padded the resource allocation bit field. In some examples, control manager 1425 can identify the format of the DCI transmission based on a trigger. In some cases, the DCI transmission includes a BWP identifier field to activate the second BWP.

[0185] Data Manager 1430 can communicate with the UE on the second BWP based on the values ​​of timing parameters. In some examples, Data Manager 1430 can send PDSCH transmissions. In some examples, Data Manager 1430 can receive PUSCH transmissions.

[0186] Figure 15A diagram of a system 1500 including device 1505 supporting timing parameter management for bandwidth portion switching, according to various aspects of this disclosure, is shown. Device 1505 may be an example of device 1205, device 1305, or base station 105 as described herein, or a component including device 1205, device 1305, or base station 105. Device 1505 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, including a communication manager 1510, a network communication manager 1515, a transceiver 1520, an antenna 1525, a memory 1530, a processor 1540, and an inter-station communication manager 1545. These components may communicate electronically via one or more buses (e.g., bus 1550).

[0187] Communication manager 1510 can identify a set of timing parameter tables for one or more potential values ​​of custom timing parameters associated with the timing of a DCI transmission to the UE and subsequent communication with the UE. The set of timing parameter tables includes at least a first timing parameter table associated with a first BWP and a second timing parameter table associated with a second BWP. Communication manager 1510 can identify triggers for switching communication with the UE from the first BWP to the second BWP. Communication manager 1510 can select values ​​for the timing parameters based on the triggers and the second timing parameter tables. Communication manager 1510 can send a DCI transmission on the first BWP to activate the second BWP. The DCI transmission includes a resource allocation bit field indicating the value of the timing parameter, wherein the size of the resource allocation bit field is based on the configuration of the first BWP. Communication manager 1510 can communicate with the UE on the second BWP according to the value of the timing parameter.

[0188] The network communication manager 1515 can manage communication with the core network (e.g., via one or more wired backhaul links). For example, the network communication manager 1515 can manage the transmission of data communication to client devices (such as one or more UEs 115).

[0189] Transceiver 1520 can communicate bidirectionally via one or more antennas, wired or wireless links as described above. For example, transceiver 1520 can represent a wireless transceiver and can communicate bidirectionally with another wireless transceiver. Transceiver 1520 may also include a modem for modulating packets and providing the modulated packets to the antenna for transmission, and demodulating packets received from the antenna. In some cases, the wireless device may include a single antenna 1525. However, in some cases, the device may have more than one antenna 1525, which may be able to transmit or receive multiple wireless transmissions simultaneously.

[0190] Memory 1530 may include RAM, ROM, or a combination thereof. Memory 1530 may store computer-readable code 1535, which includes instructions that, when executed by a processor (e.g., processor 1540), cause the device to perform the various functions described herein. In some cases, memory 1530 may contain a BIOS, which controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0191] Processor 1540 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, processor 1540 may be configured to use a memory controller to operate a memory array. In some cases, the memory controller may be integrated into processor 1540. Processor 1540 may be configured to execute computer-readable instructions stored in memory (e.g., memory 1530) to cause the device to perform various functions (e.g., functions or tasks supporting timing parameter management for bandwidth portion switching).

[0192] Inter-site communication manager 1545 can manage communication with other base stations 105, and may include a controller or scheduler for cooperating with other base stations 105 to control communication with UE 115. For example, inter-site communication manager 1545 can coordinate the scheduling of transmissions to UE 115 to implement various interference mitigation techniques such as beamforming or joint transmission. In some examples, inter-site communication manager 1545 may provide an X2 interface within LTE / LTE-A wireless communication network technology to provide communication between base stations 105.

[0193] Code 1535 may include instructions for implementing various aspects of this disclosure, including instructions for supporting wireless communication. Code 1535 may be stored in a non-transitory computer-readable medium, such as system memory or other types of memory. In some cases, code 1535 may not be directly executable by processor 1540, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein.

[0194] Figure 16 A flowchart illustrating a method 1600 for managing timing parameters supporting bandwidth partial handover according to various aspects of this disclosure is shown. Operation of method 1600 can be implemented by a UE 115 or its components as described herein. For example, operation of method 1600 can be implemented by, as referred to... Figures 8 to 11The communication manager described herein is used for execution. In some examples, the UE can execute a set of instructions to control the UE's functional units to perform the functions described below. Alternatively or supplementarily, the UE can use dedicated hardware to perform aspects of the functions described below.

[0195] At 1605, the UE can identify a set of timing parameter tables for each custom timing parameter with respect to one or more potential values ​​for timing parameters associated with the timing between the reception of DCI from the base station and subsequent communication with the base station based on the DCI. The set of timing parameter tables includes at least a first timing parameter table associated with a first BWP and a second timing parameter table associated with a second BWP. Operation of 1605 can be performed according to the method described herein. In some examples, aspects of the operation of 1605 can be determined by reference to... Figures 8 to 11 The table manager described is used to execute this.

[0196] At 1610, the UE can receive a DCI transmission on the first BWP for activating the second BWP. The DCI transmission includes a resource allocation bit field indexed to at least a subset of the second timing parameter table, wherein the size of the resource allocation bit field is based on the configuration of the first BWP. Operation 1610 can be performed according to the method described herein. In some examples, aspects of the operation of 1610 can be determined by referring to... Figures 8 to 11 The control manager described is used to execute this.

[0197] At point 1615, the UE can identify the value for the timing parameter based on the second timing parameter table and the size of the resource allocation bit field. The operation at point 1615 can be performed according to the method described herein. In some examples, aspects of the operation at point 1615 can be determined by referring to... Figures 8 to 11 The parameter manager described is used for execution.

[0198] At point 1620, the UE can communicate with the base station on the second BWP based on the values ​​of the timing parameters. The operation at point 1620 can be performed according to the method described herein. In some examples, aspects of the operation at point 1620 can be derived as described in reference... Figures 8 to 11 The described data manager is used to execute this.

[0199] Figure 17 A flowchart illustrating method 1700 for managing timing parameters supporting bandwidth partial handover according to various aspects of this disclosure is shown. Operation of method 1700 can be implemented by base station 105 or its components as described herein. For example, operation of method 1700 can be implemented by, as referred to... Figures 12 to 15The communication manager described herein is used for execution. In some examples, the base station may execute a set of instructions to control the functional units of the base station to perform the functions described below. Alternatively or supplementarily, the base station may use dedicated hardware to perform aspects of the functions described below.

[0200] At 1705, the base station can identify a set of timing parameter tables for each custom-defined potential value of timing parameters, said timing parameters being associated with the timing between transmission to the UE to the DCI and subsequent communication with the UE according to the DCI, the set of timing parameter tables including at least a first timing parameter table associated with a first BWP and a second timing parameter table associated with a second BWP. Operation of 1705 can be performed according to the method described herein. In some examples, aspects of the operation of 1705 can be determined by reference to... Figures 12 to 15 The table controller described is used to execute this.

[0201] At point 1710, the base station can select values ​​for the timing parameters based on the second timing parameter table. The operation at point 1710 can be performed according to the method described herein. In some examples, aspects of the operation at point 1710 can be determined by referring to... Figures 12 to 15 The parameters described are used by the controller to execute.

[0202] At point 1715, the base station can transmit a DCI transmission on the first BWP to activate the second BWP. The DCI transmission includes a resource allocation bit field indicating the value of timing parameters, wherein the size of the resource allocation bit field is based on the configuration of the first BWP. Operation at point 1715 can be performed according to the method described herein. In some examples, aspects of operation at point 1715 can be determined by referring to... Figures 12 to 15 The control manager described is used to execute this.

[0203] At 1720, the base station can communicate with the UE on the second BWP based on the values ​​of timing parameters. The operation at 1720 can be performed according to the method described herein. In some examples, aspects of the operation at 1720 can be determined by referring to... Figures 12 to 15 The described data manager is used to execute this.

[0204] It should be noted that the methods described above describe possible implementations, and that the operations and steps can be rearranged or otherwise modified, and that other implementations are possible. Furthermore, aspects from two or more methods can be combined.

[0205] The technologies described in this article can be used in various wireless communication systems, such as Code Division Multiple Access (CMDA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), and other systems. CDMA systems can implement radio technologies such as CDMA2000 and Universal Terrestrial Radio Access (UTRA). CDMA2000 encompasses the IS-2000, IS-95, and IS-856 standards. Versions of IS-2000 are often referred to as CDMA2000 1X, 1X, etc. IS-856 (TIA-856) is often referred to as CDMA2000 1xEV-DO, High-Speed ​​Packet Data (HRPD), etc. UTRA includes Wideband CDMA (WCDMA) and other variations of CDMA. TDMA systems can implement radio technologies such as the Global System for Mobile Communications (GSM).

[0206] OFDMA systems can implement radio technologies such as Ultra Mobile Broadband (UMB), Evolved UTRA (E-UTRA), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, and Flash-OFDM. UTRA and E-UTRA are part of the Universal Mobile Telecommunications System (UMTS). LTE, LTE-A, and LTE-APro are versions of UMTS using E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, LTE-APro, NR, and GSM are described in documents from an organization called the 3rd Generation Partnership Project (3GPP). CDMA2000 and UMB are described in documents from an organization called the 3rd Generation Partnership Project 2 (3GPP2). The technologies described herein can be used in the systems and radio technologies mentioned above, as well as other systems and radio technologies. While aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for illustrative purposes, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in most of the description, the techniques described herein are applicable to applications beyond LTE, LTE-A, LTE-A Pro, or NR.

[0207] Macro cells typically cover a relatively large geographic area (e.g., a radius of several kilometers) and allow unrestricted access by UEs with service subscriptions to a network provider. In contrast, small cells can be associated with a lower-power base station 105 and can operate in the same or different (e.g., licensed, unlicensed, etc.) frequency bands as macro cells. Depending on the examples, small cells can include pico cells, femto cells, and microcells. For example, a pico cell can cover a small geographic area and allow unrestricted access by UEs 115 with service subscriptions to a network provider. A femto cell can also cover a small geographic area (e.g., a residential area) and provide restricted access by UEs 115 associated with that femto cell (e.g., UE 115 in a Closed Subscriber Group (CSG), UE 115 for a user in a residential area, etc.). An eNB for a macro cell can be referred to as a macro eNB. An eNB for a small cell can be referred to as a small cell eNB, pico eNB, femto eNB, or home eNB. eNB can support one or more (e.g., two, three, four, etc.) cells, and can also support communication using one or more component carriers.

[0208] One or more wireless communication systems 100 described herein can support synchronous or asynchronous operation. For synchronous operation, base stations 105 can have similar frame timing, and transmissions from different base stations 105 can be approximately time-aligned. For asynchronous operation, base stations 105 can have different frame timing, and transmissions from different base stations 105 may not be time-aligned. The techniques described herein can be used for both synchronous and asynchronous operation.

[0209] The information and signals described herein can be represented using any of the various techniques and methods available. For example, the data, instructions, commands, information, signals, bits, symbols, and chips mentioned in the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.

[0210] The various illustrative blocks and modules described in connection with the disclosure herein can be implemented or executed using a general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration).

[0211] The functions described herein can be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions can be stored or transmitted as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described above can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination of these. Features used to implement the functions can also be physically located in various locations, including being distributed such that different parts of the functions are implemented in different physical locations.

[0212] Computer-readable media includes both non-transitory computer storage media and communication media, with communication media including any medium that facilitates the transfer of a computer program from one place to another. Non-transitory storage media can be any available medium accessible by a general-purpose computer or a special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media can include random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory, compressed optical disc (CD) ROM or other optical disc storage, disk storage or other magnetic storage devices, or any other non-transitory medium capable of carrying or storing desired units of program code in the form of instructions or data structures, and accessible by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. Furthermore, any connection is appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of media. As used herein, disks and optical discs include CDs, laser discs, optical discs, digital multifunction discs (DVDs), floppy disks, and Blu-ray discs. Disks typically copy data magnetically, while optical discs use lasers to copy data optically. The combinations described above also fall within the scope of computer-readable media.

[0213] As used herein (including in the claims), "or" as used in a list of items (e.g., a list of items ending with a phrase such as "at least one of..." or "one or more of...") indicates an inclusive list, such that a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (e.g., A and B and C). Furthermore, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, an exemplary step described as "based on condition A" may be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least partially based on".

[0214] In the accompanying drawings, similar components or features may have the same reference numerals. Furthermore, various components of the same type can be distinguished by a dash followed by a second reference numeral, used to differentiate between similar components. If only the first reference numeral is used in the specification, the description applies to any one of the similar components having the same first reference numeral, without regard to the second reference numeral or other subsequent reference numerals.

[0215] This document describes exemplary configurations with reference to the accompanying drawings, but does not represent all examples that can be implemented or that are within the scope of the claims. The term "exemplary" as used herein means "serving as an example, instance, or illustration," not "preferred" or "advantageous over other examples." The detailed description includes specific details for the purpose of providing an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0216] The description herein is provided to enable those skilled in the art to implement or use the present disclosure. Various modifications to the present disclosure will be apparent to those skilled in the art, and the general principles defined herein can be applied to other variations without departing from the scope of the disclosure. Therefore, the present disclosure is not limited to the examples and designs described herein, but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.

Claims

1. A user equipment (UE) for wireless communication, comprising: One or more processors; as well as One or more memories coupled to the one or more processors and storing processor-executable code, which, when executed by the one or more processors, is configured to cause the UE to perform the following operations: Identify multiple sets of timing parameters, each set defining one or more potential values ​​for timing parameters associated with the timing of the reception of downlink information (DCI) from a network device and subsequent communication with the network device based on the DCI, the multiple sets of timing parameters including at least a first set of timing parameters associated with a first bandwidth portion (BWP) and a second set of timing parameters associated with a second BWP; On the first BWP, a DCI transmission for activating the second BWP is received, the DCI transmission including a resource allocation bit field indexed at least a subset of the second timing parameter set, wherein the size of the resource allocation bit field is at least partially based on the configuration of the first BWP. The value for the timing parameter is identified at least in part based on the second set of timing parameters and the size of the resource allocation bit field; as well as Communicating with the network device on the second BWP based on the values ​​of the timing parameters, wherein, when the first set of timing parameters includes more timing parameters than the second set of timing parameters, the processor-executable code is further configured to cause the UE to perform the following operations: Identify a subset of bits in the resource allocation bit field, wherein the subset of bits indexes the time series parameters in the second time series parameter set; as well as The value for the timing parameter is determined based on the indexed timing parameters in the second set of timing parameters.

2. The UE according to claim 1, wherein, Identifying the subset of bits in the resource allocation bit field includes using the least significant bit of the resource allocation bit field.

3. The UE according to claim 1, wherein, The first timing parameter set is associated with uplink transmissions on the first BWP, and the plurality of timing parameter sets also include a third timing parameter set associated with downlink transmissions on the first BWP.

4. The UE according to claim 1, wherein, The first BWP has a first tone interval, and the second BWP has a second tone interval, wherein a first potential value for the timing parameter in the first set of timing parameters is at least partially based on the first tone interval, and a second potential value for the timing parameter in the second set of timing parameters is at least partially based on the second tone interval.

5. The UE according to claim 1, wherein, One or more bits in the resource allocation bit field are zero-padded.

6. A user equipment (UE) for wireless communication, comprising: One or more processors; as well as One or more memories coupled to the one or more processors and storing processor-executable code, which, when executed by the one or more processors, is configured to cause the UE to perform the following operations: Identify multiple sets of timing parameters, each set defining one or more potential values ​​for timing parameters associated with the timing of the reception of downlink information (DCI) from a network device and subsequent communication with the network device based on the DCI, the multiple sets of timing parameters including at least a first set of timing parameters associated with a first bandwidth portion (BWP) and a second set of timing parameters associated with a second BWP; On the first BWP, a DCI transmission for activating the second BWP is received, the DCI transmission including a resource allocation bit field indexed at least a subset of the second timing parameter set, wherein the size of the resource allocation bit field is at least partially based on the configuration of the first BWP. The value for the timing parameter is identified at least in part based on the second set of timing parameters and the size of the resource allocation bit field; as well as Communicating with the network device on the second BWP based on the values ​​of the timing parameters, wherein when the first set of timing parameters includes fewer timing parameters compared to the second set of timing parameters, the processor-executable code is further configured to cause the UE to perform the following operations: Identify a subset of timing parameters in the second timing parameter set that are addressable via the resource allocation bit field; Identify the timing parameters indexed by the resource allocation bit field within the subset of timing parameters in the second timing parameter set; and The value for the time series parameter is determined based on the indexed time series parameter, wherein the value for the time series parameter is a potential value corresponding to the indexed time series parameter.

7. The UE according to claim 6, wherein, The subset in the second timing parameter set includes the timing parameter with the lowest index in the second timing parameter set, the timing parameter with the lowest index corresponding to the value of the timing parameter used to switch to the second BWP.

8. The UE according to claim 6, wherein, The subset in the second set of timing parameters includes the maximum value among the one or more potential values ​​for the timing parameters from the second set of timing parameters.

9. The UE according to claim 6, wherein, The subset of the second timing parameter set includes at least one timing parameter corresponding to the value of the timing parameter used for communication in the second BWP.

10. The UE according to claim 9, wherein, The values ​​of the timing parameters include a first value for wake-up communication, a second value for data communication, or a third value for micro-sleep communication.

11. The UE according to claim 6, wherein, Identifying the subset of timing parameters in the second timing parameter set that are addressable via the resource allocation bit field includes: using the lowest-indexed timing parameter in the second timing parameter set, starting from the lowest-indexed timing parameter and proceeding to the last addressable timing parameter in the second timing parameter set.

12. The UE according to claim 6, wherein, Identifying the subset of timing parameters in the second timing parameter set that are addressable via the resource allocation bit field includes: indexing the timing parameters in the second timing parameter set using the least significant bit in the resource allocation bit field.

13. The UE according to claim 6, wherein, The first timing parameter set is associated with uplink transmissions on the first BWP, and the plurality of timing parameter sets also include a third timing parameter set associated with downlink transmissions on the first BWP.

14. The UE according to claim 6, wherein, The first BWP has a first tone interval, and the second BWP has a second tone interval, wherein a first potential value for the timing parameter in the first set of timing parameters is at least partially based on the first tone interval, and a second potential value for the timing parameter in the second set of timing parameters is at least partially based on the second tone interval.

15. A user equipment (UE), comprising: One or more processors; as well as One or more memories coupled to the one or more processors and storing processor-executable code, which, when executed by the one or more processors, is configured to cause the UE to perform the following operations: On a first bandwidth portion (BWP), downlink control information (DCI) transmission for activating a second BWP is received from a network device, wherein the DCI transmission includes a resource allocation bit field indicating values ​​for timing parameters from a plurality of timing parameter sets, the plurality of timing parameter sets defining one or more potential values ​​for the timing parameters, wherein the size of the resource allocation bit field is associated with the configuration of the first BWP, and wherein the plurality of timing parameter sets includes a first timing parameter set associated with the first BWP and a second timing parameter set associated with the second BWP; and Communicating with the network device on the second BWP according to the value of the timing parameter; The first timing parameter set includes more timing parameters than the second timing parameter set. The bit subset of the resource allocation bit field indexes the first timing parameter of the second timing parameter set. The resource allocation bit field indicates the timing parameter based on the indexed first timing parameter in the second timing parameter set.

16. The UE according to claim 15, wherein, The first timing parameter set is associated with uplink transmissions on the first BWP, and the plurality of timing parameter sets also include a third timing parameter set associated with downlink transmissions on the first BWP.

17. A method for wireless communication, comprising: Identify multiple sets of timing parameters, each set defining one or more potential values ​​for timing parameters associated with the timing of the reception of downlink information (DCI) from a network device and subsequent communication with the network device based on the DCI, the multiple sets of timing parameters including at least a first set of timing parameters associated with a first bandwidth portion (BWP) and a second set of timing parameters associated with a second BWP; On the first BWP, a DCI transmission for activating the second BWP is received, the DCI transmission including a resource allocation bit field indexed at least a subset of the second timing parameter set, wherein the size of the resource allocation bit field is at least partially based on the configuration of the first BWP. The value for the timing parameter is identified at least in part based on the second set of timing parameters and the size of the resource allocation bit field; as well as Communicating with the network device on the second BWP based on the value of the timing parameter, wherein, when the first timing parameter set includes more timing parameters than the second timing parameter set, identifying the value of the timing parameter includes: Identify a subset of bits in the resource allocation bit field, wherein the subset of bits indexes the timing parameters in the second timing parameter set; and The value for the timing parameter is determined based on the indexed timing parameters in the second set of timing parameters.

18. The method according to claim 17, wherein, Identifying the subset of bits in the resource allocation bit field includes using the least significant bit of the resource allocation bit field.

19. The method of claim 17, wherein, The first timing parameter set is associated with uplink transmissions on the first BWP, and the plurality of timing parameter sets also include a third timing parameter set associated with downlink transmissions on the first BWP.

20. A method for wireless communication, comprising: Identify multiple sets of timing parameters, each set defining one or more potential values ​​for timing parameters associated with the timing of the reception of downlink information (DCI) from a network device and subsequent communication with the network device based on the DCI, the multiple sets of timing parameters including at least a first set of timing parameters associated with a first bandwidth portion (BWP) and a second set of timing parameters associated with a second BWP; On the first BWP, a DCI transmission for activating the second BWP is received, the DCI transmission including a resource allocation bit field indexed at least a subset of the second timing parameter set, wherein the size of the resource allocation bit field is at least partially based on the configuration of the first BWP. The value for the timing parameter is identified at least in part based on the second set of timing parameters and the size of the resource allocation bit field; as well as Communicating with the network device on the second BWP based on the value of the timing parameter, wherein identifying the value of the timing parameter includes: when the first timing parameter set includes fewer timing parameters compared to the second timing parameter set. Identify a subset of timing parameters in the second timing parameter set that are addressable via the resource allocation bit field; Identify the timing parameters indexed by the resource allocation bit field within the subset of timing parameters in the second timing parameter set; and The value for the time series parameter is determined based on the indexed time series parameter, wherein the value for the time series parameter is a potential value corresponding to the indexed time series parameter.

21. The method according to claim 20, wherein, in, The subset in the second timing parameter set includes the timing parameter with the lowest index in the second timing parameter set, the timing parameter with the lowest index corresponding to the value of the timing parameter used to switch to the second BWP.

22. The method according to claim 20, wherein, The subset in the second set of timing parameters includes the maximum value among the one or more potential values ​​for the timing parameters from the second set of timing parameters.

23. A method for wireless communication, comprising: On a first bandwidth portion (BWP), downlink control information (DCI) transmission for activating a second BWP is received from a network device, wherein the DCI transmission includes a resource allocation bit field indicating values ​​for timing parameters from a plurality of timing parameter sets, the plurality of timing parameter sets defining one or more potential values ​​for the timing parameters, wherein the size of the resource allocation bit field is associated with the configuration of the first BWP, and wherein the plurality of timing parameter sets includes a first timing parameter set associated with the first BWP and a second timing parameter set associated with the second BWP; and Communicating with the network device on the second BWP according to the value of the timing parameter; The first timing parameter set includes fewer timing parameters compared to the second timing parameter set. A subset of the timing parameters in the second timing parameter set is addressable through the resource allocation bit field. A first timing parameter in the subset of the second timing parameter set is indexed through the resource allocation bit field. The resource allocation bit field indicates the timing parameter based on the indexed first timing parameter.

Images