+

WO2020092732A1 - Mesures en état de repos de rrc dans des systèmes de nouvelle radio (nr) - Google Patents

Mesures en état de repos de rrc dans des systèmes de nouvelle radio (nr) Download PDF

Info

Publication number
WO2020092732A1
WO2020092732A1 PCT/US2019/059106 US2019059106W WO2020092732A1 WO 2020092732 A1 WO2020092732 A1 WO 2020092732A1 US 2019059106 W US2019059106 W US 2019059106W WO 2020092732 A1 WO2020092732 A1 WO 2020092732A1
Authority
WO
WIPO (PCT)
Prior art keywords
cell
ssb
frequency
circuitry
measurement
Prior art date
Application number
PCT/US2019/059106
Other languages
English (en)
Inventor
Rui Huang
Zhibin Yu
Qiming Li
Hua Li
Yang Tang
Jie Cui
Original Assignee
Intel Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Intel Corporation filed Critical Intel Corporation
Priority to EP19879574.2A priority Critical patent/EP3874816A4/fr
Publication of WO2020092732A1 publication Critical patent/WO2020092732A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W56/00—Synchronisation arrangements
    • H04W56/001—Synchronization between nodes
    • H04W56/0015—Synchronization between nodes one node acting as a reference for the others
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/16—Discovering, processing access restriction or access information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • H04W68/02—Arrangements for increasing efficiency of notification or paging channel
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states

Definitions

  • Embodiments of the present invention relate generally to the technical field of wireless communications.
  • a UE is required to perform
  • the UE also monitors paging occasions on its serving cell while in RRC IDLE.
  • the UE must power on (e.g., enter a higher power state) to perform these measurements, which can consume significant energy.
  • Figure 1 illustrates a network in accordance with some embodiments.
  • Figure 2 graphically illustrates synchronization signal/physical broadcast channel block (SSB) bursts and paging occasions for a serving cell, an intra-frequency cell, and an inter- frequency cell, along with corresponding measurements performed by the UE, in accordance with an example of various embodiments.
  • SSB synchronization signal/physical broadcast channel block
  • Figure 3 graphically illustrates a more detailed view of one set of SSBs and paging occasions for the serving cell, in accordance with various embodiments.
  • Figure 4 illustrates an operation flow/algorithmic structure in accordance with some embodiments.
  • FIG. 5 illustrates an example of infrastructure equipment in accordance with various embodiments.
  • Figure 6 depicts example components of a computer platform or device in accordance with various embodiments.
  • Figure 7 depicts example components of baseband circuitry and radio frequency end modules in accordance with various embodiments.
  • Figure 8 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (for example, a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein.
  • a machine-readable or computer-readable medium for example, a non-transitory machine-readable storage medium
  • FIG. 1 illustrates a network 100 in accordance with some embodiments.
  • 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.
  • RAN radio access network
  • the base station 108 may be referred to as a base station (“BS”), NodeB, evolved NodeB (“eNB”), next generation NodeB (“gNB”), RAN node, Road Side Unit (“RSU”), and so forth, and can comprise a ground station (e.g., a terrestrial access point) or a satellite station providing coverage within a geographic area (for example, a cell).
  • An RSU may refer to any transportation infrastructure entity implemented in or by a gNB/eNB/RAN node or a stationary (or relatively stationary) UE, where an RSU implemented in or by a UE may be referred to as a“UE-type RSU,” and an RSU implemented in or by an gNB may be referred to as a“gNB-type RSU.”
  • the RAN may be a next generation (“NG”) radio access network (“RAN”), in which case the base station 108 may be a gNB that communicates with the UE 104 using a new radio (“NR”) access technology.
  • the RAN 112 may be a NR wireless cellular network.
  • the UE 104 may be any mobile or non-mobile computing device that is connectable to one or more cellular networks.
  • the UE 104 may be a smartphone, a laptop computer, a desktop computer, a vehicular computer, a smart sensor, etc.
  • the UE 104 may be an Internet of Things (“IoT”) UE, which may include a network access layer designed for low-power IoT applications utilizing short-lived UE connections.
  • IoT Internet of Things
  • An IoT UE can utilize technologies such as machine-to-machine (“M2M”) or machine-type communications (“MTC”) for exchanging data with an MTC server or device via a public land mobile network (“PLMN”), Proximity-Based Service (“ProSe”) or device-to-device (“D2D”) communication, sensor networks, or IoT networks.
  • M2M or MTC exchange of data may be a machine- initiated exchange of data.
  • An IoT network describes interconnecting IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-lived connections.
  • the IoT UEs may execute background applications (for example, keep-alive messages, status updates, etc.) to facilitate the connections of the IoT network.
  • the UE 104 can be configured to communicate using Orthogonal Frequency -Division Multiplexing (“OFDM”) communication signals with the base station 108 over a multicarrier communication channel in accordance with various communication techniques, such as, but not limited to, an Orthogonal Frequency -Division Multiple Access (“OFDMA”) communication technique (for example, for downlink
  • OFDM Orthogonal Frequency -Division Multiplexing
  • OFDMA Orthogonal Frequency -Division Multiple Access
  • the OFDM signals can comprise a plurality of orthogonal subcarriers.
  • a downlink resource grid can be used for downlink transmissions from the base station 108 to the UE 104, while uplink transmissions can utilize similar techniques.
  • the grid can be a time-frequency grid, called a resource grid or time-frequency resource grid, which is the physical resource in the downlink in each slot.
  • a time-frequency plane representation is a common practice for OFDM systems, which makes it intuitive for radio resource allocation.
  • Each column and each row of the resource grid corresponds to one OFDM symbol and one OFDM subcarrier, respectively.
  • the duration of the resource grid in the time domain corresponds to one slot in a radio frame.
  • the smallest time-frequency unit in a resource grid is denoted as a resource element.
  • Each resource grid comprises a number of resource blocks, which describe the mapping of certain physical channels to resource elements.
  • Each resource block comprises a collection of resource elements; in the frequency domain, this may represent the smallest quantity of resources that currently can be allocated. There are several different physical channels that are conveyed using such resource blocks.
  • the UE 104 may perform radio resource management (RRM), in which the UE 104 measures feedback information on one or more measurement objects (MO) (e.g., cells).
  • the feedback information may include, for example, a received signal received power (RSRP), a received signal received quality (RSRQ), a signal to interference plus noise ratio (SINR), a channel quality indicator (CQI), and/or another suitable quality metric.
  • the feedback information may be measured on one or more reference signals transmitted by the respective measurement object.
  • the reference signal may include a synchronization signal (SS)/physical broadcast channel (PBCH) block (SSB) and/or a channel state information reference signal (CSI-RS).
  • SS synchronization signal
  • PBCH physical broadcast channel
  • CSI-RS channel state information reference signal
  • the UE 104 may transmit the feedback information to the gNB 108.
  • the gNB 108 may use the feedback information, for example, to determine one or more configuration parameters for the UE 104 to communicate on the RAN 108 and/or whether to handover the UE 104 to a different serving cell.
  • UE side conditions for performing RRM measurements on identified cells are reused from Long Term Evolution (LTE).
  • LTE Long Term Evolution
  • UE’s side conditions for identified a cell can be different.
  • options for UE side conditions for RRM measurements in an NR cell include:
  • PSS primary synchronization signal
  • SSS secondary synchronization signal
  • UE knows the PSS/SSS boundary timing and the SSB timing index that corresponds to the specific SSB that is to be measured by the UE.
  • the UE would need to perform the RRM measurements for all SSBs in a SSB measurement time configuration (SMTC). Accordingly, the UE would perform unnecessary RRM measurements, and/or be powered on for a longer period of time.
  • SMTC SSB measurement time configuration
  • the UE may perform the RRM measurements for only the SSBs that correspond to the SSB indexes for the UE (e.g., for intra-frequency and/or inter-frequency cells). Accordingly, the UE may be powered on for less time, and/or may be able to perform RRM measurements on more cells within the same time period (e.g., discontinuous reception (DRX) cycle and/or SSB burst period).
  • DRX discontinuous reception
  • the UE knows the SSB index (e.g., in addition to the PSS/SSS symbol timing boundary) for the specific SSBs within an SMTC that are to be measured by the UE (e.g., that use the transmit beam associated with the UE).
  • the UE may know the SSB index(es) via network signaling.
  • the SSB may be quasi-colocated with another signal, such as another reference signal and/or a physical downlink shared channel (PDSCH).
  • the SSB indexes of the SSBs within an SMTC may be predefined by the network.
  • the SSB indexes may be predefined for respective channels/bands of the network. It will be apparent that other mechanisms for the UE to determine the SSB index may be used.
  • the UE is to be able to identify new intra- frequency cells and perform synchronization signal received signal received power (SS-RSRP) and synchronization signal received signal received quality (SS-RSRQ) measurements of the identified intra-frequency cells without an explicit intra-frequency neighbour list containing physical layer cell identities.
  • An intra frequency cell is considered to be detectable according to the conditions for a corresponding Band.
  • the UE is to measure SS-RSRP and SS-RSRQ at least every T measure, NR_Intra for intra- frequency cells that are identified and measured according to the measurement rules.
  • the UE is to filter SS-RSRP and SS- RSRQ measurements of each measured intra-frequency cell using at least 2 measurements. Within the set of measurements used for the filtering, at least two measurements is to be spaced by at least Tmeasure.NR intra/2.
  • the UE is to measure SS-RSRP or SS-RSRQ at least every Kcamer * T measure, NR_intcr (see e.g., table 2 infra) for identified lower or equal priority inter-frequency cells. If the UE detects on a NR carrier a cell whose physical identity is indicated as not allowed for that carrier in the measurement control system information of the serving cell, the UE is not required to perform measurements on that cell.
  • the UE is to filter SS-RSRP or SS-RSRQ measurements of each measured higher, lower and equal priority inter-frequency cell using at least 2 measurements. Within the set of measurements used for the filtering, at least two measurements is to be spaced by at least T measure, NR_Inter/2.
  • the UE when the UE measures SS-RSRP and SS-RSRQ at least every T measure, NR_xxx (see tables 1 and 2 infra) for the identified intra/inter- frequency cells, the following side condition shall be clarified as: the SSB index is known by the UE.
  • the embodiments herein provide significant power saving gains when the UE is performs intra/inter-frequency measurement in RRC IDLE state with known SSB timing. Additionally, it may be possible to support more measurement carriers if the measurement occurred within an associated SSB.
  • Embodiment 1 the UE is synchronized with PSS/SSS symbol boundary only. In this
  • the UE would only need to perform the intra-frequency and inter-frequency measurements over all SSBs in SMTC.
  • Embodiment 2 the UE obtained both PSS/SSS and SSB timing index when identifying a cell.
  • the UE can perform the intra-frequency and inter-frequency measurements within a specific SSB belonging this UE.
  • the UE when the UE performs the measurement on the target intra/inter-frequency cells, the UE may be powered-on (e.g.,“awake” to receive signals) over a whole SMTC window in which all possible SSBs transmitted by gNB are included.
  • the UE may be powered-on (e.g.,“awake” to receive signals) over a whole SMTC window in which all possible SSBs transmitted by gNB are included.
  • the total power consumption will be increased greatly.
  • the total UE power-on time for NR RRC Idle measurement and paging every DRX cycle may be as follows:
  • Embodiment 1 3*(2*T_rf+ T smtc)
  • T_rf is the duration of UE RF retuning which is about 200us typically
  • T smtc is the duration of a SMTC window (5ms)
  • T_ssb is the duration of a SSB which include 4 OFDM symbols.
  • Embodiment 1 may guarantee that the UE completes the intra/inter-frequency measurement within a shorter delay (e.g., the additional 1 SMTC may be needed in order to get SSB timing index at most).
  • the implementation with the side condition to enable short measurement time may be preferable.
  • UE power consumption is a key considerations for NR RRC IDLE state requirements.
  • the UE can be much more flexible to implement the inter-frequency measurement in NR RRC IDLE. For example, if SSB index of measured cell is known, the UE can perform both inter-frequency measurements with the intra-frequency measurements or paging in a same SMTC window. As a result, it is feasible to support more inter-frequency carriers within a limited delay.
  • Figure 2 graphically illustrates a graph 202 that shows SSBs 204a-b and paging occasions 206 for a serving cell, a graph 208 that shows SSBs 2l0a-b for an intra-frequency cell, and a graph 212 that illustrates SSBs 2l4a-b for an inter-frequency cell.
  • the different SSBs within a same SMTC may be transmitted using different configurations, such as different transmit beams.
  • Figure 2 further illustrates a graph 216 of RRM measurements and paging monitoring under embodiment 1 described above (e.g., the UE knows the PSS/SSS timing boundary, but does not know the SSB index for the SSB relevant to the UE), and a graph 218 of RRM measurements and paging monitoring under embodiment 2 described above (e.g., the UE knows the PSS/SSS timing boundary and the SSB index for the SSB relevant to the UE).
  • the paging occasions 206 may be quasi-colocated (QCLed) with the respective SSBs 204a-b of the serving cell (e.g., as shown in Figure 3), and the UE may utilize automatic gain control (AGC) for the paging occassions 206.
  • QCL automatic gain control
  • the UE performs an RRM measurement 220 on the intra-frequency cell during a first SSB burst period 222, an RRM measurement 224 on the inter-frequency cell during a second SSB burst period 226, and monitors a paging occasion 228 on the serving cell during the second SSB burst period 226.
  • the RRM measurement 220, RRM measurement 224, and monitoring 228 are each performed for a duration of an entire SMTC window (e.g., during all SSBs 204a-b, 2l4a-b, and 2l0a-b, respectively). Accordingly, the RRM measurement 224 and monitoring 228 are performed during separate SMTC windows of the second SSB burst period 226.
  • the UE performs an RRM measurement 230 on the intra-frequency cell during the first SSB period 222, an RRM measurement 232 on the inter-frequency cell during the second SSB burst period 226, and monitors a paging occasion 234 during the second SSB burst period.
  • the RRM measurement 230, RRM measurement 232, and monitoring 234 are performed for the duration of one SSB. Accordingly, the UE may be powered on for less time. Additionally, or alternatively, the UE may multiple RRM measurements and/or paging monitoring instances within a same SMTC window. For example, as shown in graph 218, the UE may perform paging monitoring 234 and RRM measurement 232 within the same SMTC window.
  • the UE is to measure SS-RSRP and SS-RSRQ at least every T measure, NR_xxx for the identified intra/inter-frequency cells, the following side condition shall be clarified as: the SSB index is known by UE.
  • the value of T measure. ⁇ R_ ⁇ W is based on the values given by tables 1 and 2, where“xxx” is“NR_Intra” or “NR Inter.”
  • Table 2 Tdetect ,NR_Inter, Tmeasure,NR_Inter nd T evaluate, NR_Inter
  • new side condition for UE measurement in NR RRC IDLE mode may be applied as follows:
  • the UE shall be able to identify new intra-frequency cells and perform SS-RSRP and SS-RSRQ measurements of the identified intra-frequency cells given associated SSB timing index known by UE without an explicit intra-frequency neighbour list containing physical layer cell identities.
  • An intra frequency cell is considered to be detectable according to the conditions for a corresponding Band.
  • the UE shall measure SS-RSRP and SS-RSRQ at least every Tmeasure,NR_intra (see table 1) for intra-frequency cells that are identified given associated SSB timing index known by UE and measured according to the measurement rules.
  • the UE shall filter SS-RSRP and SS-RSRQ measurements of each measured intra- frequency cell using at least 2 measurements. Within the set of measurements used for the filtering, at least two measurements shall be spaced by at least T m easure,NR_intra/2.
  • the UE shall measure SS-RSRP and SS-RSRQ at least every Kcamer * Tmeasure,NR_inter (see table 2) for inter-frequency cells that are identified given an associated SSB timing index known by the UE and measured according to the measurement rules.
  • Figure 4 illustrates an operation flow/algorithmic structure 400 in accordance with some embodiments.
  • the operation flow/algorithmic structure 400 may be performed, in part or in whole, by the UE 104 or components thereof.
  • the operation flow/algorithmic structure 400 may be performed by the baseband circuitry implemented in the UE 104.
  • the operation flow/algorithmic structure 400 may include, at 404, determining a SSB index for a cell to be measured when the UE is in a RRC idle state.
  • the cell may be, for example, an intra-frequency cell or an inter-frequency cell.
  • the UE may determine respective SSB indexes for multiple cells that are to be measured by the UE.
  • the operation flow/algorithmic structure 400 may further include, at 408, performing or causing to perform RRM measurements on a first SSB of the cell based on the SSB index, wherein a gNB associated with the cell transmits a plurality of SSBs with different SSB indexes within a SMTC window.
  • the plurality of SSBs may be transmitted with different transmit beams.
  • the UE may perform multiple RRM measurements on different cells and/or monitor a paging occasion in the serving cell and perform one or more RRM measurements on another cell in a same SMTC window.
  • Radio Resource Control is a protocol for the radio interface between a UE e.g.,
  • the RRC involves transporting radio related information in transparent containers between a source gNB and target gNB upon inter gNB handover; transporting radio related information transported in transparent containers between a source or target gNB and another system upon inter RAT handover; and transporting radio related information in transparent containers between a source eNB and target gNB during E-UTRA-NR Dual Connectivity.
  • RRC also involves communicating radio related parameters from a gNB to a UE, and communicating various UE capabilities from a UE to a gNB.
  • RRC also involves various aspects as discussed herein.
  • a UE (is either in RRC CONNECTED state or in RRC INACTIVE state when an RRC connection has been established. If this is not the case, such as when no RRC connection is established, the UE is in RRC IDLE state.
  • the UE monitors a Paging channel for core network (CN) paging using 5G-S-TMSI, performs neighbouring cell measurements and cell (re-)selection, and acquires system information and can send SI request (if configured).
  • CN core network
  • 5G-S-TMSI 5G-S-TMSI
  • neighbouring cell measurements and cell (re-)selection if configured.
  • SI request if configured.
  • a UE specific DRX may be configured by upper layers, and UE controlled mobility is based on network configuration.
  • the UE monitors a Paging channel for CN paging using 5G-S-TMSI and RAN paging using I-RNTI; performs neighbouring cell measurements and cell (re-)selection; performs RAN-based notification area updates periodically and when moving outside the configured RAN-based notification area; acquires system information and can send SI request (if configured).
  • a UE specific DRX may be configured by upper layers or by the RRC layer, and UE controlled mobility is based on network configuration.
  • the UE stores an AS context, and a RAN-based notification area is configured by RRC layer.
  • the UE monitors a Paging channel, if configured; monitors control channels associated with the shared data channel to determine if data is scheduled for it; provides channel quality and feedback information; performs neighbouring cell measurements and measurement reporting; and acquires system information. Additionally, the UE stores the AS context; unicast data is transferred to/from UE, and at lower layers, the UE may be configured with a UE specific DRX. For UEs supporting CA, use of one or more SCells, aggregated with the SpCell, for increased bandwidth. For UEs supporting DC, use of one SCG, aggregated with the MCG, for increased bandwidth. Furthermore, network controlled mobility within NR and is to/from E-UTRA.
  • RRC includes an RRC connection control function that is used for connection mobility including, e.g., intra-frequency and inter-frequency handover, associated security handling (e.g., key/algorithm change), and specification of RRC context information transferred between network nodes.
  • the RRC connection control function may control or instruct a network node and/or UE to perform an RRC reconfiguration procedure.
  • reconfiguration procedure is to modify an RRC connection to establish/modify/release RBs, to perform reconfiguration with synchronization (sync), to setup/modify/release measurements, to add/modify/release SCells and cell groups.
  • NAS dedicated information may be transferred from the Network to the UE.
  • RRC connection establishment involves the establishment of SRB1.
  • the network completes RRC connection establishment prior to completing the establishment of the NG connection, for example, prior to receiving the UE context information from the 5G core (5GC). Consequently, AS security is not activated during the initial phase of the RRC connection.
  • the network may configure the UE to perform measurement reporting, but the UE only sends the corresponding measurement reports after successful security activation. However, the UE only accepts a re-configuration with sync message when security has been activated.
  • the RAN Upon receiving the UE context from the 5GC, the RAN activates AS security (both ciphering and integrity protection) using the initial security activation procedure.
  • the RRC messages to activate security (command and successful response) are integrity protected, while ciphering is started only after completion of the procedure. That is, the response to the message used to activate security is not ciphered, while the subsequent messages (e.g. used to establish SRB2 and DRBs) are both integrity protected and ciphered.
  • the network After having initiated the initial security activation procedure, the network initiates the establishment of SRB2 and DRBs, i.e. the network may do this prior to receiving the confirmation of the initial security activation from the UE. In any case, the network will apply both ciphering and integrity protection for the RRC reconfiguration messages used to establish SRB2 and DRBs. The network should release the RRC connection if the initial security activation and/ or the radio bearer establishment fails.
  • the release of the RRC connection normally is initiated by the network.
  • the procedure may be used to re-direct the UE to an NR frequency or an EUTRA carrier frequency.
  • the suspension of the RRC connection is initiated by the network.
  • the UE stores the UE AS context and any configuration received from the network, and transits to RRC INACTIVE state.
  • the RRC message to suspend the RRC connection is integrity protected and ciphered.
  • the resumption of a suspended RRC connection is initiated by upper layers when the UE needs to transit from RRC INACTIVE state to RRC CONNECTED state or by RRC layer to perform a RNA update or by RAN paging from NG-RAN.
  • network configures the UE according to the RRC connection resume procedure based on the stored UE AS context and any RRC configuration received from the network.
  • the RRC connection resume procedure re-activates security and re-establishes SRB(s) and DRB(s).
  • the network may resume the suspended RRC connection and send UE to RRC CONNECTED, or reject the request to resume and send UE to RRC INACTIVE (with a wait timer), or directly re-suspend the RRC connection and send UE to RRC INACTIVE, or directly release the RRC connection and send UE to RRC IDLE, or instruct the UE to discard the stored context and initiate NAS level recovery (in this case the network sends an RRC setup message).
  • the RRC reconfiguration procedure is used to modify an RRC connection, e.g. to establish/modify/release RBs, to perform reconfiguration with sync, to setup/modify/release measurements, to add/modify/release SCells and cell groups.
  • NAS dedicated information may be transferred from the Network to the UE.
  • SRB3 can be used for measurement configuration and reporting, to (re-)configure MAC, RLC, physical layer and RLF timers and constants of the SCG configuration, and to reconfigure PDCP for DRBs associated with the S-K gNB or SRB3, provided that the (re-)configuration does not require any MeNB involvement.
  • the Network may initiate the RRC reconfiguration procedure to a UE in
  • RRC_CONNECTED mode The Network applies the procedure as follows: the establishment of RBs (other than SRB1, that is established during RRC connection establishment) is performed only when AS security has been activated; the addition of Secondary Cell Group and SCells is performed only when AS security has been activated; and the reconflgurationWithSync is included in secondaryCellGroup only when at least one DRB is setup in SCG.
  • the UE may initiate an RRC connection re-establishment procedure to re-establish the RRC connection.
  • the UE may initiate the procedure in order to continue the RRC connection.
  • the connection re-establishment succeeds if the network is able to find and verify a valid UE context or, if the UE context cannot be retrieved, and the network responds with an RRCSetup according to section 5.3.3.4. If AS security has not been activated, the UE does not initiate the procedure but instead moves to RRC IDLE directly
  • MR-DC involves a Rx/Tx UE configured to utilize radio resources provided by two distinct schedulers in two different nodes connected via non-ideal backhaul, one providing E- UTRA access and the other one providing NR access.
  • One scheduler is located in a MN and the other in the SN.
  • the MN and SN are connected via a network interface and at least the MN is connected to the core network.
  • MR-DC includes EN-DC or NGEN-DC.
  • EN-DC a UE may be connected to one eNB that acts as an MN and one en-gNB that acts as an SN.
  • the eNB is connected to an EPC and the en-gNB is connected to the eNB via the X2 interface.
  • the en-gNB is a node that provides new radio (NR) user plane and control plane protocol terminations towards the UE, and acts as the SN in EN-DC.
  • NR-EN a UE may be connected to one gNB that acts as the MN and one ng- eNB that acts as a SN.
  • the gNB is connected to 5GC and the ng-eNB (Master Node eNB) is connected to the gNB via the Xn interface.
  • RRC includes a measurement configuration and reporting function that is used for establishment/modification/release of measurements (e.g. intra-frequency, inter-frequency, and inter- RAT measurements).
  • the network may configure an RRC CONNECTED UE to perform measurements and report them in accordance with the measurement configuration.
  • the measurement configuration is provided by means of dedicated signalling i.e. using the
  • the network may configure the UE to perform NR measurements, and/or Inter-radio access technology (RAT) measurements of E-UTRA frequencies.
  • the network may configure the UE to report measurement information based on SS/PBCH block(s), including measurement results per SS/PBCH block; measurement results per cell based on SS/PBCH block(s); and/or SS/PBCH block(s) indexes.
  • the network may configure the UE to report measurement information based on CSI-RS resources, including measurement results per C SI RS resource; measurement results per cell based on CSI-RS resource(s); and/or CSI-RS resource measurement identifiers.
  • the measurement configuration includes the following parameters: measurement objects, reporting configurations, measurement identities, quantity configurations, and measurement gaps.
  • the reporting configurations include lists of reporting configurations where there can be one or multiple reporting configurations per measurement object.
  • Each reporting configuration includes a reporting criterion, reference signal (RS) type, and reporting format.
  • RS reference signal
  • the measurement identities include list of measurement identities where each measurement identity links one measurement object with one reporting configuration. By configuring multiple measurement identities, it is possible to link more than one measurement object to the same reporting configuration, as well as to link more than one reporting configuration to the same measurement object.
  • the measurement identity is also included in the measurement report that triggered the reporting, serving as a reference to the network.
  • the quantity configuration defines the measurement filtering configuration used for all event evaluation and related reporting of that measurement type.
  • the network may configure up to 2 quantity configurations with a reference in the NR measurement object to the configuration that is to be used.
  • different filter coefficients can be configured for different measurement quantities, for different RS types, and for measurements per cell and per beam.
  • Measurement gaps are periods that the UE may use to perform measurements, i.e. no (UL, DL) transmissions are scheduled.
  • a measurement object is a list of objects on which the UE is to perform the
  • a measurement object For intra-frequency and inter-frequency measurements, a measurement object indicates the frequency/time location and subcarrier spacing of reference signals to be measured. Associated with this measurement object, the network may configure a list of cell specific offsets, a list of 'blacklisted' cells and a list of 'whitelisted' cells. Blacklisted cells are not applicable in event evaluation or measurement reporting. Whitelisted cells are the only ones applicable in event evaluation or measurement reporting. The UE determines which MO corresponds to each serving cell frequency from the frequencylnfoDL in
  • the UE When the UE is in the RRC CONNECTED state, the UE maintains a measurement object list, a reporting configuration list, and a measurement identities list according to signalling and procedures in this specification.
  • the measurement object list possibly includes NR intra-frequency object(s), NR inter-frequency object(s) and inter-RAT objects.
  • the reporting configuration list includes NR and inter-RAT reporting configurations. Any measurement object can be linked to any reporting configuration of the same RAT type. Some reporting configurations may not be linked to a measurement object. Likewise, some measurement objects may not be linked to a reporting configuration.
  • the cell reselection procedure allows the UE to select a more suitable cell and to camp on that cell.
  • the UE is to attempt to detect, synchronise, and monitor intra-frequency, inter-frequency and inter-RAT cells indicated by the serving cell.
  • the serving cell may not provide explicit neighbour list but carrier frequency information and bandwidth information only.
  • UE measurement activity is also controlled by measurement rules defined in 3GPP TS 36.304, allowing the UE to limit its measurement activity.
  • the UE is to be capable of monitoring at least: Intra-frequency carrier, and depending on UE capability, 7 NR inter- frequency carriers, depending on UE capability, 7 FDD E-UTRA inter-RAT carriers, and depending on UE capability, 7 TDD E-UTRA inter-RAT carriers.
  • a UE supporting E-UTRA measurements in RRC IDLE state is to be capable of monitoring a total of at least 14 carrier frequency layers, which includes serving layer, comprising of any above defined combination of E-UTRA FDD, E-UTRA TDD and NR layers.
  • the UE filters the SS-RSRP and SS-RSRQ measurements of the serving cell using at least two measurements. Within the set of measurements used for the filtering, at least two measurements is to be spaced by, at least DRX cycle/2. If the UE has evaluated a number of DRX cycles N se rv consecutive DRX cycles that the serving cell does not fulfill the cell selection criterion S, the UE initiates the measurements of all neighbour cells indicated by the serving cell, regardless of the measurement rules currently limiting UE measurement activities. If the UE in RRC IDLE has not found any new suitable cell based on searches and measurements using the intra-frequency, inter-frequency and inter-RAT information indicated in the system information for 10 s, the UE initiates cell selection procedures for the selected PLMN.
  • the network provides a single per-UE measurement gap pattern for concurrent monitoring of all frequency layers.
  • the UE does not transmit any data; is not required to receive data from the corresponding E-UTRAN PCell, E-UTRAN SCell(s) and NR serving cells for NS A; and is not required to receive data from the corresponding NR serving cells for SA.
  • the network provides either per-FR measurement gap patterns or a single per-UE measurement gap pattern.
  • the per-FR The per-FR
  • measurement gap patterns are for a frequency range where the UE requires per-FR measurement gap for concurrent monitoring of all frequency layers of each frequency range independently.
  • the single per-UE measurement gap pattern is for concurrent monitoring of all frequency layers of all frequency ranges.
  • the UE does not transmit any data on serving cells in the corresponding frequency range; is not required to receive data from the corresponding E- UTRAN PCell, E-UTRAN SCell(s) and NR serving cells for NSA; and is not required to receive data from the corresponding NR serving cells for SA.
  • Example measurement gap patterns that may be supported by the UE are listed in Table 9.1.2-1 based on the applicability specified in table 9.1.2-2 and 9.1.2-3.
  • UE determines measurement gap timing based on gap offset configuration and measurement gap timing advance configuration provided by higher layer signalling.
  • Measurement objects are in both E- UTRA /FR1 and FR2, if the MN indicates UE that the measurement gap from MN applies to E- UTRA/FR1/FR2 serving cells, UE fulfils the per-UE measurement requirements for both E- UTRA/FR1 and FR2 measurement objects based on the measurement gap pattern configured by MN.
  • the effective MGRP in this FR used to determine requirements is 20ms for FR2 NR measurements; 40ms for FR1 NR measurements; 40ms for LTE measurements; and 40ms for FR1+LTE measurements
  • the scheduling opportunity in the FR depends on the configured measurement gap pattern.
  • the UE For intra-frequency NR cells, the UE identifies new intra-frequency cells and performs SS-RSRP and SS-RSRQ measurements of the identified intra-frequency cells without an explicit intra-frequency neighbour list containing physical layer cell identities. In various embodiments, the UE identifies new intra-frequency cells and performs SS-RSRP and SS-RSRQ
  • An intra frequency cell is considered to be detectable according to a predefined or configured SS-RSRP, SS-RSRP Es/Iot for a corresponding band.
  • the UE measures SS-RSRP and SS-RSRQ at least every T measure, NR_Intra for intra-frequency cells that are identified and measured according to the measurement rules.
  • the UE measures SS-RSRP and SS-RSRQ at least every Tmeasure.
  • NR intra see e.g., table 1 supra) for intra-frequency cells that are identified given an associated SSB timing index known by the UE and measured according to the measurement rules.
  • the UE filters SS-RSRP and SS-RSRQ measurements of each measured intra-frequency cell using at least 2 measurements. Within the set of measurements used for the filtering, at least two measurements is to be spaced by at least Tmeasure.NR intra/2. If the Treseiection timer has a non- zero value and the intra-frequency cell is better ranked than the serving cell, the UE evaluates the intra-frequency cell for the Treseiection time, and if this cell remains better ranked within this duration, then the UE reselects to that cell.
  • a measurement is defined to be an S SB intra-frequency measurement provided the center frequency of the SSB of the serving cell indicated for measurement and the center frequency of the SSB of the neighbour cell are the same, and the subcarrier spacing of the two SSB are also the same.
  • the UE can perform intra-frequency SSB based measurements without measurement gaps under the following conditions: the SSB is completely contained in the downlink operating bandwidth of the UE; the SSB has the same subcarrier spacing as the downlink data transmission to the UE; the UE is measuring on FR1 ; and the serving cell data transmissions to the UE have the same subcarrier spacing as the SSB to be measured.
  • SSB based measurements are configured along with one or two measurement timing configuration(s) (SMTC) which provides periodicity, duration and offset information on a window of up to 5ms where the measurements are to be performed.
  • SMTC measurement timing configuration
  • up to two measurement window periodicities may be configured.
  • a single measurement window offset and measurement duration are configured per intra-frequency measurement object.
  • the UE When measurement gaps are needed, the UE is not expected to detect SSBs that start earlier than the gap starting time + switching time, nor detect SSB which end later than the gap end - switching time.
  • the switching time is 0.5ms for FR1 and 0.25ms for FR2.
  • the number of cell and number of SSB requirements for FR1 are as follows: For each intra-frequency layer, the UE is capable of monitoring at least 8 cells. For each intra-frequency layer, during each layer 1 measurement period, the UE is to be capable of monitoring at least 14 SSBs with different SSB index and/or PCI on the intra-frequency layer, where the number of SSBs in the serving cell (except for the SCell) is no smaller than the number of configured RLM-RS SSB resources.
  • the Reference Signal for RLM (RLM-RS) resource is a resource out of the set of resources configured for RLM by higher layer parameter RLM-RS-List.
  • the number of cell and number of SSB requirements for FR2 are as follows: For each intra-frequency layer the UE is to be capable of monitoring at least 6 cells on a single serving carrier (PCC or PSCC or 1 SCC if PCC/PSCC is in a band different from SCC) out of all the serving carriers configured in the same band. For each intra-frequency layer, during each layer 1 measurement period, the UE is to be capable of monitoring at least 24 SSB with different SSB index and/or PCI on a single serving carrier (PCC or PSCC or 1 SCC if PCC/PSCC is in a band different from SCC) out of all the serving carriers configured in the same band. UE is to be capable of monitoring 1-4 SSB(s) on serving cell for each of the other serving carrier(s) in the same band. UE is to be capable of performing RSRP and RSRQ on all above-mentioned SSBs.
  • Measurement reporting may be periodic or event-triggered periodic.
  • the periodically triggered measurement report is to include RSRP, RSRQ, and RS-SINR measurements.
  • the UE does not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
  • a measurement reporting delay is defined as the time between an event that will trigger a measurement report and the point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH.
  • the delay uncertainty is: 2 x TTlDCCH.
  • This measurement reporting delay excludes a delay which caused by no UL resoureces for UE to send the measurement report.
  • the event triggered measurement reporting delay, measured without L3 filtering is less than T identify intra with index or T identify intra without index. When L3 filtering is used an additional delay can be expected.
  • the event triggered measurement reporting delay is to be less than TMeasurement_Period, intra provided the timing to that cell has not changed more than ⁇ Xthreshoid * Ts and the L3 filter has not been used.
  • L3 filtering is used, an additional delay can be expected.
  • the UE For intra-frequency measurements with no measurement gaps, the UE is to identify a new detectable intra frequency cell within Tidentify_intra_without_index if UE is not indicated to report SSB based RRM measurement result with the associated SSB index, or the UE has been indicated that the neighbour cell is synchronous with the serving cell. Otherwise UE is to be able to identify a new detectable intra frequency cell within Tidentify_ intra_with_index. The UE is to be able to identify a new detectable intra frequency SS block of an already detected cell within
  • Tidentify_intra_without_index Kca (TpSS/SSS_sync + T SSB_measurement_period) lUS
  • Tidentify_intra_with_index Kca (TpSS/SSS_sync + T SSB_measurement_period + TsSB_time_index) lUS
  • Tpss/sss_sync is the time period used in PSS/SSS detection
  • TssB timejndex is the time period used to acquire the index of the SSB being measured
  • T ssB_measurement_period is equal to a measurement period of SSB based measurement
  • Kca 1 for FR1 for measurements on frequencies corresponding to PCell or PSCell
  • Kca is the number of configured SCells for measurements on frequencies corresponding to FR1 only Scells.
  • the UE With respect to scheduling availability of UE during intrafrequency measurements, the UE is required to be capable of measuring without measurement gaps when the SSB is completely contained in the active bandwidth part of the UE.
  • the measurement signal has different subcarrier spacing than PDSCH/PDCCH and on frequency range FR2, there are restrictions on the scheduling availabilityas described as follows.
  • Another restriction is that, if useServingCellTimingForSync is not enabled the UE is not expected to transmit PUCCH/PUSCH or receive PDCCH/PDSCH on all symbols within SMTC window duration.
  • intra-band carrier aggregation the scheduling restrictions apply to all serving cells on the band.
  • inter-band carrier aggregation within FR1 there are no scheduling restrictions on FR1 serving cell(s) in the bands due to measurements performed on FR1 serving cell frequency layer in different bands
  • the following scheduling restriction applies to SS-RSRQ measurement on an FR2 intra- frequency cell: the UE is not expected to transmit PUCCH/PUSCH or receive PDCCH/PDSCH on SSB symbols to be measured, RSSI measurement symbols, 1 data symbol before each consecutive SSB/RSSI symbols and 1 data symbol after each consecutive SSB/RSSI symbols within SMTC window duration (it is assumed that useServingCellTimingForSync is always enabled for FR2).
  • intra-band carrier aggregation the scheduling restrictions apply to all serving cells on the band.
  • inter-band carrier aggregation within FR2 the scheduling restrictions apply to all serving cells on the bands.
  • the UE For intra-frequency measurements with measurement gaps, the UE is to identify a new detectable intra frequency cell within Tidentify_mtra_withoutjndex if UE is not indicated to report SSB based RRM measurement result with the associated SSB index, or the UE has been indicated that the neighbour cell is synchronous with the serving cell. Otherwise UE is to identify a new detectable intra frequency cell within Tidentify_ intra_with_index. The UE is to identify a new detectable intra frequency SS block of an already detected cell within Tidentify_ intra_without_index.
  • Tidentify_intra_without_index TpSS/SSS_sync + T SSB_measurement_period lUS
  • Tidentify_intra_with_index TpSS/SSS_sync + T SSB_measurement_period + TsSB_time_index
  • Tpss/sss_sync the time period used in PSS/SSS detection
  • TssBjimejndex is the time period used to acquire the index of the SSB being measured
  • T ssB_measurement_period is equal to a measurement period of SSB based measurement.
  • the UE For inter-frequency NR cells, the UE identifies new inter-frequency cells and performs SS-RSRP or SS-RSRQ measurements of identified inter-frequency cells if carrier frequency information is provided by the serving cell, even if no explicit neighbour list with physical layer cell identities is provided.
  • An inter- frequency cell is considered to be detectable according to a predefined or configured SS-RSRP, SS-RSRP Es/Iot for a corresponding band.
  • the UE When higher priority cells are found by the higher priority search, these cells are measured at least every Tmeasure,NR_Inter . If, after detecting a cell in a higher priority search, it is determined that reselection has not occurred then the UE is not required to continuously measure the detected cell to evaluate the ongoing possibility of reselection. However, the minimum measurement filtering requirements specified later in this section is to still be met by the UE before it makes any determination that it may stop measuring the cell. If the UE detects on a NR carrier a cell whose physical identity is indicated as not allowed for that carrier in the measurement control system information of the serving cell, the UE is not required to perform measurements on that cell.
  • the UE measures SS-RSRP or SS-RSRQ at least every Kcamer * Tmcasure.NRjntcr for identified lower or equal priority inter-frequency cells. If the UE detects on a NR carrier a cell whose physical identity is indicated as not allowed for that carrier in the measurement control system information of the serving cell, the UE is not required to perform measurements on that cell. According to various embodiments herein, the UE measures SS-RSRP and SS-RSRQ at least every Kcamer * Tmcasure.NRjntcr (see e.g., table 2 supra) for inter-frequency cells that are identified given an associated SSB timing index known by the UE and measured according to the measurement rules.
  • the UE filters SS-RSRP or SS-RSRQ measurements of each measured higher, lower and equal priority inter-frequency cell using at least 2 measurements.
  • the filtering is to be such that the UE is to be capable of evaluating that the inter- frequency cell has met a reselection criterion within Kcamer * Tevaluate,NR_Inter when Treselection — 0 provided that the reselection criteria is met by a predefined or configured margin.
  • the side conditions for SS-RSRP apply to both serving and inter- frequency cells.
  • the UE evaluates this inter-frequency cell for the Treselection time, and if this cell remains better ranked within this duration, then the UE reselects to that cell.
  • a measurement is defined to be an SSB inter-frequency measurement provided it is not defined as an intra-frequency measurement as discussed previously.
  • the UE is to identify new inter-frequency cells and perform SS-RSRP, SS-RSRQ, and SS-SINR measurements of identified inter-frequency cells if carrier frequency information is provided by the PCell or the PSCell, even if no explicit neighbor list with physical layer cell identities is provided.
  • SSB measurements are configured along with a measurement timing configuration (SMTC) per carrier, which provides periodicity, duration and offset information on a window of up to 5ms where the measurements on the configured inter-frequency carrier are to be performed.
  • SMTC measurement timing configuration
  • one measurement window periodicity may be configured per inter-frequency measurement object.
  • the UE When measurement gaps are needed, the UE is not expected to detect SSB on an inter- frequency measurement object which start earlier than the gap starting time + switching time, nor detect SSB which end later than the gap end - switching time.
  • the switching time When the inter-frequency cells are in FR2 and the per-FR gap is configured to the UE, the switching time is 0.25ms. Otherwise the switching time is 0.5ms.
  • the UE For each inter-frequency layer, the UE is capable of monitoring at least 4 cells.
  • the number of cell and number of SSB requirements for FR1 are as follows: For each inter-frequency layer, the UE is to be capable of monitoring at least 4 cells. For each inter- frequency layer, during each layer 1 measurement period, the UE is to be capable of monitoring at least 7 SSBs with different SSB index and/or PCI on the inter-frequency layer.
  • the number of cell and number of SSB requirements for FR2 are as follows: For each inter-frequency layer, the UE is to be capable of monitoring at least 4 cells. For each inter- frequency layer, during each layer 1 measurement period, the UE is to be capable of monitoring at least 10 SSBs with different SSB index and/or PCI on the inter-frequency layer. The UE is to be capable of monitoring at least one SSB per cell.
  • the UE When measurement gaps are provided, or the UE supports capability of conducting such measurements without gaps, the UE is to be able to identify a new detectable inter frequency cell within Tidentifyjnter withoutjndex if UE is not indicated to report S SB based RRM measurement result with the associated S SB index. Otherwise UE is to be able to identify a new detectable inter frequency cell within Tidentay _inter_with_index. The UE is to be able to identify a new detectable inter frequency SS block of an already detected cell within TSSB _time_index_inter.
  • Tidentify_inter_without_index (TpSS/SSS_sync_inter + T SSB_measurement_period_inter) lUS
  • Tidentify_inter_with_index (TpSS/SSS_sync_inter + T SSB_measurement_period_inter +
  • Tpss/sss_sync_mter is the time period used in PSS/SSS detection
  • TSSB_ time_index_inter IS the time period used to acquire the index of the SSB being measured
  • ssB_measurement_period_inter is equal to a measurement period of SSB based measurement.
  • the UE physical layer is capable of reporting SS-RSRP, SS-RSRQ and SS-SINR measurements to higher layers with a predetermined or configured measurement accuracy
  • Measurement reporting may be periodic or event-triggered periodic.
  • the periodically triggered measurement report is to include RSRP, RSRQ, and RS-SINR measurements.
  • the UE does not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
  • a measurement reporting delay is defined as the time between an event that will trigger a measurement report and the point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that that the measurement report is not delayed by other RRC signalling on the DCCH.
  • This measurement reporting delay excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay uncertainty is: [2 x TTIDCCH. ]
  • This measurement reporting delay excludes a delay which caused by no UL resources for UE to send the measurement report.
  • the event triggered measurement reporting delay, measured without L3 filtering is to be less than [T identify -inter ] .
  • L3 filtering an additional delay can be expected. If a cell which has been detectable at least for the time period [Tidenttfyjnter ] and then triggers the measurement report, the event triggered measurement reporting delay is less than [TMeasurement_Period_inter_FDD ] provided the timing to that cell has not changed more than [ ⁇ 50 Ts] while measurement gap has not been available and the L3 filter has not been used.
  • an additional delay can be expected.
  • the UE For inter-RAT measurements, such as FDD/TDD NR-EUTRAN measurements, the UE is required to be in the RRC CONNECTED state, configured with at least a Pcell, and configured with an appropriate measurement gap pattern.
  • Example gap patterns are shown by table RR.C-1.
  • a measurement object is a single EUTRA carrier frequency.
  • the network can configure a list of cell specific offsets, a list of 'blacklisted' cells and a list of 'whitelisted' cells. Blacklisted cells are not applicable in event evaluation or measurement reporting. Whitelisted cells are the only ones applicable in event evaluation or measurement reporting.
  • the UE measures RSRP and RSRQ of detected EUTRA cells in the neighbor frequency list at the minimum measurement rate specified in this section.
  • the parameter NEUTRA_camer is the number of carriers in the neighbour frequency list.
  • the UE filters the RSRP and RSRQ measurements of each measured EUTRA cell using at least two measurements. Within the set of measurements used for the filtering, at least two measurements are spaced by at least half the minimum specified measurement period. The UE also evaluates whether a newly detectable inter-RAT E-UTRAN cell meets a reselection criteria
  • TreselectionRAT 0 provided that the reselection criteria is met by a margin of at least 5dB for reselections based on ranking or 6dB for RSRP reselections based on absolute priorities or 4dB for RSRQ reselections based on absolute priorities. If the Treseiection timer has a non-zero value and the inter-RAT EUTRA cell is satisfied with the reselection criteria, the UE evaluates this E- UTRA cell for the Treseiection time. If this cell remains satisfied with the reselection criteria within this duration, then the UE reselects to that cell.
  • An E-UTRAN FDD cell of E-UTRAN TDD cell is considered to be detectable when RSRP related side conditions are fulfilled for a corresponding Band, RSRQ related side conditions are fulfilled for a corresponding Band, RS-SINR related side conditions are fulfilled for a corresponding Band, and/or SCH RP and SCH Es/Iot for a corresponding Band are fulfilled.
  • E-UTRAN FDD cells when the UE requires measurement gaps to idenitify and measurement inter-RAT cells and an appropriate measurement gap pattern is scheduled, the UE is to be able to identify a new detectable FDD cell within Tidentify, E-UTRAN FDD according to the following expression:
  • TBas ckicm iv 480 ms
  • Tinteri is defined in table 9.4.1-1
  • K depends at least on Nfreq, SA and whether and how gaps are shared.
  • Identification of a cell is to include detection of the cell and additionally performing a single measurement with measurement period of TMeasure, E-UTRAN
  • the UE is also capable of identifying and performing NR-E-UTRAN FDD RSRP, RSRQ, and RS-SINR measurements of at least 4 E-UTRAN FDD cells per E-UTRA FDD carrier frequency layer for up to 7 E-UTRA FDD carrier frequency layers. If higher layer filtering is used, an additional cell identification delay can be expected.
  • the UE When DRX is in use and measurement gaps are configured, the UE is to be able to identify a new detectable E-UTRAN FDD cell within Tidentify, E-UTRAN FDD.
  • the UE When DRX is in use, the UE is to be capable of performing NR - E-UTRAN FDD RSRP and RSRQ measurements of at least 4 E-UTRAN FDD cells per E-UTRA FDD frequency layer for up to 7 E-UTRA FDD carrier frequency layers, and the UE physical layer is to be capable of reporting NR - E-UTRAN FDD RSRP and RSRQ measurements to higher layers with the measurement period Tm easure, E- UTRAN FDD. If higher layer filtering is used, an additional cell identification delay can be expected.
  • Measurement reporting may be periodic, event-triggered periodic, or event-triggered.
  • the periodically triggered measurement report is to include RSRP, RSRQ, and RS-SINR measurements.
  • the UE does not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
  • the measurement reporting delay is defined as the time between an event that will trigger a measurement report and the point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that that the measurement report is not delayed by other RRC signalling on the DCCH.
  • This measurement reporting delay excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH.
  • the delay uncertainty is: 2 x TTIDCCH where TTIDCCH is the duration of subframe or slot or subslot when the measurement report is transmitted on the PUSCH with subframe or slot or subslot duration.
  • This measurement reporting delay excludes a delay which caused by no UL resources for UE to send the measurement report.
  • the event triggered measurement reporting delay, measured without L3 filtering is to be less than T identify, E-UTRAN FDD without DRX and with DRX, respectively. When L3 filtering is used, an additional delay can be expected. If a cell which has been detectable at least for the time period Tidcmify.
  • E-UTRAN FDD for FDD cells
  • E-UTRAN TDD for TDD cells
  • the event triggered measurement reporting delay is to be less than TMeasure, E-UTRAN FDD or TMeasure
  • E-UTRAN TDD provided the timing to that cell has not changed more than ⁇ 50 Ts while measurement gap has not been available and the L3 filter has not been used.
  • E-UTRAN TDD cells the UE requires measurement gaps to identify and measurement inter-RAT cells and an appropriate measurement gap pattern is scheduled, the UE is to identify a new detectable FDD cell within Tidentify, E-UTRAN TDD according to the following expression: Configuration 0 OG configuration 1 is applied; or
  • TBasicidentify 480 ms
  • Tinteri is defined in table 9.4.1-1
  • K depends at least on Nfreq, SA and whether and how gaps are shared. Identification of a cell is to include detection of the cell and additionally performing a single measurement with
  • the UE is also capable of identifying and performing NR-E-UTRAN TDD RSRP, RSRQ, and RS-SINR measurements of at least 4 E-UTRAN TDD cells per E-UTRA TDD carrier frequency layer for up to 7 E-UTRA TDD carrier frequency layers. If higher layer filtering is used, an additional cell identification delay can be expected.
  • the UE is to be able to identify a new detectable E-UTRAN TDD cell within Tidenttfy, E-UTRAN TDD.
  • the UE When DRX is in use, the UE is to be capable of performing NR - E-UTRAN TDD RSRP and RSRQ measurements of at least 4 E-UTRAN TDD cells per E-UTRA TDD frequency layer for up to 7 E-UTRA TDD carrier frequency layers, and the UE physical layer is to be capable of reporting NR - E-UTRAN TDD RSRP and RSRQ measurements to higher layers with the measurement period T measure E- UTRAN TDD. If higher layer filtering is used, an additional cell identification delay can be expected.
  • FIG. 5 illustrates an example of infrastructure equipment 500 in accordance with various embodiments.
  • the infrastructure equipment 500 (or“system 500”) may be implemented as a base station, radio head, RAN node, application server(s), and/or any other element/device discussed herein.
  • the system 500 could be implemented in or by a UE.
  • the system 500 includes application circuitry 505, baseband circuitry 510, one or more radio front end modules (RFEMs) 515, memory circuitry 520, power management integrated circuitry (PMIC) 525, power tee circuitry 530, network controller circuitry 535, network interface connector 540, satellite positioning circuitry 545, and user interface 550.
  • RFEMs radio front end modules
  • PMIC power management integrated circuitry
  • PMIC power management integrated circuitry
  • the device 500 may include additional elements such as, for example,
  • memory /storage memory /storage, display, camera, sensor, or input/output (I/O) interface.
  • I/O input/output
  • the components described below may be included in more than one device.
  • said circuitries may be separately included in more than one device for CRAN, vBBU, or other like implementations.
  • Application circuitry 505 includes circuitry such as, but not limited to one or more processors (or processor cores), cache memory, and one or more of low drop-out voltage regulators (LDOs), interrupt controllers, serial interfaces such as SPI, I 2 C or universal programmable serial interface module, real time clock (RTC), timer-counters including interval and watchdog timers, general purpose input/output (I/O or IO), memory card controllers such as Secure Digital (SD) MultiMediaCard (MMC) or similar, Universal Serial Bus (USB) interfaces, Mobile Industry Processor Interface (MIPI) interfaces and Joint Test Access Group (JTAG) test access ports.
  • LDOs low drop-out voltage regulators
  • interrupt controllers serial interfaces such as SPI, I 2 C or universal programmable serial interface module, real time clock (RTC), timer-counters including interval and watchdog timers, general purpose input/output (I/O or IO), memory card controllers such as Secure Digital (SD) MultiMediaCard (MMC) or
  • the processors (or cores) of the application circuitry 505 may be coupled with or may include memory /storage elements and may be configured to execute instructions stored in the memory /storage to enable various applications or operating systems to run on the system 500.
  • the memory /storage elements may be on-chip memory circuitry, which may include any suitable volatile and/or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, Flash memory, solid-state memory, and/or any other type of memory device technology, such as those discussed herein.
  • the processor(s) of application circuitry 505 may include, for example, one or more processor cores (CPUs), one or more application processors, one or more graphics processing units (GPUs), one or more reduced instruction set computing (RISC) processors, one or more Acom RISC Machine (ARM) processors, one or more complex instruction set computing (CISC) processors, one or more digital signal processors (DSP), one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, or any suitable combination thereof.
  • the application circuitry 505 may comprise, or may be, a special-purpose processor/controller to operate according to the various embodiments herein.
  • the processor(s) of application circuitry 505 may include one or more Intel Pentium®, Core®, or Xeon® processor(s); Advanced Micro Devices (AMD) Ryzen® processor(s), Accelerated Processing Units (APUs), or Epyc® processors; ARM-based processor(s) licensed from ARM Holdings, Ltd. such as the ARM Cortex-A family of processors and the ThunderX2® provided by Cavium(TM), Inc.; a MIPS-based design from MIPS
  • the system 500 may not utilize application circuitry 505, and instead may include a special-purpose processor/controller to process IP data received from an EPC or 5GC, for example.
  • the application circuitry 505 may include one or more hardware accelerators, which may be microprocessors, programmable processing devices, or the like.
  • the one or more hardware accelerators may include, for example, computer vision (CV) and/or deep learning (DL) accelerators.
  • the programmable processing devices may be one or more a field-programmable devices (FPDs) such as field-programmable gate arrays (FPGAs) and the like; programmable logic devices (PLDs) such as complex PLDs (CPLDs), high-capacity PLDs (HCPLDs), and the like; ASICs such as structured ASICs and the like; programmable SoCs (PSoCs); and the like.
  • FPDs field-programmable devices
  • PLDs programmable logic devices
  • CPLDs complex PLDs
  • HPLDs high-capacity PLDs
  • ASICs such as structured ASICs and the like
  • PSoCs programmable SoCs
  • the circuitry of application circuitry 505 may comprise logic blocks or logic fabric, and other interconnected resources that may be programmed to perform various functions, such as the procedures, methods, functions, etc. of the various embodiments discussed herein.
  • the circuitry of application circuitry 505 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-fuses, etc.)) used to store logic blocks, logic fabric, data, etc. in look-up-tables (LUTs) and the like.
  • 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-fuses, etc.)
  • SRAM static random access memory
  • LUTs look-up-tables
  • the baseband circuitry 510 may be implemented, for example, as a solder-down substrate including one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board or a multi-chip module containing two or more integrated circuits.
  • the various hardware electronic elements of baseband circuitry 510 are discussed infra with regard to Figure XT.
  • User interface circuitry 550 may include one or more user interfaces designed to enable user interaction with the system 500 or peripheral component interfaces designed to enable peripheral component interaction with the system 500.
  • User interfaces may include, but are 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 touchpad, a touchscreen, speakers or other audio emitting devices, microphones, a printer, a scanner, a headset, a display screen or display device, etc.
  • Peripheral component interfaces may include, but are not limited to, a nonvolatile memory port, a universal serial bus (USB) port, an audio jack, a power supply interface, etc.
  • USB universal serial bus
  • the radio front end modules (RFEMs) 515 may comprise a millimeter wave (mmWave) RFEM and one or more sub-mmWave radio frequency integrated circuits (RFICs).
  • the one or more sub-mmWave RFICs may be physically separated from the mmWave RFEM.
  • the RFICs may include connections to one or more antennas or antenna arrays (see e.g., antenna array 711 of Figure 7 infra), and the RFEM may be connected to multiple antennas.
  • both mmWave and sub-mmWave radio functions may be implemented in the same physical RFEM 515, which incorporates both mmWave antennas and sub-mmWave.
  • the memory circuitry 520 may include one or more of volatile memory including dynamic random access memory (DRAM) and/or synchronous dynamic random access memory (SDRAM), and nonvolatile memory (NVM) including high-speed electrically erasable memory (commonly referred to as Flash memory), phase change random access memory (PRAM), magnetoresistive random access memory (MRAM), etc., and may incorporate the three- dimensional (3D) cross-point (XPOINT) memories from Intel® and Micron®.
  • Memory circuitry 520 may be implemented as one or more of solder down packaged integrated circuits, socketed memory modules and plug-in memory cards.
  • the PMIC 525 may include voltage regulators, surge protectors, power alarm detection circuitry, and one or more backup power sources such as a battery or capacitor.
  • the power alarm detection circuitry may detect one or more of brown out (under-voltage) and surge (over voltage) conditions.
  • the power tee circuitry 530 may provide for electrical power drawn from a network cable to provide both power supply and data connectivity to the infrastructure equipment 500 using a single cable.
  • the network controller circuitry 535 may provide connectivity to a network using a standard network interface protocol such as Ethernet, Ethernet over GRE Tunnels, Ethernet over Multiprotocol Label Switching (MPLS), or some other suitable protocol.
  • Network connectivity may be provided to/from the infrastructure equipment 500 via network interface connector 540 using a physical connection, which may be electrical (commonly referred to as a“copper interconnect”), optical, or wireless.
  • the network controller circuitry 535 may include one or more dedicated processors and/or FPGAs to communicate using one or more of the
  • the network controller circuitry 535 may include multiple controllers to provide connectivity to other networks using the same or different protocols.
  • the positioning circuitry 545 includes circuitry to receive and decode signals transmitted/broadcasted by a positioning network of a global navigation satellite system
  • GNSS navigation satellite constellations
  • the positioning circuitry 545 comprises various hardware elements (e.g., including hardware devices such as switches, filters, amplifiers, antenna elements, and the like to facilitate OTA communications) to communicate with components of a positioning network, such as navigation satellite
  • the positioning circuitry 545 may include a Micro- Technology for Positioning, Navigation, and Timing (Micro-PNT) IC that uses a master timing clock to perform position tracking/estimation without GNSS assistance.
  • the positioning circuitry 545 may also be part of, or interact with, the baseband circuitry 510 and/or RFEMs 515 to communicate with the nodes and components of the positioning network.
  • the positioning circuitry 545 may also provide position data and/or time data to the application circuitry 505, which may use the data to synchronize operations with various infrastructure (e.g., RAN nodes, etc.), or the like.
  • interface circuitry may include any number of bus and/or interconnect (IX) technologies such as industry standard architecture (ISA), extended ISA (EISA), peripheral component interconnect (PCI), peripheral component interconnect extended (PCIx), PCI express (PCIe), or any number of other technologies.
  • IX interconnect
  • the bus/IX may be a proprietary bus, for example, used in a SoC based system.
  • Other bus/IX systems may be included, such as an I 2 C interface, an SPI interface, point to point interfaces, and a power bus, among others.
  • Figure 6 illustrates an example of a platform 600 (or“device 600”) in accordance with various embodiments.
  • the computer platform 600 may be suitable for use as a UE, application server, and/or any other element/device discussed herein.
  • the platform 600 may include any combinations of the components shown in the example.
  • the components of platform 600 may be implemented as integrated circuits (ICs), portions thereof, discrete electronic devices, or other modules, logic, hardware, software, firmware, or a combination thereof adapted in the computer platform 600, or as components otherwise incorporated within a chassis of a larger system.
  • the block diagram of Figure 6 is intended to show a high level view of components of the computer platform 600. However, some of the components shown may be omitted, additional components may be present, and different arrangement of the components shown may occur in other implementations.
  • Application circuitry 605 includes circuitry such as, but not limited to one or more processors (or processor cores), cache memory, and one or more of LDOs, interrupt controllers, serial interfaces such as SPI, I 2 C or universal programmable serial interface module, RTC, timer-counters including interval and watchdog timers, general purpose I/O, memory card controllers such as SD MMC or similar, USB interfaces, MIPI interfaces, and JTAG test access ports.
  • the processors (or cores) of the application circuitry 605 may be coupled with or may include memory /storage elements and may be configured to execute instructions stored in the memory /storage to enable various applications or operating systems to run on the system 600.
  • the memory /storage elements may be on-chip memory circuitry, which may include any suitable volatile and/or non-volatile memory, such as DRAM, SRAM,
  • EPROM EPROM
  • EEPROM Electrically erasable programmable read-only memory
  • Flash memory solid-state memory, and/or any other type of memory device technology, such as those discussed herein.
  • the processor(s) of application circuitry 505 may include, for example, one or more processor cores, one or more application processors, one or more GPUs, one or more RISC processors, one or more ARM processors, one or more CISC processors, one or more DSP, one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, a multithreaded processor, an ultra-low voltage processor, an embedded processor, some other known processing element, or any suitable combination thereof.
  • processor cores for example, one or more processor cores, one or more application processors, one or more GPUs, one or more RISC processors, one or more ARM processors, one or more CISC processors, one or more DSP, one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, a multithreaded processor, an ultra-low voltage processor, an embedded processor, some other known processing element, or any suitable combination thereof
  • the application circuitry 505 may comprise, or may be, a special-purpose processor/controller to operate according to the various embodiments herein.
  • processor(s) of application circuitry 605 may include an Intel®
  • the processors of the application circuitry 605 may also be one or more of Advanced Micro Devices (AMD) Ryzen® processor(s) or Accelerated Processing Units (APUs); A5-A9 processor(s) from Apple® Inc., QualcommTM processor(s) from Qualcomm® Technologies, Inc., Texas Instruments, Inc.® Open Multimedia Applications Platform (OMAP)TM processor(s); a MIPS-based design from MIPS Technologies, Inc. such as MIPS Warrior M-class, Warrior I- class, and Warrior P-class processors; an ARM-based design licensed from ARM Holdings,
  • AMD Advanced Micro Devices
  • APUs Accelerated Processing Units
  • A5-A9 processor(s) from Apple® Inc.
  • SnapdragonTM processor(s) from Qualcomm® Technologies, Inc. Texas Instruments, Inc.
  • OMAP Open Multimedia Applications Platform
  • MIPS-based design from MIPS Technologies, Inc. such as MIPS Warrior M-class, Warrior I- class, and Warrior P-
  • the application circuitry 605 may be a part of a system on a chip (SoC) in which the application circuitry 605 and other components are formed into a single integrated circuit, or a single package, such as the EdisonTM or GalileoTM SoC boards from Intel®
  • SoC system on a chip
  • application circuitry 605 may include circuitry such as, but not limited to, one or more a field-programmable devices (FPDs) such as FPGAs and the like; programmable logic devices (PLDs) such as complex PLDs (CPLDs), high-capacity PLDs (HCPLDs), and the like; ASICs such as structured ASICs and the like; programmable SoCs (PSoCs); and the like.
  • FPDs field-programmable devices
  • PLDs programmable logic devices
  • CPLDs complex PLDs
  • HPLDs high-capacity PLDs
  • PSoCs programmable SoCs
  • the circuitry of application circuitry 605 may comprise logic blocks or logic fabric, and other interconnected resources that may be programmed to perform various functions, such as the procedures, methods, functions, etc. of the various embodiments discussed herein.
  • the circuitry of application circuitry 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-fuses, etc.)) used to store logic blocks, logic fabric, data, etc. in look-up tables (LUTs) and the like.
  • 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-fuses, etc.)
  • SRAM static random access memory
  • LUTs look-up tables
  • the baseband circuitry 610 may be implemented, for example, as a solder-down substrate including one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board or a multi-chip module containing two or more integrated circuits.
  • the various hardware electronic elements of baseband circuitry 610 are discussed infra with regard to Figure 7.
  • the RFEMs 615 may comprise a millimeter wave (mmWave) RFEM and one or more sub-mmWave radio frequency integrated circuits (RFICs).
  • the one or more sub-mmWave RFICs may be physically separated from the mmWave RFEM.
  • the RFICs may include connections to one or more antennas or antenna arrays (see e.g., antenna array 711 of Figure 7 infra), and the RFEM may be connected to multiple antennas.
  • both mmWave and sub-mmWave radio functions may be implemented in the same physical RFEM 615, which incorporates both mmWave antennas and sub-mmWave.
  • the memory circuitry 620 may include any number and type of memory devices used to provide for a given amount of system memory.
  • the memory circuitry 620 may include one or more of volatile memory including random access memory (RAM), dynamic RAM (DRAM) and/or synchronous dynamic RAM (SDRAM), and nonvolatile memory (NVM) including high-speed electrically erasable memory (commonly referred to as Flash memory), phase change random access memory (PRAM), magnetoresistive random access memory (MRAM), etc.
  • RAM random access memory
  • DRAM dynamic RAM
  • SDRAM synchronous dynamic RAM
  • NVM nonvolatile memory
  • Flash memory high-speed electrically erasable memory
  • PRAM phase change random access memory
  • MRAM magnetoresistive random access memory
  • the memory circuitry 620 may be developed in accordance with a Joint Electron Devices Engineering Council (JEDEC) low power double data rate (LPDDR)-based design, such as LPDDR2, LPDDR3, LPDDR4, or the like.
  • JEDEC Joint Electron Device
  • Memory circuitry 620 may be implemented as one or more of solder down packaged integrated circuits, single die package (SDP), dual die package (DDP) or quad die package (Q17P), socketed memory modules, dual inline memory modules (DIMMs) including microDIMMs or MiniDIMMs, and/or soldered onto a motherboard via a ball grid array (BGA).
  • the memory circuitry 620 may be on-die memory or registers associated with the application circuitry 605.
  • memory circuitry 620 may include one or more mass storage devices, which may include, inter alia, a solid state disk drive (SSDD), hard disk drive (HDD), a micro HDD, resistance change memories, phase change memories, holographic memories, or chemical memories, among others.
  • SSDD solid state disk drive
  • HDD hard disk drive
  • micro HDD micro HDD
  • resistance change memories phase change memories
  • phase change memories phase change memories
  • holographic memories holographic memories
  • chemical memories among others.
  • the computer platform 600 may incorporate the three-dimensional (3D) cross-point (XPOINT) memories from Intel® and Micron®.
  • Removable memory circuitry 623 may include devices, circuitry, enclosures/housings, ports or receptacles, etc. used to couple portable data storage devices with the platform 600. These portable data storage devices may be used for mass storage purposes, and may include, for example, flash memory cards (e.g., Secure Digital (SD) cards, microSD cards, xD picture cards, and the like), and USB flash drives, optical discs, external HDDs, and the like.
  • flash memory cards e.g., Secure Digital (SD) cards, microSD cards, xD picture cards, and the like
  • USB flash drives e.g., USB flash drives, optical discs, external HDDs, and the like.
  • the platform 600 may also include interface circuitry (not shown) that is used to connect external devices with the platform 600.
  • the external devices connected to the platform 600 via the interface circuitry include sensor circuitry 621 and electro-mechanical components (EMCs) 622, as well as removable memory devices coupled to removable memory circuitry 623.
  • EMCs electro-mechanical components
  • the sensor circuitry 621 include devices, modules, or subsystems whose purpose is to detect events or changes in its environment and send the information (sensor data) about the detected events to some other a device, module, subsystem, etc.
  • sensors include, inter alia, inertia measurement units (IMUs) comprising accelerometers, gyroscopes, and/or magnetometers; microelectromechanical systems (MEMS) or nanoelectromechanical systems (NEMS) comprising 3-axis accelerometers, 3-axis gyroscopes, and/or magnetometers; level sensors; flow sensors; temperature sensors (e.g., thermistors); pressure sensors; barometric pressure sensors; gravimeters; altimeters; image capture devices (e.g., cameras or lensless apertures); light detection and ranging (LiDAR) sensors; proximity sensors (e.g., infrared radiation detector and the like), depth sensors, ambient light sensors, ultrasonic transceivers; microphones or other like audio capture devices; etc
  • EMCs 622 include devices, modules, or subsystems whose purpose is to enable platform 600 to change its state, position, and/or orientation, or move or control a mechanism or (sub)system. Additionally, EMCs 622 may be configured to generate and send
  • EMCs 622 include one or more power switches, relays including electromechanical relays (EMRs) and/or solid state relays (SSRs), actuators (e.g., valve actuators, etc.), an audible sound generator, a visual warning device, motors (e.g., DC motors, stepper motors, etc.), wheels, thrusters, propellers, claws, clamps, hooks, and/or other like electro-mechanical components.
  • EMRs electromechanical relays
  • SSRs solid state relays
  • actuators e.g., valve actuators, etc.
  • audible sound generator e.g., a visual warning device
  • motors e.g., DC motors, stepper motors, etc.
  • wheels thrusters, propellers, claws, clamps, hooks, and/or other like electro-mechanical components.
  • platform 600 is configured to operate one or more EMCs 622 based on one or more captured events and/or instructions or control signals received from a service provider and/or
  • the interface circuitry may connect the platform 600 with positioning circuitry 645.
  • the positioning circuitry 645 includes circuitry to receive and decode signals transmitted/broadcasted by a positioning network of a GNSS.
  • GNSS navigation satellite constellations
  • Examples of navigation satellite constellations (or GNSS) include United States’ GPS, Russia’s GLONASS, the European Union’s Galileo system, China’s BeiDou Navigation Satellite System, a regional navigation system or GNSS augmentation system (e.g., NAVIC), Japan’s QZSS, France’s DORIS, etc.), or the like.
  • the positioning circuitry 645 comprises various hardware elements (e.g., including hardware devices such as switches, filters, amplifiers, antenna elements, and the like to facilitate OTA communications) to communicate with components of a positioning network, such as navigation satellite constellation nodes.
  • the positioning circuitry 645 may include a Micro-PNT IC that uses a master timing clock to perform position tracking/estimation without GNSS assistance.
  • the positioning circuitry 645 may also be part of, or interact with, the baseband circuitry 510 and/or RFEMs 615 to communicate with the nodes and components of the positioning network.
  • the positioning circuitry 645 may also provide position data and/or time data to the application circuitry 605, which may use the data to synchronize operations with various infrastructure (e.g., radio base stations), for tum-by -turn navigation applications, or the like
  • the interface circuitry may connect the platform 600 with Near-Field Communication (NFC) circuitry 640.
  • NFC circuitry 640 is configured to provide contactless, short-range communications based on radio frequency identification (RFID) standards, wherein magnetic field induction is used to enable communication between NFC circuitry 640 and NFC-enabled devices external to the platform 600 (e.g., an“NFC touchpoint”).
  • RFID radio frequency identification
  • NFC circuitry 640 comprises an NFC controller coupled with an antenna element and a processor coupled with the NFC controller.
  • the NFC controller may be a chip/IC providing NFC functionalities to the NFC circuitry 640 by executing NFC controller firmware and an NFC stack.
  • the NFC stack may be executed by the processor to control the NFC controller, and the NFC controller firmware may be executed by the NFC controller to control the antenna element to emit short-range RF signals.
  • the RF signals may power a passive NFC tag (e.g., a microchip embedded in a sticker or wristband) to transmit stored data to the NFC circuitry 640, or initiate data transfer between the NFC circuitry 640 and another active NFC device (e.g., a smartphone or an NFC-enabled POS terminal) that is proximate to the platform 600.
  • a passive NFC tag e.g., a microchip embedded in a sticker or wristband
  • another active NFC device e.g., a smartphone or an NFC-enabled POS terminal
  • the driver circuitry 646 may include software and hardware elements that operate to control particular devices that are embedded in the platform 600, attached to the platform 600, or otherwise communicatively coupled with the platform 600.
  • the driver circuitry 646 may include individual drivers allowing other components of the platform 600 to interact with or control various input/output (I/O) devices that may be present within, or connected to, the platform 600.
  • I/O input/output
  • driver circuitry 646 may include a display driver to control and allow access to a display device, a touchscreen driver to control and allow access to a touchscreen interface of the platform 600, sensor drivers to obtain sensor readings of sensor circuitry 621 and control and allow access to sensor circuitry 621, EMC drivers to obtain actuator positions of the EMCs 622 and/or control and allow access to the EMCs 622, a camera driver to control and allow access to an embedded image capture device, audio drivers to control and allow access to one or more audio devices.
  • a display driver to control and allow access to a display device
  • a touchscreen driver to control and allow access to a touchscreen interface of the platform 600
  • sensor drivers to obtain sensor readings of sensor circuitry 621 and control and allow access to sensor circuitry 621
  • EMC drivers to obtain actuator positions of the EMCs 622 and/or control and allow access to the EMCs 622
  • a camera driver to control and allow access to an embedded image capture device
  • audio drivers to control and allow access to one or more audio devices.
  • the power management integrated circuitry (PMIC) 625 may manage power provided to various components of the platform 600.
  • the PMIC 625 may control power- source selection, voltage scaling, battery charging, or DC-to-DC conversion.
  • the PMIC 625 may often be included when the platform 600 is capable of being powered by a battery 630, for example, when the device is included in a UE.
  • the PMIC 625 may control, or otherwise be part of, various power saving mechanisms of the platform 600. For example, if the platform 600 is in an
  • RRC_Connected state where it is still connected to the RAN node as it expects to receive traffic shortly, then it may enter a state known as Discontinuous Reception Mode (DRX) after a period of inactivity. During this state, the platform 600 may power down for brief intervals of time and thus save power. If there is no data traffic activity for an extended period of time, then the platform 600 may transition off to an RRC Idle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc. The platform 600 goes into a very low power state and it performs paging where again it periodically wakes up to listen to the network and then powers down again.
  • DRX Discontinuous Reception Mode
  • the platform 600 may not receive data in this state; in order to receive data, it must transition back to RRC Connected state.
  • An additional power saving mode may allow a device to be unavailable to the network for periods longer than a paging interval (ranging from seconds to a few hours). During this time, the device is totally unreachable to the network and may power down completely. Any data sent during this time incurs a large delay and it is assumed the delay is acceptable.
  • a battery 630 may power the platform 600, although in some examples the platform 600 may be mounted deployed in a fixed location, and may have a power supply coupled to an electrical grid.
  • the battery 630 may be a lithium ion battery, a metal-air battery, such as a zinc- air battery, an aluminum-air battery, a lithium-air battery, and the like. In some implementations, such as in V2X applications, the battery 630 may be a typical lead-acid automotive battery.
  • the battery 630 may be a“smart battery,” which includes or is coupled with a Battery Management System (BMS) or battery monitoring integrated circuitry.
  • BMS Battery Management System
  • the BMS may be included in the platform 600 to track the state of charge (SoCh) of the battery 630.
  • the BMS may be used to monitor other parameters of the battery 630 to provide failure predictions, such as the state of health (SoH) and the state of function (SoF) of the battery 630.
  • the BMS may communicate the information of the battery 630 to the application circuitry 605 or other components of the platform 600.
  • the BMS may also include an analog-to-digital (ADC) convertor that allows the application circuitry 605 to directly monitor the voltage of the battery 630 or the current flow from the battery 630.
  • the battery parameters may be used to determine actions that the platform 600 may perform, such as transmission frequency, network operation, sensing frequency, and the like.
  • a power block, or other power supply coupled to an electrical grid may be coupled with the BMS to charge the battery 630.
  • the power block XS30 may be replaced with a wireless power receiver to obtain the power wirelessly, for example, through a loop antenna in the computer platform 600.
  • a wireless battery charging circuit may be included in the BMS. The specific charging circuits chosen may depend on the size of the battery 630, and thus, the current required.
  • the charging may be performed using the Airfuel standard promulgated by the Airfuel Alliance, the Qi wireless charging standard promulgated by the Wireless Power Consortium, or the Rezence charging standard promulgated by the Alliance for Wireless Power, among others.
  • User interface circuitry 650 includes various input/output (I/O) devices present within, or connected to, the platform 600, and includes one or more user interfaces designed to enable user interaction with the platform 600 and/or peripheral component interfaces designed to enable peripheral component interaction with the platform 600.
  • the user interface circuitry 650 includes input device circuitry and output device circuitry.
  • Input device circuitry includes any physical or virtual means for accepting an input including, inter alia, one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, keypad, mouse, touchpad, touchscreen, microphones, scanner, headset, and/or the like.
  • the output device circuitry includes any physical or virtual means for showing information or otherwise conveying information, such as sensor readings, actuator position(s), or other like information.
  • Output device circuitry may include any number and/or combinations of audio or visual display, including, inter alia, 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 touchscreens (e.g., Liquid Chrystal Displays (LCD), LED displays, quantum dot displays, projectors, etc.), with the output of characters, graphics, multimedia objects, and the like being generated or produced from the operation of the platform 600.
  • the output device circuitry may also include speakers or other audio emitting devices, printer(s), and/or the like.
  • the sensor circuitry 621 may be used as the input device circuitry (e.g., an image capture device, motion capture device, or the like) and one or more EMCs may be used as the output device circuitry (e.g., an actuator to provide haptic feedback or the like).
  • EMCs e.g., an actuator to provide haptic feedback or the like.
  • NFC circuitry comprising an NFC controller coupled with an antenna element and a processing device may be included to read electronic tags and/or connect with another NFC-enabled device.
  • Peripheral component interfaces may include, but are not limited to, a non-volatile memory port, a USB port, an audio jack, a power supply interface, etc.
  • bus or interconnect may include any number of technologies, including ISA, EISA, PCI, PCIx, PCIe, a Time-Trigger Protocol (TTP) system, a FlexRay system, or any number of other technologies.
  • the bus/IX may be a proprietary bus/IX, for example, used in a SoC based system.
  • Other bus/IX systems may be included, such as an I 2 C interface, an SPI interface, point-to-point interfaces, and a power bus, among others.
  • FIG 7 illustrates example components of baseband circuitry 710 and radio front end modules (RFEM) 715 in accordance with various embodiments.
  • the baseband circuitry 710 corresponds to the baseband circuitry 510 and 610 of Figures 5 and 6, respectively.
  • the RFEM 715 corresponds to the RFEM 515 and 615 of Figures 5 and 6, respectively.
  • the RFEMs 715 may include Radio Frequency (RF) circuitry 706, front-end module (FEM) circuitry 708, antenna array 711 coupled together at least as shown.
  • the baseband circuitry 710 includes circuitry and/or control logic configured to carry out various radio/network protocol and radio control functions that enable communication with one or more radio networks via the RF circuitry 706.
  • the radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc.
  • modulation/demodulation circuitry of the baseband circuitry 710 may include Fast-Fourier Transform (FFT), precoding, or constellation mapping/demapping functionality.
  • encoding/decoding circuitry of the baseband circuitry 710 may include convolution, tail-biting convolution, turbo, Viterbi, or Low Density Parity Check (LDPC) encoder/decoder functionality.
  • FFT Fast-Fourier Transform
  • encoding/decoding circuitry of the baseband circuitry 710 may include convolution, tail-biting convolution, turbo, Viterbi, or Low Density Parity Check (LDPC) encoder/decoder functionality.
  • LDPC Low Density Parity Check
  • the baseband circuitry 710 is configured to process baseband signals received from a receive signal path of the RF circuitry 706 and to generate baseband signals for a transmit signal path of the RF circuitry 706.
  • the baseband circuitry 710 is configured to interface with application circuitry 505/605 (see Figures 5 and 6) for generation and processing of the baseband signals and for controlling operations of the RF circuitry 706.
  • the baseband circuitry 710 may handle various radio control functions.
  • the aforementioned circuitry and/or control logic of the baseband circuitry 710 may include one or more single or multi-core processors.
  • the one or more processors may include a 3G baseband processor 704A, a 4G/LTE baseband processor 704B, a 5G/NR baseband processor 704C, or some other baseband processor(s) 704D for other existing generations, generations in development or to be developed in the future (e.g., sixth generation (6G), etc.).
  • 6G sixth generation
  • some or all of the functionality of baseband processors 704A- D may be included in modules stored in the memory 704G and executed via a Central
  • CPU 704E Processing Unit
  • baseband processors 704A-D may be provided as hardware accelerators (e.g., FPGAs, ASICs, etc.) loaded with the appropriate bit streams or logic blocks stored in respective memory cells.
  • the memory 704G may store program code of a real-time OS (RTOS), which when executed by the CPU 704E (or other baseband processor), is to cause the CPU 704E (or other baseband processor) to manage resources of the baseband circuitry 710, schedule tasks, etc.
  • RTOS real-time OS
  • the RTOS may include Operating System Embedded (OSE)TM provided by Enea®, Nucleus RTOSTM provided by Mentor Graphics®, Versatile Real-Time Executive (VRTX) provided by Mentor Graphics®, ThreadXTM provided by Express Logic®, FreeRTOS, REX OS provided by Qualcomm®, OKL4 provided by Open Kernel (OK) Labs®, or any other suitable RTOS, such as those discussed herein.
  • the baseband circuitry 710 includes one or more audio digital signal processor(s) (DSP) 704F.
  • the audio DSP(s) 704F include elements for compression/decompression and echo cancellation and may include other suitable processing elements in other embodiments.
  • each of the processors 704A-704E include respective memory interfaces to send/receive data to/from the memory 704G.
  • the baseband circuitry 710 may further include one or more interfaces to communicatively couple to other circuitries/devices, such as an interface to send/receive data to/from memory external to the baseband circuitry 710; an application circuitry interface to send/receive data to/from the application circuitry 505/605 of FIGS.
  • an RF circuitry interface to send/receive data to/from RF circuitry 706 of Figure XT; a wireless hardware connectivity interface to send/receive data to/from one or more wireless hardware elements (e.g., Near Field Communication (NFC) components, Bluetooth®/ Bluetooth® Low Energy components, Wi-Fi® components, and/or the like); and a power management interface to send/receive power or control signals to/from the PMIC 625.
  • NFC Near Field Communication
  • Bluetooth®/ Bluetooth® Low Energy components e.g., Bluetooth®/ Bluetooth® Low Energy components, Wi-Fi® components, and/or the like
  • a power management interface to send/receive power or control signals to/from the PMIC 625.
  • baseband circuitry 710 comprises one or more digital baseband systems, which are coupled with one another via an interconnect subsystem and to a CPU subsystem, an audio subsystem, and an interface subsystem.
  • the digital baseband subsystems 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, point-to-point connections, network-on-chip (NOC) structures, and/or some other suitable bus or interconnect technology, such as those discussed herein.
  • the audio subsystem may include DSP circuitry, buffer memory, program memory, speech processing accelerator circuitry, data converter circuitry such as analog-to-digital and digital-to-analog converter circuitry, analog circuitry including one or more of amplifiers and filters, and/or other like components.
  • baseband circuitry 710 may include protocol processing circuitry with one or more instances of control circuitry (not shown) to provide control functions for the digital baseband circuitry and/or radio frequency circuitry (e.g., the radio front end modules 715).
  • the baseband circuitry 710 includes individual processing device(s) to operate one or more wireless communication protocols (e.g., a“multi-protocol baseband processor” or“protocol processing circuitry”) and individual processing device(s) to implement PHY layer functions.
  • the PHY layer functions include the aforementioned radio control functions.
  • the protocol processing circuitry operates or implements various protocol layers/entities of one or more wireless communication protocols.
  • the protocol processing circuitry may operate LTE protocol entities and/or 5G/NR protocol entities when the baseband circuitry 710 and/or RF circuitry 706 are part of mmWave communication circuitry or some other suitable cellular communication circuitry.
  • the protocol processing circuitry would operate MAC, RLC, PDCP, SDAP, RRC, and NAS functions.
  • the protocol processing circuitry may operate one or more IEEE-based protocols when the baseband circuitry 710 and/or RF circuitry 706 are part of a Wi-Fi communication system.
  • the protocol processing circuitry would operate Wi-Fi MAC and logical link control (LLC) functions.
  • the protocol processing circuitry may include one or more memory structures (e.g., 704G) to store program code and data for operating the protocol functions, as well as one or more processing cores to execute the program code and perform various operations using the data.
  • the baseband circuitry 710 may also support radio communications for more than one wireless protocol.
  • the various hardware elements of the baseband circuitry 710 discussed herein may be implemented, for example, as a solder-down substrate including one or more integrated circuits (ICs), a single packaged IC soldered to a main circuit board or a multi-chip module containing two or more ICs.
  • the components of the baseband circuitry 710 may be suitably combined in a single chip or chipset, or disposed on a same circuit board.
  • some or all of the constituent components of the baseband circuitry 710 and RF circuitry 706 may be implemented together such as, for example, a system on a chip (SoC) or System-in- Package (SiP).
  • SoC system on a chip
  • SiP System-in- Package
  • the constituent components of the baseband circuitry 710 may be implemented as a separate SoC that is communicatively coupled with and RF circuitry 706 (or multiple instances of RF circuitry 706).
  • some or all of the constituent components of the baseband circuitry 710 and the application circuitry 505/605 may be implemented together as individual SoCs mounted to a same circuit board (e.g., a“multi-chip package”).
  • the baseband circuitry 710 may provide for communication compatible with one or more radio technologies.
  • the baseband circuitry 710 may support communication with an E-UTRAN or other WMAN, a WLAN, a WPAN.
  • Embodiments in which the baseband circuitry 710 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.
  • RF circuitry 706 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium.
  • the RF circuitry 706 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network.
  • RF circuitry 706 may include a receive signal path, which may include circuitry to down-convert RF signals received from the FEM circuitry 708 and provide baseband signals to the baseband circuitry 710.
  • RF circuitry 706 may also include a transmit signal path, which may include circuitry to up-convert baseband signals provided by the baseband circuitry 710 and provide RF output signals to the FEM circuitry 708 for transmission.
  • the receive signal path of the RF circuitry 706 may include mixer circuitry 706a, amplifier circuitry 706b and filter circuitry 706c.
  • the transmit signal path of the RF circuitry 706 may include filter circuitry 706c and mixer circuitry 706a.
  • RF circuitry 706 may also include synthesizer circuitry 706d for synthesizing a frequency for use by the mixer circuitry 706a of the receive signal path and the transmit signal path.
  • the mixer circuitry 706a of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 708 based on the synthesized frequency provided by synthesizer circuitry 706d.
  • the amplifier circuitry 706b may be configured to amplify the down-converted signals and the filter circuitry 706c may be a low- pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals.
  • Output baseband signals may be provided to the baseband circuitry 710 for further processing.
  • the output baseband signals may be zero-frequency baseband signals, although this is not a requirement.
  • mixer circuitry 706a of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.
  • the mixer circuitry 706a of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 706d to generate RF output signals for the FEM circuitry 708.
  • the baseband signals may be provided by the baseband circuitry 710 and may be filtered by filter circuitry 706c.
  • the mixer circuitry 706a of the receive signal path and the mixer circuitry 706a of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and upconversion, respectively.
  • the mixer circuitry 706a of the receive signal path and the mixer circuitry 706a of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection).
  • the mixer circuitry 706a of the receive signal path and the mixer circuitry 706a of the transmit signal path may be arranged for direct downconversion and direct upconversion, respectively.
  • the mixer circuitry 706a of the receive signal path and the mixer circuitry 706a of the transmit signal path may be configured for super-heterodyne operation.
  • the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of the embodiments is not limited in this respect.
  • the output baseband signals and the input baseband signals may be digital baseband signals.
  • the RF circuitry 706 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 710 may include a digital baseband interface to communicate with the RF circuitry 706.
  • ADC analog-to-digital converter
  • DAC digital-to-analog converter
  • a separate radio IC circuitry may be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this respect.
  • the synthesizer circuitry 706d may be a fractional -N synthesizer or a fractional N/N+l synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable.
  • synthesizer circuitry 706d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.
  • the synthesizer circuitry 706d may be configured to synthesize an output frequency for use by the mixer circuitry 706a of the RF circuitry 706 based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry 706d may be a fractional N/N+l synthesizer.
  • frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a requirement.
  • VCO voltage controlled oscillator
  • Divider control input may be provided by either the baseband circuitry 710 or the application circuitry 505/605 depending on the desired output frequency.
  • a divider control input (e.g., N) may be determined from a look-up table based on a channel indicated by the application circuitry 505/605.
  • Synthesizer circuitry 706d of the RF circuitry 706 may include a divider, a delay-locked loop (DLL), a multiplexer and a phase accumulator.
  • the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DP A).
  • the DMD may be configured to divide the input signal by either N or N+l (e.g., based on a carry out) to provide a fractional division ratio.
  • the DLL may include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop.
  • the delay elements may be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line.
  • Nd is the number of delay elements in the delay line.
  • synthesizer circuitry 706d may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other.
  • the output frequency may be a LO frequency (fLO).
  • the RF circuitry 706 may include an IQ/polar converter.
  • FEM circuitry 708 may include a receive signal path, which may include circuitry configured to operate on RF signals received from antenna array 711, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 706 for further processing.
  • FEM circuitry 708 may also include a transmit signal path, which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 706 for transmission by one or more of antenna elements of antenna array 711.
  • the amplification through the transmit or receive signal paths may be done solely in the RF circuitry 706, solely in the FEM circuitry 708, or in both the RF circuitry 706 and the FEM circuitry 708.
  • the FEM circuitry 708 may include a TX/RX switch to switch between transmit mode and receive mode operation.
  • the FEM circuitry 708 may include a receive signal path and a transmit signal path.
  • the receive signal path of the FEM circuitry 708 may include an LNA to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 706).
  • the transmit signal path of the FEM circuitry 708 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 706), and one or more filters to generate RF signals for subsequent transmission by one or more antenna elements of the antenna array 711.
  • PA power amplifier
  • the antenna array 711 comprises one or more antenna elements, each of which is configured convert electrical signals into radio waves to travel through the air and to convert received radio waves into electrical signals.
  • digital baseband signals provided by the baseband circuitry 710 is converted into analog RF signals (e.g., modulated waveform) that will be amplified and transmitted via the antenna elements of the antenna array 711 including one or more antenna elements (not shown).
  • the antenna elements may be omnidirectional, direction, or a combination thereof.
  • the antenna elements may be formed in a multitude of arranges as are known and/or discussed herein.
  • the antenna array 711 may comprise microstrip antennas or printed antennas that are fabricated on the surface of one or more printed circuit boards.
  • the antenna array 711 may be formed in as a patch of metal foil (e.g., a patch antenna) in a variety of shapes, and may be coupled with the RF circuitry 706 and/or FEM circuitry 708 using metal transmission lines or the like.
  • Processors of the application circuitry 505/605 and processors of the baseband circuitry 710 may be used to execute elements of one or more instances of a protocol stack.
  • processors of the baseband circuitry 710 may be used execute Layer 3, Layer 2, or Layer 1 functionality, while processors of the application circuitry 505/605 may utilize data (e.g., packet data) received from these layers and further execute Layer 4 functionality (e.g., TCP and UDP layers).
  • Layer 3 may comprise a RRC layer, described in further detail below.
  • Layer 2 may comprise a MAC layer, an RLC layer, and a PDCP layer, described in further detail below.
  • Layer 1 may comprise a PHY layer of a UE/RAN node, described in further detail below.
  • Figure 8 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein.
  • Figure 8 shows a diagrammatic representation of hardware resources 800 including one or more processors (or processor cores) 810, one or more memory /storage devices 820, and one or more communication resources 830, each of which may be communicatively coupled via a bus 840.
  • node virtualization e.g., NFV
  • a hypervisor 802 may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 800.
  • the processors 810 may include, for example, a processor 812 and a processor 814.
  • the processor(s) 810 may be, for example, 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 DSP such as a baseband processor, an ASIC, an FPGA, a radio- frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.
  • CPU central processing unit
  • RISC reduced instruction set computing
  • CISC complex instruction set computing
  • GPU graphics processing unit
  • DSP such as a baseband processor, an ASIC, an FPGA, a radio- frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.
  • the memory /storage devices 820 may include main memory, disk storage, or any suitable combination thereof.
  • the memory /storage devices 820 may include, but are not limited to, any type of volatile or nonvolatile 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.
  • DRAM dynamic random access memory
  • SRAM static random access memory
  • EPROM erasable programmable read-only memory
  • EEPROM electrically erasable programmable read-only memory
  • Flash memory solid-state storage, etc.
  • the communication resources 830 may include interconnection or network interface components or other suitable devices to communicate with one or more peripheral devices 804 or one or more databases 806 via a network 808.
  • the communication resources 830 may include wired communication components (e.g., for coupling via USB), cellular communication components, NFC components, Bluetooth® (or Bluetooth® Low Energy) components, Wi-Fi® components, and other communication components..
  • Instructions 850 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 810 to perform any one or more of the methodologies discussed herein.
  • the instructions 850 may reside, completely or partially, within at least one of the processors 810 (e.g., within the processor’s cache memory), the memory /storage devices 820, or any suitable combination thereof.
  • any portion of the instructions 850 may be transferred to the hardware resources 800 from any combination of the peripheral devices 804 or the databases 806. Accordingly, the memory of processors 810, the memory /storage devices 820, the peripheral devices 804, and the databases 806 are examples of computer-readable and machine-readable media.
  • At least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and/or methods as set forth in the example section below.
  • the baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below.
  • circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below in the example section.
  • At least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and/or methods as set forth in the example section below.
  • the baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below.
  • circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below in the example section.
  • Example 1 is one or more computer-readable media (CRM) having instructions, stored thereon, that when executed by one or more processors cause a user equipment (UE) to:
  • CRM computer-readable media
  • SSB synchronization signal/physical broadcast channel block
  • RRC radio resource control
  • RRM radio resource management
  • Example 2 is the one or more CRM of Example 1, wherein the cell is an intra-frequency cell.
  • Example 3 is the one or more CRM of Example 1, wherein the cell is an inter-frequency cell.
  • Example 4 is the one or more CRM of Example 1, wherein the SSB index is a first SSB index, wherein the cell is a first cell that is an intra-frequency cell, wherein the SMTC window is a first SMTC window, and wherein the instructions, when executed by the one or more processors, further cause the UE to: determine a second SSB index for a second cell to be measured, wherein the second cell is an inter-frequency cell; and perform or cause performance of RRM measurements on the second SSB of the second cell based on the second SSB index, wherein the second cell transmits a plurality of SSBs with different SSB indexes within a second SMTC window.
  • the SSB index is a first SSB index
  • the cell is a first cell that is an intra-frequency cell
  • the SMTC window is a first SMTC window
  • the instructions when executed by the one or more processors, further cause the UE to: determine a second SSB index for a second cell
  • Example 5 is the one or more CRM of Example 1, wherein the SSB index is a first SSB index, and wherein the instructions, when executed by the one or more processors, further cause the UE to: determine a second SSB index of a serving cell of the UE, wherein the second SSB index is associated with the UE; and monitor or cause monitoring of a paging occasion of the serving cell based on the second SSB index and during the SMTC window during which the UE also performs one of the RRM measurements.
  • Example 6 is the one or more CRM of Example 1, wherein the SSB index is a first SSB index, wherein the cell is a first cell that is an inter-frequency cell, wherein the SMTC window is a first SMTC window, and wherein the instructions, when executed by the one or more processors, further cause the UE to: determine a second SSB index for a second cell to be measured, wherein the second cell is an inter-frequency cell; and perform or cause performance of RRM measurements on the second SSB of the second cell based on the second SSB index, wherein at least one of the RRM measurements on the first and second SSBs are performed in the same SMTC window.
  • the SSB index is a first SSB index
  • the cell is a first cell that is an inter-frequency cell
  • the SMTC window is a first SMTC window
  • the instructions when executed by the one or more processors, further cause the UE to: determine a second SSB index for a second cell to be measured,
  • Example 7 is the one or more CRM of Example 1, wherein the SSB index is determined based on quasi-colocation with another signal.
  • Example 8 is the one or more CRM of Example 7, wherein the another signal is a physical downlink shared channel (PDSCH) received by the UE.
  • PDSCH physical downlink shared channel
  • Example 9 is the one or more CRM of Example 1, wherein the SSB index is determined based on a frequency band of the cell.
  • Example 10 is the one or more CRM of any one of Examples 1-9, wherein the instructions, when executed by the one or more processors, further cause the UE to: enter an awake power state to perform the RRM measurements; and enter a sleep power state between the RRM measurements.
  • Example 11 is an apparatus to be implemented in a user equipment (UE), the apparatus comprising: a memory to store a synchronization signal/physical broadcast channel block (SSB) index for a cell to be measured when the UE is in a radio resource control (RRC) idle state, wherein the cell is an intra-frequency cell or an inter-frequency cell; and baseband circuitry coupled to the memory, the baseband circuitry to cause the UE to perform radio resource management (RRM) measurements on a first SSB of the cell based on the SSB index, wherein a next generation Node B (gNB) associated with the cell transmits a plurality of SSBs with different SSB indexes within a SSB measurement time configuration (SMTC) window.
  • SSB
  • Example 12 is the apparatus of Example 11, wherein the cell is an intra-frequency cell.
  • Example 13 is the apparatus of Example 11, wherein the cell is an inter-frequency cell.
  • Example 14 is the apparatus of Example 11, wherein the SSB index is a first SSB index, wherein the cell is a first cell that is an intra-frequency cell, wherein the SMTC window is a first SMTC window, and wherein: the memory is further to store a second SSB index for a second cell to be measured, wherein the second cell is an inter-frequency cell; and the baseband circuitry is further to cause the UE to perform RRM measurements on the second SSB of the second cell based on the second SSB index, wherein the second cell transmits a plurality of SSBs with different SSB indexes within a second SMTC window.
  • the SSB index is a first SSB index
  • the cell is a first cell that is an intra-frequency cell
  • the SMTC window is a first SMTC window
  • the memory is further to store a second SSB index for a second cell to be measured, wherein the second cell is an inter-frequency cell
  • the baseband circuitry
  • Example 15 is the apparatus of Example 11, wherein the SSB index is a first SSB index, and wherein: the memory is further to store a second SSB index of a serving cell of the UE, wherein the second SSB index is one of multiple SSB indexes of the serving cell and is associated with the UE; and the baseband circuitry is further to cause the UE to monitor a paging occasion of the serving cell during the SMTC window based on the second SSB index.
  • Example 16 is the apparatus of Example 11, wherein the SSB index is a first SSB index, wherein the cell is a first cell that is an inter-frequency cell, wherein the SMTC window is a first SMTC window, and wherein: the memory is to store a second SSB index for a second cell to be measured, wherein the second cell is an inter-frequency cell; and the baseband circuitry is further to cause the UE to perform RRM measurements on a second SSB of the second cell based on the second SSB index, wherein at least one of the RRM measurements on the first and second SSBs are performed in the same SMTC window.
  • the SSB index is a first SSB index
  • the cell is a first cell that is an inter-frequency cell
  • the SMTC window is a first SMTC window
  • the memory is to store a second SSB index for a second cell to be measured, wherein the second cell is an inter-frequency cell
  • the baseband circuitry is further to cause the
  • Example 17 is the apparatus of Example 1, wherein the baseband circuitry is further to: determine the SSB index based on quasi-colocation with another signal; and cause the memory to store the SSB index.
  • Example 18 is the apparatus of Example 11, wherein the baseband circuitry is further to: determine the SSB index based on a frequency band of the cell; and cause the memory to store the SSB index.
  • Example 19 is the apparatus of Example 11, wherein the baseband circuitry is further to: transition the UE to an awake power state to perform the RRM measurements; and transition the UE to a sleep power state between the RRM measurements.
  • Example 20 is the apparatus of any one of Examples 11-19, further comprising radio frequency circuitry coupled to the baseband circuitry, the radio frequency circuitry to perform the RRM measurements.
  • Example 21 is an apparatus to be implemented in a user equipment (UE), the apparatus comprising: means for receiving a first signal/physical broadcast channel block (SSB) index for an intra-frequency cell to be measured when the UE is in a radio resource control (RRC) idle state; means for receiving a second SSB index for a first inter-frequency cell to be measured when the UE is in the RRC idle state; means for receiving a third SSB index for a second inter- frequency cell to be measured when the UE is in the RRC idle state; means for receiving a fourth SSB index for a serving cell of the UE; means for performing a first radio resource management (RRM) measurement on the intra-frequency cell based on the first SSB index; means for performing a second RRM measurement on the first inter-frequency cell based on the second SSB index; means for performing a third RRM measurement on the second inter-frequency cell based on the third SSB index; and means for monitoring a paging occasion of the serving cell based on the fourth SS
  • Example 22 is the apparatus of Example 21, wherein the second RRM measurement and the monitoring of the paging occasion are to be performed during the same SMTC window.
  • Example 23 is the apparatus of Example 21, wherein the second RRM measurement and the third RRM measurement are to be performed during the same SMTC window.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Des modes de réalisation de la présente invention concernent des techniques permettant d'effectuer des mesures de gestion de ressources radio (RRM) lorsqu'un équipement d'utilisateur (UE) est dans un état de repos de commande de ressources radio (RRC) dans un réseau de nouvelle radio (NR) 5G. D'autres modes de réalisation peuvent faire l'objet d'une description et de revendications.
PCT/US2019/059106 2018-11-01 2019-10-31 Mesures en état de repos de rrc dans des systèmes de nouvelle radio (nr) WO2020092732A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP19879574.2A EP3874816A4 (fr) 2018-11-01 2019-10-31 Mesures en état de repos de rrc dans des systèmes de nouvelle radio (nr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201862754526P 2018-11-01 2018-11-01
US62/754,526 2018-11-01

Publications (1)

Publication Number Publication Date
WO2020092732A1 true WO2020092732A1 (fr) 2020-05-07

Family

ID=70464200

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2019/059106 WO2020092732A1 (fr) 2018-11-01 2019-10-31 Mesures en état de repos de rrc dans des systèmes de nouvelle radio (nr)

Country Status (2)

Country Link
EP (1) EP3874816A4 (fr)
WO (1) WO2020092732A1 (fr)

Cited By (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022029720A1 (fr) * 2020-08-06 2022-02-10 Telefonaktiebolaget Lm Ericsson (Publ) Fenêtre de configuration d'instant de mesure de bloc de signaux de synchronisation, et configuration d'intervalle de mesure pour des réseaux non terrestres
CN114584955A (zh) * 2020-11-30 2022-06-03 航天信息股份有限公司 一种唤醒功率设置方法及车载电子标签
CN114759967A (zh) * 2021-01-08 2022-07-15 联发科技（新加坡）私人有限公司 用于执行测量的方法及用户设备
WO2022151339A1 (fr) * 2021-01-15 2022-07-21 Apple Inc. Appareil, procédé pour équipement utilisateur, équipement utilisateur et procédé pour élément de réseau
WO2022155869A1 (fr) * 2021-01-22 2022-07-28 Qualcomm Incorporated Détection de cellule candidate pour mode autonome
WO2022195315A1 (fr) * 2021-03-18 2022-09-22 Orope France Sarl Appareil et procédé de communication sans fil
EP4167640A1 (fr) * 2021-10-18 2023-04-19 MediaTek Inc. Changement de synchronisation et nouvelle procédure de mobilité radio
WO2023069486A1 (fr) * 2021-10-20 2023-04-27 Intel Corporation Retard de rapport de mesure pour des intervalles de mesure pré-configurés
WO2023128857A1 (fr) * 2021-12-27 2023-07-06 Telefonaktiebolaget Lm Ericsson (Publ) Procédure de mesures dans un état de faible mobilité de ntn
EP4156761A4 (fr) * 2020-08-06 2023-07-12 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Procédé de mesure de cellule voisine, dispositif terminal et dispositif réseau
WO2023151026A1 (fr) * 2022-02-11 2023-08-17 Apple Inc. Surveillance de liaison radio et amélioration de gestion de ressources radio inactives pour des réseaux non terrestres
WO2023206144A1 (fr) * 2022-04-27 2023-11-02 Apple Inc. Mesure gnss améliorée pour ntn iot
WO2024020901A1 (fr) * 2022-07-27 2024-02-01 Nokia Shanghai Bell Co., Ltd. Recherche de cellule de desserte
WO2024096962A1 (fr) * 2022-10-31 2024-05-10 Qualcomm Incorporated Mesures de fréquence inter-intra de csi-rs

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CA3049318A1 (fr) 2017-01-06 2018-07-12 Ntt Docomo, Inc. Terminal utilisateur et procede de communication radio
WO2018143760A1 (fr) 2017-02-06 2018-08-09 엘지전자 주식회사 Procédé de réalisation de mesure et équipement utilisateur

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CA3049318A1 (fr) 2017-01-06 2018-07-12 Ntt Docomo, Inc. Terminal utilisateur et procede de communication radio
WO2018143760A1 (fr) 2017-02-06 2018-08-09 엘지전자 주식회사 Procédé de réalisation de mesure et équipement utilisateur

Non-Patent Citations (5)

* Cited by examiner, † Cited by third party
Title
ANONYMOUS: "3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Requirements for support of radio resource management (Release 15)", 3GPP STANDARD; TECHNICAL SPECIFICATION; 3GPP TS 38.133, vol. RAN WG4, no. V15.3.0, 3 October 2018 (2018-10-03), pages 1 - 136, XP051487579 *
INTEL CORPORATION: "Summary of Offline Discussion for NR RRM measurements", 3GPP DRAFT; R1-1807689 SUMMARY RRM - TUE, vol. RAN WG1, 24 May 2018 (2018-05-24), Busan, South Korea, pages 1 - 13, XP051515430 *
LG ELECTRONICS: "Discussions on detection and measurement on IAB nodes", 3GPP DRAFT; R1-1810274 DISCUSSIONS ON DETECTION AND MEASUREMENT AMONG IAB NODES, vol. RAN WG1, 29 September 2018 (2018-09-29), Chengdu, China, pages 1 - 6, XP051517688 *
See also references of EP3874816A4
VIVO: "On UE Power Consumption Reduction in RRM Measurements", 3GPP DRAFT; R1-1810415 ON UE POWER CONSUMPTION REDUCTION IN RRM MEASUREMENTS, vol. RAN WG1, rements, 29 September 2018 (2018-09-29), Chengdu, China, pages 1 - 7, XP051517824 *

Cited By (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4156761A4 (fr) * 2020-08-06 2023-07-12 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Procédé de mesure de cellule voisine, dispositif terminal et dispositif réseau
WO2022029720A1 (fr) * 2020-08-06 2022-02-10 Telefonaktiebolaget Lm Ericsson (Publ) Fenêtre de configuration d'instant de mesure de bloc de signaux de synchronisation, et configuration d'intervalle de mesure pour des réseaux non terrestres
US20230284060A1 (en) * 2020-08-06 2023-09-07 Telefonaktiebolaget Lm Ericsson (Publ) Synchronization signal block measurement timing configuration window and measurement gap configuration for non-terrestrial networks
CN114584955A (zh) * 2020-11-30 2022-06-03 航天信息股份有限公司 一种唤醒功率设置方法及车载电子标签
CN114759967A (zh) * 2021-01-08 2022-07-15 联发科技（新加坡）私人有限公司 用于执行测量的方法及用户设备
TWI787039B (zh) * 2021-01-08 2022-12-11 新加坡商聯發科技（新加坡）私人有限公司 用於執行測量的方法及使用者設備
CN114759967B (zh) * 2021-01-08 2024-05-14 联发科技（新加坡）私人有限公司 用于执行测量的方法及用户设备
WO2022151339A1 (fr) * 2021-01-15 2022-07-21 Apple Inc. Appareil, procédé pour équipement utilisateur, équipement utilisateur et procédé pour élément de réseau
US12082028B2 (en) 2021-01-15 2024-09-03 Apple Inc. Apparatus, method for user equipment, user equipment and method for network element to configure measurement gap (MG) patterns
WO2022155869A1 (fr) * 2021-01-22 2022-07-28 Qualcomm Incorporated Détection de cellule candidate pour mode autonome
WO2022195315A1 (fr) * 2021-03-18 2022-09-22 Orope France Sarl Appareil et procédé de communication sans fil
EP4167640A1 (fr) * 2021-10-18 2023-04-19 MediaTek Inc. Changement de synchronisation et nouvelle procédure de mobilité radio
WO2023069486A1 (fr) * 2021-10-20 2023-04-27 Intel Corporation Retard de rapport de mesure pour des intervalles de mesure pré-configurés
WO2023128857A1 (fr) * 2021-12-27 2023-07-06 Telefonaktiebolaget Lm Ericsson (Publ) Procédure de mesures dans un état de faible mobilité de ntn
WO2023151026A1 (fr) * 2022-02-11 2023-08-17 Apple Inc. Surveillance de liaison radio et amélioration de gestion de ressources radio inactives pour des réseaux non terrestres
WO2023206144A1 (fr) * 2022-04-27 2023-11-02 Apple Inc. Mesure gnss améliorée pour ntn iot
WO2024020901A1 (fr) * 2022-07-27 2024-02-01 Nokia Shanghai Bell Co., Ltd. Recherche de cellule de desserte
WO2024096962A1 (fr) * 2022-10-31 2024-05-10 Qualcomm Incorporated Mesures de fréquence inter-intra de csi-rs

Also Published As

Publication number Publication date
EP3874816A4 (fr) 2022-08-24
EP3874816A1 (fr) 2021-09-08

Similar Documents

Publication Publication Date Title
WO2020092732A1 (fr) Mesures en état de repos de rrc dans des systèmes de nouvelle radio (nr)
US11831381B2 (en) Beam failure recovery for uplink
US20200374735A1 (en) Signaling enhancements of smtc configuration for an iab mt
US11917663B2 (en) Physical downlink shared channel (PDSCH) repetition transmission for reliable communications
US12156197B2 (en) Preconfigured shared resources for uplink transmission
US11991574B2 (en) Method for cross-cell beam measurement
US12022398B2 (en) Techniques to reduce radio resource management measurements and user equipment power consumption
US12279247B2 (en) Setting default physical downlink shared channel (PDSCH) beams
US20220167223A1 (en) Methods for Enhanced Handover Using Conditional and Simultaneous Connectivity Handover
US12120571B2 (en) User equipment-triggered lower layer-based handover
US12041487B2 (en) User equipment based packet data convergence protocol (PDCP) duplication activation and deactivation
US20210135816A1 (en) Aperiodic sounding reference signal (srs) triggering and low overhead srs transmission with antenna switching
US11844132B2 (en) User plane early data transmission (EDT) message 4 (MSG4) loss
WO2020102076A1 (fr) Commutation de faisceau dans une agrégation de porteuses non contiguës intra-bande
US12075301B2 (en) Cell reselection for new radio—unlicensed
US20220191896A1 (en) Systems and methods of providing timing of sl transmission when scheduled by nr gnb
US20240357438A1 (en) Generating filtered results in user equipment-triggered lower layer-based handover
US12160729B2 (en) Radio unlicensed (NR-U) idle mode operations
US12101195B2 (en) Methods for radio link failure prevention for URLLC
WO2020190965A1 (fr) Conception de signalisation pour un équipement d'utilisateur fonctionnant dans un spectre sans licence

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19879574

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2019879574

Country of ref document: EP

Effective date: 20210601

点击 这是indexloc提供的php浏览器服务，不要输入任何密码和下载