MEASUREMENT CONFIGURATION AND REPORTING SCHEMES IN WIRELESS COMMUNICATIONS

Abstract

A method of wireless communication is described. The method is performed by a user device and comprises: receiving, from a network device, at least one of measurement configuration information for configuring measurement parameters or measurement reporting information including a measurement report triggering condition; performing measurements based on the measurement configuration information received from the network device; and performing an evaluation for the measurement event according to the measurement report triggering condition.

Description

TECHNICAL FIELD

This patent document generally relates to systems, devices, and techniques for wireless communications.

BACKGROUND

Wireless communication technologies are moving the world toward an increasingly connected and networked society. The rapid growth of wireless communications and advances in technology has led to greater demand for capacity and connectivity. Other aspects, such as energy consumption, device cost, spectral efficiency, and latency are also important to meeting the needs of various communication scenarios. In comparison with the existing wireless networks, next generation systems and wireless communication techniques need to provide support for an increased number of users and devices.

SUMMARY

This document relates to methods, systems, and devices for measurement configuration and reporting schemes in wireless communications.

In one aspect, a wireless communication method is disclosed. The wireless communication method is performed by a user device and comprises: receiving, from a network device, at least one of measurement configuration information for configuring measurement parameters or measurement reporting information including a measurement report triggering condition; performing measurements based on the measurement configuration information received from the network device; and performing an evaluation for the measurement event according to the measurement report triggering condition.

In another aspect, a wireless communication method is disclosed. The wireless communication method is performed by a network device and comprises: transmitting, to a user device, at least one of measurement configuration information for configuring measurement parameters or measurement reporting information including a measurement report triggering condition; and receiving, from the user device, a measurement report including results of measurements according to the measurement reporting information.

In another aspect, a wireless communication apparatus comprising a processor configured to perform the disclosed methods is disclosed.

In another aspect, a computer readable medium having code stored thereon is disclosed. The code, when implemented by a processor, causes the processor to implement a method described in the present document.

These, and other features, are described in the present document.

BRIEF DESCRIPTION OF THE DRAWING

FIG. 1 shows a flowchart showing an example method for a measurement configuration and reporting that is performed by a user device based on some implementations of the disclosed technology.

FIG. 2 shows an example of measurement report triggering condition configured as an area scope expressed with a reference location and a radius associated with the reference location based on some implementations of the disclosed technology.

FIG. 3 shows another example of measurement report triggering condition configured as an area scope expressed with reference locations based on some implementations of the disclosed technology.

FIG. 4 shows another example of measurement report triggering condition configured as an area scope expressed with a list of tracking area identifiers (TAIs) of terrestrial network (TN) cells based on some implementations of the disclosed technology.

FIG. 5 shows an example method for a measurement configuration and reporting that is performed by a network device based on some implementations of the disclosed technology.

FIG. 6 shows an example of wireless communication including a base station (BS) and user equipment (UE) based on some implementations of the disclosed technology.

FIG. 7 shows an example of a block diagram of a portion of an apparatus based on some implementations of the disclosed technology.

DETAILED DESCRIPTION

The disclosed technology provides implementations and examples of measurement configuration and reporting schemes in wireless communications. While 5G terminology is used in some cases to facilitate understanding of the disclosed techniques, which may be applied to wireless systems and devices that use communication protocols other than 5G or 3GPP protocols.

In NR, the measurement configuration include following parameters:

• • Measurement objects: A list of objects on which a UE (user equipment) shall perform the measurements.
  • Reporting configurations: A list of reporting configurations where there can be one or multiple reporting configurations per measurement object.
  • Measurement identities: For measurement reporting, a list of measurement identities where each measurement identity links one measurement object with one reporting configuration.
  • Quantity configurations: The quantity configuration defines the measurement filtering configuration used for all event evaluation and related reporting, and for periodical reporting of that measurement.
  • Measurement gaps: Periods that the UE may use to perform measurements.

The measurement gap is configured per UE for a list of measurement objects. For the NR measurement object, SMTC (SSB based measurement timing configuration) can be configured and UE will perform measurement based on the SMTC configuration during the measurement gap.

Different cells may be deployed in a same frequency and thus may be configured as a same measurement object. The measurement object is a list of objects on which the UE is to perform measurements. For example, terrestrial network cells vs non-terrestrial network cells and non-terrestrial network cells served by satellite or HAPS in different orbits. As a result, it may be difficult for UE to perform measurements on all the cells based on the SMTC configuration per measurement object during the same measurement gap. The SSB refers to synchronization signal/PBCH block.

The UE performs measurements based on the configuration and the measurement report can be triggered periodically or by events (e.g. A1/A2/A3/A4/A5/A6/B1/B2). Examples of such events can include followings:

Event A1: Serving becomes better than absolute threshold.

Event A2: Serving becomes worse than absolute threshold.

Event A3: Neighbour becomes amount of offset better than PCell/PSCell.

Event A4: Neighbour becomes better than absolute threshold.

Event A5: PCell/PSCell becomes worse than absolute threshold1 AND Neighbour/SCell becomes better than another absolute threshold2.

Event A6: Neighbour becomes amount of offset better than SCell.

Event B1: Neighbour becomes better than absolute threshold.

Event B2: PCell becomes worse than absolute threshold1 AND Neighbour becomes better than another absolute threshold2.

For cells with large size (e.g. non-terrestrial network cells served by satellites), the reference signal (RS) measurements, for example, RSRP (Reference Signal Received Power) and RSRQ (Reference Signal Received Quality), and SINR (Signal to noise and interference ratio) measurements may not change significantly from the cell center to the cell edge. Thus, the event A1/A2/A3/A4/A5/A6/B1/B2 triggered measurement report may not be sufficient as the UE may perform measurements and send a measurement report too early or too late before reaching the cell edge.

In light of the above considerations on various propagation delays of different cells and limitations of existing measurement triggering conditions, new schemes for measurement configuration and reporting are suggested in this patent document.

FIG. 1 shows a flowchart of an example method of wireless communication that is performed by a user device. As shown in FIG. 1, at operation 110, the UE receives measurement configuration information and/or measurement report triggering condition from a network device. The measurement configuration information includes measurement gap configuration and/or SMTC configuration and can be configured via system information or dedicated RRC signaling (e.g. RRCReconfiguration message or RRC release message). At operation 120, the UE performs measurements based on the measurement configuration information. At operation 130, the UE performs an evaluation for a measurement event according to the measurement triggering report triggering condition.

The measurement gap configuration and the SMTC configuration are discussed in more detail below.

Measurement Gap Configuration

Measurement gap configurations can be performed in various manners as discussed below.

Implementation 1: A default measurement gap length (e.g. 5.5 ms or 6 ms) can be defined for a specific network scenario, a specific frequency, a specific cell or a specific satellite/HAPS. The examples of the specific network scenario include non-terrestrial network (NTN), air-to-ground (ATG), network served by satellites or high altitude platform station (HAPS), network served by low earth orbit (LEO)/Non-LEO satellite, network served by geostationary (GEO)/Non-GEO satellite.

Implementation 2: A value to be configured for measurement gap length can be limited for a specific network scenario, a specific frequency, a specific cell or a specific satellite/HAPS. The examples of the specific network scenario include NTN, ATG, network served by satellites or HAPS, network served by LEO/Non-LEO satellite, network served by GEO/Non-GEO satellite.

Implementation 3: A new measurement gap configuration is introduced for a specific network scenario, a specific frequency, a specific cell or a specific satellite/HAPS. The examples of the specific network scenario include NTN, ATG, network served by satellites or HAPS, network served by LEO/Non-LEO satellite, network served by GEO/Non-GEO satellite. For example, a value range of the new measurement gap configuration is extended to ensure that the length is larger than or equal to the SSB periodicity of the concerned cells in a specific network scenario (e.g. NTN, ATG, network served by satellites or HAPS, network served by LEO/Non-LEO satellite, network served by GEO/Non-GEO satellite), a specific frequency, or served by a specific satellite/HAPS.

A new measurement gap length (mgl) or measurement gap configuration (measGapConfig) can be configured for a specific network scenario (e.g. NTN, ATG, network served by satellites or HAPS, network served by LEO/Non-LEO satellite, network served by GEO/Non-GEO satellite), a specific frequency, a specific cell or a specific satellite/HAPS to ensure that the measurement gap length is large enough to cover all the possible SSB periodicity of cells in the same measurement objects.

In an example, mgl-NTN can be defined as follows:

Mgl-NTN-r17 ENUMERATED {ms6, ms11, ms21, ms41, ms81, ms161}

In an example, MeasGapConfig-NTN can be defined as follows:

MeasGapConfig-NTN ::=         SEQUENCE {
gapFR2-NTN                    SetupRelease { GapConfig-NTN }
OPTIONAL, -- Need M
...,
[[
gapFR1-NTN                    SetupRelease { GapConfig-NTN }
OPTIONAL, -- Need M
GapUE-NTN                     SetupRelease { GapConfig-NTN }
OPTIONAL -- Need M
]]
}
GapConfig-NTN ::=             SEQUENCE {
gapOffset-NTN                 INTEGER (0..159),
mg1-NTN                       ENUMERATED {ms6, ms11, ms21, ms41, ms81, ms161},
mgrp-NTN                      ENUMERATED {ms20, ms40, ms80, ms160},
mgta-NTN                      ENUMERATED {ms0, ms0dot25, ms0dot5},
...,
[[
refServCellIndicator-NTN      ENUMERATED {pCell, pSCell, mcg-FR2}
OPTIONAL -- Cond NEDCorNRDC
]],
[[
refFR2ServCellAsyncCA-NTN-r17 ServCellIndex
OPTIONAL -- Cond AsyncCA
]]
}

In an example, MeasGapConfig-NeighSat can be defined as follows:

MeasGapConfig-NeighSat ::=       SEQUENCE {
neighbourSateliteId              INTEGER (0..maxNrofSupportedSatellites)
gapFR2-NeighSat                  SetupRelease { GapConfig-NTN }
OPTIONAL, -- Need M
...,
[[
gapFR1-NeighSat                  SetupRelease { GapConfig-NTN }
OPTIONAL, -- Need M
GapUE-NeighSat                   SetupRelease { GapConfig-NTN }
OPTIONAL -- Need M
]]
}
GapConfig-NeighSat ::=           SEQUENCE {
gapOffset-NeighSat               INTEGER (0..159),
mg1-NeighSat                     ENUMERATED {ms6, ms11, ms21, ms41, ms81, ms161},
mgrp-NeighSat                    ENUMERATED {ms20, ms40, ms80, ms160},
mgta-NeighSat                    ENUMERATED {ms0, ms0dot25, ms0dot5},
...,
[[
refServCellIndicator-NeighSat    ENUMERATED {pCell, pSCell, mcg-FR2}
OPTIONAL -- Cond NEDCorNRDC
]],
[[
refFR2ServCellAsyncCA-NeighSat-r17 ServCellIndex
OPTIONAL -- Cond AsyncCA
]]
}

Implementation 4: An indicator is introduced to indicate whether extra compensation is needed in the measurement gap. For example, an indicator can be provided to indicate that the transmission delay or timing advance (TA) shall be used as compensation in the measurement gap, and UE may delay start of the measurement gap based on the compensation. The indicator can be configured for a certain network scenario (e.g. NTN, ATG, network served by satellites or HAPS, network served by LEO/Non-LEO satellite, network served by GEO/Non-GEO satellite), a certain cell, a certain frequency or a certain satellite/HAPS (High Altitude Platform Station).

As an example, gapPrecompensation-r17 can be defined as follows:

gapPrecompensation-r17 ENUMERATED {enabled}
OPTIONAL,  -- Need R

Upon receiving the gapPrecompensation-r17, UE will compensate for the one-way transmission delay between the UE and the satellite/HAPS/NTN GW before starting the measurement gap.

Implementation 5: An extra measurement gap offset is introduced to delay the start of measurement gap. The extra measurement gap can be configured for a specific network scenario (e.g. NTN, ATC, network served by satellites or HAPS, network served by LEO/Non-LEO satellite, network served by GEO/Non-GEO satellite), a specific frequency, a specific cell or a specific satellite/HAPS. The value of the extra measurement gap offset can be configured in one of the following options:

Option 1: The value of the extra measurement gap offset is the transmission delay between the UE and the satellite/HAPS serving the PCell or the transmission delay between UE and the satellite/HAPS serving a certain neighbor cell or cells on a certain frequency.

Option 2: The value of the extra measurement gap offset is the transmission delay between the UE and the NTN/HAPS gateway (GW) serving the PCell or the transmission delay between the UE and the NTN/HAPS GW serving a certain neighbour cell or cells on a certain frequency.

Option 3: The value of the extra measurement gap offset is the transmission delay between the satellite/HAPS and the NTN/HAPS gateway (GW) serving the PCell or the transmission delay between the satellite/HAPS and the NTN/HAPS GW serving a certain neighbour cell or cells on a certain frequency.

As an example, extraGapOffset-r17 can be defined as follows:

extraGapOff set-r17 ENUMERATED {ms6, ms10, ms20, ms40,
                    ms80, ms160, ms320, ms640},
OPTIONAL,  -- Need R

Implementation 6: An indicator is introduced to indicate that the reference timing of measurement gap is timing on satellite/HAPS serving the PCell or timing on the NTN/HAPS GW serving the PCell. The indicator can be defined and configured for a specific network scenario (e.g. NTN, ATC, network served by satellites or HAPS, network served by LEO/Non-LEO satellite, network served by GEO/Non-GEO satellite), a specific frequency, a specific cell or a specific satellite/HAPS.

Implementation 7: A start timing reference for measurement gap is introduced, which is used to indicate the start point of the measurement gap. The start timing is given by an absolute timing (e.g. a UTC time) and the time refers to the timing on the serving satellite/HAPS of PCell or on the NTN/HAPS GW of PCell. The start timing reference can be configured for a certain cell, a certain frequency or a certain satellite/HAPS (High Altitude Platform Station) in an explicit way or implicit way. The starting timing reference for a certain cell, a certain frequency, a certain satellite/HAPS (High Altitude Platform Station) or a certain network scenario can also be specified in specs with a fixed value or value range.

An example of an explicit configuring of the start time reference for measurement gap is provided below:

gapstartTimeInfo-r17	SEQUENCE {
	timeinfoUTC	INTEGER (0..549755813887),
	dayLightSavingTime	BIT STRING (SIZE (2))	OPTIONAL,	-- Need
R
	leapSeconds	INTEGER (−127..128)	OPTIONAL,	-- Need
R
	localTimeOffset	INTEGER (−63..64)	OPTIONAL	-- Need
R
	}		OPTIONAL,	-- Need R

Upon receiving this gapStartTimeInfo-r17, UE can derive the start timing reference for measurement gap at the UE side (e.g. the gapStartTimeInfo-r17+the transmission delay between UE and the serving satellite/HAPS of PCell or the NTN/HAPS GW of PCell).

SMTC Configuration

SMTC configurations can be performed in various manners as discussed below.

Implementation 1: A default SMTC configuration (e.g. with default SSB periodicity 5 ms) can be defined for a specific network scenario (e.g. NTN, ATC, network served by satellites or HAPS, network served by LEO/Non-LEO satellite, network served by GEO/Non-GEO satellite), a specific frequency, a specific cell or a specific satellite/HAPS.

Implementation 2: A value to be configured for SMTC configuration can be limited in a specific network scenario (e.g. NTN, ATG, network served by satellites or HAPS, network served by LEO/Non-LEO satellite, network served by GEO/Non-GEO satellite), a specific frequency, a specific cell or a specific satellite/HAPS.

Implementation 3: A new SMTC configuration is introduced for a specific network scenario (e.g. NTN, ATG, network served by satellites or HAPS, network served by LEO/Non-LEO satellite, network served by GEO/Non-GEO satellite), a specific frequency, a specific cell or a specific satellite/HAPS. For example, the value range of the new SMTC configuration is extended to ensure that the length is less than or equal to the measurement gap of the concerned cells in a network scenario (e.g. NTN, ATG, network served by satellites or HAPS, network served by LEO/Non-LEO satellite, network served by GEO/Non-GEO satellite), a specific frequency, or served by a specific satellite/HAPS.

In an example, SSB-MTC-NeighSat can be defined as follows:

smtcNeighSatList         SEQUENCE (SIZE (1..maxNrofSupportedSatellites)) OF SSB-MTC-
NeighSat
SSB-MTC-NeighSat ::=     SEQUENCE {
neighbourSateliteId      INTEGER (0..maxNrofSupportedSatellites)
periodicityAndOffset     CHOICE {
sf5                      INTEGER (0..4),
sf10                     INTEGER (0..9),
sf20                     INTEGER (0..19),
sf40                     INTEGER (0..39),
sf80                     INTEGER (0..79),
sf160                    INTEGER (0..159)
},
duration                 ENUMERATED { sf1, sf2, sf3, sf4, sf5 }
}
SSB-MTC2 ::=             SEQUENCE {
pci-List                 SEQUENCE (SIZE (1..maxNrofPCIsPerSMTC)) OF PhysCellId
OPTIONAL, -- Need M
periodicity              ENUMERATED {sf5, sf10, sf20, sf40, sf80, spare3, spare2,
spare1}
}
SSB-MTC2-LP-r16 ::=      SEQUENCE {
pci-List                 SEQUENCE (SIZE (1..maxNrofPCIsPerSMTC)) OF PhysCellId
OPTIONAL, -- Need R
periodicity              ENUMERATED {sf10, sf20, sf40, sf80, sf160, spare3, spare2,
spare1}
}
SSB-MTC3-r16 ::=         SEQUENCE {
periodicityAndOffset-r16 CHOICE {
sf5-r16                  INTEGER (0..4),
sf10-r16                 INTEGER (0..9),
sf20-r16                 INTEGER (0..19),
sf40-r16                 INTEGER (0..39),
sf80-r16                 INTEGER (0..79),
sf160-r16                INTEGER (0..159),
sf320-r16                INTEGER (0..319),
sf640-r16                INTEGER (0..639),
sf1280-r16               INTEGER (0..1279)
},
duration-r16             ENUMERATED {sf1, Sf2, sf3, sf4, sf5},
pci-List-r16             SEQUENCE (SIZE (1..maxNrofPCIsPerSMTC)) OF PhysCellId
OPTIONAL, -- Need M
ssb-ToMeasure-r16        SetupRelease { SSB-ToMeasure }
OPTIONAL  -- Need M
}

Each SSB-MTC-NeighSat can be identified by an index (e.g. the first SSB-MTC-NeighSat in the smtcNeighSatList is identified by index 0) can be associated with a certain frequency or a certain cell via this index.

CellsToAddModList ::= SEQUENCE (SIZE (1..maxNrofCellMeas)) OF CellsToAddMod
CellsToAddMod ::=     SEQUENCE {
smtc                  INTEGER (0. .maxNrofSupportedSatellites-1)
physCellId            PhysCellId,
cellIndividualOffset  Q-OffsetRangeList
}

Implementation 4: An indicator is introduced to indicate whether extra compensation is needed in the SMTC. For example, an indicator can be provided to indicate that the transmission delay or timing advance (TA) shall be used as compensation in the SMTC, and the UE may delay the start of the SMTC based on the compensation. The indicator can be configured for a certain cell, a certain frequency or a certain satellite/HAPS (High Altitude Platform Station).

In the example, smtcPrecompensation-r17 can be defined as follows:

smtcPrecompensation-r17 ENUMERATED {enabled}
OPTIONAL,  -- Need R

Upon receiving the smtcPrecompensation-r17, the UE will compensate for the transmission delay between the UE and the satellite/HAPS/NTN GW before starting the SMTC.

Implementation 5: An extra SMTC offset is introduced to delay the start of SMTC. The extra SMTC offset can be defined and configured for a specific network scenario (e.g. NTN, ATC, network served by satellites or HAPS, network served by LEO/Non-LEO satellite, network served by GEO/Non-GEO satellite), a specific frequency, a specific cell or a specific satellite/HAPS. The value of the extra SMTC offset can be configured in one of the following options:

Option 1: The value of the extra SMTC offset is the transmission delay between the UE and the satellite/HAPS serving the PCell or the transmission delay between the UE and the satellite/HAPS serving a certain neighbour cell or cells on a certain frequency.

Option 2: The value of the extra SMTC offset is the transmission delay between the UE and the NTN/HAPS gateway (GW) serving the PCell or the transmission delay between tjr UE and the NTN/HAPS GW serving a certain neighbour cell or cells on a certain frequency.

Option 3: The value of the extra SMTC offset is the transmission delay between the satellite/HAPS and the NTN/HAPS gateway (GW) serving the PCell or the transmission delay between the satellite/HAPS and the NTN/HAPS GW serving a certain neighbour cell or cells on a certain frequency.

In an example, extraSMTCOffset-r17 can be defined as follows:

extraSMTCOffset-r17 ENUMERATED {ms6, ms10, ms20, ms40,
                    ms80, ms160, ms320, ms640},
OPTIONAL,  -- Need R

Upon receiving the extraSMTCOffset-r17, UE will compensate the extra offset before start the SMTC.

Implementation 6: An indicator is introduced to indicate that the reference timing of SMTC is the timing on satellite/HAPS serving the PCell or the timing on the NTN/HAPS GW serving the PCell. The indicator can be defined and configured for a specific network scenario (e.g. NTN, ATC, network served by satellites or HAPS, network served by LEO/Non-LEO satellite, network served by GEO/Non-GEO satellite), a specific frequency, a specific cell or a specific satellite/HAPS.

Implementation 7: A start timing reference for SMTC is introduced, which is used to indicate the start point of the SMTC. The start timing is given by an absolute timing (e.g. a UTC time) and the time refer to the timing on the serving satellite/HAPS of PCell or on the NTN/HAPS GW of PCell. The start timing reference can be configured for a specific network scenario (e.g. NTN, ATC, network served by satellites or HAPS, network served by LEO/Non-LEO satellite, network served by GEO/Non-GEO satellite), a specific frequency, a specific cell or a specific satellite/HAPS. The starting timing reference can also be specified in specs with a fixed value or value range.

An example of an explicit configuring of the start time reference for SMTC is provided below:

smtcStartTimeInfo-r17	SEQUENCE {
timeInfoUTC	INTEGER (0..549755813887),
dayLightSavingTime	BIT STRING (SIZE (2))	OPTIONAL,	--Need
R
leapSeconds	INTEGER (−127..128)	OPTIONAL,	--Need
R
localTimeOffset	INTEGER (−63..64)	OPTIONAL	--Need
R
}		OPTIONAL,	--Need R

Upon receiving this smtcStartTimeInfo-r17, the UE can derive the start timing reference for SMTC at UE side (e.g. the smtcStartTimeInfo-r17+the transmission delay between UE and the serving satellite/HAPS of PCell or the NTN/HAPS GW of PCell).

Measurement Report Triggering Condition

In some implementations, the measurement report triggering condition can be configured as an area scope along with hysteresis or a time range along with hysteresis. The UE will perform the evaluation for the measurement event according to the configured triggering condition.

Relative Area Scope as Measurement Report Triggering Condition

The following implementations can be considered to configure the area scope expressed as a distance between the UE and the satellite/HAPS, cell center or reference point.

Implementation 1: The area scope and the hysteresis are expressed as the relative distance between UE and the satellite/HAPS.

Implementation 2: The area scope is configured as the relative distance between UE and the center of a cell.

Implementation 3: The area scope is configured as the relative distance between UE and a configured reference point.

In an example (corresponding to Implementation 1), new MeasTriggerQuantity, Hysteresis, and/or MeasTriggerQuantityOffset are defined based on a distance between UE and the satellite/HAPS as shown below:

MeasTriggerQuantity ::=       CHOICE {
rsrp                          RSRP-Range,
rsrq                          RSRQ-Range,
sinr                          SINR-Range,
distanceToSat                 Distance-Range
}
MeasTriggerQuantityOffset ::= CHOICE {
rsrp                          INTEGER (−30..30),
rsrq                          INTEGER (−30..30),
sinr                          INTEGER (−30..30),
distanceToSat                 Distance-Range
}
Distance-Range ::=            INTEGER(0..XX)
Hysteresis ::=                INTEGER (0..XX)

The IE Hysteresis is a parameter used within the entry and leave condition of an event triggered reporting condition. The actual value is field value*0.5 km.

The actual value of Distance-Range is the field value*0.5 km.

A new field indicating the coordinates or the ID of the serving or neighbouring satellites/HAPS or NTN/HAPS GW that the UE needs to evaluate the distance to will be defined and configured to UE for a specific cell, a specific network scenario (e.g. NTN, ATC, network served by satellites or HAPS, network served by LEO/Non-LEO satellite, network served by GEO/Non-GEO satellite), a specific frequency for the UE to perform measurement evaluation on.

In an example, the below indicates the satellite coordinates:

servingSatCoordinates        SatCoordinates OPTIONAL, -- Need R
neighbourSatCoordinatesList  SEQUENCE (SIZE (1..maxNrofNeighbourSatellites)) OF
SatCoordinates OPTIONAL, -- Need R
SatCoordinates::= SEQUENCE {
satCoordinates  OCTET STRING OPTIONAL
}

To indicate the satellite identity, the satellite/HAPS ephemeris will be provided to the UE. The coordinates of the serving or neighbouring satellites/HAPS can either be included directly in the ephemeris information or derived based on the orbital parameters in the ephemeris information. Each satellite/HAPS will be associated with an ID in the ephemeris and the satellite/HAPS ID will be configured to UE for a specific cell, a specific network scenario (e.g. NTN, ATC, network served by satellites or HAPS, network served by LEO/Non-LEO satellite, network served by GEO/Non-GEO satellite), a specific frequency for the UE to perform measurement evaluation on.

In an example (corresponding to Implementation 2), new MeasTriggerQuantity, Hysteresis, and/or MeasTriggerQuantityOffset are defined based on a distance between the UE and the center of a cell as shown below.

MeasTriggerQuantity ::=        CHOICE {
rsrp                           RSRP-Range,
rsrq                           RSRQ-Range,
sinr                           SINR-Range,
distanceToCellCenter           Distance-Range
}
MeasTriggerQuantityOffset :: = CHOICE {
rsrp                           INTEGER (−30..30),
rsrq                           INTEGER (−30..30),
sinr                           INTEGER (−30..30),
distanceToCellCenter           Distance-Range
}
Distance-Range ::=             INTEGER(0..XX)
Hysteresis ::=                 INTEGER (0..XX)

The IE Hysteresis is a parameter used within the entry and leave condition of an event triggered reporting condition. The actual value is field value*0.5 km.

The actual value of Distance-Range is the field value*0.5 km.

A new field indicating the coordinates of the serving or neighbouring cell center that UE needs to evaluate the distance to will be defined and configured to UE.

In an example, the below indicates the cell center coordinates:

servingCellCenterCoordinates      CellCenterCoordinates OPTIONAL, -- Need R
neighbourCellCenterCoordinatesList     SEQUENCE (SIZE (1..maxNrofNeighbourCells)) OF
CellCenterCoordinates OPTIONAL, -- Need R
CellCenterCoordinates::= SEQUENCE {
cellCenterCoordinates  OCTET STRING OPTIONAL
}

In an example (corresponding to implementation 3), new MeasTriggerQuantity, Hysteresis, and/or MeasTriggerQuantityOffset are defined based on the distance between the UE and a reference location as shown below:

MeasTriggerQuantity ::=       CHOICE {
rsrp                          RSRP-Range,
rsrq                          RSRQ-Range,
sinr                          SINR-Range,
distanceToRefPoint            Distance-Range
}
MeasTriggerQuantityOffset ::= CHOICE {
rsrp                          INTEGER (−30..30),
rsrq                          INTEGER (−30..30),
sinr                          INTEGER (−30..30),
distanceToRefPoint            Distance-Range
}
Distance-Range ::=            INTEGER(0..XX)
Hysteresis ::=                INTEGER (0..XX)

The IE Hysteresis is a parameter used within the entry and leave condition of an event triggered reporting condition. The actual value is field value*0.5 km.

The actual value of Distance-Range is the field value*0.5 km.

A new field indicating the coordinates of a reference point that the UE needs to evaluate the distance to will be defined and configured to the UE and the reference point can be configured for a specific cell or specific frequency.

In an example, the below indicates the cell center coordinates:

servingRef Point       RefPiontCoordinates OPTIONAL, -- Need R
neighbourRefPointList  SEQUENCE (SIZE (1..maxNrofRefPionts)) OF RefPointCoordinates
OPTIONAL,              -- Need R
RefPointCoordinates::= SEQUENCE {
refPointCoordinates    OCTET STRING OPTIONAL
}

Some implementations of the disclosed technology configure measurement report triggering condition that is received from the network device. The following events can be configured to trigger measurement report:

Event A1 (Serving becomes better than threshold):

eventA1		SEQUENCE {
	a1-Threshold		MeasTriggerQuantity,
	reportOnLeave		BOOLEAN,
	hysteresis		Hysteresis,
}	timeToTrigger		TimeToTrigger

The a1-Threshold and hysteresis are configured as the distance between UE and the serving satellite/HAPS, cell center or reference point.

Upon receiving the event A1, the UE shall perform at least one of following operations:

• • Operation 1: The UE considers that the entering condition for this event is satisfied when the entering condition A1-1 is fulfilled. In one example, the entering condition A1-1 may correspond to: Ds−Hys>Thresh. Ds is the distance between UE and the serving satellite/HAPS, cell center or reference point, not taking into account any offsets. Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigNR for this event). Thresh is the threshold parameter for this event (i.e. a1-Threshold as defined within reportConfigNR for this event). In some implementations, the Ds is expressed in km, Hys is expressed in km, and Tresh is expressed in the same unit as Ds.
  • Operation 2: The UE considers that the leaving condition for this event is satisfied when the leaving condition A1-2 is fulfilled. In one example, the leaving condition A1-2 may correspond to: Ds+Hys<Thresh. Ds, Hys, Tresh have been already discussed for the entering condition A1-1 above.
  • Operation 3: For this measurement, the UE considers the NR serving cell corresponding to the associated measObjectNR associated with this event.

Event A2 (Serving becomes worse than threshold):

eventA2		SEQUENCE {
	a2-Threshold		MeasTriggerQuantity,
	reportOnLeave		BOOLEAN,
	hysteresis		Hysteresis,
},	timeToTrigger		TimeToTrigger

The a2-Threshold and hysteresis are configured as the distance between UE and the serving satellite/HAPS, cell center or reference point.

Upon receiving the event A2, UE shall perform at least one of following operations:

• • Operation 1: The UE considers the entering condition for this event to be satisfied when the entering condition A2-1 is fulfilled. In one example, the entering condition A2-1 may correspond to: Ds+Hys>Thresh. Ds is the distance between UE and the serving satellite/HAPS, cell center or reference point, not taking into account any offsets. Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigNR for this event). Thresh is the threshold parameter for this event (i.e. a2-Threshold as defined within reportConfigNR for this event). In some implementations, the Ds is expressed in km, Hys is expressed in km, and Tresh is expressed in the same unit as Ds.
  • Operation 2: The UE considers that the leaving condition for this event is satisfied when the leaving condition A2-2 is fulfilled. In one example, the leaving condition A2-2 may correspond to: Ds−Hys<Thresh. Ds, Hys, Tresh have been already discussed for the entering condition A2-1 above.
  • Operation 3: For this measurement, consider the serving cell indicated by the measObjectNR associated with this event.

Event A3 (Neighbour becomes offset better than SpCell):

eventA3                  SEQUENCE {
        a3-Offset        MeasTriggerQuantityOffset,
        reportOnLeave    BOOLEAN,
        hysteresis       Hysteresis,
        timeToTrigger    TimeToTrigger,
        useWhiteCellList BOOLEAN
},

The a3-Offset and hysteresis are configured as the distance between UE and the serving satellite/HAPS, cell center or reference point.

Upon receiving the event A3, UE shall perform at least one of following operations:

• • Operation 1: The UE considers the entering condition for this event to be satisfied when the entering condition A3-1 is fulfilled. In one example, the entering condition A2-1 may correspond to: Dn+Ofn+Ocn−Hys>Dp+Ofp+Ocp+Off. The variables in the formula are defined as follows:

Dn is the distance between UE and the neighbour satellite/HAPS, cell center or reference point, not taking into account any offsets.

Ofn is the measurement object specific offset of the reference signal of the neighbour cell (i.e. offsetMO as defined within measObjectNR corresponding to the neighbour cell).

Ocn is the cell specific offset of the neighbour cell (i.e. celllndividualOffset as defined within measObjectNR corresponding to the frequency of the neighbour cell), and set to zero if not configured for the neighbour cell.

Dp is the distance between UE and the serving satellite/HAPS, cell center or reference point, not taking into account any offsets.

Ofp is the measurement object specific offset of the SpCell (i.e. offsetMO as defined within measObjectNR corresponding to the SpCell).

Ocp is the cell specific offset of the SpCell (i.e. celllndividualOffset as defined within measObjectNR corresponding to the SpCell), and is set to zero if not configured for the SpCell.

Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigNR for this event).

Off is the offset parameter for this event (i.e. a3-Offset as defined within reportConfigNR for this event).

Dn and Dp are expressed in km in case of Distance.

Ofn, Ocn, Ofp, Ocp, Hys, Off are expressed in km.

• • Operation 2: The UE considers the leaving condition for this event to be satisfied when the leaving condition A3-2 is fulfilled. In one example, the leaving condition A3-2 may correspond to: Dn+Ofn+Ocn+Hys<Dp+Ofp+Ocp+Off. The variables in the formula have been already discussed for the entering condition A3-1.
  • Operation 3: The UE uses the SpCell for Dp, Ofp and Ocp.

Event A4 (Neighbour becomes better than threshold):

eventA4          SEQUENCE {
a4-Threshold     MeasTriggerQuantity,
reportOnLeave    BOOLEAN,
hysteresis       Hysteresis,
timeToTrigger    TimeToTrigger,
useWhiteCellList BOOLEAN
},

The a4-Threshold and hysteresis are configured as the distance between UE and the serving satellite/HAPS, cell center or reference point.

Upon receiving the event A4, the UE shall perform at least one of following operations:

• • Operation 1: The UE considers the entering condition for this event to be satisfied when the entering condition A4-1 is fulfilled. In one example, the entering condition A4-1 may correspond to: Mn+Ofn+Ocn−Hys>Thresh. The variables in the formula are defined as follows:

Mn is the distance between UE and the neighbour satellite/HAPS, cell center or reference point, not taking into account any offsets.

Ofn is the measurement object specific offset of the neighbour cell (i.e. offsetMO as defined within measObjectNR corresponding to the neighbour cell).

Ocn is the measurement object specific offset of the neighbour cell (i.e. celllndividualOffset as defined within measObjectNR corresponding to the neighbour cell), and set to zero if not configured for the neighbour cell.

Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigNR for this event).

Thresh is the threshold parameter for this event (i.e. a4-Threshold as defined within reportConfigNR for this event).

Mn is expressed in km in case of Distance.

Ofn, Ocn, Hys are expressed in km.

Thresh is expressed in the same unit as Mn.

• • Operation 2: The UE considers the leaving condition for this event to be satisfied when the leaving condition A4-2 is fulfilled. In one example, the leaving condition A4-2 may correspond to: Mn+Ofn+Ocn+Hys<Thresh. The variables in the formula have been already discussed for the entering condition A4-1.

Event A5 (SpCell becomes worse than threshold1 and neighbour becomes better than threshold2):

eventA5          SEQUENCE {
a5-Threshold1    MeasTriggerQuantity,
a5-Threshold2    MeasTriggerQuantity,
reportOnLeave    BOOLEAN,
hysteresis       Hysteresis,
timeToTrigger    TimeToTrigger,
useWhiteCellList BOOLEAN
},

The a5-Threshold1, a5-Threshold2 and hysteresis are configured as the distance between the UE and the serving satellite/HAPS, cell center or reference point.

Upon receiving the event A5, the UE shall perform at least one of following operations:

• • Operation 1: The UE considers the entering condition for this event to be satisfied when both conditions A5-1 and A5-2 are fulfilled. In one example, the entering conditions A5-1 and A5-2 may correspond to: Mp+Hys<Thresh1 and Mn+Ofn+Ocn−Hys>Thresh2, respectively. The variables in the formula are defined as follows:

Mp is the distance between UE and the serving satellite/HAPS, cell center or reference point, not taking into account any offsets.

Mn is the distance between UE and the neighbour satellite/HAPS, cell center or reference point, not taking into account any offsets.

Ofn is the measurement object specific offset of the neighbour cell (i.e. offsetMO as defined within measObjectNR corresponding to the neighbour cell).

Ocn is the cell specific offset of the neighbour cell (i.e. celllndividualOffset as defined within measObjectNR corresponding to the neighbour cell), and set to zero if not configured for the neighbour cell.

Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigNR for this event).

Thresh1 is the threshold parameter for this event (i.e. a5-Threshold1 as defined within reportConfigNR for this event).

Thresh2 is the threshold parameter for this event (i.e. a5-Threshold2 as defined within reportConfigNR for this event).

Mn, Mp are expressed in km in case of Distance.

Ofn, Ocn, Hys are expressed in km.

Thresh1 is expressed in the same unit as Mp.

Thresh2 is expressed in the same unit as Mn.

• • Operation 2: The UE considers the leaving condition for this event to be satisfied when both conditions A5-3 and A5-4 are fulfilled. In one example, the entering conditions A5-3 and A5-4 may correspond to: Mp+Hys>Thresh1 and Mn+Ofn+Ocn−Hys<Thresh2, respectively. The variables in the formula have been already discussed for the entering conditions above.
  • Operation 3: The UE uses the SpCell for Mp.

Event A6 (Neighbour becomes offset better than SCell):

eventA6          SEQUENCE {
a6-Offset        MeasTriggerQuantityOffset,
reportOnLeave    BOOLEAN,
hysteresis       Hysteresis,
timeToTrigger    TimeToTrigger,
useWhiteCellList BOOLEAN
},

The a6-Offset and hysteresis are configured as the distance between the UE and the serving satellite/HAPS, cell center or reference point.

Upon receiving the event A4, UE shall perform at least one of following operations:

• • Operation 1: The UE considers the entering condition for this event to be satisfied when the entering condition A6-1 is fulfilled. In one example, the entering condition A6-1 may correspond to: Mn+Ocn−Hys>Ms+Ocs+Off. The variables in the formula are defined as follows:

Mn is the distance between UE and the neighbour satellite/HAPS, cell center or reference point, not taking into account any offsets.

Ocn is the cell specific offset of the neighbour cell (i.e. cellIndividualOffset as defined within the associated measObjectNR), and set to zero if not configured for the neighbour cell.

Ms is the distance between UE and the serving satellite/HAPS, cell center or reference point, not taking into account any offsets.

Ocs is the cell specific offset of the serving cell (i.e. cellIndividualOffset as defined within the associated measObjectNR), and is set to zero if not configured for the serving cell.

Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigNR for this event).

Off is the offset parameter for this event (i.e. a6-Offset as defined within reportConfigNR for this event).

Mn, Ms are expressed in km in case of Distance.

Ocn, Ocs, Hys, Off are expressed in km.

• • Operation 2: The UE considers the leaving condition for this event to be satisfied when the leaving condition A6-2 is fulfilled. In one example, the leaving condition A6-2 may correspond to: Mn+Ocn−Hys<Ms+Ocs+Off. The variables in the formula have been already discussed for the entering condition A4-1.
  • Operation 3: For this measurement, the UE considers the (secondary) cell corresponding to the measObjectNR associated with this event to be the serving cell.

Absolute Area Scope as Measurement Report Triggering Condition

The following implementations can be considered to configure an absolute area scope as measurement report triggering condition.

Implementation 1: The area scope can be expressed as a single reference location (represented by location coordinates) and a radius associated with the reference location. FIG. 2 shows an example of the area scope 210 that is expressed as a reference location using a radius 220 associated with the reference location.

Implementation 2: The area scope can be expressed with a list of location coordinates. FIG. 3 shows an example of the area scope 310 that is expressed as reference locations.

Implementation 3: The area scope can be expressed with a list of tracking area identifiers (TAIs) of terrestrial network (TN) cells. The TAI includes PLMN ID and tracking area code (TAC)) FIG. 4 shows an example of the area scope 410 that is expressed as a list of TAIs of TN cells. In FIG. 4, a list of TAIs of TN cells (e.g. TAI #1 420 and TAI #3 440) are located around TN Cells (TAI #2 430) and can be configured to represent the cell edge of the serving non-terrestrial network (NTN) cell.

Implementation 4: The area scope can be expressed as two pairs of high and low thresholds for longitude and latitude. In some other implementations, the area scope can be expressed with a low or high threshold along with a offset for longitude and latitude.

Example of Implementation 1:

The following LocationTriggerConfig can be introduced and configured to UE:

LocationTriggerConfig-r17 ::= SEQUENCE {
refPointCoordinates           OCTET STRING,
radius                        Radius-Range,
hysteresisForRadius-r17       Hysteresis-r17,
timeToTrigger                 TimeToTrigger
}
Radius-Range ::=      INTEGER (0..XX)
Hysteresis ::=      INTEGER (0..XX)

The IE Hysteresis is a parameter used within the entry and leave condition of the location triggered reporting condition. The actual value is field value*0.1 km.

The actual value for the Radius-Range is the field value*0.5 km.

Example of Implementation 2:

LocationTriggerConfig-r17 ::=   SEQUENCE {
areaScope      SEQUENCE (SIZE (1..maxNrofCoordinates)) OF Coordinate
OPTIONAL, -- Need R
hysteresis-r17 Hysteresis-r17,
timeToTrigger  TimeToTrigger
}
Hysteresis ::= INTEGER (0..XX)

The IE Hysteresis is a parameter used within the entry and leave condition of an location triggered reporting condition. The actual value is field value*0.5 km.

Example of Implementation 3:

LocationTriggerConfig-r17 ::= SEQUENCE {
areaScope                     SEQUENCE (SIZE (1..maxNrofTAIs)) OF
TAI OPTIONAL, -- Need R
timeToTrigger                 TimeToTrigger
}
Hysteresis ::=                INTEGER (0..XX)

The LocationTriggerConfig can be configured for the serving cell/frequency or the neighbour cell/frequency. UE send measurement report when it is in or out of the configured area scope.

Implementation Example 4:

LocationTriggerConfig-r17 ::= SEQUENCE {
longitude-Threshold1-r17      OCTET STRING,
longitude-Threshold2-r17      OCTET STRING,
latitude-Threshold1-r17       OCTET STRING,
latitude-Threshold2-r17       OCTET STRING,
hysteresis-r17                Hysteresis-r17,
timeToTrigger                 TimeToTrigger
}

The IE Hysteresis is a parameter used within the entry and leave condition of an location triggered reporting condition. The actual value is field value*0.5 km.

The LocationTriggerConfig can be configured for the serving cell/frequency or the neighbour cell/frequency. The UE can send a measurement report when one or more of the following event happens:

Event 1: UE is in the area scope configured for the serving cell/frequency.

Event 2: UE is out of the area scope configured for the serving cell/frequency.

Event 3: UE is in the area scope configured for the neighbour cell/frequency.

Event 4: UE is out of the area scope configured for the serving cell/frequency and is in the area scope configured for the neighbour cell/frequency.

Implementation example 5: New MeasTriggerQuantity, Hysteresis, and/or MeasTriggerQuantityOffset based on the area scope are defined.

MeasTriggerQuantity ::=       CHOICE {
rsrp                          RSRP-Range,
rsrq                          RSRQ-Range,
sinr                          SINR-Range,
areascope                     Area-Scope
}
MeasTriggerQuantityOffset ::= CHOICE {
rsrp                          INTEGER (−30..30),
rsrq                          INTEGER (−30..30),
sinr                          INTEGER (−30..30),
areascope                     Area-Scope
}
Hysteresis ::=    SEQUENCE {
areaScope   Area-Scope
}
Area-Scope ::=  SEQUENCE {
refPointCoordinates           OCTET STRING,
radius                        Radius-Range
}
Radius-Range ::=          INTEGER (0..XX)
Area-Scope ::=  SEQUENCE {
areaScope  SEQUENCE (SIZE (1..maxNrofCoordinates)) OF Coordinate
}
Area-Scope ::=   SEQUENCE {
areaScope  SEQUENCE (SIZE (1..maxNrofTAIs)) OF TAI
}
Area-Scope ::=   SEQUENCE {
longitude-Threshold1-r17   OCTET STRING,
longitude-Threshold2-r17  OCTET STRING,
latitude-Threshold1-r17   OCTET STRING,
latitude-Threshold2-r17   OCTET STRING,
}

The MeasTriggerQuantity, Hysteresis, and/or MeasTriggerQuantityOffset based on the area scope can be configured in the following events that triggers measurement report:

Event A1: Serving becomes better than absolute threshold.

Event A2: Serving becomes worse than absolute threshold.

Event A3: Neighbour becomes amount of offset better than PCell/PSCell.

Event A4: Neighbour becomes better than absolute threshold.

Event A5: PCell/PSCell becomes worse than absolute threshold1 AND Neighbour/SCell becomes better than another absolute threshold2.

Event A6: Neighbour becomes amount of offset better than SCell.

Event B1: Neighbour becomes better than absolute threshold.

Event B2: PCell becomes worse than absolute threshold1 AND Neighbour becomes better than another absolute threshold2.

Time Range along with hysteresis as Measurement Report Triggering Condition

In some implementations, the measurement report triggering condition can be configured as a time range along with hysteresis. Examples of the time range configured are discussed in the below.

Implementation Example 1:

The time range is configured as two thresholds (upper bound and lower bound) of UTC time

TimeTriggerConfig-r17 ::=	SEQUENCE {
time-Threshold1-r17	TimeInfoUTC,
time-Threshold2-r17	TimeInfoUTC,
hysteresis-r17	Hysteresis-r17,
timeToTrigger	TimeToTrigger
}
TimeInfoUTC	SEQUENCE {
timeInfoUTC	INTEGER (0..549755813887),
dayLightSavingTime	BIT STRING (SIZE (2))	OPTIONAL, -- Need R
leapSeconds	INTEGER (−127..128)	OPTIONAL, -- Need R
localTimeOffset	INTEGER (−63..64)	OPTIONAL -- Need R
}	OPTIONAL, -- Need R
Hysteresis ::=	INTEGER (0..XX)

The IE Hysteresis is a parameter used within the entry and leave condition of an location triggered reporting condition. The actual value is field value*0.1 ms.

Implementation Example 2:

The time range is configured as a start time and a duration.

TimeTriggerConfig-r17 ::=	SEQUENCE {
startTime-r17	TimeInfoUTC,
duration-r17     INTEGER (0..XX),
hysteresis-r17	Hysteresis-r17,
timeToTrigger	TimeToTrigger
}
TimeInfoUTC	SEQUENCE {
timeInfoUTC	INTEGER (0..549755813887),
dayLightSavingTime	BIT STRING (SIZE (2))	OPTIONAL,
-- Need R
leapSeconds	INTEGER (−127..128)	OPTIONAL,
-- Need R
localTimeOffset	INTEGER (−63..64)	OPTIONAL
-- Need R
}	OPTIONAL,
-- Need R
Hysteresis ::=     INTEGER (0..XX)

The IE Hysteresis is a parameter used within the entry and leave condition of an location triggered reporting condition. The actual value is field value*0.1 ms.

The actual value for duration-r17 is the field value*0.5 ms.

The TimeTriggerConfig can be configured for the serving cell/frequency or the neighbour cell/frequency. UE send measurement report when one or more of the following event happens:

Event 1: UE is in the time range configured for the serving cell/frequency.

Event 2: UE is out of the time range configured for the serving cell/frequency.

Event 3: UE is in the time range configured for the neighbour cell/frequency.

Event 4: UE is out of the time range configured for the serving cell/frequency and is in the time range configured for the neighbour cell/frequency.

Implementation Example 3:

New MeasTriggerQuantity, Hysteresis, and/or MeasTriggerQuantityOffset based on the time range are defined.

MeasTriggerQuantity ::=	CHOICE {
rsrp	RSRP-Range,
rsrq	RSRQ-Range,
sinr	SINR-Range,
timeRange	Time-Range
}
MeasTriggerQuantityOffset ::=	CHOICE {
rsrp	INTEGER (−30..30),
rsrq	INTEGER (−30..30),
sinr	INTEGER (−30..30),
timeRange	Time-Range
}
Hysteresis ::=    SEQUENCE {
timeRange	Time-Range
}
Time-Range ::=   SEQUENCE {
time-Threshold1-r17	TimeInfoUTC,
time-Threshold2-r17	TimeInfoUTC
}
Time-Range ::=   SEQUENCE {
startTime-r17	TimeInfoUTC,
duration-r17	INTEGER (0..XX)
}
TimeInfoUTC	SEQUENCE {
timeInfoUTC	INTEGER (0..549755813887),
dayLightSavingTime	BIT STRING (SIZE (2))	OPTIONAL,
-- Need R
leapSeconds	INTEGER (−127..128)	OPTIONAL,
-- Need R
localTimeOffset	INTEGER (−63..64)	OPTIONAL
-- Need R
}	OPTIONAL,
-- Need R

The actual value for duration-r17 is the field value*0.5 ms.

The MeasTriggerQuantity, Hysteresis, and/or MeasTriggerQuantityOffset based on the time range can be configured in the following events that triggers measurement report:

Event A1: Serving becomes better than absolute threshold.

Event A2: Serving becomes worse than absolute threshold.

Event A3: Neighbour becomes amount of offset better than PCell/PSCell.

Event A4: Neighbour becomes better than absolute threshold.

Event A5: PCell/PSCell becomes worse than absolute threshold1 AND Neighbour/SCell becomes better than another absolute threshold2.

Event A6: Neighbour becomes amount of offset better than SCell.

Event B1: Neighbour becomes better than absolute threshold.

Event B2: PCell becomes worse than absolute threshold1 AND Neighbour becomes better than another absolute threshold2.

Measurement report triggering condition as area scope or time range that can be configured per UE or per measurement object (MO)

The measurement report triggering condition as an area scope or time range can be configured per UE or per measurement object (MO). The measurement report triggering condition as an area scope or time range can be configured per UE in MeasConfig.

The following implementations can be considered when configuring the measurement report triggering condition as an area scope or time range per MO:

Implementation 1: New report type “locationTriggered” or “timeTriggered” is introduced in, for example, Report ConfigNR.

Implementation 2: The area scope or time range is introduced as an additional report condition in, for example, ReportConfigNRExt-r17.

Implementation 3: The area scope or time range is introduced as an additional event for the event triggered measurement report in, for example, EventTriggerConfig.

The following examples can be considered for the per UE configuration.

-- ASN1START
-- TAG-MEASCONFIG-START
MeasConfig ::=                 SEQUENCE {
measObjectToRemoveList         MeasObjectToRemoveList
OPTIONAL, -- Need N
measObjectToAddModList         MeasObjectToAddModList
OPTIONAL, -- Need N
reportConfigToRemoveList       ReportConfigToRemoveList
OPTIONAL, -- Need N
reportConfigToAddModList       ReportConfigToAddModList
OPTIONAL, -- Need N
measIdToRemoveList             MeasIdToRemoveList
OPTIONAL, -- Need N
measIdToAddModList             MeasIdToAddModList
OPTIONAL, -- Need N
s-MeasureConfig                CHOICE {
ssb-RSRP                       RSRP-Range,
csi-RSRP                       RSRP-Range
}
OPTIONAL, -- Need M
quantityConfig                 QuantityConfig
OPTIONAL, -- Need M
measGapConfig                  MeasGapConfig
OPTIONAL, -- Need M
measGapSharingConfig           MeasGapSharingConfig
OPTIONAL, -- Need M
...,
[[
interFrequencyConfig-NoGap-r16 ENUMERATED {true}
OPTIONAL -- Need R
]] ,
[[
locationTriggered-r17          LocationTriggeredConfig-r17
]]
[[
timeTriggered-r17              TimeTriggeredConfig-r17
]]
}
MeasObjectToRemoveList ::=     SEQUENCE (SIZE (1..maxNrofObjectId)) OF MeasObjectId
MeasIdToRemoveList ::=         SEQUENCE (SIZE (1..maxNrofMeasId)) OF MeasId
ReportConfigToRemoveList ::=   SEQUENCE (SIZE (1..maxReportConfigId)) OF ReportConfigId
-- TAG-MEASCONFIG-STOP
-- ASN1STOP

The following examples can be considered for the per MO configuration.

Example 1 (Corresponding to Implementation 1 that introduces a new report type “locationTriggered.”)

ReportConfigNR ::=     SEQUENCE {
reportType             CHOICE {
periodical             PeriodicalReportConfig,
eventTriggered         EventTriggerConfig,
...,
reportCGI              ReportCGI,
reportSFTD             ReportSFTD-NR,
condTriggerConfig-r16  CondTriggerConfig-r16,
cli-Periodical-r16     CLI-PeriodicalReportConfig-r16,
cli-EventTriggered-r16 CLI-EventTriggerConfig-r16,
locationTriggered-r17  LocationTriggeredConfig-r17,
timeTriggered-r17      TimeTriggeredConfig-r17
}
}

Example 2 (Corresponding to Implementation 2 that introduces the area scope as an additional report configuration.)

ReportConfigNR ::=        SEQUENCE {
reportType                CHOICE {
periodical                PeriodicalReportConfig,
eventTriggered            EventTriggerConfig,
...,
reportCGI                 ReportCGI,
reportSFTD                ReportSFTD-NR,
condTriggerConfig-r16     CondTriggerConfig-r16,
cli-Periodical-r16        CLI-PeriodicalReportConfig-r16,
cli-EventTriggered-r16    CLI-EventTriggerConfig-r16
}
}
ReportConfigNRExt-r17 ::= SEQUENCE {
locationTriggered-r17     LocationTriggeredConfig-r17,
timeTriggered-r17         TimeTriggeredConfig-r17
}

Example 3 (Corresponding to Implementation 3 that introduces the area scope as an additional event triggered measurement report)

EventTriggerConfig::=         SEQUENCE {
eventId                       CHOICE {
eventA1                       SEQUENCE {
a1-Threshold                  MeasTriggerQuantity,
reportOnLeave                 BOOLEAN,
hysteresis                    Hysteresis,
timeToTrigger                 TimeToTrigger
},
eventA2                       SEQUENCE {
a2-Threshold                  MeasTriggerQuantity,
reportOnLeave                 BOOLEAN,
hysteresis                    Hysteresis,
timeToTrigger                 TimeToTrigger
},
eventA3                       SEQUENCE {
a3-Offset                     MeasTriggerQuantityOffset,
reportOnLeave                 BOOLEAN,
hysteresis                    Hysteresis,
timeToTrigger                 TimeToTrigger,
useWhiteCellList              BOOLEAN
},
eventA4                       SEQUENCE {
a4-Threshold                  MeasTriggerQuantity,
reportOnLeave                 BOOLEAN,
hysteresis                    Hysteresis,
timeToTrigger                 TimeToTrigger,
useWhiteCellList              BOOLEAN
},
eventA5                       SEQUENCE {
a5-Threshold1                 MeasTriggerQuantity,
a5-Threshold2                 MeasTriggerQuantity,
reportOnLeave                 BOOLEAN,
hysteresis                    Hysteresis,
timeToTrigger                 TimeToTrigger,
useWhiteCellList              BOOLEAN
},
eventA6                       SEQUENCE {
a6-Offset                     MeasTriggerQuantityOffset,
reportOnLeave                 BOOLEAN,
hysteresis                    Hysteresis,
timeToTrigger                 TimeToTrigger,
useWhiteCellList              BOOLEAN
},
... },
rsType                        NR-RS-Type,
reportInterval                ReportInterval,
reportAmount                  ENUMERATED {r1, r2, r4, r8, r16, r32, r64, infinity},
reportQuantityCell            MeasReportQuantity,
maxReportCells                INTEGER (1..maxCellReport),
reportQuantityRS-Indexes      MeasReportQuantity
OPTIONAL, -- Need R
maxNrofRS-IndexesToReport     INTEGER (1..maxNrofIndexesToReport)
OPTIONAL, -- Need R
includeBeamMeasurements       BOOLEAN,
reportAddNeighMeas            ENUMERATED {setup}
OPTIONAL, -- Need R
...,
[[
measRSSI-ReportConfig-r16     MeasRSSI-ReportConfig-r16
OPTIONAL, -- Need R
useT312-r16      BOOLEAN
OPTIONAL, -- Need M
includeCommonLocationInfo-r16 ENUMERATED {true}
OPTIONAL, -- Need R
includeBT-Meas-r16     SetupRelease {BT-NameList-r16}
OPTIONAL, -- Need M
includeWLAN-Meas-r16   SetupRelease {WLAN-NameList-r16}
OPTIONAL, -- Need M
includeSensor-Meas-r16   SetupRelease {Sensor-NameList-r16}
OPTIONAL, -- Need M
]]
[[
locationTriggered-r17         LocationTriggeredConfig-r17
]]
[[
timeTriggered-r17      TimeTriggeredConfig-r17
]]
}

Relationship Between Measurement Report Triggering Condition as Area Scope or Time Range and Other measurement Reporting Triggering Conditions

The relationship between the measurement report triggering condition as an area scope and the periodical measurement report triggering condition or the triggering condition based on RSRP/RSRQ/SINR will be discussed.

Implementation 1: The measurement report triggering condition as an area scope or time range is configured separately from the periodical measurement report triggering condition or the triggering condition based on RSRP/RSRQ/SINR. When the measurement report triggering condition as an area scope or time range is configured for a UE or a measurement object, neither the periodical measurement report triggering condition nor the triggering condition based on RSRP/RSRQ/SINR shall be configured.

Implementation 2: The measurement report triggering condition as an area scope or time range is configured together with the periodical measurement report triggering condition or the triggering condition based on RSRP/RSRQ/SINR.

Option 2-1: The measurement report triggering condition as an area scope is configured together with the periodical measurement report triggering condition.

Option 2-1-1: UE triggers measurement report when both the measurement report triggering condition as an area scope or time range and the periodical measurement report triggering condition is satisfied. Thus, UE only sends periodical measurement report when UE is in the configured area scope or time range or out of the configured area or time range.

Option 2-1-2: UE triggers measurement report when either the measurement report triggering condition as an area scope or time range and the periodical measurement report triggering condition is satisfied.

Option 2-2: The measurement report triggering condition as an area scope or time range is configured together with the the triggering condition based on RSRP/RSRQ/SINR.

Option 2-2-1: UE triggers measurement report when both of the measurement report triggering condition as an area scope or time range and the triggering condition based on RSRP/RSRQ/SINR is satisfied.

• • Example 1: UE triggers measurement report when the triggering condition based on RSRP/RSRQ/SINR is satisfied and UE moves in or out of the configured area or time range.
  • Example 2: UE triggers measurement report when UE is in or out of the configured area or time range and the triggering condition based on RSRP/RSRQ/SINR is satisfied.

Option 2-2-2: UE triggers measurement report when either of the measurement report triggering condition as an area scope or time range and the triggering condition based on RSRP/RSRQ/SINR is satisfied.

Option 2-3: The measurement report triggering condition as an area scope or time range is configured together with the triggering condition based on RSRP/RSRQ/SINR and the periodical measurement report triggering condition.

Option 2-3-1: UE triggers measurement report when all of the measurement report triggering condition as an area scope or time range, the triggering condition based on RSRP/RSRQ/SINR and the periodical measurement report triggering condition is satisfied.

Option 2-3-2: UE triggers measurement report when one of the measurement report triggering condition as an area scope or time range, the triggering condition based on RSRP/RSRQ/SINR, and the periodical measurement report triggering condition is satisfied.

The triggering condition based on RSRP/RSRQ/SINR, the triggering condition based on area scope, and/or triggering condition based on time range mentioned above can be configured for the serving cell/frequency and/or the neighbouring cell/frequency. The triggering condition configured for a certain frequency can be evaluated base on the best cell in this frequency.

Relationship Between Measurement Report Triggering Condition as Area Scope and Measurement Report Triggering Condition as time range.

Measurement report triggering condition as area scope and measurement report triggering condition as time range can be configured together for the same UE, measurement object, cell or frequency. The measurement report will be sent when all the triggering conditions are satisfied or any one from them is satisfied. In the measurement report, UE may report the event or condition or type of the triggering event (e.g. location based, time based, RSRP/RSRQ/SINR based or periodical) that triggers this report, e.g. when multiple measurement triggering events or conditions have been configured.

When different types of triggering conditions (e.g. location based, time based, periodical and RSRP/RSRQ/SINR based) are configured together for the same UE, measurement object, cell or frequency, they can be configured as one combined event. For example, the following event can be configured:

Event 1: UE is in the configured scope of the serving cell and the RSRP of the serving cell is larger than a threshold.

Multiple types of triggering conditions can also be configured as separate events. For example, the following events have been defined and UE triggers the measurement report when all of them are satisfied or any one from them is satisfied:

Event 2: UE is in the configured scope of the serving cell.

Event 3: The RSRP of the serving cell is larger than a threshold.

Event 4: UE is in the time range configured for the serving cell.

The triggering condition expressed as area scope or time range can also be configured as execution condition for conditional handover (CHO). It may be configured together with the existing CHO execution condition (i.e. A3 or A5, A3+A3, A3+A5, A5+A5). UE performs CHO when all the configured execution conditions are satisfied.

The implementations and examples of the wireless communication method disclosed above can facilitate measurement information reporting. FIG. 5 shows an example method for a measurement configuration and reporting based on some implementations of the disclosed technology. The method 500 is performed by a network device. At 510, the network device transmits, to a user device, at least one of measurement configuration information for configuring measurement parameters or measurement reporting information including a measurement report triggering condition. In some implementations, at least one of the measurement configuration information and the measurement reporting information is included in a system information or a dedicated radio resource control signaling. In some implementations, the measurement configuration information includes at least one of measurement gap configuration or SMTC (SSB based measurement timing configuration) configuration for a specific network scenario, a specific frequency, a specific cell or a specific satellite/high altitude platform station (HAPS). In some implementations, the specific network scenario includes non-terrestrial network (NTN), air-to-ground (ATG), network served by satellites or high altitude platform station (HAPS), network served by low earth orbit (LEO)/Non-LEO satellite or network served by geostationary (GEO)/Non-GEO satellite. At 520, the network device receives, from the user device, a measurement report including results of measurements according to the measurement reporting information.

The implementations as discussed above will apply to a wireless communication. FIG. 6 shows an example of a wireless communication system (e.g., a 5G or NR cellular network) that includes a BS 620 and one or more user equipment (UE) 611, 612 and 613. In some embodiments, the UEs access the BS (e.g., the network) using implementations of the disclosed technology 631, 632, 633), which then enables subsequent communication (641, 642, 643) from the BS to the UEs. The UE may be, for example, a smartphone, a tablet, a mobile computer, a machine to machine (M2M) device, an Internet of Things (IoT) device, and so on.

FIG. 7 shows an example of a block diagram representation of a portion of an apparatus. An apparatus 710 such as a base station or a user device which may be any wireless device (or UE) can include processor electronics 720 such as a microprocessor that implements one or more of the techniques presented in this document. The apparatus 710 can include transceiver electronics 730 to send and/or receive wireless signals over one or more communication interfaces such as antenna 740. The apparatus 710 can include other communication interfaces for transmitting and receiving data. The apparatus 710 can include one or more memories (not explicitly shown) configured to store information such as data and/or instructions. In some implementations, the processor electronics 720 can include at least a portion of transceiver electronics 730. In some embodiments, at least some of the disclosed techniques, modules or functions are implemented using the apparatus 710.

Additional features of the above-described methods/techniques that may be preferably implemented in some implementations are described below using a clause-based description format.

1. A method of wireless communication, the method performed by a user device and comprising: receiving, from a network device, at least one of measurement configuration information for configuring measurement parameters or measurement reporting information including a measurement report triggering condition; performing measurements based on the measurement configuration information received from the network device; and performing an evaluation for the measurement event according to the measurement report triggering condition.

2. The method of clause 1, wherein the at least one of the measurement configuration information or the measurement reporting information is included in a system information or a dedicated radio resource control signaling.

3. The method of clause 1, wherein the measurement configuration information includes at least one of measurement gap configuration or SMTC (SSB based measurement timing configuration) configuration for a specific network scenario, a specific frequency, a specific cell or a specific satellite/high altitude platform station (HAPS).

4. The method of clause 3, wherein the specific network scenario includes non-terrestrial network (NTN), air-to-ground (ATG), network served by satellites or high altitude platform station (HAPS), network served by low earth orbit (LEO)/Non-LEO satellite or network served by geostationary (GEO)/Non-GEO satellite.

5. The method of clause 1, further comprising: triggering to report the measurement report when the measurement report triggering condition is satisfied.

6. The method of clause 3, wherein the measurement gap configuration includes one of the followings: 1) a default measurement gap length or a limited measurement gap length, 2) an extended measurement gap length, 3) an indicator showing whether extra compensation is needed in a measurement gap, 4) an extra measurement gap offset used to delay a start of the measurement gap, 5) an indicator indicating reference timing of the measurement gap as a timing on satellite/HAPS serving a primary cell (PCell) or a timing on a NTN/HAPS GW serving the PCell, or 6) a start timing reference used to indicate a start point of the measurement gap.

7. The method of clause 3, wherein the SMTC configuration includes one of followings: 1) a default or limited SMTC configuration, 2) an indicator showing whether extra compensation is needed in the SMTC, 3) an extra measurement gap offset used to delay a start of the SMTC, 4) an indicator showing reference timing of the SMTC is a timing on satellite/HAPS serving a primary cell (PCell) or a timing on a NTN/HAPS GW serving the PCell, or 5) a start timing reference used to indicate a start point of the SMTC.

8. The method of clause 1, wherein the measurement triggering condition is an area scope configured for a serving cell, a serving frequency, a neighbour cell, or a neighboring frequency, and wherein a measurement report is sent when the user device is in or out of the area scope.

9. The method of clause 8, wherein the area scope is configured as one of followings: 1) a distance between UE and the satellite/HAPS, cell center or reference point, 2) a single reference location and a radius associated with the reference location, 3) a list of location coordinates, 4) a list of tracking area identifiers (TAIs) of terrestrial network (TN) cells, 5) two pairs of high and low thresholds for longitude and latitude, or 6) either low or high threshold along with a offset for longitude and latitude.

10. The method of clause 1, wherein the measurement triggering condition is a time range configured for a serving cell, a serving frequency, a neighbour cell, or a neighbor frequency, and wherein a measurement report is sent when the user device is in or out of the time range.

11. The method of clause 1, wherein the measurement report triggering condition is configured together with a periodical measurement report triggering condition or an event based triggering condition based on reference signal received power (RSRP), reference signal received quality (RSRQ), or signal to noise and interference ratio (SINR).

12. The method of clause 1, further comprising: triggering a measurement report to be sent when one of the measurement report triggering condition, a periodical measurement report triggering condition or an event based triggering condition based on reference signal received power (RSRP), reference signal received quality (RSRQ), or signal to noise and interference ratio (SINR) is satisfied.

13. The method of clause 1, further compromising: triggering a measurement report to be sent when all of the measurement report triggering condition, a periodical measurement report triggering condition, and an event based triggering condition based on reference signal received power (RSRP), reference signal received quality (RSRQ), or signal to noise and interference ratio (SINR) are satisfied.

14. A method of wireless communication, the method performed by a network device and comprising: transmitting, to a user device, at least one of measurement configuration information for configuring measurement parameters or measurement reporting information including a measurement report triggering condition; and receiving, from the user device, a measurement report including results of measurements according to the measurement reporting information.

15. The method of clause 14, wherein the at least one of the measurement configuration information and the measurement reporting information is included in a system information or a dedicated radio resource control signaling.

16. The method of clause 14, wherein the measurement configuration information includes at least one of measurement gap configuration or SMTC (SSB based measurement timing configuration) configuration for a specific network scenario, a specific frequency, a specific cell or a specific satellite/high altitude platform station (HAPS).

17. The method of clause 16, wherein the specific network scenario includes non-terrestrial network (NTN), air-to-ground (ATG), network served by satellites or high altitude platform station (HAPS), network served by low earth orbit (LEO)/Non-LEO satellite or network served by geostationary (GEO)/Non-GEO satellite.

18. The method of clause 16, wherein the measurement gap configuration includes one of the followings: 1) a default measurement gap length or a limited measurement gap length, 2) an extended measurement gap length, 3) an indicator showing whether extra compensation is needed in a measurement gap, 4) an extra measurement gap offset used to delay a start of the measurement gap, 5) an indicator indicating reference timing of the measurement gap as a timing on satellite/HAPS serving a primary cell (PCell) or a timing on a NTN/HAPS GW serving the PCell, or 6) a start timing reference used to indicate a start point of the measurement gap.

19. The method of clause 16, wherein the SMTC configuration includes one of followings: 1) a default or limited SMTC configuration, 2) an indicator showing whether extra compensation is needed in the SMTC, 3) an extra measurement gap offset used to delay a start of the SMTC, 4) an indicator showing reference timing of the SMTC is a timing on satellite/HAPS serving a primary cell (PCell) or a timing on a NTN/HAPS GW serving the PCell, or 5) a start timing reference used to indicate a start point of the SMTC.

20. The method of clause 14, wherein the measurement triggering condition is an area scope configured for a serving cell, a serving frequency, a neighbour cell, or a neighboring frequency, and wherein a measurement report is sent from the user device when the user device is in or out of the area scope.

21. The method of clause 20, wherein the area scope is configured as one of followings: 1) a distance between UE and the satellite/HAPS, cell center or reference point, 2) a single reference location and a radius associated with the reference location, 3) a list of location coordinates, 4) a list of tracking area identifiers (TAIs) of terrestrial network (TN) cells, 5) two pairs of high and low thresholds for longitude and latitude, or 6) either low or high threshold along with a offset for longitude and latitude.

22. The method of clause 14, wherein the measurement triggering condition is a time range configured for a serving cell, a serving frequency, a neighbour cell, or a neighbor frequency, and wherein a measurement report is sent from the user device when the user device is in or out of the time range.

23. The method of clause 14, wherein the measurement report triggering condition is configured together with a periodical measurement report triggering condition or an event based triggering condition based on reference signal received power (RSRP), reference signal received quality (RSRQ), or signal to noise and interference ratio (SINR).

24. A communication apparatus comprising a processor configured to implement a method recited in any one or more of clauses 1 to 23.

25. A computer readable medium having code stored thereon, the code, when executed, causing a processor to implement a method recited in any one or more of clauses 1 to 23.

In some embodiments, a base station may be configured to implement some or all of the base station side techniques described in the present document.

It is intended that the specification, together with the drawings, be considered exemplary only, where exemplary means an example and, unless otherwise stated, does not imply an ideal or a preferred embodiment. As used herein, the use of “or” is intended to include “and/or”, unless the context clearly indicates otherwise.

Some of the embodiments described herein are described in the general context of methods or processes, which may be implemented in one embodiment by a computer program product, embodied in a computer-readable medium, including computer-executable instructions, such as program code, executed by computers in networked environments. A computer-readable medium may include removable and non-removable storage devices including, but not limited to, Read Only Memory (ROM), Random Access Memory (RAM), compact discs (CDs), digital versatile discs (DVD), etc. Therefore, the computer-readable media can include a non-transitory storage media. Generally, program modules may include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. Computer- or processor-executable instructions, associated data structures, and program modules represent examples of program code for executing steps of the methods disclosed herein. The particular sequence of such executable instructions or associated data structures represents examples of corresponding acts for implementing the functions described in such steps or processes.

Some of the disclosed embodiments can be implemented as devices or modules using hardware circuits, software, or combinations thereof. For example, a hardware circuit implementation can include discrete analog and/or digital components that are, for example, integrated as part of a printed circuit board. Alternatively, or additionally, the disclosed components or modules can be implemented as an Application Specific Integrated Circuit (ASIC) and/or as a Field Programmable Gate Array (FPGA) device. Some implementations may additionally or alternatively include a digital signal processor (DSP) that is a specialized microprocessor with an architecture optimized for the operational needs of digital signal processing associated with the disclosed functionalities of this application. Similarly, the various components or sub-components within each module may be implemented in software, hardware or firmware. The connectivity between the modules and/or components within the modules may be provided using any one of the connectivity methods and media that is known in the art, including, but not limited to, communications over the Internet, wired, or wireless networks using the appropriate protocols.

While this document contains many specifics, these should not be construed as limitations on the scope of an invention that is claimed or of what may be claimed, but rather as descriptions of features specific to particular embodiments. Certain features that are described in this document in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable sub-combination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a sub-combination or a variation of a sub-combination. Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results.

Only a few implementations and examples are described and other implementations, enhancements and variations can be made based on what is described and illustrated in this disclosure.

Claims

1. A method of wireless communication, the method performed by a user device and comprising: receiving, from a network device, at least one of measurement configuration information for configuring measurement parameters or measurement reporting information including a measurement report triggering condition;performing measurements based on the measurement configuration information received from the network device; andperforming an evaluation for a measurement event according to the measurement report triggering condition,wherein the measurement triggering condition is i) an area scope configured for a serving cell, a serving frequency, a neighbour cell, or a neighboring frequency, or ii) a time range configured for a serving cell, a serving frequency, a neighbour cell, or a neighbor frequency, andwherein a measurement event is considered as triggered when the user device is in or out of the area scope or the time range.

2. The method of claim 1, wherein the at least one of the measurement configuration information or the measurement reporting information is included in a system information or a dedicated radio resource control signaling.

3. The method of claim 1, wherein the measurement configuration information includes at least one of a measurement gap configuration or a SMTC (SSB based measurement timing configuration) configuration for a specific network scenario, a specific frequency, a specific cell, a specific satellite, or a high altitude platform station (HAPS).

4. The method of claim 3, wherein the specific network scenario includes a non-terrestrial network (NTN), an air-to-ground (ATG), a network served by satellites or a high altitude platform station (HAPS), a network served by a low earth orbit (LEO) or a Non-LEO satellite, or a network served by a geostationary (GEO) or a Non-GEO satellite.

5. The method of claim 1, further comprising: triggering to report the measurement event when the measurement report triggering condition is satisfied.

6. The method of claim 3, wherein the measurement gap configuration includes one of followings: 1) a default measurement gap length or a limited measurement gap length, 2) an extended measurement gap length, 3) an indicator showing whether extra compensation is needed in a measurement gap, 4) an extra measurement gap offset used to delay a start of the measurement gap, 5) an indicator indicating reference timing of the measurement gap as a timing on a satellite or high altitude platform station (HAPS) serving a primary cell (PCell) or a timing on a non-terrestrial network (NTN) or HAPS gateway (GW) serving the PCell, or 6) a start timing reference used to indicate a start point of the measurement gap, or wherein the SMTC configuration includes one of followings:1) a default or limited SMTC configuration, 2) an indicator showing whether extra compensation is needed in the SMTC, 3) an extra measurement gap offset used to delay a start of the SMTC, 4) an indicator showing reference timing of the SMTC is the timing on the satellite or HAPS serving the primary cell (PCell) or the timing on the NTN or HAPS GW serving the PCell, or 5) a start timing reference used to indicate a start point of the SMTC.

7. The method of claim 1, wherein the area scope is configured as one of followings: 1) a distance between UE and one of a satellite, a high altitude platform station (HAPS), a cell center, or a reference point, 2) a single reference location and a radius associated with the reference location, 3) a list of location coordinates, 4) a list of tracking area identifiers (TAIs) of terrestrial network (TN) cells, 5) two pairs of high and low thresholds for longitude and latitude, or 6) either a low or high threshold along with an offset for longitude and latitude.

8. The method of claim 1, wherein the measurement report triggering condition is configured together with a periodical measurement report triggering condition or an event based triggering condition based on reference signal received power (RSRP), reference signal received quality (RSRQ), or signal to noise and interference ratio (SINR).

9. The method of claim 1, further comprising: triggering a measurement report to be sent when one or all of the measurement report triggering condition, a periodical measurement report triggering condition or an event based triggering condition based on reference signal received power (RSRP), reference signal received quality (RSRQ), or signal to noise and interference ratio (SINR) are satisfied.

10. A method of wireless communication, the method performed by a network device and comprising: transmitting, to a user device, at least one of measurement configuration information for configuring measurement parameters or measurement reporting information including a measurement report triggering condition; andreceiving, from the user device, a measurement report including results of measurements according to the measurement reporting information,wherein the measurement triggering condition is i) an area scope configured for a serving cell, a serving frequency, a neighbour cell, or a neighboring frequency, or ii) a time range configured for a serving cell, a serving frequency, a neighbour cell, or a neighbor frequency, andwherein a measurement event is considered as triggered when the user device is in or out of the area scope or the time range.

11. The method of claim 10, wherein the at least one of the measurement configuration information or the measurement reporting information is included in a system information or a dedicated radio resource control signaling.

12. The method of claim 10, wherein the measurement configuration information includes at least one of measurement gap configuration or SMTC (SSB based measurement timing configuration) configuration for a specific network scenario, a specific frequency, a specific cell, a specific satellite, or a high altitude platform station (HAPS).

13. The method of claim 12, wherein the specific network scenario includes a non-terrestrial network (NTN), an air-to-ground (ATG), a network served by satellites or a high altitude platform station (HAPS), a network served by a low earth orbit (LEO) or Non-LEO satellite, or a network served by a geostationary (GEO) or Non-GEO satellite, or wherein the measurement gap configuration includes one of followings: 1) a default measurement gap length or a limited measurement gap length, 2) an extended measurement gap length, 3) an indicator showing whether extra compensation is needed in a measurement gap, 4) an extra measurement gap offset used to delay a start of the measurement gap, 5) an indicator indicating reference timing of the measurement gap as a timing on a satellite or high altitude platform station (HAPS) serving a primary cell (PCell) or a timing on a non-terrestrial network (NTN) or HAPS gateway (GW) serving the PCell, or 6) a start timing reference used to indicate a start point of the measurement gap, orwherein the SMTC configuration includes one of followings: 1) a default or limited SMTC configuration, 2) an indicator showing whether extra compensation is needed in the SMTC, 3) an extra measurement gap offset used to delay a start of the SMTC, 4) an indicator showing reference timing of the SMTC is the timing on the satellite or HAPS serving the primary cell (PCell) or the timing on the NTN/HAPS GW serving the PCell, or 5) a start timing reference used to indicate a start point of the SMTC.

14. The method of claim 10, wherein the area scope is configured as one of followings: 1) a distance between UE and one of a satellite, a high altitude platform station (HAPS), a cell center, or a reference point, 2) a single reference location and a radius associated with the reference location, 3) a list of location coordinates, 4) a list of tracking area identifiers (TAIs) of terrestrial network (TN) cells, 5) two pairs of high and low thresholds for longitude and latitude, or 6) either low or high threshold along with a offset for longitude and latitude.

15. The method of claim 10, wherein the measurement report triggering condition is configured together with a periodical measurement report triggering condition or an event based triggering condition based on reference signal received power (RSRP), reference signal received quality (RSRQ), or signal to noise and interference ratio (SINR).

16. A communication apparatus comprising a processor configured to implement a method including: receiving, from a network device, at least one of measurement configuration information for configuring measurement parameters or measurement reporting information including a measurement report triggering condition;performing measurements based on the measurement configuration information received from the network device; andperforming an evaluation for a measurement event according to the measurement report triggering condition,wherein the measurement triggering condition is i) an area scope configured for a serving cell, a serving frequency, a neighbour cell, or a neighboring frequency, or ii) a time range configured for a serving cell, a serving frequency, a neighbour cell, or a neighbor frequency, andwherein a measurement event is considered as triggered when the communication apparatus is in or out of the area scope or the time range.

17. The communication apparatus of claim 16, wherein the at least one of the measurement configuration information or the measurement reporting information is included in a system information or a dedicated radio resource control signaling.

18. The communication apparatus of claim 16, wherein the area scope is configured as one of followings: 1) a distance between UE and one of a satellite, a high altitude platform station (HAPS), a cell center, or a reference point, 2) a single reference location and a radius associated with the reference location, 3) a list of location coordinates, 4) a list of tracking area identifiers (TAIs) of terrestrial network (TN) cells, 5) two pairs of high and low thresholds for longitude and latitude, or 6) either low or high threshold along with a offset for longitude and latitude.

19. The communication apparatus of claim 16, wherein the measurement report triggering condition is configured together with a periodical measurement report triggering condition or an event based triggering condition based on reference signal received power (RSRP), reference signal received quality (RSRQ), or signal to noise and interference ratio (SINR).

20. The communication apparatus of claim 16, wherein triggering a measurement report to be sent when one or all of the measurement report triggering condition, a periodical measurement report triggering condition or an event based triggering condition based on reference signal received power (RSRP), reference signal received quality (RSRQ), or signal to noise and interference ratio (SINR) are satisfied.