Techniques for reducing radio resource management measurements and user equipment power consumption

Abstract

Embodiments of the present disclosure provide techniques for reducing radio resource management (RRM) measurements and user equipment (UE) power consumption in a wireless cellular network. Other embodiments are also described and claimed to be protected.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application is a divisional application of the invention patent application with international application number PCT / US2019 / 053193, international application date September 26, 2019, date of entry into the Chinese national phase March 24, 2021, Chinese national application number 201980062606.9, and invention name “Technology for reducing radio resource management measurements and user equipment power consumption”.

[0003] This application claims priority to U.S. Provisional Patent Application No. 62 / 739,078, filed on September 28, 2018. Technical Field

[0004] Embodiments of the present invention generally relate to the field of wireless communication technology. Background Art

[0005] In a new radio (NR) wireless communication network, a user equipment (UE) performs radio resource monitoring (RRM) on a measurement object (e.g., a cell). Therefore, the UE measures feedback information about the measurement object and transmits the feedback information to the network. These measurements consume a lot of power of the UE. BRIEF DESCRIPTION OF THE DRAWINGS

[0006] The embodiment will be more easily understood by the following specific implementation in conjunction with the accompanying drawings. In order to facilitate this description, similar reference numerals represent similar structural elements. In each figure of the accompanying drawings, the embodiment is shown by way of example and not limitation.

[0007] Figure 1 A network according to some embodiments is shown.

[0008] Figure 2 An operational flow / algorithm structure according to some embodiments is shown.

[0009] Figure 3 An operational flow / algorithm structure according to some embodiments is shown.

[0010] Figure 4 An operational flow / algorithm structure according to some embodiments is shown.

[0011] Figure 5 An operational flow / algorithm structure according to some embodiments is shown.

[0012] Figure 6 Examples of infrastructure equipment according to various embodiments are shown.

[0013] Figure 7Depicted are exemplary components of a computer platform or device according to various embodiments.

[0014] Figure 8 Depicted are exemplary components of baseband circuitry and RF end modules according to various embodiments.

[0015] Fig. 9 is a block diagram illustrating components capable of reading instructions from a machine-readable medium or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more of the methodologies discussed herein, according to some exemplary embodiments. DETAILED DESCRIPTION

[0016] The following specific embodiments relate to the accompanying drawings. The same figure numbers may be used to identify the same or similar elements in different drawings. In the following description, for the purpose of illustration and not limitation, specific details, such as specific structures, architectures, interfaces, technologies, etc., are described to provide a thorough understanding of the various aspects of each embodiment. However, it will be apparent to those skilled in the art who benefit from the present disclosure that the various aspects of each embodiment can be practiced in other examples that deviate from these specific details. In some cases, the description of well-known equipment, circuits, and methods is omitted so that the description of the various embodiments will not be obscured by unnecessary details. For the purpose of this document, the phrases "A or B" and "A / B" refer to (A), (B), or (A and B).

[0017] Figure 1 A network 100 is shown according to some embodiments. In general, the components shown in the network 100 may be similar and substantially interchangeable with the components of the same name in other figures described herein. The network 100 may include a UE 104 to communicate with a base station 108 of a radio access network (RAN) 112 using one or more radio access technologies.

[0018] The base station 108 may be referred to as a base station ("BS"), a NodeB, an evolved NodeB ("eNB"), a next generation NodeB ("gNB"), a RAN node, a road side unit ("RSU"), etc., and may include a ground station (e.g., a terrestrial access point) or a satellite station that provides coverage within a geographic area (e.g., a cell). An RSU may refer to any transport infrastructure entity implemented in or by a gNB / eNB / RAN node or a stationary (or relatively stationary) UE, wherein an RSU implemented in or by a UE may be referred to as a "UE-type RSU", and an RSU implemented in or by a gNB may be referred to as a "gNB-type RSU".

[0019] In some embodiments, the RAN may be a next generation ("NG") radio access network ("RAN"), in which case the base stations 108 may be gNBs that use new radio ("NR") access technology to communicate with the UEs 104. Thus, the RAN 112 may be a NR wireless cellular network.

[0020] UE 104 may be any mobile or non-mobile computing device capable of connecting to one or more cellular networks. For example, UE 104 may be a smart phone, a laptop computer, a desktop computer, a car computer, a smart sensor, etc. In some embodiments, UE 104 may be an Internet of Things ("IoT") UE, which may include a network access layer designed for low-power IoT applications that utilize transient UE connections. IoT UEs may utilize technologies such as machine-to-machine ("M2M") or machine-type communications ("MTC") to exchange data with MTC servers or devices via public land mobile networks ("PLMN"), proximity-based services ("ProSe"), or device-to-device ("D2D") communications, sensor networks, or IoT networks. M2M or MTC data exchanges may be machine-initiated data exchanges. IoT networks describe interconnected IoT UEs that may include uniquely identifiable embedded computing devices (within the Internet infrastructure) with transient connections. IoT UEs may execute background applications (e.g., keep active messages, status updates, etc.) to facilitate connectivity to IoT networks.

[0021] According to some embodiments, UE 104 may be configured to communicate with base station 108 over a multi-carrier communication channel using orthogonal frequency division multiplexing ("OFDM") communication signals according to various communication techniques, such as, but not limited to, orthogonal frequency division multiple access ("OFDMA") communication techniques (e.g., for downlink communications) or single carrier frequency division multiple access ("SC-FDMA") communication techniques (e.g., for uplink or sidelink communications), although the scope of the embodiments is not limited in this respect. OFDM signals may include multiple orthogonal subcarriers.

[0022] In some embodiments, a downlink resource grid may be used for downlink transmissions from a base station 108 to a UE 104, while uplink transmissions may utilize similar techniques. The grid may be a time-frequency grid, referred to as a resource grid or a 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 a common practice, which makes wireless resource allocation intuitive. Each column and each row of the resource grid corresponds to an OFDM symbol and an OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to a time slot in a radio frame. The smallest time-frequency unit in the resource grid is represented as a resource element. Each resource grid includes a plurality of resource blocks, which 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 currently be allocated. Such resource blocks are used to transmit several different physical channels.

[0023] In various embodiments, UE 104 may perform radio resource monitoring (RRM), wherein UE 104 measures feedback information about one or more measurement objects (MOs) (e.g., cells). The feedback information may include, for example, received signal received power (RSRP), received signal received quality (RSRQ), signal to interference plus noise ratio (SINR), channel quality indicator (CQI), and / or another suitable quality metric. Feedback information about one or more reference signals transmitted by the corresponding measurement object may be measured. For example, in some embodiments, the reference signal may include a synchronization signal (SS) / physical broadcast channel (PBCH) block (SSB) and / or a channel state information (CSI) reference signal (CSI-RS).

[0024] UE 104 may transmit the feedback information to gNB 108. gNB 108 may use the feedback information, for example, to determine one or more configuration parameters for enabling UE 104 to communicate on RAN 108 and / or whether to switch UE 104 to a different serving cell.

[0025] In various embodiments, the UE 104 may reduce the number of RRM measurements under some conditions, such as mobility-related conditions indicating that the UE is stationary or low mobility or very high mobility (which may also be referred to as extreme mobility or training speed mobility), and / or other conditions, such as MO configuration, cell type (e.g., size of the cell, such as macro cell or small cell; high-speed dedicated network cell, etc.), operating frequency, and / or one or more other conditions. For example, the UE 104 may reduce the number of RRM measurements based on one or more conditions indicating that the UE 104 is stationary or low mobility. When the UE 104 is stationary or low mobility, the RRM measurements may be relatively consistent over time, and therefore more RRM measurements may not be needed.

[0026] Additionally or alternatively, UE 104 may reduce the number of RRM measurements based on one or more conditions indicating that the UE has very high mobility (e.g., greater than a high mobility state defined under LTE, as discussed further below). When UE 104 has very high mobility, network conditions and / or serving cells may change so quickly that by the time the network is able to consider the RRM measurements, the RRM measurements do not represent current conditions.

[0027] In some embodiments, the decision to reduce the number of RRM measurements may be made further based on the location of the UE 104 in the serving cell. For example, other conditions being equal, if the UE 104 is near the edge of the serving cell, the UE 104 may determine not to reduce the number of RRM measurements, but if the UE 104 is near the center of the cell, the UE may determine to reduce the number of RRM measurements. The location of the UE 104 within the cell may be determined, for example, based on measured feedback information (e.g., RSRP, RSRQ, SINR, CQI, etc.) and / or other techniques.

[0028] In various embodiments, UE 104 can reduce the number of RRM measurements by, for example, skipping one or more RRM measurements (e.g., performing them otherwise if the conditions for skipping are not met) or extending the time between consecutive RRM measurements (e.g., by notifying the network that the time between RRM measurements should be extended so that the network will extend the time between transmissions of corresponding reference signals).

[0029] Additionally or alternatively, in some embodiments, even when both SSB and CSI-RS are configured for the UE, the UE 104 may determine not to measure both SSB and CSI-RS. For example, under certain conditions (such as mobility-related conditions), the UE 104 may skip one or more measurements of SSB and / or one or more measurements of CSI-RS.

[0030] Additionally or alternatively, UE 104 may limit usage of multiple antennas, MIMO layers, and / or RF chains under certain conditions.

[0031] These and other embodiments are described in further detail below. Various aspects of the embodiments can be applied in combination with each other or independently.

[0032] In LTE, there are three mobility states defined for UE: normal mobility, medium mobility and high mobility. CRmax The number of cell reselections during the period is less than the first threshold N CR_M , the UE can determine that its mobility is in normal mobility state. CRmaxThe number of cell reselections during the period is greater than or equal to the first threshold N CR_M But less than the second threshold N CR_H , the UE may determine that its mobility is medium mobility. In addition, if the number of cell reselections during the time period TcRmax is greater than the second threshold N CR_H , then the UE can determine that its mobility is high mobility. Time period T CRmax and / or threshold N CR_M and N CR_H It may be predefined and / or signaled by the network.When counting the number of cell reselections, the UE may not consider consecutive reselections where a cell is reselected again immediately after one reselection for the mobility state detection criteria.

[0033] In some embodiments, the UE may enter a mobility state based on its determined mobility. If the UE is in a high mobility state or a medium mobility state, the UE shall apply speed-related scaling rules as defined in subclause 5.2.4.3.1 in TS 38.304. The cell reselection scaling rules for the medium mobility state and the high mobility state may use T-Reselection values ​​of 0 seconds to 7 seconds, and SpeedStateScaleFactors of 0.25, 0.5, 0.75, and 1. The scaling rules may cause the UE to reduce the number of RRM measurements.

[0034] In various embodiments provided herein, when the UE detects that it is stationary or low mobility, the UE may reduce the number of RRM measurements. In addition or alternatively, when the UE detects that it is very high mobility (e.g., mobility higher than the "high mobility" state defined in LTE), the UE may reduce the number of RRM measurements. In some embodiments, the UE's processing of RRM measurements may depend on the UE's RRC connection state (e.g., RRC Connected, RRC_IDLE, RRC_INACTIVE). For example, when the UE is in RRC_IDLE or RRC_INACTIVE but not in RRC Connected, the UE may reduce the number of RRM measurements for stationary / low mobility and / or very high mobility conditions.

[0035] Note that in some embodiments, the UE may not be able to skip RRM measurements on the serving cell before each paging occasion (PO) because the UE may need to perform timing / frequency tracking of the SSB before each PO. In addition, if the SSB does not occur in the PO, the UE may wake up before the PO to obtain the SSB, thereby performing serving cell measurements while in RRC_IDLE / INACTIVE. However, the UE may be able to skip inter-frequency or inter-RAT measurements.

[0036] The following describes some exemplary options on how a UE may determine that its mobility is stationary / low and / or very high mobility:

[0037] Variable speed method :A threshold value may be defined for a UE to determine whether it is in a stationary mobility state (e.g., a no mobility state or a low mobility state). The information of the threshold value may be fixed in the specification, or the value may be provided to the UE by the network (e.g., via broadcast or dedicated signaling). For example, if the UE is in a certain time period (which may be a traditional TOR max or may be referred to as, for example, T CRstationary A certain number of cell reselections (which may be referred to as, for example, N) are performed during a period of CR_L ) or less. Therefore, if the number of cell reselections in this time period is greater than N CR_L and less than N CR_M , the UE may determine that it is in normal mobility. For example, the UE may determine its mobility state as follows:

[0038] State detection standard example #1 :

[0039] Stationary / low mobility status criteria :

[0040] - If in time period T CRmax The number of cell reselections during the period is less than N CR_L .

[0041] Normal mobility status criteria:

[0042] - If in time period T CRmax The number of cell reselections during Greater than or equal to N CR_L but Less than N CR_M .

[0043] Medium mobility status criteria:

[0044] - If in time period T CRmax The number of cell reselections during the period is greater than or equal to N CR_M But less than N CR_H .

[0045] High mobility status criteria:

[0046] - If in time period T CRmax The number of cell reselections during the period is greater than N CR_H .

[0047] In some embodiments, N CR_L It can be 1. Therefore, if the number of cell reselections during the time period is 0 (the UE does not perform any cell reselection during the time period), the UE can determine that it is stationary or low mobility. Therefore, the status criteria can be as follows:

[0048] State Detection Standard Example #2 :

[0049] No mobility status standard :

[0050] - If in time period T CRmax The number of cell reselections during this period is equal to 0.

[0051] Normal mobility status criteria:

[0052] - If in time period T CRmax The number of cell reselections during Greater than 0 but Less than N CR_M .

[0053] Medium mobility status criteria:

[0054] - If in time period T CRmax The number of cell reselections during the period is greater than or equal to N CR_M But less than N CR_H .

[0055] High mobility status criteria:

[0056] - If in time period T CRmax The number of cell reselections during the period is greater than N CR_H .

[0057] The parameters of the time period and the mobility threshold may be configured by the network (eg, via a broadcast message or an RRC dedicated message).

[0058] In various embodiments, similar methods may be used to enable a UE to determine whether it is in a very high mobility state. For example, a threshold may be defined and / or signaled to the UE (e.g., via broadcast or dedicated signaling) for the UE to determine whether it is in a very high mobility state. For example, if the UE determines that the number of cell reselections is equal to or greater than the number of cell reselections in a particular time period (which may be a conventional T CRmax Or it may be called, for example, T CRVeryHigh The threshold value during the period (which may be referred to as, for example, N CR_V ), the UE may determine that it is in a very high mobility state.

[0059] Fixed speed method : The mobility information (e.g., stationary / low mobility or very high mobility) can be a fixed configuration of the UE, which can be known by the network, for example, via subscription, capabilities (e.g., at the AS or NAS level), device type, etc. This information can also be negotiated between the UE and the network; for example, the network needs to configure or allow the UE to operate as a stationary device or a very high-speed device all the time or until otherwise instructed. In addition, in some embodiments, the network can be the driving factor for determining whether the UE can operate at very high / extreme speeds, for example, the network deployment knows when the UE is in high-speed training.

[0060] Deployment related methods : Whether the UE is stationary may take into account network deployment, for example, in the case of a large cell with multiple transmission reception points (TRPs).

[0061] UE feedback method: The UE may know UE mobility information (e.g., whether the UE is stationary / low mobility or very high mobility) via non-3GPP mechanisms (e.g., via GPS and / or other location information). This information may provide more accurate input on other aspects such as mobility speed, location, etc. In some embodiments, the UE may send this mobility information to the network via an RRC message.

[0062] Additionally or alternatively, the network may pre-configure the mobility state of the UE to perform corresponding RRM measurement actions, as discussed further below.

[0063] Rel-15 LTE HSDN (High Speed ​​Dedicated Network) Method : The UE may determine a cell in a HSDN condition based on information provided via System Information (SI) or a dedicated message. The UE may determine that its mobility is very high based on the cell connected to the HSDN.

[0064] Note that HSDN in Rel-15 implements cell reselection priorities for dedicated networks, and different weights for each cell (depending on the cell size). The UE takes this weight into account to count the cells. Therefore, the main goal of Rel-15 is to improve cell reselection, but not RRM measurements (which are provided by the embodiments of this article).

[0065] In some embodiments, any of the options described herein for how a UE may determine whether its mobility is stationary / low and / or very high mobility may be used in conjunction with one or more other options.

[0066] UE reporting of mobility information

[0067] The following describes some exemplary embodiments of how a UE may share its mobility information (e.g., to indicate whether the UE mobility is stationary / low mobility or very high mobility). In various embodiments, the UE may report its mobility information via uplink (UL) dedicated signaling, for example, in an RRC or medium access control (MAC) control element (CE). For example, the RRCSetupComplete, RRCResumeComplete, and / or RRCRereinmentComplete messages may include mobility state information indicating that the UE is in stationary / low mobility or very high mobility. For example, the information element mobilityState-rxy may indicate the mobility information of the UE according to any of the following examples:

[0068] Example #1:

[0069] -MobilityState-rxyENUMERATED{NoneNormalMediumHigh}

[0070] Example #2:

[0071] -MobilityState-rxyENUMERATED{low normal medium high}

[0072] Example #3:

[0073] -Mobility State-rxyENUMERATED (Normal Medium High Very High)

[0074] Example #4:

[0075] -MobilityState-rxyENUMERATED (None / Low, Normal, Medium, High, Very High)

[0076] The above RRC message and / or another message (eg, UECapabilityInformatio) may also include that the UE is a stationary type UE and / or is capable of determining when the UE is a stationary or non-mobile UE and / or a very high mobility UE.

[0077] In various implementations, the information provided by the UE to the network may include one or more of the following:

[0078] - Mobility status: Low, Normal, Medium, High, Very High

[0079] - Speed: actual speed of UE, such as 0km / h, 3km / h, 30km / h, etc.

[0080] - Coordinates: UE can periodically send coordinates to the network and the network can estimate UE speed / mobility

[0081] Alternatively or additionally, the network may perform network based mobility estimation and send the information to the UE.

[0082] Example RRM enhancements for static / low mobility UEs and / or very high mobility UEs

[0083] In various embodiments, a certain number of RRM measurements may be skipped for certain cells and / or frequencies (implicit blacklist based on the UE's condition). This may be done without affecting the UE's requirements (e.g., as defined by RAN4). For example, new scaling factors may be defined for UEs that are stationary / low mobility and / or have changing high mobility. An exemplary change to TS 38.304 and TS 38.331 is shown below to provide new scaling factors for low mobility UEs. Corresponding changes may be made to provide new scaling factors for very high mobility UEs.

[0084] 5.2.4.3.1 Scaling rules

[0085] The UE shall apply the following scaling rules:

[0086] - If neither medium mobility nor high mobility is detected Low motion is not detected either state:

[0087] - No scaling is applied.

[0088] - If a high mobility state is detected:

[0089] - If broadcast in system information, "Q hyst The speed-dependent scaling factor "sf-High" is added to Q hyst

[0090] For NR cells, if broadcast in system information, Treselection NR Multiply by "Treselection NR The speed-dependent scaling factor of sf-High

[0091] - For EUTRA cells, multiply TreselectionEUTRA by sf-High of "Speed ​​Dependent Scaling Factor for TreselectionEUTRA" if broadcasted in system information

[0092] - If medium mobility state is detected:

[0093] - If broadcast in system information, "Q hyst The speed-dependent scaling factor of the sf-Medium is added to Q hyst ;

[0094] For NR cells, if broadcast in system information, Treselection NR Multiply by "Treselection NR The speed-dependent scaling factor of sf-Medium

[0095] - For EUTRA cells, multiply TreselectionEUTRA by sf-Medium of "Speed ​​dependent scaling factor for TreselectionEUTRA" if broadcasted in system information

[0096] - If a low mobility state is detected :

[0097] - If broadcast in system information, "Q hvst The speed-dependent scaling factor "sf-

[0098] Low added to Q hvst ;

[0099] -For NR cells, if broadcast in system information, Treselection NR Multiply

[0100] "Treselection NR The speed-dependent scaling factor of sf-Low

[0101] - For EUTRA cells, if broadcast in system information, multiply TreselectionEUTRA by sf-Low of "Speed-dependent scaling factor for TreselectionEUTRA"

[0102] Depending on how the skipping of measurements is defined, different options can be considered. For example:

[0103] - Option (1) The time required for the UE to obtain valid measurements is delayed due to skipping within the measurement cycle.

[0104] ■ If the UE needs to take at least 'N' samples in order to have a valid measurement, and the UE skips some legacy occurrences, it will take the UE longer to obtain it.

[0105] ■The minimum requirements of UE will be affected (RAN4 impact).

[0106] ■ The network can configure the UE with different SMTC (SS / PBCH Block Measurement Timing Configuration) periodicities. A new longer value can also be defined for the SMTC periodicity. Alternatively, within the same period, the UE can be allowed to skip certain values.

[0107] - Option (2) The time required for the UE to obtain valid measurements is the same, even if the UE skips some samples in the measurement period.

[0108] ■The minimum requirements of UE will not be affected (RAN4 is not affected).

[0109] - Option (3) The UE is provided with a different SMTC (SS / PBCH Block Measurement Timing Configuration) configuration to delay instances when the UE acquires its measured samples.

[0110] ■The minimum requirements of UE will be affected (RAN4 impact).

[0111] Considerations for UEs in RRC CONNECTED

[0112] The above embodiments are applicable to UEs in RRC_IDLE and / or RRC_INACTIVE. Some or all of the embodiments may also be applicable to UEs in RRC_CONNECTED. Additional considerations for UEs in RRC_CONNECTED are described below.

[0113] In RRC_CONNECTED, there is only one level of Ssearch, which will allow only one level of skipping RRM measurements regardless of intra-frequency / inter-frequency / inter-RAT measurements. In some embodiments, different levels may be defined for intra-frequency, inter-frequency and inter-RAT, so that similar thresholds are defined for RRC_CONNECTED, and also for RRC_IDLE and RRC_INACTIVE.

[0114] The following new scenarios may be enhanced for UEs in RRC_CONNECTED in order to reduce RRM measurements: Scenario A) stationary UE (which may also be referred to as no mobility or low mobility), and Scenario B) very high mobility UE (which may also be referred to as extreme mobility or training speed mobility).

[0115] In some embodiments, a UE in RRC_CONNECTED may determine its mobility based on the activation and / or deactivation of a measurement object (MO). A conventional network may change or remove the measurement configuration of the UE to stop or skip RRM measurements. However, this is not done in a dynamic manner. In various embodiments, unicast signaling (e.g., RRC and / or MAC) may be enabled to allow activation and deactivation of a given MO provided to the UE. Alternatively, new signaling may be defined to disable or deactivate a given MO during a specific time period when triggered.

[0116] Additionally or alternatively, the UE may determine its mobility state based on information available only in RRC_CONNECTED (e.g., handover information, CSI reports, etc.). The UE may request or notify the network of its UE mobility state, or the network may determine the UE mobility state based on this information provided by the UE or collected at the network side.

[0117] In some embodiments, the UE may autonomously enable and disable one or more MOs based on the UE's mobility state. This may be a purely UE-based solution, where the UE detects a specific mobility state and determines whether to enable and / or disable one or more MOs based on the configuration of the corresponding MO.

[0118] Skip RRM measurements based on cell or frequency

[0119] In various embodiments, the UE may be configured to skip one or more RRM measurements based on the cell type (e.g., macro cell deployment and / or small cell deployment). In addition, this information may also be tied to the above-mentioned mobility-related scenarios. For example, the UE may be configured to have a cell list with cell IDs for skipping based on the above-mentioned mobility-related conditions. In some embodiments, the decision whether to skip one or more RRM measurements may also take into account the location of the UE in the cell (e.g., whether the UE is near the edge of the cell).

[0120] These embodiments are applicable to UEs in any RRC state.

[0121] Similar enhancements may be enabled based on a given operating frequency.

[0122] Skipping RRM based on MO in RRC CONNECTED

[0123] In various embodiments, a UE in RRC CONNECTED may be configured with different MOs based on its mobility state. For example, one or more MOs may be optimized for different mobility-related scenarios described herein. In addition, the network may provide multiple MOs to the UE and activate / deactivate them based on the mobility speed of the UE. Alternatively, the UE may autonomously select one or more MOs to be used based on its mobility state and / or other conditions that may be defined.

[0124] Skip RS

[0125] In various embodiments, if the UE is configured with both SSB and CSI-RS, the UE may skip RRM measurements on SSB or CSI-RS. This may apply, for example, to a UE in RRC_CONNECTED.

[0126] In Rel-15, the UE can be configured by the network to measure in both SSB and CSI-RS, it should be understood that the UE cannot combine measurements taken from SSB with measurements taken from CSI-RS. From the RAN2 side, MO configuration can be provided for SSB and CSI-RS together or independently; however, reporting configuration will be provided for SSB and CSI-RS independently.

[0127] According to embodiments herein, if the network configures two types of measurements (via SSB and CSI-RS), some cases may be defined for the UE to skip RRM measurements for one of them:

[0128] - Option 1), it is left to the UE implementation to choose which one.

[0129] - Option 2), the UE always skips one of the following based on a given situation / condition: Option 2.a) skip SSB and proceed to CSI-RS or Option 2.b) skip CSI-RS and SSB. The situation / condition may be tied to the mobility state of the UE, the location of the UE and / or the RSRP / RSRQ of the UE, etc.

[0130] - In addition, the UE may skip one or more of RSRP, RSRQ, SINR for specific mobility states.

[0131] Reduce RF chain usage

[0132] In various implementations, a UE may reduce its usage of RF chains (eg, transmit chains and / or receive chains), multiple antennas, or multiple MIMO layers based on certain configurations or conditions (eg, based on measurement configurations).

[0133] In LTE, perCC-GapIndication is introduced, where UE assistance is provided as part of UE capabilities for each CC band indication.

[0134] In some implementations, the UE may change its use of RF chains, multiple antennas, and / or multiple MIMO layers based on one or both of the following options:

[0135] - Option 1) Semi-static : UE provides different UE capability configurations when querying the network.

[0136] - Option 2) Dynamic based on UE trigger or request :The UE provides a preference for changing its use of RF chains, multiple antennas, or MIMO layers. This information may be provided via an L2 mechanism (e.g., within an RRC message or MACCE) or via an L1 mechanism (e.g., downlink control information (DCI)) at any given time. Alternatively, the network may confirm its request or may provide an alternative configuration associated with the same or different kind of information.

[0137] - Option 3) Dynamic NW trigger / indication : The UE changes its configuration based on certain conditions / situations, such as based on a certain mobility state or based on information provided on a traffic status report, or via an indication provided by the network for the UE to change the usage of the MIMO layer or RF chain or antenna to be used.

[0138] -Option 4) Hybrid Approach : The UE is configured with multiple configurations that are foreseen to be desirable for a given UE, multiple antennas or MIMO layers of the RF chain, and one or the other is used based on a given situation / condition. These conditions may be specified in the network or may be driven by network indications (e.g., activation / deactivation of a given configuration).

[0139] For example, in some embodiments, a maximum number of MIMO layers may be configured for a bandwidth part (BWP). The UE may limit the number of MIMO layers to this maximum number and may ignore the cell-specific value provided in the PDSCHServingCellConfig information element when operating with a BWP. If the maximum number of MIMO layers is not configured for a BWP, the UE may use a cell-specific value for the BWP.

[0140] Figure 2 An operational flow / algorithm structure 200 is shown according to some embodiments. The operational flow / algorithm structure 200 may be performed partially or completely by the UE 104 or a component thereof. For example, in some embodiments, the operational flow / algorithm structure 200 may be performed by a baseband circuit implemented in the UE 104.

[0141] The operational flow / algorithm structure 200 may include determining that the mobility of the UE is low or very high at 204. Low (e.g., stationary) or very high mobility may be defined as described herein. For example, the UE may be further configured to determine whether the mobility of the UE is normal, medium, or high, where low mobility is lower mobility than normal mobility, and where very high mobility is greater than high mobility.

[0142] The operational flow / algorithm structure 200 may also include extending a time period between RRM measurements of one or more cells of the wireless cellular network based on the determination at 208. For example, if the mobility of the UE is low or very high, the UE may skip one or more RRM measurements (e.g., that would otherwise be performed). In some embodiments, if the mobility of the UE is low or very high, the UE may apply a scaling factor as described herein.

[0143] Figure 3 An operational flow / algorithm structure 300 is illustrated according to some embodiments. The operational flow / algorithm structure 300 may be performed partially or completely by the base station 108 or a component thereof. For example, in some embodiments, the operational flow / algorithm structure 300 may be performed by baseband circuitry implemented in the base station 108.

[0144] The operational flow / algorithm structure 300 may include receiving an indication from a user equipment (UE) that the UE's mobility is low or very high at 304. Low (e.g., stationary) or very high mobility may be defined as described herein. For example, the UE may be further configured to determine whether the UE's mobility is normal, medium, or high, where low mobility is lower mobility than normal mobility, and where very high mobility is greater than high mobility.

[0145] The operational flow / algorithm structure 300 may also include adjusting one or more parameters for the UE based on the indication at 308. For example, a time period between RRM measurements made by the UE on one or more cells may be extended.

[0146] In some embodiments, the operational flow / algorithm structure 300 may also include encoding a message for transmission to the gNB to indicate the mobility of the UE.

[0147] Figure 4 An operational flow / algorithm structure 400 is shown according to some embodiments. The operational flow / algorithm structure 400 may be performed partially or completely by the UE 104 or a component thereof. For example, in some embodiments, the operational flow / algorithm structure 400 may be performed by a baseband circuit implemented in the UE 104.

[0148] The operational flow / algorithm structure 400 may include, at 404, receiving configuration information indicating at least one of a maximum number of radio frequency (RF) chains, a maximum number of antennas, or a maximum number of MIMO layers to be used by the UE.

[0149] The operational flow / algorithm structure 400 may also include limiting the use of RF chains, antennas, or MIMO layers to a corresponding maximum number at 408. In some embodiments, the number of RF chains, antennas, and / or MIMO layers may be limited based on one or more conditions (such as UE mobility, network conditions, etc.).

[0150] Figure 5 Another operational flow / algorithm structure 500 according to some embodiments is shown. The operational flow / algorithm structure 500 may be performed partially or completely by the UE 104 or a component thereof. For example, in some embodiments, the operational flow / algorithm structure 500 may be performed by a baseband circuit implemented in the UE 104.

[0151] The operational flow / algorithm structure 500 may include, at 504, receiving configuration information for a channel state information reference signal (CSI-RS) and a synchronization signal (SS) / physical broadcast channel (PBCH) block (SSB).

[0152] The operation flow / algorithm structure 500 may also include determining to skip RRM measurement on one of the CSI-RS or SSB at 508. The UE may perform RRM measurement on the other of the CSI-RS or SSB. In some embodiments, the UE may determine to skip RRM measurement on one of the CSI-RS or SSB based on one or more circumstances (such as UE mobility and / or network conditions, etc.).

[0153] Figure 6 An example of infrastructure equipment 600 according to various embodiments is shown. Infrastructure equipment 600 (or "system 600") may be implemented as a base station, a radio head, a RAN node, etc., such as the base station 108 previously shown and described. System 600 may include one or more of the following: application circuit 605, baseband circuit 610, one or more radio front-end modules 615, memory circuit 620, power management integrated circuit (PMIC) 625, power tee circuit 630, network controller circuit 635, network interface connector 640, satellite positioning circuit 645, and user interface 650. In some embodiments, device 600 may include additional elements, such as, for example, memory / storage, display, camera, sensor, or input / output (I / O) interface. In other embodiments, the components described below may be included in more than one device (e.g., the circuit may be included separately in more than one device for CRAN, vBBU, or other similar implementations).

[0154] As used herein, the term "circuit" may refer to, be part of, or include a hardware component such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) and / or a memory (shared, dedicated, or group) configured to provide the described functions, an application specific integrated circuit (ASIC), a field programmable device (FPD) (e.g., a field programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high capacity PLD (HCPLD), a structured ASIC, or a programmable system on chip (SoC)), a digital signal processor (DSP), etc. In some embodiments, the circuit may execute one or more software or firmware programs to provide at least some of the described functions. In addition, the term "circuit" may also refer to a combination of one or more hardware elements and a program code for performing the functions of the program code (or a combination of circuits used in an electrical or electronic system). In these embodiments, the combination of hardware elements and program code may be referred to as a specific type of circuit.

[0155] The terms "application circuitry" and / or "baseband circuitry" may be considered synonymous with "processor circuitry" and may be referred to as "processor circuitry". As used herein, the term "processor circuitry" may refer to, be part of, or include a circuit capable of sequentially and automatically performing a series of arithmetic or logical operations or recording, storing, and / or transmitting digital data. The term "processor circuitry" may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, and / or any other device capable of executing or otherwise operating computer-executable instructions (such as program code, software modules, and / or functional processes).

[0156] The application circuit 605 may include one or more central processing unit (CPU) cores and one or more of the following: cache memory, a low dropout regulator (LDO), an interrupt controller, a serial interface such as SPI, I2C or a general programmable serial interface module, a real-time clock (RTC), a timer-counter including an interval timer and a watchdog timer, a general 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) interface, and a joint test access group (JTAG) test access port. As an example, the application circuit 605 may include one or more Intel or Processor: Advanced Micro Devices (AMD) Processor, Accelerated Processing Unit (APU) or processor; etc. In some embodiments, system 600 may not utilize application circuit 605, and instead may include a dedicated processor / controller to process IP data received, for example, from an EPC or 5GC.

[0157] Additionally or alternatively, the application circuit 605 may include circuits such as, but not limited to, one or more field programmable devices (FPDs) such as field programmable gate arrays (FPGAs), etc.; programmable logic devices (PLDs), such as complex PLDs (CPLDs), high capacity PLDs (HCPLDs), etc.; ASICs, such as structured ASICs, etc.; programmable SoCs (PSoCs); etc. In such embodiments, the circuits of the application circuit 605 may include logic blocks or logic structures, and other interconnected resources that can be programmed to perform various functions such as the processes, methods, functions, etc. of the various embodiments discussed herein. In such embodiments, the circuits of the application circuit 605 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), anti-fuse, etc.)) for storing logic blocks, logic structures, data, etc. in look-up tables (LUTs), etc.

[0158] Baseband circuit 610 can be implemented as, for example, a solder-in substrate, which 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. Although not shown, baseband circuit 610 may include one or more digital baseband systems, which may be coupled to a CPU subsystem, an audio subsystem, and an interface subsystem via an interconnect subsystem. The digital baseband subsystem may also be coupled to a digital baseband interface and a mixed signal baseband subsystem via another interconnect subsystem. Each of the interconnect subsystems may include a bus system, a point-to-point connector, a network on chip (NOC) structure, and / or some other suitable bus or interconnect technology, such as those discussed herein. The audio subsystem may include a digital signal processing circuit, a buffer memory, a program memory, a voice processing accelerator circuit, a data converter circuit such as an analog-to-digital converter circuit and a digital-to-analog converter circuit, an analog circuit including one or more of an amplifier and a filter, and / or other similar components. In one aspect of the disclosure, baseband circuitry 610 may include protocol processing circuitry having one or more control circuit instances (not shown) to provide control functionality for digital baseband circuitry and / or radio frequency circuitry (eg, radio front end module 615).

[0159] The user interface circuit 650 may include one or more user interfaces designed to enable a user to interact with the system 600 or a peripheral component interface designed to enable a peripheral component to interact with the system 600. 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 transmitting device, a microphone, a printer, a scanner, a headset, a display screen or display device, etc. The peripheral component interface may include, but is not limited to, a non-volatile memory port, a universal serial bus (USB) port, an audio jack, a power interface, etc.

[0160] The radio front end module (RFEM) 615 may include a millimeter wave 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 separated 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, both millimeter wave and sub-millimeter wave radio functions may be implemented in the same physical radio front end module 615. The RFEM 615 may combine both millimeter wave antennas and sub-millimeter wave antennas.

[0161] The memory circuit 620 may include one or more of the following: a volatile memory including a dynamic random access memory (DRAM) and / or a synchronous dynamic random access memory (SDRAM), a non-volatile memory (NVM) including a high-speed electrically erasable memory (commonly referred to as a "flash memory"), a phase change random access memory (PRAM), a magnetoresistive random access memory (MRAM), etc., and may be combined with and The memory circuit 620 may be implemented as one or more of the following: a solder-in package integrated circuit, a socket memory module, and a plug-in memory card.

[0162] The PMIC 625 may include a voltage regulator, a surge protector, a power alarm detection circuit, and one or more backup power sources, such as a battery or capacitor. The power alarm detection circuit may detect one or more of a brownout (undervoltage) and a surge (overvoltage) condition. The power tee circuit 630 may provide power extracted from a network cable to provide both power and data connections for the infrastructure equipment 600 using a single cable.

[0163] The network controller circuit 635 may provide connectivity to the network using a standard network interface protocol such as Ethernet, Ethernet based on a GRE tunnel, Ethernet based on a multi-protocol label switching (MPLS), or some other suitable protocol. A physical connection may be used to provide a network connection to / from the infrastructure equipment 600 via a network interface connector 640, which may be an electrical connection (commonly referred to as a "copper interconnect"), an optical connection, or a wireless connection. The network controller circuit 635 may include one or more dedicated processors and / or FPGAs for communicating using one or more of the aforementioned protocols. In some implementations, the network controller circuit 635 may include multiple controllers for providing connectivity to other networks using the same or different protocols.

[0164] The positioning circuit 645 may include circuits for receiving and decoding signals transmitted by one or more navigation satellite constellations of a global navigation satellite system (GNSS). Examples of navigation satellite constellations (or GNSS) may include the United States' Global Positioning System (GPS), Russia's Global Navigation System (GLONASS), the European Union's Galileo system, China's BeiDou Navigation Satellite System, regional navigation systems, or GNSS augmentation systems (e.g., navigation using the Indian constellation (NAVIC), Japan's Quasi-Zenith Satellite System (QZSS), France's Doppler Orbit Chart and Satellite Integrated Radio Positioning (DORIS), etc.), etc.

[0165] The positioning circuit 645 may include various hardware elements (eg, including hardware devices such as switches, filters, amplifiers, antenna elements, etc. to facilitate OTA communications) to communicate with components of a positioning network such as a navigation satellite constellation node.

[0166] A node or satellite of a navigation satellite constellation ("GNSS node") may provide a positioning service by continuously transmitting or broadcasting GNSS signals along a line of sight, which a GNSS receiver (e.g., positioning circuit 645 and / or positioning circuit implemented by UE 104, etc.) may use to determine their GNSS position. The GNSS signal may include a pseudo-random code (e.g., a sequence of ones and zeros) known to the GNSS receiver and a message including a transmission time (ToT) of a code period (e.g., a defined point in the pseudo-random code sequence) and the GNSS node position at the ToT. The GNSS receiver may monitor / measure GNSS signals transmitted / broadcasted by multiple GNSS nodes (e.g., four or more satellites) and solve various formulas to determine the corresponding GNSS position (e.g., spatial coordinates). The GNSS receiver also implements a clock that is generally less stable and less accurate than the atomic clock of the GNSS node, and the GNSS receiver may use the measured GNSS signal to determine the deviation of the GNSS receiver from the true time (e.g., the offset of the GNSS receiver clock relative to the GNSS node time). In some embodiments, the positioning circuit 645 may include a micro technology integrated circuit (IC) for positioning, navigation, and timing (micro PNT) that performs position tracking / estimation using a master timing clock without GNSS assistance.

[0167] The GNSS receiver may measure the time of arrival (ToA) of GNSS signals from multiple GNSS nodes based on its own clock. The GNSS receiver may determine the time of flight (ToF) value of each received GNSS signal based on the ToA and ToT, and then may determine a three-dimensional (3D) position and clock bias based on the ToF. The 3D position may then be converted to latitude, longitude, and altitude. The positioning circuit 645 may provide data to the application circuit 605, which may include one or more of position data or time data. The application circuit 605 may use the time data to synchronize operations with other radio base stations (e.g., base station 108, etc.).

[0168] Figure 6The components shown can use interface circuits to communicate with each other. As used herein, the term "interface circuit" may refer to, be a part of, or include the following items: a circuit that provides information exchange between two or more components or devices. The term "interface circuit" may refer to one or more hardware interfaces, such as a bus, an input / output (I / O) interface, a peripheral component interface, a network interface card, etc. Any suitable bus technology can be used in various specific implementations, which may include any number of technologies, including industry standard architecture (ISA), extended ISA (EISA), peripheral component interconnect (PCI), peripheral component interconnect extension (PCIx), PCI express (PCIe) or any number of other technologies. The bus may be a proprietary bus, for example, used in a system based on SoC. Other bus systems may be included, such as I2C interface, SPI interface, point-to-point interface, and power bus, etc.

[0169] Figure 7 An example of a platform 700 (or "device 700") according to various embodiments is shown. In an embodiment, the computer platform 700 may be suitable for use as a UE 104, a base station 108, or any other element / device discussed herein. The platform 700 may include any combination of components shown in the example. The components of the platform 700 may be implemented as integrated circuits (ICs), portions thereof, discrete electronic devices, or other modules, logic, hardware, software, firmware, or combinations thereof suitable for use in the computer platform 700, or implemented as components otherwise incorporated within a chassis of a larger system. Figure 7 The block diagram is intended to show a high-level view of the components of computer platform 700. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur in other implementations.

[0170] The application circuit 705 may include circuits such as, but not limited to, a single-core or multi-core processor and one or more of the following: cache memory, a low dropout regulator (LDO), an interrupt controller, a serial interface such as a serial peripheral interface (SPI), an internal integrated circuit (I2C) or a general programmable serial interface circuit, a real-time clock (RTC), a timer-counter including an interval timer and a watchdog timer, a general input / output (IO), a memory card controller such as a secure digital / multimedia card (SD / MMC) or similar products, a universal serial bus (USB) interface, a mobile industry processor interface (MIPI) interface, and a joint test access group (JTAG) test access port. The processor may include any combination of a general-purpose processor and / or a dedicated processor (e.g., a graphics processor, an application processor, etc.). The processor (or core) may be coupled to or may include a memory / storage device and may be configured to execute instructions stored in the memory / storage device to enable various applications or operating systems to run on the platform 700. In some embodiments, the processor of the application circuit 605 / 705 may process IP data packets received from the EPC or 5GC.

[0171] The application circuit 705 may be or include a microprocessor, a multi-core processor, a multi-threaded processor, an ultra-low voltage processor, an embedded processor, or other known processing elements. In one example, the application circuit 705 may include a processor based on Architecture Core TM Processors such as Quark TM 、Atom TM , i3, i5, i7 or MCU class processors, or available from Santa Clara, CA company( The processor of the application circuit 705 may also be one or more of the following: Advanced Micro Devices (AMD) Processor or Accelerated Processing Unit (APU); from Inc.'s A5-A9 processors, Snapdragon by Technologies, Inc. TM Processor, Texas Instruments, Open Multimedia Applications Platform(OMAP) TMprocessor; MIPS-based designs from MIPS Technologies, Inc.; ARM-based designs from ARM Holdings, Ltd.; etc. In some implementations, the application circuit 705 can be part of a system on a chip (SoC), where the application circuit 705 and other components are formed as a single integrated circuit or a single package, such as company( Edison Corporation TM or Galileo TM SoC board.

[0172] Additionally or alternatively, the application circuit 705 may include circuits such as, but not limited to, one or more field programmable devices (FPDs) such as FPGAs, etc.; programmable logic devices (PLDs) such as complex PLDs (CPLDs), high capacity PLDs (HCPLDs), etc.; ASICs such as structured ASICs, etc.; programmable SoCs (PSoCs); etc. In such embodiments, the circuits of the application circuit 705 may include logic blocks or logic structures, and other interconnected resources that can be programmed to perform various functions such as the processes, methods, functions, etc. of the various embodiments discussed herein. In such embodiments, the circuits of the application circuit 705 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), anti-fuse, etc.)) for storing logic blocks, logic structures, data, etc. in look-up tables (LUTs), etc.

[0173] Baseband circuit 710 can be implemented as, for example, a solder-in substrate, which 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. Although not shown, baseband circuit 710 may include one or more digital baseband systems, which may be coupled to a CPU subsystem, an audio subsystem, and an interface subsystem via an interconnect subsystem. The digital baseband subsystem may also be coupled to a digital baseband interface and a mixed signal baseband subsystem via another interconnect subsystem. Each of the interconnect subsystems may include a bus system, a point-to-point connector, a network on chip (NOC) structure, and / or some other suitable bus or interconnect technology, such as those discussed herein. The audio subsystem may include a digital signal processing circuit, a buffer memory, a program memory, a voice processing accelerator circuit, a data converter circuit such as an analog-to-digital converter circuit and a digital-to-analog converter circuit, an analog circuit including one or more of an amplifier and a filter, and / or other similar components. In one aspect of the disclosure, baseband circuitry 710 may include protocol processing circuitry having one or more control circuit instances (not shown) to provide control functionality for digital baseband circuitry and / or radio frequency circuitry (eg, radio front end module 715).

[0174] The radio front end module (RFEM) 715 may include a millimeter wave 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 separated 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, both millimeter wave and sub-millimeter wave radio functions may be implemented in the same physical radio front end module 715. The RFEM 715 may combine both millimeter wave antennas and sub-millimeter wave antennas.

[0175] The memory circuit 720 may include any number and type of memory devices for providing a fixed amount of system memory. For example, the memory circuit 720 may include one or more of the following: volatile memory, including random access memory (RAM), dynamic RAM (DRAM) and / or synchronous dynamic RAM (SDRAM); and non-volatile memory, including high-speed electrically erasable memory (commonly referred to as flash memory), phase change random access memory (PRAM), magnetoresistive random access memory (MRAM), etc. The memory circuit 720 may be developed according to the Joint Electron Device Engineering Council (JEDEC) based low power double data rate (LPDDR) design such as LPDDR2, LPDDR3, LPDDR4, etc. The memory circuit 720 may be implemented as one or more of the following: a solder-in package integrated circuit, a single die package (SDP), a dual die package (DDP) or a quad die package (Q17P), a socketed memory module, a dual in-line memory module (DIMM) including a micro DIMM or a mini DIMM, and / or soldered to a motherboard via a ball grid array (BGA). In a low-power implementation, the memory circuit 720 may be an on-chip memory or register associated with the application circuit 705. To provide persistent storage of information such as data, applications, operating systems, etc., the memory circuit 720 may include one or more mass storage devices, which may include, among others, a solid-state disk drive (SSDD), a hard disk drive (HDD), a micro HDD, a resistive change memory, a phase change memory, a holographic memory, or a chemical memory. For example, the computer platform 700 may be combined with and Three-dimensional (3D) cross-point (XPOINT) memory.

[0176] Removable memory circuitry 723 may include devices, circuitry, housings / casings, ports or receptacles, etc., for coupling portable data storage devices to platform 700. 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.

[0177] The platform 700 may also include an interface circuit (not shown) for connecting an external device to the platform 700. The external device connected to the platform 700 via the interface circuit may include a sensor 721, such as an accelerometer, a level sensor, a flow sensor, a temperature sensor, a pressure sensor, a barometric pressure sensor, etc. The interface circuit may be used to connect the platform 700 to an electromechanical component (EMC) 722, which may allow the platform 700 to change its state, position, and / or orientation, or to move or control a mechanism or system. The EMC 722 may include one or more power switches, relays (including electromechanical relays (EMRs) and / or solid-state relays (SSRs)), actuators (e.g., valve actuators, etc.), audible sound generators, visual warning devices, motors (e.g., DC motors, stepper motors, etc.), wheels, thrusters, propellers, claws, clamps, hooks, and / or other similar electromechanical components. In an embodiment, the platform 700 may be configured to operate one or more EMCs 722 based on one or more capture events and / or instructions or control signals received from a service provider and / or various clients.

[0178] In some implementations, the interface circuit can connect the platform 700 to the positioning circuit 745, which can communicate with the reference Figure 6 The positioning circuit 645 discussed is the same or similar.

[0179] In some implementations, the interface circuit can connect the platform 700 to a near field communication (NFC) circuit 740, which can include an NFC controller coupled to an antenna element and a processing device. The NFC circuit 740 can be configured to read an electronic tag and / or connect to another NFC-enabled device.

[0180] The driver circuit 746 may include software and hardware elements for controlling specific devices embedded in, attached to, or otherwise communicatively coupled to the platform 700. The driver circuit 746 may include various drivers to allow other components of the platform 700 to interact with or control various input / output (I / O) devices that may be present in or connected to the platform 700. For example, the driver circuit 746 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 700, a sensor driver for obtaining sensor readings of the sensor 721 and controlling and allowing access to the sensor 721, an EMC driver for obtaining actuator positions of the EMC 722 and / or controlling and allowing access to the EMC 722, 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.

[0181] A power management integrated circuit (PMIC) 725 (also referred to as “power management circuit 725”) may manage power provided to various components of the platform 700. Specifically, the PMIC 725 may control power selection, voltage scaling, battery charging, or DC-DC conversion with respect to the baseband circuit 710. The PMIC 725 may typically be included when the platform 700 is capable of being powered by a battery 730, such as when the device is included in a UE 104.

[0182] In some embodiments, the PMIC 725 may control or otherwise be part of various power saving mechanisms of the platform 700. For example, if the platform 700 is in the RRC_Connected state, where the device is still connected to the RAN node because it expects to receive traffic immediately, then after a period of inactivity, the device may enter a state known as discontinuous reception mode (DRX). During this state, the platform 700 may be powered off for short time intervals, thereby saving power. If there is no data traffic activity for an extended period of time, the platform 700 may transition to the RRC_Idle state, where the device is disconnected from the network and no operations such as channel quality feedback, handover, etc. are performed. The platform 700 enters a very low power state and performs paging, where the device wakes up periodically again to listen to the network and then powers off again. The platform 700 may not receive data in this state; in order to receive data, the platform must transition back to the RRC_Connected state. Additional power saving modes may prevent the device from using the network for longer than the paging interval (ranging from a few seconds to a few hours). During this time, the device is completely unable to connect to the network and can be completely powered off. Any data sent during this time will be significantly delayed, and it is assumed that the delay is acceptable.

[0183] The battery 730 can power the platform 700, but in some examples, the platform 700 can be mounted in a fixed location and can have a power source coupled to a power grid. The battery 730 can be a lithium-ion battery, a metal-air battery such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, etc. In some implementations, such as in V2X applications, the battery 730 can be a typical lead-acid car battery.

[0184] In some implementations, the battery 730 may be a "smart battery" that includes or is coupled to a battery management system (BMS) or a battery monitoring integrated circuit. The BMS may be included in the platform 700 to track the state of charge (SoCh) of the battery 730. The BMS may be used to monitor other parameters of the battery 730, such as the state of health (SoH) and state of function (SoF) of the battery 730 to provide fault prediction. The BMS may transmit information about the battery 730 to the application circuit 705 or other components of the platform 700. The BMS may also include an analog-to-digital (ADC) converter that allows the application circuit 705 to directly monitor the voltage of the battery 730 or the current from the battery 730. The battery parameters may be used to determine actions that the platform 700 may perform, such as transmission frequency, network operation, sensing frequency, etc.

[0185] A power block or other power source coupled to the grid can be coupled to the BMS to charge the battery 730. In some examples, the power block can be replaced by a wireless power receiver to obtain power wirelessly, for example, through a loop antenna in the computer platform 700. In these examples, a wireless battery charging circuit can be included in the BMS. The specific charging circuit selected can depend on the size of the battery 730 and therefore the current required. Charging can be performed using the aviation fuel standard published by the Aviation Fuel Alliance, the Qi wireless charging standard published by the Wireless Power Alliance, or the Rezence charging standard published by the Wireless Power Alliance.

[0186] The user interface circuit 750 includes various input / output (I / O) devices present in or connected to the platform 700, and includes one or more user interfaces designed to enable user interaction with the platform 700 and / or a peripheral component interface designed to enable peripheral components to interact with the platform 700. The user interface circuit 750 includes input device circuits and output device circuits. The input device circuit includes any physical or virtual means for accepting input, including, in particular, one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a touchpad, a touch screen, a microphone, a scanner, a headset, etc. The output device circuit 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, among other things, one or more simple visual outputs / indicators (e.g., 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.), where outputs of characters, graphics, multimedia objects, etc. are generated or produced by the operation of the platform 700. The output device circuitry may also include speakers or other audio emitting devices, printers, etc. In some embodiments, the sensor circuitry 721 may be used as an input device circuitry (e.g., an image capture device, a motion capture device, etc.) and one or more EMCs may be used as output device circuitry (e.g., an actuator for providing tactile feedback, etc.). In another example, an NFC circuit may be included to read an electronic tag and / or connect to another NFC-enabled device, the NFC circuitry including an NFC controller and a processing device coupled to an antenna element. The peripheral component interfaces may include, but are not limited to, a non-volatile memory port, a universal serial bus (USB) port, an audio jack, a power interface, etc.

[0187] Although not shown, the components of platform 700 can communicate with each other using a suitable bus technology, which can include any number of technologies, including industry standard architecture (ISA), extended ISA (EISA), peripheral component interconnect (PCI), peripheral component interconnect extended (PCIx), PCI express (PCIe), time triggered protocol (TTP) system, FlexRay system or any number of other technologies. The bus can be a proprietary bus, for example, used in a SoC-based system. Other bus systems such as I2C interface, SPI interface, point-to-point interface and power bus, etc. can be included.

[0188] Figure 8Exemplary components of baseband circuitry 610 / 710 and radio front end modules (RFEM) 615 / 715 are shown according to various embodiments. As shown, RFEM 615 / 715 may include radio frequency (RF) circuitry 806, front end module (FEM) circuitry 808, and one or more antennas 820 coupled together at least as shown.

[0189] The baseband circuit 610 / 710 may include circuits such as, but not limited to, one or more single-core or multi-core processors. The baseband circuit 610 / 710 may include one or more baseband processors or control logic components to process baseband signals received from the receive signal path of the RF circuit 806 and generate baseband signals for the transmit signal path of the RF circuit 806. The baseband processing circuit 610 / 710 may interact with the application circuit 605 / 705 to generate and process baseband signals and control the operation of the RF circuit 806. For example, in some embodiments, the baseband circuit 610 / 710 may include a third generation (3G) baseband processor 804A, a 4G baseband processor 804B, a 5G baseband processor 804C, or other baseband processors 804D of other existing generations, generations under development, or generations to be developed in the future (e.g., second generation (2G), sixth generation (6G), etc.). The baseband circuit 610 / 710 (e.g., one or more of the baseband processors 804A-804D) may handle various radio control functions that can communicate with one or more radio networks via the RF circuit 806. In other embodiments, some or all of the functions of the baseband processors 804A-D may be included in a module stored in the memory 804G and executed via the central processing unit (CPU) 804E. The radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, radio frequency shifting, etc. In some embodiments, the modulation / demodulation circuit of the baseband circuit 610 / 710 may include fast Fourier transform (FFT), precoding, or constellation mapping / demapping functions. In some embodiments, the encoding / decoding circuit of the baseband circuit 610 / 710 may include convolution, tail-biting convolution, turbo, Viterbi, or low-density parity check (LDPC) encoder / decoder functions. The implementation of the modulation / demodulation and encoder / decoder functions is not limited to these examples, and may include other suitable functions in other embodiments.

[0190] In some embodiments, the baseband circuit 610 / 710 may include one or more audio digital signal processors (DSPs) 804F. The audio DSP 804F may include elements for compression / decompression and echo cancellation, and may include other suitable processing elements in other embodiments. In some embodiments, the components of the baseband circuit may be appropriately combined in a single chip or a single chipset, or disposed on the same circuit board. In some embodiments, some or all of the components of the baseband circuit 610 / 710 and the application circuit 605 / 705 may be implemented together, such as, for example, on a system on a chip (SOC).

[0191] In some embodiments, the baseband circuit 610 / 710 can provide communications compatible with one or more radio technologies. For example, in some embodiments, the baseband circuit 610 / 710 can support communications with E-UTRAN or other WMANs, WLANs, WPANs. Embodiments in which the baseband circuit 610 / 710 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuits.

[0192] RF circuit 806 can use modulated electromagnetic radiation to communicate with a wireless network through a non-solid medium. In various embodiments, RF circuit 806 may include switches, filters, amplifiers, etc. to facilitate communication with a wireless network. RF circuit 806 may include a receive signal path, which may include circuits for down-converting RF signals received from FEM circuit 808 and providing baseband signals to baseband circuit 610 / 710. RF circuit 806 may also include a transmit signal path, which may include circuits for up-converting baseband signals provided by baseband circuit 610 / 710 and providing RF output signals for transmission to FEM circuit 808.

[0193] In some embodiments, the receive signal path of the RF circuit 806 may include a mixer circuit 806a, an amplifier circuit 806b, and a filter circuit 806c. In some embodiments, the transmit signal path of the RF circuit 806 may include a filter circuit 806c and a mixer circuit 806a. The RF circuit 806 may also include a synthesizer circuit 806d for synthesizing the frequencies used by the mixer circuit 806a of the receive signal path and the transmit signal path. In some embodiments, the mixer circuit 806a of the receive signal path may be configured to down-convert the RF signal received from the FEM circuit 808 based on the synthesized frequency provided by the synthesizer circuit 806d. The amplifier circuit 806b may be configured to amplify the down-converted signal, and the filter circuit 806c may be a low pass filter (LPF) or a band pass filter (BPF) configured to remove unwanted signals from the down-converted signal to generate an output baseband signal. The output baseband signal may be provided to the baseband circuit 610 / 710 for further processing. In some embodiments, the output baseband signal may be a zero frequency baseband signal, although this is not required.In some embodiments, the mixer circuit 806a of the receive signal path may include a passive mixer, although the scope of the embodiments is not limited in this respect.

[0194] In some embodiments, mixer circuit 806a of the transmit signal path may be configured to upconvert an input baseband signal based on a synthesized frequency provided by synthesizer circuit 806d to generate an RF output signal for FEM circuit 808. The baseband signal may be provided by baseband circuit 610 / 710 and may be filtered by filter circuit 806c.

[0195] In some embodiments, the mixer circuit 806a of the receive signal path and the mixer circuit 806a of the transmit signal path may include two or more mixers and may be arranged for orthogonal down-conversion and up-conversion, respectively. In some embodiments, the mixer circuit 806a of the receive signal path and the mixer circuit 806a of the transmit signal path may include two or more mixers and may be arranged for image suppression (e.g., Hartley image suppression). In some embodiments, the mixer circuit 806a of the receive signal path and the mixer circuit 806a of the transmit signal path may be arranged for direct down-conversion and direct up-conversion, respectively. In some embodiments, the mixer circuit 806a of the receive signal path and the mixer circuit 806a of the transmit signal path may be configured for superheterodyne operation.

[0196] In some embodiments, the output baseband signal and the input baseband signal may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternative embodiments, the output baseband signal and the input baseband signal may be digital baseband signals. In these alternative embodiments, the RF circuit 806 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuits, and the baseband circuit 610 / 710 may include a digital baseband interface to communicate with the RF circuit 806.

[0197] In some dual-mode embodiments, separate radio IC circuits may be provided to process signals for each spectrum, although the scope of the embodiments is not limited in this respect.

[0198] In some embodiments, synthesizer circuit 806d can be a fractional-N synthesizer or a fractional-N / N+1 synthesizer, but the scope of the embodiments is not limited in this regard, as other types of frequency synthesizers may also be suitable. For example, synthesizer circuit 806d can be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider.

[0199] Synthesizer circuit 806d may be configured to synthesize an output frequency based on a frequency input and a divider control input for use by mixer circuit 806a of RF circuit 806. In some embodiments, synthesizer circuit 806d may be a fractional-N / N+1 synthesizer.

[0200] In some embodiments, the frequency input may be provided by a voltage controlled oscillator (VCO), although this is not required. The divider control input may be provided by the baseband circuit 610 / 710 or the application circuit 605 / 705 according to the desired output frequency. In some embodiments, the divider control input (e.g., N) may be determined from a lookup table based on the channel indicated by the application circuit 605 / 705.

[0201] The synthesizer circuit 806d of the RF circuit 806 may include a frequency divider, a delay locked loop (DLL), a multiplexer, and a phase accumulator. In some embodiments, the frequency divider may be a dual-mode frequency divider (DMD), and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by N or N+1 (e.g., based on carry) to provide a fractional division ratio. In some example embodiments, the DLL may include a cascaded, tunable, delay element, a phase detector, a charge pump, and a D-type flip-flop set. In these embodiments, the delay element may be configured to divide the VCO cycle into Nd equal phase groups, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

[0202] In some embodiments, the synthesizer circuit 806d can be configured to generate a carrier frequency as an output frequency, while in other embodiments, the output frequency can be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used with a quadrature generator and divider circuit to generate multiple signals with multiple different phases relative to each other at the carrier frequency. In some embodiments, the output frequency can be the LO frequency (fLO). In some embodiments, the RF circuit 806 can include an IQ / polarity converter.

[0203] The FEM circuitry 808 may include a receive signal path that may include circuitry configured to operate on RF signals received from one or more antennas 820, amplify the received signals, and provide an amplified version of the received signals to the RF circuitry 806 for further processing. The FEM circuitry 808 may also include a transmit signal path that may include circuitry configured to amplify transmit signals provided by the RF circuitry 806 for transmission through one or more of the one or more antennas 820. In various embodiments, amplification by the transmit or receive signal path may be accomplished only in the RF circuitry 806, only in the FEM circuitry 808, or in both the RF circuitry 806 and the FEM circuitry 808.

[0204] In some embodiments, the FEM circuit 808 may include a TX / RX switch to switch between transmit mode and receive mode operation. The FEM circuit 808 may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuit 808 may include an LNA to amplify the received RF signal and provide the amplified received RF signal as an output (e.g., to the RF circuit 806). The transmit signal path of the FEM circuit 808 may include a power amplifier (PA) to amplify the input RF signal (e.g., provided by the RF circuit 806); and one or more filters to generate an RF signal for subsequent transmission (e.g., through one or more of the one or more antennas 820).

[0205] The processor of the application circuit 605 / 705 and the processor of the baseband circuit 610 / 710 can be used to execute elements of one or more instances of the protocol stack. For example, the processor of the baseband circuit 610 / 710 can be used alone or in combination to perform layer 3, layer 2, or layer 1 functions, and the processor of the application circuit 605 / 705 can utilize data received from these layers (e.g., packet data) and further perform layer 4 functions (e.g., TCP and UDP layers). As mentioned herein, layer 3 may include an RRC layer, which will be described in further detail below. As mentioned herein, layer 2 may include a MAC layer, an RLC layer, and a PDCP layer, which will be described in further detail below. As mentioned herein, layer 1 may include a PHY layer of a UE / RAN node, which will be described in further detail herein.

[0206] Fig. 9 is a block diagram illustrating components capable of reading instructions from a machine-readable medium 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 exemplary embodiments. Specifically, Fig. 9 A schematic diagram of hardware resources 900 is shown, including one or more processors (or processor cores) 910, one or more memory / storage devices 920, and one or more communication resources 930, each of which may be communicatively coupled via a bus 940. As used herein, the terms "computing resources," "hardware resources," and the like may refer to physical or virtual devices, physical or virtual components within a computing environment, and / or physical or virtual components within a particular device, such as computer equipment, mechanical equipment, memory space, processor / CPU time and / or processor / CPU usage, processor and accelerator load, hardware time or usage, power, input / output operations, ports or network sockets, channel / link allocation, throughput, memory usage, storage, network, database, and applications, etc. For embodiments in which node virtualization (e.g., NFV) is utilized, a hypervisor 902 may be executed to provide an execution environment for one or more network slices / subslices to utilize hardware resources 900. "Virtualized resources" may refer to computing, storage, and / or network resources provided by a virtualization infrastructure to applications, devices, systems, and the like.

[0207] Processor 910 (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, processor 1012 and processor 914.

[0208] The memory / storage device 920 may include main memory, disk storage, or any suitable combination thereof. The memory / storage device 920 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, etc.

[0209] The communication resources 930 may include an interconnect or network interface component or other suitable device to communicate with one or more peripheral devices 904 or one or more databases 906 via the network 908. For example, the communication resources 1030 may include a wired communication component (e.g., for coupling via a universal serial bus (USB)), a cellular communication component, an NFC component, Parts (e.g. Low power consumption), Components and other communication components. As used herein, the term "network resource" or "communication resource" may refer to a computing resource that can be accessed by a computer device via a communication network. The term "system resource" may refer to any kind of shared entity that provides a service, and may include computing resources and / or network resources. System resources can be considered as a set of coherent functions, network data objects, or services that can be accessed by a server, wherein such system resources reside on a single host or multiple hosts and can be clearly identified. Instructions 950 may include software, programs, applications, applets, applications, or other executable codes for causing at least any one of the processors 910 to perform any one or more of the methods discussed herein. Instructions 950 may reside completely or partially in at least one of the processors 910 (e.g., in the cache memory of the processor), in the memory / storage device 920, or in any suitable combination thereof. In addition, any portion of the instructions 950 may be transmitted to the hardware resources 900 from any combination of the peripheral device 904 or the database 906. Thus, the memory of processor 910, memory / storage device 920, peripheral device 904, and database 906 are examples of computer-readable media and machine-readable media.

[0210] 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, processes and / or methods described in the following example section. For example, the baseband circuit described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the following embodiments. For another example, the circuits associated with the UE, base station, network element, etc. described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the embodiments shown in the example section below.

[0211] Some non-limiting examples of various embodiments are provided below.

[0212] Embodiment 1 is one or more computer readable media (CRM) having stored thereon instructions that, when executed by one or more processors, cause a user equipment (UE) to: determine that the mobility of the UE is low or very high; and based on the determination, extend the time period between radio resource management (RRM) measurements of one or more cells of a wireless cellular network.

[0213] Embodiment 2 is one or more CRMs according to embodiment 1 or another embodiment of the present invention, wherein the instruction is also used to cause the UE to determine whether the mobility is normal, medium or high, wherein the low mobility is a mobility lower than the normal mobility and the very high mobility is greater than the high mobility.

[0214] Embodiment 3 is one or more CRMs according to embodiments 1 to 2 or another embodiment herein, wherein the determination is a determination that the mobility of the UE is low.

[0215] Embodiment 4 is one or more CRMs according to embodiment 3 or another embodiment herein, wherein if the number of cell reselections during a defined time period is less than a threshold, the UE determines that the mobility of the UE is low.

[0216] Embodiment 5 is one or more CRMs according to embodiment 3 or another embodiment herein, wherein if the number of cell reselections during a defined time period is 0, the UE determines that the mobility of the UE is low.

[0217] Embodiment 6 is one or more CRMs according to embodiments 1 to 2 or another embodiment herein, wherein the determination is a determination that the mobility of the UE is very high.

[0218] Embodiment 7 is one or more CRMs according to embodiments 1 to 6 or another embodiment herein, wherein the mobility of the UE is a fixed configuration of the UE.

[0219] Embodiment 8 is one or more CRMs according to embodiments 1 to 7 or another embodiment herein, wherein the UE is configured to extend the time period between RRM measurements based on a determination of whether the UE is in RRC_IDLE or RRC_INACTIVE state.

[0220] Embodiment 9 is one or more CRMs according to embodiments 1 to 8 or another embodiment of the present invention, wherein the instruction, when executed, also causes the UE to encode a message for transmission to a next generation Node B (gNB) of the wireless cellular network to indicate the mobility of the UE.

[0221] Embodiment 10 is one or more CRMs according to embodiments 1 to 9 or another embodiment herein, wherein the UE is configured to extend the time period between RRM measurements by skipping one or more RRM measurements.

[0222] Embodiment 11 is one or more CRMs according to embodiments 1 to 10 or another embodiment of the present invention, wherein the UE is used to extend the time period between RRM measurements for a subset of cells, measurement objects or frequencies on which the UE operates.

[0223] Embodiment 12 is one or more CRMs according to embodiments 1 to 11 or another embodiment of this document, wherein the instruction, when executed, is further used to cause the UE to:

[0224] receiving configuration information for a channel state information reference signal (CSI-RS) and a synchronization signal (SS) / physical broadcast channel (PBCH) block (SSB); and

[0225] Determine to skip RRM measurement of the CSI-RS or the SSB.

[0226] Embodiment 13 is one or more CRMs according to any one of embodiments 1 to 12 or another embodiment of the present invention, wherein the UE is used to further extend the time period between RRM measurements based on a received signal received power (RSRP), received signal received quality (RSRQ), or signal to interference plus noise ratio (SINR) for a cell associated with the RRM measurement.

[0227] Embodiment 14 is one or more computer-readable media (CRM) having stored thereon instructions that, when executed by one or more processors, cause a next-generation Node B (gNB) of a wireless cellular network to perform the following operations: receiving an indication from a user equipment (UE) that the mobility of the UE is low or very high, wherein the UE is further configured to determine whether the mobility of the UE is normal, medium, or high, wherein the low mobility is a lower mobility than the normal mobility, and wherein the very high mobility is greater than the high mobility; and adjusting one or more parameters for the UE based on the indication.

[0228] Embodiment 15 is one or more CRMs according to embodiment 14 or another embodiment herein, wherein the adjustment of the one or more parameters comprises extending a time period between radio resource management (RRM) measurements of one or more cells of the wireless cellular network.

[0229] Embodiment 16 is one or more CRMs according to embodiments 14 to 15 or another embodiment herein, wherein the indication is an indication that the mobility of the UE is low.

[0230] Embodiment 17 is one or more CRMs according to embodiments 14 to 15 or another embodiment herein, wherein the indication is an indication that the mobility of the UE is very high.

[0231] Embodiment 18 is one or more CRMs according to embodiments 14 to 17 or another embodiment herein, wherein the mobility of the UE is a fixed configuration of the UE.

[0232] Embodiment 19 is one or more CRMs according to embodiments 14 to 18 or another embodiment of the present invention, wherein the UE is in RRC_IDLE, RRC_INACTIVE, or RRC_CONNECTED state relative to the gNB.

[0233] Embodiment 20 is one or more computer-readable media (CRM) having stored thereon instructions that, when executed by one or more processors, cause a user equipment (UE) to: receive configuration information indicating at least one of a maximum number of radio frequency (RF) chains, a maximum number of antennas, or a maximum number of MIMO layers to be used by the UE; and limit use of the RF chain, the antenna, or the MIMO layer to the corresponding maximum number.

[0234] Embodiment 21 is one or more CRMs according to embodiment 20 or another embodiment herein, wherein the UE is configured to limit the usage of the RF chain, the antenna, or the MIMO layer to the corresponding maximum network under certain network conditions.

[0235] Embodiment 22 is one or more CRMs according to embodiments 20 to 21 or another embodiment herein, wherein the configuration information is used to indicate the maximum number of MIMO layers to be used by the UE.

[0236] Unless explicitly stated otherwise, any of the above embodiments may be combined with any other embodiment (or combination of embodiments). The foregoing description of one or more specific 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. In view of the above teachings, modifications and variations are possible or can be obtained from the practice of various embodiments.

Claims

1. One or more computer readable media CRM having stored thereon instructions which, when executed by one or more processors, cause a user equipment UE of a wireless cellular network to: receiving configuration information indicating a maximum number of RF chains or a maximum number of MIMO layers to be used by the UE; and The usage of the number of RF chains is reduced to the maximum number of RF chains or the usage of the number of MIMO layers is reduced to the maximum number of MIMO layers.

2. The one or more CRMs of claim 1, wherein the instructions, when executed by one or more processors, cause the UE to reduce usage of the number of RF chains or the number of MIMO layers based on mobility of the UE.

3. The one or more CRMs of claim 1, wherein the instructions, when executed by one or more processors, cause the UE to reduce usage of the number of RF chains or the number of MIMO layers based on a network query.

4. The one or more CRMs of claim 1, wherein the instructions, when executed by one or more processors, cause the UE to reduce usage of the number of RF chains or the number of MIMO layers based on a trigger or a network request.

5. The one or more CRMs of claim 4, wherein the instructions, when executed by one or more processors, further cause the UE to provide a preference for reducing usage of the number of RF chains or the number of MIMO layers via an L1 mechanism.

6. The one or more CRMs of claim 4, wherein the instructions, when executed by one or more processors, further cause the UE to provide a preference for reducing usage of the number of RF chains or the number of MIMO layers via an L2 mechanism.

7. One or more CRMs according to claim 1, wherein the instructions, when executed by one or more processors, cause the UE to: reduce the number of RF chains or the use of the number of MIMO layers based on a specific mobility state, information provided on a traffic status report, or an indication provided by the wireless cellular network for the UE to change the number of RF chains or the use of the number of MIMO layers.

8. A user equipment UE, comprising: A front-end circuit configured to receive configuration information indicating a maximum number of radio frequency (RF) chains or a maximum number of MIMO layers to be used by the UE; as well as A processor circuit is configured to reduce usage of the number of RF chains to the maximum number of RF chains or to reduce usage of the number of MIMO layers to the maximum number of MIMO layers.

9. The UE of claim 8, wherein the processor circuit is configured to reduce usage of the number of RF chains or the number of MIMO layers based on mobility of the UE.

10. The UE of claim 8, wherein the processor circuit is configured to reduce usage of the number of RF chains or the number of MIMO layers based on a network query.

11. The UE of claim 8, wherein the processor circuit is configured to reduce usage of the number of RF chains or the number of MIMO layers based on a trigger or a network request. 12 . The UE of claim 10 , wherein the processor circuit is further configured to provide a preference for reducing usage of the number of RF chains or the number of MIMO layers via an L1 mechanism.

13. The UE of claim 10, wherein the processor circuit is further configured to provide a preference for reducing usage of the number of RF chains or the number of MIMO layers via an L2 mechanism.

14. The UE according to claim 8, wherein the processor circuit is configured to reduce the number of RF chains or the usage of the number of MIMO layers based on a specific mobility state, information provided on a traffic status report, or an indication provided by the network for the UE to change the number of RF chains or the usage of the number of MIMO layers.

15. A method comprising: Receiving, by a user equipment UE, configuration information indicating a maximum number of radio frequency (RF) chains or a maximum number of MIMO layers to be used by the UE; as well as The UE reduces usage of the number of RF chains to the maximum number of RF chains or reduces usage of the number of MIMO layers to the maximum number of MIMO layers.

16. The method of claim 15, wherein said reducing comprises: The number of RF chains or the usage of the number of MIMO layers is reduced based on the mobility of the UE.

17. The method of claim 15, wherein said reducing comprises: The number of RF chains or the use of the number of MIMO layers is reduced based on a network query.

18. The method of claim 15, wherein said reducing comprises: The usage of the number of RF chains or the number of MIMO layers is reduced based on a trigger or a network request.

19. The method according to claim 18, further comprising: A preference to reduce usage of the number of RF chains or the number of MIMO layers is provided by the UE via an L2 mechanism.

20. The method of claim 15, wherein said reducing comprises: Reducing the number of RF chains or the usage of the number of MIMO layers based on a specific mobility state, information provided on a traffic state report, or an indication provided by the network for the UE to change the number of RF chains or the usage of the number of MIMO layers.

Images