WO2019098920A1 - Temps de déclenchement (ttt) alternatif pour des événements de mesure sur la base d'un type de signal de référence (rs) - Google Patents

Temps de déclenchement (ttt) alternatif pour des événements de mesure sur la base d'un type de signal de référence (rs) Download PDF

Info

Publication number
WO2019098920A1
WO2019098920A1 PCT/SE2018/051171 SE2018051171W WO2019098920A1 WO 2019098920 A1 WO2019098920 A1 WO 2019098920A1 SE 2018051171 W SE2018051171 W SE 2018051171W WO 2019098920 A1 WO2019098920 A1 WO 2019098920A1
Authority
WO
WIPO (PCT)
Prior art keywords
neighbor cells
lists
list
ttt
alternate
Prior art date
Application number
PCT/SE2018/051171
Other languages
English (en)
Inventor
Pradeepa Ramachandra
Johan Rune
Kristina Zetterberg
Icaro L. J. Da Silva
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
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 Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Publication of WO2019098920A1 publication Critical patent/WO2019098920A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0083—Determination of parameters used for hand-off, e.g. generation or modification of neighbour cell lists
    • H04W36/0085—Hand-off measurements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0058—Transmission of hand-off measurement information, e.g. measurement reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0061—Transmission or use of information for re-establishing the radio link of neighbour cell information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0083—Determination of parameters used for hand-off, e.g. generation or modification of neighbour cell lists
    • H04W36/0085—Hand-off measurements
    • H04W36/0088—Scheduling hand-off measurements

Definitions

  • the present Application is related to wireless communication networks, and more specifically related to reporting measurements made on signals from neighbor cells in a wireless network.
  • the base station can create multiple coverage beams - sometimes referred to as “beamforming” - with each beam targeted to a particular user or subset of users within the base station’s entire coverage area. In this manner, the base station can spatially multiplex more users within a given frequency bandwidth in the coverage area, thereby increasing system capacity.
  • This technique is often referred to as very large (VL) multi-user (MU) multiple-input-multiple-output (MIMO), and is abbreviated by VL-MIMO hereinafter.
  • LTE Long-Term Evolution
  • 4G fourth-generation
  • NR new radio
  • RRM radio resource management
  • the transmitted signals on which the UE makes RRM measurements are often referred to as reference signals (RS).
  • RS reference signals
  • the network informs the UE of requested information using a measurement configuration, while the UE uses a measurement report to inform the network about the measurements made on the neighbor cells. This exchange of information is part of the Radio Resource Control (RRC) protocol.
  • RRC Radio Resource Control
  • the measurement configuration is provided to the UE by means of dedicated signaling.
  • the measurement configuration provided to the UE typically can include the following parameters:
  • Measurement Objects q measOhjeci frequencies and cells on which the LIE shall perform the measurements. These include intra- and inter- frequency neighbors using either the same or a different radio access technology (RAT).
  • RAT radio access technology
  • Reporting Configurations (reporiConfig). the criteria used by the UE to trigger the transmission of a measurement report and the quantities that the UE can include in the report. Triggers can either be periodic or event-based.
  • Measurement Identities identifiers that link a measurement object with a reporting configuration, e.g., as reference numbers in measurement reports.
  • Measurement Gaps periods of time that the UE may use to perform measurements while in connected mode.
  • TTT Time-To-Trigger
  • the triggering criterion and TTT are configured in a reporiConfig message sent by the network to the UE.
  • the value of TTT provided in reporiConfig is applicable to all neighbor cells of the UE that could trigger a measurement report based on the specified triggering criterion.
  • the ASN. l code for an exemplary reporiConfig message is shown below.
  • messages can refer to an actual message defined as part of a particular protocol (e.g., RRC protocol), or to a defined portion of an actual message (e.g., an information element (IE) in an RRC-defmed message).
  • RRC protocol e.g., RRC protocol
  • IE information element
  • ReportConfigEUTRA SEQUENCE ⁇ triggerType CHOICE ⁇
  • ThresholdEUTRA a5-Thresholdl ThresholdEUTRA
  • Threshold2 ThresholdE UTRA event A6-r 10 SEQUENCE ⁇
  • An exemplary 5G HetNet is shown in Figure 1 and can comprise five (5) macro cells (“macro-A” through“macro-E”) and four (4) micro cells (“micro-A” through“micro- D”), all of which utilize NR technology.
  • An exemplary UE can be situated within the coverage area of macro-A, referred to as UE’s serving cell. The UE can then be configured for RRM measurements of all, or a subset of, its neighbor cells comprising all microcells and macrocells B-D.
  • an alternativeTimeToTrigger (also referred to as “ altTTT’) was introduced in Release 12.
  • the network can facilitate improved UE measurement reporting that avoids and/or reduces both unnecessary and untimely (e.g, too late) measurement reports.
  • usage of TTT and alternativeTimeToTrigger a generic larger value of TTT (l60ms) can be used for slowly varying macrocell neighbors and a smaller value of alternativeTimeToTrigger (40ms) can be used for quickly varying microcell neighbors.
  • the value for alternativeTimeToTrigger can also be configured in the reportConfig message and the cells for which this value is applicable are provided in a corresponding measObject message.
  • An exemplary procedure and corresponding ASN. l configurations in reportConfig and measObject (relevant portions only) are given below.
  • MeasObjectEUTRA SEQUENCE ⁇
  • AltTTT-CellsToAddModList-rl 2 :: SEQUENCE (SIZE (L.maxCellMeas)) OF AltTTT- CellsToAddMod-rl 2
  • AltTTT-CellsToAddMod-rl 2 :: SEQ UENCE ⁇ celllndex-rl2 INTEGER (L.maxCellMeas), phys CellldRange-rl 2 PhysCellldRange
  • the UE can make RRM measurements on multiple types of RSs transmitted by the gNB.
  • the UE can make measurements on Channel State Information RS (CSI-RS) and Synchronization Signal Blocks (SSBs).
  • CSI-RS Channel State Information RS
  • SSBs Synchronization Signal Blocks
  • the UE can be configured, via reportConfig , to measure only SSBs, only CSI-RS, or both types.
  • the beamformers in each gNB can be configured to transmit CSI-RS and SSBs with different number of beams and/or beam patterns.
  • the number of beams used to sweep the CSI-RS can be larger than the number of beams used to sweep SSBs. This can cause the UE to measure different reference signal received power (RSRP) values for CSI-RS and SSBs when determinining cell quality for a neighbor cell.
  • RSRP reference signal received power
  • the changes in a UE’s CSI-RS based RSRP measurements for cell A (serving cell) and cell B (target neighbor cell) over time are shown.
  • the measured RSRP for neighbor cell B becomes greater than the measured RSR for serving cell A, initiating the TTT for the reporting event (assuming other relevant offsets are zero).
  • the TTT expires and the UE tries to send the measurement report.
  • the CSI-RS-based measured RSRP of cell B is 5CSI-RS larger than the corresponding measured value of cell A.
  • FIG 3 the changes in a UE’s SSB-based RSRP measurements for cell A (serving cell) and cell B (target neighbor cell) over time are shown.
  • the measured RSRP for neighbor cell B becomes greater than the measured RSR for serving cell A, initiating the TTT for the reporting event (assuming other relevant offsets are zero).
  • the TTT expires and the UE tries to send the measurement report.
  • the SSB-based measured RSRP of cell B is 5SSB larger than the corresponding measured value of cell A.
  • the difference in measured RSRP values of cells A and B at the time of sending measurement report can vary largely based on the type of RS used for the measurement.
  • One solution to this problem is to configure different TTT values using different reportConfig messages, e.g, one reportConfig is used to configure TTTCSI-RS for CSI-RS-based measurements and another is used to configure TTTSSB for S SB-based measurements.
  • reportConfig is used to configure TTTCSI-RS for CSI-RS-based measurements
  • TTTSSB for S SB-based measurements.
  • it can be beneficial to use a smaller TTT value when a UE is evaluating the reporting configuration for a cell based on CSI- RS e.g, to reduce the risk of too late a handover).
  • TTT value when a TIE is evaluating the reporting configuration for a cell based on SSB (e.g, to reduce unnecessary measurement reports).
  • One method of achieving this is to use the TTT field in the reportConfig differently for CSI-RS based reporting configurations compared to SS based reporting configurations.
  • the scenario may involve a HetNet where macro-A (the serving cell for a EGE) has neighbor cells macro-B through macro-E and micro-A through micro-D.
  • macro-A the serving cell for a EGE
  • macro-E the serving cell for a EGE
  • micro-A the serving cell for a EGE
  • Exemplary desired TTT values that can facilitate the desired reduction in unnecessary measurement reports and avoidance of untimely measurement reports are listed in Table 1 below, while corresponding reportConfig values for the two types of RS are given in Table 2 below.
  • Table 1 Exemplary TTT values corresponding to Figure 1.
  • Table 2 Exemplary configurations corresponding to TTT values shown in Table 1.
  • the first reporting configuration is for the SSB based cell measurements with a TTT of 320 ms and the alternativeTimeToTrigger of 160 ms. This configuration will facilitate the inclusion of all neighbor microcells in the altTTT- CellsToAddModList identified in the measObject message.
  • the second reporting configuration is for the CSI-RS based measurements with a TTT of 160 ms and alternativeTimeToTrigger of 40 ms. Since neighbor cells micro-A and micro-B are already included in the altTTT- CellsToAddModList, however, they will be forced to use a TTT of 40 ms instead of the desired 160 ms TTT, as shown in Table 2.
  • Exemplary embodiments of the present disclosure can provide solutions to these and other challenges, such as by configuring a EGE to facilitate the use of TTT values corresponding to the particular RS that the TIE utilizes for RRM measurements in the context of mobility events.
  • some exemplary embodiments disclosed herein can configure a TIE with an RS-type-specific altTTT-CellsToAddModList in the measObject message, e.g., altTTT-CellsToAddModList-SSBBased or altTTT-CellsToAddModList-CSI- RSBased.
  • the TIE can apply the corresponding altTTT-CellsToAddModList when identifying what value of TTT to be used for which cells.
  • exemplary embodiments can configure the EGE with an RS-type specific altTTT-CellsToAddModList in the reportConfig message.
  • the TIE can apply the corresponding altTTT-CellsToAddModList while identifying what value of TTT to be used for which cells.
  • exemplary embodiments can provide a flexible technique to configure different TTT values for different cells depending on the RS type most suitable for each cell, thereby enabling more robust mobility for UEs between cells in a network.
  • Such exemplary embodiments can include methods and/or procedures performed by a base station (e.g, eNB or gNB) for configuring a wireless device (e.g, TIE) to report measurements made on signals from neighbor cells in a wireless network.
  • a base station e.g, eNB or gNB
  • a wireless device e.g, TIE
  • An exemplary method and/or procedure can include the base station transmitting, to a wireless device, a measurement object message identifying a plurality of neighbor cells on which to perform measurements and one or more subsets of the plurality of neighbor cells, each subset corresponding to one of a plurality of RS types available to be measured.
  • the exemplary method and/or procedure can also include the base station transmitting, to the wireless device, a reporting configuration message identifying one or more reporting events, each reporting event corresponding to measurements of a particular one of the plurality of RS types.
  • the exemplary method and/or procedure can also include the base station receiving, from the wireless device, a measurement report corresponding to one of the reporting events, the measurement report comprising measurements made on one of the subset of neighbor cells based on the corresponding RS type.
  • the measurement object message can include an alternate TTT associated with each of the one of more subsets of the neighbor cells, and the measurements comprising the measurement report are reported based on the alternate TTT.
  • the measurement object messages can include a plurality of lists of neighbor cells associated with an alternate TTT, the plurality of lists comprising a first list of neighbor cells associated with th alternate TTT for measurements based on all RS types and one of more futher lists of neighbor cells, each further list associated with the alternate TTT for measurements based on a particular RS type.
  • at least a portion of the further lists can identify neighbor cells to be added to the first list for measurements based on the associated RS type.
  • at least a portion of the further lists can identify neighbor cells to be removed from the first list for measurements based on the associated RS type.
  • the measurement object message can include a plurality of lists of neighbor cells associated with an alternate TTT, each list further associated with a unique index, and the report configuration message can comprise one or more indicators, each indicator identifying one of the plurality of lists according to the associated index value.
  • the plurality of lists of neighbor cells can comprise a first plurality of lists corresponding to a first RS type and a second plurality of lists corresponding to a second RS type, each list further associated with an index value unique to the particular plurality; and each indicator can identify a list of the first plurality or the second plurality according to the associated index value.
  • the measurement object message can include a plurality of lists of neighbor cells, the plurality of lists comprising a first plurality of lists of neighbor cells to be associated with an alternate TTT and a second plurality of lists of neighbor cells not to be associated with the alternate TTT, each list further associated with an index value unique to the particular plurality.
  • the report configuration message can include a list of neighbor cells associated with the alternate TTT and one or more indicators, each indicator identifying one of the plurality of lists according to the associated index value.
  • each of the first and second pluralities of lists is further associated with a particular RS type, each list is further associated with an index value unique to the particular plurality and the particular RS type.
  • the measurements comprising the measurement report can include measurements made on a determined list of neighbor cells comprising the list of neighbor cells associated with the alternate TTT and lists of neighbor cells of the first plurality identified by the one or more indicators, wherein the determined list excludes lists of neighbor cells of the second plurality identified by the one or more indicators.
  • Exemplary embodiments also include base stations (e.g ., eNB or gNB) configured to perform the operations of the above-described exemplary methods and/or procedures.
  • base stations e.g ., eNB or gNB
  • exemplary embodiments can include methods and/or procedures performed by a wireless device for reporting measurements made on signals from neighbor cells in a wireless network.
  • the exemplary methods and/or procedures can include the wireless device receiving, from a serving base station, a measurement object message identifying a plurality of neighbor cells on which to perform measurements and one or more subsets of the plurality of neighbor cells, each subset corresponding to one of a plurality of RS types available to be measured.
  • the exemplary methods and/or procedures can also include the wireless device receiving, from the serving base station, a reporting configuration message identifying one or more reporting events, each reporting event corresponding to measurements of a particular one of the plurality of RS types.
  • the exemplary methods and/or procedures can also include the wireless device determining, based on the received measurement object and reporting configuration messages, reporting events for each of the one or more subsets of the plurality of neighbor cells.
  • the exemplary methods and/or procedures can also include the wireless device reporting, according to one of the determined reporting events, measurements made on the corresponding subset of neighbor cells based on the corresponding RS type.
  • the measurement object message can include an alternate TTT associated with each of the one of more subsets of the neighbor cells, and determining reporting events can include assigning the alternate TTT for reporting measurements made on the associated subset of neighbor cells based on the corresponding RS type.
  • the measurement object message can include a plurality of lists of neighbor cells associated with an alternate TTT.
  • the plurality of lists can include a first list of neighbor cells associated with the alternate TTT for measurements based on all RS types and one of more fiither lists of neighbor cells, each further list associated with the alternate TTT for measurements based on a particular RS type.
  • at least a portion of the further lists can identify neighbor cells to be added to the first list for measurements based on the associated RS type.
  • at least a portion of the further lists can identify neighbor cells to be removed from the first list for measurements based on the associated RS type.
  • the measurement object message can include a plurality of lists of neighbor cells associated with an alternate TTT, each list further associated with a unique index.
  • the report configuration message can include one or more indicators, each indicator identifying one of the plurality of lists according to the associated index value.
  • the plurality of lists of neighbor cells can include a first plurality of lists corresponding to a first RS type and a second plurality of lists corresponding to a second RS type, each list further associated with an index value unique to the particular plurality.
  • Each indicator can identify a list of the first plurality or the second plurality according to the associated index value.
  • the measurement object message can include a plurality of lists of neighbor cells, the plurality of lists comprising a first plurality of lists of neighbor cells to be associated with an alternate TTT and a second plurality of lists of neighbor cells not to be associated with the alternate TTT, each list further associated with an index value unique to the particular plurality.
  • the report configuration message can include a list of neighbor cells associated with the alternate TTT and one or more indicators, each indicator identifying one of the plurality of lists according to the associated index value.
  • each of the first and second pluralities of lists is further associated with a particular RS type, each list further associated with an index value unique to the particular plurality and the particular RS type.
  • the wireless device can determine the reporting events by assigning the alternate TTT for reporting measurements made on a determined list of neighbor cells comprising the list of neighbor cells associated with the alternate TTT and lists of neighbor cells of the first plurality identified by the one or more indicators, wherein the determined list excludes lists of neighbor cells of the second plurality identified by the one or more indicators.
  • Exemplary embodiments can also include wireless devices (e.g ., UEs) configured to perform the operations of the above-described exemplary methods and/or procedures.
  • wireless devices e.g ., UEs
  • These and other exemplary embodiments can provide various advantages, including improved flexibility for the network to configure various TTT (and alternate TTT) values for reporting measurements of signals in neighbor cells, according to characteristics of individual cells and individual reference signals, including the per-cell beamforming used to transmit each type of reference signal.
  • Such advantages can facilitate more timely design, implementation, and deployment of 5G/NR solutions.
  • More generally, such embodiments can provide more robust mobility for wireless devices, which can facilitate improvements in capacitiy, throughput, latency, etc. that are promised by multi-antenna beamforming/spatial multiplexing solutions for 5G/NR.
  • FIG. 1 illustrates an exemplary heterogenous network (HetNet) in 5G.
  • Figure 2 illustrates various exemplary CSI-RS-based RSRP measurements.
  • Figure 3 illustrates various exemplary SSB-based RSRP measurements.
  • Figure 4 is a block diagram of an exemplary wireless network configurable according to various exemplary embodiments of the present disclosure.
  • FIG. 5 is a flowchart illustrating an exemplary method and/or procedure performed by a user equipment (UE), according to various exemplary embodiments of the present disclosure.
  • UE user equipment
  • Figure 6 is a flowchart illustrating an exemplary method and/or procedure performed by a base station, according to various exemplary embodiments of the present disclosure.
  • Figure 7 illustrates one embodiment of a UE, according to various exemplary embodiments of the present disclosure.
  • Figure 8 illustrates a virtualization environment, according to various exemplary embodiments of the present disclosure.
  • Figure 9 schematically illustrates a telecommunication network connected via an intermediate network to a host computer, according to various exemplary embodiments of the present disclosure.
  • Figure 10 is a generalized block diagram of a host computer communicating via a base station with a user equipment over a partially wireless connection, according to various exemplary embodiments of the present disclosure.
  • FIGS 11 to 14 are flowcharts illustrating example methods implemented in a communication system including a host computer, a base station, and a UE, according to various exemplary embodiments of the present disclosure.
  • the network can configure EEs to report RRM measurements based on a separate altTTT-CellsToAddModList for each RS type (referred to, e.g., as ciltTTT-CellsToAddModList-SSBBased and altTTT-CellsToAddModList-CSI-RSBased ).
  • Table 3 illustrates an exemplary measurement reporting configuration, according to these embodiments, for the exemplary HetNet shown in Figure 1.
  • a EE evaluates a received SSB-based measurement reporting configuration, it can apply a l60-ms TTT for the four neighboring microcells and a 320-ms TTT for all other neighbor cells (e.g, the macrocells).
  • the EE evaluates a received CSI-RS-based measurement reporting configuration, it can apply a 120-ms TTT for micro-C and micro-D, and a 40-ms TTT for all other cells.
  • Table 1 Exemplary TTT configuration values corresponding to particular embodiments.
  • ASN. l code for an exemplary measObjectNR message providing the above configurations is shown below (relevant portions only). Such exemplary ASN. l code can be included, e.g ., in a 3GPP specification of functionality corresponding and/or related to these embodiments.
  • the MeasObjectNR message can include information applicable for SSB-based or CSI-RS-based intra- or inter-frequency RRM measurements.
  • MeasObjectNR :: SEQUENCE ⁇
  • altTTT-CellsToRemoveList-SSBBased CelllndexList OPTIONAL altTTT-CellsToAddModList-SSBBased AltTTT-CellsToAddModList OPTIONAL
  • altTTT-CellsToRemoveList-CSI-RSBased CelllndexList OPTIONAL altTTT-CellsToAddModList-CSI-RSBased AltTTT-CellsToAddModList OPTIONAL
  • AltTTT-CellsToAddModList :: SEQUENCE (SIZE (L.maxCellMeas)) OF AltTTT- CellsToAddMod
  • An exemplary wireless device operation and/or procedure related to the above- described exemplary embodiments can include receiving a measurement object encompassing rsType specific altTTT-CellsToAddModList , namely altTTT-
  • the exemplary method and/or procedure may include receiving reportingConfigurations involving either SSB based events only, or CSI-RS based event only or both SSB based events and CSI-RS based events.
  • the exemplary method and/or procedure can include applying contents of alternativeTimetoTrigger in reportConfig of SSB events to the cells in altTTT-CellsToAddModList-SSBBased and apply contents of alternativeTimeToTrigger in reportConfig of CSI-RS events to the cells in altTTT-CellsToAddModList-CSI-RSBased.
  • the network can configure UEs to report RRM measurements based on a common list of altTTT-CellsToAddModList (referred to, e.g. , as altTTT-CellsToAddModListCommon ) that contains cells for which alternativeTimeToTrigger is applicable, independent of whether the cell quality determination is based on SSB or CSI- RS measurements.
  • the network can provide separate RS-pecific lists (referred to, e.g.
  • Table 2 Exemplary TTT configuration values corresponding to particular embodiments.
  • ASN. l code for an exemplary measObjectNR message providing the above configurations is shown below (relevant portions only). Such exemplary ASN. l code can be included, e.g. , in a 3GPP specification of functionality corresponding and/or related to these embodiments.
  • t e MeasObjectNR message can include information applicable for SSB-based or CSI-RS-based intra- or inter-frequency RRM measurements.
  • each of altTTT-CellsToAddModListCommon , altTTT-CellsToAddModList- SSBBased and altTTT-CellsToAddModList-CSI-RSBased are coded using altTTT- CellsToAddModList.
  • MeasOb jectNR : : SEQ UENCE ⁇
  • altTTT-CellsToRemoveList-SSBBased CelllndexList OPTIONAL altTTT-CellsToAddModList-SSBBased AltTTT-CellsToAddModList OPTIONAL
  • altTTT-CellsToRemoveList-CSI-RSBased CelllndexList OPTIONAL altTTT-CellsToAddModList-CSl-RSBased AltTTT-CellsToAddModList OPTIONAL
  • AltTTT-CellsToAddModList :: SEQUENCE (SIZE (L.maxCellMeas)) OF AltTTT- CellsToAddMod
  • all alternative TTT configurations can be specified in reportConfig messages, thereby removing the reporting configuration dependency on a measurement object contents, such as the measObjectNR messages described above.
  • the altTTT-CellsToAddModList and alternativeTimeToTrigger can be included in a reportConfigNR message.
  • An exemplary configuration for this embodiment is illustrated in Table 5.
  • Such embodiments facilitate additional flexibility for the network to specify and/or modify the particular cells for which alternative TTT values are applicable, e.g. , based on specific events.
  • the network can configure different cells as part of the altTTT- CellsToAddModList for different events.
  • ASN. l code for an exemplary reportConfigNR message providing the above configurations is shown below (relevant portions only).
  • Such exemplary ASN. l code can be included, e.g . , in a 3GPP specification of functionality corresponding and/or related to these embodiments. Although these embodiments are described in relation to 5G/NR, they are also applicable to 4G/LTE radio networks.
  • ReportConfigNR :: SEQUENCE ⁇
  • AltTTT-CellsToAddModList :: SEQUENCE (SIZE ..maxCellMeas)) OF AltTTT- CellsToAddMod
  • the network can configure UEs to report RRM measurements based on a plurality of lists altTTT-CellsToAddModList in a measObject message.
  • an arbitrary number of altTTT-CellsToAddModList can be provided in the measObject message and the reportConfig message can provide an indication of which list(s) is(are) applicable for the current reporting configuration.
  • ASN.1 code relevant portions only
  • Such exemplary ASN. l code can be included, e.g. , in a 3GPP specification of functionality corresponding and/or related to these embodiments.
  • the lists are provided in altTTT-CellsToAddModListOfLists.
  • the configuration can include an index (referred to, e.g. , as altTTT- CellsToAddModListlndex ) and a list of cells (referred to, e.g., as altTTT- CellsToAddModListValues) .
  • the maximum number of lists can be limited by maxNumOfList.
  • the value of maxNumOfList can be independently configured in the measObject , while in other embodiments, the value of maxNumOfList can be derived from maxCellMeas (e.g, equal to maxCellMeas or maxCellMeas 2 ).
  • the corresponding AltTTT-CellsToAddModListLndex provided in the reportConifg indicates the particular cell list for which alternative TTT is applicable.
  • the altTTT- CellsToRemoveListOfLists provides the UE with a list of integer cell-list indices (respectively CellListLndex) in the form of ListOfCellListLndex.
  • altTTT-CellsToAddModListLndex as configured in the altTTT- CellsToAddModListOfLists.
  • altTTT- CellsToAddModListOfLists and altTTT-CellsToRemoveListOfLists can be provided in reportConfigNR rather than measObjectNR, as shown below.
  • MeasOb jectNR : : SEQ UENCE ⁇
  • ListOfCellListlndex SEQUENCE (SIZE (1.. maxNumOfList)) OF CellListlndex
  • AltTTT-CellsToAddModList : : SEQ UENCE ⁇
  • AltTTT-CellsToAddModValues SEQUENCE (SIZE (L.maxCellMeas)) OF AltTTT- CellsToAddMod
  • Other exemplary embodiments can include multi-level and/or hierarchical configurations for cells or list-of-cells to be removed from a measurement object.
  • Such configurations can include a altTTT-CellsToRemoveListOfLists that can be specified as ListOfCelllndexListWithRef and encoded as a sequence of CelllndexListWithRef.
  • Each CelllndexListWithRef can include a listlndex (e.g., identifying a particular list) and a list of cells (listOfCells) to be removed from the identified list for a particular measurement. If all the cells are removed from the identified list, then the list can also be removed.
  • the reportConfigNR message for conveying this configuration will be similar to the one comprising the altTTT-CellsToAddModListOfLists discussed above.
  • ASN. l code (relevant portions only) is shown below for exemplary measObjectNR and reportConfigNR messages according to these exemplary embodiments.
  • Such exemplary ASN.l code can be included, e.g, in a 3 GPP specification of functionality corresponding and/or related to these embodiments.
  • AltTTT-CellsToAddModListOfLists :: SEQUENCE (SIZE (L. maxNumOfList)) OF AltTTT-
  • AltTTT-CellsToAddModList : : SEQ UENCE ⁇
  • AltTTT-CellsToAddModValues SEQUENCE (SIZE (L.maxCellMeas)) OF AltTTT- CellsToAddMod
  • the network can configure UEs to report RRM measurements based on a plurality of lists of altTTT-CellsToAddModList provided in measObject message for each RS type and, in a reportConfig message, an indication as to which list(s) is(are) applicable for the current reporting configuration.
  • ASN.1 code (relevant portions only) is shown below for exemplary measObjectNR and reportConfigNR messages according to these exemplary embodiments.
  • Such exemplary ASN. l code can be included, e.g. , in a 3GPP specification of functionality corresponding and/or related to these embodiments.
  • a plurality of RS-type-specific cell lists are identified in respective altTTT-CellsToAddModListOfSSBLists and altTTT-CellsToAddModListOfCSI- RSLists.
  • Each RS-type-specific list referenced by these lists is identified by an index ⁇ altTTT- CellsToAddModListlndex ) and a list of cells altTTT-CellsToAddModListValues) .
  • the altTTT-CellsToAddModListlndex provided in the reportConifg message indicates (by an index into the list-of-list) a cell list for which an alternative TTT is applicable.
  • the UE can evaluate this RS-type-specific list received in this manner while determining whether to utilize an SSB-based list or a CSI-RS-based list provided in the measObject message.
  • the measObjectNR message can include RS-type-specific lists altTTT- CellsToRemoveList-SSBBased and altTTT-CellsToRemoveList-CSI-RSBased.
  • Each of these RS-type-specific lists can comprise integer index values, each index identifying a list of cells for which an alternative TTT is not applicable.
  • These RS-type-specific lists correspond to the altTTT-CellsToAddModListlndex as configured in altTTT-CellsToAddModListOfSSBLists and altTTT-CellsToAddModListOfCSI-RSLists , respectively. Although shown in the ASN.
  • the altTTT-CellsToRemoveList-SSBBasedList , altTTT- CellsToRemoveList-CSI-RSBasedList, altTTT-CellsToAddModListOfSSBLists, and altTTT- CellsToAddModListOfCSI-RSLists can be provided in the reportConfig message in other exemplary embodiments.
  • MeasObjectNR SEQUENCE ⁇ altTTT-CellsToRemoveList-SSBBased ListOfCellListlndex OPTIONAL, altTTT-CellsToRemoveList-CSI-RSBased ListOfCellListlndex OPTIONAL, altTTT-CellsToAddModListOfSSBLists AltTTT-CellsToAddModListOfLists OPTIONAL, altTTT-CellsToAddModListOfCSI-RSLists AltTTT-CellsToAddModListOfLists OPTIONAL,
  • AltTTT-CellsToAddModListOfLists :: SEQUENCE (SIZE (L. maxNumOfList)) OF AltTTT- CellsToAddModLists
  • AltTTT-CellsToAddModLists : : SEQ UENCE ⁇
  • AltTTT-CellsToAddModValues SEQUENCE (SIZE (L.maxCellMeas)) OF AltTTT- CellsToAddMod
  • ReportConfigNR :: SEQUENCE ⁇
  • an RS-type-specific, multi-level and/or hierarchical configuration can be provided for cells or list-of-cells to be removed from the measurement object.
  • Such configurations can include respective altTTT-CellsToRemoveList-SSBBasedList and altTTT-CellsToRemoveList-CSI-RSBasedList that can be specified as ListOfCelllndexListWithRef and encoded as a sequence of CelllndexListWithRef.
  • Each CelllndexListWithRef can include a listlndex (e.g., identifying a particular list) and a list of cells (listOfCells) to be removed from from the identified list for a particular RS-type-specific measurement.
  • the reportConfig message of this embodiment can be similar to others discussed above.
  • ASN.1 code (relevant portions only) is shown below for exemplary measObjectNR and reportConfigNR messages according to these exemplary embodiments.
  • Such exemplary ASN. l code can be included, e.g. , in a 3GPP specification of functionality corresponding and/or related to these embodiments.
  • AltTTT-CellsToAddModListOfLists :: SEQUENCE (SIZE (1.. maxNumOfList)) OF AltTTT- CellsToAddModLists
  • AltTTT-CellsToAddModLists : : SEQ UENCE ⁇
  • ReportConfigNR :: SEQUENCE ⁇
  • LTE networks can be configured to broadcast so-called “white lists” and/or“black lists.”
  • the term“white list” can be used to refer to a list of neighbor cells and/or frequencies that UEs in the current serving cell (i.e., the cell broadcasting the respective lists) should consider for RRM measurements and cell re-selection.
  • the term“black list” can be used to refer to a list of neighbor cells and/or frequencies that UEs in the current serving cell should not consider for RRM measurements and cell re-selection.
  • Such lists can be provided, e.g. , in a measObject message. Morever, it is anticipated that 5G networks can broadcast similar lists, e.g. , in a measObjectNR message.
  • certain exemplary embodiments of the present disclosure can be used to specify a“white list” and/or a“black list” according to RS type, and/or to modify a“white list” and/or a“black list” by adding or removing cells (or lists of cells) according to RS type.
  • Such exemplary embodiments can apply any of the principles, structures, and/or techniques discussed above with respect to alternative TTT for measurement reporting, but in the context of“white lists” and“black lists” used for selection of cells for measurement and/or re-selection.
  • a wireless network such as the example wireless network illustrated in Figure 4.
  • the wireless network of Figure 4 only depicts network 406, network nodes 460 and 460b, and WDs 410, 410b, and 4l0c.
  • a wireless network can further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device.
  • network node 460 and wireless device (WD) 410 are depicted with additional detail.
  • the wireless network can provide communication and other types of services to one or more wireless devices to facilitate the wireless devices’ access to and/or use of the services provided by, or via, the wireless network.
  • the wireless network can comprise and/or interface with any type of communication, telecommunication, data, cellular, and/or radio network or other similar type of system.
  • the wireless network can be configured to operate according to specific standards or other types of predefined rules or procedures.
  • particular embodiments of the wireless network can implement communication standards, such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, or 5G standards; wireless local area network (WLAN) standards, such as the IEEE 802.1 1 standards; and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WIMAX), BLUETOOTH, Z-WAVE and/or ZIGBEE standards.
  • GSM Global System for Mobile Communications
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • WLAN wireless local area network
  • any other appropriate wireless communication standard such as the Worldwide Interoperability for Microwave Access (WIMAX), BLUETOOTH, Z
  • Network 406 can comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTNs), packet data networks, optical networks, wide- area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.
  • PSTNs public switched telephone networks
  • WANs wide-area networks
  • LANs local area networks
  • WLANs wireless local area networks
  • wired networks wireless networks, metropolitan area networks, and other networks to enable communication between devices.
  • Network node 460 and WD 410 comprise various components described in more detail below. These components work together in order to provide network node and/or wireless device functionality, such as providing wireless connections in a wireless network.
  • the wireless network can comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and/or any other components or systems that can facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.
  • network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the wireless network to enable and/or provide wireless access to the wireless device and/or to perform other functions (e.g ., administration) in the wireless network.
  • network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g, radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)).
  • APs access points
  • BSs base stations
  • eNBs evolved Node Bs
  • gNBs NR NodeBs
  • Base stations can be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and can then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations.
  • a base station can be a relay node or a relay donor node controlling a relay.
  • a network node can also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio.
  • RRUs remote radio units
  • RRHs Remote Radio Heads
  • Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio.
  • Parts of a distributed radio base station can also be referred to as nodes in a distributed antenna system (DAS).
  • DAS distributed antenna system
  • network nodes include multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), core network nodes (e.g, MSCs, MMEs), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g, E-SMLCs), and/or MDTs.
  • MSR multi-standard radio
  • RNCs radio network controllers
  • BSCs base station controllers
  • BTSs base transceiver stations
  • transmission points transmission nodes
  • MCEs multi-cell/multicast coordination entities
  • core network nodes e.g, MSCs, MMEs
  • O&M nodes e.g, OSS nodes, SON nodes, positioning nodes (e.g, E-SMLCs), and/or MDTs.
  • network nodes can represent any suitable device (or group of devices) capable, configured, arranged, and/or operable to enable and/or provide a wireless device with access to the wireless network or to provide some service to a wireless device that has accessed the wireless network.
  • network node 460 can include processing circuitry 470, device readable medium 480, interface 490, auxiliary equipment 484, power source 486, power circuitry 487, and antenna 462.
  • network node 460 illustrated in the example wireless network of Figure 4 can represent a device that can include the illustrated combination of hardware components, other embodiments can comprise network nodes with different combinations of components. It is to be understood that a network node can comprise any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods and/or procedures disclosed herein.
  • network node 460 can comprise multiple different physical components that make up a single illustrated component (e.g ., device readable medium 480 can comprise multiple separate hard drives as well as multiple RAM modules).
  • network node 460 can be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which can each have their own respective components.
  • network node 460 can comprise multiple separate components (e.g, BTS and BSC components)
  • one or more of the separate components can be shared among several network nodes.
  • a single RNC can control multiple NodeB s.
  • each unique NodeB and RNC pair can in some instances be considered a single separate network node.
  • network node 460 can be configured to support multiple radio access technologies (RATs).
  • RATs radio access technologies
  • Network node 460 can also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 460, such as, for example, GSM, WCDMA, LTE, NR, WiFi, or BLUETOOTH wireless technologies. These wireless technologies can be integrated into the same or different chip or set of chips and other components within network node 460.
  • Processing circuitry 470 can be configured to perform any determining, calculating, or similar operations (e.g, certain obtaining operations) described herein as being provided by a network node. These operations performed by processing circuitry 470 can include processing information obtained by processing circuitry 470 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • processing information obtained by processing circuitry 470 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • Processing circuitry 470 can comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node 460 components, such as device readable medium 480, network node 460 functionality.
  • processing circuitry 470 can execute instructions stored in device readable medium 480 or in memory within processing circuitry 470.
  • Such functionality can include providing any of the various wireless features, functions, or benefits discussed herein.
  • processing circuitry 470 can include a system on a chip (SOC).
  • SOC system on a chip
  • processing circuitry 470 can include one or more of radio frequency (RF) transceiver circuitry 472 and baseband processing circuitry 474.
  • radio frequency (RF) transceiver circuitry 472 and baseband processing circuitry 474 can be on separate chips (or sets of chips), boards, or units, such as radio units and digital units.
  • part or all of RF transceiver circuitry 472 and baseband processing circuitry 474 can be on the same chip or set of chips, boards, or units
  • processing circuitry 470 executing instructions stored on device readable medium 480 or memory within processing circuitry 470.
  • some or all of the functionality can be provided by processing circuitry 470 without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner.
  • processing circuitry 470 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 470 alone or to other components of network node 460, but are enjoyed by network node 460 as a whole, and/or by end users and the wireless network generally.
  • Device readable medium 480 can comprise any form of volatile or non-volatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer-executable memory devices that store information, data, and/or instructions that can be used by processing circuitry 470.
  • volatile or non-volatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or
  • Device readable medium 480 can store any suitable instructions, data or information, including a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 470 and, utilized by network node 460.
  • Device readable medium 480 can be used to store any calculations made by processing circuitry 470 and/or any data received via interface 490.
  • processing circuitry 470 and device readable medium 480 can be considered to be integrated.
  • Interface 490 is used in the wired or wireless communication of signalling and/or data between network node 460, network 406, and/or WDs 410.
  • interface 490 can comprise port(s)/terminal(s) 494 to send and receive data, for example to and from network 406 over a wired connection.
  • Interface 490 also can include radio front end circuitry 492 that can be coupled to, or in certain embodiments a part of, antenna 462.
  • Radio front end circuitry 492 can comprise filters 498 and amplifiers 496.
  • Radio front end circuitry 492 can be connected to antenna 462 and processing circuitry 470. Radio front end circuitry can be configured to condition signals communicated between antenna 462 and processing circuitry 470.
  • Radio front end circuitry 492 can receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 492 can convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 498 and/or amplifiers 496. The radio signal can then be transmitted via antenna 462. Similarly, when receiving data, antenna 462 can collect radio signals which are then converted into digital data by radio front end circuitry 492. The digital data can be passed to processing circuitry 470. In other embodiments, the interface can comprise different components and/or different combinations of components.
  • network node 460 may not include separate radio front end circuitry 492, instead, processing circuitry 470 can comprise radio front end circuitry and can be connected to antenna 462 without separate radio front end circuitry 492.
  • processing circuitry 470 can comprise radio front end circuitry and can be connected to antenna 462 without separate radio front end circuitry 492.
  • all or some of RF transceiver circuitry 472 can be considered a part of interface 490.
  • interface 490 can include one or more ports or terminals 494, radio front end circuitry 492, and RF transceiver circuitry 472, as part of a radio unit (not shown), and interface 490 can communicate with baseband processing circuitry 474, which is part of a digital unit (not shown).
  • Antenna 462 can include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals.
  • Antenna 462 can be coupled to radio front end circuitry 490 and can be any type of antenna capable of transmitting and receiving data and/or signals wirelessly.
  • antenna 462 can comprise one or more omni-directional, sector or panel antennas operable to transmit/receive radio signals between, for example, 2 GHz and 66 GHz.
  • An omni-directional antenna can be used to transmit/receive radio signals in any direction
  • a sector antenna can be used to transmit/receive radio signals from devices within a particular area
  • a panel antenna can be a line of sight antenna used to transmit/receive radio signals in a relatively straight line.
  • the use of more than one antenna can be referred to as MIMO.
  • antenna 462 can be separate from network node 460 and can be connectable to network node 460 through an interface or port.
  • Antenna 462, interface 490, and/or processing circuitry 470 can be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by a network node. Any information, data and/or signals can be received from a wireless device, another network node and/or any other network equipment. Similarly, antenna 462, interface 490, and/or processing circuitry 470 can be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and/or signals can be transmitted to a wireless device, another network node and/or any other network equipment.
  • Power circuitry 487 can comprise, or be coupled to, power management circuitry and can be configured to supply the components of network node 460 with power for performing the functionality described herein. Power circuitry 487 can receive power from power source 486. Power source 486 and/or power circuitry 487 can be configured to provide power to the various components of network node 460 in a form suitable for the respective components ( e.g ., at a voltage and current level needed for each respective component). Power source 486 can either be included in, or external to, power circuitry 487 and/or network node 460.
  • network node 460 can be connectable to an external power source (e.g., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry 487.
  • power source 486 can comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry 487. The battery can provide backup power should the external power source fail.
  • Other types of power sources such as photovoltaic devices, can also be used.
  • Alternative embodiments of network node 460 can include additional components beyond those shown in Figure 4 that can be responsible for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein.
  • network node 460 can include user interface equipment to allow and/or facilitate input of information into network node 460 and to allow and/or facilitate output of information from network node 460. This can allow and/or facilitate a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 460.
  • wireless device refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices.
  • the term WD can be used interchangeably herein with user equipment (UE).
  • Communicating wirelessly can involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air.
  • a WD can be configured to transmit and/or receive information without direct human interaction.
  • a WD can be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network.
  • Examples of a WD include, but are not limited to, a smart phone, a mobile phone, a cell phone, a voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless cameras, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mounted equipment (LME), a smart device, a wireless customer-premise equipment (CPE), a vehicle-mounted wireless terminal device, etc.
  • VoIP voice over IP
  • PDA personal digital assistant
  • LOE laptop-embedded equipment
  • LME laptop-mounted equipment
  • CPE wireless customer-premise equipment
  • a WD can support device-to-device (D2D) communication, for example by implementing a 3 GPP standard for sidelink communication, vehicle-to-vehicle (V2V), vehicle- to-infrastructure (V2I), vehicle-to-everything (V2X) and can in this case be referred to as a D2D communication device.
  • D2D device-to-device
  • V2V vehicle-to-vehicle
  • V2I vehicle- to-infrastructure
  • V2X vehicle-to-everything
  • a WD can represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another WD and/or a network node.
  • the WD can in this case be a machine-to-machine (M2M) device, which can in a 3GPP context be referred to as an MTC device.
  • M2M machine-to-machine
  • the WD can be a UE implementing the 3 GPP narrow band internet of things (NB-IoT) standard.
  • NB-IoT narrow band internet of things
  • machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances (e.g . refrigerators, televisions, etc.) personal wearables (e.g., watches, fitness trackers, etc.).
  • a WD can represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.
  • a WD as described above can represent the endpoint of a wireless connection, in which case the device can be referred to as a wireless terminal. Furthermore, a WD as described above can be mobile, in which case it can also be referred to as a mobile device or a mobile terminal.
  • wireless device 410 can include antenna 41 1, interface 414, processing circuitry 420, device readable medium 430, user interface equipment 432, auxiliary equipment 434, power source 436 and power circuitry 437.
  • WD 410 can include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD 410, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WIMAX, or BLUETOOTH wireless technologies, just to mention a few. These wireless technologies can be integrated into the same or different chips or set of chips as other components within WD 410.
  • Antenna 41 1 can include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface 414.
  • antenna 41 1 can be separate from WD 410 and be connectable to WD 410 through an interface or port.
  • Antenna 41 1, interface 414, and/or processing circuitry 420 can be configured to perform any receiving or transmitting operations described herein as being performed by a WD. Any information, data and/or signals can be received from a network node and/or another WD.
  • radio front end circuitry and/or antenna 41 1 can be considered an interface.
  • interface 414 can comprise radio front end circuitry 412 and antenna 41 1.
  • Radio front end circuitry 412 comprise one or more filters 418 and amplifiers 416.
  • Radio front end circuitry 414 is connected to antenna 41 1 and processing circuitry 420, and can be configured to condition signals communicated between antenna 41 1 and processing circuitry 420.
  • Radio front end circuitry 412 can be coupled to or a part of antenna 41 1.
  • WD 410 may not include separate radio front end circuitry 412; rather, processing circuitry 420 can comprise radio front end circuitry and can be connected to antenna 41 1.
  • some or all of RF transceiver circuitry 422 can be considered a part of interface 414.
  • Radio front end circuitry 412 can receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 412 can convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 418 and/or amplifiers 416. The radio signal can then be transmitted via antenna 41 1. Similarly, when receiving data, antenna 41 1 can collect radio signals which are then converted into digital data by radio front end circuitry 412. The digital data can be passed to processing circuitry 420. In other embodiments, the interface can comprise different components and/or different combinations of components.
  • Processing circuitry 420 can comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and/or encoded logic operable to provide, either alone or in conjunction with other WD 410 components, such as device readable medium 430, WD 410 functionality.
  • Such functionality can include providing any of the various wireless features or benefits discussed herein.
  • processing circuitry 420 can execute instructions stored in device readable medium 430 or in memory within processing circuitry 420 to provide the functionality disclosed herein.
  • processing circuitry 420 can include one or more of RF transceiver circuitry 422, baseband processing circuitry 424, and application processing circuitry 426.
  • the processing circuitry can comprise different components and/or different combinations of components.
  • processing circuitry 420 of WD 410 can comprise a SOC.
  • RF transceiver circuitry 422, baseband processing circuitry 424, and application processing circuitry 426 can be on separate chips or sets of chips.
  • part or all of baseband processing circuitry 424 and application processing circuitry 426 can be combined into one chip or set of chips, and RF transceiver circuitry 422 can be on a separate chip or set of chips.
  • part or all of RF transceiver circuitry 422 and baseband processing circuitry 424 can be on the same chip or set of chips, and application processing circuitry 426 can be on a separate chip or set of chips.
  • part or all of RF transceiver circuitry 422, baseband processing circuitry 424, and application processing circuitry 426 can be combined in the same chip or set of chips.
  • RF transceiver circuitry 422 can be a part of interface 414.
  • RF transceiver circuitry 422 can condition RF signals for processing circuitry 420.
  • processing circuitry 420 executing instructions stored on device readable medium 430, which in certain embodiments can be a computer-readable storage medium.
  • some or all of the functionality can be provided by processing circuitry 420 without executing instructions stored on a separate or discrete device readable storage medium, such as in a hard-wired manner.
  • processing circuitry 420 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 420 alone or to other components of WD 410, but are enjoyed by WD 410 as a whole, and/or by end users and the wireless network generally.
  • Processing circuitry 420 can be configured to perform any determining, calculating, or similar operations (e.g . , certain obtaining operations) described herein as being performed by a WD. These operations, as performed by processing circuitry 420, can include processing information obtained by processing circuitry 420 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD 410, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • Device readable medium 430 can be operable to store a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 420.
  • Device readable medium 430 can include computer memory (e.g., Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (e.g, a hard disk), removable storage media (e.g, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non- transitory device readable and/or computer executable memory devices that store information, data, and/or instructions that can be used by processing circuitry 420.
  • processing circuitry 420 and device readable medium 430 can be considered to be integrated.
  • User interface equipment 432 can include components that allow and/or facilitate a human user to interact with WD 410. Such interaction can be of many forms, such as visual, audial, tactile, etc. User interface equipment 432 can be operable to produce output to the user and to allow and/or facilitate the user to provide input to WD 410.
  • the type of interaction can vary depending on the type of user interface equipment 432 installed in WD 410. For example, if WD 410 is a smart phone, the interaction can be via a touch screen; if WD 410 is a smart meter, the interaction can be through a screen that provides usage ( e.g . , the number of gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected).
  • User interface equipment 432 can include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment 432 can be configured to allow and/or facilitate input of information into WD 410, and is connected to processing circuitry 420 to allow and/or facilitate processing circuitry 420 to process the input information. User interface equipment 432 can include, for example, a microphone, a proximity or other sensor, keys/buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface equipment 432 can also be configured to allow and/or facilitate output of information from WD 410, and to allow and/or facilitate processing circuitry 420 to output information from WD 410.
  • User interface equipment 432 can include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits, of user interface equipment 432, WD 410 can communicate with end users and/or the wireless network, and allow and/or facilitate them to benefit from the functionality described herein.
  • Auxiliary equipment 434 is operable to provide more specific functionality which may not be generally performed by WDs. This can comprise specialized sensors for doing measurements for various purposes, interfaces for additional types of communication such as wired communications etc. The inclusion and type of components of auxiliary equipment 434 can vary depending on the embodiment and/or scenario.
  • Power source 436 can, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g, an electricity outlet), photovoltaic devices or power cells, can also be used.
  • WD 410 can further comprise power circuitry 437 for delivering power from power source 436 to the various parts of WD 410 which need power from power source 436 to carry out any functionality described or indicated herein.
  • Power circuitry 437 can in certain embodiments comprise power management circuitry.
  • Power circuitry 437 can additionally or alternatively be operable to receive power from an external power source; in which case WD 410 can be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable.
  • Power circuitry 437 can also in certain embodiments be operable to deliver power from an external power source to power source 436. This can be, for example, for the charging of power source 436. Power circuitry 437 can perform any converting or other modification to the power from power source 436 to make it suitable for supply to the respective components of WD 410.
  • FIG 5 illustrates an exemplary method and/or procedure 500 performed in a wireless device (e.g ., a user equipment (UE) or component thereof), according to various exemplary embodiments of the present disclosure.
  • processing circuitry 420 of wireless device 410 shown in Figure 4 can be configured to perform operations of the exemplary method and/or procedure 500, e.g., in cooperation with one or more other components of wireless device 410.
  • the exemplary method and/or procedure is illustrated in Figure 5 by blocks in a particular order, this order is exemplary and the operations corresponding to the blocks can be performed in different orders, and can be combined and/or divided into blocks having different functionality than shown in Figure 5.
  • the exemplary method and/or procedure shown in Figure 5 can be complimentary to the exemplary method and/or procedure illustrated in Figure 6.
  • the exemplary methods and/or procedures shown in Figures 5 and 6 are capable of being used cooperatively to provide the benefits, advantages, and/or solutions to problems described hereinabove.
  • the exemplary method and/or procedure can include block 502 where the wireless device can receive, from a serving base station, a measurement object message identifying: a plurality of neighbor cells on which to perform measurements; and one or more subsets of the plurality of neighbor cells, each subset corresponding to one of a plurality of RS types available to be measured.
  • the exemplary method and/or procedure can include block 504, where the wireless device can receive, from the serving base station, a reporting configuration message identifying one or more reporting events, each reporting event corresponding to measurements of a particular one of the plurality of RS types.
  • the exemplary method and/or procedure can include block 506, where the wireless device can determine, based on the received measurement object and reporting configuration messages, reporting events for each of the one or more subsets of the plurality of neighbor cells.
  • the exemplary method and/or procedure can include block 508, the wireless device can report, according to one of the determined reporting events, measurements made on the corresponding subset of neighbor cells based on the corresponding RS type.
  • the measurement object message can include an alternate TTT associated with each of the one of more subsets of the neighbor cells, and determining reporting events can comprise assigning the alternate TTT for reporting measurements made on the associated subset of neighbor cells based on the corresponding RS type.
  • the measurement object messages can comprise a plurality of lists of neighbor cells associated with an alternate TTT, the plurality of lists comprising: a first list of neighbor cells associated with th alternate TTT for measurements based on all RS types; and one of more futher lists of neighbor cells, each further list associated with the alternate TTT for measurements based on a particular RS type.
  • at least a portion of the further lists can identify neighbor cells to be added to the first list for measurements based on the associated RS type.
  • at least a portion of the further lists can identify neighbor cells to be removed from the first list for measurements based on the associated RS type.
  • the measurement object message can include a plurality of lists of neighbor cells associated with an alternate time-to-trigger TTT, each list further associated with a unique index; and the report configuration message can comprise one or more indicators, each indicator identifying one of the plurality of lists according to the associated index value.
  • the plurality of lists of neighbor cells can comprise a first plurality of lists corresponding to a first RS type and a second plurality of lists corresponding to a second RS type, each list further associated with an index value unique to the particular plurality; and each indicator can identify a list of the first plurality or the second plurality according to the associated index value.
  • the measurement object message can comprise a plurality of lists of neighbor cells, the plurality of lists comprising a first plurality of lists of neighbor cells to be associated with an alternate TTT and a second plurality of lists of neighbor cells not to be associated with the alternate TTT, each list further associated with an index value unique to the particular plurality.
  • the report configuration message can comprise a list of neighbor cells associated with the alternate TTT and one or more indicators, each indicator identifying one of the plurality of lists according to the associated index value.
  • each of the first and second pluralities of lists is further associated with a particular RS type, each list further associated with an index value unique to the particular plurality and the particular RS type.
  • the wireless device can determine the reporting events by assigning the alternate TTT for reporting measurements made on a determined list of neighbor cells comprising the list of neighbor cells associated with the alternate TTT and lists of neighbor cells of the first plurality identified by the one or more indicators, wherein the determined list excludes lists of neighbor cells of the second plurality identified by the one or more indicators.
  • FIG. 6 illustrates an exemplary method and/or procedure 600 performed in a base station (e.g., eNB or gNB), in accordance with particular exemplary embodiments of the present disclosure.
  • processing circuitry 470 of network node 460 shown in Figure 4 can be configured to perform operations of the exemplary method and/or procedure 600, e.g., in cooperation with one or more other components of network node 460.
  • the exemplary method and/or procedure is illustrated in Figure 6 by blocks in a particular order, this order is exemplary and the operations corresponding to the blocks can be performed in different orders, and can be combined and/or divided into blocks having different functionality than shown in Figure 6.
  • the exemplary method and/or procedure shown in Figure 6 can be complimentary to the exemplary method and/or procedure illustrated in Figure 5.
  • the exemplary methods and/or procedures shown in Figures 5 and 6 are capable of being used cooperatively to provide the benefits, advantages, and/or solutions to problems described hereinabove.
  • the exemplary method and/or procedure can include block 602, where the base station can transmit, to a wireless device, a measurement object message identifying: a plurality of neighbor cells on which to perform measurements; and one or more subsets of the plurality of neighbor cells, each subset corresponding to one of a plurality of RS types available to be measured.
  • the exemplary method and/or procedure can also include block 604, whyere the base station can transmit, to a wireless device, a reporting configuration message identifying one or more reporting events, each reporting event corresponding to measurements of a particular one of the plurality of RS types.
  • the exemplary method and/or procedure can also include block 606, the base station can receive, from the wireless device, a measurement report corresponding to one of the reporting events, the measurement report comprising measurements made on one of the subset of neighbor cells based on the corresponding RS type
  • the measurement object message can include an alternate TTT associated with each of the one of more subsets of the neighbor cells, and the measurements comprising the measurement report are reported based on the alternate TTT.
  • the measurement object message can comprise a plurality of lists of neighbor cells associated with an alternate TTT, the plurality of lists comprising: a first list of neighbor cells associated with th alternate TTT for measurements based on all RS types; and one of more futher lists of neighbor cells, each further list associated with the alternate TTT for measurements based on a particular RS type.
  • at least a portion of the further lists can identify neighbor cells to be added to the first list for measurements based on the associated RS type.
  • at least a portion of the further lists can identify neighbor cells to be removed from the first list for measurements based on the associated RS type.
  • the measurement object message can include a plurality of lists of neighbor cells associated with an alternate TTT, each list further associated with a unique index; and the report configuration message can comprise one or more indicators, each indicator identifying one of the plurality of lists according to the associated index value.
  • the plurality of lists of neighbor cells can comprise a first plurality of lists corresponding to a first RS type and a second plurality of lists corresponding to a second RS type, each list further associated with an index value unique to the particular plurality; and each indicator can identify a list of the first plurality or the second plurality according to the associated index value.
  • the measurement object message can comprise a plurality of lists of neighbor cells, the plurality of lists comprising a first plurality of lists of neighbor cells to be associated with an alternate TTT and a second plurality of lists of neighbor cells not to be associated with the alternate TTT, each list further associated with an index value unique to the particular plurality.
  • the report configuration message can comprise a list of neighbor cells associated with the alternate TTT and one or more indicators, each indicator identifying one of the plurality of lists according to the associated index value.
  • each of the first and second pluralities of lists is further associated with a particular RS type, each list further associated with an index value unique to the particular plurality and the particular RS type.
  • the measurements comprising the measurement report can include measurements made on a determined list of neighbor cells comprising the list of neighbor cells associated with the alternate TTT and lists of neighbor cells of the first plurality identified by the one or more indicators, wherein the determined list excludes lists of neighbor cells of the second plurality identified by the one or more indicators.
  • Figure 7 illustrates one embodiment of a UE in accordance with various aspects described herein.
  • a user equipment or UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device.
  • a UE can represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g ., a smart sprinkler controller).
  • a UE can represent a device that is not intended for sale to, or operation by, an end user but which can be associated with or operated for the benefit of a user (e.g., a smart power meter).
  • UE 700 can be any UE identified by the 3 rd Generation Partnership Project (3GPP), including a NB-IoT UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.
  • UE 700 as illustrated in Figure 7, is one example of a WD configured for communication in accordance with one or more communication standards promulgated by the 3 rd Generation Partnership Project (3GPP), such as 3GPP’s GSM, UMTS, LTE, and/or 5G standards.
  • 3GPP 3 rd Generation Partnership Project
  • the term WD and UE can be used interchangeable. Accordingly, although Figure 7 is a UE, the components discussed herein are equally applicable to a WD, such as WD 410, and vice-versa.
  • UE 700 can include processing circuitry 701 that is operatively coupled to input/output interface 705, radio frequency (RF) interface 709, network connection interface 711, memory 715 including random access memory (RAM) 717, read-only memory (ROM) 719, and storage medium 721 or the like, communication subsystem 731, power source 733, and/or any other component, or any combination thereof.
  • Storage medium 721 can include operating system 723, application program 725, and data 727. In other embodiments, storage medium 721 can include other similar types of information.
  • Certain UEs can utilize all of the components shown in Figure 7, or only a subset of the components. The level of integration between the components can vary from one UE to another UE. Further, certain UEs can contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
  • processing circuitry 701 can be configured to process computer instructions and data.
  • Processing circuitry 701 can be configured to implement any sequential state machine operative to execute machine instructions stored as machine-readable computer programs in the memory, such as one or more hardware-implemented state machines (e.g . , in discrete logic, FPGA, ASIC, etc.); programmable logic together with appropriate firmware; one or more stored program, general-purpose processors, such as a microprocessor or Digital Signal Processor (DSP), together with appropriate software; or any combination of the above.
  • the processing circuitry 701 can include two central processing units (CPUs). Data can be information in a form suitable for use by a computer.
  • input/output interface 705 can be configured to provide a communication interface to an input device, output device, or input and output device.
  • UE 700 can be configured to use an output device via input/output interface 705.
  • An output device can use the same type of interface port as an input device.
  • a USB port can be used to provide input to and output from UE 700.
  • the output device can be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof.
  • UE 700 can be configured to use an input device via input/output interface 705 to allow and/or facilitate a user to capture information into UE 700.
  • the input device can include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like.
  • the presence- sensitive display can include a capacitive or resistive touch sensor to sense input from a user.
  • a sensor can be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another like sensor, or any combination thereof.
  • the input device can be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.
  • RF interface 709 can be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna.
  • Network connection interface 71 1 can be configured to provide a communication interface to network 743a.
  • Network 743a can encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof.
  • network 743a can comprise a Wi-Fi network.
  • Network connection interface 71 1 can be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, TCP/IP, SONET, ATM, or the like.
  • Network connection interface 71 1 can implement receiver and transmitter functionality appropriate to the communication network links ( e.g . , optical, electrical, and the like). The transmitter and receiver functions can share circuit components, software or firmware, or alternatively can be implemented separately.
  • RAM 717 can be configured to interface via bus 702 to processing circuitry 701 to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers.
  • ROM 719 can be configured to provide computer instructions or data to processing circuitry 701.
  • ROM 719 can be configured to store invariant low-level system code or data for basic system functions such as basic input and output (I/O), startup, or reception of keystrokes from a keyboard that are stored in a non-volatile memory.
  • Storage medium 721 can be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives.
  • storage medium 721 can be configured to include operating system 723, application program 725 such as a web browser application, a widget or gadget engine or another application, and data file 727.
  • Storage medium 721 can store, for use by UE 700, any of a variety of various operating systems or combinations of operating systems.
  • Storage medium 721 can be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), floppy disk drive, flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro- DIMM SDRAM, smartcard memory such as a subscriber identity module or a removable user identity (SIM/RUIM) module, other memory, or any combination thereof.
  • RAID redundant array of independent disks
  • HD-DVD high-density digital versatile disc
  • HDDS holographic digital data storage
  • DIMM synchronous dynamic random access memory
  • SIM/RUIM removable user identity
  • Storage medium 721 can allow and/or facilitate UE 700 to access computer-executable instructions, application programs or the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data.
  • An article of manufacture, such as one utilizing a communication system can be tangibly embodied in storage medium 721, which can comprise a device readable medium.
  • processing circuitry 701 can be configured to communicate with network 743b using communication subsystem 731.
  • Network 743a and network 743b can be the same network or networks or different network or networks.
  • Communication subsystem 731 can be configured to include one or more transceivers used to communicate with network 743b.
  • communication subsystem 731 can be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another WD, UE, or base station of a radio access network (RAN) according to one or more communication protocols, such as IEEE 802.7, CDMA, WCDMA, GSM, LTE, ETTRAN, WiMax, or the like.
  • Each transceiver can include transmitter 733 and/or receiver 735 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links ( e.g . , frequency allocations and the like). Further, transmitter 733 and receiver 735 of each transceiver can share circuit components, software or firmware, or alternatively can be implemented separately.
  • the communication functions of communication subsystem 731 can include data communication, voice communication, multimedia communication, short-range communications such as BLEETOOTH technology, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof.
  • communication subsystem 731 can include cellular communication, Wi-Fi communication, BLEETOOTH communication, and GPS communication.
  • Network 743b can encompass wired and/or wireless networks such as a local- area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof.
  • network 743b can be a cellular network, a Wi-Fi network, and/or a near-field network.
  • Power source 713 can be configured to provide alternating current (AC) or direct current (DC) power to components of EE 700.
  • communication subsystem 731 can be configured to include any of the components described herein.
  • processing circuitry 701 can be configured to communicate with any of such components over bus 702.
  • any of such components can be represented by program instructions stored in memory that when executed by processing circuitry 701 perform the corresponding functions described herein.
  • the functionality of any of such components can be partitioned between processing circuitry 701 and communication subsystem 731.
  • the non-computationally intensive functions of any of such components can be implemented in software or firmware and the computationally intensive functions can be implemented in hardware.
  • FIG 8 is a schematic block diagram illustrating a virtualization environment 800 in which functions implemented by some embodiments can be virtualized.
  • virtualizing means creating virtual versions of apparatuses or devices which can include virtualizing hardware platforms, storage devices and networking resources.
  • virtualization can be applied to a node (e.g ., a virtualized base station or a virtualized radio access node) or to a device (e.g., a UE, a wireless device or any other type of communication device) or components thereof and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components (e.g, via one or more applications, components, functions, virtual machines or containers executing on one or more physical processing nodes in one or more networks).
  • some or all of the functions described herein can be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 800 hosted by one or more of hardware nodes 830. Further, in embodiments in which the virtual node is not a radio access node or does not require radio connectivity (e.g, a core network node), then the network node can be entirely virtualized.
  • the functions can be implemented by one or more applications 820 (which can alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operative to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.
  • Applications 820 are run in virtualization environment 800 which provides hardware 830 comprising processing circuitry 860 and memory 890.
  • Memory 890 contains instructions 895 executable by processing circuitry 860 whereby application 820 is operative to provide one or more of the features, benefits, and/or functions disclosed herein.
  • Virtualization environment 800 can comprise general-purpose or special-purpose network hardware devices 830 comprising a set of one or more processors or processing circuitry 860, which can be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors.
  • processors or processing circuitry 860 can be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors.
  • Each hardware device can comprise memory 890-1 which can be non-persistent memory for temporarily storing instructions 895 or software executed by processing circuitry 860.
  • Each hardware device can comprise one or more network interface controllers (NICs) 870, also known as network interface cards, which include physical network interface 880.
  • NICs network interface controllers
  • Each hardware device can also include non-transitory, persistent, machine-readable storage media 890-2 having stored therein software 895 and/or instructions executable by processing circuitry 860.
  • Software 895 can include any type of software including software for instantiating one or more virtualization layers 850 (also referred to as hypervisors), software to execute virtual machines 840 as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.
  • Virtual machines 840 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and can be run by a corresponding virtualization layer 850 or hypervisor. Different embodiments of the instance of virtual appliance 820 can be implemented on one or more of virtual machines 840, and the implementations can be made in different ways.
  • processing circuitry 860 executes software 895 to instantiate the hypervisor or virtualization layer 850, which can sometimes be referred to as a virtual machine monitor (VMM).
  • VMM virtual machine monitor
  • Virtualization layer 850 can present a virtual operating platform that appears like networking hardware to virtual machine 840.
  • hardware 830 can be a standalone network node with generic or specific components.
  • Hardware 830 can comprise antenna 8225 and can implement some functions via virtualization.
  • hardware 830 can be part of a larger cluster of hardware (e.g . such as in a data center or customer premise equipment (CPE)) where many hardware nodes work together and are managed via management and orchestration (MANO) 8100, which, among others, oversees lifecycle management of applications 820.
  • CPE customer premise equipment
  • NFV network function virtualization
  • NFV network function virtualization
  • virtual machine 840 can be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine.
  • Each of virtual machines 840, and that part of hardware 830 that executes that virtual machine be it hardware dedicated to that virtual machine and/or hardware shared by that virtual machine with others of the virtual machines 840, forms a separate virtual network elements (VNE).
  • VNE virtual network elements
  • VNF Virtual Network Function
  • one or more radio units 8200 that each include one or more transmitters 8220 and one or more receivers 8210 can be coupled to one or more antennas 8225.
  • Radio units 8200 can communicate directly with hardware nodes 830 via one or more appropriate network interfaces and can be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.
  • control system 8230 which can alternatively be used for communication between the hardware nodes 830 and radio units 8200.
  • a communication system can include telecommunication network 910, such as a 3 GPP -type cellular network, which can comprise access network 91 1, such as a radio access network, and core network 914.
  • Access network 91 1 can comprise a plurality of base stations 9l2a, 9l2b, 9l2c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 913a, 913b, 913c.
  • Each base station 912a, 912b, 912c is connectable to core network 914 over a wired or wireless connection 915.
  • a first EGE 991 located in coverage area 913c can be configured to wirelessly connect to, or be paged by, the corresponding base station 912c.
  • a second EGE 992 in coverage area 913a is wirelessly connectable to the corresponding base station 9l2a. While a plurality of EIEs 991, 992 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole EGE is in the coverage area or where a sole EGE is connecting to the corresponding base station 912.
  • Telecommunication network 910 is itself connected to host computer 930, which can be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm.
  • Host computer 930 can be under the ownership or control of a service provider, or can be operated by the service provider or on behalf of the service provider.
  • Connections 921 and 922 between telecommunication network 910 and host computer 930 can extend directly from core network 914 to host computer 930 or can go via an optional intermediate network 920.
  • Intermediate network 920 can be one of, or a combination of more than one of, a public, private or hosted network; intermediate network 920, if any, can be a backbone network or the Internet; in particular, intermediate network 920 can comprise two or more sub-networks (not shown).
  • the communication system of Figure 9 as a whole can facilitate connectivity between the connected UEs 991, 992 and host computer 930.
  • the connectivity can be described as an over-the-top (OTT) connection 950.
  • Host computer 930 and the connected UEs 991, 992 are configured to communicate data and/or signaling via OTT connection 950, using access network 911, core network 914, any intermediate network 920 and possible further infrastructure (not shown) as intermediaries.
  • OTT connection 950 can be transparent in the sense that the participating communication devices through which OTT connection 950 passes are unaware of routing of uplink and downlink communications.
  • base station 912 may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer 930 to be forwarded ( e.g ., handed over) to a connected UE 991. Similarly, base station 912 need not be aware of the future routing of an outgoing uplink communication originating from the UE 991 towards the host computer 930.
  • host computer 1010 can comprise hardware 1015 including communication interface 1016 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system 1000.
  • Host computer 1010 further can comprise processing circuitry 1018, which can have storage and/or processing capabilities.
  • processing circuitry 1018 can comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • Host computer 1010 further can comprise software 1011, which is stored in or accessible by host computer 1010 and executable by processing circuitry 1018.
  • Software 1011 can include host application 1012.
  • Host application 1012 can be operable to provide a service to a remote user, such as UE 1030 connecting via OTT connection 1050 terminating at UE 1030 and host computer 1010. In providing the service to the remote user, host application 1012 can provide user data which is transmitted using OTT connection 1050.
  • Communication system 1000 can also include base station 1020 provided in a telecommunication system and comprising hardware 1025 enabling it to communicate with host computer 1010 and with EE 1030.
  • Hardware 1025 can include communication interface 1026 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system 1000, as well as radio interface 1027 for setting up and maintaining at least wireless connection 1070 with EE 1030 located in a coverage area (not shown in Figure 10) served by base station 1020.
  • Communication interface 1026 can be configured to facilitate connection 1060 to host computer 1010. Connection 1060 can be direct or it can pass through a core network (not shown in Figure 10) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system.
  • hardware 1025 of base station 1020 can also include processing circuitry 1028, which can comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • Base station 1020 further includes software 1021 stored internally or accessible via an external connection.
  • Communication system 1000 can also include EE 1030 already referred to. Its hardware 1035 can include radio interface 1037 configured to set up and maintain wireless connection 1070 with a base station serving a coverage area in which EE 1030 is currently located. Hardware 1035 of EE 1030 can also include processing circuitry 1038, which can comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. EE 1030 further can comprise software 1031, which is stored in or accessible by EE 1030 and executable by processing circuitry 1038. Software 1031 can include client application 1032. Client application 1032 can be operable to provide a service to a human or non-human user via EE 1030, with the support of host computer 1010.
  • an executing host application 1012 can communicate with the executing client application 1032 via OTT connection 1050 terminating at EE 1030 and host computer 1010.
  • client application 1032 can receive request data from host application 1012 and provide user data in response to the request data.
  • OTT connection 1050 can transfer both the request data and the user data.
  • Client application 1032 can interact with the user to generate the user data that it provides.
  • host computer 1010, base station 1020 and UE 1030 illustrated in Figure 10 can be similar or identical to host computer 930, one of base stations 912a, 912b, 912c and one ofUEs 991, 992 of Figure 9, respectively.
  • the inner workings of these entities can be as shown in Figure 10 and independently, the surrounding network topology can be that of Figure 9.
  • OTT connection 1050 has been drawn abstractly to illustrate the communication between host computer 1010 and UE 1030 via base station 1020, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • Network infrastructure can determine the routing, which it can be configured to hide from UE 1030 or from the service provider operating host computer 1010, or both. While OTT connection 1050 is active, the network infrastructure can further take decisions by which it dynamically changes the routing (e.g ., on the basis of load balancing consideration or reconfiguration of the network).
  • Wireless connection 1070 between UE 1030 and base station 1020 is in accordance with the teachings of the embodiments described throughout this disclosure.
  • One or more of the various embodiments improve the performance of OTT services provided to UE 1030 using OTT connection 1050, in which wireless connection 1070 forms the last segment.
  • the exemplary embodiments disclosed herein improve flexibility for the network to configure various TTT (and alternate TTT) values for reporting measurements of signals in neighbor cells, according to characteristics of individual cells and individual reference signals, including the per-cell beamforming used to transmit each type of reference signal.
  • TTT and alternate TTT
  • Such advantages can facilitate more timely design, implementation, and deployment of 5G/NR solutions.
  • More generally, such embodiments provide more robust mobility for wireless devices, which can facilitate improvements in capacitiy, throughput, latency, etc. that are promised by multi-antenna beamforming/spatial multiplexing solutions for 5G/NR.
  • a measurement procedure can be provided for the purpose of monitoring data rate, latency and other network operational aspects on which the one or more embodiments improve.
  • the measurement procedure and/or the network functionality for reconfiguring OTT connection 1050 can be implemented in software 1011 and hardware 1015 of host computer 1010 or in software 1031 and hardware 1035 of UE 1030, or both.
  • sensors can be deployed in or in association with communication devices through which OTT connection 1050 passes; the sensors can participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 1011, 1031 can compute or estimate the monitored quantities.
  • the reconfiguring of OTT connection 1050 can include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect base station 1020, and it can be unknown or imperceptible to base station 1020. Such procedures and functionalities can be known and practiced in the art.
  • measurements can involve proprietary UE signaling facilitating host computer lOlO’s measurements of throughput, propagation times, latency and the like.
  • the measurements can be implemented in that software 1011 and 1031 causes messages to be transmitted, in particular empty or‘dummy’ messages, using OTT connection 1050 while it monitors propagation times, errors etc.
  • FIG 11 is a flowchart illustrating an exemplary method and/or procedure implemented in a communication system, in accordance with various embodiments.
  • the communication system can include a host computer, a base station and a UE which, in some exemplary embodiments, can be those described with reference to Figures 4 and 7-10. For simplicity of the present disclosure, only drawing references to Figure 11 will be included in this section.
  • the host computer provides user data.
  • substep 1111 (which can be optional) of step 1110, the host computer provides the user data by executing a host application.
  • the host computer initiates a transmission carrying the user data to the UE.
  • step 1130 the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure.
  • step 1140 the UE executes a client application associated with the host application executed by the host computer.
  • FIG. 12 is a flowchart illustrating an exemplary method and/or procedure implemented in a communication system, in accordance with various embodiments.
  • the communication system can include a host computer, a base station and a UE which can be those described with reference to Figures 4 and 7-10. For simplicity of the present disclosure, only drawing references to Figure 12 will be included in this section.
  • the host computer provides user data.
  • the host computer provides the user data by executing a host application.
  • the host computer initiates a transmission carrying the user data to the UE.
  • the transmission can pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure.
  • step 1230 (which can be optional), the UE receives the user data carried in the transmission.
  • FIG. 13 is a flowchart illustrating an exemplary method and/or procedure implemented in a communication system, in accordance with various embodiments.
  • the communication system can include a host computer, a base station and a UE which can be those described with reference to Figures 4 and 7-10. For simplicity of the present disclosure, only drawing references to Figure 13 will be included in this section.
  • step 1310 the UE receives input data provided by the host computer. Additionally or alternatively, in step 1320, the UE provides user data.
  • substep 1321 (which can be optional) of step 1320, the UE provides the user data by executing a client application.
  • substep 131 1 (which can be optional) of step 1310, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer.
  • the executed client application can further consider user input received from the user.
  • the UE initiates, in substep 1330 (which can be optional), transmission of the user data to the host computer.
  • step 1340 of the method the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.
  • FIG 14 is a flowchart illustrating an exemplary method and/or procedure implemented in a communication system, in accordance with various embodiments.
  • the communication system can include a host computer, a base station and a UE which can be those described with reference to Figures 4 and 7-10.
  • the base station receives user data from the UE.
  • the base station initiates transmission of the received user data to the host computer.
  • the host computer receives the user data carried in the transmission initiated by the base station.
  • the term unit can have conventional meaning in the field of electronics, electrical devices and/or electronic devices and can include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.
  • a method performed by a wireless device for reporting measurements made on signals from neighbor cells in a wireless network comprising:
  • identifying i. a plurality of neighbor cells on which to perform measurements; and ii. one or more subsets of the plurality of neighbor cells, each subset corresponding to one of a plurality of reference signal (RS) types available to be measured;
  • RS reference signal
  • configuration messages reporting events for each of the one or more subsets of the plurality of neighbor cells.
  • the measurement object message comprises an alternate time-to-trigger (TTT) associated with each of the one of more subsets of the neighbor cells;
  • - determing reporting events comprises assigning the alternate TTT for
  • the measurement object messages comprises a plurality of lists of neighbor cells associated with an alternate time-to-trigger (TTT), the plurality of lists comprising:
  • the measurement object message comprises a plurality of lists of neighbor cells associated with an alternate time-to-trigger (TTT), each list further associated with a unique index; and
  • TTT alternate time-to-trigger
  • the report configuration message comprises one or more indicators, each
  • the plurality of lists of neighbor cells comprises a first plurality of lists
  • each indicator identifies a list of the first plurality or the second plurality
  • the measurement object message comprises a plurality of lists of neighbor cells, the plurality of lists comprising a first plurality of lists of neighbor cells to be associated with an alternate time-to-trigger (TTT) and a second plurality of lists of neighbor cells not to be associated with the alternate TTT, each list further associated with an index value unique to the particular plurality;
  • TTT time-to-trigger
  • the report configuration message comprises a list of neighbor cells associated with the alternate TTT and one or more indicators, each indicator identifying one of the plurality of lists according to the associated index value.
  • each of the first and second pluralities of lists is further associated with a particular RS type, each list further associated with an index value unique to the particular plurality and the particular RS type.
  • determing reporting events comprises assigning the alternate TTT for reporting measurements made on a determined list of neighbor cells comprising the list of neighbor cells associated with the alternate TTT and lists of neighbor cells of the first plurality identified by the one or more indicators, but exclusing lists of neighbor cells of the second plurality identified by the one or more indicators.
  • a method performed by a base station for configuring a wireless device to report measurements made on signals from neighbor cells in a wireless network comprising: a. transmitting, to a wireless device, a measurement object message identifying: i. a plurality of neighbor cells on which to perform measurements; and ii. one or more subsets of the plurality of neighbor cells, each subset corresponding to one of a plurality of reference signal (RS) types available to be measured; b. transmitting, to the wireless device, a reporting configuration message
  • RS reference signal
  • the measurement object message comprises an alternate time-to-trigger (TTT) associated with each of the one of more subsets of the neighbor cells; and - the measurements comprising the measurement report are reported based on the alternate TTT.
  • TTT time-to-trigger
  • the measurement object messages comprises a plurality of lists of neighbor cells associated with an alternate time-to-trigger (TTT), the plurality of lists comprising:
  • the measurement object message comprises a plurality of lists of neighbor cells associated with an alternate time-to-trigger (TTT), each list further associated with a unique index; and
  • TTT alternate time-to-trigger
  • the report configuration message comprises one or more indicators, each
  • the plurality of lists of neighbor cells comprises a first plurality of lists corresponding to a first RS type and a second plurality of lists corresponding to a second RS type, each list further associated with an index value unique to the particular plurality;
  • each indicator identifies a list of the first plurality or the second plurality according to the associated index value.
  • the measurement object message comprises a plurality of lists of neighbor cells, the plurality of lists comprising a first plurality of lists of neighbor cells to be associated with an alternate time-to-trigger (TTT) and a second plurality
  • each list further associated with an index value unique to the particular plurality
  • the report configuration message comprises a list of neighbor cells associated with the alternate TTT and one or more indicators, each indicator identifying one of the plurality of lists according to the associated index value.
  • each of the first and second pluralities of lists is further associated with a particular RS type, each list further associated with an index value unique to the particular plurality and the particular RS type.
  • the measurements comprising the measurement report include measurements made on a determined list of neighbor cells comprising the list of neighbor cells associated with the alternate TTT and lists of neighbor cells of the first plurality identified by the one or more indicators, but exclusing lists of neighbor cells of the second plurality identified by the one or more indicators.
  • a wireless device comprising:
  • - power supply circuitry configured to supply power to the wireless device.
  • a base station comprising:
  • ser equipment comprising:
  • radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry;
  • processing circuitry being configured to perform operations corresponding to any of the methods of embodiments 1-10;
  • an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry
  • mmunication system including a host computer comprising:
  • UE user equipment
  • the cellular network comprises a base station having a radio interface and processing circuitry, the base station’s processing circuitry configured to perform operations corresponding to any of the methods of embodiments 1 1- 20
  • the UE comprises processing circuitry configured to execute a client
  • a user equipment (UE) configured to communicate with a base station, the UE
  • a communication system including a host computer comprising:
  • a communication interface configured to forward user data to a cellular
  • UE user equipment
  • the UE comprises a radio interface and processing circuitry, the UE’s components configured to perform operations corresponding to any of the methods of embodiments 1-10.
  • the communication system of embodiment 32, wherein the cellular network can also include a base station configured to communicate with the UE.
  • the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data
  • the UE’s processing circuitry is configured to execute a client application associated with the host application.
  • a method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: - at the host computer, providing user data; and
  • a communication system including a host computer comprising:
  • a - communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station
  • the UE comprises a radio interface and processing circuitry, the UE’s processing circuitry configured to perform operations corresponding to any of the methods of embodiments 1-10.
  • the processing circuitry of the host computer is configured to execute a host application
  • the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data.
  • the processing circuitry of the host computer is configured to execute a host application, thereby providing request data
  • the user data to be transmitted is provided by the client application in response to the input data.
  • a communication system including a host computer comprising a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the base station comprises a radio interface and processing circuitry, the base station’s processing circuitry configured to perform operations corresponding to any of the methods of embodiments 11-20.
  • UE user equipment
  • the communication system of the previous embodiment further including the base station.
  • the processing circuitry of the host computer is configured to execute a host application
  • the UE is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer.

Landscapes

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

Abstract

Selon un aspect, l'invention concerne un dispositif sans fil qui peut rapporter des mesures effectuées sur des signaux provenant de cellules voisines dans un réseau sans fil. Le dispositif sans fil peut recevoir un message d'objet de mesure, provenant d'une station de base, identifier des cellules voisines sur lesquelles effectuer des mesures et des sous-ensembles des cellules voisines, chaque sous-ensemble correspondant à l'un d'une pluralité de types de RS disponibles à mesurer. Le dispositif sans fil reçoit un message de configuration de rapport provenant de la station de base identifiant des événements de rapport, chaque événement de rapport correspondant à des mesures d'un type particulier parmi les types de RS. Le dispositif sans fil peut déterminer, sur la base de l'objet de mesure reçu et des messages de configuration de rapport, des événements de rapport pour chacun des sous-ensembles des cellules voisines et rapporte, à la station de base, selon l'un des événements de rapport déterminés, des mesures effectuées sur le sous-ensemble correspondant de cellules voisines sur la base du type de RS correspondant.
PCT/SE2018/051171 2017-11-16 2018-11-14 Temps de déclenchement (ttt) alternatif pour des événements de mesure sur la base d'un type de signal de référence (rs) WO2019098920A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201762587155P 2017-11-16 2017-11-16
US62/587,155 2017-11-16

Publications (1)

Publication Number Publication Date
WO2019098920A1 true WO2019098920A1 (fr) 2019-05-23

Family

ID=66539116

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2018/051171 WO2019098920A1 (fr) 2017-11-16 2018-11-14 Temps de déclenchement (ttt) alternatif pour des événements de mesure sur la base d'un type de signal de référence (rs)

Country Status (1)

Country Link
WO (1) WO2019098920A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022204706A1 (fr) * 2021-03-25 2022-09-29 Qualcomm Incorporated Techniques de production de rapports de mesures pour des communications avec formation de faisceaux

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150327098A1 (en) * 2013-01-18 2015-11-12 Huawei Technologies Co., Ltd. Measurement method and apparatus, and communications node
US20170013490A1 (en) * 2014-03-14 2017-01-12 Nokia Solutions And Networks Oy Dormant Cell RRM Measurement Reporting

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150327098A1 (en) * 2013-01-18 2015-11-12 Huawei Technologies Co., Ltd. Measurement method and apparatus, and communications node
US20170013490A1 (en) * 2014-03-14 2017-01-12 Nokia Solutions And Networks Oy Dormant Cell RRM Measurement Reporting

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "Initial ASN.1 TP on RRM", 3GPP TSG-RAN WG2 #99-BIS TDOC R2-1710840, vol. RAN WG2, 8 October 2017 (2017-10-08), Prague, Czech, XP051342865 *
ERICSSON: "TP for TS 36.331 on inter-RAT NR measurement", 3GPP TSG-RAN WG2 #99BIS TDOC R2-1711129, vol. RAN WG2, 29 September 2017 (2017-09-29), Prague, Czech Republic, XP051355404 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022204706A1 (fr) * 2021-03-25 2022-09-29 Qualcomm Incorporated Techniques de production de rapports de mesures pour des communications avec formation de faisceaux

Similar Documents

Publication Publication Date Title
EP3533259B1 (fr) Rapport contenant un indicateur nsa/sa nr
US10601556B2 (en) Measurement gap configuration
US11665567B2 (en) Adaptive CSI reporting for carrier aggregation
JP2022504658A (ja) Ｎｒ－ｄｃにおける測定設定
US20200092738A1 (en) Cell Global Identifier Reporting in a Wireless Communication System
US11805455B2 (en) Cell global identifier, CGI, reporting of enhanced LTE (eLTE) cells
US20200053583A1 (en) Method, network node and ue for handling rrm measurements on a carrier comprising a plurality of synchronization sequence blocks
US11343727B2 (en) Cell global identifier reporting in a wireless communication system
WO2019162904A1 (fr) Notification de mesures déclenchée par événement dans un scénario de connectivité double intrafréquence
US20230054571A1 (en) Key Change Notification for Authentication and Key Management for Applications
US20230008485A1 (en) Improving Coexistence Using Virtual Non-Public Network Fencing in Macro Public Networks
EP3858087B1 (fr) Procédés et appareils de configuration et de rapport de mesure
WO2020139178A1 (fr) Appareils et procédés destinés à une double connectivité
WO2019098920A1 (fr) Temps de déclenchement (ttt) alternatif pour des événements de mesure sur la base d'un type de signal de référence (rs)
US20220110176A1 (en) Multi-Connectivity in a Wireless Communication Network
US20240089816A1 (en) Conditional Handover OAM Measurements
US20220338116A1 (en) Cell Reselection in LTE-M Standalone Cells
US20230080741A1 (en) Reducing Signalling Overhead in Handover Preparation
EP4026388B1 (fr) Connectivité double sensible à la liaison montante
US20230292306A1 (en) Methods of autonomous transmission after cancellation
US20220394602A1 (en) On demand system information block request over srb3
US20240121593A1 (en) Restriction of number of pscells in mhi report
US20220346110A1 (en) Filtered user equipment throughput counter
WO2024035291A1 (fr) Configuration de référence pour un ou plusieurs candidats de mobilité inter-cellules l1/l2
WO2022139667A1 (fr) Améliorations d'informations d'historique de mobilité avec identité de réseau de téléphonie mobile terrestre public (plmn)

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: 18879551

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18879551

Country of ref document: EP

Kind code of ref document: A1