Triggering reference signals in wireless networks
By using reference signals to trigger activation and synchronization of auxiliary service cells (SCells) in wireless communication systems, the problem of insufficient data rate and reliability in multi-cell communication is solved, and a more efficient multi-cell transmission environment is achieved.
Patent Information
- Application Number
- CN202080060489.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2020-09-01
- Filing Date
- 2020-09-02
- Publication Date
- 2024-11-08
- Estimated Expiration
- 2040-09-02
AI Technical Summary
In wireless communication systems, it is difficult for the prior art to effectively activate and synchronize auxiliary service cells (SCells) to realize multi-cell communication, resulting in insufficient data rate and reliability.
Multi-cell communication is achieved by transmitting a reference signal trigger between a user equipment (UE) and a master serving cell (PCell), SCell is activated, and synchronized with the SCell based on multiple reference signals. The method includes receiving a reference signal message at the PCell, identifying and transmitting a reference signal for the SCell, ensuring that the UE is synchronized with the time and frequency of the SCell, thereby activating the SCell for multi-cell communication.
It improves data rate and communication reliability, enhances user experience in multi-cell transmission environment, and reduces the time and overhead required for SCell activation through effective reference signal management and synchronization mechanism.
Smart Images

Figure CN114365446B_ABST
Abstract
Description
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This patent application claims priority to and the benefit of pending non-provisional application No. 17 / 009,607, filed in the U.S. Patent and Trademark Office on September 1, 2020, and provisional application No. 62 / 895,832, filed in the U.S. Patent and Trademark Office on September 4, 2019, the entire contents of which are incorporated herein by reference as if fully set forth below and for all applicable purposes. Technical Field
[0003]
[0013] Generally speaking, the techniques discussed below relate to wireless communication systems, and more particularly, to multi-cell configurations in wireless communication systems. Background Art
[0004] A wireless communication network may utilize a coordinated multi-point (CoMP) network configuration in which transmissions from multiple transmission points (TRPs) may be directed to a UE simultaneously. In a multi-TRP transmission scheme, multiple TRPs may or may not be co-located and may or may not be in the same cell. Each of the multiple TRPs may send the same or different data to a user equipment (UE). When different data is sent from multiple TRPs, higher throughput may be achieved. When the same data (with potentially different redundant versions) is sent from multiple TRPs, transmission reliability may be improved.
[0005] In some examples, each TRP can utilize the same carrier frequency to communicate with the UE. In other examples, each TRP can utilize different carrier frequencies (called component carriers), and carrier aggregation can be performed at the UE. In this example, the multi-TRP transmission scheme can be referred to as a multi-carrier or multi-cell transmission scheme. In a multi-carrier or multi-cell transmission scheme, there are several serving cells, each of which communicates with the UE using a different component carrier. One of the serving cells can be referred to as a primary serving cell (PCell), and the other serving cells can be referred to as secondary serving cells (SCells). The PCell maintains the primary connection with the UE and is responsible for radio resource control (RRC) connection establishment.
[0006] A multi-cell transmission scheme may be implemented across different radio access technologies (RATs), such as 5G New Radio (NR) or Long Term Evolution (LTE). In such a multi-RAT-dual connectivity (MR-DC) configuration, the PCell may be associated with a first RAT (e.g., 5G-NR or LTE) and the SCell may be associated with a second RAT (e.g., 5G-NR or LTE). Enhancements in a multi-cell environment are continued to improve user experience. Summary of the invention
[0007] A summary of one or more aspects of the present disclosure is presented below in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all expected features of the present disclosure, and is neither intended to identify key or important elements of all aspects of the present disclosure, nor is it intended to delineate the scope of any or all aspects of the present disclosure. Its sole purpose is to present some concepts of one or more aspects of the present disclosure as a prelude to a more detailed description presented later.
[0008] In one example, a method for a user equipment (UE) to communicate in a wireless communication network including a primary serving cell (PCell) and a secondary serving cell (SCell) is disclosed. The method may include: receiving a reference signal trigger from the PCell, the reference signal trigger being used to trigger communication and processing of one or more reference signals between the UE and the SCell; and synchronizing with the SCell based on the one or more reference signals to activate the SCell for multi-cell communication.
[0009] Another example provides a scheduled entity in a wireless communication network including a primary serving cell (PCell) and a secondary serving cell (SCell). The scheduled entity includes: a transceiver; a memory; and a processor communicatively coupled to the transceiver and the memory. The processor and the memory may be configured to: receive a reference signal trigger from the PCell, the reference signal trigger being used to trigger communication and processing of one or more reference signals between the UE and the SCell; and synchronize with the SCell based on the one or more reference signals to activate the SCell for multi-cell communication.
[0010] In another example, a method for a primary serving cell (PCell) to facilitate multi-cell communication in a wireless communication network including a PCell and a secondary serving cell (SCell) is disclosed. The method may include: communicating with a user equipment (UE) in the PCell; activating communication between the UE and the SCell for multi-cell communication; and sending a reference signal trigger to the UE to enable the UE to synchronize with the SCell, the reference signal trigger being used to trigger communication and processing of one or more reference signals between the UE and the SCell.
[0011] In another example, a method for a secondary serving cell (SCell) to facilitate multi-cell communication in a wireless communication network including a primary serving cell (PCell) and a SCell. The method may include: configuring multiple reference signals in the SCell; receiving a reference signal message from the PCell for a user equipment (UE) to use to synchronize with the SCell, the reference signal message including an indication of one or more reference signals of the multiple reference signals selected by the PCell; and communicating the one or more reference signals with the UE to enable the UE to synchronize with the SCell and activate the SCell for multi-cell communication.
[0012] After reading the following specific embodiments, these aspects and other aspects will become more fully understood. After reading the following description of specific exemplary embodiments in conjunction with the accompanying drawings, other aspects, features and embodiments will become apparent to those of ordinary skill in the art. Although the features of the present disclosure can be discussed with respect to certain embodiments and accompanying drawings below, all embodiments of the present disclosure can include one or more advantageous features discussed herein. In other words, although one or more embodiments can be discussed as having certain advantageous features, one or more features in such features can also be used according to the various embodiments of the present disclosure discussed herein. In a similar manner, although exemplary embodiments can be discussed hereinafter as equipment, system or method embodiments, it should be understood that such exemplary embodiments can be implemented in various equipment, systems and methods. BRIEF DESCRIPTION OF THE DRAWINGS
[0013] Figure 1 is a schematic diagram of a wireless communication system according to some aspects.
[0014] Figure 2 is a conceptual illustration of an example of a wireless access network in accordance with some aspects.
[0015] Figure 3 is a schematic diagram of the organization of radio resources in an air interface utilizing orthogonal frequency division multiplexing (OFDM) according to some aspects.
[0016] Figure 4 is a block diagram illustrating a wireless communication system supporting multiple-input multiple-output (MIMO) communications in accordance with some aspects.
[0017] Figure 5 is a diagram illustrating beamforming in a wireless communication system.
[0018] Figure 6 is a diagram illustrating a multi-cell transmission environment according to some aspects.
[0019] Figure 7is a diagram illustrating example signaling for activating communication with a secondary serving cell (SCell) in a multi-cell transmission environment according to some aspects.
[0020] Figure 8 is a block diagram illustrating an example of a hardware implementation for employing a scheduling entity of a processing system according to some aspects.
[0021] Fig. 9 is a block diagram illustrating an example of a hardware implementation for a scheduled entity employing a processing system according to some aspects.
[0022] Fig.10 is a flow chart illustrating an example process for UE synchronizing communications with SCells to activate the SCells in a multi-cell transmission environment according to some aspects.
[0023] Fig.11 is a flow chart illustrating an example process for a UE to handle reference signal triggering from a PCell to activate an SCell in a multi-cell transmission environment according to some aspects.
[0024] Fig.12 is a flow chart illustrating another example process for UE synchronizing communications with SCells to activate the SCells in a multi-cell transmission environment according to some aspects.
[0025] Fig.13 is a flow chart illustrating an example process for a scheduling entity serving a primary serving cell (PCell) to activate communications between a scheduled entity and a SCell in a multi-cell transmission environment in accordance with some aspects.
[0026] Fig.14 is a flow chart illustrating another exemplary process for a scheduling entity serving a primary serving cell (PCell) to activate communications between a scheduled entity and a SCell in a multi-cell transmission environment in accordance with some aspects.
[0027] Fig.15 is a flow chart illustrating another exemplary process for a scheduling entity serving a primary serving cell (PCell) to activate communications between a scheduled entity and a SCell in a multi-cell transmission environment in accordance with some aspects.
[0028] Fig.16 is a flow chart illustrating an example process for a scheduling entity serving a SCell in a multi-cell transmission environment to facilitate synchronization with a scheduled entity to activate the SCell for communication with the scheduled entity in accordance with some aspects.
[0029] Fig.17is a flow chart illustrating another example process for a scheduling entity serving a SCell in a multi-cell transmission environment to facilitate synchronization with a scheduled entity to activate the SCell for communication with the scheduled entity in accordance with some aspects.
[0030] Fig.18 is a flow chart illustrating another example process for a scheduling entity serving a SCell in a multi-cell transmission environment to facilitate synchronization with a scheduled entity to activate the SCell for communication with the scheduled entity in accordance with some aspects. DETAILED DESCRIPTION
[0031] The detailed description set forth below in conjunction with the accompanying drawings is intended as a description of various configurations and is not intended to represent the only configuration in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In some cases, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.
[0032] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified with the frequency range names FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). Frequencies between FR1 and FR2 are typically referred to as mid-band frequencies. Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as the “Sub-6 GHz” band in various documents and articles. FR2 sometimes presents a similar naming problem, although unlike the Extremely High Frequency (EHF) band (30 GHz–300 GHz), which is identified as the “millimeter wave” band by the International Telecommunication Union (ITU), it is often (interchangeably) referred to as the “millimeter wave” band in documents and articles.
[0033] In view of the above, unless otherwise explicitly stated, it should be understood that the term "sub-6GHz" and the like (if used herein) can broadly represent frequencies that may be lower than 6GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise explicitly stated, it should be understood that the term "millimeter wave" and the like (if used herein) can broadly represent frequencies that may include mid-band frequencies, may be within FR2, or may be within the EHF band.
[0034] Although various aspects and embodiments are described in this application by the description of some examples, it will be understood by those skilled in the art that other implementations and use cases may occur in many different arrangements and scenarios. The innovation described herein can be implemented across many different platform types, devices, systems, shapes, sizes and packaging arrangements. For example, embodiments and / or use can be implemented via integrated chip embodiments and other devices based on non-module components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing equipment, medical equipment, AI-enabled devices, etc.). Although some examples may be specifically targeted or not targeted at use cases or applications, various applicability of the described innovations may occur. The range of implementations can range from chip-level or modular components to non-modular, non-chip-level implementations and further to the spectrum of aggregated, distributed or original equipment manufacturer (OEM) devices or systems incorporating one or more aspects of the described innovations. In some actual settings, the device incorporating the various aspects and features described may also have to include additional components and features for implementing and practicing the claimed and described embodiments. For example, the transmission and reception of wireless signals necessarily include several components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). It is intended that the innovations described herein can be practiced in a variety of devices, chip-level components, systems, distributed arrangements, end-user devices, etc., of varying sizes, shapes, and configurations.
[0035] Various aspects of the present disclosure relate to mechanisms for activating a secondary serving cell (SCell) in a wireless communication network that supports a multi-cell transmission environment. In some examples, a scheduled entity (e.g., UE) in a connection mode with a primary serving cell (PCell) can be synchronized with the SCell to activate the SCell for multi-cell communication with the PCell and the SCell. In order to achieve synchronization with the SCell, one or more reference signals can be transmitted between the scheduled entity and the SCell for on-demand processing thereof. For example, the PCell can trigger communication and processing of one or more reference signals between the scheduled entity and the SCell when it is determined that communication between the scheduled entity and the SCell is activated. In some examples, the PCell can utilize a first radio access technology (RAT) and the SCell utilizes a second RAT.
[0036] In some examples, the PCell may send a reference signal trigger to the scheduled entity that identifies one or more reference signals to be transmitted with the SCell. The reference signal trigger may be included, for example, within a medium access control-control element (MAC-CE). In addition, the PCell may also send an indication of one or more reference signals identified in the reference signal trigger to the SCell via, for example, backhaul signaling. Examples of reference signals may include, but are not limited to, a channel state information-reference signal (CSI-RS), a synchronization signal block (SSB), or a sounding reference signal (SRS).
[0037] In some examples, each of the reference signals may be pre-configured with the same or different transmission configuration index (TCI) state (e.g., for downlink reference signals) or spatial relationship indicator (SRI) (e.g., for uplink reference signals). For example, each of the reference signals may be transmitted on the same or different beams. In some examples, one or more of the downlink reference signals may be sent from different transmit receive points (TRPs). In this example, the TCI state may include a TRP identity or a cell identity.
[0038] In some examples, the scheduled entity may send confirmation information to the SCell to confirm receipt of the MAC-CE. In an example where a downlink reference signal is transmitted using different TCI states (e.g., via different beams), the scheduled entity may send confirmation information in a beam scanning manner across one or more beams in the beam used for the reference signal. For example, the scheduled entity may receive a reference signal and send confirmation information on an uplink beam corresponding to the spatial direction of the downlink beam of the received downlink reference signal. In some examples, the SCell may select a service beam pair link (BPL) for the scheduled entity based on different receive beams carrying confirmation information. The SCell may also provide the received confirmation information to the PCell via, for example, a backhaul link.
[0039] The various concepts presented throughout this disclosure may be implemented across a variety of telecommunication systems, network architectures and communication standards. Figure 1 , various aspects of the present disclosure are illustrated with reference to a wireless communication system 100 as a non-limiting illustrative example. The wireless communication system 100 includes three interacting domains: a core network 102, a radio access network (RAN) 104, and a user equipment (UE) 106. By virtue of the wireless communication system 100, the UE 106 may be enabled to communicate data with an external data network 110, such as (but not limited to) the Internet.
[0040] The RAN 104 may implement any suitable one or more wireless communication technologies to provide wireless 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, commonly referred to as 5G. As another example, the RAN 104 may operate under a mix of 5G NR and Evolved Universal Terrestrial Radio Access Network (eUTRAN) standards, commonly referred to as Long Term Evolution (LTE). 3GPP refers to this hybrid RAN as the Next Generation RAN, or NG-RAN. Of course, many other examples may be utilized within the scope of the present disclosure.
[0041] As shown, the RAN 104 includes multiple base stations 108. In a broad sense, a base station is a network element in a radio access network that is responsible for wirelessly transmitting and receiving to or from a UE in one or more cells. In different technologies, standards, or contexts, a base station may be referred to as a base transceiver station (BTS), a wireless base station, a wireless transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), an access point (AP), a Node B (NB), an eNode B (eNB), a gNode B (gNB), or some other suitable terminology by those skilled in the art.
[0042] The wireless access network 104 is also shown to support wireless communications for multiple mobile devices. A mobile device may be referred to as a user equipment (UE) in the 3GPP standard, but those skilled in the art may also refer to it as a mobile station (MS), a user station, a mobile unit, a user unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile user station, an access terminal (AT), a mobile terminal, a wireless terminal, a remote terminal, a mobile phone, a terminal, a user agent, a mobile client, a client, or some other suitable term. A UE may be a device that provides a user with access to network services.
[0043] In this document, a "mobile" device does not necessarily have mobile capabilities and can be stationary. The term "mobile device" or "mobile device" refers broadly to a wide variety of devices and technologies. A UE may include several hardware structural components whose size, shape, and arrangement are used to 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 phones, cellular (cell) phones, smart phones, session initiation protocol (SIP) phones, laptops, personal computers (PCs), notebooks, netbooks, smart books, tablet computers, personal digital assistants (PDAs), and a wide range of embedded systems (e.g., corresponding to the "Internet of Things" (IoT)). A mobile device may additionally be a car or other transport vehicle, a remote sensor or actuator, a robot or robotic device, a satellite radio unit, a global positioning system (GPS) device, an object tracking device, a drone, a multi-axis aircraft, a quadcopter, a remote control device, a consumer and / or wearable device (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), an appliance, a vending machine, smart lighting, a home security system, a smart meter, etc. The mobile device may additionally be a smart energy device, a security device, a solar panel or solar array, a municipal infrastructure device (controlling power (e.g., smart grid), lighting, water, etc.), an industrial automation and enterprise device, a logistics controller, an agricultural device, etc. In addition, the mobile device may provide connected medicine or telemedicine support (i.e., healthcare at a distance). Telehealth devices may include remote health monitoring devices and remote health management devices, whose communications may be given priority processing or access over other types of information, for example, in terms of priority access for transmitting critical service data and / or associated QoS for transmitting critical service data.
[0044] Wireless communication between RAN 104 and UE 106 can be described as utilizing an air interface. Transmissions from a base station (e.g., base station 108) to one or more UEs (e.g., UE 106) over an air interface can be referred to as downlink (DL) transmissions. According to certain aspects of the present disclosure, the term "downlink" can refer to point-to-multipoint transmissions originating from a scheduling entity (further described below; e.g., base station 108). Another way to describe this scheme is to use the term "broadcast channel multiplexing". Transmissions from a UE (e.g., UE 106) to a base station (e.g., base station 108) can be referred to as uplink (UL) transmissions. According to other aspects of the present disclosure, the term "uplink" can refer to point-to-point transmissions originating from a scheduled entity (further described below; e.g., UE 106).
[0045] In some examples, access to the air interface may be scheduled, wherein a scheduling entity (e.g., a base station 108) allocates communication resources between some or all devices and equipment within its service area or cell. In the present disclosure, as discussed further below, a scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more scheduled entities. That is, for scheduled communications, a UE 106 (which may be a scheduled entity) may utilize resources allocated by the scheduling entity 108.
[0046] Base station 108 is not the only entity that can act as a scheduling entity. That is, in some examples, a UE can act as a scheduling entity to schedule resources for one or more scheduled entities (e.g., one or more other UEs).
[0047] like Figure 1 As shown, the scheduling entity 108 can broadcast downlink traffic 112 to one or more scheduled entities 106. Broadly speaking, the scheduling entity 108 is a node or device responsible for scheduling traffic in the wireless communication network, including downlink traffic 112 and, in some examples, uplink traffic 116 from one or more scheduled entities 106 to the scheduling entity 108. On the other hand, the scheduled entity 106 is a node or device that receives downlink control information 114, including but not limited to scheduling information (e.g., grants), synchronization or timing information, or other control information from another entity in the wireless communication network (such as the scheduling entity 108).
[0048] In addition, uplink and / or downlink control information and / or traffic information can be time-divided into frames, subframes, time slots and / or symbols. As used herein, a symbol can refer to a time unit that carries one resource element (RE) per subcarrier in an orthogonal frequency division multiplexing (OFDM) waveform. A time slot can carry 7 or 14 OFDM symbols. A subframe can refer to a duration of 1ms. Multiple subframes or time slots can be grouped together to form a single frame or radio frame. Of course, these definitions are not required, and any suitable scheme for organizing waveforms can be utilized, and the various time divisions of waveforms can have any suitable duration.
[0049] Typically, the base stations 108 may include a backhaul interface for communicating with a backhaul portion 120 of the wireless communication system. The backhaul 120 may provide a link between the base stations 108 and the core network 102. Additionally, in some examples, a backhaul network may provide interconnections between the respective base stations 108. Various types of backhaul interfaces may be employed, such as a direct physical (telephone line) connection using any suitable transport network, a wireless connection, a virtual network, etc.
[0050] 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 5G standards (e.g., 5GC). In other examples, the core network 102 may be configured according to 4G Evolved Packet Core (EPC) or any other suitable standard or configuration.
[0051] Reference now Figure 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 similar to that described above and in Figure 1 The geographic area covered by the RAN 200 may be divided into cellular areas (cells), which may be uniquely identified by a user equipment (UE) based on an identity broadcast from an access point or base station. Figure 2 Macro cells 202, 204, and 206 and small cells 208 are shown, each of which may include one or more sectors (not shown). A sector is a sub-area of a cell. All sectors within a cell are served by the same base station. A wireless link within a sector may be identified by a single logical identifier belonging to the sector. In a cell divided into sectors, multiple sectors within a cell may be formed by antenna groups, each of which is responsible for communication with a UE in a portion of the cell.
[0052] exist Figure 2, two base stations 210 and 212 are shown in cells 202 and 204; and a third base station 214 is shown as controlling a remote radio head (RRH) 216 in cell 206. That is, the base station may have an integrated antenna or may be connected to an antenna or RRH by a feeder cable. In the example shown, cells 202, 204, and 206 may be referred to as macro cells because base stations 210, 212, and 214 support cells with large sizes. In addition, base station 218 is shown in a small cell 208 (e.g., a macro cell, a micro cell, a femto cell, a home base station, a home node B, a home eNode B, etc.) that may overlap with one or more macro cells. In this example, cell 208 may be referred to as a small cell because base station 218 supports a cell with a relatively small size. The size of the cell may be determined based on the system design and component constraints.
[0053] It should be understood that the wireless access network 200 may include any number of wireless base stations and cells. In addition, relay nodes may be deployed to extend the size or coverage area of a given cell. Base stations 210, 212, 214, 218 provide wireless access points to the core network for any number of mobile devices. In some examples, base stations 210, 212, 214, and / or 218 may be similar to those described above and in Figure 1 The base stations / scheduling entities 108 shown are identical.
[0054] Within the RAN 200, a cell may include UEs that communicate with one or more sectors of each cell. In addition, each base station 210, 212, 214, and 218 may be configured to provide services to the core network 102 (see FIG. 1 ) for all UEs in the corresponding cell. Figure 1 ) access point. For example, UEs 222 and 224 may communicate with base station 210; UEs 226 and 228 may communicate with base station 212; UEs 230 and 232 may communicate with base station 214 via RRH 216; and UE 234 may communicate with base station 218. In some examples, UEs 222, 224, 226, 228, 230, 232, 234, 238, 240, and / or 242 may communicate with the base stations described above and in Figure 1 The UE / scheduled entity 106 shown in FIG. 1 is the same as that shown in FIG.
[0055] In some examples, unmanned aerial vehicle (UAV) 220 (which may be a drone or a quadcopter) may be a mobile network node and may be configured to function as a UE. For example, UAV 220 may operate within cell 202 by communicating with base station 210.
[0056] In another aspect of RAN 200, sidelink signals can be used between UEs without having to rely on scheduling or control information from a base station. For example, two or more UEs (e.g., UE 226 and 228) can communicate with each other using peer-to-peer (P2P) or sidelink signals 227 without relaying the communication through a base station (e.g., base station 212). In another example, UE 238 is shown as communicating with UE 240 and 242. Here, UE 238 can be used as a scheduling entity or a primary sidelink device, and UE 240 and 242 can be used as a scheduled entity or a non-primary (e.g., auxiliary) sidelink device. In yet another example, a UE can act as a scheduling entity in a device-to-device (D2D), peer-to-peer (P2P) or vehicle-to-vehicle (V2V) network and / or a mesh network. In the mesh network example, in addition to communicating with the scheduling entity 238, UE 240 and 242 can optionally communicate directly with each other. Thus, in a wireless communication system having scheduled access to time-frequency resources and having a cellular configuration, a P2P configuration, or a mesh configuration, a scheduling entity and one or more scheduled entities may communicate using the scheduled resources. In some examples, the sidelink signal 227 includes sidelink traffic and sidelink control.
[0057] The air interface in the wireless access network 200 may utilize one or more multiplexing and multiple access algorithms to enable simultaneous communication of various devices. For example, the 5G NR specification utilizes OFDM with a cyclic prefix (CP) to provide multiple access for UL transmissions from UEs 222 and 224 to the base station 210, and multiplexing for DL transmissions from the base station 210 to one or more UEs 222 and 224. In addition, for UL transmissions, the 5G NR specification provides support for discrete Fourier transform spread OFDM (DFT-s-OFDM) with CP (also referred to as single carrier FDMA (SC-FDMA)). However, within the scope of the present disclosure, multiplexing and multiple access are not limited to the above schemes, and may be provided using time division multiple access (TDMA), code division multiple access (CDMA), frequency division multiple access (FDMA), sparse code multiple access (SCMA), resource extension multiple access (RSMA), or other suitable multiple access schemes. Furthermore, multiplexed DL transmissions from base station 210 to UEs 222 and 224 may be provided using time division multiplexing (TDM), code division multiplexing (CDM), frequency division multiplexing (FDM), OFDM, sparse code multiplexing (SCM), or other suitable multiplexing schemes.
[0058] The air interface in the wireless access network 200 may also utilize one or more duplex algorithms. Duplex refers to a point-to-point communication link in which two endpoints can communicate with each other in two 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 the other endpoint at a time. In a wireless link, a full-duplex channel usually relies on the physical isolation of the transmitter and the receiver, as well as suitable interference elimination techniques. Full-duplex simulation is usually implemented for a wireless link by utilizing frequency division duplex (FDD) or time division duplex (TDD). In FDD, transmissions in different directions operate on different carrier frequencies. In TDD, time division multiplexing is used to separate transmissions in different directions on a given channel. That is, sometimes a channel is dedicated to transmission in one direction, and at other times a channel is dedicated to transmission in another direction, where the direction can change very quickly, for example, several times per time slot.
[0059] In various implementations, the air interface in the wireless access network 200 can utilize licensed spectrum, unlicensed spectrum, or shared spectrum. Licensed spectrum provides exclusive use of a portion of the spectrum, typically by virtue of a mobile network operator purchasing a license from a government regulator. Unlicensed spectrum provides shared use of a portion of the spectrum without the need for a government-granted license. Although it is still generally expected that some technical rules will be met to access the unlicensed spectrum, typically any operator or device can gain access. Shared spectrum may fall between licensed and unlicensed spectrum, where technical rules or restrictions may be required to access the spectrum, but the spectrum can still be shared by multiple operators and / or multiple RATs. For example, the holder of a license for a portion of the licensed spectrum may provide licensed shared access (LSA) to share the spectrum with other parties, for example, using conditions determined by the appropriate licensee to obtain access.
[0060] In some examples, the 5G network (e.g., RAN 200) may also support carrier aggregation of a primary serving cell (PCell) and one or more secondary serving cells (SCells). Each of the PCell and SCell may send the same or different data to the UE. In addition, each SCell in the PCell and SCell may utilize different carrier frequencies (referred to as component carriers), and carrier aggregation may be performed at the UE. The PCell maintains the primary connection with the UE and is responsible for radio resource control (RRC) connection establishment. In addition, physical uplink control channel (PUCCH) transmissions from the UE to the base station occur on the PCell.
[0061] In 5G-NR, carrier aggregation can utilize component carriers in the same frequency band or in different frequency bands. In some examples, carriers can include licensed bands (e.g., 5G, 4G using various licensed bands) and unlicensed bands (e.g., Wi-Fi, using Industrial, Scientific, and Medical (ISM) bands and Unlicensed National Information Infrastructure (U-NII) bands). In some examples, a single radio resource control (RRC) layer can configure carrier aggregation using carriers below 6 GHz and carriers above 6 GHz (such as millimeter wave (mmWave) carriers). For example, a PCell or anchor cell can configure carrier aggregation to offload data traffic to one or more component carriers, each of the one or more component carriers corresponding to an SCell. In some examples, a PCell can use a carrier below 6 GHz, while an SCell can use a carrier above 6 GHz (e.g., a mmWave carrier).
[0062] Various aspects of the present disclosure will be described with reference to OFDM waveforms. Figure 3 Schematically shown in FIG. It will be appreciated by those skilled in the art that various aspects of the present disclosure may be applied to SC-FDMA waveforms in substantially the same manner as described below. That is, while some examples of the present disclosure may focus on OFDM links for clarity, it will be appreciated that the same principles may also be applied to SC-FDMA waveforms.
[0063] Reference now Figure 3 , shows an expanded view of an exemplary DL subframe 302, showing an OFDM resource grid. However, as will be readily appreciated by those skilled in the art, the PHY transmission structure for any particular application may differ from the examples described herein, depending on any number of factors. Here, time is in the horizontal direction, in units of OFDM symbols; and frequency is in the vertical direction, in units of subcarriers.
[0064] Resource grid 304 can be used to schematically represent the time-frequency resources for a given antenna port. That is, in a multiple-input multiple-output (MIMO) implementation with multiple available antenna ports, corresponding multiple resource grids 304 can be used for communication. Resource grid 304 is divided into multiple resource elements (REs) 306. RE (which is 1 subcarrier × 1 symbol) is the smallest discrete part of the time-frequency grid and contains a single complex value representing data or signals from a physical channel. Depending on the modulation used in a specific implementation, each RE can represent one or more information bits. In some examples, a block of REs can be referred to as a physical resource block (PRB) or resource block (RB) 308, which contains any suitable number of consecutive subcarriers in the frequency domain. In one example, an RB can include 12 subcarriers, which is independent of the numerology used. In some examples, depending on the numerology, an RB can include any suitable number of consecutive OFDM symbols in the time domain. In the present disclosure, it is assumed that a single RB such as RB 308 corresponds entirely to a single direction of communication (for transmission or reception of a given device).
[0065] A collection of contiguous or discontinuous resource blocks may be referred to herein as a resource block group (RBG), a subband, or a bandwidth part (BWP). A collection of subbands or BWPs may span the entire bandwidth. Scheduling of a UE for downlink or uplink transmission (scheduled entity) typically involves scheduling one or more resource elements 306 within one or more subbands or bandwidth parts (BWPs). Therefore, a UE typically uses only a subset of a resource grid 304. An RB may be the smallest resource unit that can be allocated to a UE. Therefore, the more RBs scheduled for a UE, and the higher the modulation scheme selected for the air interface, the higher the data rate of the UE.
[0066] In this illustration, RB 308 is shown as occupying less than the entire bandwidth of subframe 302, with some subcarriers shown above and below RB 308. In a given implementation, subframe 302 may have a bandwidth corresponding to any number of one or more RBs 308. Also, in this illustration, RB 308 is shown as occupying less than the entire duration of subframe 302, although this is only one possible example.
[0067] Each 1 ms subframe 302 may include one or more adjacent time slots. Figure 3In the example shown, as an illustrative example, a subframe 302 includes four time slots 310. In some examples, a time slot can be defined according to a specified number of OFDM symbols with a given cyclic prefix (CP) length. For example, a time slot can include 7 or 14 OFDM symbols with a nominal CP. Another example may include a micro-time slot (sometimes referred to as a shortened transmission time interval (TTI)) with a shorter duration (e.g., one to three OFDM symbols). In some cases, these micro-time slots or shortened transmission time intervals (TTIs) may be sent by occupying resources scheduled for ongoing time slot transmissions for the same or different UEs. Any number of resource blocks can be used within a subframe or time slot.
[0068] An expanded view of one of the time slots 310 shows that the time slot 310 includes a control region 312 and a data region 314. In general, the control region 312 may carry control channels, and the data region 314 may carry data channels. Of course, a time slot may contain all DL, all UL, or at least one DL portion and at least one UL portion. Figure 3 The structure shown is merely exemplary in nature and different slot structures may be used and may include one or more of each of the control region and the data region.
[0069] Although in Figure 3 Although not shown in the figure, various REs 306 within the RB 308 may be scheduled to carry one or more physical channels, including control channels, shared channels, data channels, etc. Other REs 306 within the RB 308 may also carry pilot or reference signals, including but not limited to demodulation reference signals (DMRS), control reference signals (CRS), channel state information-reference signals (CSI-RS), or sounding reference signals (SRS). These pilot or reference signals may be provided to a receiving device to perform channel estimation of the corresponding channel, which may enable coherent demodulation / detection of control and / or data channels within the RB 308.
[0070] In DL transmission, the base station may allocate one or more REs 306 (e.g., within the control region 312) to carry DL control information including one or more DL control channels to one or more scheduled entities (such as a physical hybrid automatic repeat request (HARQ) indicator channel (PHICH), a physical downlink control channel (PDCCH), etc.). The PDCCH carries downlink control information (DCI), which includes, but is not limited to, power control commands, scheduling information, grants, and / or assignments of REs for DL and UL transmissions. The PHICH carries HARQ feedback transmissions, such as acknowledgements (ACKs) or negative acknowledgements (NACKs). HARQ is a technique well known to those of ordinary skill in the art, in which the accuracy of the integrity of a packet transmission may be checked at the receiving side, for example, using any suitable integrity check mechanism, such as a checksum or a cyclic redundancy check (CRC). If the integrity of the transmission is confirmed, an ACK may be sent, and if not, a NACK may be sent. In response to the NACK, the transmitting device may send a HARQ retransmission, which may enable append combining, incremental redundancy, etc.
[0071] The base station may also allocate one or more REs 306 to carry other DL signals, such as DMRS; phase tracking reference signal (PT-RS); CSI-RS; primary synchronization signal (PSS); and secondary synchronization signal (SSS). The UE may utilize the PSS and SSS to achieve radio frame, subframe, time slot and symbol synchronization in the time domain, identify the center of the channel (system) bandwidth in the frequency domain, and identify the physical cell identity (PCI) of the cell. The synchronization signals PSS and SSS, and in some examples, PBCH and PBCHDMRS, may be sent in a synchronization signal block (SSB). The PBCH may also include a master information block (MIB), which includes various system information, and parameters for decoding a system information block (SIB). The SIB may be, for example, SystemInformationType 1 (SIB1), which may include various additional system information. Examples of system information sent in the MIB may include, but are not limited to, subcarrier spacing, system frame number, configuration of a PDCCH control resource set (CORESET) (e.g., PDCCH CORESET0), and a search space for SIB1. Examples of additional system information sent in SIB1 may include, but are not limited to, random access search space, common search space list, paging search space, downlink configuration information, and uplink configuration information. MIB and SIB1 together provide minimum system information (SI) for initial access.
[0072] In UL transmission, the UE may utilize one or more REs 306 to carry UL control information including one or more UL control channels to a scheduling entity, such as a physical uplink control channel (PUCCH). The UL control information may include a variety of packet types and categories, including pilots, reference signals, and information configured to enable or assist in decoding uplink data transmissions. In some examples, the control information may include a scheduling request (SR), i.e., a request for a scheduling entity to schedule an uplink transmission. Here, in response to the SR sent on the control channel, the scheduling entity may send downlink control information that may schedule resources for uplink packet transmission. The UL control information may also include HARQ feedback, channel state feedback (CSF), or any other suitable UL control information.
[0073] In addition to control information, one or more REs 306 (e.g., within the data region 314) may be allocated for user data traffic. Such traffic may be carried on one or more traffic channels (e.g., for DL transmissions, a physical downlink shared channel (PDSCH); or for UL transmissions, a physical uplink shared channel (PUSCH)). In some examples, one or more REs 306 within the data region 314 may be configured to carry a SIB (e.g., SIB1) that carries information that may enable access to a given cell.
[0074] These physical channels are typically multiplexed and mapped to transport channels for processing at the medium access control (MAC) layer. Transport channels carry information blocks called transport blocks (TBs). Based on the modulation and coding scheme (MCS) and the number of RBs in a given transmission, the transport block size (TBS), which corresponds to the number of information bits, can be a controlled parameter.
[0075] Combination of the above Figure 1-3 The channels or carriers described are not necessarily all channels or carriers that may be used between a scheduling entity and a scheduled entity, and one of ordinary skill in the art will recognize that other channels or carriers may be used in addition to those shown, such as other traffic, control, and feedback channels.
[0076] In some examples, the scheduling entity and / or the scheduled entity may be configured for beamforming and / or multiple-input multiple-output (MIMO) techniques. Figure 4An example of a wireless communication system 400 supporting MIMO technology is shown. In a MIMO system, a transmitter 402 includes multiple transmit antennas 404 (e.g., N transmit antennas), and a receiver 406 includes multiple receive antennas 408 (e.g., M receive antennas). Therefore, there are NxM signal paths 410 from the transmit antennas 404 to the receive antennas 408. Each of the transmitter 402 and the receiver 406 can be implemented, for example, within a scheduled entity, a scheduling entity, or other suitable wireless communication device.
[0077] The use of such multi-antenna technology enables wireless communication systems to exploit the spatial domain to support spatial multiplexing, beamforming, and transmit diversity. Spatial multiplexing can be used to send different data streams (also called layers) simultaneously on the same time-frequency resources. Data streams can be sent to a single UE to increase the data rate, or to multiple UEs to increase the overall system capacity, the latter of which is called multi-user MIMO (MU-MIMO). This is achieved by spatially precoding each data stream (i.e., multiplying data streams with different weights and phase shifts) and then transmitting each spatially precoded stream through multiple transmit antennas on the downlink. The spatially precoded data streams arrive at UEs with different spatial signatures, which enables each UE in the UE to recover one or more data streams destined for the UE. On the uplink, each UE sends a spatially precoded data stream, which enables the base station to identify the source of each spatially precoded data stream.
[0078] The number of data streams or layers corresponds to the rank of the transmission. Typically, the rank of the MIMO system 400 is limited to the number of transmit antennas 404 or receive antennas 408, whichever is lower. In addition, the channel conditions at the UE and other considerations (such as the available resources at the base station) may also affect the transmission rank. For example, the rank (and therefore the number of data streams) assigned to a particular UE on the downlink can be determined based on a rank indicator (RI) sent from the UE to the base station. The RI can be determined based on the antenna configuration (e.g., the number of transmit antennas and receive antennas) and the measured signal to interference and noise ratio (SINR) on each receive antenna in the receive antenna. The RI can indicate, for example, the number of layers that can be supported under the current channel conditions. The base station can use the RI and resource information (e.g., the available resources and amount of data to be scheduled for the UE) to assign the transmission rank to the UE.
[0079] In one example, if Figure 4 As shown, a rank-2 spatial multiplexing transmission on a 2x2 MIMO antenna configuration will send one data stream from each transmit antenna 404. Each data stream follows a different signal path 410 to each receive antenna 408. The receiver 406 can then reconstruct the data stream using the received signal from each receive antenna 408.
[0080] Beamforming is a signal processing technique that can be used at a transmitter 402 or a receiver 406 to shape or steer an antenna beam (e.g., a transmit beam or a receive beam) along a spatial path between the transmitter 402 and the receiver 406. Beamforming can be achieved by combining signals transmitted via antennas 404 or 408 (e.g., antenna elements of an antenna array module) so that some of the signals experience constructive interference and other signals experience destructive interference. In order to produce the desired constructive / destructive interference, the transmitter 402 or the receiver 406 can apply an amplitude and / or phase offset to the signal transmitted or received from each of the antennas 404 or 408 associated with the transmitter 402 or the receiver 406.
[0081] In 5G-NR systems, especially for systems above 6 GHz or mmWave, beamformed signals can be used for most downlink channels, including the physical downlink control channel (PDCCH) and the physical downlink shared channel (PDSCH). In addition, broadcast control information (such as the master system information block (MSIB), slot format indicator (SFI), and paging information) can be sent in a beam scanning manner so that all scheduled entities (UEs) in the coverage area of the transmit and receive point (TRP) (e.g., gNB) can receive the broadcast control information. In addition, for UEs configured with beamforming antenna arrays, beamformed signals can also be used for uplink channels, including the physical uplink control channel (PUCCH) and the physical uplink shared channel (PUSCH). However, it should be understood that enhanced mobile broadband (eMBB) gNBs can also use beamformed signals for systems below 6 GHz.
[0082] Figure 5 is a diagram illustrating communication between a base station (BS) 504 (such as a gNB) and a UE 502 using beamformed signals according to some aspects of the present disclosure. The base station 504 may be Figure 1 and / or Figure 2 Any of the base stations or scheduling entities shown in , and UE 502 may be Figure 1 and / or Figure 2 Any of the UEs or scheduled entities shown in .
[0083] exist Figure 5In the example shown, the base station 504 is configured to generate multiple beams 506a-506h, each beam being associated with a different beam direction. In addition, the UE 502 is configured to generate multiple beams 508a-508e, each beam being associated with a different beam direction. The base station 504 and the UE 502 may select one or more beams 506a-506h on the base station 504 and one or more beams 508a-508e on the UE 502 for transmission of uplink and downlink signals therebetween.
[0084] In an example, the base station 504 may be configured to scan or transmit on each of the multiple downlink beams 506a-506h during one or more synchronization slots. For example, the base station 504 may transmit a reference signal, such as an SSB or CSI-RS, on each beam in different beam directions during the synchronization slot. The transmission of the beam reference signal may occur periodically (e.g., as configured by the gNB via radio resource control (RRC) signaling), semi-persistently (e.g., as configured by the gNB via RRC signaling and activated / deactivated via medium access control-control element (MAC-CE) signaling), or aperiodically (e.g., triggered by the gNB via downlink control information (DCI)). It should be noted that while some beams are shown as being adjacent to each other, such an arrangement may be different in different aspects. For example, the downlink beams 506a-506h transmitted during the same symbol may not be adjacent to each other. In some examples, the base station 504 may transmit more or fewer beams distributed in all directions (e.g., 360 degrees).
[0085] In addition, the UE 502 is configured to receive downlink beam reference signals on multiple uplink beams 508a-508e. In some examples, the UE 502 searches for and identifies each of the downlink beams 506a-506h based on the beam reference signals. The UE 502 then performs beam measurements (e.g., reference signal received power (RSRP), SINR, reference signal received quality (RSRQ), etc.) on the beam reference signals to determine the corresponding beam quality of each of the downlink beams 506a-506h as measured on each of the uplink beams 508a-508e.
[0086] The UE 502 may then send a beam measurement report (e.g., a layer 1 (L1) measurement report) including corresponding beam identifiers (e.g., beam indices) and beam measurements (e.g., RSRP) for one or more of the downlink beams 506a-506h to the base station 504. The base station 504 may then select one or more downlink beams on which to send unicast downlink control information and / or user data traffic to the UE 502. In some examples, the selected downlink beam has the highest gain from the L1 measurement report. In some examples, the UE 502 may also identify the downlink beam selected by the base station from the beam measurements. The transmission of the L1 measurement report may occur periodically (e.g., as configured by the gNB via RRC signaling), semi-persistently (e.g., as configured by the gNB via RRC signaling and activated / deactivated via MAC-CE signaling), or aperiodically (e.g., as triggered by the gNB via DCI).
[0087] The base station 504 or UE 502 may also select a corresponding uplink beam on the UE 502 for each selected serving downlink beam to form a corresponding downlink beam pair link (BPL) for each selected serving downlink beam. For example, the UE 502 may utilize beam measurements to select a corresponding uplink beam for each serving downlink beam. In some examples, the selected uplink beam paired with a particular downlink beam may have the highest gain for the particular downlink beam.
[0088] In other examples, when the channel is reciprocal (e.g., the downlink and uplink channel qualities are the same), the base station 504 can derive the downlink beam. The derivation of the downlink beam can be based on uplink measurements performed by the base station 504, such as by measuring the received power, quality, or other variables on multiple base station beams 506a-506h of a sounding reference signal (SRS) or other uplink reference signal sent by the wireless communication device 502 on one or more of the uplink beams 508a-508e. In some examples, the base station 504 can derive the downlink beam based on a combination of L1 measurement reports and uplink measurements.
[0089] In addition to MIMO and beamforming technologies, 5G-NR networks can also support carrier aggregation of component carriers transmitted from different transmit and receive points (TRPs) in a multi-cell transmission environment. Figure 6An example of a multi-cell transmission environment 600 is shown in FIG. The multi-cell transmission environment 600 includes a primary serving cell (PCell) 602 and one or more secondary serving cells (SCells) 606a, 606b, 606c, and 606d. PCell 602 may be referred to as an anchor cell that provides a radio resource control (RRC) connection to a UE. In some examples, the PCell and one or more SCells may be co-located (e.g., different transmit receive points (TRPs) may be in the same location).
[0090] When carrier aggregation is configured, one or more of the SCells 606a-606d may be activated or added to the PCell 602 to form a serving cell serving the user equipment (UE) 610. Each serving cell corresponds to a component carrier (CC). The CC of the PCell 602 may be referred to as a primary CC, and the CC of the SCell 606a-606d may be referred to as a secondary CC. The PCell 602 and one or more of the SCells 606 may be served by corresponding TRPs 604 and 608a-608c. Each TRP 604 and 608a-608c may be a base station (e.g., a gNB), a remote radio head of a gNB, or a remote radio head associated with the gNB. Figure 1 , Figure 2 , Figure 4 and Figure 5 Other scheduling entities similar to those shown in any of the figures in . In some examples, a base station (e.g., base station 504) can include multiple TRPs, each TRP corresponding to one of multiple co-located antenna arrays, each antenna array supporting a different carrier. Figure 6 In the example shown, SCells 606a-606c are each served by a corresponding base station 608a-608c. In addition, SCell 606d and PCell 602 are co-located and served by a single base station 604. The coverage of PCell 602 and SCell 606d may be different because component carriers in different frequency bands may experience different path losses.
[0091] The PCell 602 may add or remove one or more of the SCells 606a-606d to improve reliability and / or increase data rates for connections to the UE 610. However, the PCell 602 may only change when switching to another PCell.
[0092] In some examples, PCell 602 may utilize a first radio access technology (RAT) (such as LTE), and one or more SCells 606 in SCell 606 may utilize a second RAT (such as 5G-NR). In this example, the multi-cell transmission environment may be referred to as a multi-RAT-dual connection (MR-DC) environment. In some examples, PCell 602 may be a low-band cell, and SCell 606 may be a high-band cell. A low-band (LB) cell uses a CC in a frequency band lower than that of a high-band cell. For example, a high-band cell may use a mmWave CC, and a low-band cell may use a CC in a frequency band lower than mmWave (e.g., lower than a 6 GHz band). Typically, a cell using mmWave CCs may provide a larger bandwidth than a cell using low-band CCs. In addition, when using a carrier with a frequency higher than 6 GHz (e.g., mmWave), beamforming may be used to send and receive signals.
[0093] The PCell 602 is responsible not only for connection establishment, but also for radio resource management (RRM) and radio link monitoring (RLM) of the connection with the UE 610. For example, the PCell 602 can activate one or more SCells (e.g., SCell 606a) for multi-cell communication with the UE 610. In some examples, when the SCell 606a is not used for data transmission / reception, the PCell can activate the SCell 606a on an on-demand basis instead of maintaining the SCell activation in order to reduce the power consumption of the UE 610. However, there is a delay involved in activating the SCell 606a, which is mainly due to the time involved in the time / frequency synchronization between the UE 610 and the SCell 606a. For example, in order to synchronize the UE 610 with the SCell 606a, the UE 610 and / or the SCell 606a can measure or otherwise utilize one or more reference signals transmitted between the UE 610 and the SCell 606a. Examples of reference signals may include, but are not limited to, aperiodic or semi-persistent downlink CSI-RS, downlink synchronization signal blocks (SSBs), and / or uplink SRS.
[0094] In some examples, in order to minimize the time involved in synchronizing with the SCell 606a during SCell activation, the SCell 606a may continuously send reference signals with high periodicity. However, this may increase the overhead in the SCell 606a. In various aspects of the present disclosure, the PCell 602 may trigger the transmission of one or more reference signals between the UE 610 and the SCell 606a on demand to enable the UE 610 to synchronize with the SCell 606a in a reduced time while also minimizing the overhead in the SCell 606a.
[0095] Figure 7 is a diagram showing exemplary signaling for activating communication with SCell 706 in a multi-cell transmission environment. Figure 7 In the example shown, UE 702 is in connected mode with PCell 704. Each of PCell 704 and SCell 706 is served by a corresponding scheduling entity (e.g., a base station). The scheduling entity may be Figure 1 , Figure 2 , Figure 5 and Figure 6 Any of the base stations or other scheduling entities shown in , and UE 702 may be Figure 1 , Figure 2 , Figure 5 and Figure 6 Any of the UEs or scheduled entities shown in .
[0096] In 5G-NR, control and data may be transmitted between UE 702 and each of PCell 704 and SCell 706 via one or more TRPs over multiple different beams / paths, each beam / path having a different spatial relationship with the other beams / paths. At 708, during activation of SCell 706, SCell 706 may pre-configure each of the reference signals to be transmitted between UE 702 and SCell 706. For example, SCell 706 may pre-configure each of the reference signals to have a specific time-frequency resource and a specific beam / path, and provide configuration information for each of the reference signals to UE 702 via, for example, RRC signaling during an initial access procedure of the UE with SCell 706.
[0097] In some examples, the configuration information may include a transmission configuration indicator (TCI) state (e.g., for a downlink reference signal) or a spatial relationship indicator (SRI) (e.g., for an uplink reference signal) indicating quasi co-location (QCL) information (e.g., QCL type and time-frequency resource) of the reference signal. Examples of QCL types may include one or more of Doppler shift, Doppler spread, average delay, delay spread, and spatial RX parameters (e.g., spatial beam). In some examples, each of the reference signals may be pre-configured with the same or different TCI state (e.g., for a downlink reference signal) or SRI (e.g., for an uplink reference signal) relative to the spatial beam or BPL on which the reference signal is transmitted. Thus, each of the reference signals may be transmitted on the same or different beams or BPLs. In addition, one or more of the downlink reference signals may be sent from different transmit receive points (TRPs) associated with the SCell or associated with another cell co-located with the TRP of the SCell. In this example, the TCI status may include a TRP identity (ID) or an equivalent cell ID.
[0098] At 710, the PCell 704 may determine to activate the SCell 706 for multi-cell communication and send a reference signal trigger to the UE 702 for identifying one or more of the reference signals to be transmitted with the SCell 706. For example, the PCell 704 may receive an activation message from the UE 702 to activate communication with the SCell 706. As another example, the PCell 704 may decide to activate communication between the UE 702 and the SCell 706 to provide a higher data rate to the UE 702. In some examples, the PCell 704 may select one or more of the reference signals preconfigured by the SCell 706 for activating the SCell 706 and send an identifier of each of the selected reference signals in the reference signal trigger. The reference signal trigger may be included, for example, within a medium access control-control element (MAC-CE) of a physical downlink control channel (PDCCH). At 712, the PCell 704 may also send a reference signal message to the SCell 706, for example, by backhaul signaling via a wired or wireless connection, the reference signal message including an indication of one or more reference signals identified in the reference signal trigger.
[0099] At 714, one or more reference signals identified in the reference signal trigger may be transmitted between the UE 702 and the SCell 706. Examples of reference signals may include aperiodic or semi-persistent CSI-RS, synchronization signal blocks (SSBs), and / or uplink SRSs. For example, the SCell 706 may schedule resources for transmitting aperiodic downlink reference signals (e.g., CSI-RSs) based on corresponding TCI states, or utilize semi-persistently scheduled resources to send downlink reference signals (e.g., CSI-RSs) based on corresponding TCI states. The SCell 706 may also send SSBs according to the periodicity set for the SSBs in the SCell. In addition, the SCell 706 may receive an uplink sounding reference signal (SRS) from the UE 702 on pre-configured (e.g., semi-persistently scheduled) uplink resources. For example, the SCell 706 may receive the SRS based on an SRI (e.g., one or more beams) defined for the SRS. In some examples, each of the reference signals may be transmitted using the same TCI state or SRI (e.g., on the same beam or BPL). In other examples, one or more of the reference signals may be transmitted using different TCI states or SRI (e.g., via different beams or BPLs). In addition, one or more of the reference signals may be repeated in a beam scanning manner across multiple beams.
[0100] At 716, the UE 702 may utilize one or more reference signals to synchronize with the SCell 706. For example, the UE 702 may utilize the SSB for time / frequency synchronization with the SCell 706 and derive frame information in the SCell 706. The UE 702 may also measure the CSI-RS for time / frequency tracking. In some examples, the UE 702 may also provide channel state feedback (CSF) to the SCell 706 based on the CSI-RS measurement to enable the SCell 706 to select a modulation and coding scheme (MCS) for downlink communication with the UE 702. On the uplink, the SCell 706 may measure the SRS sent by the UE 702 to obtain channel state information and further enable the UE to synchronize with the SCell 706. For example, the SRS may be sent on multiple beams, and the SCell 706 may measure the SRS on each of the receive beams to obtain time and frequency synchronization for the UE 702. The SCell 706 may then send time / frequency synchronization information to the UE 702 to enable the UE 702 to synchronize with the SCell 706 .
[0101] At 718, UE 702 may send confirmation information to SCell 706 for confirming receipt of a MAC-CE including a reference signal trigger. For example, the confirmation information may include an ACK or a NACK, and the timing of the ACK / NACK transmission may be defined based on the transmission timing of the triggered reference signal. In addition, the ACK / NACK spatial relationship may be linked to the TCI state of the triggered reference signal. In an example where the reference signal is transmitted using different TCI states (e.g., via different beams), UE 702 may send confirmation information in a beam scanning manner across one or more beams in the beams used for the reference signal. In some examples, the UE may send an ACK / NACK for the MAC-CE within a beam-scanned physical uplink control channel (PUCCH), with a one-to-one mapping between the PUCCH beam and the TCI state (e.g., downlink beam spatial direction) for each reference signal in the triggered reference signal. In this example, ACK / NACK is sent on each beam in the beam corresponding to each reference signal in the reference signal triggered by the MAC-CE.
[0102] In other examples, the UE 702 may select a subset of triggered reference signals for measurement (e.g., for synchronization) and send an ACK / NACK for the MAC-CE within the beam-scanned PUCCH, with a one-to-one mapping between the PUCCH beams and TCI states (e.g., spatial directions) of the subset of triggered reference signals. In this example, the subset of triggered reference signals may be selected by the UE 702 based on one or more metrics. For example, the UE 702 may select a subset of triggered reference signals based on the TCI state (e.g., beam) used to transmit each of the triggered reference signals.
[0103] In some examples, SCell 706 can select a serving beam pair link (BPL) for UE 702 based on different receive beams carrying acknowledgment information. For example, SCell 706 can measure the signal-to-interference-plus-noise ratio (SINR) on each ACK / NACK beam in the ACK / NACK beam to identify the serving BPL for UE 702.
[0104] In the example where the UE 702 sends an uplink SRS to the SCell (e.g., at 714), at 716 / 718, instead of the UE 702 sending an ACK / NACK, the SCell 706 may send an ACK / NACK to the UE 702 on each of the downlink beams corresponding to the SRI of the SRS (e.g., each of the downlink beams has the same spatial direction as the uplink beam used to send the SRS). In this example, the ACK / NACK may also include time / frequency synchronization information to enable the UE 702 to synchronize with the SCell 706. The ACK / NACK indicates confirmation information for the MAC-CE by confirming the reception of the SRS based on the MAC-CE SRS trigger.
[0105] At 720, the SCell 706 may also provide acknowledgement information (ACK / NACK) to the PCell 704 via, for example, a backhaul link. In the example of receiving an ACK / NACK from the UE 702 (e.g., at 718), the SCell 706 may forward the ACK / NACK to the PCell 704. In the example of sending an ACK / NACK from the SCell 706 to the UE 702 (e.g., in response to an SRS), the SCell 706 may also send an ACK / NACK to the PCell 704.
[0106] Figure 8 814 is a conceptual diagram illustrating an example of a hardware implementation of an exemplary scheduling entity 800 employing a processing system 814. For example, the scheduling entity 800 may be such as Figure 1 , Figure 2 and Figure 5-Figure 7 In some examples, the scheduling entity 800 may serve a PCell or a SCell for multi-cell communication with a UE.
[0107] The scheduling entity 800 may be implemented with a processing system 814 including one or more processors 804. Examples of processors 804 include microprocessors, microcontrollers, digital signal processors (DSPs), field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform various functions described throughout the present disclosure. In various examples, the scheduling entity 800 may be configured to perform any one or more of the functions described herein. That is, the processor 804 as used in the scheduling entity 800 may be used to implement any one or more of the following processes. The processor 804 may be implemented via a baseband or modem chip in some cases, while in other implementations, the processor 804 itself may include several devices that are different and distinct from the baseband or modem chip (e.g., in such a scenario, may work together to implement the embodiments discussed herein). And as mentioned above, various hardware arrangements and components outside the baseband modem processor may be used in implementations, including RF chains, power amplifiers, modulators, buffers, interleavers, adders / summers, etc.
[0108] In this example, the processing system 814 may be implemented with a bus architecture (generally represented by bus 802). Bus 802 may include any number of interconnecting buses and bridges, depending on the specific application and overall design constraints of the processing system 814. Bus 802 communicatively couples together various circuits including one or more processors (generally represented by processor 804), memory 805, and computer readable media (generally represented by computer readable media 806). Bus 802 may also link various other circuits, such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further.
[0109] The bus interface 808 provides an interface between the bus 802, the transceiver 810, and the antenna array 830. The transceiver 810 provides a unit for communicating with various other devices via a transmission medium (e.g., an air interface). The antenna array 830 provides a unit for digital and / or analog beamforming using, for example, the transceiver 810. In some examples, the scheduling entity 800 may include a plurality of transceivers 810 and antenna arrays 830, each of which is associated with a TRP of the scheduling entity 800. Depending on the nature of the device, a user interface 812 (e.g., a keypad, a display, a speaker, a microphone, a joystick) may also be provided. Of course, such a user interface 812 is optional and may be omitted in some examples, such as a base station.
[0110] The processor 804 is responsible for managing the bus 802 and general processing, which includes the execution of software stored on the computer-readable medium 806. The software, when executed by the processor 804, causes the processing system 814 to perform the various functions described below for any particular device. The computer-readable medium 806 and memory 805 may also be used to store data that is manipulated by the processor 804 when executing the software.
[0111] One or more processors 804 in the processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise, software should be construed broadly to mean instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc. The software may reside on a computer-readable medium 806.
[0112] Computer readable medium 806 can be a non-transitory computer readable medium. Non-transitory computer readable media include, for example, magnetic storage devices (e.g., hard disks, floppy disks, magnetic strips), optical disks (e.g., compact disks (CDs) or digital versatile disks (DVDs)), smart cards, flash memory devices (e.g., cards, sticks or key drives), random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), registers, removable disks, and any other suitable medium for storing software and / or instructions that can be accessed and read by a computer. Computer readable media can also include, for example, carrier waves, transmission lines, and any other suitable medium for sending software and / or instructions that can be accessed and read by a computer. Computer readable medium 806 can reside in processing system 814, outside processing system 814, or distributed on multiple entities including processing system 814. Computer readable medium 806 can be embodied in a computer program product. By way of example, a computer program product can include a computer readable medium in a packaging material. Those skilled in the art will recognize how best to implement the described functionality presented throughout this disclosure depending on the particular application and the overall design constraints imposed on the overall system.
[0113] In some aspects of the present disclosure, the processor 804 may include circuits configured for various functions. For example, the processor 804 may include a multi-cell management circuit 841 configured to facilitate a multi-cell transmission environment for one or more scheduled entities (UEs). In some examples, the scheduling entity 800 may serve a PCell, and the multi-cell management circuit 841 may be configured to add one or more SCells (each SCell utilizing a different carrier) as a serving cell to provide a multi-cell transmission environment for a specific scheduled entity (e.g., UE). For example, the multi-cell management circuit 841 may be configured to determine to activate communication between the scheduled entity and the SCell for multi-cell communication. The scheduling entity 800 may receive an activation message from the scheduled entity to activate the SCell for multi-cell communication, or the multi-cell management circuit 841 may decide to activate communication between the scheduled entity and the SCell to provide a higher data rate to the scheduled entity.
[0114] The multi-cell management circuit 841 may also be configured to send a reference signal trigger to the scheduled entity when determining to activate the SCell so as to trigger the transmission of one or more reference signals between the scheduled entity and the SCell so that the scheduled entity can be synchronized with the SCell. In some examples, the reference signal trigger identifies one or more reference signals among multiple reference signals that are configured to be sent or received by the scheduled entity in the SCell. In some examples, the multi-cell management circuit 841 may select one or more reference signals from multiple reference signals. In this example, one or more selected reference signals include a subset of multiple reference signals. The multi-cell management circuit 841 may also be configured to send a reference signal message to the SCell including an indication of one or more reference signals identified in the reference signal trigger. The reference signal may be sent to the SCell via, for example, a backhaul interface (e.g., a wired or wireless connection).
[0115] In some examples, the multi-cell management circuit 841 can be configured to send a MAC-CE including a reference signal trigger to the scheduled entity within the PDSCH. The multi-cell management circuit 841 can also be configured to receive confirmation information (e.g., ACK / NACK) from the SCell to confirm that the MAC-CE is received by the scheduled entity.
[0116] In some examples, the scheduling entity 800 may serve the SCell, and the multi-cell management circuit 841 may be configured to enable the scheduled entity to synchronize with the SCell to activate multi-cell communication with the PCell and the SCell for the scheduled entity. In this example, the multi-cell management circuit 841 may be configured to receive a reference signal message from the PCell, indicating that one or more reference signals identified in the reference signal trigger are transmitted to the scheduled entity. The one or more reference signals may include, but are not limited to, CSI-RS, SSB, or SRS. The multi-cell management circuit 841 may also be configured to receive ACK / NACK from the scheduled entity in response to the transmission of one or more downlink reference signals and provide the ACK / NACK to the PCell. The multi-cell management circuit 841 may also be configured to provide ACK / NACK to the scheduled entity in response to receiving one or more uplink reference signals, and further provide ACK / NACK to the PCell. In some examples, each of the PCell and the SCell uses a different RAT (e.g., LTE and 5G-NR).
[0117] After activating the SCell, the multi-cell management circuit 841 may also be configured to coordinate other downlink and uplink transmissions with the scheduled entity via a backhaul interface connection or other connection between the PCell and the SCell. The multi-cell management circuit 841 may also be configured to execute multi-cell software 851 stored on the computer-readable medium 806 to implement one or more functions described herein.
[0118] Processor 804 may also include resource assignment and scheduling circuit 842, which is configured to generate, schedule and modify resource assignments or grants of time-frequency resources (e.g., a set of one or more resource elements). For example, resource assignment and scheduling circuit 842 may schedule time-frequency resources within multiple TDD and / or FDD subframes, time slots and / or mini-slots to carry user data traffic and / or control information to and / or from multiple UEs (scheduled entities). In some examples, resource assignment and scheduling circuit 842 may operate in conjunction with multi-cell management circuit 841 to schedule multi-cell transmissions to and / or from scheduled entities.
[0119] In the example where the scheduling entity 800 serves a PCell, the resource assignment and scheduling circuit 842 may also be configured to schedule resources for transmitting a reference signal trigger (e.g., MAC-CE) to the scheduled entity. The resource assignment and scheduling circuit 842 may also be configured to schedule resources for transmitting a reference signal message to the SCell when communicating with the SCell via a wireless backhaul link. In addition, the resource assignment and scheduling circuit 842 may be configured to schedule resources for transmitting confirmation information from the SCell to the PCell via a wireless backhaul link.
[0120] In an example where the scheduling entity 800 serves the SCell, the resource assignment and scheduling circuit 842 may be configured to schedule resources (non-periodic, semi-persistent, or with a predetermined period) for transmitting one or more reference signals indicated in a reference signal message. For example, the resource assignment and scheduling circuit 842 may be configured to pre-configure each reference signal in the reference signal with a specific time-frequency resource and a specific beam / path. In some examples, the configuration information may include a TCI state or a spatial relationship indicator (SRI) indicating a spatial beam or BPL on which the reference signal is transmitted. In some examples, each reference signal in the reference signal may be transmitted on the same or different beams or BPLs. In addition, one or more downlink reference signals may be transmitted from different TRPs associated with the SCell. In this example, the TCI state may include a TRP identity (ID) or an equivalent cell ID.
[0121] The resource assignment and scheduling circuit 842 may also be configured to schedule resources for transmitting confirmation information from the scheduled entity to the SCell (e.g., in response to the scheduled entity receiving one or more downlink reference signals) or from the SCell to the scheduled entity (e.g., in response to receiving one or more uplink reference signals from the scheduled entity). The resource assignment and scheduling circuit 842 may also be configured to execute resource assignment and scheduling software 852 stored on the computer-readable medium 806 to implement one or more functions described herein.
[0122] The processor 804 may also include a communication and processing circuit 843, which is configured to communicate with one or more scheduled entities (e.g., UE) and one or more other cells in a multi-cell environment. The communication and processing circuit 843 may include one or more hardware components that provide a physical structure for performing wireless communication (e.g., signal reception and / or signal transmission) and signal processing (e.g., processing received signals and / or processing signals for transmission). For example, the communication and processing circuit 843 may be configured to generate and send downlink user data services and downlink control channels in one or more subframes, time slots and / or small slots according to resources assigned to downlink user data services and / or downlink control information by resource assignment and scheduling circuit 842. In addition, the communication and processing circuit 843 may be configured to receive and process uplink user data services and uplink control channels in one or more subframes, time slots and / or small slots according to resources assigned to uplink user data services and / or uplink control information by resource assignment and scheduling circuit 842.
[0123] In the example where the scheduling entity 800 serves the PCell, the communication and processing circuit 843 can be configured to operate with the multi-cell management circuit 841 to generate and send a reference signal trigger (e.g., MAC-CE) to the scheduled entity and to generate and send a reference signal message to the SCell. In addition, the communication and processing signal can also be configured to receive confirmation information from the SCell and provide the confirmation information to the multi-cell management circuit 841. The communication and processing circuit 843 can also be configured to receive an activation message from the scheduled entity to activate the SCell for multi-cell communication and provide the activation message to the multi-cell management circuit 841.
[0124] In an example where the scheduling entity 800 serves the SCell, the communication and processing circuit 843 may be configured to receive a reference signal message from the PCell and provide the reference signal message to the multi-cell management circuit 841. The communication and processing circuit 843 may also be configured to transmit one or more reference signals with the scheduled entity to enable the scheduled entity to be synchronized with the SCell. For example, the communication and processing circuit 843 may be configured to generate and send SSB or CSI-RS on one or more beams via one or more TRPs in the SCell using the antenna array 830 and the transceiver 810 for use by the scheduled entity synchronized with the SCell. As another example, the communication and processing circuit 843 may be configured to receive SRS from the scheduled entity on one or more beams using the antenna array 830 and the transceiver 810. In addition, the communication and processing circuit 843 may be configured to provide configuration information of each reference signal in the reference signal to the scheduled entity via, for example, RRC signaling during the initial access process.
[0125] In some examples, the communication and processing circuit 843 may be configured to receive confirmation information (e.g., one or more ACK / NACKs, each on a separate beam) confirming receipt of a MAC-CE including a reference signal trigger, and provide the confirmation information to the multi-cell management circuit 841. The communication and processing circuit 843 may also be configured to operate with the multi-cell management circuit 841 to send confirmation information to the PCell.
[0126] In some examples, the spatial relationship of the received ACK / NACK can be related to the TCI state of the triggered reference signal. In examples where the reference signal is transmitted using different TCI states (e.g., via different beams), the communication and processing circuit 843 can receive confirmation information on one or more beams used for the downlink reference signal. In some examples, confirmation information can be received on each of the beams corresponding to each of the reference signals triggered by the reference signal trigger. In other examples, confirmation information can be received on a subset of beams corresponding to the triggered reference signal.
[0127] In an example where the communication and processing circuit 843 receives an uplink SRS from a scheduled entity instead of receiving confirmation information from the scheduled entity, the communication and processing circuit 843 may transmit an ACK / NACK to the scheduled entity on each of the beams on which the SRS is received to confirm the reception of the scheduled entity of the MAC-CE (e.g., as a result of receiving the SRS). In this example, the communication and processing circuit 843 may also generate and send time / frequency synchronization information and confirmation information to enable the scheduled entity to synchronize with the SCell. The communication and processing circuit 843 may distinguish the time / frequency synchronization information by measuring the received SRS. The communication and processing circuit 843 may also be configured to execute the communication and processing software 853 stored on the computer-readable medium 806 to implement one or more functions described herein.
[0128] The processor 804 may also include a beam selection circuit 844 configured to select a service beam pair link (BPL) between the SCell and the scheduled entity based on different receive beams carrying confirmation information. For example, the beam selection circuit 844 may measure a signal to interference noise ratio (SINR) on each ACK / NACK beam in the ACK / NACK beam to identify the service BPL of the scheduled entity. The beam selection circuit 844 may also be configured to execute beam selection software 854 stored on the computer-readable medium 806 to implement one or more functions described herein.
[0129] Fig. 9904. Figure 1 , 2 and any one or more of the user equipment (UE) shown in 5-7.
[0130] The processing system 914 can be used with Figure 8 The processing system 814 shown is substantially the same, including a bus interface 908, a bus 902, a memory 905, a processor 904, and a computer readable medium 906. In addition, the scheduled entity 900 may include a computer readable medium similar to the computer readable medium 906. Figure 8 The user interface 912, transceiver 910 and antenna array 930 of those described. That is, as used in the scheduled entity 900, the processor 904 may be used to implement any one or more of the processes described below.
[0131] In some aspects of the present disclosure, the processor 904 may include a multi-cell management circuit 941 configured to facilitate simultaneous communication with one or more PCells and one or more SCells in a multi-cell transmission environment. In some examples, when in a connected mode with a PCell, the multi-cell management circuit 941 may determine that the SCell should be activated to facilitate multi-cell communication. In this example, the multi-cell management circuit 941 may be configured to transmit an activation message to the PCell to activate the SCell for multi-cell communication with the scheduled entity 900.
[0132] The multi-cell management circuit 941 may also be configured to receive a reference signal trigger (e.g., within a MAC-CE) for triggering communication of one or more reference signals between the scheduled entity 900 and the SCell. The reference signal trigger may identify one or more reference signals of a plurality of reference signals configured to be used by the scheduled entity 900 in the SCell. The multi-cell management circuit 941 may also be configured to synchronize with the SCell based on the one or more reference signals to activate the SCell.
[0133] In some examples, the multi-cell management circuit 941 may be configured to receive one or more downlink reference signals (e.g., CSI-RS or SSB) identified in the reference signal trigger via one or more beams according to beam information 915 (e.g., TCI state) of each downlink reference signal in the downlink reference signal. The beam information 915 may be received, for example, during initial access and stored in the memory 905. The multi-cell management circuit 941 may then be configured to perform time / frequency synchronization with the SCell using the one or more downlink reference signals. In some examples, the multi-cell management circuit 941 may be configured to transmit an uplink reference signal (e.g., SRS) to the SCell in response to a reference signal trigger via one or more beams according to beam information 915 (e.g., SRI) of the uplink reference signal, so that the SCell can determine time / frequency synchronization information for the scheduled entity 900. In this example, the multi-cell management circuit 941 may also be configured to receive time / frequency synchronization information from the SCell.
[0134] The multi-cell management circuit 941 may also be configured to send confirmation information (e.g., ACK / NACK) to the SCell for confirming receipt of the MAC-CE carrying the reference signal trigger. The timing of the ACK / NACK transmission may be defined based on the transmission timing of the triggered downlink reference signal. In addition, the ACK / NACK spatial relationship may be related to the TCI state 915 of the triggered downlink reference signal. For example, the ACK / NACK transmission may be repeated on an uplink beam having the same spatial direction as the triggered downlink reference signal.
[0135] In an example where a downlink reference signal is transmitted using different TCI states (e.g., via different beams), the multi-cell management circuit 941 may send confirmation information in a beam scanning manner across one or more beams used to receive the downlink reference signal. In some examples, the multi-cell management circuit 941 may send ACK / NACK for MAC-CE in a beam scanning physical uplink control channel (PUCCH), with a one-to-one mapping between the PUCCH beam and the TCI state (e.g., spatial direction) of each triggered downlink reference signal. In this example, ACK / NACK is sent on each beam in the beam corresponding to each reference signal in the reference signal triggered by MAC-CE. In other examples, the multi-cell management circuit 941 may select a subset of the triggered reference signals for measurement (e.g., for synchronization), and transmit ACK / NACK for MAC-CE in a beam scanning PUCCH, with a one-to-one mapping between the PUCCH beam and the TCI state (e.g., spatial direction) of the triggered reference signal. In this example, the subset of triggered reference signals may be selected by the multi-cell management circuit 941 based on one or more metrics.
[0136] In an example where a reference signal trigger triggers communication of an uplink reference signal (e.g., SRS), the multi-cell management circuit 941 may not transmit an ACK / NACK to the SCell, but may receive an ACK / NACK from the SCell in response to receiving the SRS at the SCell. For example, the multi-cell management circuit 941 may receive an ACK / NACK from the SCell on each of the beams corresponding to the SRI of the SRS. In this example, the ACK / NACK may also include time / frequency synchronization information to enable the multi-cell management circuit 941 to synchronize with the SCell. The multi-cell management circuit 941 may also be configured to execute multi-cell management software 951 stored on the computer-readable medium 906 to implement one or more of the functions described herein.
[0137] The processor 904 may also include a communication and processing circuit 942, which is configured to communicate with one or more scheduling entities (e.g., a base station serving a PCell and one or more SCells) in a multi-cell environment. The communication and processing circuit 942 may include one or more hardware components that provide a physical structure for performing wireless communication (e.g., signal reception and / or signal transmission) and signal processing (e.g., processing received signals and / or processing signals for transmission). For example, the communication and processing circuit 942 may be configured to generate and send uplink user data services and uplink control channels in one or more subframes, time slots, and / or mini-slots according to resources assigned by the PCell or SCell to uplink user data services and / or uplink control information. In addition, the communication and processing circuit 942 may be configured to receive and process downlink user data services and downlink control channels in one or more subframes, time slots, and / or mini-slots according to resources assigned by the PCell or SCell to downlink user data services and / or downlink control information.
[0138] In some examples, the communication and processing circuitry 942 may be configured to receive a reference signal trigger (e.g., MAC-CE) from the PCell and provide the reference signal trigger to the multi-cell management circuitry 941. In addition, the communication and processing circuitry 942 may be configured to operate with the multi-cell management circuitry 941 to generate and send an activation message to activate the SCell for multi-cell communication.
[0139] The communication and processing circuit 942 may also be configured to receive and process one or more downlink reference signals (e.g., CSI-RS and / or SSB) identified in a reference signal trigger on one or more beams based on beam information 915 (e.g., TCI state) of the downlink reference signal to enable the multi-cell management circuit 941 to synchronize with the SCell. In addition, the communication and processing circuit 942 may be configured to operate with the multi-cell management circuit 941 to generate and send an uplink reference signal (e.g., SRS) identified in a reference signal trigger based on beam information 915 (e.g., SRI) associated with the uplink reference signal.
[0140] The communication and processing circuit 942 may also be configured to operate with the multi-cell management circuit 941 to generate and send confirmation information to the SCell on one or more beams (e.g., as selected by the multi-cell management circuit 941) for downlink reference signals. In addition, the communication and processing circuit 942 may be configured to receive and process confirmation information from the SCell on one or more beams for uplink reference signals. In this example, the communication and processing circuit 942 may also be configured to receive time / frequency synchronization information and confirmation information from the SCell, and provide the time / frequency synchronization information to the multi-cell management circuit 941 for synchronization with the SCell. The communication and processing circuit 942 may also be configured to execute communication and processing software 952 stored on the computer-readable medium 906 to implement one or more functions described herein.
[0141] The processor 904 may also include a beam selection circuit 943 configured to measure the SINR or reference signal received power (RSRP) on each ACK / NACK beam in the ACK / NACK beams received from the SCell, and select a serving beam pair link (BPL) between the SCell and the scheduled entity 900 based on the measured beam. In some examples, the beam selection circuit 943 may also be configured to send a beam measurement report to the SCell to indicate the selected BPL. The beam selection circuit 943 may also be configured to execute beam selection software 953 stored on the computer-readable medium 906 to implement one or more functions described herein.
[0142] Fig.10 1 is a flow chart illustrating an exemplary process 1000 for synchronizing a UE with an SCell to activate an SCell in a multi-cell transmission environment according to some aspects of the present disclosure. As described below, within the scope of the present disclosure, some or all of the illustrated features may be omitted in certain implementations, and some of the illustrated features may not be required for implementations of all embodiments. In some examples, the process 1000 may be performed by Fig. 9 The process 1000 is shown as being performed by the scheduling entity 900. In some examples, the process 1000 can be performed by any suitable device or unit for performing the functions or algorithms described below.
[0143] At box 1002, a scheduled entity (e.g., a UE) may receive a reference signal trigger from a PCell, the reference signal trigger being used to trigger communication and processing of one or more reference signals between the UE and the SCell. In some examples, the reference signal trigger may identify one or more reference signals among a plurality of reference signals configured in the SCell for the scheduled entity to send or receive in the SCell. In some examples, the reference signal trigger may be included in a MAC-CE sent from the PCell in a PDSCH. Examples of reference signals may include, but are not limited to, CSI-RS, SSB, and SRS. In some examples, the PCell includes a first radio access technology (RAT) and the SCell includes a second RAT. For example, the above reference Fig. 9 The multi-cell management circuitry 941 , communication and processing circuitry 942 , and transceiver 910 shown and described may provide means for receiving a reference signal trigger from a PCell.
[0144] At box 1004, the scheduled entity may synchronize with the SCell based on one or more reference signals to activate the SCell for multi-cell communication. In some examples, the scheduled entity may receive one or more downlink reference signals from the SCell on one or more beams according to the TCI state preconfigured for the downlink reference signal. The scheduled entity may then synchronize with the SCell using the one or more downlink reference signals. In other examples, the scheduled entity may send an uplink reference signal to the SCell on one or more beams based on the SRI of the uplink reference signal. The SCell may then determine time / frequency synchronization information based on the uplink reference signal and send the time / frequency synchronization information to the scheduled entity for synchronization with the SCell. For example, the above reference Fig. 9 The multi-cell management circuitry 941 , communication and processing circuitry 942 , and transceiver 910 shown and described may provide means for transmitting one or more reference signals with the SCell to synchronize with the SCell.
[0145] Fig.11 1 is a flow chart illustrating an exemplary process 1100 for a UE to process a reference signal trigger from a PCell to activate an SCell in a multi-cell transmission environment according to some aspects of the present disclosure. As described below, within the scope of the present disclosure, some or all of the illustrated features may be omitted in certain implementations, 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 Fig. 9 The process 1100 is shown to be performed by the scheduling entity 900. In some examples, the process 1100 can be performed by any suitable device or unit for performing the functions or algorithms described below.
[0146] At block 1102, a scheduled entity (e.g., a UE) may receive a MAC-CE from a PCell including a reference signal trigger identifying one or more reference signals among a plurality of reference signals configured in an SCell for activating the SCell. Examples of reference signals may include, but are not limited to, CSI-RS, SSB, and SRS. For example, the reference signal above Fig. 9 The multi-cell management circuitry 941, communication and processing circuitry 942, and transceiver 910 shown and described may provide means for receiving a MAC-CE including a reference signal trigger from a PCell.
[0147] At block 1104, the scheduled entity may send confirmation information to the SCell to confirm receipt of the MAC-CE. In some examples, the scheduled entity may send the confirmation information on at least one beam associated with at least one of the one or more reference signals for selecting a serving beam pair link for communication between the SCell and the scheduled entity. For example, the above reference Fig. 9 The multi-cell management circuitry 941 , communication and processing circuitry 942 , and transceiver 910 shown and described may provide means for sending confirmation information to the SCell.
[0148] Fig.12 1 is a flow chart illustrating another exemplary process 1200 for UE to synchronously communicate with SCell to activate SCell in a multi-cell transmission environment according to some aspects of the present disclosure. As described below, within the scope of the present disclosure, some or all of the illustrated features may be omitted in certain implementations, and some illustrated features may not be required for implementation of all embodiments. In some examples, the process 1200 may be performed by Fig. 9 The process 1200 is shown to be performed by the scheduling entity 900. In some examples, the process 1200 can be performed by any suitable device or unit for performing the functions or algorithms described below.
[0149] At block 1202, the scheduled entity (eg, UE) may send an activation message to the PCell to activate communication with the SCell for multi-cell communication with the PCell and the SCell. Fig. 9 The multi-cell management circuitry 941 , communication and processing circuitry 942 , and transceiver 910 shown and described may provide means for sending an activation message to a PCell.
[0150] At block 1204, the scheduled entity may receive a reference signal trigger from the PCell, the reference signal trigger being used to trigger communication and processing of one or more reference signals between the UE and the SCell. In some examples, the reference signal trigger may identify one or more reference signals among a plurality of reference signals configured in the SCell for the scheduled entity to send or receive in the SCell. In some examples, the reference signal trigger may be included in a MAC-CE sent from the PCell in the PDSCH. Examples of reference signals may include, but are not limited to, CSI-RS, SSB, and SRS. For example, the reference signal trigger may be included in the MAC-CE sent from the PCell in the PDSCH. Fig. 9 The multi-cell management circuitry 941 , communication and processing circuitry 942 , and transceiver 910 shown and described may provide means for receiving a reference signal trigger from a PCell.
[0151] At box 1206, the scheduled entity may synchronize with the SCell based on one or more reference signals to activate the SCell for multi-cell communication. In some examples, the scheduled entity may receive one or more downlink reference signals from the SCell on one or more beams according to the TCI state preconfigured for the downlink reference signal. The scheduled entity may then synchronize with the SCell using the one or more downlink reference signals. In other examples, the scheduled entity may send an uplink reference signal to the SCell on one or more beams based on the SRI of the uplink reference signal. The SCell may then determine time / frequency synchronization information based on the uplink reference signal and send the time / frequency synchronization information to the scheduled entity for synchronization with the SCell. For example, the above reference Fig. 9 The multi-cell management circuitry 941 , communication and processing circuitry 942 , and transceiver 910 shown and described may provide means for transmitting one or more reference signals with the SCell to synchronize with the SCell.
[0152] In one configuration, the scheduling entity 900 (eg, UE) includes a unit for activating SCells in a multi-cell transmission environment as described in the present disclosure. In one aspect, the above-mentioned unit may be Fig. 9 The processor 904 is configured to perform the functions described by the aforementioned units. In another aspect, the aforementioned units may be circuits or any devices configured to perform the functions described by the aforementioned units.
[0153] Of course, in the above example, the circuit included in the processor 904 is provided only as an example, and other units for performing the functions may be included in various aspects of the present disclosure, including but not limited to being stored in the computer-readable storage medium 906 or Figure 1 , 2, 4-7 and / or 9, any other suitable device or unit described in any one of the instructions stored in, and using, for example, the present invention with respect to Figure 10-12 Describe the process and / or algorithm.
[0154] Fig.13 1 is a flow chart illustrating an exemplary process 1300 for a scheduling entity serving a PCell in a multi-cell transmission environment to activate communications between a scheduled entity and an SCell according to some aspects of the present disclosure. As described below, within the scope of the present disclosure, some or all of the illustrated features may be omitted in certain implementations, and some of the illustrated features may not be required for implementation of all embodiments. In some examples, the process 1300 may be performed by Figure 8 The scheduling entity 800 is shown to perform. In some examples, the process 1300 can be performed by any suitable device or unit for performing the functions or algorithms described below.
[0155] At block 1302, a scheduling entity (eg, a base station) may communicate with a scheduled entity (eg, a UE) in a PCell in a multi-cell environment. Figure 8 The multi-cell management circuitry 841, communication and processing circuitry 843, and transceiver 810 shown and described may provide means for communicating with scheduled entities.
[0156] At block 1304, the scheduling entity may determine to activate communication between the scheduled entity and the SCell for multi-cell communication. In some examples, the scheduling entity may receive an activation message from the scheduled entity to activate the SCell for multi-cell communication. In other examples, the scheduling entity may activate communication between the scheduled entity and the SCell, for example, to provide a higher data rate to the scheduled entity. In some examples, the PCell includes a first RAT and the SCell includes a second RAT. For example, the above reference Figure 8 The multi-cell management circuit 841 shown and described may provide means for activating communications between scheduled entities and SCells.
[0157] At box 1306, the scheduling entity may send a reference signal trigger to the scheduled entity, which reference signal trigger is used to trigger the transmission and processing of one or more reference signals between the scheduled entity and the SCell so that the scheduled entity can be synchronized with the SCell. Examples of reference signals include, but are not limited to, CSI-RS, SSB, and SRS. In some examples, the reference signal trigger may identify one or more reference signals from multiple reference signals configured in the SCell. For example, the scheduling entity may select one or more reference signals from multiple reference signals so that the reference signal trigger identifies a subset of the multiple reference signals for the scheduled entity to use when synchronizing with the SCell. In some examples, the reference signal trigger is included in a MAC-CE that is sent from the PCell to the scheduled entity within the PDSCH. For example, the above reference Figure 8 The multi-cell management circuitry 841, communication and processing circuitry 843, and transceiver 810 shown and described may provide means for sending a reference signal trigger to a scheduled entity.
[0158] Fig.14 1 is a flow chart illustrating another exemplary process 1400 for a scheduling entity serving a PCell in a multi-cell transmission environment to activate communications between a scheduled entity and an SCell according to some aspects of the present disclosure. As described below, within the scope of the present disclosure, some or all of the illustrated features may be omitted in certain implementations, and some of the illustrated features may not be required for implementation of all embodiments. In some examples, the process 1400 may be performed by Figure 8 The scheduling entity 800 is shown to perform. In some examples, the process 1400 can be performed by any suitable device or unit for performing the functions or algorithms described below.
[0159] At block 1402, a scheduling entity (eg, a base station) may communicate with a scheduled entity (eg, a UE) in a PCell in a multi-cell environment. Figure 8 The multi-cell management circuitry 841, communication and processing circuitry 843, and transceiver 810 shown and described may provide means for communicating with scheduled entities.
[0160] At block 1404, the scheduling entity may determine to activate communication between the scheduled entity and the SCell for multi-cell communication. In some examples, the scheduling entity may receive an activation message from the scheduled entity to activate the SCell for multi-cell communication. In other examples, the scheduling entity may activate communication between the scheduled entity and the SCell, for example, to provide a higher data rate to the scheduled entity. For example, the above reference Figure 8The multi-cell management circuit 841 shown and described may provide means for activating communications between scheduled entities and SCells.
[0161] At block 1406, the scheduling entity may select a subset of the plurality of reference signals configured in the SCell for SCell synchronization with the scheduled entity. Figure 8 The multi-cell management circuitry 841 , communication and processing circuitry 843 , and transceiver 810 shown and described may provide means for selecting a subset of SCell reference signals for synchronization with the SCell of a scheduled entity.
[0162] At block 1408, the scheduling entity may send a reference signal trigger to the scheduled entity, the reference signal trigger being used to trigger communication and processing of a subset of reference signals between the scheduled entity and the SCell to enable the scheduled entity to synchronize with the SCell. Examples of reference signals include, but are not limited to, CSI-RS, SSB, and SRS. In some examples, the reference signal trigger is included in a MAC-CE that is sent from the PCell to the scheduled entity within the PDSCH. For example, the reference signal trigger above Figure 8 The multi-cell management circuitry 841, communication and processing circuitry 843, and transceiver 810 shown and described may provide means for sending a reference signal trigger to a scheduled entity.
[0163] At block 1410, the scheduling entity may send an indication of the selected reference signal subset to the SCell. For example, the scheduling entity may send the indication of the selected reference signal subset via backhaul signaling. For example, the above reference Figure 8 The multi-cell management circuitry 841 , communication and processing circuitry 843 , and transceiver 810 shown and described may provide means for sending an indication of a selected reference signal subset to a SCell.
[0164] Fig.15 1 is a flow chart illustrating another exemplary process 1500 for a scheduling entity serving a PCell in a multi-cell transmission environment to activate communications between a scheduled entity and an SCell according to some aspects of the present disclosure. As described below, within the scope of the present disclosure, some or all of the illustrated features may be omitted in certain implementations, and some of the illustrated features may not be required for implementation of all embodiments. In some examples, the process 1500 may be performed by Figure 8 The scheduling entity 800 is shown to perform. In some examples, the process 1500 can be performed by any suitable device or unit for performing the functions or algorithms described below.
[0165] At block 1502, a scheduling entity (eg, a base station) may communicate with a scheduled entity (eg, a UE) in a PCell in a multi-cell environment. Figure 8 The multi-cell management circuitry 841, communication and processing circuitry 843, and transceiver 810 shown and described may provide means for communicating with scheduled entities.
[0166] At block 1504, the scheduling entity may determine to activate communication between the scheduled entity and the SCell for multi-cell communication. In some examples, the scheduling entity may receive an activation message from the scheduled entity to activate the SCell for multi-cell communication. In other examples, the scheduling entity may activate communication between the scheduled entity and the SCell, for example, to provide a higher data rate to the scheduled entity. For example, the above reference Figure 8 The multi-cell management circuit 841 shown and described may provide means for activating communications between scheduled entities and SCells.
[0167] At block 1506, the scheduling entity may send a MAC-CE including a reference signal trigger to the scheduled entity, triggering communication and processing of one or more reference signals between the scheduled entity and the SCell to enable the scheduled entity to synchronize with the SCell. Examples of reference signals include, but are not limited to, CSI-RS, SSB, and SRS. In some examples, the reference signal trigger may identify one or more reference signals from a plurality of reference signals configured in the SCell. For example, the scheduling entity may select one or more reference signals from a plurality of reference signals such that the reference signal trigger identifies a subset of the plurality of reference signals for use by the scheduled entity in synchronizing with the SCell. For example, the reference signal trigger may identify a subset of the plurality of reference signals for use by the scheduled entity in synchronizing with the SCell. Figure 8 The multi-cell management circuitry 841, communication and processing circuitry 843, and transceiver 810 shown and described may provide means for sending a reference signal trigger to a scheduled entity.
[0168] At block 1508, the scheduling entity may receive confirmation information from the SCell to confirm that the scheduled entity received the MAC-CE. For example, the confirmation information may be transmitted from the scheduled entity to the SCell, and the SCell may then provide the confirmation information to the PCell via, for example, backhaul signaling. For example, the above reference Figure 8 The multi-cell management circuitry 841 , communication and processing circuitry 843 , and transceiver 810 shown and described may provide means for receiving confirmation information from a SCell.
[0169] Fig.161 is a flow chart illustrating an exemplary process 1600 for a scheduling entity serving an SCell in a multi-cell transmission environment to facilitate synchronization with a scheduled entity to activate the SCell for communication with the scheduled entity according to some aspects of the present disclosure. As described below, within the scope of the present disclosure, some or all of the illustrated features may be omitted in certain implementations, and some of the illustrated features may not be required for implementation of all embodiments. In some examples, the process 1600 may be performed by Figure 8 The scheduling entity 800 is shown to perform. In some examples, the process 1600 can be performed by any suitable device or unit for performing the functions or algorithms described below.
[0170] At block 1602, a scheduling entity (e.g., a base station) may configure a plurality of reference signals for a scheduled entity (e.g., a UE). Examples of reference signals may include, but are not limited to, CSI-RS, SSB, and SRS. For example, the scheduling entity may configure a TCI state or SRI for each reference signal in the reference signal (e.g., a spatial beam). The scheduling entity may also communicate beam information indicating the TCI state or SRI to the scheduled entity, e.g., during initial access of the scheduled entity in an SCell. For example, the above reference Figure 8 The multi-cell management circuitry 841, communication and processing circuitry 843, and transceiver 810 shown and described may provide means for configuring multiple reference signals.
[0171] At block 1604, the scheduling entity may receive a reference signal message from the PCell, the reference signal message including an indication of one or more reference signals of a plurality of reference signals selected by the PCell for the UE to use for synchronization with the SCell. Figure 8 The multi-cell management circuit 841 shown and described may provide means for receiving reference signal messages.
[0172] At box 1606, the scheduling entity may transmit one or more reference signals to the scheduled entity to enable the scheduled entity to synchronize with the SCell and activate the SCell for multi-cell communication. In some examples, the scheduling entity may send one or more downlink reference signals in the SCell on one or more beams according to the TCI state preconfigured for the downlink reference signal. The scheduled entity may then synchronize with the SCell using the one or more downlink reference signals. In other examples, the scheduling entity may receive an uplink reference signal from the scheduled entity on one or more beams according to the SRI of the uplink reference signal. The scheduling entity may then determine time / frequency synchronization information based on the uplink reference signal and send the time / frequency synchronization information to the scheduled entity for synchronization with the SCell. For example, the above reference Figure 8The multi-cell management circuitry 841, communication and processing circuitry 843, and transceiver 810 shown and described may provide means for communicating one or more reference signals with a scheduled entity.
[0173] Fig.17 1 is a flowchart illustrating another exemplary process 1700 for a scheduling entity serving an SCell in a multi-cell transmission environment to facilitate synchronization with a scheduled entity to activate the SCell for communication with the scheduled entity according to some aspects of the present disclosure. As described below, within the scope of the present disclosure, some or all of the illustrated features may be omitted in certain implementations, and some of the illustrated features may not be required for implementation of all embodiments. In some examples, the process 1700 may be performed by Figure 8 The scheduling entity 800 is shown to perform. In some examples, the process 1700 can be performed by any suitable device or unit for performing the functions or algorithms described below.
[0174] At block 1702, a scheduling entity (e.g., a base station) may configure a plurality of reference signals for a scheduled entity (e.g., a UE). Examples of reference signals may include, but are not limited to, CSI-RS, SSB, and SRS. For example, the scheduling entity may configure a TCI state or SRI for each reference signal in the reference signal (e.g., a spatial beam). The scheduling entity may also communicate beam information indicating the TCI state or SRI to the scheduled entity, e.g., during initial access of the scheduled entity in an SCell. For example, the above reference Figure 8 The multi-cell management circuitry 841, communication and processing circuitry 843, and transceiver 810 shown and described may provide means for configuring multiple reference signals.
[0175] At block 1704, the scheduling entity may receive a reference signal message from the PCell, the reference signal message including an indication of one or more reference signals of a plurality of reference signals selected by the PCell for the UE to use for synchronization with the SCell. Figure 8 The multi-cell management circuit 841 shown and described may provide means for receiving reference signal messages.
[0176] At box 1706, the scheduling entity may transmit one or more reference signals to the scheduled entity so that the scheduled entity can synchronize with the SCell and activate the SCell for multi-cell communication. In some examples, the scheduling entity may send one or more downlink reference signals in the SCell on one or more beams according to the TCI state preconfigured for the downlink reference signal. The scheduled entity may then synchronize with the SCell using the one or more downlink reference signals. In other examples, the scheduling entity may receive an uplink reference signal from the scheduled entity on one or more beams according to the SRI of the uplink reference signal. The scheduling entity may then determine time / frequency synchronization information based on the uplink reference signal and send the time / frequency synchronization information to the scheduled entity for synchronization with the SCell. For example, the above reference Figure 8 The multi-cell management circuitry 841, communication and processing circuitry 843, and transceiver 810 shown and described may provide means for communicating one or more reference signals with a scheduled entity.
[0177] At block 1708, the scheduling entity may receive, from the scheduled entity, confirmation information confirming receipt of a MAC-CE sent from the PCell to the scheduled entity, the MAC-CE identifying each of the one or more reference signals to be transmitted between the scheduled entity and the scheduling entity (e.g., SCell). Figure 8 The multi-cell management circuitry 841, communication and processing circuitry 843, and transceiver 810 shown and described may provide means for receiving acknowledgement information from a scheduled entity.
[0178] At block 1710, the scheduling entity may send confirmation information to the PCell. Figure 8 The multi-cell management circuitry 841 , communication and processing circuitry 843 , and transceiver 810 shown and described may provide means for sending confirmation information to the PCell.
[0179] Fig.18 A flowchart illustrating another exemplary process 1800 of a scheduling entity serving an SCell in a multi-cell transmission environment facilitating synchronization with a scheduled entity to activate the SCell for communication with the scheduled entity according to some aspects of the present disclosure. As described below, within the scope of the present disclosure, some or all of the illustrated features may be omitted in certain implementations, and some of the illustrated features may not be required for implementation of all embodiments. In some examples, the process 1800 may be performed by Figure 8 The scheduling entity 800 is shown to perform. In some examples, the process 1800 can be performed by any suitable device or unit for performing the functions or algorithms described below.
[0180] At block 1802, a scheduling entity (e.g., a base station) may configure a plurality of reference signals for a scheduled entity (e.g., a UE). Examples of reference signals may include, but are not limited to, CSI-RS, SSB, and SRS. For example, the scheduling entity may configure a TCI state or SRI for each reference signal in the reference signal (e.g., a spatial beam). The scheduling entity may also communicate beam information indicating the TCI state or SRI to the scheduled entity, e.g., during initial access of the scheduled entity in an SCell. For example, the above reference Figure 8 The multi-cell management circuitry 841, communication and processing circuitry 843, and transceiver 810 shown and described may provide means for configuring multiple reference signals.
[0181] At block 1804, the scheduling entity may receive a reference signal message from the PCell, the reference signal message including an indication of one or more reference signals of a plurality of reference signals selected by the PCell for the UE to use for synchronization with the SCell. Figure 8 The multi-unit management circuit 841 shown and described may provide means for receiving reference signal messages.
[0182] At box 1806, the scheduling entity may transmit one or more reference signals to the scheduled entity so that the scheduled entity can synchronize with the SCell and activate the SCell for multi-cell communication. In some examples, the scheduling entity may send one or more downlink reference signals in the SCell on one or more beams according to the TCI state preconfigured for the downlink reference signal. The scheduled entity may then synchronize with the SCell using the one or more downlink reference signals. In other examples, the scheduling entity may receive an uplink reference signal from the scheduled entity on one or more beams according to the SRI of the uplink reference signal. The scheduling entity may then determine time / frequency synchronization information based on the uplink reference signal and send the time / frequency synchronization information to the scheduled entity for synchronization with the SCell. For example, the above reference Figure 8 The multi-cell management circuitry 841, communication and processing circuitry 843, and transceiver 810 shown and described may provide means for communicating one or more reference signals with a scheduled entity.
[0183] At block 1808, the scheduling entity may receive, from the scheduled entity, confirmation information confirming receipt of a MAC-CE sent from the PCell to the scheduled entity on at least one beam associated with at least one of the reference signals, the MAC-CE identifying each of the one or more reference signals transmitted between the scheduled entity and the scheduling entity (e.g., SCell). In some examples, the scheduling entity may receive the confirmation information on at least one beam associated with at least one selected reference signal selected by the scheduled entity. For example, the above reference Figure 8 The multi-cell management circuitry 841, communication and processing circuitry 843, and transceiver 810 shown and described may provide means for receiving acknowledgement information from a scheduled entity.
[0184] At block 1810, the scheduling entity may select a serving beam pair link for communicating with the scheduled entity based on at least one beam on which the confirmation information is received. Figure 8 The beam selection circuit 844 shown and described may provide means for selecting a serving beam pair link.
[0185] In one configuration, the scheduling entity 800 (e.g., a base station) includes a unit for activating an SCell to communicate with a scheduled entity (e.g., a UE) in a multi-cell transmission environment as described in the present disclosure. In one aspect, the above-mentioned unit can be Figure 8 The processor 804 shown is configured to perform the functions described in the above units. In another aspect, the above units may be circuits or any devices configured to perform the functions described in the above units.
[0186] Of course, in the above example, the circuit included in the processor 804 is provided only as an example, and other units for performing the functions may be included in various aspects of the present disclosure, including but not limited to being stored in the computer-readable storage medium 806 or in Figure 1 , 2 and / or any other suitable device or unit described in any one of 4-8, and using, for example, Figure 13-18 The processes and / or algorithms described in this document.
[0187] The following provides an overview of examples of the present disclosure.
[0188] Example 1: A method for a user equipment (UE) to communicate in a wireless communication network including a primary service cell (PCell) and a secondary service cell (SCell), the method comprising: receiving a reference signal trigger from the PCell, wherein the reference signal trigger is used to trigger communication and processing of one or more reference signals between the UE and the SCell; and synchronizing with the SCell based on the one or more reference signals to activate the SCell for multi-cell communication.
[0189] Example 2: The method according to Example 1, wherein the reference signal trigger identifies one or more reference signals among a plurality of reference signals configured in the SCell.
[0190] Example 3: The method according to Example 1 or 2, wherein receiving a reference signal trigger further comprises: receiving a medium access control-control element (MAC-CE) including the reference signal trigger.
[0191] Example 4: The method according to any one of Examples 1-3 further includes: sending confirmation information to the SCell to confirm receipt of the MAC-CE.
[0192] Example 5: A method according to any one of Examples 1-4, wherein sending confirmation information further comprises: sending confirmation information on at least one beam associated with at least one reference signal among one or more reference signals for selecting a serving beam pair link for communication between the SCell and the UE.
[0193] Example 6: A method according to any one of Examples 1-5, wherein the one or more reference signals include at least one of the following: a channel state information-reference signal (CSI-RS), a synchronization signal block (SSB), or a sounding reference signal (SRS).
[0194] Example 7: The method according to any one of Examples 1-6 further includes: in response to receiving a reference signal trigger, sending an uplink reference signal of one or more reference signals to the SCell.
[0195] Example 8: A method according to any of Examples 1-7, wherein the PCell includes a first radio access technology (RAT) and the SCell includes a second RAT.
[0196] Example 9: The method according to any one of Examples 1-8 further includes: sending an activation message to the PCell to activate communication with the SCell, for multi-cell communication with the PCell and the SCell.
[0197] Example 10: A scheduled entity in a wireless communication network including a primary service cell (PCell) and a secondary service cell (SCell), the scheduled entity comprising: a transceiver; a memory; and a processor, which is communicatively coupled to the transceiver and the memory, the processor and the memory being configured to perform the method of any one of Examples 1-9.
[0198] Example 11: A method for a primary service cell (PCell) to facilitate multi-cell communication in a wireless communication network including a PCell and a secondary service cell (SCell), the method comprising: communicating with a user equipment (UE) in the PCell; activating communication between the UE and the SCell for multi-cell communication; and sending a reference signal trigger to the UE to trigger communication and processing of one or more reference signals between the UE and the SCell to enable the UE to synchronize with the SCell.
[0199] Example 12: The method according to Example 11, wherein activating communication between the UE and the SCell further comprises: receiving an activation message from the UE to activate the SCell for multi-cell communication.
[0200] Example 13: A method according to Example 11 or 12, wherein the reference signal trigger identifies one or more reference signals among a plurality of reference signals configured in the SCell.
[0201] Example 14: The method according to any one of Examples 11-13 further includes: selecting one or more reference signals from a plurality of reference signals, wherein the one or more reference signals include a subset of the plurality of reference signals.
[0202] Example 15: The method according to any one of Examples 11-14 further includes: sending an indication of one or more reference signals identified in the reference signal trigger to the SCell.
[0203] Example 16: A method according to any one of Examples 11-15, wherein sending a reference signal trigger further includes: sending a medium access control-control element (MAC-CE) including the reference signal trigger.
[0204] Example 17: The method according to any one of Examples 11-16 further includes: receiving confirmation information from the SCell for confirming that the UE has received the MAC-CE, wherein the confirmation information is transmitted from the UE to the SCell.
[0205] Example 18: A method according to any of Examples 11-17, wherein the PCell includes a first radio access technology (RAT) and the SCell includes a second RAT.
[0206] Example 19: A method for a secondary service cell (SCell) to facilitate multi-cell communication in a wireless communication network including a primary service cell (PCell) and the SCell, the method comprising: configuring multiple reference signals in the SCell; receiving a reference signal message from the PCell for a user equipment (UE) to use to synchronize with the SCell, the message comprising an indication of one or more reference signals of a plurality of reference signals selected by the PCell; and communicating the one or more reference signals to the UE to enable the UE to synchronize with the SCell and activate the SCell for multi-cell communication.
[0207] Example 20: The method according to Example 19 further includes: receiving confirmation information from the UE, confirming receipt of a medium access control-control element (MAC-CE) sent from the PCell to the UE, wherein the MAC-CE identifies each of the one or more reference signals to be transmitted between the UE and the SCell.
[0208] Example 21: A method according to Example 19 or 20, wherein receiving confirmation information also includes: receiving confirmation information on at least one beam associated with at least one reference signal among the one or more reference signals.
[0209] Example 22: The method according to any one of Examples 19-21 also includes: selecting a serving beam pair link for communicating with the UE based on at least one beam on which confirmation information is received.
[0210] Example 23: A method according to any one of Examples 19-22, wherein receiving confirmation information on at least one beam also includes: receiving confirmation information on at least one beam associated with at least one selected reference signal among one or more reference signals selected by the UE.
[0211] Example 24: The method according to any one of Examples 19-23 also includes: sending confirmation information to PCell.
[0212] Example 25: The method according to any one of Examples 19-24 also includes: receiving an uplink reference signal of one or more reference signals from a UE.
[0213] Several aspects of wireless communication networks have been presented with reference to exemplary implementations. As those skilled in the art will readily appreciate, various aspects described throughout this disclosure may be extended to other telecommunication systems, network architectures, and communication standards.
[0214] By way of example, various aspects may be implemented in other systems defined by 3GPP, such as LTE, Evolved Packet System (EPS), Universal Mobile Telecommunications System (UMTS), and / or Global System for Mobile (GSM). Various aspects may also be extended to systems defined by the Third Generation Partnership Project 2 (3GPP2), such as CDMA2000 and / or Evolution Data Optimized (EV-DO). Other examples may be implemented in systems employing Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE802.20, Ultra Wideband (UWB), Bluetooth, and / or other suitable systems. The actual telecommunication standard, network architecture, and / or communication standard employed will depend on the specific application and the overall design constraints imposed on the system.
[0215] In the present disclosure, 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 being preferred or advantageous over other aspects of the present disclosure. Likewise, the term "aspect" does not require that all aspects of the present disclosure include the discussed features, advantages, or modes of operation. The term "coupled" is used herein to refer to a direct or indirect coupling between two objects. For example, if object A physically contacts object B, and object B contacts object C, objects A and C may still be considered to be coupled to each other—even if they are not in direct physical contact with each other. For example, a first object may be coupled to a second object even if the first object never directly contacts the second object physically. The terms "circuit" and "circuitry" are used broadly and are intended to include hardware implementations of electrical devices and conductors that, when connected and configured, enable the functions described in the present disclosure to be performed, without limitation to the type of electronic circuits, as well as software implementations of information and instructions that, when executed by a processor, enable the functions described in the present disclosure to be performed.
[0216] Figure 1-Figure 18 One or more of the components, steps, features, and / or functions shown in the drawings may be rearranged and / or combined into a single component, step, feature, or function, or may be embodied in several components, steps, or functions. Additional elements, components, steps, and / or functions may also be added without departing from the novel features disclosed herein. Figure 1 , 2 and / or Figure 4-9 The apparatus, devices and / or components shown in the can be configured to perform one or more of the methods, features or steps described herein. The novel algorithms described herein can also be effectively implemented in software and / or embedded in hardware.
[0217] It should be understood that the specific order or hierarchy of steps in the disclosed methods is an illustration of exemplary processes. It should be understood that the specific order or hierarchy of steps in the methods may be rearranged based on design preferences. The accompanying method claims present elements of the various steps in a sample order, and are not meant to be limited to the specific order or hierarchy presented unless specifically recited therein.
[0218] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not intended to be limited to the various aspects shown herein, but to conform to the full scope consistent with the language of the claims, wherein unless otherwise specified, the elements mentioned in the singular are not intended to represent "one and only one", but "one or more". Unless otherwise expressly stated, the term "some" refers to one or more. The phrase "at least one" referring to a list of items refers to any combination of these items, including a single member. For example, "at least one of a, b, or c" is intended to cover: a; b; c; a and b; a and c; b and c; and a, b, and c. All structural and functional equivalents of the elements throughout the various aspects described in this disclosure that are known or will be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be covered by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly stated in the claims. No claim element is to be construed under 35 USC §112(f) unless the element is expressly recited using the phrase "means for" or, in the case of a method claim, the phrase "step for."
Claims
1. A method for a user equipment (UE) to communicate in a wireless communication network including a primary serving cell (PCell) and a secondary serving cell (SCell), the method include: receiving a reference signal trigger from the PCell, the reference signal trigger being used to trigger transmission and processing of one or more reference signals between the UE and the SCell; synchronizing with the SCell based on the one or more reference signals to activate the SCell for multi-cell communication; as well as Send confirmation information for confirming receipt of the reference signal trigger to activate the SCell, wherein the confirmation information is sent to the SCell on at least one beam associated with at least one reference signal among the one or more reference signals.
2. The method according to claim 1, in, The reference signal trigger identifies the one or more reference signals among a plurality of reference signals configured in the SCell.
3. The method according to claim 2, in, Receiving the reference signal trigger also includes: A medium access control-control element (MAC-CE) including the reference signal trigger is received.
4. The method according to claim 3, in, The confirmation information is used to confirm receipt of the MAC-CE.
5. The method according to claim 4, further comprising: include: Based on the at least one beam associated with the confirmation information, a serving beam pair link is selected for communication between the SCell and the UE.
6. The method according to claim 1, in, The one or more reference signals include at least one of: a channel state information-reference signal (CSI-RS), a synchronization signal block (SSB), or a sounding reference signal (SRS).
7. The method according to claim 1, further comprising: include: In response to receiving the reference signal trigger, an uplink reference signal of the one or more reference signals is sent to the SCell.
8. The method according to claim 1, in, The PCell includes a first radio access technology (RAT), and the SCell includes a second RAT.
9. The method according to claim 1, further comprising: include: An activation message is sent to the PCell to activate communication with the SCell, for the multi-cell communication with the PCell and the SCell.
10. A scheduled entity in a wireless communication network comprising a primary serving cell (PCell) and a secondary serving cell (SCell), the scheduled entity include: Transceiver; Memory; as well as a processor communicatively coupled to the transceiver and the memory, wherein the processor and the memory are configured to: receiving, via the transceiver, a reference signal trigger from the PCell, the reference signal trigger being used to trigger transmission and processing of one or more reference signals between the UE and the SCell; synchronizing with the SCell based on the one or more reference signals to activate the SCell for multi-cell communication; and Send confirmation information for confirming receipt of the reference signal trigger to activate the SCell, wherein the confirmation information is sent to the SCell on at least one beam associated with at least one reference signal among the one or more reference signals.
11. The scheduled entity according to claim 10, in, The reference signal trigger identifies the one or more reference signals among a plurality of reference signals configured in the SCell.
12. The scheduled entity according to claim 11, in, The processor and the memory are further configured to: receiving a medium access control-control element (MAC-CE) including the reference signal trigger; The confirmation information is used to confirm receipt of the MAC-CE.
13. The scheduled entity according to claim 12, in, The processor and the memory are further configured to: Based on the at least one beam associated with the confirmation information, a serving beam pair link is selected for communication between the SCell and the UE.
14. The scheduled entity according to claim 10, in, The processor and the memory are further configured to: In response to receiving the reference signal trigger, an uplink reference signal of the one or more reference signals is sent to the SCell.
15. The scheduled entity according to claim 10, in, The processor and the memory are further configured to: An activation message is sent to the PCell to activate communication with the SCell, for the multi-cell communication with the PCell and the SCell.
16. A method for a primary serving cell (PCell) to facilitate multi-cell communication in a wireless communication network comprising the PCell and a secondary serving cell (SCell), the method include: Communicating with a user equipment (UE) in the PCell; activating communication between the UE and the SCell for the multi-cell communication; as well as A reference signal trigger is sent to the UE, wherein the reference signal trigger is used to trigger the transmission and processing of one or more reference signals between the UE and the SCell, so as to configure the UE to synchronize with the SCell using the one or more reference signals and to send confirmation information to the SCell on at least one beam associated with at least one of the one or more reference signals to confirm the receipt of the reference signal trigger to activate the SCell.
17. The method according to claim 16, in, The activating communication between the UE and the SCell further includes: An activation message is received from the UE to activate the SCell for the multi-cell communication.
18. The method according to claim 16, in, The reference signal trigger identifies one or more reference signals among a plurality of reference signals configured in the SCell.
19. The method according to claim 18, further comprising: include: The one or more reference signals are selected from the plurality of reference signals, wherein the one or more reference signals comprise a subset of the plurality of reference signals.
20. The method according to claim 16, further comprising: include: An indication of the one or more reference signals identified in the reference signal trigger is sent to the SCell.
21. The method according to claim 16, in, The sending of the reference signal trigger further includes: A medium access control-control element (MAC-CE) including the reference signal trigger is sent.
22. The method according to claim 21, further comprising: include: The confirmation information for confirming that the UE has received the MAC-CE is received from the SCell, wherein the confirmation information is transmitted from the UE to the SCell.
23. The method according to claim 16, in, The PCell includes a first radio access technology (RAT), and the SCell includes a second RAT.
24. A method for a secondary serving cell (SCell) to facilitate multi-cell communication in a wireless communication network comprising a primary serving cell (PCell) and the SCell, the method include: configuring a plurality of reference signals in the SCell; receiving a reference signal message from the PCell for use by a user equipment (UE) to synchronize with the SCell, the reference signal message comprising an indication of one or more of the plurality of reference signals selected by the PCell; transmitting the one or more reference signals to a UE so that the UE can synchronize with the SCell and activate the SCell for the multi-cell communication; as well as A confirmation message for confirming that a reference signal trigger is received from the PCell to activate the SCell is received from the UE, the confirmation message being received on at least one beam associated with at least one reference signal among the one or more reference signals.
25. The method according to claim 24, further comprising: include: The confirmation information is received from the UE to confirm receipt of a medium access control-control element (MAC-CE) sent from the PCell to the UE, wherein the MAC-CE identifies each of the one or more reference signals to be transmitted between the UE and the SCell.
26. The method according to claim 24, further comprising: include: A serving beam pair link for communication with the UE is selected based on the at least one beam on which the confirmation information is received.
27. The method according to claim 26, in, Receiving the confirmation information on at least one beam further comprises: The acknowledgement information is received on at least one beam associated with at least one selected reference signal of the one or more reference signals selected by the UE.
28. The method according to claim 25, further comprising: include: Send the confirmation information to the PCell.
29. The method according to claim 24, further comprising: include: An uplink reference signal of the one or more reference signals is received from the UE.
30. A scheduling entity for a primary serving cell (PCell) to facilitate multi-cell communication in a wireless communication network comprising the PCell and a secondary serving cell (SCell), include: Transceiver; Memory; as well as A processor communicatively coupled to the transceiver and the memory, wherein the processor and the memory are configured to perform the method of any one of claims 16-23.
31. A scheduling entity for a secondary serving cell (SCell) to facilitate multi-cell communication in a wireless communication network comprising a primary serving cell (PCell) and the SCell, include: Transceiver; Memory; as well as A processor communicatively coupled to the transceiver and the memory, wherein the processor and the memory are configured to perform the method of any one of claims 24-29.
