RATE MATCHING AND BEAM MEASUREMENT FOR INTER-CELL BEAM MANAGEMENT AND INTER-CELL MULTI-TRP OPERATION

Inter-cell beam management and inter-cell multiple transmission and reception point (multi-TRP) operation may include decoding a cell-specific reference signal (CRS) pattern list configuration received from a base station. The CRS pattern list configuration may include one or more CRS pattern lists. Each of the one or more CRS pattern lists correspond to one or more cells of a plurality of cells configured by the base station. Beam management associated with the plurality of cells may be performed based on the CRS pattern list configuration.

TECHNICAL FIELD

This application relates generally to wireless communication systems, including inter-cell beam management and inter-cell multi-TRP operation.

BACKGROUND

Wireless mobile communication technology uses various standards and protocols to transmit data between a base station and a wireless communication device. Wireless communication system standards and protocols can include, for example, 3rd Generation Partnership Project (3GPP) long term evolution (LTE) (e.g., 4G), 3GPP new radio (NR) (e.g., 5G), and IEEE 802.11 standard for wireless local area networks (WLAN) (commonly known to industry groups as Wi-Fi®).

As contemplated by the 3GPP, different wireless communication systems standards and protocols can use various radio access networks (RANs) for communicating between a base station of the RAN (which may also sometimes be referred to generally as a RAN node, a network node, or simply a node) and a wireless communication device known as a user equipment (UE). 3GPP RANs can include, for example, global system for mobile communications (GSM), enhanced data rates for GSM evolution (EDGE) RAN (GERAN), Universal Terrestrial Radio Access Network (UTRAN), Evolved Universal Terrestrial Radio Access Network (E-UTRAN), and/or Next-Generation Radio Access Network (NG-RAN).

Each RAN may use one or more radio access technologies (RATs) to perform communication between the base station and the UE. For example, the GERAN implements GSM and/or EDGE RAT, the UTRAN implements universal mobile telecommunication system (UMTS) RAT or other 3GPP RAT, the E-UTRAN implements LTE RAT (sometimes simply referred to as LTE), and NG-RAN implements NR RAT (sometimes referred to herein as 5G RAT, 5G NR RAT, or simply NR). In certain deployments, the E-UTRAN may also implement NR RAT. In certain deployments, NG-RAN may also implement LTE RAT.

A base station used by a RAN may correspond to that RAN. One example of an E-UTRAN base station is an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (also commonly denoted as evolved Node B, enhanced Node B, eNodeB, or eNB). One example of an NG-RAN base station is a next generation Node B (also sometimes referred to as a or g Node B or gNB).

A RAN provides its communication services with external entities through its connection to a core network (CN). For example, E-UTRAN may utilize an Evolved Packet Core (EPC), while NG-RAN may utilize a 5G Core Network (5GC).

Frequency bands for 5G NR may be separated into two or more different frequency ranges. For example, Frequency Range 1 (FR1) may include frequency bands operating in sub-6 GHz frequencies, some of which are bands that may be used by previous standards, and may potentially be extended to cover new spectrum offerings from 410 MHz to 7125 MHz. Frequency Range 2 (FR2) may include frequency bands from 24.25 GHz to 52.6 GHz. Note that in some systems, FR2 may also include frequency bands from 52.6 GHz to 71 GHz (or beyond). Bands in the millimeter wave (mm Wave) range of FR2 may have smaller coverage but potentially higher available bandwidth than bands in FR1. Skilled persons will recognize these frequency ranges, which are provided by way of example, may change from time to time or from region to region.

DETAILED DESCRIPTION

By way of background, 3gPP Release 17 (Rel-17) has plans to support both inter-cell beam management (also referred to herein as BM) and inter-cell multi-transmission and reception points (TRPs). For inter-cell beam management, base stations (e.g., gNBs) may provide a transmission configuration indicator (TCI) associated with a neighbor cell synchronization signal block (SSB) for uplink and downlink signals. Notably, TCIs may be used for beam indication and can be based on a media access control (MAC) control element (CE) or downlink control information (DCI). In addition, a UE may not have to simultaneously communicate (e.g., simultaneously transmit or receive) with more than one cell.

For inter-cell multi-TRP operation, a base station (e.g., gNB) can provide TCIs associated with SSBs from different cells for signals associated with different control resource set (CORESET) pool indexes (CORESETPoolIndex(es)). Notably, signals associated with one CORESETPoolIndex may be associated with a single cell and UEs may have to simultaneously communicate with more than one cell. CORESETS may be utilized for physical downlink control channel (PDCCH) configuration. In addition, CORESET pool indexes may each be associated with a particular TRP.

In 3GPP Release 16 (Rel-16), with regard to dynamic spectrum sharing between LTE and NR, rate matching in NR may include consideration of LTE cell-specific reference signals (CRSs). In particular, a base station (e.g., a gNB) can provide a list of CRS patterns via radio resource control (RRC) signaling for rate matching purposes (see e.g., Section 6.3.2 of 3GPP Technical Specification (TS) 38.331). In addition, resource elements corresponding to a configured CRS pattern may be considered to be “not available” for rate matching purposes.

For single-TRP operation, a base station (e.g., a gNB) can provide one list of CRS patterns while for multi-TRP operation, a base station can provide two lists of CRS patterns, where each list is associated with a single TRP. For instance, the following may apply:

To measure beam quality, a UE can report Layer 1 Reference Signal Received Power (L1-RSRP) for a subset of SSBs among a list of SSBs from one or more neighbor cell(s). Regarding which, the following may apply: 1. UEs may be configured to measure SSBs from multiple cells; 2. SSBs from multiple cells may be multiplexed in a fully-overlapped pattern; 3. Base stations (e.g., gNBs) can configure time domain measurement restrictions for SSBs (see e.g., Section 5.2.1.4.3 of 3GPP TS 38.514), including: a. If a higher layer parameter referred to as timeRestrictionForChannelMeasurements in a channel state information (CSI) report configuration (CSI-ReportConfig) is set to “notConfigured,” a UE may derive channel measurements for computing L1-RSRP values reported in an uplink slot n based on a synchronization signal/physical broadcast channel (SS/PBCH) or a non-zero power (NZP) CSI-reference signal (CSI-RS), no later than a CSI reference resource (see e.g., 3GPP TS 38.211[4]) associated with the CSI resource setting; or b. If the higher layer parameter timeRestrictionForChannelMeasurements in CSI-ReportConfig is set to “Configured”, the UE may derive channel measurements for computing L1-RSRP reported in an uplink slot n based on a most recent (and no later than the CSI reference resource) occasion of an SS/PBCH or an NZP CSI-RS (see e.g., 3GPP TS 38.211[4]) associated with the CSI resource setting; and 3. A reported L1-RSRP may follow a minimal processing delay Z=Z3 and Z′=Z3′ (see e.g., Section 5.4 3GPP TS 38.414], where: a. Z is a minimal offset between a last symbol of a DCI triggering an L1-RSRP report and a first symbol of the L1-RSRP report; and b. Z′ is a minimal offset between a last symbol of an SSB and a first symbol of the L1-RSRP report.

In addition, the following related issues may remain: 1. For inter-cell BM and inter-cell multi-TRP operation, a base station can configure up to seven cells for each component carrier (CC), where a corresponding LTE CRS pattern for each such cell may be different. Accordingly, up to eight LTE CRS patterns may be applicable when including the serving cell. Such scenarios may create great complexity and the manner in which to support such cell-specific CRS patterns is currently unresolved; and 2. SSBs from different cells may be multiplexed in overlapping resources (seeFIG.1for more details), which may cause a UEs complexity in measuring L1-RSRP from SSBs with overlapped resources in comparison to non-overlapped resources to be quite different. The manner in which networks can support such scenarios (e.g., supporting different beam report latency for different overlapping cases) also remains unresolved. Accordingly, the principles and solutions described herein may assist in resolving such issues.

As briefly referred to above,FIG.1illustrates slots (i.e., slot1and slot2) and SSBs of three different cells (i.e., cell1102, cell2104, and cell3106). As represented by ellipse108, a first SSB (or SSB1) associated with each of cell1102, cell2104, and cell3106may include overlapping resources. Similarly, as represented by ellipse112, a third SSB (or SSB3) associated with cell1102and cell3106may also include overlapping resources. Again, such overlapping resources between SSBs of separate cells may create additional complexity in measuring L1-RSRP corresponding to such SSBs. As shown,FIG.1also includes SSB2110corresponding to cell1102and SSB4114corresponding to cell2104, neither of which include any overlapping resources.

In a first solution, various options may be utilized to support cell-specific LTE CRS pattern lists. For instance, in a first option, a base station (e.g., a gNB) can configure an LTE CRS pattern list for each cell of a potential plurality of cells via RRC. In particular, for N cells, a base station may provide N LTE CRS pattern lists. In some embodiments, however, a base station may share less than N LTE CRS pattern lists with respect to N cells (e.g., when some of the N cells share a same LTE CRS pattern). In scenarios where a CRS pattern is not provided, a CRS pattern list of a corresponding serving cell can be reused (or rate matching for LTE CRS may simply be ignored).

With respect to the first option, for downlink signals having an indication of the TCI State associated with the cell, the corresponding CRS pattern is considered for rate matching. For downlink signals without TCI indicated, however, the following three options may be utilized: a. The LTE CRS pattern list configured for the serving cell is used for rate matching; b. The LTE CRS pattern list configured for the cell associated with a TCI applied for a dedicated physical downlink shared channel (PDSCH) is used for rate matching. For inter-cell multi-TRP, this option may include the dedicated physical downlink control channel (PDCCH)/PDSCH indicating the PDCCH/PDSCH associated with CORESETPoolIndex=0; or c. No LTE CRS pattern is considered for rate matching (e.g., when there is no LTE deployed in the same location as the cell).

In a second option of the first solution, an LTE CRS pattern list can be updated by MAC CE. In a first example, a base station may initially provide a set of LTE CRS pattern lists by RRC signaling. In such cases, a MAC CE can then indicate a particular LTE CRS pattern list from the set of LTE CRS pattern lists to be used for a CORESETPoolIndex (i.e., for inter-cell multi-TRP) or for a CC. In a second example, a base station again may initially provide an LTE CRS pattern list by RRC signaling. The configuration for each parameter may then be updated by MAC CE.

In a third option of the first solution, an LTE CRS pattern list can be further refined by scheduling DCI. In a first example, a base station may provide a set of LTE CRS pattern lists by RRC signaling, further refine the set of lists via MAC CE, and indicate one of the LTE CRS pattern lists from the set of lists refined by MAC CE via DCI. In a second example, a base station may provide a set of LTE CRS pattern lists by RRC and then use DCI to indicate one particular LTE CRS pattern list from the set of LTE CRS pattern lists.

FIG.2illustrates an example for cell-specific CRS patterns and corresponding TCI indications. As shown,FIG.2includes an LTE CRS pattern202associated with a first cell and an LTE CRS pattern204associated with a second cell. Upon receiving a first TCI state indication (i.e., TCI state1206) corresponding to the first cell, rate matching may be performed based on the LTE CRS pattern202(as represented by pattern1rate matching208) after an action delay. Similarly, upon receiving a second TCI state indication (i.e., TCI state2210) corresponding to the second cell, rate matching may be performed based on the LTE CRS pattern204(as represented by pattern2rate matching212).

Further enhancements to general rate matching patterns for each cell (associated with the first solution) will now be discussed. In an example, with regard to different configurations for different cells, a rate matching pattern (RateMatchingPattern) or rate matching group (RateMatchingGroup) may be provided in a cell-specific manner. In fact, the first, second, and third options of the first solution may be used for rate matching patterns and rate matching group determinations and configurations. For instance, in a scheduling DCI, a corresponding rate matching group for a given cell may be selected. Notably, RateMatchingPattern and RateMatchingGroup are defined in Section 6.3.2 of 3GPP TS 38.331.

In another enhancement, with regard to different configuration for different cells, a scrambling identification (ID) may also be configured in a cell-specific manner. As such, the first, second, and third options of the first solution may again be used to support cell-specific scrambling IDs (e.g. dataScramblingIdentityPDSCH). In an example, when a scrambling ID is not provided, a corresponding cell ID may be used for data scrambling, which cell ID may be determined based on a cell associated with an indicated TCI State for the downlink signal.

In yet another enhancement, with regard to UE memory management, a UE can report a maximum number of rate matching patterns and/or LTE CRS pattern lists across configured cells as a UE capability. Alternatively, a UE can report a maximum number of neighbor cells with different rate matching patterns or LTE CRS pattern lists it can support in comparison to a serving cell's rate matching patterns.

In a second solution, various options may be utilized for minimal measurement delay with respect to overlapped SSBs. For instance, in a first option, a minimal delay for Z and Z′ may be Z3+d and Z3′+d, where d can be predefined (e.g., d is determined by a number of overlapped SSB symbols(S) or S*ceiling {(N−1)/K}, where N is a number of overlapped SSBs and K indicates a number of SSBs that a UE can simultaneously receive (which may be predefined (e.g., K=1) or reported by UE capability)). When there are multiple overlapping occasions, d may be counted based on a total number of d for all the occasions or a maximum number of d for all the occasions. For example, inFIG.1, to report L1-RSRP for all the SSBs, d=4*2+0+4+0=12 symbols or d=max {4*2, 0, 4, 0}=8 symbols (i.e., 4*2 based on the two additional overlapping SSBs of ellipse108, 4 based on the one additional overlapping SSB of ellipse112and two 0's based on SSB2110and SSB4114not including any additional overlapping SSBs).

In another example, a scaling factor S maybe introduced to calculate a value of ‘d’. For instance, d=S*Z_3*N, where N is a number of overlapped SSBs. In such embodiments, the value of S maybe hard-encoded in the specification or reported in a UE capability report. This embodiment may be useful in some instances by the fact that some of baseband processing steps are shared for multiple SSBs that are measured by UE.

In an enhancement of the first option, for Frequency Range 2 (FR2) with regard to UE beam sweeping, d may be defined in terms of an SSB periodicity level. For example, d may be determined by SSB periodicity (T) or T*(N−1). Alternatively, d may be reported based on UE capability.

In a second option of the second solution, measurements may take ceiling {N/K} CSI processing units (CPUs), where N is a number of overlapped SSBs and K indicates a number of SSBs that a UE can simultaneously receive (which may be predefined (e.g., K=1) or reported by UE capability)), resulting in a minimal delay of Z=Z3 and Z′=Z3′ (CPU is defined in Section 5.2.1.6 of 3GPP TS 38.514). Notably, such embodiments include an assumption that UEs would process the measurement of overlapped SSBs in a parallel processing mode.

In a third option of the second solution, whether the first option or the second option of the second solution is utilized may be reported by UE capability. For instance, such determinations may be based on whether a given UE is capable of parallel processing. For UEs that can support both options, an RRC parameter may be introduced for option selection. In addition, a UE may report/update which option it prefers via MAC CE, followed by a base station RRC reconfiguration.

In a fourth option of the second solution, a UE can report a capability of a maximum number of overlapped SSBs it can support for L1-RSRP measurement. The base station's configuration may then be based on the reported UE capability, resulting in a minimal processing delay of Z=Z3 and Z′=Z3′.

For other measurements (e.g., beam failure detection (BFD), radio link monitoring (RLM), and so forth), overlapped SSBs may be used for similar or different functionalities (e.g., a first is configured for BFD and a second is configured for L1-RSRP measurement).

An evaluation periodicity for such other measurements (e.g., BFD, RLM, and so forth) may be scaled in accordance with various options. For instance, in a first option, such scaling factor may be predefined. In a first example, the periodicity for an SSB for BFD/RLM (or other measurements) may be Xms*(N−1), where X indicates the periodicity without overlapped SSBs. In a second example, the periodicity for an SSB for BFD/RLM (or other measurements) could be Xms*ceiling {(N−1)/K}, where X indicates the periodicity without overlapped SSBs. Regardless, an overall periodicity for BFD/RLM (or other measurements) may be determined by a minimum periodicity or maximum periodicity for the SSBs configured for BFD/RLM (or other measurements).

In a second option, such scaling factor may be reported by UE capability. For instance, an RRC parameter may be introduced to configure the scaling factor based on UE capability.

FIG.3illustrates a method for inter-cell beam management/inter-cell multi-TRP operation. In block302, the method300decodes a cell-specific reference signal (CRS) pattern list configuration received from a base station. The CRS pattern list configuration may include one or more CRS pattern lists. In addition, each of the one or more CRS pattern lists may correspond to one or more cells of a plurality of cells configured by the base station. In block304, the method300performs beam management associated with the plurality of cells based on the CRS pattern list configuration. For instance, such CRS pattern list configuration may include CRS patterns similar to LTE CRS pattern202ofFIG.2.

The method300may also include performing beam management including at least one of performing Layer 1-Reference Signal Received Power (L1-RSRP) measurements and rate matching corresponding to a first cell of the plurality of cells. The method300may also include decoding a transmission configuration indicator (TCI) state indication associated with a downlink signal of a first cell of the plurality of cells, and performing rate matching based at least partially on a CRS pattern corresponding to the first cell. The CRS pattern may be included within the one or more CRS pattern lists.

The method300may further include the plurality of cells configured by the base station comprising seven cells and the one or more CRS pattern lists comprising eight CRS pattern lists. The method300may further include determining that a downlink signal of a first cell of the plurality of cells does not include an associated transmission configuration indicator (TCI) state indication.

The method300may further include, based on determining that the downlink signal of the first cell does not include an associated transmission configuration indicator (TCI) state indication, performing rate matching based at least partially on a first CRS pattern list configured for a current serving cell of the UE, or performing rate matching based on a second CRS pattern list associated with a cell corresponding to a TCI for a dedicated physical downlink shared channel (PDSCH).

The method300may further include the CRS pattern list configuration being provided by radio resource configuration (RRC). The method300may also include updating at least one of the one or more CRS pattern lists via a medium access control (MAC) control element (CE). The method300may further include decoding downlink control information (DCI) indicating a first CRS pattern list from the one or more CRS pattern lists.

The method300may further include decoding scheduling downlink control information (DCI) indicating a rate matching group associated with the CRS pattern list configuration. The method300may further include decoding a UE capability communication for transmission to the base station. The UE capability communication may indicate a maximum number of CRS pattern lists associated with the plurality of cells configured by the base station.

The method300may further include identifying overlapping synchronization signal blocks (SSBs) between multiple cells of the plurality of cells configured by the base station. The method300may further include the overlapping SSBs between multiple cells of the plurality of cells comprising a first set of SSBs associated with a first cell of the plurality of cells and a second set of SSBs associated with a second cell of the plurality of cells. The first set of SSBs may be configured for beam failure detection (BFD) and the second set of SSBs may be configured for Layer 1-Reference Signal Received Power (L1-RSRP) measurements.

The method300may further include an evaluation periodicity associated with BFD including a scaling factor. The method300may also include the scaling factor being either pre-defined or reported by the UE as a UE capability. The method300may further include identifying overlapping synchronization signal blocks (SSBs) between multiple cells of the plurality of cells configured by the base station.

The method300may further include a minimum measurement delay associated with performing beam management including consideration of a number of overlapping synchronization signal blocks (SSBs) between multiple cells of the plurality of cells configured by the base station. The method300may further include the minimum measurement delay further including consideration of a number of overlapping SSB symbols and a maximum number of SSBs that the UE is configured to receive simultaneously.

The method300may also include the minimum measurement delay further including consideration of an SSB periodicity level for beam sweeping in Frequency Range 2 (FR2). The method300may further include, when the UE is configured to process overlapping SSB measurements in parallel, a duration of performing measurements comprising a number of channel state information (CSI) processing units. The number may be calculated based on a number of overlapping SSB symbols and a maximum number of SSBs that the UE is configured to receive simultaneously.

The method300may further include encoding a UE capability report for transmission to the base station, the UE capability report including an indication of parallel processing capabilities of the UE.

The method300may further include encoding a UE capability report for transmission to the base station. The UE capability report may include an indication of a maximum number of overlapping SSBs the UE supports for Layer 1-Reference Signal Received Power (L1-RSRP) measurements.

Embodiments contemplated herein include an apparatus comprising means to perform one or more elements of the method300. This apparatus may be, for example, an apparatus of a UE (such as a wireless device502that is a UE, as described herein).

Embodiments contemplated herein include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of the method300. This non-transitory computer-readable media may be, for example, a memory of a UE (such as a memory506of a wireless device502that is a UE, as described herein).

Embodiments contemplated herein include an apparatus comprising logic, modules, or circuitry to perform one or more elements of the method300. This apparatus may be, for example, an apparatus of a UE (such as a wireless device502that is a UE, as described herein).

Embodiments contemplated herein include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of the method300. This apparatus may be, for example, an apparatus of a UE (such as a wireless device502that is a UE, as described herein).

Embodiments contemplated herein include a computer program or computer program product comprising instructions, wherein execution of the program by a processor is to cause the processor to carry out one or more elements of the method300. The processor may be a processor of a UE (such as a processor(s)504of a wireless device502that is a UE, as described herein). These instructions may be, for example, located in the processor and/or on a memory of the UE (such as a memory506of a wireless device502that is a UE, as described herein).

FIG.4illustrates an example architecture of a wireless communication system400, according to embodiments disclosed herein. The following description is provided for an example wireless communication system400that operates in conjunction with the LTE system standards and/or 5G or NR system standards as provided by 3GPP technical specifications.

As shown byFIG.4, the wireless communication system400includes UE402and UE404(although any number of UEs may be used). In this example, the UE402and the UE404are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks), but may also comprise any mobile or non-mobile computing device configured for wireless communication.

The UE402and UE404may be configured to communicatively couple with a RAN406. In embodiments, the RAN406may be NG-RAN, E-UTRAN, etc. The UE402and UE404utilize connections (or channels) (shown as connection408and connection410, respectively) with the RAN406, each of which comprises a physical communications interface. The RAN406can include one or more base stations, such as base station412and base station414, that enable the connection408and connection410.

In this example, the connection408and connection410are air interfaces to enable such communicative coupling, and may be consistent with RAT(s) used by the RAN406, such as, for example, an LTE and/or NR.

In some embodiments, the UE402and UE404may also directly exchange communication data via a sidelink interface416. The UE404is shown to be configured to access an access point (shown as AP418) via connection420. By way of example, the connection420can comprise a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein the AP418may comprise a Wi-Fi® router. In this example, the AP418may be connected to another network (for example, the Internet) without going through a CN424.

In embodiments, the UE402and UE404can be configured to communicate using orthogonal frequency division multiplexing (OFDM) communication signals with each other or with the base station412and/or the base station414over a multicarrier communication channel in accordance with various communication techniques, such as, but not limited to, an orthogonal frequency division multiple access (OFDMA) communication technique (e.g., for downlink communications) or a single carrier frequency division multiple access (SC-FDMA) communication technique (e.g., for uplink and ProSe or sidelink communications), although the scope of the embodiments is not limited in this respect. The OFDM signals can comprise a plurality of orthogonal subcarriers.

In some embodiments, all or parts of the base station412or base station414may be implemented as one or more software entities running on server computers as part of a virtual network. In addition, or in other embodiments, the base station412or base station414may be configured to communicate with one another via interface422. In embodiments where the wireless communication system400is an LTE system (e.g., when the CN424is an EPC), the interface422may be an X2 interface. The X2 interface may be defined between two or more base stations (e.g., two or more eNBs and the like) that connect to an EPC, and/or between two eNBs connecting to the EPC. In embodiments where the wireless communication system400is an NR system (e.g., when CN424is a 5GC), the interface422may be an Xn interface. The Xn interface is defined between two or more base stations (e.g., two or more gNBs and the like) that connect to 5GC, between a base station412(e.g., a gNB) connecting to 5GC and an eNB, and/or between two eNBs connecting to 5GC (e.g., CN424).

The RAN406is shown to be communicatively coupled to the CN424. The CN424may comprise one or more network elements426, which are configured to offer various data and telecommunications services to customers/subscribers (e.g., users of UE402and UE404) who are connected to the CN424via the RAN406. The components of the CN424may be implemented in one physical device or separate physical devices including components to read and execute instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium).

In embodiments, the CN424may be an EPC, and the RAN406may be connected with the CN424via an S1 interface428. In embodiments, the S1 interface428may be split into two parts, an S1 user plane (S1-U) interface, which carries traffic data between the base station412or base station414and a serving gateway (S-GW), and the S1-MME interface, which is a signaling interface between the base station412or base station414and mobility management entities (MMEs).

In embodiments, the CN424may be a 5GC, and the RAN406may be connected with the CN424via an NG interface428. In embodiments, the NG interface428may be split into two parts, an NG user plane (NG-U) interface, which carries traffic data between the base station412or base station414and a user plane function (UPF), and the S1 control plane (NG-C) interface, which is a signaling interface between the base station412or base station414and access and mobility management functions (AMFs).

Generally, an application server430may be an element offering applications that use internet protocol (IP) bearer resources with the CN424(e.g., packet switched data services). The application server430can also be configured to support one or more communication services (e.g., VoIP sessions, group communication sessions, etc.) for the UE402and UE404via the CN424. The application server430may communicate with the CN424through an IP communications interface432.

FIG.5illustrates a system500for performing signaling534between a wireless device502and a network device518, according to embodiments disclosed herein. The system500may be a portion of a wireless communications system as herein described. The wireless device502may be, for example, a UE of a wireless communication system. The network device518may be, for example, a base station (e.g., an eNB or a gNB) of a wireless communication system.

The wireless device502may include one or more processor(s)504. The processor(s)504may execute instructions such that various operations of the wireless device502are performed, as described herein. The processor(s)504may include one or more baseband processors implemented using, for example, a central processing unit (CPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a controller, a field programmable gate array (FPGA) device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.

The wireless device502may include a memory506. The memory506may be a non-transitory computer-readable storage medium that stores instructions508(which may include, for example, the instructions being executed by the processor(s)504). The instructions508may also be referred to as program code or a computer program. The memory506may also store data used by, and results computed by, the processor(s)504.

The wireless device502may include one or more transceiver(s)510that may include radio frequency (RF) transmitter and/or receiver circuitry that use the antenna(s)512of the wireless device502to facilitate signaling (e.g., the signaling534) to and/or from the wireless device502with other devices (e.g., the network device518) according to corresponding RATs.

The wireless device502may include one or more antenna(s)512(e.g., one, two, four, or more). For embodiments with multiple antenna(s)512, the wireless device502may leverage the spatial diversity of such multiple antenna(s)512to send and/or receive multiple different data streams on the same time and frequency resources. This behavior may be referred to as, for example, multiple input multiple output (MIMO) behavior (referring to the multiple antennas used at each of a transmitting device and a receiving device that enable this aspect). MIMO transmissions by the wireless device502may be accomplished according to precoding (or digital beamforming) that is applied at the wireless device502that multiplexes the data streams across the antenna(s)512according to known or assumed channel characteristics such that each data stream is received with an appropriate signal strength relative to other streams and at a desired location in the spatial domain (e.g., the location of a receiver associated with that data stream). Certain embodiments may use single user MIMO (SU-MIMO) methods (where the data streams are all directed to a single receiver) and/or multi user MIMO (MU-MIMO) methods (where individual data streams may be directed to individual (different) receivers in different locations in the spatial domain).

In certain embodiments having multiple antennas, the wireless device502may implement analog beamforming techniques, whereby phases of the signals sent by the antenna(s)512are relatively adjusted such that the (joint) transmission of the antenna(s)512can be directed (this is sometimes referred to as beam steering).

The wireless device502may include one or more interface(s)514. The interface(s)514may be used to provide input to or output from the wireless device502. For example, a wireless device502that is a UE may include interface(s)514such as microphones, speakers, a touchscreen, buttons, and the like in order to allow for input and/or output to the UE by a user of the UE. Other interfaces of such a UE may be made up of made up of transmitters, receivers, and other circuitry (e.g., other than the transceiver(s)510/antenna(s)512already described) that allow for communication between the UE and other devices and may operate according to known protocols (e.g., Wi-Fi®, Bluetooth®, and the like).

The wireless device502may include an Inter-cell module516. The Inter-cell module516may be implemented via hardware, software, or combinations thereof. For example, the Inter-cell module516may be implemented as a processor, circuit, and/or instructions508stored in the memory506and executed by the processor(s)504. In some examples, the Inter-cell module516may be integrated within the processor(s)504and/or the transceiver(s)510. For example, the Inter-cell module516may be implemented by a combination of software components (e.g., executed by a DSP or a general processor) and hardware components (e.g., logic gates and circuitry) within the processor(s)504or the transceiver(s)510.

The Inter-cell module516may be used for various aspects of the present disclosure, for example, aspects ofFIGS.1through3. The Inter-cell module516is configured to assist with inter-cell beam management and inter-cell multi-TRP operation, as further described herein.

The network device518may include one or more processor(s)520. The processor(s)520may execute instructions such that various operations of the network device518are performed, as described herein. The processor(s)520may include one or more baseband processors implemented using, for example, a CPU, a DSP, an ASIC, a controller, an FPGA device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.

The network device518may include a memory522. The memory522may be a non-transitory computer-readable storage medium that stores instructions524(which may include, for example, the instructions being executed by the processor(s)520). The instructions524may also be referred to as program code or a computer program. The memory522may also store data used by, and results computed by, the processor(s)520.

The network device518may include one or more transceiver(s)526that may include RF transmitter and/or receiver circuitry that use the antenna(s)528of the network device518to facilitate signaling (e.g., the signaling534) to and/or from the network device518with other devices (e.g., the wireless device502) according to corresponding RATs.

The network device518may include one or more antenna(s)528(e.g., one, two, four, or more). In embodiments having multiple antenna(s)528, the network device518may perform MIMO, digital beamforming, analog beamforming, beam steering, etc., as has been described.

The network device518may include one or more interface(s)530. The interface(s)530may be used to provide input to or output from the network device518. For example, a network device518that is a base station may include interface(s)530made up of transmitters, receivers, and other circuitry (e.g., other than the transceiver(s)526/antenna(s)528already described) that enables the base station to communicate with other equipment in a core network, and/or that enables the base station to communicate with external networks, computers, databases, and the like for purposes of operations, administration, and maintenance of the base station or other equipment operably connected thereto.

The network device518may include an inter-cell module532. The inter-cell module532may be implemented via hardware, software, or combinations thereof. For example, the inter-cell module532may be implemented as a processor, circuit, and/or instructions524stored in the memory522and executed by the processor(s)520. In some examples, the inter-cell module532may be integrated within the processor(s)520and/or the transceiver(s)526. For example, the inter-cell module532may be implemented by a combination of software components (e.g., executed by a DSP or a general processor) and hardware components (e.g., logic gates and circuitry) within the processor(s)520or the transceiver(s)526.

The inter-cell module532may be used for various aspects of the present disclosure, for example, aspects ofFIGS.1through3. The inter-cell module532is configured to assist with inter-cell beam management and inter-cell multi-TRP operation, as further described herein.

For one or more embodiments, at least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and/or methods as set forth herein. For example, a baseband processor as described herein in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth herein. For another example, circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth herein.