CN116235594A

CN116235594A - Subcarrier spacing restriction for SSB, CSI-RS for L3 mobility and PDCCH/PDSCH

Info

Publication number: CN116235594A
Application number: CN202180059299.6A
Authority: CN
Inventors: 崔杰; 叶春璇; 张大伟; 孙海童; 何宏; M·拉加万; O·奥特莱; 杨维东; 唐扬; 张羽书
Original assignee: Apple Inc
Current assignee: Apple Inc
Priority date: 2020-07-29
Filing date: 2021-04-14
Publication date: 2023-06-06
Also published as: US20220353126A1; KR20230029876A; WO2022021944A1; EP4162752A1; EP4162752A4

Abstract

Techniques are provided for supporting different parameter sets for concurrent intra-frequency measurements and downlink data reception. A User Equipment (UE) may send a message to a wireless network to indicate whether the UE supports a mixed parameter set, wherein different subcarrier spacings (SCS) are used in a serving cell or a neighboring cell to simultaneously process at least two of: the UE making intra-frequency measurements of a Synchronization Signal Block (SSB); the UE performs intra-frequency measurements of channel state information reference signals (CSI-RS) for mobility; and reception of a Physical Downlink Control Channel (PDCCH) or a Physical Downlink Shared Channel (PDSCH) by the UE. Based on the indication, the network may configure at least one of CSI-RS measurement expectations, SSB measurement expectations, and scheduling restrictions of reception of the PDCCH or the PDSCH by the UE.

Description

Subcarrier spacing restriction for SSB, CSI-RS for L3 mobility and PDCCH/PDSCH

Technical Field

The present application relates generally to wireless communication systems, including systems that support different sets of parameters for concurrent intra-frequency measurements and downlink data reception.

Background

Wireless mobile communication technology uses various standards and protocols to transfer data between a base station and a wireless mobile device. Wireless communication system standards and protocols may include 3 rd generation partnership project (3 GPP) Long Term Evolution (LTE) (e.g., 4G) or new air interface (NR) (e.g., 5G); the Institute of Electrical and Electronics Engineers (IEEE) 802.16 standard, which is commonly referred to by industry organizations as Worldwide Interoperability for Microwave Access (WiMAX); and the IEEE 802.11 standard for Wireless Local Area Networks (WLANs), which is commonly referred to by industry organizations as Wi-Fi. In a 3GPP Radio Access Network (RAN) in an LTE system, a base station may include a RAN node, such as an evolved Universal terrestrial radio Access network (E-UTRAN) node B (also commonly referred to as an evolved node B, enhanced node B, eNodeB, or eNB), and/or a Radio Network Controller (RNC) in the E-UTRAN, that communicates with wireless communication devices called User Equipment (UE). In a fifth generation (5G) wireless RAN, the RAN nodes may include 5G nodes, NR nodes (also referred to as next generation node bs or G nodebs (gnbs)).

The RAN communicates between RAN nodes and UEs using Radio Access Technology (RAT). The RAN may comprise a global system for mobile communications (GSM), enhanced data rates for GSM evolution (EDGE) RAN (GERAN), universal Terrestrial Radio Access Network (UTRAN), and/or E-UTRAN, which provides access to communication services through a core network. Each of the RANs operates according to a particular 3GPP RAT. For example, GERAN implements GSM and/or EDGE RATs, UTRAN implements Universal Mobile Telecommunications System (UMTS) RATs or other 3gpp RATs, e-UTRAN implements LTE RATs, and NG-RAN implements 5G RATs. In some deployments, the E-UTRAN may also implement the 5G RAT.

The frequency band of 5G NR can be divided into two different frequency ranges. Frequency range 1 (FR 1) may include frequency bands operating at frequencies below 6GHz, some of which are available for use by previous standards, and may potentially be extended to cover new spectrum products of 410MHz to 7125 MHz. The frequency range 2 (FR 2) may include a frequency band of 24.25GHz to 52.6 GHz. The frequency band in the millimeter wave (mmWave) range of FR2 may have a smaller range but potentially higher available bandwidth than the frequency band in FR 1. The skilled person will appreciate that these frequency ranges provided by way of example may vary from time to time or region to region.

Drawings

For ease of identifying discussions of any particular element or act, one or more of the most significant digits in a reference numeral refer to the figure number that first introduces that element.

Fig. 1 illustrates a method for a wireless network according to one embodiment.

Fig. 2 illustrates a method for a User Equipment (UE) according to one embodiment.

Fig. 3 illustrates a system according to one embodiment.

Fig. 4 illustrates infrastructure equipment according to one embodiment.

Fig. 5 illustrates a platform according to one embodiment.

Fig. 6 shows components according to one embodiment.

Detailed Description

In a wireless network, downlink (DL) -based Radio Resource Management (RRM) measurements at UEs in connected mode may be used for layer 3 (L3) mobility. L3 mobility may allow a UE to roam in different networks without losing its Internet Protocol (IP) address and session. Reference Signal Received Power (RSRP) of a Synchronization Signal (SS) block (SSB) or a channel state information reference signal (CSI-RS) measured by the UE in the connected mode may be used for L3 mobility.

Generally, a base station may broadcast SSB signals that include synchronization and cell-specific information for accessing a cell associated with the base station. SSBs may include a Primary Synchronization Signal (PSS), a Secondary Synchronization Signal (SSS), and a Physical Broadcast Channel (PBCH). Thus, SSB may also be referred to as a synchronization signal/PBCH block. The PSS and SSS may include synchronization signaling and information for decoding the PBCH, such as a cell Identifier (ID). The PBCH may indicate transmission parameters that may be used for initial cell access, including downlink system bandwidth used by the cell, physical hybrid automatic repeat request (HARQ) channel structure, system frame number, and/or antenna port. After decoding the PBCH, the UE may monitor the downlink of the CSI-RS (e.g., for L3 mobility purposes) according to the resource locations associated with the antenna ports identified by the CSI-RS configuration of the serving cell and/or one or more neighboring cells. Upon detection of the CSI-RS, the UE may generate Channel Quality Information (CQI), which is then fed back to the base station and used to select transmission parameters during link establishment.

In some systems, the measurement object of CSI-RS for mobility may be configured with a specific subcarrier spacing (SCS) on each frequency layer. For example, the measurement object configuration Information Element (IE) may include:

on the same frequency, the control or data channel (e.g., physical Downlink Control Channel (PDCCH) or Physical Downlink Shared Channel (PDSCH)) and SSB may have SCS different from that of the CSI-RS for mobility. However, the PDCCH or PDSCH may also have SCS different from SSB. Thus, for example, for PDCCH/PDSCH, SSB and CSI-RS for mobility, there may be three different parameter sets on one frequency (e.g., 15kHz SCS, 30kHz SCS and 60kHz SCS for FR 1). As used herein, a parameter set refers to a particular SCS value (e.g., 15 kHz). However, those skilled in the art will recognize from the disclosure herein that a parameter set may associate a particular SCS value with one or more other parameters, such as the Cyclic Prefix (CP) length of an Orthogonal Frequency Division Multiplexing (OFDM) symbol.

Although some wireless systems may use a hybrid parameter set for SSB and PDCCH/PDSCH, some UEs may not have sufficient processing, memory, and/or power resources to process using three different SCSs on one frequency to coordinate measurement resources or demodulation resources between PDCCH/PDSCH, SSB, and CSI-RS for mobility. For example, the difficulty of the UE may have been increased for the case of measurement without Measurement Gaps (MG). The PDCCH/PDSCH may naturally be muted if the MG is configured for measurement. Accordingly, certain embodiments disclosed herein provide for limitations of SCS in intra-frequency CSI-RS mobility measurements and measurement and/or scheduling limitations.

In some wireless systems, when CSI-RS resources of the serving cell are available, the CSI-RS based intra-frequency measurements include measurements defined as CSI-RS based intra-frequency measurements, provided that: the SCS of the CSI-RS resource configured for measurement on the neighbor cell is the same as the SCS of the CSI-RS resource indicated for measurement on the serving cell, and the CP type of the CSI-RS resource configured for measurement on the neighbor cell is the same as the CP type of the CSI-RS resource indicated for measurement on the serving cell, and this applies to a predetermined SCS (e.g., 60 kHz), and wherein the center frequency of the CSI-RS resource configured for measurement on the neighbor cell is the same as the center frequency of the CSI-RS resource indicated for measurement on the serving cell. Otherwise, if the CSI-RS based inter-frequency measurement is not the CSI-RS based intra-frequency measurement, the CSI-RS based inter-frequency measurement may be a measurement defined as the CSI-RS based inter-frequency measurement. In general, the UE may use the gap to perform inter-frequency measurements. Thus, a UE performing inter-frequency measurements may not experience the same difficulties as when the UE performs intra-frequency measurements on the same frequency or Component Carrier (CC) with a mixed parameter set.

In some embodiments, SCS is limited for SSB, L3CSI-RS, and PDCCH/PDSCH in order to avoid increasing the cost and complexity of the UE. Thus, while the network can use three different SCSs for SSB, L3CSI-RS and PDCCH/PDSCH, SCS restrictions allow for configuration of at most two SCSs for one serving cell only. Thus, two operations of three operations of SSB-based measurement, L3 CSI-RS-based measurement, and PDCCH/PDSCH reception share the first SCS, and the remaining operations use the second SCS. For example, in one embodiment, the SCS restriction may indicate that the SSB and CSI-RS for mobility share the same SCS of the same serving cell. In another example, the SCS restriction may indicate that the PDCCH/PDSCH and CSI-RS for mobility share the same SCS of the same serving cell. SCS limits may be defined in the standard so that the UE and the network use the same SCS assumptions and options. In other embodiments, SCS restrictions may be configured on a network, serving cell, or Component Carrier (CC) basis.

Even when SCS restrictions allow only at most two SCSs for one serving cell, some UEs may not support mixed parameter sets (different SCSs) on the same frequency. Thus, the UE may send a message to the network to indicate the UE's ability to support the hybrid parameter set. In some embodiments, UE capability parameters in a Radio Resource Control (RRC) message may be modified to indicate support for CSI-RS for mobility in a hybrid parameter set.

For example, a simultaneousrxdata ssb-DiffNumerology parameter in a set of UE capability parameters defined in 3gpp TS 38.306 indicates whether the UE supports concurrent intra-frequency measurements on a serving cell or neighboring cells with different parameter sets and PDCCH or PDSCH reception from the serving cell. In embodiments where SSB and CSI-RS for mobility share the same SCS of the same serving cell, the simultanesssb-DiffNumerology parameters may be updated to indicate whether the UE supports concurrent intra-frequency measurements on the serving cell or neighboring cells with different parameter sets, as well as PDCCH or PDSCH reception from the serving cell, regarding SSB or CSI-RS for mobility. In another embodiment of the PDCCH/PDSCH and CSI-RS for mobility sharing the same SCS of the same serving cell, the simultaneousrxdata ssb-DiffNumerology parameters may be configured to indicate whether the UE supports concurrent intra-frequency measurements on the serving cell or neighboring cells with different parameter sets and PDCCH or PDSCH reception from the serving cell or CSI-RS measurements for mobility.

The network may respond to the indication of UE capability by configuring CSI-RS measurement expectations, SSB measurement expectations, or scheduling restrictions of the UE for reception of PDCCH or PDSCH.

In one embodiment, for example, the serving cell is configured to have the SSB and CSI-RS for mobility share a first SCS and have the PDCCH/PDSCH use a second SCS. The UE may send a UE capability message including a simultaneousrxdata SSB-DiffNumerology parameter to indicate whether the UE supports intra-frequency measurements on SSB or CSI-RS for mobility on a serving cell or neighboring cells that are concurrent with different parameter sets and PDCCH or PDSCH reception from the serving cell. If the UE capability message indicates that a mixed parameter set is supported, the network schedules the UE to receive PDCCH and/or PDSCH on symbols where the UE may also measure SSB or CSI-RS. However, if the UE capability message indicates that the hybrid parameter set is not supported, the network does not schedule the UE for PDCCH and/or PDSCH reception on a set of symbols where the UE measures SSB or CSI-RS and one symbol before and one symbol after the SSB or CSI-RS. One symbol before and one symbol after the SSB or CSI-RS provides a margin for time misalignment between the serving cell and the UE.

In another exemplary embodiment, the serving cell is configured to let PDCCH/PDSCH and CSI-RS for mobility share a first SCS and to let SSB use a second SCS. The UE may send a UE capability message including a simultaneousrxdata ssb-DiffNumerology parameter to indicate whether the UE supports intra-frequency measurements on a serving cell or neighboring cells that are concurrent with different parameter sets and PDCCH or PDSCH reception from the serving cell or CSI-RS measurements for mobility. If the UE capability message indicates that a hybrid parameter set is supported, the network may expect the UE to perform CSI-RS measurements and SSB measurements on the same symbol. However, if the UE capability message indicates that the hybrid parameter set is not supported, the network does not expect the UE to perform CSI-RS measurements and SSB measurements on the same symbol. For example, when the UE cannot support the mixed parameter set, the network may determine: the UE is not expected to perform CSI-RS measurements on a set of symbols in which the UE is measuring SSB and one symbol before and one symbol after SSB; the UE is not expected to perform SSB measurements on a set of symbols in which the UE is measuring CSI-RS and one symbol before CSI-RS and one symbol after CSI-RS; or using scaling factors for time resource allocation for CSI-RS based mobility measurements and SSB based mobility measurements (e.g., when CSI-RS based mobility measurements and SSB based mobility measurements collide with each other in the time domain, 50% of the time opportunities are used for CSI-RS based mobility measurements and 50% of the time opportunities are used for SSB based mobility measurements). The former symbol and the latter symbol provide a margin for time misalignment between the serving cell and the UE.

In another embodiment, the UE may indicate the capability of its number of hybrid parameter sets, and the network configures CSI-RS or PDCCH/PDSCH based on the capability.

For example, in one embodiment, the UE sends a UE capability message including a simultaneouscsirsandsb-DiffNumerology parameter to indicate whether the UE supports intra-frequency measurements for both SSB and CSI-RS for mobility on concurrent serving or neighbor cells with different parameter sets. If the UE indicates that it cannot support simultaneouscsirsandsb-diffnumerics, after receiving the UE capability, the network may optionally determine: the UE is not expected to perform CSI-RS measurements on a set of symbols in which the UE is measuring SSB and one symbol before and one symbol after SSB; the UE is not expected to perform SSB measurements on a set of symbols in which the UE is measuring CSI-RS and one symbol before CSI-RS and one symbol after CSI-RS; or using scaling factors for time resource allocation for CSI-RS based mobility measurements and SSB based mobility measurements (e.g., when CSI-RS based mobility measurements and SSB based mobility measurements collide with each other in the time domain, 50% of the time opportunities are used for CSI-RS based mobility measurements and 50% of the time opportunities are used for SSB based mobility measurements). Also, the former symbol and the latter symbol provide a margin for time misalignment between the serving cell and the UE.

As another exemplary embodiment, the UE transmits a UE capability message including a simultaneousrxdata csirs-DiffNumerology parameter to indicate whether the UE supports intra-frequency measurements on a serving cell or neighboring cells with concurrent CSI-RS for mobility with different parameter sets and PDCCH or PDSCH reception from the serving cell. If the UE indicates that it cannot support simultaneousrxdata csirs-DiffNumerology, after receiving the UE capability, the network may determine not to schedule the UE for PDCCH/PDSCH reception on the set of symbols in which the UE is measuring CSI-RS and one symbol before and one symbol after the CSI-RS. The former symbol and the latter symbol provide a margin for time misalignment between the serving cell and the UE.

As another exemplary embodiment, the UE transmits a UE capability message including a simultaneousrxdata csirdssb-DiffNumerology parameter to indicate whether the UE supports concurrent intra-frequency measurements on a serving cell or neighboring cells with a first SCS (SCS 1), intra-frequency measurements on CSI-RSs for mobility with a second SCS (SCS 2), and PDCCH or PDSCH reception from a serving cell with a third SCS (SCS 3), wherein SCS 1, SCS2, and SCS3 are three different SCS. In FR1, for example, SCS 1 is selected from 15kHz or 30kHz, and SCS2 and SCS3 are selected from 30kHz or 60kHz. In FR2, for example, SCS 1 is selected from 120kHz or 240kHz, and SCS2 and SCS3 are selected from 60kHz and 120kHz. If the UE indicates that it cannot support simultaneousrxdata csirsandssb-diffnumerics, after receiving the UE capability, the network may determine that: when receiving data and measuring CSI-RS for mobility and measuring SSB collide in the time domain and they use different SCS, it is not desirable for the UE to receive data and measure CSI-RS for mobility and measure SSB.

Fig. 1 is a flow chart illustrating a method 100 for a wireless network, according to some embodiments. In block 102, the method 100 includes: the message from the UE is decoded. The message includes an indication of whether the UE supports a hybrid parameter set, wherein different SCS are used in the serving cell or in a neighboring cell to concurrently process at least two of: intra-frequency measurement of SSB by UE, intra-frequency measurement of CSI-RS for mobility by UE, and reception of PDCCH or PDSCH by UE. In block 104, based on the indication, the method 100 further comprises: at least one of CSI-RS measurement expectations, SSB measurement expectations, and scheduling restrictions of UE reception of PDCCH or PDSCH is configured.

In certain embodiments, the method 100 further comprises: at most two SCSs are configured for the serving cell, wherein the SSB and the CSI-RS for mobility share a first SCS of the two SCSs of the serving cell. The indication indicates whether the UE supports concurrent reception of PDCCH or PDSCH from the serving cell by the UE using the first SCS and intra-frequency measurement of SSB or CSI-RS for mobility by the UE using the second of the two SCS. The indication may include, for example, a simultaneousrxdata ssb-DiffNumerology parameter in a set of UE capability parameters. The method 100 may further include: in response to the indication indicating that the UE does not support the mixed parameter set, the scheduling restriction is configured to not schedule the UE for reception of the PDCCH or PDSCH on: the UE is configured to measure a set of one or more symbols of the SSB or CSI-RS thereon; a first symbol preceding the set of one or more symbols; and a second symbol subsequent to the set of one or more symbols.

In certain embodiments, the method 100 further comprises: at most two SCSs are configured for the serving cell, wherein CSI-RS for mobility and reception of PDCCH or PDSCH by the UE share a first SCS of the two SCSs of the serving cell. The indication indicates whether the UE supports concurrency: the UE's reception of PDCCH or PDSCH from the serving cell or the UE's intra-frequency measurement of CSI-RS for mobility using a first of the two SCS, and the UE's intra-frequency measurement of SSB using a second of the two SCS. In one embodiment, in response to the indication indicating that the UE does not support the hybrid parameter set, the method 100 further comprises: configuring CSI-RS measurements to not expect the UE to perform CSI-RS measurements on: the UE is configured to measure a set of one or more symbols of the SSB thereon; a first symbol preceding the set of one or more symbols; and a second symbol subsequent to the set of one or more symbols. In another embodiment, in response to the indication indicating that the UE does not support the mixed parameter set, the method 100 further comprises: configuring SSB measurements to be performed by an unexpected UE on: the UE is configured to measure a set of one or more symbols of the CSI-RS thereon; a first symbol preceding the set of one or more symbols; and a second symbol subsequent to the set of one or more symbols. In another embodiment, the method 100 further comprises: in response to the indication that the UE does not support the hybrid parameter set, a scaling factor is used to divide the time resource allocation between CSI-RS based mobility measurements and SSB based mobility measurements.

In some embodiments, the indication indicates whether the UE supports both intra-frequency measurements for SSB with the first SCS and intra-frequency measurements for CSI-RS for mobility with the second SCS on a concurrent serving cell or neighboring cell, and the method 100 further comprises: at least one of the CSI-RS and the PDCCH or PDSCH is configured based on the indication. The indication may include, for example, a simultaneousCSIRSandSSB-DiffNumerology parameter in a set of UE capability parameters. In one such embodiment, in response to the indication indicating that the UE does not support the mixed parameter set, the method includes: configuring CSI-RS measurements to not expect the UE to perform CSI-RS measurements on: the UE is configured to measure a set of one or more symbols of the SSB thereon; a first symbol preceding the set of one or more symbols; and a second symbol subsequent to the set of one or more symbols. In another embodiment, the method 100 further comprises: in response to the indication indicating that the UE does not support the mixed parameter set, configuring SSB measurements to be expected to be performed by the unexpected UE on: the UE is configured to measure a set of one or more symbols of the CSI-RS thereon; a first symbol preceding the set of one or more symbols; and a second symbol subsequent to the set of one or more symbols. In another embodiment, in response to the indication that the UE does not support the hybrid parameter set, a scaling factor is used to divide the time resource allocation between CSI-RS based mobility measurements and SSB based mobility measurements.

In one embodiment, the indication indicates whether the UE supports intra-frequency measurements on CSI-RS for mobility using the first SCS on a concurrent serving cell or neighboring cell and PDCCH or PDSCH reception from the serving cell at the UE using the second SCS, and the method 100 further comprises: at least one of the CSI-RS and the PDCCH or PDSCH is configured based on the indication. The indication may include, for example, a simultaneousrxdata csirs-DiffNumerology parameter in a set of UE capability parameters. In one such embodiment, in response to the indication indicating that the UE does not support the mixed parameter set, the method 100 includes: the UE is not scheduled for PDCCH or PDSCH reception on: the UE is configured to measure a set of one or more symbols of the CSI-RS thereon; a first symbol preceding the set of one or more symbols; and a second symbol subsequent to the set of one or more symbols.

In some embodiments, the indication indicates whether the UE supports intra-frequency measurements on SSBs with the first SCS, intra-frequency measurements on CSI-RSs for mobility with the second SCS, and PDCCH or PDSCH reception from the serving cell at the UE with the third SCS on the concurrent serving cell or neighboring cells, and the method 100 further comprises: at least one of the CSI-RS and the PDCCH or PDSCH is configured based on the indication. The indication may include, for example, a simultaneousrxdata csirsandssb-DiffNumerology parameter in a set of UE capability parameters. In one such embodiment, in the first frequency range (FR 1), the method 100 further comprises: selecting a first SCS from a first group comprising 15kHz and 30kHz, and selecting a second SCS and a third SCS from a second group comprising 30kHz and 60 kHz; and in the second frequency range (FR 2), the first SCS is selected from a third set comprising 120kHz and 240kHz, and the second SCS and the third SCS are selected from a fourth set comprising 60kHz and 120 kHz. In some such embodiments, the first SCS, the second SCS, and the third SCS are selected to be three different SCS values. In one embodiment, the method 100 further comprises: in response to the indication that the UE does not support the mixed parameter set, the UE is not expected to perform operations of receiving data, measuring CSI-RS for mobility, and measuring SSB when these operations collide in the time domain and using different SCS values for the first SCS, the second SCS, and the third SCS.

Fig. 2 is a flow chart illustrating a method 200 for a UE in accordance with certain embodiments. In block 202, the method 200 includes: a message is generated to be sent to a base station in a wireless network. The message includes an indication of whether the UE supports a hybrid parameter set, wherein different SCS are used in the serving cell or in a neighboring cell to concurrently process at least two of: intra-frequency measurement of SSB by UE; intra-frequency measurement of CSI-RS for mobility by UE; and the UE receives PDCCH or PDSCH. In block 204, the method 200 includes: based on whether the UE supports the hybrid parameter set, when operations of receiving data from the serving cell, measuring CSI-RS for mobility, and measuring SSB collide in a time domain, one or more operations selected from these operations are performed.

In one embodiment of method 200, the serving cell is configured with at most two SCSs, wherein the SSB and CSI-RS for mobility share a first SCS of the two SCSs of the serving cell, and wherein the indication indicates whether the UE supports concurrency: intra-frequency measurement of SSB or CSI-RS for mobility by UE using first SCS; and reception of the PDCCH or the PDSCH from the serving cell by the UE using a second SCS of the two SCSs.

In one embodiment of the method 200, the serving cell is configured with at most two SCS, wherein the CSI-RS for mobility and the UE reception of PDCCH or PDSCH share a first SCS of the two SCS of the serving cell, and wherein the indication indicates whether the UE supports concurrency: intra-frequency measurement of SSB by UE using first SCS; and reception of the PDCCH or PDSCH from the serving cell by the UE or intra-frequency measurement of the CSI-RS for mobility by the UE using a second SCS of the two SCSs.

In one embodiment of the method 200, the indication indicates whether the UE supports both intra-frequency measurements for SSB with the first SCS and intra-frequency measurements for CSI-RS for mobility with the second SCS on concurrent serving or neighboring cells.

In one embodiment of the method 200, the indication indicates whether the UE supports intra-frequency measurements on CSI-RS for mobility with the first SCS on concurrent serving or neighboring cells and PDCCH or PDSCH reception from the serving cell at the UE with the second SCS.

In some embodiments of method 200, the indication indicates whether the UE supports intra-frequency measurements on SSBs with the first SCS, intra-frequency measurements on CSI-RS for mobility with the second SCS, and PDCCH or PDSCH reception from the serving cell at the UE with the third SCS on concurrent serving or neighboring cells. In some such embodiments, in a first frequency range (FR 1), the method 200 comprises: selecting a first SCS from a first group comprising 15kHz and 30kHz, and selecting a second SCS and a third SCS from a second group comprising 30kHz and 60 kHz; and in the second frequency range (FR 2), the first SCS is selected from a third set comprising 120kHz and 240kHz, and the second SCS and the third SCS are selected from a fourth set comprising 60kHz and 120 kHz. In certain embodiments, the first SCS, the second SCS, and the third SCS are selected to be three different SCS values.

Fig. 3 illustrates an exemplary architecture of a system 300 of a network in accordance with various embodiments. The following description is provided for an example system 300 that operates in conjunction with the LTE system standard and the 5G or NR system standard provided by the 3GPP technical specifications. However, the example embodiments are not limited in this regard and the embodiments may be applied to other networks that benefit from the principles described herein, such as future 3GPP systems (e.g., sixth generation (6G)) systems, IEEE 802.16 protocols (e.g., WMAN, wiMAX, etc.), and the like.

As shown in fig. 3, system 300 includes UE 322 and UE 320. In this example, UE 322 and UE 320 are shown as smart phones (e.g., handheld touch screen mobile computing devices connectable to one or more cellular networks), but may also include any mobile or non-mobile computing devices, such as consumer electronics devices, cellular phones, smart phones, functional handsets, tablet computers, wearable computer devices, personal Digital Assistants (PDAs), pagers, wireless handheld devices, desktop computers, laptop computers, in-vehicle infotainment (IVI), in-vehicle entertainment (ICE) devices, dashboards (ICs), heads-up display (HUD) devices, on-board diagnostic (OBD) devices, dashtop Mobile Equipment (DME), mobile Data Terminals (MDT), electronic Engine Management Systems (EEMS), electronic/Engine Control Units (ECU), electronic/Engine Control Modules (ECM), embedded systems, microcontrollers, control modules, engine Management Systems (EMS), networking or "smart" appliances, MTC devices, M2M, ioT devices, and the like.

In some embodiments, UE 322 and/or UE 320 may be IoT UEs that may include a network access layer designed for low power IoT applications that utilize short-term UE connections. IoT UEs may utilize technologies such as M2M or MTC to exchange data with MTC servers or devices via PLMN, proSe, or D2D communications, sensor networks, or IoT networks. The M2M or MTC data exchange may be a machine-initiated data exchange. IoT networks describe interconnected IoT UEs that may include uniquely identifiable embedded computing devices (within the internet infrastructure) with ephemeral connections. The IoT UE may execute a background application (e.g., keep-alive messages, status updates, etc.) to facilitate connection of the IoT network.

UE 322 and UE 320 may be configured to connect, e.g., communicatively couple, with AN access node or radio access node (shown as (R) AN 308). In AN embodiment, (R) AN 308 may be a NG RAN or SG RAN, E-UTRAN, or a legacy RAN, such as UTRAN or GERAN. As used herein, the term "NG RAN" or the like may refer to the (R) AN 308 operating in AN NR or SG system, and the term "E-UTRAN" or the like may refer to the (R) AN 308 operating in AN LTE or 4G system. UE 322 and UE 320 utilize connections (or channels) (shown as connection 304 and connection 302, respectively), each of which includes a physical communication interface or layer (discussed in further detail below).

In this example, connection 304 and connection 302 are air interfaces for enabling communicative coupling, and may conform to cellular communication protocols, such as GSM protocols, CDMA network protocols, PTT protocols, POC protocols, UMTS protocols, 3GPP LTE protocols, SG protocols, NR protocols, and/or any other communication protocols discussed herein. In an embodiment, UE 322 and UE 320 may also exchange communication data directly via ProSe interface 310. ProSe interface 310 may alternatively be referred to as Side Link (SL) interface 110 and may include one or more logical channels including, but not limited to PSCCH, PSSCH, PSDCH and PSBCH.

UE 320 is shown configured to access AP 312 (also referred to as a "WLAN node," "WLAN terminal," "WT," etc.) via connection 324. Connection 324 may comprise a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, where AP 312 would comprise wireless fidelity

And a router. In this example, the AP 312 may be connected to the internet without being connected to the core network of the wireless system (described in further detail below). In various embodiments, UE 320, (R) AN 308 and AP 312 may be configured to operate with LWA and/or LWIP. LWA operations may involve UEs 320 in rrc_connected being configured by RAN node 314 or RAN node 316 to utilize radio resources of LTE and WLAN. LWIP operations may involve UE 320 using WLAN radio resources (e.g., connection 324) to authenticate and encrypt packets (e.g., IP packets) sent over connection 324 via an IPsec protocol tunnel. IPsec tunneling may involve encapsulating the entire original IP packet and adding a new packet header, thereby protecting the original header of the IP packet.

(R) AN 308 may include one or more AN nodes, such as RAN node 314 and RAN node 316, that enable connection 304 and connection 302. As used herein, the terms "access node," "access point," and the like may describe equipment that provides radio baseband functionality for data and/or voice connections between a network and one or more users. These access nodes may be referred to as BS, gNB, RAN nodes, eNB, nodeB, RSU, TRxP or TRP, etc., and may include ground stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographic area (e.g., cell). As used herein, the term "NG RAN node" or the like may refer to a RAN node (e.g., a gNB) operating in an NR or SG system, while the term "E-UTRAN node" or the like may refer to a RAN node (e.g., an eNB) operating in an LTE or 4G system 300. According to various embodiments, RAN node 314 or RAN node 316 may be implemented as one or more of a dedicated physical device such as a macrocell base station and/or a Low Power (LP) base station for providing a femtocell, picocell, or other similar cell having a smaller coverage area, smaller user capacity, or higher bandwidth than a macrocell.

In some embodiments, all or part of RAN node 314 or RAN node 316 may be implemented as one or more software entities running on a server computer as part of a virtual network that may be referred to as a CRAN and/or virtual baseband unit pool (vbup). In these embodiments, the CRAN or vBBUP may implement RAN functionality partitioning, such as PDCP partitioning, where the RRC and PDCP layers are operated by the CRAN/vBBUP, while other L2 protocol entities are operated by respective RAN nodes (e.g., RAN node 314 or RAN node 316); MAC/PHY partitioning, where RRC, PDCP, RLC and MAC layers are operated by CRAN/vbup and PHY layers are operated by individual RAN nodes (e.g., RAN node 314 or RAN node 316); or "lower PHY" split, where RRC, PDCP, RLC, MAC layers and upper portions of the PHY layers are operated by CRAN/vBBUP and lower portions of the PHY layers are operated by the respective RAN nodes. The virtualization framework allows idle processor cores of RAN node 314 or RAN node 316 to execute other virtualized applications. In some implementations, a separate RAN node may represent a respective gNB-DU connected to the gNB-CU via a respective F1 interface (not shown in fig. 3). In these implementations, the gNB-DU may include one or more remote radio heads or RFEMs, and the gNB-CU may be operated by a server (not shown) located in the (R) AN 308 or by a server pool in a similar manner as the CRAN/vbBBUP. Additionally or alternatively, one or more of RAN node 314 or RAN node 316 may be a next generation eNB (NG-eNB), which is a RAN node that provides E-UTRA user plane and control plane protocol terminations to UE 322 and UE 320 and connects to an SGC via an NG interface (discussed below). In a V2X scenario, one or more of

RAN nodes

314 or 316 may be or act as an RSU.

The term "road side unit" or "RSU" may refer to any traffic infrastructure entity for V2X communication. The RSU may be implemented in or by a suitable RAN node or stationary (or relatively stationary) UE, wherein the RSU implemented in or by the UE may be referred to as a "UE-type RSU", the RSU implemented in or by the eNB may be referred to as an "eNB-type RSU", the RSU implemented in or by the gNB may be referred to as a "gNB-type RSU", etc. In one example, the RSU is a computing device coupled with radio frequency circuitry located on the road side that provides connectivity support to passing vehicle UEs (vues). The RSU may also include internal data storage circuitry for storing intersection map geometry, traffic statistics, media, and applications/software for sensing and controlling ongoing vehicle and pedestrian traffic. The RSU may operate over the 5.9GHz Direct Short Range Communication (DSRC) band to provide very low latency communications required for high speed events, such as crashes, traffic warnings, and the like. Additionally or alternatively, the RSU may operate on the cellular V2X frequency band to provide the aforementioned low-delay communications, as well as other cellular communication services. Additionally or alternatively, the RSU may operate as a Wi-Fi hotspot (2.4 GHz band) and/or provide connectivity to one or more cellular networks to provide uplink and downlink communications. Some or all of the radio frequency circuitry of the computing device and RSU may be packaged in a weather resistant package suitable for outdoor installation, and may include a network interface controller to provide a wired connection (e.g., ethernet) with a traffic signal controller and/or a backhaul network.

RAN node 314 and/or RAN node 316 may terminate the air interface protocol and may be the first point of contact for UE 322 and UE 320. In some embodiments, RAN node 314 and/or RAN node 316 may perform various logical functions of (R) AN 308, including but not limited to Radio Network Controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.

In an embodiment, UE 322 and UE 320 may be configured to communicate with each other or RAN node 314 and/or RAN node 316 over a multicarrier communication channel using OFDM communication signals in accordance with various communication techniques such as, but not limited to, OFDMA communication techniques (e.g., for downlink communications) or SC-FDMA communication techniques (e.g., for uplink and ProSe or side-link communications), although the scope of the embodiments is not limited in this respect. The OFDM signal may comprise a plurality of orthogonal subcarriers.

In some embodiments, the downlink resource grid may be used for downlink transmissions from RAN node 314 and/or RAN node 316 to UE 322 and UE 320, while uplink transmissions may utilize similar techniques. The grid may be a time-frequency grid, referred to as a resource grid or time-frequency resource grid, which is a physical resource in the downlink in each time slot. For OFDM systems, such time-frequency plane representation is common practice, which makes radio resource allocation intuitive. Each column and each row of the resource grid corresponds to one OFDM symbol and one OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to one slot in the radio frame. The smallest time-frequency unit in the resource grid is denoted as a resource element. Each resource grid includes a plurality of resource blocks that describe the mapping of certain physical channels to resource elements. Each resource block includes a set of resource elements; in the frequency domain, this may represent the minimum amount of resources that can be currently allocated. Several different physical downlink channels are transmitted using such resource blocks.

According to various embodiments,

UEs

322 and 320 and RAN node 314 and/or RAN node 316 transmit (e.g., transmit and receive) data over a licensed medium (also referred to as "licensed spectrum" and/or "licensed band") and an unlicensed shared medium (also referred to as "unlicensed spectrum" and/or "unlicensed band"). The licensed spectrum may include channels operating in a frequency range of about 400MHz to about 3.8GHz, while the unlicensed spectrum may include the 5GHz band.

To operate in unlicensed spectrum,

UEs

322 and 320 and RAN node 314 or RAN node 316 may operate using LAA, eLAA, and/or feLAA mechanisms. In these implementations,

UEs

322 and 320 and RAN node 314 or RAN node 316 may perform one or more known media sensing operations and/or carrier sensing operations to determine whether one or more channels in the unlicensed spectrum are unavailable or otherwise occupied prior to transmission in the unlicensed spectrum. The medium/carrier sensing operation may be performed according to a Listen Before Talk (LBT) protocol.

LBT is a mechanism by which equipment (e.g., UE 322 and UE 320, RAN node 314 or RAN node 316, etc.) senses a medium (e.g., a channel or carrier frequency) and transmits when the medium is sensed to be idle (or when a particular channel in the medium is sensed to be unoccupied). The medium sensing operation may include a CCA that utilizes at least the ED to determine whether other signals are present on the channel in order to determine whether the channel is occupied or idle. The LBT mechanism allows the cellular/LAA network to coexist with existing systems in the unlicensed spectrum and with other LAA networks. The ED may include sensing RF energy over an expected transmission band for a period of time, and comparing the sensed RF energy to a predefined or configured threshold.

In general, existing systems in the 5GHz band are WLANs based on IEEE 802.11 technology. WLAN employs a contention-based channel access mechanism called CSMA/CA. Here, when a WLAN node (e.g., a Mobile Station (MS) such as UE 322, AP 312, etc.) intends to transmit, the WLAN node may first perform CCA prior to transmitting. In addition, in the case where more than one WLAN node senses the channel as idle and transmits simultaneously, a backoff mechanism is used to avoid collisions. The backoff mechanism may be a counter that is randomly introduced within the CWS, increases exponentially when a collision occurs, and resets to a minimum when the transmission is successful. The LBT mechanism designed for LAA is somewhat similar to CSMA/CA for WLAN. In some implementations, the LBT procedure of DL or UL transmission bursts (including PDSCH or PUSCH transmissions) may have LAA contention window of variable length between X and Y ECCA slots, where X and Y are the minimum and maximum values of the CWS of the LAA. In one example, the minimum CWS for LAA transmission may be 9 microseconds (μs); however, the size of the CWS and the MCOT (e.g., transmission burst) may be based on government regulatory requirements.

The LAA mechanism is built on the CA technology of the LTE-Advanced system. In CA, each aggregated carrier is referred to as a CC. One CC may have a bandwidth of 1.4, 3, 5, 10, 15, or 20MHz, and a maximum of five CCs may be aggregated, so the maximum aggregate bandwidth is 100MHz. In an FDD system, the number of aggregated carriers may be different for DL and UL, where the number of UL CCs is equal to or lower than the number of DL component carriers. In some cases, each CC may have a different bandwidth than other CCs. In a TDD system, the number of CCs and the bandwidth of each CC are typically the same for DL and UL.

The CA also includes individual serving cells to provide individual CCs. The coverage of the serving cell may be different, for example, because CCs on different frequency bands will experience different path losses. The primary serving cell or PCell may provide PCC for both UL and DL and may handle RRC and NAS related activities. Other serving cells are referred to as scells, and each SCell may provide a respective SCC for both UL and DL. SCCs may be added and removed as needed, while changing PCC may require UE 322 to undergo a handover. In LAA, eLAA, and feLAA, some or all of the scells may operate in unlicensed spectrum (referred to as "LAA SCell"), and the LAA SCell is assisted by a PCell operating in licensed spectrum. When the UE is configured with more than one LAA SCell, the UE may receive a UL grant on the configured LAA SCell indicating different PUSCH starting locations within the same subframe.

PDSCH carries user data and higher layer signaling to UE 322 and UE 320. The PDCCH carries, among other information, information about transport formats and resource allocations related to the PDSCH channel. It may also inform UE 322 and UE 320 about transport format, resource allocation and HARQ information related to the uplink shared channel. In general, downlink scheduling (allocation of control and shared channel resource blocks to UEs 320 within a cell) may be performed at either RAN node 314 or RAN node 316 based on channel quality information fed back from either UE 322 and UE 320. The downlink resource allocation information may be sent on a PDCCH for (e.g., allocated to) each of the UE 322 and the UE 320.

The PDCCH transmits control information using CCEs. The PDCCH complex-valued symbols may first be organized into quadruples before being mapped to resource elements, and then may be aligned for rate matching using a sub-block interleaver. Each PDCCH may be transmitted using one or more of these CCEs, where each CCE may correspond to nine sets of four physical resource elements, respectively, referred to as REGs. Four Quadrature Phase Shift Keying (QPSK) symbols may be mapped to each REG. Depending on the size of the DCI and the channel conditions, the PDCCH may be transmitted using one or more CCEs. There may be four or more different PDCCH formats defined in LTE with different numbers of CCEs (e.g., aggregation level, l=1, 2, 4, or 8).

Some embodiments may use the concept of resource allocation for control channel information, which is an extension of the above described concept. For example, some embodiments may utilize EPDCCH using PDSCH resources for control information transmission. The EPDCCH may be transmitted using one or more ECCEs. Similar to the above, each ECCE may correspond to nine sets of four physical resource elements, referred to as EREGs. In some cases, ECCEs may have other amounts of EREGs.

RAN node 314 or RAN node 316 may be configured to communicate with each other via interface 330. In embodiments where system 300 is an LTE system (e.g., when CN 306 is an EPC), interface 330 may be an X2 interface. The X2 interface may be defined between two or more RAN nodes (e.g., two or more enbs, etc.) connected to the EPC and/or between two enbs connected to the EPC. In some implementations, the X2 interface may include an X2 user plane interface (X2-U) and an X2 control plane interface (X2-C). The X2-U may provide a flow control mechanism for user packets transmitted over the X2 interface and may be used to communicate information regarding the delivery of user data between enbs. For example, X2-U may provide specific sequence number information about user data transmitted from the MeNB to the SeNB; information regarding successful in-sequence delivery of PDCP PDUs from the SeNB to the UE 322 for user data; PDCP PDU information not delivered to the UE 322; information about a current minimum expected buffer size at the Se NB for transmitting user data to the UE; etc. X2-C may provide LTE access mobility functions including context transfer from source eNB to target eNB, user plane transfer control, etc.; a load management function; inter-cell interference coordination function.

In embodiments where system 300 is an SG or NR system (e.g., when CN 306 is an SGC), interface 330 may be an Xn interface. An Xn interface is defined between two or more RAN nodes (e.g., two or more gnbs, etc.) connected to the SGC, between a RAN node 314 (e.g., a gNB) connected to the SGC and an eNB, and/or between two enbs connected to a 5GC (e.g., CN 306). In some implementations, the Xn interface can include an Xn user plane (Xn-U) interface and an Xn control plane (Xn-C) interface. Xn-U may provide non-guaranteed delivery of user plane PDUs and support/provide data forwarding and flow control functions. An Xn-C may provide management and error handling functions for managing the functions of the Xn-C interface; mobility support for UE 322 in CONNECTED mode (e.g., CM-CONNECTED) includes functionality for managing UE mobility in CONNECTED mode between one or more RAN nodes 314 or RAN nodes 316. Mobility support may include context transfer from the old (source) serving RAN node 314 to the new (target) serving RAN node 316, and control of user plane tunnels between the old (source) serving RAN node 314 to the new (target) serving RAN node 316. The protocol stack of an Xn-U may include a transport network layer built on top of an Internet Protocol (IP) transport layer, and a GTP-U layer on top of a UDP and/or IP layer for carrying user plane PDUs. The Xn-C protocol stack may include an application layer signaling protocol, referred to as the Xn application protocol (Xn-AP), and a transport network layer built on SCTP. SCTP may be on top of the IP layer and may provide guaranteed delivery of application layer messages. In the transport IP layer, signaling PDUs are delivered using point-to-point transport. In other implementations, the Xn-U protocol stack and/or the Xn-C protocol stack may be the same or similar to the user plane and/or control plane protocol stacks shown and described herein.

The (R) AN 308 is shown communicatively coupled to the core network-in this embodiment, the CN 306. The CN 306 may include one or more network elements 332 configured to provide various data and telecommunications services to clients/subscribers (e.g., users of the UEs 322 and 320) connected to the CN 306 via the (R) AN 308. The components of the CN 306 may be implemented in one physical node or in a separate physical node, including components for reading and executing instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium). In some embodiments, NFV may be used to virtualize any or all of the above-described network node functions via executable instructions stored in one or more computer-readable storage media (described in further detail below). The logical instantiation of the CN 306 may be referred to as a network slice, and the logical instantiation of a portion of the CN 306 may be referred to as a network sub-slice. NFV architecture and infrastructure can be used to virtualize one or more network functions onto physical resources (alternatively performed by proprietary hardware) that include industry standard server hardware, storage hardware, or a combination of switches. In other words, NFV systems may be used to perform virtual or reconfigurable implementations of one or more EPC components/functions.

Generally, the application server 318 may be an element that provides applications (e.g., UMTS PS domain, LTE PS data services, etc.) that use IP bearer resources with the core network. The application server 318 may also be configured to support one or more communication services (e.g., voIP session, PTT session, group communication session, social network service, etc.) for the UE 322 and UE 320 via the EPC. The application server 318 may communicate with the CN 306 through an IP communication interface 336.

In AN embodiment, the CN 306 may be AN SGC and the (R) AN 116 may be connected with the CN 306 via AN NG interface 334. In an embodiment, NG interface 334 may be split into two parts: a NG user plane (NG-U) interface 326 that carries traffic data between RAN node 314 or RAN node 316 and the UPF; and an S1 control plane (NG-C) interface 328, which is a signaling interface between RAN node 314 or RAN node 316 and the AMF.

In embodiments, the CN 306 may be an SG CN, while in other embodiments, the CN 306 may be an EPC. In the case where the CN 306 is EPC, (R) AN 116 may connect with the CN 306 via S1 interface 334. In an embodiment, the S1 interface 334 may be split into two parts: an S1 user plane (S1-U) interface 326 that carries traffic data between the RAN node 314 or the RAN node 316 and the S-GW; and an S1-MME interface 328, which is a signaling interface between the RAN node 314 or the RAN node 316 and the MME.

Fig. 4 illustrates an example of infrastructure equipment 400, in accordance with various embodiments. Infrastructure equipment 400 may be implemented as a base station, a radio head, a RAN node, AN, AN application server, and/or any other element/device discussed herein. In other examples, the infrastructure equipment 400 may be implemented in or by a UE.

Infrastructure equipment 400 includes application circuitry 402, baseband circuitry 404, one or more radio front end modules 406 (RFEM), memory circuitry 408, power management integrated circuitry (shown as PMIC 410), power tee circuitry 412, network controller circuitry 414, network interface connector 420, satellite positioning circuitry 416, and user interface circuitry 418. In some implementations, the infrastructure equipment 400 may include additional elements, such as memory/storage devices, displays, cameras, sensors, or input/output (I/O) interfaces. In other embodiments, these components may be included in more than one device. For example, the circuitry may be included solely in more than one device for CRAN, vBBU, or other similar implementations. Application circuitry 402 includes one or more low dropout regulators such as, but not limited to, one or more processors (or processor cores), cache memory, and low dropout regulators (LDOs), interrupt controllers, serial interfaces such as SPI, I ² A C or universal programmable serial interface module, a Real Time Clock (RTC), a timer-counter including an interval timer and a watchdog timer, a universal input/output (I/O or IO), a memory card controller such as a Secure Digital (SD) multimedia card (MMC) or similar product, a Universal Serial Bus (USB) interface, a Mobile Industry Processor Interface (MIPI), and a Joint Test Access Group (JTAG) test access port. The processor (or core) of the application circuit 402 may be coupled with or may include memory/storage elements and may be configured to execute instructions stored in the memory/storage to enable various applications or operating systems to be provided at the infrastructure equipment 4Run on 00. In some implementations, the memory/storage elements may be on-chip memory circuitry that may include any suitable volatile and/or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, flash memory, solid state memory, and/or any other type of memory device technology, such as those discussed herein.

The processors of application circuitry 402 may include, for example, one or more processor Cores (CPUs), one or more application processors, one or more Graphics Processing Units (GPUs), one or more Reduced Instruction Set Computing (RISC) processors, one or more Acorn RISC Machine (ARM) processors, one or more Complex Instruction Set Computing (CISC) processors, one or more Digital Signal Processors (DSPs), one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, or any suitable combination thereof. In some embodiments, the application circuitry 402 may include or may be a dedicated processor/controller for operation according to various embodiments herein. As an example, the processor of application circuit 402 may include one or more Intel' s

Or->

A processor; advanced Micro Devices (AMD)>

Processor, acceleration Processing Unit (APU) or +.>

A processor; ARM holders, ltd. Authorized ARM-based processors, such as ARM Cortex-A series processors and +.>

MIPS-based designs from MIPS Technologies, inc, such as MIPS Warrior P-stage processors; etcEtc. In some embodiments, the infrastructure equipment 400 may not utilize the application circuitry 402 and may instead include a dedicated processor/controller to process IP data received from, for example, the EPC or 5 GC.

In some implementations, the application circuitry 402 may include one or more hardware accelerators, which may be microprocessors, programmable processing devices, or the like. The one or more hardware accelerators may include, for example, computer Vision (CV) and/or Deep Learning (DL) accelerators. For example, the programmable processing device may be one or more Field Programmable Devices (FPDs), such as a Field Programmable Gate Array (FPGA), or the like; programmable Logic Devices (PLDs), such as Complex PLDs (CPLDs), high-capacity PLDs (HCPLDs), and the like; an ASIC, such as a structured ASIC; a programmable SoC (PSoC); etc. In such implementations, the circuitry of application circuitry 402 may include logic blocks or logic frameworks, as well as other interconnection resources that may be programmed to perform various functions, such as the procedures, methods, functions, etc., of the various embodiments discussed herein. In such implementations, the circuitry of application circuitry 402 may include memory cells (e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, static memory (e.g., static Random Access Memory (SRAM), antifuse, etc)) for storing logic blocks, logic frameworks, data, etc. in a look-up table (LUT), etc. The baseband circuitry 404 may be implemented, for example, as a solder-in substrate that includes one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board, or a multi-chip module containing two or more integrated circuits.

The user interface circuitry 418 may include one or more user interfaces designed to enable a user to interact with the infrastructure equipment 400 or a peripheral component interface designed to enable a peripheral component to interact with the infrastructure equipment 400. The user interface may include, but is not limited to, one or more physical or virtual buttons (e.g., a reset button), one or more indicators (e.g., light Emitting Diodes (LEDs)), a physical keyboard or keypad, a mouse, a touch pad, a touch screen, a speaker or other audio emitting device, a microphone, a printer, a scanner, a headset, a display screen or display device, and the like. Peripheral component interfaces may include, but are not limited to, non-volatile memory ports, universal Serial Bus (USB) ports, audio jacks, power interfaces, and the like.

Radio front-end module 406 may include a millimeter wave (mmWave) radio front-end module (RFEM) and one or more sub-millimeter wave Radio Frequency Integrated Circuits (RFICs). In some implementations, the one or more sub-millimeter wave RFICs may be physically separate from the millimeter wave RFEM. The RFIC may include connections to one or more antennas or antenna arrays, and the RFEM may be connected to multiple antennas. In alternative implementations, the radio functions of both millimeter wave and sub-millimeter wave may be implemented in the same physical radio front-end module 406 that incorporates both millimeter wave antennas and sub-millimeter wave.

The memory circuitry 408 may include one or more of the following: volatile memory including Dynamic Random Access Memory (DRAM) and/or Synchronous Dynamic Random Access Memory (SDRAM), non-volatile memory (NVM) including high-speed electrically erasable memory (commonly referred to as "flash memory"), phase-change random access memory (PRAM), magnetoresistive Random Access Memory (MRAM), and the like, and may be combined

And->

Three-dimensional (3D) cross-point (XPOINT) memory. The memory circuit 408 may be implemented as one or more of the following: solder-in package integrated circuits, socket memory modules, and plug-in memory cards.

The PMIC 410 may include a voltage regulator, a surge protector, a power alert detection circuit, and one or more backup power sources, such as a battery or a capacitor. The power alert detection circuit may detect one or more of a power down (under voltage) and surge (over voltage) condition. The power tee circuit 412 may provide power extracted from the network cable to use a single cable to provide both power and data connections for the infrastructure equipment 400.

The network controller circuit 414 may provide connectivity to the network using standard network interface protocols such as Ethernet, GRE tunnel-based Ethernet, multiprotocol label switching (MPLS) based Ethernet, or some other suitable protocol. The network connection may be provided to/from the infrastructure equipment 400 via the network interface connector 420 using a physical connection, which may be an electrical connection (commonly referred to as a "copper interconnect"), an optical connection, or a wireless connection. The network controller circuit 414 may include one or more dedicated processors and/or FPGAs for communicating using one or more of the foregoing protocols. In some implementations, the network controller circuit 414 may include multiple controllers for providing connections to other networks using the same or different protocols.

The positioning circuitry 416 includes circuitry to receive and decode signals transmitted/broadcast by a positioning network of a Global Navigation Satellite System (GNSS). Examples of navigation satellite constellations (or GNSS) include the Global Positioning System (GPS) of the united states, the global navigation system (GLONASS) of russia, the galileo system of the european union, the beidou navigation satellite system of china, the regional navigation system or GNSS augmentation system (e.g., navigation using the indian constellation (NAVIC), the quasi-zenith satellite system (QZSS) of japan, the doppler orbit map of france, satellite integrated radio positioning (DORIS) and so on). The positioning circuitry 416 includes various hardware elements (e.g., including hardware devices such as switches, filters, amplifiers, antenna elements, etc. for facilitating OTA communications) to communicate with components of the positioning network such as navigation satellite constellation nodes. In some implementations, the positioning circuitry 416 may include a micro-technology (micro PNT) IC for positioning, navigation, and timing that performs position tracking/estimation using a master timing clock without GNSS assistance. The positioning circuitry 416 may also be part of or interact with the baseband circuitry 404 and/or the radio front end module 406 to communicate with nodes and components of a positioning network. The positioning circuitry 416 may also provide location data and/or time data to the application circuitry 402, which may use the data to synchronize operations with various infrastructures, etc. The components shown in FIG. 4 may communicate with each other using interface circuitry The interface circuitry may include any number of bus and/or Interconnect (IX) technologies, such as Industry Standard Architecture (ISA), enhanced ISA (EISA), peripheral Component Interconnect (PCI), peripheral component interconnect extensions (PCix), PCI express (PCie), or any number of other technologies. The bus/IX may be a proprietary bus, for example, for use in SoC based systems. Other bus/IX systems may be included such as I ² C interface, SPI interface, point-to-point interface, and power bus, among others.

Fig. 5 illustrates an example of a platform 500 according to various embodiments. In embodiments, the computer platform 500 may be adapted to function as a UE, an application server, and/or any other element/device discussed herein. Platform 500 may include any combination of the components shown in the examples. The components of platform 500 may be implemented as Integrated Circuits (ICs), portions of ICs, discrete electronic devices, or other modules adapted in computer platform 500, logic, hardware, software, firmware, or combinations thereof, or as components otherwise incorporated within the chassis of a larger system. The block diagram of fig. 5 is intended to illustrate a high-level view of the components of computer platform 500. However, some of the illustrated components may be omitted, additional components may be present, and different arrangements of the illustrated components may occur in other implementations.

Application circuitry 502 includes circuitry such as, but not limited to, one or more processors (or processor cores), cache memory, and LDOs, interrupt controllers, serial interfaces (such as SPIs), I ² C or one or more of a universal programmable serial interface module, RTC, timer (including interval timer and watchdog timer), universal I/O, memory card controller (such as SD MMC or similar controller), USB interface, MIPI interface, and JTAG test access port. The processor (or core) of the application circuitry 502 may be coupled with or may include memory/storage elements and may be configured to execute instructions stored in the memory/storage elements to enable various applications or operating systems to run on the platform 500. In some implementations, the memory/storage element may be an on-chip memory circuit that may include any suitable volatile and/or non-volatile memorySuch as DRAM, SRAM, EPROM, EEPROM, flash memory, solid state memory, and/or any other type of memory device technology, such as those discussed herein.

The processor of application circuitry 502 may include, for example, one or more processor cores, one or more application processors, one or more GPUs, one or more RISC processors, one or more ARM processors, one or more CISC processors, one or more DSPs, one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, a multi-threaded processor, an ultra-low voltage processor, an embedded processor, some other known processing elements, or any suitable combination thereof. In some embodiments, the application circuitry 502 may include or may be a dedicated processor/controller for operation according to various embodiments herein.

As an example, the processor of the application circuit 502 may include a processor based on

Architecture Core ^TM Such as a Quark ^TM 、Atom ^TM I3, i5, i7 or MCU-level processor, or are available from +.>

Another such processor of the company. The processor of the application circuit 502 may also be one or more of the following: advanced Micro Devices (AMD)>

A processor or an Acceleration Processing Unit (APU); from->

AS-A9 processor from Inc

Snapdragon from Technologies, inc ^TM Processor, texas Instruments, ">

Open Multimedia Applications Platform(OMAP) ^TM A processor; MIPS-based designs from MIPS Technologies, inc, such as MIPS Warrior M stage, warrior I stage, and Warrior P stage processors; ARM-based designs, such as ARM Cortex-A, cortex-R and Cortex-M series processors, that obtain ARM holders, ltd. Permissions; etc. In some implementations, application circuit 502 may be part of a system on a chip (SoC), where application circuit 502 and other components are formed as a single integrated circuit or a single package, such as that obtained from +.>

Edison from Corporation ^TM Or Galileo ^TM SoC board.

Additionally or alternatively, the application circuitry 502 may include circuitry such as, but not limited to, one or more Field Programmable Devices (FPDs) such as FPGAs, or the like; programmable Logic Devices (PLDs), such as Complex PLDs (CPLDs), high-capacity PLDs (HCPLDs), and the like; an ASIC, such as a structured ASIC; a programmable SoC (PSoC); etc. In such embodiments, the circuitry of application circuitry 502 may include logic blocks or logic frameworks, as well as other interconnect resources that may be programmed to perform various functions, such as the processes, methods, functions, etc., of the various embodiments discussed herein. In such implementations, the circuitry of application circuitry 502 may include memory cells (e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, static memory (e.g., static Random Access Memory (SRAM), antifuse, etc)) for storing logic blocks, logic frameworks, data, etc. in a look-up table (LUT), etc.

The baseband circuitry 504 may be implemented, for example, as a solder-in substrate that includes one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board, or a multi-chip module containing two or more integrated circuits.

Radio front-end module 506 may include a millimeter wave (mmWave) radio front-end module (RFEM) and one or more sub-millimeter wave Radio Frequency Integrated Circuits (RFICs). In some implementations, the one or more sub-millimeter wave RFICs may be physically separate from the millimeter wave RFEM. The RFIC may include connections to one or more antennas or antenna arrays, and the RFEM may be connected to multiple antennas. In alternative implementations, the radio functions of both millimeter wave and sub-millimeter wave may be implemented in the same physical radio front-end module 506 that incorporates both millimeter wave antennas and sub-millimeter wave.

The memory circuitry 508 may include any number and type of memory devices for providing a given amount of system memory. For example, the memory circuit 508 may include one or more of the following: volatile memory including Random Access Memory (RAM), dynamic RAM (DRAM), and/or synchronous dynamic RAM (SD RAM); and nonvolatile memory (NVM), which includes high-speed electrically erasable memory (commonly referred to as flash memory), phase change random access memory (PRAM), magnetoresistive Random Access Memory (MRAM), and the like. The memory circuit 508 may be developed in accordance with a Joint Electronic Device Engineering Council (JEDEC) Low Power Double Data Rate (LPDDR) based design such as LPDDR2, LPDDR3, LPDDR4, etc. The memory circuit 508 may be implemented as one or more of the following: solder-in package integrated circuits, single Die Packages (SDPs), dual Die Packages (DDPs) or quad die packages (Q17P), socket memory modules, dual in-line memory modules (DIMMs) including micro DIMMs or mini DIMMs, and/or soldered to a motherboard via a Ball Grid Array (BGA). In a low power implementation, the memory circuit 508 may be an on-chip memory or register associated with the application circuit 502. To provide persistent storage of information, such as data, applications, operating systems, etc., the memory circuit 508 may include one or more mass storage devices, which may include, among other things, a Solid State Disk Drive (SSDD), a Hard Disk Drive (HDD), a micro HDD, a resistance change memory, a phase change memory, a holographic memory, or a chemical memory. For example, computer platform 500 may be obtained in connection with a computer system

And->

Three-dimensional (3D) cross-point (XPOINT) memory.

Removable memory circuit 526 may include devices, circuits, housings/casings, ports or sockets, etc. for coupling the portable data storage device to platform 500. These portable data storage devices may be used for mass storage and may include, for example, flash memory cards (e.g., secure Digital (SD) cards, micro SD cards, xD picture cards, etc.), as well as USB flash drives, optical disks, external HDDs, etc.

Platform 500 may also include interface circuitry (not shown) for connecting external devices to platform 500. External devices connected to platform 500 via the interface circuitry include sensors 522 and electromechanical components (shown as EMC 524), as well as removable memory devices coupled to removable memory 526.

The sensor 522 includes a device, module, or subsystem that is aimed at detecting an event or change in its environment, and transmits information (sensor data) about the detected event to some other device, module, subsystem, or the like. Examples of such sensors include, inter alia: an Inertial Measurement Unit (IMU) comprising an accelerometer, gyroscope and/or magnetometer; microelectromechanical Systems (MEMS) or nanoelectromechanical systems (NEMS) including triaxial accelerometers, triaxial gyroscopes and/or magnetometers; a liquid level sensor; a flow sensor; a temperature sensor (e.g., a thermistor); a pressure sensor; an air pressure sensor; a gravimeter; a height gauge; an image capturing device (e.g., a camera or a lens-free aperture); light detection and ranging (LiDAR) sensors; proximity sensors (e.g., infrared radiation detectors, etc.), depth sensors, ambient light sensors, ultrasonic transceivers; a microphone or other similar audio capturing device; etc.

EMC 524 includes devices, modules or subsystems that are intended to enable platform 500 to change its state, position and/or orientation or to move or control a mechanism or (subsystem). In addition, EMC 524 may be configured to generate and send messages/signaling to other components of platform 500 to indicate the current state of EMC 524. Examples of EMC 524 include one or more power switches, relays (including electromechanical relays (EMR) and/or Solid State Relays (SSR)), actuators (e.g., valve actuators, etc.), audible sound generators, visual warning devices, motors (e.g., DC motors, stepper motors, etc.), wheels, propellers, claws, clamps, hooks, and/or other similar electromechanical components. In an embodiment, the platform 500 is configured to operate one or more EMCs 524 based on one or more capture events and/or instructions or control signals received from service providers and/or various clients. In some implementations, interface circuitry may connect the platform 500 with positioning circuitry 516. The positioning circuitry 516 includes circuitry for receiving and decoding signals transmitted/broadcast by a positioning network of a GNSS. Examples of navigation satellite constellations (or GNSS) may include GPS in the united states, GLONASS in russia, galileo system in the european union, beidou navigation satellite system in china, regional navigation system or GNSS augmentation system (e.g., NAVIC, QZSS in japan, DORIS in france, etc.), etc. The positioning circuitry 516 includes various hardware elements (e.g., including hardware devices such as switches, filters, amplifiers, antenna elements, etc. for facilitating OTA communications) to communicate with components of the positioning network such as navigation satellite constellation nodes. In some implementations, the positioning circuitry 516 may include a mini-PNT IC that performs position tracking/estimation using a master timing clock without GNSS assistance. The positioning circuitry 516 may also be part of or interact with the baseband circuitry 504 and/or the radio front end module 506 to communicate with nodes and components of a positioning network. The positioning circuit 516 may also provide location data and/or time data to the application circuit 502, which may use the data to synchronize operation with various infrastructure (e.g., radio base stations) for turn-by-turn navigation applications, etc.

In some implementations, the interface circuit may connect the platform 500 with near field communication circuitry (shown as NFC circuitry 512). NFC circuit 512 is configured to provide contactless proximity communication based on Radio Frequency Identification (RFID) standards, wherein magnetic field induction is used to enable communication between NFC circuit 512 and NFC-enabled devices (e.g., an "NFC contact point") external to platform 500. NFC circuit 512 includes an NFC controller coupled with the antenna element and a processor coupled with the NFC controller. The NFC controller may be a chip/IC that provides NFC functionality to NFC circuit 512 by executing NFC controller firmware and an NFC stack. The NFC stack may be executable by the processor to control the NFC controller, and the NFC controller firmware may be executable by the NFC controller to control the antenna element to transmit the short range RF signal. The RF signal may power a passive NFC tag (e.g., a microchip embedded in a sticker or wristband) to transfer stored data to NFC circuit 512 or initiate a data transfer between NFC circuit 512 and another active NFC device (e.g., a smart phone or NFC-enabled POS terminal) proximate to platform 500.

The drive circuitry 518 may include software elements and hardware elements for controlling particular devices embedded in the platform 500, attached to the platform 500, or otherwise communicatively coupled with the platform 500. The drive circuitry 518 may include various drivers to allow other components of the platform 500 to interact with or control various input/output (I/O) devices that may be present within or connected to the platform 500. For example, the drive circuit 518 may include a display driver for controlling and allowing access to a display device, a touch screen driver for controlling and allowing access to a touch screen interface of the platform 500, a sensor driver for obtaining sensor readings and controlling of the sensor 522 and allowing access to the sensor 522, an EMC driver for obtaining actuator positions and/or controlling of the EMC 524 and allowing access to the EMC 524, a camera driver for controlling and allowing access to an embedded image capture device, and an audio driver for controlling and allowing access to one or more audio devices.

A power management integrated circuit (shown as PMIC 510) (also referred to as a "power management circuit") may manage the power provided to the various components of platform 500. In particular, the pmic 510 may control power supply selection, voltage scaling, battery charging, or DC-DC conversion relative to the baseband circuitry 504. The PMIC 510 may generally be included when the platform 500 is capable of being powered by the battery 514, for example, when the device is included in a UE.

In some embodiments, PMIC 510 may control or otherwise be part of the various power saving mechanisms of platform 500. For example, if the platform 500 is in an RRC Connected state in which the platform is still Connected to the RAN node because it is expected to receive traffic soon, after a period of inactivity, the platform may enter a state called discontinuous reception mode (DRX). During this state, the platform 500 may be powered down for a short time interval, thereby saving power. If there is no data traffic activity for an extended period of time, the platform 500 may transition to an RRC_Idle state in which the device is disconnected from the network and no operations such as channel quality feedback, switching, etc. are performed by the platform 500 into a very low power state and paging is performed in which the device wakes up again periodically to listen to the network and then powers down again. The platform 500 may not receive data in this state; in order to receive data, the platform must transition back to the rrc_connected state. The additional power saving mode may cause the device to fail to use the network for more than a paging interval (varying from seconds to hours). During this time, the device is not connected to the network at all and may be powered off at all. Any data transmitted during this period causes a significant delay and the delay is assumed to be acceptable.

The battery 514 may power the platform 500, but in some examples, the platform 500 may be mounted in a fixed location and may have a power source coupled to a power grid. The battery 514 may be a lithium ion battery, a metal-air battery such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, or the like. In some implementations, such as in V2X applications, the battery 514 may be a typical lead-acid automotive battery.

In some implementations, the battery 514 may be a "smart battery" that includes or is coupled to a Battery Management System (BMS) or battery monitoring integrated circuit. A BMS may be included in the platform 500 to track the state of charge (SoCh) of the battery 514. The BMS may be used to monitor other parameters of the battery 514, such as the state of health (SoH) and the state of function (SoF) of the battery 514 to provide a fault prediction. The BMS may communicate information of the battery 514 to the application circuitry 502 or other components of the platform 500. The BMS may also include an analog-to-digital (ADC) converter that allows the application circuitry 502 to directly monitor the voltage of the battery 514 or the current from the battery 514. The battery parameters may be used to determine actions that the platform 500 may perform, such as transmission frequency, network operation, sensing frequency, and the like.

A power block or other power source coupled to the power grid may be coupled with the BMS to charge the battery 514. In some examples, the power block may be replaced with a wireless power receiver to wirelessly draw power, for example, through a loop antenna in computer platform 500. In these examples, the wireless battery charging circuit may be included in the BMS. The particular charging circuit selected may depend on the size of the battery 514 and, thus, the current required. The charging may be performed using aviation fuel standards promulgated by the aviation fuel alliance, qi wireless charging standards promulgated by the wireless power alliance, or Rezence charging standards promulgated by the wireless power alliance.

User interface circuitry 520 includes various input/output (I/O) devices present within or connected to platform 500 and includes one or more user interfaces designed to enable user interaction with platform 500 and/or peripheral component interfaces designed to enable peripheral component interaction with platform 500. The user interface circuitry 520 includes input device circuitry and output device circuitry. The input device circuitry includes any physical or virtual means for accepting input, including, inter alia, one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a touch pad, a touch screen, a microphone, a scanner, a headset, and the like. Output device circuitry includes any physical or virtual means for displaying information or otherwise conveying information, such as sensor readings, actuator positions, or other similar information. The output device circuitry may include any number and/or combination of audio or visual displays, including, inter alia, one or more simple visual outputs/indicators, such as binary status indicators (e.g., light Emitting Diodes (LEDs)) and multi-character visual outputs, or more complex outputs, such as display devices or touch screens (e.g., liquid Crystal Displays (LCDs), LED displays, quantum dot displays, projectors, etc.), wherein the output of characters, graphics, multimedia objects, etc. is generated or produced by operation of the platform 500. The output device circuitry may also include speakers or other audio emitting devices, printers, etc. In some implementations, the sensor 522 may be used as an input device circuit (e.g., an image capture device, a motion capture device, etc.) and one or more EMCs may be used as an output device circuit (e.g., an actuator for providing haptic feedback, etc.). In another example, an NFC circuit may be included to read an electronic tag and/or connect with another NFC enabled device, the NFC circuit including an NFC controller and a processing device coupled with an antenna element. Peripheral component interfaces may include, but are not limited to, non-volatile memory ports, USB ports, audio jacks, power interfaces, and the like.

Although not shown, the components of the platform 500 may communicate with each other using suitable bus or Interconnect (IX) technology, which may include any number of technologies, including ISA, EISA, PCI, PCix, PCie, time Triggered Protocol (TTP) systems, flexRay systems, or any number of other technologies. The bus/IX may be a proprietary bus/IX, for example, for use in a SoC based system. Other bus/IX systems may be included such as I ² C interface, SPI interface, point-to-point interface, and power bus, among others.

Fig. 6 is a block diagram illustrating a component 600 capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more of the methods discussed herein, according to some example embodiments. In particular, FIG. 6 shows a schematic diagram of a hardware resource 602 that includes one or more processors 606 (or processor cores), one or more memory/storage devices 614, and one or more communication resources 624, each of which may be communicatively coupled via a bus 616. For implementations in which node virtualization (e.g., NFV) is utilized, the hypervisor 622 can be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 602.

The processor 606 (e.g., a Central Processing Unit (CPU), a Reduced Instruction Set Computing (RISC) processor, a Complex Instruction Set Computing (CISC) processor, a Graphics Processing Unit (GPU), a Digital Signal Processor (DSP) (such as a baseband processor), an Application Specific Integrated Circuit (ASIC), a Radio Frequency Integrated Circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, a processor 608 and a processor 610.

Memory/storage 614 may include main memory, disk memory, or any suitable combination thereof. Memory/storage 614 may include, but is not limited to, any type of volatile or non-volatile memory, such as Dynamic Random Access Memory (DRAM), static Random Access Memory (SRAM), erasable Programmable Read Only Memory (EPROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory, solid state storage, and the like.

Communication resources 624 may include an interconnection or network interface component or other suitable device to communicate with one or more peripheral devices 604 or one or more databases 620 via network 618. For example, communications resources 624 may include wired communications components (e.g., for coupling via a Universal Serial Bus (USB)), cellular communications components, NFC components, and so forth,

Parts (e.g.)>

Low power consumption)/(f)>

Components and other communication components.

The instructions 612 may include software, programs, applications, applets, applications, or other executable code for causing at least any one of the processors 606 to perform any one or more of the methods discussed herein. The instructions 612 may reside, completely or partially, within at least one of the processors 606 (e.g., within a cache memory of the processor), the memory/storage 614, or any suitable combination thereof. Further, any portion of the instructions 612 may be transferred from any combination of the peripheral 604 or the database 620 to the hardware resource 602. Thus, the memory of the processor 606, the memory/storage 614, the peripherals 604 and the database 620 are examples of computer readable and machine readable media.

For one or more embodiments, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, procedures, and/or methods described in the examples section below. For example, the baseband circuitry described above in connection with one or more of the foregoing figures may be configured to operate according to one or more of the following examples. As another example, circuitry associated with a UE, base station, network element, etc. 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 shown in the examples section below.

Examples section

The following examples relate to further embodiments.

Embodiment 1 is a method for a wireless network. The method comprises the following steps: a message from a User Equipment (UE) is decoded. The message includes an indication of whether the UE supports a mixed parameter set, wherein different subcarrier spacings (SCS) are used in a serving cell or a neighboring cell to concurrently process at least two of: the UE making intra-frequency measurements of a Synchronization Signal Block (SSB); the UE performs intra-frequency measurements of channel state information reference signals (CSI-RS) for mobility; and reception of a Physical Downlink Control Channel (PDCCH) or a Physical Downlink Shared Channel (PDSCH) by the UE. The method further comprises the steps of: based on the indication, at least one of CSI-RS measurement expectations, SSB measurement expectations, and scheduling restrictions of reception of the PDCCH or the PDSCH by the PDCCH or the UE are configured.

Embodiment 2 includes the method of embodiment 1, further comprising: configuring at most two SCSs for the serving cell, wherein the SSB and the CSI-RS for mobility share a first SCS of the two SCSs of the serving cell, and wherein the indication indicates whether the UE supports concurrency: intra-frequency measurements of the SSB or the CSI-RS for mobility by the UE using the first SCS; and the UE receiving the PDCCH or the PDSCH from the serving cell using a second SCS of the two SCS.

Embodiment 3 includes the method of embodiment 2, further comprising: in response to the indication indicating that the UE does not support the mixed parameter set, the scheduling restriction is configured to not schedule the UE for reception of the PDCCH or the PDSCH on: the UE is configured to measure a set of one or more symbols of the SSB or the CSI-RS thereon; a first symbol preceding the set of one or more symbols; and a second symbol subsequent to the set of one or more symbols.

Embodiment 4 includes the method of embodiment 1, further comprising: configuring at most two SCS for the serving cell, wherein the CSI-RS for mobility and the reception of the PDCCH or PDSCH by the UE share a first SCS of the two SCS of the serving cell, and wherein the indication indicates whether the UE supports concurrency: reception of the PDCCH or the PDSCH from the serving cell or intra-frequency measurement of the CSI-RS for mobility by the UE using the first SCS; and intra-frequency measurements of the SSB by the UE using a second SCS of the two SCSs.

Embodiment 5 includes the method of embodiment 4, further comprising: in response to the indication indicating that the UE does not support the mixed parameter set, configuring the CSI-RS measurements to be desirable to not expect the UE to perform CSI-RS measurements on: the UE is configured to measure a set of one or more symbols of the SSB thereon; a first symbol preceding the set of one or more symbols; and a second symbol subsequent to the set of one or more symbols.

Embodiment 6 includes the method of embodiment 4, further comprising: in response to the indication indicating that the UE does not support the mixed parameter set, configuring the SSB measurement to be desirable to not expect the UE to perform SSB measurements on: the UE is configured to measure a set of one or more symbols of the CSI-RS thereon; a first symbol preceding the set of one or more symbols; and a second symbol subsequent to the set of one or more symbols.

Embodiment 7 includes the method of embodiment 4, further comprising: in response to the indication that the UE does not support the hybrid parameter set, a scaling factor is used to divide a time resource allocation between CSI-RS based mobility measurements and SSB based mobility measurements.

Embodiment 8 includes the method of any of embodiments 2-7, wherein the indication includes a simultaneousrxdata ssb-DiffNumerology parameter in a set of UE capability parameters.

Embodiment 9 includes the method of embodiment 1, wherein the indication indicates whether the UE supports both concurrent intra-frequency measurements for the SSB on the serving cell or the neighboring cell with a first SCS and intra-frequency measurements for the CSI-RS for mobility with a second SCS, the method further comprising: at least one of the PDCCH or the PDSCH and the CSI-RS are configured based on the indication.

Embodiment 10 includes the method of embodiment 9, further comprising: in response to the indication indicating that the UE does not support the mixed parameter set, configuring the CSI-RS measurements to be desirable to not expect the UE to perform CSI-RS measurements on: the UE is configured to measure a set of one or more symbols of the SSB thereon; a first symbol preceding the set of one or more symbols; and a second symbol subsequent to the set of one or more symbols.

Embodiment 11 includes the method of embodiment 9, further comprising: in response to the indication indicating that the UE does not support the mixed parameter set, configuring the SSB measurement to be desirable to not expect the UE to perform SSB measurements on: the UE is configured to measure a set of one or more symbols of the CSI-RS thereon; a first symbol preceding the set of one or more symbols; and a second symbol subsequent to the set of one or more symbols.

Embodiment 12 includes the method of embodiment 9, further comprising: in response to the indication that the UE does not support the hybrid parameter set, a scaling factor is used to divide a time resource allocation between CSI-RS based mobility measurements and SSB based mobility measurements.

Embodiment 13 includes the method of any of embodiments 9-12, wherein the indication includes a simultaneousCSIRSandSSB-DiffNumerology parameter in a set of UE capability parameters.

Embodiment 14 includes the method of embodiment 1, wherein the indication indicates whether the UE supports concurrent intra-frequency measurements on the serving cell or the neighboring cell with a first SCS with respect to the CSI-RS for mobility and PDCCH or PDSCH reception from the serving cell at the UE with a second SCS, the method further comprising: at least one of the PDCCH or the PDSCH and the CSI-RS are configured based on the indication.

Embodiment 15 includes the method of embodiment 14, further comprising: in response to the indication indicating that the UE does not support the mixed parameter set, the UE is not scheduled for the PDCCH or PDSCH reception on: the UE is configured to measure a set of one or more symbols of the CSI-RS thereon; a first symbol preceding the set of one or more symbols; and a second symbol subsequent to the set of one or more symbols.

Embodiment 16 includes the method of any of embodiments 14-15, wherein the indication includes a simultaneousrxdata csirs-DiffNumerology parameter in a set of UE capability parameters.

Embodiment 17 includes the method of embodiment 1, wherein the indication indicates whether the UE supports concurrent intra-frequency measurements on the serving cell or the neighboring cell with a first SCS, intra-frequency measurements on the CSI-RS for mobility with a second SCS, and PDCCH or PDSCH reception from the serving cell at the UE with a third SCS, the method further comprising: at least one of the PDCCH or the PDSCH and the CSI-RS are configured based on the indication.

Embodiment 18 includes the method of embodiment 17, further comprising: selecting the first SCS from a first set comprising 15kHz and 30kHz and the second SCS and the third SCS from a second set comprising 30kHz and 60kHz in a first frequency range (FR 1); and in a second frequency range (FR 2), the first SCS is selected from a third set comprising 120kHz and 240kHz, and the second SCS and the third SCS are selected from a fourth set comprising 60kHz and 120 kHz.

Embodiment 19 includes the method of embodiment 17, further comprising: in response to the indication that the UE does not support the hybrid parameter set, the UE is not expected to perform the operations of receiving data, measuring the CSI-RS for mobility, and measuring the SSB when the operations collide in the time domain and different SCS values are used for the first SCS, the second SCS, and the third SCS.

Embodiment 20 includes a method according to any of embodiments 17-19, wherein the indication includes a simultaneousrxdata csirsandssb-DiffNumerology parameter in a set of UE capability parameters.

Embodiment 21 is a method for a User Equipment (UE), the method comprising: generating a message to be sent to a base station in a wireless network, the message comprising an indication of whether the UE supports a mixed parameter set, wherein different subcarrier spacing (SCS) is used in a serving cell or a neighboring cell to concurrently process at least two of: the UE making intra-frequency measurements of a Synchronization Signal Block (SSB); the UE performs intra-frequency measurements of channel state information reference signals (CSI-RS) for mobility; and reception of a Physical Downlink Control Channel (PDCCH) or a Physical Downlink Shared Channel (PDSCH) by the UE; and performing one or more operations selected from the operations when receiving data from the serving cell, measuring the CSI-RS for mobility, and measuring the SSB to collide in a time domain based on whether the UE supports the hybrid parameter set.

Embodiment 22 includes the method of embodiment 21 wherein the serving cell is configured with at most two SCSs, wherein the SSB and the CSI-RS for mobility share a first SCS of the two SCSs of the serving cell, and wherein the indication indicates whether the UE supports concurrency: intra-frequency measurements of the SSB or the CSI-RS for mobility by the UE using the first SCS; and the UE receiving the PDCCH or the PDSCH from the serving cell using a second SCS of the two SCS.

Embodiment 23 includes the method of embodiment 21 wherein the serving cell is configured with at most two SCS, wherein the CSI-RS for mobility and the UE's reception of the PDCCH or PDSCH share a first SCS of the two SCS of the serving cell, and wherein the indication indicates whether the UE supports concurrency: reception of the PDCCH or the PDSCH from the serving cell or intra-frequency measurement of the CSI-RS for mobility by the UE using the first SCS; and intra-frequency measurements of the SSB by the UE using a second SCS of the two SCSs.

Embodiment 24 includes the method of embodiment 21 wherein the indication indicates whether the UE supports both concurrent intra-frequency measurements for the SSB on the serving cell or the neighboring cell with a first SCS and intra-frequency measurements for the CSI-RS for mobility with a second SCS.

Embodiment 25 includes the method of embodiment 21 wherein the indication indicates whether the UE supports concurrent intra-frequency measurements on the serving cell or the neighboring cell with the first SCS with respect to the CSI-RS for mobility and PDCCH or PDSCH reception from the serving cell at the UE with the second SCS.

Embodiment 26 includes the method of embodiment 21 wherein the indication indicates whether the UE supports concurrent intra-frequency measurements with respect to the SSB on the serving cell or the neighboring cell with a first SCS, intra-frequency measurements with respect to the CSI-RS for mobility with a second SCS, and PDCCH or PDSCH reception from the serving cell at the UE with a third SCS.

Embodiment 27 includes the method of embodiment 26, further comprising: selecting the first SCS from a first set comprising 15kHz and 30kHz and the second SCS and the third SCS from a second set comprising 30kHz and 60kHz in a first frequency range (FR 1); and in a second frequency range (FR 2), the first SCS is selected from a third set comprising 120kHz and 240kHz, and the second SCS and the third SCS are selected from a fourth set comprising 60kHz and 120 kHz.

Embodiment 28 includes the method of embodiment 27 wherein the first SCS, the second SCS, and the third SCS are selected as three different SCS values.

Embodiment 29 is a computer-readable storage medium comprising instructions that, when processed by a computer, configure a processor to perform a method according to any one of embodiments 1 to 28.

Embodiment 30 is a computing device comprising a processor and a memory storing instructions that, when executed by the processor, configure the device to perform a method according to any one of embodiments 1 to 28.

Embodiment 31 may comprise an apparatus comprising means for performing one or more elements of a method as described in or in connection with any of the embodiments above or any other method or process described herein.

Embodiment 32 may include one or more non-transitory computer-readable media comprising instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of the method or any other method or process described in or relating to any of the embodiments described above.

Embodiment 33 may comprise an apparatus comprising logic, modules, or circuitry to perform one or more elements of the method described in or relating to any of the embodiments described above or any other method or process described herein.

Embodiment 34 may include a method, technique, or process, or portion or part thereof, as described in or relating to any of the embodiments above.

Embodiment 35 may 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 the method, technique, or process described in or related to any one of the embodiments above, or portions thereof.

Embodiment 36 may include a signal, or portion or component thereof, as described in or associated with any of the above embodiments.

Embodiment 37 may include a datagram, packet, frame, segment, protocol Data Unit (PDU), or message, or portion or component thereof, as described in any of the above embodiments or otherwise described in this disclosure.

Embodiment 38 may include a data-encoded signal or portion or component thereof as described in or relating to any of the above embodiments, or otherwise described in this disclosure.

Embodiment 39 may comprise a signal encoded with a datagram, packet, frame, segment, PDU, or message, or portion or feature thereof, as described in any of the above embodiments or otherwise described in this disclosure.

Embodiment 40 may comprise electromagnetic signals carrying computer readable instructions for execution by one or more processors to cause the one or more processors to perform the method, technique, or process, or portion thereof, of or associated with any of the embodiments described above.

Embodiment 41 may comprise a computer program comprising instructions, wherein execution of the program by a processing element causes the processing element to perform the method, technique or process, or portion thereof, as described in or in connection with any of the embodiments above.

Embodiment 42 may include signals in a wireless network as shown and described herein.

Embodiment 43 may include a method of communicating in a wireless network as shown and described herein.

Embodiment 44 may include a system for providing wireless communications as shown and described herein.

Embodiment 45 may include an apparatus for providing wireless communications as shown and described herein.

Any of the above embodiments may be combined with any other embodiment (or combination of embodiments) unless explicitly stated otherwise. The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various implementations.

Embodiments and implementations of the systems and methods described herein may include various operations that may be embodied in machine-executable instructions to be executed by a computer system. The computer system may include one or more general-purpose or special-purpose computers (or other electronic devices). The computer system may include hardware components that include specific logic components for performing operations, or may include a combination of hardware, software, and/or firmware.

It should be appreciated that the systems described herein include descriptions of specific embodiments. These embodiments may be combined into a single system, partially incorporated into other systems, divided into multiple systems, or otherwise divided or combined. Furthermore, it is contemplated that in another embodiment parameters, attributes, aspects, etc. of one embodiment may be used. For the sake of clarity, these parameters, attributes, aspects, etc. are described in one or more embodiments only, and it should be recognized that these parameters, attributes, aspects, etc. may be combined with or substituted for parameters, attributes, aspects, etc. of another embodiment unless specifically stated herein.

It is well known that the use of personally identifiable information should follow privacy policies and practices that are recognized as meeting or exceeding industry or government requirements for maintaining user privacy. In particular, personally identifiable information data should be managed and processed to minimize the risk of inadvertent or unauthorized access or use, and the nature of authorized use should be specified to the user.

Although the foregoing has been described in some detail for purposes of clarity of illustration, it will be apparent that certain changes and modifications may be practiced without departing from the principles of the invention. It should be noted that there are many alternative ways of implementing both the processes and apparatuses described herein. The present embodiments are, therefore, to be considered as illustrative and not restrictive, and the description is not to be limited to the details given herein, but may be modified within the scope and equivalents of the appended claims.

Claims

1. A method for a wireless network, the method comprising:

decoding a message from a User Equipment (UE), the message comprising an indication of whether the UE supports a mixed parameter set, wherein different subcarrier spacing (SCS) is used in a serving cell or a neighboring cell to concurrently process at least two of:

-intra-frequency measurement of a Synchronization Signal Block (SSB) by the UE;

an intra-frequency measurement of a channel state information reference signal (CSI-RS) for mobility by the UE; and

the UE receiving a Physical Downlink Control Channel (PDCCH) or a Physical Downlink Shared Channel (PDSCH); and

based on the indication, at least one of the following is configured: CSI-RS measurement expectations, SSB measurement expectations, and scheduling restrictions of the UE on reception of the PDCCH or the PDSCH.

2. The method of claim 1, further comprising:

configuring at most two SCS for the serving cell, wherein the SSB and the CSI-RS for mobility share a first SCS of the two SCS of the serving cell, and

wherein the indication indicates whether the UE supports concurrency:

intra-frequency measurements of the SSB or CSI-RS for mobility by the UE using the first SCS; and

the UE, which uses a second SCS of the two SCSs, receives the PDCCH or the PDSCH from the serving cell.

3. The method of claim 2, further comprising: in response to the indication indicating that the UE does not support the mixed parameter set, configuring the scheduling restriction to not schedule the UE to receive the PDCCH or the PDSCH on:

A set of one or more symbols, the UE configured to measure the SSB or the CSI-RS over the set of one or more symbols;

a first symbol preceding the set of one or more symbols; and

a second symbol following the set of one or more symbols.

4. The method of claim 1, further comprising:

configuring at most two SCS for the serving cell, wherein the CSI-RS for mobility and reception of the PDCCH or PDSCH by the UE share a first SCS of the two SCS of the serving cell, and

wherein the indication indicates whether the UE supports concurrency:

reception of the PDCCH or PDSCH by the UE from the serving cell or intra-frequency measurement of the CSI-RS for mobility by the UE using the first SCS; and

the UE's intra-frequency measurements of the SSB using a second SCS of the two SCSs.

5. The method of claim 4, further comprising: in response to the indication indicating that the UE does not support the mixed parameter set, configuring the CSI-RS measurements to be desirable to not expect the UE to perform CSI-RS measurements on:

a set of one or more symbols, the UE configured to measure the SSB over the set of one or more symbols;

A first symbol preceding the set of one or more symbols; and

a second symbol following the set of one or more symbols.

6. The method of claim 4, further comprising: in response to the indication indicating that the UE does not support the mixed parameter set, configuring the SSB measurement to be desirable to not expect the UE to perform SSB measurements on:

a set of one or more symbols, the UE configured to measure the CSI-RS over the set of one or more symbols;

a first symbol preceding the set of one or more symbols; and

a second symbol following the set of one or more symbols.

7. The method of claim 4, further comprising: in response to the indication indicating that the UE does not support the hybrid parameter set, a scaling factor is used to divide time resource allocation between CSI-RS based mobility measurements and SSB based mobility measurements.

8. A method according to any of claims 2 to 7, wherein the indication comprises a simultaneousrxdata ssb-DiffNumerology parameter in a set of UE capability parameters.

9. The method of claim 1, wherein the indication indicates whether the UE supports both intra-frequency measurements for the SSB with a first SCS and intra-frequency measurements for the CSI-RS for mobility with a second SCS on the serving cell or the neighboring cell that are concurrent, the method further comprising: at least one of the PDCCH or the PDSCH and the CSI-RS are configured based on the indication.

10. The method of claim 9, further comprising: in response to the indication indicating that the UE does not support the mixed parameter set, configuring the CSI-RS measurements to be desirable to not expect the UE to perform CSI-RS measurements on:

a first symbol preceding the set of one or more symbols; and

a second symbol following the set of one or more symbols.

11. The method of claim 9, further comprising: in response to the indication indicating that the UE does not support the mixed parameter set, configuring the SSB measurement to be desirable to not expect the UE to perform SSB measurements on:

a set of one or more symbols, wherein the UE is configured to measure the CSI-RS over the set of one or more symbols;

a first symbol preceding the set of one or more symbols; and

a second symbol following the set of one or more symbols.

12. The method of claim 9, further comprising: in response to the indication indicating that the UE does not support the hybrid parameter set, a scaling factor is used to divide time resource allocation between CSI-RS based mobility measurements and SSB based mobility measurements.

13. A method according to any of claims 9 to 12, wherein the indication comprises a simultaneousCSIRSandSSB-DiffNumerology parameter in a set of UE capability parameters.

14. The method of claim 1, wherein the indication indicates whether the UE supports concurrent intra-frequency measurements on the CSI-RS for mobility with a first SCS on the serving cell or the neighboring cell and PDCCH or PDSCH reception from the serving cell at the UE with a second SCS, the method further comprising: at least one of the PDCCH or the PDSCH and the CSI-RS are configured based on the indication.

15. The method of claim 14, further comprising: in response to the indication indicating that the UE does not support the mixed parameter set, the UE is not scheduled for the PDCCH or PDSCH reception on:

a first symbol preceding the set of one or more symbols; and

a second symbol following the set of one or more symbols.

16. A method according to any of claims 14 to 15, wherein the indication comprises a simultaneousrxdata csirs-DiffNumerology parameter in a set of UE capability parameters.

17. The method of claim 1, wherein the indication indicates whether the UE supports concurrent intra-frequency measurements with a first SCS on the serving cell or the neighboring cell, intra-frequency measurements with a second SCS on the CSI-RS for mobility, and PDCCH or PDSCH reception from the serving cell at the UE with a third SCS, the method further comprising: at least one of the PDCCH or the PDSCH and the CSI-RS are configured based on the indication.

18. The method of claim 17, further comprising:

-in a first frequency range (FR 1), selecting said first SCS from a first set comprising 15kHz and 30kHz, and selecting said second SCS and said third SCS from a second set comprising 30kHz and 60 kHz; and

in a second frequency range (FR 2), the first SCS is selected from a third set comprising 120kHz and 240kHz, and the second SCS and the third SCS are selected from a fourth set comprising 60kHz and 120 kHz.

19. The method of claim 17, further comprising: in response to the indication indicating that the UE does not support the mixed parameter set, the UE is not expected to perform operations of receiving data, measuring the CSI-RS for mobility, and measuring the SSB when the operations collide in a time domain and different SCS values are used for the first SCS, the second SCS, and the third SCS.

20. A method according to any of claims 17 to 19, wherein the indication comprises a simultaneousrxdata csirsandssb-DiffNumerology parameter in a set of UE capability parameters.

21. A computer readable storage medium comprising instructions which, when processed by a computer, configure the processor to perform the method of any one of claims 1 to 20.

22. A computing device comprising a processor and a memory storing instructions that, when executed by the processor, configure the device to perform the method of any one of claims 1 to 20.

23. A User Equipment (UE), comprising:

a memory device for storing data of a message to be sent to a base station in a wireless network; and

a processor configured to:

generating the message to be sent to the base station, the message comprising an indication of whether the UE supports a mixed parameter set, wherein different subcarrier spacing (SCS) is used in a serving cell or a neighboring cell to concurrently process at least two of:

-intra-frequency measurement of a Synchronization Signal Block (SSB) by the UE;

based on whether the UE supports the hybrid parameter set, one or more operations selected from the operations of receiving data from the serving cell, measuring the CSI-RS for mobility, and measuring the SSB are performed when the operations collide in a time domain.

24. The UE of claim 23, wherein the serving cell is configured with at most two SCSs, wherein the SSB and the CSI-RS for mobility share a first SCS of the two SCSs of the serving cell, and wherein the indication indicates whether the UE supports concurrency:

25. The UE of claim 23, wherein the serving cell is configured with at most two SCSs, wherein the CSI-RS for mobility and reception of the PDCCH or PDSCH by the UE share a first SCS of the two SCSs of the serving cell, and

Wherein the indication indicates whether the UE supports concurrency:

reception of the PDCCH or PDSCH by the UE from the serving cell or intra-frequency measurement of the CSI-RS for mobility by the UE using a first SCS; and

26. The UE of claim 23, wherein the indication indicates whether the UE supports both intra-frequency measurements for the SSB with a first SCS and intra-frequency measurements for the CSI-RS for mobility with a second SCS on the serving cell or the neighboring cell that are concurrent.

27. The UE of claim 23, wherein the indication indicates whether the UE supports concurrent intra-frequency measurements on the CSI-RS for mobility with a first SCS on the serving cell or the neighboring cell and PDCCH or PDSCH reception from the serving cell at the UE with a second SCS.

28. The UE of claim 23, wherein the indication indicates whether the UE supports concurrent intra-frequency measurements with a first SCS on the serving cell or the neighboring cell, intra-frequency measurements with a second SCS on the CSI-RS for mobility, and PDCCH or PDSCH reception from the serving cell at the UE with a third SCS.

29. The UE of claim 28, wherein the processor is further configured to:

30. The UE of claim 29 wherein the first SCS, the second SCS, and the third SCS are selected to be three different SCS values.