TW201931913A - Feedback timing and uplink control information resource management for carrier aggregation activation - Google Patents

Abstract

Aspects of the present disclose provide various methods and apparatuses for communicating, controlling, and configuring component carrier and bandwidth part (BWP). A scheduling entity receives a capability report from a user equipment (UE). The capability report indicates a capability of the UE to utilize at least one of carrier aggregation (CA) or one or more bandwidth parts. The scheduling entity transmits a command to the UE to reconfigure at least one of a CA configuration or a bandwidth part (BWP) configuration. The scheduling entity determines an anticipated response timing of an acknowledgment (ACK) of the command based on the capability report received from the UE. The scheduling entity receives the ACK according to the anticipated response timing.

Description

Feedback timing and uplink control information resource management for carrier aggregation start

This patent application claims Non-Provisional Patent Application No. 16 / 124,116 filed with the US Patent and Trademark Office on September 6, 2018 and Provisional Patent Application No. 62 / filed with the US Patent Office on September 11, 2017 557,016 priority and rights.

The large technical system discussed below is related to wireless communication systems and to carrier aggregation (CA) and bandwidth part (BWP) configuration and control in wireless communication.

Carrier Aggregation (CA) is a technology used in wireless communications to increase peak user data rates, improve connection reliability, and / or increase the total capacity of the network available to users. The CA may combine two or more component carriers that may be continuous or discontinuous in frequency. In next-generation networks, one or more bandwidth sections can be defined in a carrier band or component carrier (CC). The bandwidth part (BWP) is a continuous set of physical resource blocks in a carrier frequency band. The user equipment may be configured to operate in a specific BWP having a bandwidth narrower than the full bandwidth of the corresponding component carrier. As the demand for mobile broadband access continues to grow, research and development continue to advance CA and BWP-related wireless communication technologies, not only to meet the growing demand for mobile broadband access, but also to promote and enhance the use of mobile communications Experience.

A brief summary of one or more aspects of the present case is presented below in order to provide a basic understanding of this aspect. This summary is not an extensive overview of all the expected features of the content of the case, and is neither intended to identify key or important elements of all aspects of the content of the case, nor to illustrate the scope of any or all aspects of the content of the case. Its sole purpose is to present some concepts of one or more aspects of the content in a simplified form as a prelude to the more detailed description that is presented later.

One aspect of the content of this case provides a method of wireless communication capable of operating at a scheduling entity. The scheduling entity receives a capability report from a user equipment (UE). The capability report indicates the UE's capability to utilize at least one of carrier aggregation (CA) or one or more bandwidth portions. The scheduling entity sends a command to the UE to reconfigure at least one of a CA configuration or a bandwidth part (BWP) configuration. The scheduling entity determines the expected response timing of the acknowledgement (ACK) of the command based on the capability report received from the UE. The scheduling entity receives the ACK according to the expected response timing.

Another aspect of the content of the present case provides a wireless communication method capable of operating at a user equipment (UE). The UE sends a capability report to the scheduling entity. The capability report indicates the UE's capability to utilize at least one of carrier aggregation (CA) or one or more bandwidth portions. The UE receives a command from a scheduling entity to reconfigure at least one of a carrier aggregation (CA) configuration or a bandwidth part (BWP) configuration. The UE sends a command acknowledgement (ACK) using the timing based on the capability report.

Another aspect of the present disclosure provides a device for wireless communication. The device includes: a communication interface configured to communicate with a user equipment (UE); a memory; and a processor operatively coupled to the communication interface and the memory. The processor and memory are configured to receive a capability report from the UE. The capability report indicates the UE's capability to utilize at least one of carrier aggregation (CA) or one or more bandwidth portions. The processor and memory are also configured to send a command to the UE to reconfigure at least one of a CA configuration or a bandwidth part (BWP) configuration. The processor and memory are also configured to determine the expected response timing of the acknowledgement (ACK) of the command based on the capability report received from the UE. The processor and memory are also configured to receive ACKs based on the expected response timing.

Another aspect of the content of the present invention provides a user equipment (UE) for wireless communication. The UE includes: a communication interface configured to communicate with a scheduling entity; a memory; and a processor operatively coupled to the communication interface and the memory. The processor and memory are configured to send a capability report to a scheduling entity. The capability report indicates the UE's capability to utilize at least one of carrier aggregation (CA) or one or more bandwidth portions. The processor and memory are also configured to receive a command from a scheduling entity to reconfigure at least one of a carrier aggregation (CA) configuration or a bandwidth part (BWP) configuration. The processor and memory are configured to send a command acknowledgement (ACK) using a timing based on the capability report.

These and other aspects of the invention will be more fully understood when browsing the detailed description below. Other aspects, features, and embodiments of the present invention will become apparent to those of ordinary skill in the art when the following description of specific exemplary embodiments of the invention is viewed in conjunction with the accompanying drawings. Although features of the invention may be discussed with respect to certain embodiments and drawings below, all embodiments of the invention may include one or more of the advantageous features discussed herein. In other words, although one or more embodiments may be discussed as having certain advantageous features, one or more of such features may also be used in accordance with various embodiments of the invention discussed herein. In a similar manner, although exemplary embodiments may be discussed below as device, system, or method embodiments, it should be understood that such exemplary embodiments may be implemented in various devices, systems, and methods.

The detailed description set forth below in connection with the accompanying drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein can be practiced. The detailed description includes specific details for providing a thorough understanding of various concepts. However, it will be apparent to those skilled in the art that the concepts may be practiced without these specific details. In some instances, well-known structures and components are illustrated in block diagram form in order to avoid obscuring this concept.

Although aspects and embodiments have been described in this case by illustrating some examples, those skilled in the art will understand that additional implementations and use cases may occur in many different arrangements and scenarios. The innovations described in this article can be implemented across many different platform types, devices, systems, shapes, sizes, packaging arrangements. For example, embodiments and / or uses may be integrated with chip embodiments and other non-module based devices (eg, end-user devices, vehicles, communications devices, computing devices, industrial devices, retail / purchase devices, medical devices , AI-enabled devices, etc.). Although some examples may or may not be specific to use cases or applications, the applicability of the various types of innovations described may arise. Implementations can range from wafer-level or modular components to non-modular, non-wafer-level implementations, and can also be aggregated, decentralized, or OEM devices incorporating one or more of the described innovations Or system. In some practical settings, a device incorporating the described aspects and features may also necessarily include additional components and features for implementing and practicing the claimed and described embodiments. For example, the transmission and reception of wireless signals necessarily includes multiple components for analog and digital purposes (for example, including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / demands, etc. And other hardware components). The innovations described herein are intended to be implemented in a variety of devices, wafer-level components, systems, decentralized arrangements, end-user devices, and the like, of various sizes, shapes, and configurations.

Carrier Aggregation (CA) is a technique widely used in wireless communications to increase bandwidth, reliability, and / or throughput. In next-generation networks, such as 5G New Radio (NR), CAs can be enhanced to provide more flexibility to handle user equipment (UE) with different capabilities. In 5G NR, the bandwidth part (BWP) consists of a group of consecutive physical resource blocks (PRBs), and each BWP can have its own numerology (eg, cyclic prefix length and subcarriers) interval). One or more bandwidth part configurations for each component carrier (CC) may be configured for the UE. If BWP is used, the UE performs reception and / or transmission within the carrier activity or within the configured BWP. In some examples, the total bandwidth of the CC may be divided into multiple BWPs (eg, one to four BWPs per CC). CC's BWP can have different bandwidths, such as narrow-band BWP and wide-band BWP. In some examples, BWPs can overlap in frequency. Any change in the configuration of the component carrier and BWP (eg, activation / deactivation) changes the amount of data transmission available to the UE. Aspects of the content of this case provide various methods and devices for transmitting, controlling, and configuring CCs and BWPs.

The concepts provided throughout this case can be implemented in various telecommunication systems, network architectures and communication standards. Referring now to FIG. 1, by way of illustration and not limitation, reference is made to the wireless communication system 100 to illustrate various aspects of the present disclosure. The wireless communication system 100 includes three interactive domains: a core network 102, a radio access network (RAN) 104, and a user equipment (UE) 106. With the wireless communication system 100, the UE 106 can perform data communication with an external data network 110 (such as, but not limited to, the Internet).

The RAN 104 may implement any suitable one or more wireless communication technologies to provide radio access to the UE 106. As an example, the RAN 104 may operate in accordance with the 3rd Generation Partnership Project (3GPP) New Radio (NR) specification (which is often referred to as 5G for short). As another example, the RAN 104 may operate under a hybrid of 5G NR and the Evolved Universal Terrestrial Radio Access Network (eUTRAN) standard, which is commonly referred to as LTE. 3GPP refers to this hybrid RAN as the next-generation RAN or NG-RAN. Of course, many other examples can be used within the scope of this case.

As shown, the RAN 104 includes a plurality of base stations 108. In summary, a base station is a network element in a radio access network that is responsible for radio transmission and reception to or from a UE in one or more cells. In different technologies, standards or contexts, those skilled in the art may refer to base stations differently as base station transceivers (BTS), radio base stations, radio transceivers, transceiver functions, basic service set (BSS), extensions Service Set (ESS), Access Point (AP), Node B (NB), Evolved Node B (eNB), Next Generation Node B (gNB), or some other suitable term.

Further illustrated is a radio access network 104 that supports wireless communication for multiple mobile devices. A mobile device can be referred to as a user equipment (UE) in the 3GPP standard, but those skilled in the art can also refer to this mobile device as a mobile station (MS), user station, mobile unit, user unit, wireless unit, remote Unit, mobile device, wireless device, wireless communication device, remote device, mobile user station, access terminal (AT), mobile terminal, wireless terminal, remote terminal, handheld device, terminal, user agent, mobile service customer Client, client, or some other suitable term. A UE may be a device that provides users with access to network services.

For the purposes of this document, "mobile" devices are not necessarily mobile capable and may be stationary. The term mobile device or mobile device broadly represents a wide variety of devices and technologies. The UE may include multiple hardware structural components whose size, shape, and arrangement facilitate communication; such components may include antennas, antenna arrays, RF chains, amplifiers, one or more processors, etc. that are electrically coupled to each other. For example, some non-limiting examples of mobile devices include: mobile devices, cellular (cell) phones, smart phones, communications protocol initiation (SIP) phones, laptops, personal computers (PCs), laptops, small computers Laptops, smart computers, tablets, personal digital assistants (PDAs), and various embedded systems, such as the "Internet of Things" (IoT). The mobile device may additionally be a car or other transportation vehicle, a remote sensor or actuator, a robot or robotic device, a satellite radio device, a global positioning system (GPS) device, an object tracking device, a drone, a multi-axis aircraft, a quad Rotorcraft, remote control equipment, consumer and / or wearable devices such as glasses, wearable cameras, virtual reality devices, smart watches, health or fitness trackers, digital audio players (e.g. MP3 players), cameras, Game consoles, etc. The mobile device may additionally be a digital home or smart home device, such as home audio, video and / or multimedia devices, appliances, vending machines, smart lighting, home security systems, smart instruments, etc. Mobile devices can also be smart energy devices, security devices, solar panels or solar cell arrays, municipal infrastructure equipment (e.g., smart grids) that control power, lighting, water, etc .; industrial automation and enterprise equipment; logistics controllers; Equipment; military defense equipment, vehicles, aircraft, ships, and weapons. In addition, mobile devices can provide connected medical or telemedicine support, such as remote healthcare. Remote medical equipment can include remote health monitoring equipment and remote health management equipment, which can give its communications priority processing or preferential access over other types of information, such as preferential access in the transmission of key service data, And / or relevant QoS aspects used for transmission of critical service information.

Wireless communication between the RAN 104 and the UE 106 can be described as utilizing an air interface. Transmissions over a air interface from a base station (eg, base station 108) to one or more UEs (eg, UE 106) may be referred to as downlink (DL) transmissions. According to some aspects of the content of this case, the term downlink may refer to point-to-multipoint transmissions originating from a scheduling entity (described further below, for example, base station 108). Another way to describe this scheme may be to use the term broadcast channel multiplexing. A transmission from a UE (eg, UE 106) to a base station (eg, base station 108) may be referred to as an uplink (UL) transmission. According to other aspects of the content of this case, the term uplink may refer to a point-to-point transmission originating from a scheduled entity (further described below; for example, UE 106).

In some examples, access to the air interface may be scheduled, where the scheduling entity (eg, base station 108) allocates resources for communication between some or all of its equipment and equipment within its service area or cell. In this case, as discussed further below, the scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more scheduled entities. That is, for scheduled communications, the UE 106 (which may be the scheduled entity) may use the resources allocated by the scheduling entity 108.

The base station 108 is not the only entity that can be used as a scheduling entity. That is, in some examples, the UE may be used as a scheduling entity to schedule resources for one or more scheduled entities (eg, one or more other UEs).

As shown in FIG. 1, the scheduling entity 108 may broadcast the downlink traffic 112 to one or more scheduled entities 106. In summary, the scheduling entity 108 is a node or device that is responsible for scheduling traffic in a wireless communication network. The traffic includes downlink traffic 112, and in some instances, includes scheduling from one or more scheduled traffic. The uplink traffic 116 from the entity 106 to the scheduling entity 108. In another aspect, the scheduled entity 106 is a node or device that receives downlink control information 114 from another entity (eg, the scheduling entity 108) in the wireless communication network. The downlink control information 114 includes but does not Limited to scheduling information (for example, permission), synchronization or timing information, or other control information. The scheduling entity 108 may use carrier aggregation and bandwidth portions to communicate with the scheduled entity 106.

Generally, the base station 108 may include a backhaul interface for communicating with the backhaul part 120 of the wireless communication system. The backhaul section 120 may provide a link between the base station 108 and the core network 102. Further, in some examples, a backhaul network may provide interconnections between respective base stations 108. Various types of backhaul interfaces can be used, such as direct physical connections, virtual networks, etc. using any suitable transmission network.

The core network 102 may be part of the wireless communication system 100 and may be independent of the radio access technology used in the RAN 104. In some examples, the core network 102 may be configured according to a 5G standard (eg, 5GC). In other examples, the core network 102 may be configured according to the 4G Evolved Packet Core (EPC) or any other suitable standard or configuration.

Referring now to FIG. 2, by way of example and not limitation, a schematic diagram of a RAN 200 is provided. In some examples, the RAN 200 may be the same as the RAN 104 described above and illustrated in FIG. 1. The geographic area covered by the RAN 200 can be divided into a honeycomb area (cell) that can be uniquely identified by a user equipment (UE) based on an identity broadcast from one access point or base station. FIG. 2 illustrates macro cells 202, 204, and 206 and small cells 208, each of which may include one or more sectors (not shown). A sector is a subregion of a cell. All sectors within a cell are served by the same base station. A radio link within a sector can be identified by a single logical identification belonging to the sector. In a cell divided into sectors, multiple sectors within the cell may be formed by antenna groups, and each antenna is responsible for communicating with UEs in a part of the cell.

In FIG. 2, two base stations 210 and 212 are illustrated in cells 202 and 204; and a third base station 214 illustrating a remote radio head (RRH) 216 in the control cell 206. That is, the base station may have an integrated antenna or may be connected to the antenna or RRH by a feeding cable. In the example shown, the cells 202, 204, and 126 may be referred to as macro cells because the base stations 210, 212, and 214 support cells having large sizes. In addition, base stations are illustrated in small cells 208 (eg, micro cells, pico cells, femto cells, home base stations, home node B, home evolutionary node B, etc.) that can overlap with one or more macro cells. 218. In this example, the cells 208 may be referred to as small cells because the base station 218 supports cells having a relatively small size. Cell size adjustments can be made based on system design and component constraints.

It is understood that the radio access network 200 may include any number of wireless base stations and cells. In addition, relay nodes can be deployed to expand the size or coverage area of a given cell. The base stations 210, 212, 214, 218 provide wireless access points to the core network for any number of mobile devices. In some examples, the base stations 210, 212, 214, and / or 218 may be the same as the base station / scheduling entity 108 described above and illustrated in FIG.

Figure 2 also includes a quadrotor or drone 220, which may be configured to function as a base station. That is, in some examples, the cells may not necessarily be stationary, and the geographic area of the cells may move according to the location of a mobile base station such as a quadrotor 220.

Within the RAN 200, the cells may include UEs that can communicate with one or more sectors of each cell. In addition, each base station 210, 212, 214, 218, and 220 may be configured to provide all UEs in various cells with access points to the core network 102 (see FIG. 1). For example, UE 222 and 224 can communicate with base station 210; UE 226 and 228 can communicate with base station 212; UE 230 and 232 can communicate with base station 214 by means of RRH 216; UE 234 can communicate with base station Station 218 is in communication; and UE 236 may be in communication with mobile base station 220. In some examples, the UE 222, 224, 226, 228, 230, 232, 234, 236, 238, 240, and / or 242 may be the same as the UE / scheduled entity 106 described above and illustrated in FIG. 1 . The UE 230 may communicate with the base station 216 using one or more component carriers (CCs), and each CC may provide one or more bandwidth sections (BWP).

In some examples, a mobile network node (eg, quadrotor 220) may be configured to function as a UE. For example, the quadrotor 220 may operate within the cell 202 by communicating with the base station 210.

In a further aspect of the RAN 200, side link signals can be used between UEs without having to rely on scheduling or control information from the base station. For example, two or more UEs (eg, UEs 226 and 228) can communicate with each other using peer-to-peer (P2P) or side-link signals 227 without communicating via a base station (eg, base station 212). Relay. In a further example, UE 238 is illustrated in communication with UEs 240 and 242. Here, the UE 238 may be used as a scheduling entity or a primary-side link device, and UEs 240 and 242 may be used as a scheduled entity or a non-primary-side link device (for example, a secondary-side link device). In yet another example, the UE can be used as a scheduling entity in a device-to-device (D2D), peer-to-peer (P2P), or vehicle-to-vehicle (V2V) network and / or mesh network. In the mesh network example, in addition to communicating with the scheduling entity 238, the UEs 240 and 242 may optionally communicate directly with each other. Therefore, in a wireless communication system having scheduled access to time-frequency resources and having a honeycomb configuration, a P2P configuration, or a mesh configuration, the scheduling entity and one or more scheduled entities can utilize the scheduled Communication.

In the radio access network 200, the ability of a UE to communicate independently of its location when moving is referred to as mobility. The various physical channels between the UE and the radio access network are usually established, maintained and released under the control of access and mobility management functions (AMF, not shown, part of the core network 102 in FIG. 1), The AMF may include a security context management function (SCMF) that manages security contexts for both control plane and user plane functions, and a security anchor function (SEAF) that performs authentication.

In various aspects of the content of this case, the radio access network 200 may use DL-based mobility or UL-based mobility to enable mobility and handover (that is, the connection of the UE is transferred from one radio channel to another One wireless channel). In a network configured for DL-based mobility, during a call with a scheduling entity, or at any other time, the UE can monitor various parameters of signals from its serving cells and various parameters of neighboring cells . Depending on the quality of these parameters, the UE can maintain communication with one or more neighboring cells among neighboring cells. During this time, if the UE moves from one cell to another, or if the signal quality from a neighboring cell exceeds the signal quality from a serving cell for a given amount of time, the UE can proceed from the serving cell to the neighbor ( (Target) Cell handoff or handover. For example, the UE 224 (shown as a vehicle, but any suitable form of UE may be used) may move from a geographic area corresponding to its serving cell 202 to a geographic area corresponding to an adjacent cell 206. When the signal strength or quality from the neighboring cell 206 exceeds the signal strength or quality of its serving cell 202 for a given amount of time, the UE 224 may send a report message to its serving base station 210 indicating the condition. In response, the UE 224 may receive a handover command, and the UE may experience a handover to the cell 206.

In a network configured for UL-based mobility, the network may use UL reference signals from each UE to select serving cells for each UE. In some examples, base stations 210, 212, and 214/216 may broadcast unified synchronization signals (eg, unified primary synchronization signal (PSS), unified secondary synchronization signal (SSS), and unified physical broadcast channel (PBCH)). The UEs 222, 224, 226, 228, 230, and 232 can receive unified synchronization signals, export carrier frequency and time slot timing from the synchronization signals, and send uplink pilot frequencies or reference signals in response to the output timing. An uplink pilot frequency signal sent by a UE (eg, UE 224) may be received by two or more cells (eg, base stations 210 and 214/216) simultaneously within the radio access network 200. Each cell can measure the strength of the pilot signal, and the radio access network (eg, one or more of the base stations 210 and 214/216 and / or the central node within the core network) can Determine serving cells for UE 224. As the UE 224 moves through the radio access network 200, the network may continue to monitor the uplink pilot frequency signals sent by the UE 224. When the signal strength or quality of the pilot frequency signal measured by the neighboring cell exceeds the signal strength or quality measured by the serving cell, the network 200 may remove the UE 224 from the service without notifying or notifying the UE 224 Cells are delivered to neighboring cells.

Although the synchronization signals sent by the base stations 210, 212, and 214/216 may be uniform, the synchronization signals may not identify specific cells, but may identify regions of multiple cells operating at the same frequency and / or having the same timing . The use of zones in 5G networks or other next-generation communication networks enables an uplink-based mobility framework and improves the efficiency of both the UE and the network because of the mobility information that needs to be exchanged between the UE and the network The number can be reduced.

In various implementations, the air interface in the radio access network 200 may use licensed spectrum, unlicensed spectrum, or shared spectrum. Authorized spectrum usually provides exclusive use of a portion of the spectrum by a mobile network service provider purchasing a license from a government regulator. Unlicensed spectrum provides shared use of a portion of the spectrum without the need for a government-approved license. Although access to unlicensed spectrum is often still required to comply with certain technical rules, access is usually available to any service provider or device. The shared spectrum may fall between licensed and unlicensed spectrum, where technical rules or restrictions may be required to access the spectrum, but the spectrum may still be shared by multiple service providers and / or multiple RATs. For example, a holder of a license for a portion of the authorized spectrum may provide authorized shared access (LSA) to share the spectrum with other parties, for example, to obtain access using conditions determined by a suitable licensee.

The air interface in the radio access network 200 may use one or more duplex algorithms. Duplex is a point-to-point communication link in which both endpoints can communicate with each other in both directions. Full-duplex means that two endpoints can communicate with each other at the same time. Half-duplex means that only one endpoint can send information to another endpoint at a time. In wireless links, full-duplex channels usually rely on the physical separation of the transmitter and receiver and appropriate interference cancellation techniques. By using frequency division duplex (FDD) or time division duplex (TDD), full-duplex simulation is often performed on the wireless link. In FDD, transmissions in different directions work at different carrier frequencies. In TDD, time-division multiplexing is used to separate transmissions in different directions on a given channel from each other. That is, at some times, the channel is dedicated to transmission in one direction, and at other times, the channel is dedicated to transmission in the other direction, where the direction can be changed very quickly, for example, several times per time slot.

In order to obtain a lower block error rate (BLER) for transmissions via the radio access network 200 while still achieving very high data rates, channel coding can be used. That is, wireless communication can generally use appropriate error correction block codes. In a typical block code, an information message or sequence is divided into code blocks (CB), and an encoder (eg, CODEC) at the sending device then mathematically adds redundancy to the information message. The use of this redundancy in the coded information message can improve the reliability of the message and enable the correction of any bit errors that may occur due to noise.

In the early 5G NR specifications, quasi-cyclic low-density parity check (LDPC) with two different basemaps was used to encode user data: one basemap was used for large code blocks and / or high code rates, and the other One basemap is used for the other. Based on the nested sequence, the polar code is used to encode the control information and the physical broadcast channel (PBCH). For such channels, punch matching, shortening, and repetition are used for rate matching.

However, those of ordinary skill in the art will understand that any suitable channel code may be used to implement the aspect of the content of this case. Various implementations of the scheduling entity 108 and the scheduled entity 106 may include suitable hardware and capabilities (eg, encoders, decoders, and / or CODECs) to utilize one or more of the channel codes to For wireless communication.

The air interface in the radio access network 200 may utilize one or more multiplexing and multiplexing access algorithms to enable simultaneous communication of various devices. For example, the 5G NR specification utilizes Orthogonal Frequency Division Multiplexing (OFDM) with a cyclic prefix (CP) to provide multiplexed access for UL transmissions from UEs 222 and 224 to base station 210, and provides Multiplexing of DL transmissions to one or more UEs 222 and 224. In addition, for UL transmission, the 5G NR specification provides support for Discrete Fourier Transform Extended OFDM (DFT-s-OFDM) (also known as Single Carrier FDMA (SC-FDMA)) with CP. However, within the scope of the content of this case, multiplexing and multiplexing access are not limited to the above schemes, and can be provided using the following items: time division multiplexing access (TDMA), code division multiplexing access (CDMA), Frequency Division Multiplex Access (FDMA), Sparse Code Multiplex Access (SCMA), Resource Extended Multiplex Access (RSMA), or other suitable multiplexing access schemes. In addition, the following can be used to provide multiplexed DL transmission from base station 210 to UEs 222 and 224: time division multiplexing (TDM), code division multiplexing (CDM), frequency division multiplexing (FDM), orthogonal Frequency division multiplexing (OFDM), sparse code multiplexing (SCM) or other suitable multiplexing schemes.

Various aspects of the content of this case will be described with reference to the OFDM waveform schematically illustrated in FIG. 3. Those of ordinary skill in the art should understand that various aspects of the content of this case can be applied to the DFT-s-OFDMA waveform in substantially the same manner as described hereinafter. That is, for the sake of clarity, some examples of the content of this case can focus on OFDM links, but it should be understood that the same principle can also be applied to DFT-s-OFDMA waveforms.

In this case, the frame refers to a predetermined duration (for example, 10 ms) for wireless transmission, and each frame consists of a predetermined number (for example, 10) of sub-frames, such as 1ms each. composition. On a given carrier, a frame set may exist in the UL, and another frame set may exist in the DL. Referring now to FIG. 3, an expanded view of an exemplary DL sub-frame 302 is illustrated, illustrating an OFDM resource grid 304. However, as those skilled in the art will readily understand, depending on any number of factors, the PHY transmission structure for any particular application may be different from the examples described herein. Here, time is in the horizontal direction in units of OFDM symbols; and frequency is in the vertical direction in units of subcarriers or tones.

The resource grid 304 is divided into a plurality of resource elements (RE) 306. RE (which is 1 sub-carrier x 1 symbol) is the smallest discrete part of the time-frequency grid, and contains a single complex value representing the data from the physical channel or signal. Depending on the modulation used in a particular implementation, each RE may represent one or more bits of information. In some examples, the RE block may be referred to as a physical resource block (PRB), or more simply a resource block (RB) 308, which contains any suitable number of consecutive subcarriers in the frequency domain. In one example, the RB may include 12 subcarriers, the number of which is independent of the digital scheme used. In some examples, depending on the digital scheme, the RB may include any suitable number of consecutive OFDM symbols in the time domain. In the context of this case, it is assumed that a single RB such as RB 308 corresponds exactly to a single communication direction (for a given device's transmission or reception).

The UE typically utilizes only a subset of the resource grid 304. The RB may be the smallest resource element that can be allocated to the UE. Therefore, the more RBs scheduled for the UE and the higher the modulation scheme selected for the air interface, the higher the data rate for the UE. For example, a CC corresponds to a certain number of RBs that can be organized or configured into different BWPs that may or may not overlap in frequency.

In this illustration, the RB 308 is shown as occupying less than the entire bandwidth of the sub-frame 302, and some subcarriers are shown above and below the RB 308. In a given implementation, the sub-frame 302 may have a bandwidth corresponding to any number of RBs in the one or more RBs 308. Further, in this illustration, the RB 308 is shown as occupying less than the entire duration of the sub-frame 302, but this is only one possible example.

Each 1 ms sub-frame 302 may be composed of one or more adjacent time slots. In the example shown in FIG. 3, as an illustrative example, one subframe 302 includes four time slots 310. In some examples, a time slot may be defined according to a specified number of OFDM symbols having a given cyclic prefix (CP) length. For example, a time slot may include 7 or 14 OFDM symbols with a nominal CP. Additional examples may include micro time slots (eg, one or two OFDM symbols) with a shorter duration. In some cases, such micro-time slots may occupy resources that are scheduled for ongoing time slot transmissions for the same UE or for different UEs for transmission.

An expanded view of one of the time slots 310 illustrates the time slot 310 including a control area 312 and a data area 314. Generally, the control region 312 may carry a control channel (for example, PDCCH), and the data region 314 may carry a data channel (for example, PDSCH or PUSCH). Of course, the time slot may contain all DLs, all ULs, or at least one DL part and at least one UL part. The simple structure shown in FIG. 3 is merely exemplary in nature, and a different time slot structure may be used, and one or more of each of a control area and a data area may be included.

Although not illustrated in FIG. 3, various REs 306 within the RB 308 may be scheduled to carry one or more physical channels, including control channels, shared channels, data channels, and the like. The other REs 306 in the RB 308 may also carry pilot frequencies or reference signals, including but not limited to: demodulation reference signals (DMRS), control reference signals (CRS), or sounding reference signals (SRS). These pilot frequencies or reference signals can provide the receiving device to perform channel estimation on the corresponding channel, which can enable coherent demodulation / detection of the control and / or data channel in the RB 308.

In DL transmission, the sending device (eg, scheduling entity 108) may allocate one or more REs 306 (eg, within control area 312) to carry to one or more scheduled entities 106 including one or more DL control information 114 for each DL channel, such as PBCH; PSS; SSS; entity control format indicator channel (PCFICH); entity hybrid automatic repeat request (HARQ) indicator channel (PHICH); and / or entity downlink Link Control Channel (PDCCH), etc. The PCFICH provides information to assist the receiving device in receiving and decoding the PDCCH. The PDCCH carries downlink control information (DCI), which includes but is not limited to: power control commands, scheduling information, grants, and / or assignment of REs for DL and UL transmissions. The PHICH carries HARQ feedback transmissions, such as acknowledgements (ACK) or negative acknowledgements (NACK). HARQ is a technique well known to those of ordinary skill in the art, in which the integrity of a packet transmission can be checked (eg, using any suitable integrity check mechanism, such as a checksum, or cyclic redundancy check (CRC)) on the receiving side to use For accuracy. If the integrity of the transmission is confirmed, an ACK can be sent, and if the integrity is not confirmed, a NACK can be sent. In response to the NACK, the sending device can send HARQ retransmissions, which can implement additional merges, incremental redundancy, etc.

In UL transmission, a transmitting device (for example, the scheduled entity 106) may use one or more REs 306 to carry to the scheduling entity 108 and include one or more UL control channels (such as an entity uplink control channel ( PUCCH)) UL control information 118. UL control information can include various packet types and categories, including pilot frequency, reference signals, and information configured to enable or describe decoding of uplink data transmissions. In some examples, the control information 118 may include a scheduling request (SR), for example, a request for the scheduling entity 108 to schedule an uplink transmission. Here, in response to the SR sent on the control channel 118, the scheduling entity 108 can send downlink control information 114 that can schedule resources for uplink packet transmission. UL control information may also include HARQ feedback, channel state feedback (CSF), or any other suitable UL control information.

In addition to the control information, one or more REs 306 (eg, in the data area 314) may be assigned to user data or traffic data. Such traffic can be carried on one or more traffic channels. For example, for DL transmission, it is carried on the physical downlink shared channel (PDSCH); or for UL transmission, it is carried on the physical uplink shared channel (PUSCH). ) Carry on. In some examples, one or more of the REs 306 within the data area 314 may be configured to carry a system information block (SIB) that carries information that can enable access to a given cell.

The channels or carriers described above and illustrated in FIGS. 1 and 3 are not necessarily all channels or carriers that can be used between the scheduling entity 108 and the scheduled entity 106, and those skilled in the art will recognize To: In addition to the ones shown, other channels or carriers can also be used, such as other traffic, control, and feedback channels.

These physical channels are usually overridden and mapped to transmission channels for processing at the media access control (MAC) layer. A transmission channel carries a block called a transmission block (TB). Based on the modulation and coding scheme (MCS) and the number of RBs in a given transmission, the transmission block size (TBS), which can correspond to multiple bits of information, can be a controlled parameter.

FIG. 4 is a block diagram illustrating an example of a hardware implementation of a scheduling entity 400 employing a processing system 414. For example, the scheduling entity 400 may be a user equipment (UE) as shown in any one or more of FIGS. 1, 2, and / or 6. In another example, the scheduling entity 400 may be a base station as shown in any one or more of FIGS. 1, 2, and / or 6.

The scheduling entity 400 may be implemented using a processing system 414 that includes one or more processors 404. Examples of the processor 404 include a microprocessor, microcontroller, digital signal processor (DSP), field programmable gate array (FPGA), programmable logic device (PLD), state machine, gate control logic, individual hardware Body circuitry and other suitable hardware configured to perform the various functions described throughout this application. In various examples, the scheduling entity 400 may be configured to perform any one or more of the functions described herein. That is, the processor 404 as used in the scheduling entity 400 may be used to implement any one or more of the processes and procedures described and illustrated in FIGS. 6 to 12.

In this example, the processing system 414 may be implemented using a bus architecture, which is generally represented by a bus 402. The bus 402 may include any number of interconnecting buses and bridges, depending on the particular application and overall design constraints of the processing system 414. The bus 402 communicatively couples various circuits including one or more processors (typically represented by the processor 404), a memory 405, and a computer-readable medium (typically represented by the computer-readable medium 406). The memory 405 may store a capability report indicating a UE category of the scheduling entity 500 (eg, a UE) and various other information (eg, CA and BWP capabilities). The bus 402 can also be connected to various other circuits, such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and will therefore not be described further. The bus interface 408 provides an interface between the bus 402 and the transceiver 410. The transceiver 410 provides a communication interface or means for communicating with various other devices via a transmission medium. Depending on the nature of the device, a user interface 412 (eg, keyboard, display, speaker, microphone, joystick) may also be provided. Of course, such a user interface 412 is optional and may be omitted in some examples, such as a base station.

In some aspects of the present disclosure, the processor 404 may include circuits configured for various functions, including, for example, a processing circuit 440 and a communication circuit 442. For example, the circuit may be configured to implement one or more of the functions described below with respect to FIGS. 6 to 12. The processing circuit 440 may be configured to perform various data processing functions to facilitate communication using the wireless communication circuit 442. The communication circuit 442 can be configured to perform various wireless communication functions, including encoding, decoding, multiplexing, demultiplexing, interleaving, deinterleaving, noise cancellation, channel estimation, channel coding, carrier aggregation, bandwidth adaptation, and the like. In some examples, the scheduling entity may receive a UE capability report that may be stored in the memory 405.

The processor 404 is responsible for managing the bus 402 and general processing, including execution of software stored on a computer-readable medium 406. When executed by the processor 404, the software causes the processing system 414 to perform various functions described below for any particular device. The computer-readable medium 406 and the memory 405 may also be used to store data that is manipulated by the processor 404 when executing software.

One or more processors 404 in the processing system may execute software. Whether called software, firmware, intermediary software, microcode, hardware description language, or other, software should be broadly interpreted as instructions, instruction sets, codes, code snippets, codes, programs, subprograms, software modules , Applications, software applications, package software, routines, subroutines, objects, executable files, running threads, procedures, functions, etc. The software may reside on a computer-readable medium 406. Computer-readable media 406 may be non-transitory computer-readable media. For example, non-transitory computer-readable media include: magnetic storage devices (eg, hard disks, floppy disks, magnetic tapes), optical disks (eg, compact discs (CDs) or digital versatile discs (DVDs)), smart cards , Flash memory devices (for example, cards, sticks, or key drives), random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electronically erasable PROM (EEPROM), scratchpads, removable disks, and any other suitable media for storing software and / or instructions that can be accessed and read by a computer. The computer-readable medium 406 may reside in the processing system 414, external to the processing system 414, or distributed across multiple entities including the processing system 414. The computer-readable medium 406 may be embodied in a computer program product. For example, a computer program product may include computer-readable media in a packaging material. Those skilled in the art will recognize how to best implement the described functions presented throughout this case depending on the particular application and the overall design constraints imposed on the overall system.

In one or more examples, the computer-readable storage medium 406 may include software configured for various functions, including, for example, processing instructions 452 and communication instructions 454. For example, the software may be configured to implement one or more of the functions described with respect to FIGS. 6 to 12.

FIG. 5 is a conceptual diagram illustrating an example of a hardware implementation of an exemplary scheduled entity 500 employing a processing system 514. According to various aspects of the present case, an element, or any part of an element, or any combination of elements may be implemented using a processing system 514 including one or more processors 504. For example, the scheduled entity 500 may be a user equipment (UE) as shown in any one or more of FIGS. 1, 2, and / or 6.

The processing system 514 may be substantially the same as the processing system 414 shown in FIG. 4, and includes a bus interface 508, a bus 502, a memory 505, a processor 504, and a computer-readable medium 506. The memory 505 may store a capability report indicating the UE category of the scheduled entity 500 and various other information (eg, CA and BWP capabilities). Further, the scheduled entity 500 may include a user interface 512 and a transceiver 510, which are substantially similar to those described above in FIG. 4. The scheduled entity 500 may send a UE capability report to the scheduling entity 400. That is, as used in the scheduled entity 500, the processor 504 may be used to implement any one or more of the processes described and illustrated in FIGS. 6-12.

In some aspects of the present disclosure, the processor 504 may include circuits configured for various functions, including, for example, a processing circuit 540 and a communication circuit 542. For example, the circuit may be configured to implement one or more of the functions described with respect to FIGS. 6 to 12. The processing instructions 540 may be configured to perform various data processing functions to facilitate communication using the wireless communication circuit 542. The communication circuit 542 may be configured to perform various wireless communication functions, including encoding, decoding, multiplexing, demultiplexing, interleaving, deinterleaving, noise cancellation, channel estimation, channel coding, carrier aggregation, bandwidth adaptation, and the like. In one or more examples, the computer-readable storage medium 506 may include software configured for various functions, including, for example, processing instructions 552 and communication instructions 554. For example, the software may be configured to implement one or more of the functions described with respect to FIGS. 6 to 12.

FIG. 6 is a diagram illustrating an exemplary carrier aggregation signal transfer 600 according to some aspects of the present disclosure. The UE 602 can obtain the communication service from the base station (BS) 604 by executing the access procedure 606. An example of the access program 606 may be a random access program (RACH) and the like. In one aspect of the content of the present case, the UE 602 may be any UE among the UEs shown in FIG. 1, FIG. 2, and / or FIG. 5, for example, the scheduled entity 500 of FIG. 5. In one aspect of the content of this case, the BS 604 may be any of the base stations illustrated in FIG. 1, FIG. 2, and / or FIG. 4, for example, the scheduling entity 400 of FIG. 4.

After completing the access procedure 606, the UE may receive a UE capability query message 608 from the BS 604. The BS 604 uses the UE capability query message to specify what information the BS 604 wants to obtain from the UE. Subsequently, the UE 602 reports the capability information of the UE 602 requested by the BS 604. For example, the UE 602 may send UE capability information 610 to report the capabilities and / or UE category of the UE 602. The UE capability information 610 may include a UE type, a supported carrier aggregation configuration, a supported bandwidth configuration, a supported RAT, and the like. In one example, in response to carrier aggregation (CA) and bandwidth portion (BWP) configuration commands, the UE capability information 610 may instruct the UE to confirm the timing. The BS 604 may send a connection reconfiguration message 612 to the UE 602 to change some configuration of the connection or communication between the UE 602 and the BS 604. In one example, the connection reconfiguration message 612 may include a CA configuration command and / or a BWP configuration command. The CA configuration command may enable or disable the use of the CA at the UE 602. The CA configuration command may indicate a CC to be activated and / or deactivated. BWP commands can start, deactivate or switch BWP. In response to the connection reconfiguration message 612, the UE 602 may send a confirmation message (eg, CA / BWP ACK 614). For example, the CA / BWP ACK 614 may indicate that the UE received a CA or BWP command. After a certain period of time, the UE 602 completes the reconfiguration procedure for reconfiguring (eg, enabling, disabling, or switching) the CA and / or BWP. The UE 602 may then send a reconfiguration complete message 616 to notify the BS 604 that the CA and / or BWP reconfiguration has been completed.

FIG. 7 is a diagram illustrating an exemplary CA and BWP configuration timing according to some aspects of the content of the present case. In one aspect of the content of this case, the BS 604 may use the DCI carried in the PDCCH 702 to send a CA configuration command or a BWP configuration command. In response to a CA / BWP configuration command (eg, a connection reconfiguration message 612), the UE 602 may send a confirmation message (eg, a CA / BWP ACK 614 in FIG. 6), for example, in the PUCCH 704. The ACK response timing 706 between the DCI initiation of the CA / BWP configuration command and the ACK transmission may depend on the UE capability or class. In some examples, the base station 604 may determine the ACK timing based on the reported UE capability category. That is, different UEs may have different ACK response timings 706. For example, a UE with better processing and / or communication capabilities can send an ACK in PUCCH 704 faster than another UE with poorer processing and / or communication capabilities.

In one aspect of the content of this case, the BS 604 may use a MAC Control Element (CE) that can be carried in the PDSCH 708 to send CA configuration commands or BWP configuration commands. In response to a CA / BWP configuration command (eg, a connection reconfiguration message 612), the UE 602 may send a confirmation message (eg, a CA / BWP ACK 614 in FIG. 6), for example, in the PUCCH 704. The ACK timing 710 between MAC CE initiation and ACK transmission may depend on the capabilities or category of the UE. That is, in response to the CA / BWP configuration command carried in the MAC CE, different UEs may have different ACK response timings 710. After sending the ACK, the UE needs some time to reconfigure the software and / or hardware of the UE to operate in the new CA / BWP configuration. For example, the UE may need to enable or disable CC, and / or enable / disable / exchange BWP. In some examples, the DCI-based CA / BWP configuration / reconfiguration isochronous line 712 may be different (eg, longer or shorter) from the MAC CE-based CA / BWP configuration / reconfiguration isochronous line 714. At the end of the CA / BWP configuration isochronous line, configuration / reconfiguration should be completed. In some examples, the CA configuration command and the BWP configuration command may have different ACK timings and / or configuration isochrones.

In one aspect of the content of this case, the UE 602 may report the ACK response timing of the UE 602 to the base station 604 using, for example, radio resource control (RRC) signal transfer or other semi-static methods. For example, after receiving the CA / BWP configuration command, the UE 602 may send a message including the CA / BWP ACK timing 618 (see FIG. 6; for example, the same time slot, the next time slot, etc.) to the BS 604. In some examples, UE 602 may include CA / BWP ACK timing in UE capability information 610. The CA / BWP ACK timing indicates the time or time slot in which the UE sends an ACK to the CA / BWP configuration command.

CA configuration commands can start one or more CCs. The CA configuration command can disable one or more CCs. BWP configuration commands can start BWP. The BWP configuration command can disable BWP. BWP configuration commands can exchange BWPs (ie, make the UE switch from one BWP to another BWP in the same CC or different CCs).

In one aspect of the content of this case, the CA / BWP ACK isochronous line may be determined in advance based on UE capabilities or categories. For example, the BS 604 may store information about isochrones for a plurality of UE capability categories. When the UE 602 reports its UE capability category, the BS 604 may select a corresponding predetermined isochronous line for the CA / BWP configuration command destined for the UE. By determining and selecting the CA / BWP ACK isochronous line, the BS 604 can schedule UL resources for the UE to send the CA or BWP ACK based on the predetermined isochronous line. For example, the UE 602 may be scheduled to send an ACK in the same time slot as the UE receiving the CA / DWP configuration command or in a different time slot.

In another aspect of the content of the case, the BS 604 may use RRC signaling to configure CA / BWP configuration / reconfiguration isochronous lines (eg, isochronous lines 712 and 714). The CA / BWP isochronous line refers to a period of time between the initiation of a CA / BWP command and the completion of a corresponding reconfiguration (eg, activation / disabling) of a CA / BWP. For example, the BS 604 may send an RRC message (eg, a connection reconfiguration 612) to the UE including timeline information such as CA / BWP configuration. In another aspect of the content of this case, the BS 604 may use the DCI to send the CA / BWP configuration isochronous line. For example, the BS 604 may include explicit CA / BWP and other timeline information in the DCI. In some examples, the CA / BWP configuration isochronous line may be implied via the ACK / NACK timing in the DCI. In that case, the CA / BWP should be completed within a predetermined period after the ACK / NACK. In one example, the CA / BWP configuration isochrone includes processing time for: CA / BWP configuration commands (that is, after which ACK can be sent), RF retuning delay, total radiation sensitivity (TRS) loop Tracking, and channel status information (CSI) reports. Therefore, the ACK / NACK timing included in the DCI allows the UE to determine its end-to-end CA / BWP configuration isochrone.

FIG. 8 is a diagram illustrating a Bandwidth Part (BWP) adaptation example according to some aspects of the content of the present case. Initially, the UE 602 may communicate with the BS 604 using the first BWP (represented as BWP1 in FIG. 8) on the first component carrier (represented as CC1 in FIG. 8). The BS 604 may send a BWP configuration command 802 (eg, a BWP adaptation or handover command) to the UE to switch from a first BWP to a second BWP (denoted as BWP2 in FIG. 8). In one aspect of the content of this case, the BS 604 may send the BWP configuration command 802 using the resources of the BWP / CC undergoing BWP adaptation. In this example, the BS 604 sends the BWP configuration command 802 using the resources in the BWP1 of CC1. As a result, the UE 602 switches to use the BWP2 of CC1 to communicate with the BS 604. In one example, BWP1 may be a narrow-band BWP, and BWP2 may be a wide-band BWP with a wider bandwidth than BWP1. In another example, BWP2 may be a narrow-band BWP, and BWP1 may be a wide-band BWP with a wider bandwidth than BWP2. In yet another example, BWP1 and BWP2 may have the same bandwidth but use different frequency bands.

FIG. 9 is a diagram illustrating a second BWP adaptation example according to some aspects of the content of the present case. Initially, the UE 602 may communicate with the BS 604 using the first BWP (represented as BWP1 in FIG. 9) on the first CC (represented as CC1 in FIG. 8). The BS 604 may send a BWP configuration command 902 (eg, a BWP adaptation or handover command) to the UE to switch from BWP1 to a second BWP (denoted as BWP2 in FIG. 9). In one aspect of the content of this case, the BS 604 may send the BWP configuration command 902 using resources on CC2 different from CC1 undergoing BWP adaptation. This example may be referred to as cross-carrier BWP handover. The BS 604 may use the resources in the BWP 904 of CC2 to send the BWP configuration command 902. As a result, the UE 602 switches to use the BWP2 906 of CC1 to communicate with the BS 604. In one example, BWP1 may be a narrow-band BWP, and BWP2 may be a wide-band BWP with a wider bandwidth than BWP1. In another example, BWP2 may be a narrow-band BWP, and BWP1 may be a wide-band BWP with a wider bandwidth than BWP2. In yet another example, BWP1 and BWP2 may have the same bandwidth but use different frequency bands.

FIG. 10 is a diagram illustrating a third BWP adaptation example according to some aspects of the content of the present case. Initially, the UE 602 may communicate with the BS 604 using the first BWP 1002 (represented as BWP1 in FIG. 10) on the first CC (represented as CC1 in FIG. 10). The BS 604 may then send a BWP configuration command 1004 to switch from BWP1 1002 to BWP2 1006. When performing BWP adaptation on the same CC, the amount of resources (eg, uplink or UCI resources on PUCCH) that can be used to send corresponding BWP ACKs may be different after the BWP handover. In this example, BWP1 and BWP2 are on the same carrier CC1, but BWP2 provides a wider bandwidth. Therefore, more resources can be allocated to the UE 602 for sending a BWP ACK. In another example, BWP2 can provide a narrower bandwidth. Therefore, the UE 602 may have fewer resources for sending a BWP ACK after the handover.

In one aspect of the content of this case, the UE 602 may send an ACK for a BWP configuration command after a BWP handover. In this case, the UE may use the UCI resource 1008 of the BWP2 1006 to send the ACK. In addition to the resources for any operation based on BWP1 802 (eg, for ACK initiated by CA), BS 604 can also configure UCI resources for ACK based on the available resources of BWP2 804. Some kind of interruption or delay may occur before the ACK is sent to allow the UE to reconfigure (eg, retune the RF circuit) to use the new BWP.

In another aspect of the content of this case, the UE 602 may send an ACK for a BWP configuration command before the BWP handover. In this case, the UE may use the UCI resources of BWP1 1002 to send the ACK. Some kind of interruption or delay may occur after the ACK is sent to allow the UE to reconfigure (eg, retune the RF circuit) to use the new BWP2. In some aspects of the content of this case, the BS 604 may use RRC or DCI signaling to schedule UCI resources for BWP ACK.

FIG. 11 is a flowchart illustrating an exemplary process 1100 for configuring a CA or BWP according to some aspects of the content of the present case. As follows, some or all of the illustrated features may be omitted in specific implementations within the scope of this case, and some of the illustrated features may not be required for implementation of all embodiments. In some examples, the process 1100 may be performed by the scheduling entity 400 shown in FIG. 4. In some examples, process 1100 may be performed by any suitable device or means for performing the functions or algorithms described below.

At block 1102, a scheduling entity (eg, a base station) receives a capability report from a UE. The capability report indicates the UE's capability to utilize at least one of carrier aggregation (CA) or one or more bandwidth portions. For example, the scheduling entity may use the communication circuit 442 (see FIG. 4) and the transceiver 410 to receive the capability report. In one example, the UE may be any UE (eg, UE 602) shown in any of Figures 1, 2, and 6. In some examples, the capability report may indicate the UE category of the UE.

At block 1104, the scheduling entity may send a command to the UE to reconfigure at least one of a CA configuration or a bandwidth part (BWP) configuration. For example, the scheduling entity may use the communication circuit 442 and the transceiver 410 to send commands. The command can be a CA configuration command or a BWP configuration command. In one example, the scheduling entity may use DCI to send commands. In another example, the scheduling entity may use MAC CE to send commands. The CA configuration command can cause the UE to activate / deactivate one or more CCs. The BWP configuration command can enable / disable the BWP of the UE.

At block 1106, the scheduling entity may determine an expected response timing of an acknowledgement (ACK) of a command (eg, a CA configuration command or a BWP configuration) based on the capability report received from the UE. The expected response timing may be a time delay after which the UE sends the ACK of the command. For example, the scheduling entity may use the processing circuit 440 to analyze the capability report, which may indicate that, in response to the command, the UE can send an ACK after a predetermined time delay. The UE may indicate that the UE can send an ACK in the same time slot or different time slots in which the command is received. In some examples, the scheduling entity may determine the ACK timing based on the category of the UE. That is, the scheduling entity may have predetermined timing information (for example, a preset CA / BWP ACK timing) for various UE types.

At block 1108, the scheduling entity may receive the ACK based on the expected response timing. For example, the scheduling entity may use processing circuit 440 to schedule or allocate resources (eg, PRB) for receiving ACKs based on response timing, and use communication circuit 442 and transceiver 410 to receive using scheduled resources ACK.

FIG. 12 is a flowchart illustrating an exemplary process 1200 for configuring a CA or BWP according to some aspects of the present content. As described below, some or all of the illustrated features may be omitted in specific implementations within the scope of this case, and some of the illustrated features may not be required for implementation of all embodiments. In some examples, the process 1200 may be performed by the scheduled entity 500 illustrated in FIG. 5. In some examples, process 1200 may be performed by any suitable device or means for performing the functions or algorithms described below.

At block 1202, the scheduled entity (eg, UE 602) sends a capability report to the scheduling entity (eg, base station 604). The capability report indicates the UE's capability for wireless communication using at least one of carrier aggregation (CA) or one or a bandwidth portion. The capability report may indicate the UE category of the scheduled entity. For example, the scheduled entity may use the communication circuit 542 (see FIG. 5) and the transceiver 510 to send a capability report. In one example, the scheduled entity may be a UE (eg, UE 602) illustrated in any of Figures 1, 2, and 6.

At block 1204, the scheduled entity may receive a command from the scheduling entity to reconfigure at least one of a CA configuration or a BWP configuration. For example, the scheduled entity may use the communication circuit 542 and the transceiver 510 to receive commands. The command can be a CA configuration command or a BWP configuration command. In one example, the scheduled entity may receive commands in the DCI. In another example, the scheduled entity may receive the command in the MAC CE.

At block 1206, the scheduled entity may send a commanded ACK using a capability report or UE class based timing. For example, the scheduled entity may use the communication circuit 542 and the transceiver 510 to send an ACK. The capability report may indicate that the scheduled entity is able to send an ACK in a certain time slot after a predetermined time delay or after receiving the command. For example, the scheduled entity may indicate that the scheduled entity can send an ACK in the same time slot as when the command was received or in a different time slot after the time slot for receiving the command.

In one configuration, the apparatus 400 for wireless communication includes means for receiving a capability report from a UE, the capability report indicating a capability of the UE to utilize at least one of a CA or one or more bandwidth portions. The apparatus 400 also includes means for sending a command to the UE to reconfigure at least one of a CA configuration or a BWP configuration. The apparatus 400 also includes means for determining a response timing of the ACK of the command based on the capability report received from the UE. The apparatus 400 also includes means for receiving an ACK according to the determined response timing. In one aspect, the aforementioned components may be the processor 440 and the communication circuit 442, and FIG. 4 illustrates that the invention resides in the processor 440 and the communication circuit 442 configured to perform the functions described by the aforementioned components. In another aspect, the aforementioned means may be a circuit or any device configured to perform the functions described by the aforementioned means.

In one configuration, the apparatus 500 for wireless communication includes means for sending a capability report to a scheduling entity (e.g., a base station), and the capability report instructing apparatus 500 (e.g., UE) utilizes a CA or one or more frequencies The ability of at least one of the wide sections. The apparatus 500 also includes means for receiving commands from a scheduling entity to reconfigure at least one of a CA configuration or a BWP configuration. The apparatus 500 also includes means for transmitting an ACK of a command according to the capability or category of the UE.

Of course, in the above examples, the circuits included in the processor 404/504 are provided as examples only, and other components for performing the described functions may be included in various aspects of the content of this case, including but not limited to: storage Instructions in a computer-readable storage medium 406/506, or any other suitable device or component described in any one of FIGS. 1, 2 and / or 6 and using, for example, FIG. 6 to FIG. 12 describes the process and / or algorithm.

Several aspects of wireless communication networks have been presented with reference to the exemplary embodiments. As will be readily understood by those skilled in the art, the various aspects described throughout this case can be extended to other telecommunications systems, network architectures and communication standards.

For example, various aspects can be implemented in other systems defined by 3GPP, such as Long Term Evolution (LTE), Evolved Packet System (EPS), Universal Mobile Telecommunications System (UMTS), and / or Global Mobile System (GSM). Each aspect can also be extended to systems defined by 3rd Generation Partnership Project 2 (3GPP2), such as CDMA2000 and / or Evolutionary Data Optimization (EV-DO). Other examples may be implemented in systems employing IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Ultra Wide Band (UWB), Bluetooth, and / or other suitable systems. The actual telecommunications standard, network architecture, and / or communication standard used will depend on the particular application and the overall design constraints imposed on the system.

In this case, the word "exemplary" is used to mean "serving as an example, instance, or illustration." Any implementation or aspect described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other aspects of the subject matter. Similarly, the term "aspect" does not require that all aspects of the content of this case include the features, advantages, or modes of operation discussed. The term "coupled" is used herein to represent a direct or indirect coupling between two items. For example, if object A physically contacts object B and object B contacts object C, objects A and C may still be considered coupled to each other, even if they do not directly contact each other physically. For example, a first object can be coupled to a second object even if the first object never physically contacts the second object. The terms "circuitry" and "circuitry" are widely used and are intended to include hardware implementations of electrical equipment and conductors that, when connected and configured, perform the functions described in this case, and are not limited to electronics The type of circuit, and software implementation that, when executed by a processor, enables information and instructions to perform the functions described in this case.

One or more of the components, steps, features, and / or functions shown in FIGS. 1 to 12 may be rearranged and / or combined into a single component, step, feature, or function, or embodied in several components, Steps or functions. Additional elements, components, steps, and / or functions may be added without departing from the novel features disclosed herein. The devices, devices, and / or components shown in Figures 1 to 12 may be configured to perform one or more of the methods, features, or steps described herein. The novel algorithms described in this article can also be efficiently implemented in software and / or embedded in hardware.

It is understood that the specific order or hierarchy of steps in the methods disclosed is an illustration of exemplary processes. Based on design preferences, it is understood that a particular order or hierarchy of steps in a method may be rearranged. The appended method claims present the elements of the various steps in a sampling order and, unless specifically stated therein, are not meant to be limited to the specific order or hierarchy presented.

100‧‧‧Wireless communication system

102‧‧‧ Core Network

104‧‧‧Radio Access Network (RAN)

106‧‧‧User Equipment (UE)

108‧‧‧Base Station

110‧‧‧External Data Network

112‧‧‧ Downlink Traffic

114‧‧‧ downlink control information

116‧‧‧ Uplink Traffic

118‧‧‧UL Control Information

120‧‧‧Reload part

200‧‧‧RAN

202‧‧‧Macrocell

204‧‧‧ Macrocell

206‧‧‧ Macrocell

208‧‧‧Small cells

210‧‧‧Base Station

212‧‧‧Base Station

214‧‧‧Third Base Station

216‧‧‧Remote Radio Head (RRH)

218‧‧‧Base Station

220‧‧‧ Quadrotor / Drone / Base Station

222‧‧‧UE

224‧‧‧UE

226‧‧‧UE

227‧‧‧P2P signal / side link signal

228‧‧‧UE

230‧‧‧UE

232‧‧‧UE

234‧‧‧UE

236‧‧‧UE

238‧‧‧UE / scheduled entity

240‧‧‧UE

242‧‧‧UE

302‧‧‧DL sub frame

304‧‧‧Resource Grid

306‧‧‧Resource Elements (RE)

308‧‧‧Resource Block (RB)

310‧‧‧hour slot

312‧‧‧Control Area

314‧‧‧ Data area

400‧‧‧ Scheduled entity

402‧‧‧Bus

404‧‧‧Processor

405‧‧‧Memory

406‧‧‧Computer-readable media

408‧‧‧Bus Interface

410‧‧‧ Transceiver

412‧‧‧user interface

414‧‧‧Processing System

440‧‧‧Processing Circuit

442‧‧‧communication circuit

452‧‧‧Processing Instructions

454‧‧‧Communication instructions

500‧‧‧ scheduled entity

502‧‧‧Bus

504‧‧‧Processor

505‧‧‧Memory

506‧‧‧Computer-readable media

508‧‧‧ Bus Interface

510‧‧‧ Transceiver

512‧‧‧user interface

514‧‧‧treatment system

540‧‧‧Processing circuit

542‧‧‧communication circuit

552‧‧‧Processing Instructions

554‧‧‧Communication Instructions

600‧‧‧ Carrier aggregation signal transmission

602‧‧‧UE

604‧‧‧BS

606‧‧‧Access Procedure

608‧‧‧UE capability inquiry message

610‧‧‧UE Capability Information

612‧‧‧Connection reconfiguration message

614‧‧‧CA / BWP ACK

616‧‧‧Reconfiguration completed message

618‧‧‧ACK timing

702‧‧‧PDCCH

704‧‧‧PUCCH

706‧‧‧ACK response timing

708‧‧‧PDSCH

710‧‧‧ACK timing

712‧‧‧ Isochrone

714‧‧‧ isochronous

802‧‧‧BWP configuration commands

902‧‧‧BWP configuration command

904‧‧‧BWP

906‧‧‧BWP2

1002‧‧‧BWP1

1004‧‧‧BWP configuration commands

1006‧‧‧BWP2

1008‧‧‧UCI Resources

1100‧‧‧process

1102‧‧‧box

1104‧‧‧box

1106‧‧‧box

1108‧‧‧box

1200‧‧‧process

1202‧‧‧block

1204‧‧‧box

1206‧‧‧box

FIG. 1 is a schematic diagram of a wireless communication system.

FIG. 2 is a conceptual diagram of an example of a radio access network.

FIG. 3 is a schematic diagram of an organization using an orthogonal frequency division multiplexing (OFDM) wireless resource in an air interface.

FIG. 4 is a block diagram conceptually illustrating an example of a hardware implementation for a scheduling entity according to some aspects of the present content.

5 is a block diagram conceptually illustrating an example of a hardware implementation for a scheduled entity according to some aspects of the content of the present case.

FIG. 6 is a diagram illustrating an exemplary carrier aggregation signal transfer according to some aspects of the present disclosure.

FIG. 7 is a diagram illustrating exemplary carrier aggregation (CA) and bandwidth portion (BWP) configuration timings according to some aspects of the present content.

FIG. 8 is a diagram illustrating an example of BWP adaptation according to some aspects of the content of the present case.

FIG. 9 is a diagram illustrating a second BWP adaptation example according to some aspects of the content of the present case.

FIG. 10 is a diagram illustrating a third BWP adaptation example according to some aspects of the content of the present case.

FIG. 11 is a flowchart illustrating an exemplary process for configuring a CA or BWP according to some aspects of the content of the present case.

FIG. 12 is a flowchart illustrating another exemplary process for configuring a CA or BWP according to some aspects of the content of the present case.

Domestic hosting information (please note in order of hosting institution, date, and number) None

Information on foreign deposits (please note in order of deposit country, institution, date, and number) None

Claims (36)

A method of wireless communication capable of operating at a scheduling entity includes the following steps: receiving a capability report from a user equipment (UE), the capability report instructing the UE to use carrier aggregation (CA) or one or more frequencies A capability of at least one of the wide sections; sending a command to the UE to reconfigure at least one of a CA configuration or a bandwidth section (BWP) configuration; determined based on the capability report received from the UE An expected response sequence of an ACK of the command; and receiving the ACK according to the expected response sequence. The method of claim 1, wherein sending the command includes selecting to send the command in: a downlink control information (DCI) of a downlink control channel; or a media access control (MAC) control Element (CE). The method according to claim 2, wherein the response timing when using the DCI is different from the response timing when using the MAC CE. The method of claim 1, wherein the step of sending the command includes at least one of the following steps: sending a CA configuration command to change a component carrier (CC) used by the UE; or sending a BWP configuration command To change a BWP used by the UE. The method according to claim 1, wherein the step of sending the command comprises the following steps: sending a BWP configuration command using a first component carrier (CC), wherein the BWP configuration command configures the UE from the first CC A first BWP of the switch to a second BWP of the first CC. The method according to claim 5, wherein the step of receiving the ACK comprises the following steps: before switching to the second BWP, using the first BWP to receive the ACK of the command. The method according to claim 5, wherein the step of receiving the ACK comprises the following steps: After switching to the second BWP, using the second BWP to receive the ACK of the command. The method of claim 1, wherein the step of sending the command comprises the following steps: sending a BWP configuration command using a first component carrier (CC), wherein the BWP configuration command configures the UE from a second CC A first BWP of the switch to a second BWP of the second CC. The method according to claim 1, further comprising using at least one of the following to configure a timing for completing the reconfiguration of the CA configuration or the BWP configuration: radio resource control (RRC) signal delivery; or Downlink Control Information (DCI) for a downlink control channel. A method of wireless communication capable of operating at a user equipment (UE) includes the following steps: sending a capability report to a scheduling entity, the capability report instructing the UE to use carrier aggregation (CA) or one or more A capability of at least one of the bandwidth portions; receiving a command from the scheduling entity to reconfigure at least one of a carrier aggregation (CA) configuration or a bandwidth portion (BWP) configuration; and using the capability based on the capability A sequence is reported to send an acknowledgement (ACK) of the command. The method of claim 10, wherein the capability report is configured to indicate a response sequence of the ACK in response to the command from the scheduling entity. The method of claim 10, wherein the step of receiving the command comprises the following steps: receiving the command in a downlink control information (DCI) of a downlink control channel; or a medium access control (MAC) The command is received in the control element (CE). The method according to claim 12, wherein a timing of the ACK when DCI is used is different from a timing of the ACK when MAC CE is used. The method of claim 10, wherein the step of receiving the command includes at least one of the following steps: receiving a CA configuration command to change a component carrier (CC) used by the UE; or receiving a BWP configuration command To change a BWP used by the UE. The method according to claim 10, wherein the step of receiving the command comprises the following steps: using a first component carrier (CC) to receive a BWP configuration command, wherein the BWP command configures the UE from the first CC A first BWP is switched to a second BWP of the first CC. The method according to claim 15, wherein the step of sending the ACK comprises the following steps: before switching to the second BWP, using the first BWP to send the ACK of the command. The method according to claim 15, wherein the step of sending the ACK comprises the following steps: After switching to the second BWP, using the second BWP to send the ACK of the command. The method according to claim 10, wherein the step of receiving the command comprises the following steps: using a first component carrier (CC) to receive a BWP configuration command, wherein the BWP command configures the UE from a second CC A first BWP is switched to a second BWP of the second CC. A device for wireless communication includes: a communication interface configured to communicate with a user equipment (UE); a memory; and a processor operatively coupled with the communication interface and the memory Wherein the processor and the memory are configured to: receive a capability report from the UE, the capability report instructing the UE to use a capability of at least one of carrier aggregation (CA) or one or more bandwidth portions; Send a command to the UE to reconfigure at least one of a CA configuration or a bandwidth part (BWP) configuration; determine an expectation of an acknowledgement (ACK) of the command based on the capability report received from the UE Response timing; and receiving the ACK according to the expected response timing. The device according to claim 19, wherein the processor and the memory are also configured to choose to send the command in: downlink control information (DCI) of a downlink control channel; or a medium Access Control (MAC) Control Element (CE). The device according to claim 20, wherein the response timing when using the DCI is different from the response timing when using the MAC CE. The device according to claim 19, wherein the command includes at least one of the following: a CA configuration command configured to change a component carrier (CC) used by the UE; or a BWP configuration command, It is configured to change a BWP used by the UE. The device according to claim 19, wherein the processor and the memory are also configured to use a first component carrier (CC) to send the command including a BWP configuration command, and wherein the BWP configuration command changes the The UE is configured to switch from a first BWP of the first CC to a second BWP of the first CC. The device according to claim 23, wherein the processor and the memory are also configured to: before switching to the second BWP, use the first BWP to receive the ACK of the command. The device according to claim 23, wherein the processor and the memory are also configured to: after switching to the second BWP, use the second BWP to receive the ACK of the command. The device according to claim 19, wherein the processor and the memory are also configured to use a first component carrier (CC) to send the command including a BWP configuration command, wherein the BWP configuration command configures the UE To switch from a first BWP of a second CC to a second BWP of the second CC. The device of claim 19, wherein the processor and the memory are also configured to use at least one of the following to configure a timing for completing the reconfiguration of the CA configuration or the BWP configuration: Radio resource control (RRC) signal transfer; or downlink control information (DCI) on the downlink control channel. A user equipment (UE) for wireless communication includes: a communication interface configured to communicate with a scheduling entity; a memory; and a processor operatively communicating with the communication interface and the memory Body coupling, where the processor and the memory are configured to: send a capability report to the scheduling entity, the capability report instructing the UE to use carrier aggregation (CA) or at least one of one or more bandwidth portions Receiving a command from the scheduling entity to reconfigure at least one of a carrier aggregation (CA) configuration or a bandwidth part (BWP) configuration; and sending the using a timing based on the capability report Acknowledgement of the command (ACK). The UE according to claim 28, wherein the capability report is configured to indicate a response sequence of the ACK in response to the command from the scheduling entity. The UE according to claim 28, wherein the processor and the memory are also configured to select to receive the command in the following: a downlink control channel (DCI) of a downlink control channel; or a medium Access Control (MAC) Control Element (CE). The UE according to claim 30, wherein a timing of the ACK when using DCI is different from a timing of the ACK when using MAC CE. The UE according to claim 28, wherein the processor and the memory are also configured to: receive the command including a CA configuration command to change a component carrier (CC) used by the UE; or receive including a BWP This command of the command is configured to change a BWP used by the UE. The UE according to claim 28, wherein the processor and the memory are also configured to use a first component carrier (CC) to receive the command including a BWP configuration command, wherein the BWP command configures the UE To switch from a first BWP of the first CC to a second BWP of the first CC. The UE according to claim 33, wherein the processor and the memory are also configured to: before switching to the second BWP, use the first BWP to send the ACK of the command. The UE according to claim 33, wherein the processor and the memory are also configured to: after switching to the second BWP, use the second BWP to send the ACK of the command. The UE according to claim 28, wherein the processor and the memory are also configured to use a first component carrier (CC) to receive the command including a BWP configuration command, wherein the BWP command configures the UE To switch from a first BWP of a second CC to a second BWP of the second CC.