Systems and methods for event-triggered measurement reports

Abstract

The present disclosure relates to methods and devices for event-triggered measurement reports In some embodiments, a method is performed by a User Equipment (UE) operative in a wireless communication network, which is configured with at least one L1 / L2 Triggered Mobility (LTM) candidate configuration that includes Channel State Information (CSI) 5 resources that are transmitted by an LTM candidate cell and can be measured by the UE. The UE receives a configuration from a first network node which includes at least one LTM CSI reporting configuration associated with one or more event triggering condition(s), and which instruct the UE to measure one or more CSI resources according to a configured LTM candidate configuration. When the conditions for one event are met, the UE sends one or 0 more LTM reports to the first network node according to the associated LTM CSI reporting configuration.

Description

SYSTEMS AND METHODS FOR EVENT-TRIGGERED MEASUREMENT REPORTS TECHNICAL FIELD

[0001] Embodiments of the present disclosure relate to methods and devices in communication networks, in particular methods and devices for event-triggered measurement reports.BACKGROUND

[0002] Wireless communication networks, including network nodes and radio network devices such as cellphones and smartphones, are ubiquitous in many parts of the world. These networks continue to grow in capacity and sophistication. To accommodate both more users and a wider range of types of devices that may benefit from wireless communications, the technical standards governing the operation of wireless communication networks continue to evolve. The fourth generation of network standards (4G, also known as Long Term Evolution, or LTE) has been deployed, the fifth generation (5G, also known as New Radio, or NR) is in development or the early stages of deployment, and the sixth generation (6G) is being planned. Specific technical standards defining new network features and capabilities are promulgated by the Third Generation Partnership Project (3GPP) as a series of numbered Releases, e.g., Rel. 15, Rel. 16, etc.

[0003] Both LTE and NR networks follow a “cellular” architecture, wherein a plurality of generally fixed network nodes, known as base stations (also called eNB in LTE and gNB in NR) provide wireless communication services to both fixed and mobile radio network devices, referred to generally herein as User Equipment (UE), within a coverage area, or “cell.” The term “cell” also refers to a unique logical entity providing wireless communication service; hence one base station may provide a plurality of cells.

[0004] Up through LTE, the base station (eNB) was monolithic entity. NR introduced the concept of splitting the base station (gNB) between a Central Unit (CU) and Distributed Units (DU). FIG. 1 shows this architecture 100. Access and Mobility Management Function (AMF) and / or User Plane Function (UPF) in the core network connect to base stations (gNB). Each gNB is divided into a CU and a plurality of DUs. A break between the CU and DU in the network protocol stack is commonly implemented above the Radio Link Control (RLC), with RLC, MAC, and the Physical layer (PHY) implemented in the DU, while RRC, Packet Data Convergence Protocol (PDCP) and higher layer functions are implemented in the CU.

[0005] Mobility is a fundamental aspect of wireless communication networks. As a UE moves throughout a geographic region, it will move from one cell to another. The UE periodically performs measurements of the signal strength and quality of the air interface between it and a current serving cell, as well as neighboring cells. When a neighbor cell provides a consistently higher quality channel, the network performs a “handover” procedure, passing control and servicing of the UE from the current, or “source” cell to the new, or “target” cell. Accordingly, the operation is also referred to as a “cell switch.” Ideally, a handover or cell switch procedure is performed transparently to the user, who experiences no degradation in quality of any ongoing call or data stream as the procedure is executed.

[0006] Handover has conventionally been performed by Radio Resource Control (RRC) signaling, which is a high-level signaling protocol. As such, it involves extensive signaling across the air interface, and extensive processing at the UE, which consumes battery power. Release 18 introduced a cell switch triggered by the Media Access Control (MAC) layer rather than RRC. This procedure operates at lower levels of the protocol stack (e.g., Level 1 or Level 2), and is referred to as L1 / L2 Triggered Mobility (LTM). LTM can achieve faster cell switching, with lower overhead and hence power consumption, than RRC handover.

[0007] Random Access (RA) is a procedure by which a UE initially connects to a cell of a wireless communication network. The Random Access Channel (RACH) is a logical channel dedicated to RA. Upon power-on or arriving in the coverage range of a cell, a UE receives System Information (SI) periodically broadcast by the base station, which includes synchronization signals that allow the UE to roughly synchronize its timing with the cell. The UE then performs RA, which conventionally is a 4-step process. Briefly, the UE transmits one of 64 RACH preambles e.g., Zadoff-Chu sequences), referred to as Msg. 1. A base station responds with an RA response, called Msg. 2, which includes a Timing Advance (TA) value allowing the UE to time-align its transmissions, a temporary identifier Random Access Radio Network Temporary Identifier (RA-RNTI), and an uplink grant. The UE uses this grant to transmit Msg. 3, which may include RRC signaling and / or data. Finally, the base station responds with Msg. 4, which is MAC data for Contention Resolution, and assigns a Cell Radio Network Temporary Identifier (C-RNTI) to the UE.

[0008] Release 16 introduced a 2-step RACH procedure. Both messages from the UE to the network (Msg. 1 and Msg. 3) are combined into Msg. A, and both messages from the network to the UE (Msg. 2 and Msg. 4) are combined into Msg. B.

[0009] 5G NR (in Release 18) defined L1 / L2 triggered mobility (LTM) to reduce the handover latency in the legacy L3 handover by leveraging lower layer signaling. LTM is specified as a lower layer mobility procedure in Rel-18 in which a network node (e.g., gNB) receives measurement report(s), sent by a user equipment (UE), using LI signaling. The Ll-measurement reports are utilized by network to make different mobility-related decisions such as the LTM cell switch execution to another target cell by sending an LTM cell switch MAC control element (MAC CE) command. The step-by-step process for LTM is summarized below, and depicted in the signal flow diagram 200 of FIG. 2:

[0010] 1. The UE sends Measurement report(s) for the measurements performed on one or more cells to the gNB. Based on the received measurement report(s), the gNB decides to configure one or more LTM candidate cell(s). This procedure is referred to as LTM preparation.

[0011] 2. The gNB transmits an RRC Reconfiguration message to the UE including the LTM candidate configuration(s).

[0012] 3. The UE stores the LTM candidate configuration(s) and responds to gNB with an RRC Reconfiguration Complete message.

[0013] 4a. The UE may perform an early downlink (DL) synchronization with the LTM candidate cell(s) before LTM cell switch execution. The DL pre- synchronization is performed upon reception of a “Candidate Cell TCI States Activation / Deactivation MAC CE” by the UE for the transmission configuration indication (TCI) states in the configured LTM candidate cell(s). Since the DL synchronization is already acquired before the LTM cell switch, the UE is not required to wait for performing synchronization signal block (SSB) reference signal (RS) measurements after moving to the target cell which consequently reduces the mobility interruption.

[0014] 4b. The UE may also perform uplink (UL) pre-synchronization with the LTM candidate cell(s) if it receives the physical downlink control channel (PDCCH) order for early timing advance (TA) acquisition for those candidate cells. This means that the delay occurring in the random-access procedure after the baseline L3-moblity can be reduced from the overall mobility interruption in LTM.

[0015] 5. The UE performs LI measurements on the configured LTM candidate cell(s) and transmits LI measurement reports to the gNB. LI measurement should be performed for the LTM candidate cell(s) which were configured in step 2.

[0016] 6. The gNB decides to execute cell switch to a candidate target cell and transmits a MAC CE triggering cell switch by including the candidate configuration index of the LTM target cell. The UE switches to the target cell and applies the LTM candidate configuration indicated by candidate configuration index.

[0017] 7. The UE performs the random-access procedure towards the target cell if UE does not have valid TA of the target cell. Otherwise, if the UE receives a valid TA value in LTM cell switch command using early TA acquisition method in step 4b, the UE is not required to perform random-access. Moreover, if the target cell TCI state, which is included in the LTM Cell Switch MAC CE, is different from the TCI state activated in early DL synchronization, the UE may experience some delay in synchronization with the new TCI.

[0018] 8. The UE completes the LTM cell switch procedure by sending RRC Reconfiguration Complete message to target cell. If the UE has performed a random-access procedure in step 7, the UE considers that LTM cell switch execution is successfully completed when the random-access procedure is successfully completed. For RACH-less LTM, the UE considers that LTM cell switch execution is successfully completed when the UE determines that the network has successfully received its first UL data. See 3rd Generation Partnership Project (3GPP) Technical Standard (TS) 38.300, VI 8.0.0 (2023-12); Group Radio Access Network; NR; NR and NG-RAN Overall Description; Stage 2 (Release 18).

[0019] Rel-18 LTM defines 4 different types of measurement reporting related to the LTM procedures, e.g., early synchronization, LTM cell switch, provided in LTM reporting configuration. In Rel-18 LTM, periodic reporting on physical uplink control channel (PUCCH), semi-persistent reporting on PUCCH, semi-persistent reporting on physical uplink shared channel (PUSCH), and aperiodic reporting methods are mentioned. See 3GPP TS 38.331, V18.0.0, (2023-12); Group Radio Access Network; NR; Radio Resource Control (RRC) protocol specification (Release 18). All these measurement reports are carried via uplink control information (UCI). FIG. 3 shows the LTM measurement report configurations 300 for each of these reporting types.

[0020] As indicated in the LTM CSI Reporting configuration of FIG. 3, the periodic report in LTM can only be carried via PUCCH and the associated PUCCH resource configuration for report transmission, reporting periodicity, and offset are provided via RRC configuration in the serving cell. The semi-persistent report in LTM can be carried via PUSCH or PUCCH, and the transmission of semi-persistent report is activated via MAC CE.Aperiodic report in LTM can only be carried via PUSCH and the transmission of the aperiodic LTM CSI report is polled via downlink control information (DCI). See 3GPP TS 38.331, V18.0.0, (2023-12), supra.

[0021] Measurements related enhancements for purpose of supporting LTM: [RAN2, RANI]• Measurement related enhancements are applicable to Intra-CU MCG / SCG LTM and Inter-CU MCG / SCG LTM• Specify necessary components to support event triggered LI measurement reporting [RAN2, RANI].• Specify support for CSLRS measurements for LTM procedures and enable CSLRS based beam management [RANI]• Specify CSI acquisition on candidate cell(s) based on CSI-RS before or during LTM cell switch [RANI]

[0022] As part of the “Measurements-related enhancements” in LTM, Rel-19 LTM defines “Event-triggered Ll-Reporting” in LTM to address the following issues:• Excessive energy consumption at the UE due to high reporting overhead in periodic and semi-persistent LI -report types in LTM.• Inefficient use of UL resources in periodic and semi-persistent LI -report types in LTM.• If the reporting interval in the periodic and semi -persistent LI -reports is increased in LTM to enhance energy and UL resource efficiency, it may result in handover failures and / or radio link failures (RLF) due to delayed updates in the channel quality at the network.• Aperiodic LI -report in LTM may result in RLF if the report is not requested by the network in a timely manner.

[0023] In RAN2, it has been agreed that MAC CE shall be used as a report container to carry the event-triggered LTM measurement reports. It has also been agreed to introduce the following events:• Event LTM2: Beam of serving cell becomes worse than absolute threshold;• Event LTM3: Beam of candidate cell becomes amount of offset better than beam of serving cell;• Event LTM4: Beam of candidate cell becomes better than absolute threshold;• Event LTM5: Beam of serving cell becomes worse than absolute thresholdl AND Beam of candidate cell becomes better than another absolute threshold2.

[0024] There currently exist certain challenge(s).

[0025] Event-triggered LI reporting is being standardized in Release 19. At RAN2#127 it was agreed that event-triggered LI -measurements are reported by the UE to the network via MAC CE. It has also been agreed that the UE can include the SpCell beam measurement(s), i.e., the LI -measurement on the indicated beam from serving cell, in the Ll-measurement report MAC CE as well. At RAN2#129, it has been agreed that an explicit indication can be used in the LI -measurement report MAC CE to inform the network on the fulfillment of the leaving condition(s) and indicating on the triggered beam(s), i.e., the beam(s) which meet the LTM event condition(s) for the entire TTT duration.

[0026] However, the detailed signaling aspects related to the indication of report-on-leave, SpCell measurements and triggered beam(s) are still under discussion. For example, whether the UE sends the indication on the triggered beam(s), i.e., the beam(s) which fulfill the event condition(s) for the entire TTT duration, on per beam basis or in some other format.SUMMARY

[0027] Certain aspects of the disclosure may provide solutions to these or other challenges.

[0028] In some embodiments, a method is performed by a User Equipment (UE) operative in a wireless communication network, which is configured with at least one L1 / L2 Triggered Mobility (LTM) candidate configuration that includes Channel State Information (CSI) resources that are transmitted by an LTM candidate cell and can be measured by the UE. In some embodiments, the method comprises: receiving a configuration from a first network node which includes at least one LTM CSI reporting configuration associated with one or more event triggering condition(s), and which instruct the UE to measure one or more CSI resources according to a configured LTM candidate configuration; and when the conditions for one event are met, sending one or more LTM reports to the first network node according to the associated LTM CSI reporting configuration.

[0029] In some embodiments, a method is performed by a network node operative in a wireless communication network in which a User Equipment (UE) is configured with at least one L1 / L2 Triggered Mobility (LTM) candidate configuration that includes Channel State Information (CSI) resources that are transmitted by an LTM candidate cell and can be measured by the UE. In some embodiments, the method comprises: transmitting aconfiguration from to the UE which includes at least one LTM CSI reporting configuration associated with one or more event triggering condition(s), and which instruct the UE to measure one or more CSI resources according to a configured LTM candidate configuration; and when the conditions for one event are met, receiving from the UE one or more LTM reports according to the associated LTM CSI reporting configuration.

[0030] Additional embodiments are provided herein, including UEs and network nodes configured to perform the methods discussed herein.BRIEF DESCRIPTION OF THE DRAWINGS

[0031] FIG. 1 illustrates an example cellular architecture.

[0032] FIG. 2 illustrates an example L1 / L2 triggered mobility (LTM) signaling procedure.

[0033] FIG. 3 illustrates an example of LTM measurement report configurations.

[0034] FIG. 4 illustrates an example reference signal resource identifier set.

[0035] FIGS. 5-8 illustrate Media Access Control (MAC) Control Element (CE) formats in accordance with some embodiments.

[0036] FIG. 9 is a flow chart illustrating a method in accordance with some embodiments.

[0037] FIG. 10 is a flow chart illustrating a method in accordance with some embodiments.

[0038] FIG. 11 shows an example of a communication system in accordance with some embodiments.

[0039] FIG. 12 shows a wireless device in accordance with some embodiments.

[0040] FIG. 13 shows a network node in accordance with some embodiments.

[0041] FIG. 14 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized.DETAILED DESCRIPTION

[0042] This disclosure considers several different aspects of the design of Ll-measurement report MAC CE, including:• Detailed signaling related to the transmission of the SpCell beam measurement(s).• Detailed signaling related to the indication of the triggered / non-triggered LTM candidate cell beam(s) in the LI -measurement report MAC CE.• Detailed signaling aspects for indicating the reported beam(s) which fulfil the LTM event leaving condition(s).

[0043] The embodiments disclosed herein are applicable for LTM, thus the disclosure refers to the term “L1 / L2 based inter-cell mobility (LTM)” as defined in Release 18, though it interchangeably also uses the terms L1 / L2 mobility, Ll-mobility, LI based mobility, L1 / L2-centric inter-cell mobility, L1 / L2 inter-cell mobility Ll / L2-Triggered Mobility (LTM), Lower-layer triggered Mobility or simply LTM, as more widely used. The basic principle is that the UE receives a lower layer signaling from the network (e.g., a MAC Control Element - MAC CE) indicating to the UE a change (or switch or activation) of its serving cell (i.e., PCell or PSCell), wherein a lower layer signaling is a message / signaling carried via a lower layer protocol, which may be referred as a L1 / L2 inter-cell mobility execution command or LTM cell switch command. Before the UE receives the LTM cell switch command, the UE is configured by the network with one or more LTM candidate cell configurations (e.g., reception of an RRC Reconfiguration message, with at least one LTM candidate cell configuration). An LTM candidate cell configuration may include parameters in the IE CellGroupConfig per candidate cell and / or an embedded RRC Reconfiguration per LTM candidate cell. An LTM configuration may include one or multiple of the following type of elements where each element contains a configuration of one aspect of LTM, for example as follows:• LTM candidate cell configuration(s),• Inter-CU LTM candidate cell configuration(s),• Lower layer information, such as physical layer configuration, MAC layer configuration or RLC layer configuration, Cell Group configuration, serving cell configuration.• Higher layer information, such as RRC protocol parameters, such as timer values, PDCP layer configuration, radio bearer configuration or measurement configuration • Configuration of measurements for LTM• Configuration for measurement reports for LTM• CSI resource configuration(s) for LTM• CSI report configuration for LTM• Configurations of early synchronization procedures, such as• Configurations for DL pre-sync for LTM, such as configurations for early TCI state activation• Configurations for UL pre-sync for LTM, such as configurations for reception of PDCCH ordered triggered preamble transmission and reception of TA.• Configurations for the execution of an LTM cell switch procedure for a given LTM candidate cell configuration or inter-CU LTM candidate cell configuration (e.g., whether to perform random access procedure, whether to perform RLC reestablishment, or MAC reset, or PDCP recovery), a timer value, configured UL grants, dedicated RA preambles.• A configuration which the UE needs to start to operate accordingly when it performs an LTM cell switch procedure to an LTM candidate cell which is controlled by a different base station, e.g. gNB, from the current source base station e.g. serving gNB of the UE.• Information to perform security key refresh, e.g. the RRC IE MasterKeyUpdate or a RRC IE RadioBearerConfig that includes SecurityConfig withSecurity AlgorithmConfig.• Indication to perform a full configuration, e.g. the RRC field fullConfig.• Indication to perform L2 re-establishment, such as an indication to perform PDCP reestablishment for one or multiple bearers.

[0044] An LTM candidate cell is a cell the UE may be configured to perform lower layer measurements, such as Layer 1 (LI) reference signal received power (RSRP), on the synchronization signal block (SSB) and / or channel state information reference signal (CSI-RS), e.g., LTM CSI measurements. Lower layer measurements are measurements reported to support lower layer procedures like beam management, TCI state activations / deactivations, early timing advance (TA) acquisition, and link adaptation, and they aren't filtered based on Layer 3 (L3) parameters, though there may (or may not) be some filtering of these measurements based on lower layer parameters. The UE reports these measurements, and the network takes educated decision on which beam (e.g., TCI state) and / or cell the UE is to be switched to. In the case of an LTM fast failure recovery, when a failure is detected, the UE selects a cell and when the cell is an LTM candidate cell the UE does not have to perform reestablishment, but instead performs an LTM cell switch towards the selected LTM candidate cell e.g., by applying the LTM candidate cell configuration associated to the selected LTM candidate cell.

[0045] An LTM cell switch procedure or LTM execution procedure may be triggered in the UE by reception of an LTM cell switch command (e.g., LTM Cell Switch MAC CE), or alternatively, triggered in response to the detection of a failure (in case of LTM fast failure recovery). The text refers to an LTM candidate cell, which is a cell with which the UE isconfigured when configured with Ll / L2-triggered mobility. That is a cell to which the UE can move in an LTM cell switch procedure, upon reception of an LTM cell switch command. These cells may also be termed as candidate cell(s), candidates, candidate target cell, implied target cell, mobility candidates, non-serving cells, additional cells, or deactivated cells etc. An LTM candidate cell might also pertain to a candidate cell in a 5G Radio Access Technology such as NR or a future 6G Radio Access Technology.

[0046] The reference signals on which lower layer measurements are performed are provided in the LTM CSI-SSB Resource Set, under LTM CSI Resource Configuration. A resource identifier for a reference signal resource, such as a serving cell or an LTM candidate cell SSB-Index or CSI-RS-Resource ID, uniquely identifies the resource in the LTM configuration and among all the serving and LTM candidate cells. The resource identifier can be understood by both the UE and the serving gNB. In the context of LTM, the reference signal resource identifier is described by the field LTM-CSI-SSB-ResourceSet in TS 38.331 vl 8.2.0 is shown in field 400 in FIG. 4.

[0047] In the example, the ith position of the list in the field Itm-CSI-SSB-ResourceList indicates the SSB ID of the reference signal resource, while the same ith position of the list in the field Itm-CandidateldList indicates to which LTM candidate configuration index the SSB belongs.

[0048] According to some embodiments, the ‘measurement configuration’ may correspond to an LTM resource configuration (and / or a resource set configuration) which the UE receives in an RRC Reconfiguration (or RRC Resume) message, wherein each ‘LTM resource’ to be measured and to be possibly reported (depending on further rules the embodiment describes) corresponds to a Reference Signal indication (e.g., an SSB index and / or a CSI-RS resource indication) and its associated LTM Candidate Identity (ID), to indicate a specific RS (e.g., SSB index) of an LTM candidate.

[0049] According to some embodiments, a measurement configuration (e.g., resource configuration, resource set configuration) is associated with a reporting configuration (or LTM reporting configuration), by including within a reporting configuration an indication of a resource configuration (or a resource set configuration). For example, when the reporting configuration is configured in the IE LTM- ReportConfig, the instance of the IE LTM-ReportConfig includes a resource configuration (or resource set configuration) identifier, pointing to the associated measurement configuration.

[0050] According to some embodiments, the ‘measurement reporting configuration’, or simply reporting configuration correspond to an LTM reporting configuration the UE receives in an RRC Reconfiguration (or RRC Resume) message, in which an event for triggering an LTM measurement report (e.g. over MAC CE and / or UCI) is configured. An event, for example, can be defined as “a measurement quantity (e.g., LI RSRP) of an SSB (or CSLRS or beam) of an LTM candidate cell becomes an offset better than the same measurement quantity (e.g. LI RSRP) of a serving SSB (e.g. SSB of the PCell associated to an activated and / or indicated TCI state)”. The actual SSBs of the LTM candidate cell(s) to be measured are configured in the measurement configuration (or resource set or resource configuration) associated to that LTM reporting configuration. It could also be said that the event definition is like one or more conditions to be evaluated. As per Rel-18 LTM, the different types of measurement reports in LTM include periodic reporting, semi-persistent reporting, and aperiodic reporting. However, Rel-19 also introduces event-triggered report type in LTM which is transmitted upon the fulfilment of the associated event condition(s).

[0051] An LI event type in LTM is a class of events, e.g. LTM2, LTM3, LTM4, LTM5. An LI event or event instance is an instance of an event type, e.g. an LTM3 event configured with certain parameters like offset, threshold, time-to-trigger (TTT) etc., and associated with an LTM resource configuration. An LI event identifier uniquely identifies an event instance and can be understood by both the UE and the serving gNB. The condition(s) defined in the LTM events are also referred to as triggering condition(s), event condition(s), LTM event condition(s), event trigger condition(s) or simply trigger condition(s) in the text.

[0052] A measurement quantity refers to one of:• Ll-RSRP from SS-RSRP or CSI-RSRP, or• LI- signal-to-interference and noise ratio (SINR) from SS-SINR or CSLSINR, or • LI- reference signal received quality (RSRQ) from SS-RSRQ or CSI-RSRQ,

[0053] The measurement quantity value refers to the value which the UE reports for the measurement quantity of an SSB or a CSLRS resource. In Rel-18 LTM Ll-reporting, the measurement quantity is primarily the SS-RSRP for the LTM measurement resource with the highest measurement and differential SS-RSRP value(s) with respect to the highest SS-RSRP measurement. A triggering measurement quantity value for an event is a measurement quantity value that meets the conditions for the event throughout the TTT duration and hence triggers the UE to send the measurement report.

[0054] The disclosure uses different terms for LTM reports, which include lower layer report, lower layer measurement report, lower layer reporting, Ll-report, LI -measurement report, LI event triggered measurement report, LI -reporting, LTM measurement report interchangeably without any loss of meaning. For the event-triggered LTM reports, the text uses the terms event-triggered Ll-report, event-triggered LI -measurement report, event-triggered lower layer measurement report, event-triggered lower layer reporting, event-triggered LI -reporting, LI -measurement report, LI event triggered measurement report, LTM measurement report, LTM event triggered measurement report interchangeably.

[0055] The disclosure uses the term “cell” to identify a location (or coverage) on which the UE is located. However, the term “cell” can also be exchanged without any loss of meaning with the terms “radio resources”, “beams”, “TCI state”, or “tracking reference signal (TRS)”. This is just to clarify that this disclosure does not target specifically a scenario where there is a cell, but rather when a UE uses a set of source radio resources and need to switch to a target set of radio resources. In such a case, radio resource can also identify a set of configurations, field, parameters, or ASN.l structures or IES. The disclosure also uses the terms like non-fulfilling beams or non-fulfilling reference signals which are the SSB-RS / CSI-RS which do not fulfil the condition(s) defined for the given LTM event. Moreover, the disclosure uses the term “first network node” to refer to a source cell / serving cell / source gNB-DU / S-DU.

[0056] In the context of the disclosure a “triggered cell” refers to a triggered LTM candidate cell, which is an LTM candidate cell for which a beam, or Reference Signal (e.g. CSLRS, SSB) or Synchronization Signal (e.g., SSB) transmitted in a beam, fulfill a triggering condition for transmitting a measurement report. A triggered LTM candidate cell may have been configured as part of the LTM resource configuration.

[0057] In the context of the disclosure a “event-triggered beam / triggered beam / triggering beam” refers to a beam of a triggered LTM candidate cell i.e., a beam, or Reference Signal (e.g. CSI-RS, SSB) or Synchronization Signal (e.g. SSB) transmitted in a beam, which fulfills a triggering condition for transmitting an LTM measurement report. A triggered beam may have been configured as part of the LTM resource configuration and associated to an LTM candidate cell.

[0058] In the context of the disclosure, a “non-triggered cell” refers to a non-triggered LTM candidate cell, which is a cell for which any beam, or Reference Signal (e.g. CSLRS, SSB) or Synchronization Signal (e.g. SSB) transmitted in a beam, does not fulfill thetriggering condition with which the UE is configured, for transmitting an LTM measurement report. A non-triggered LTM candidate cell may have been configured as part of the LTM resource configuration.

[0059] In the context of the disclosure, a “non-triggered beam” refers to a beam, or Reference Signal (e.g., CSLRS, SSB) or Synchronization Signal (e.g., SSB) transmitted in a beam, which does not fulfill a triggering condition for transmitting an LTM measurement report. A non-triggered beam may have been configured as part of the LTM resource configuration and associated to an LTM candidate cell. In other words, for a given LTM measurement report, triggered to be transmitted according to a specific triggering condition configured in a specific reporting configuration, the non-triggered beam is a beam which does not fulfill that condition.

[0060] In the context of the disclosure, the terms “LTM”, or “LTM candidate cell”, or “LTM event”, “LTM measurement configuration (e.g., LTM CSI-SSB Resource Set)” or “LTM reporting configuration” may be used. However, all the embodiments and solutions described may be equally applied to the case of when LTM is “conditional”. In this case, the main difference between an LTM candidate cell and a conditional LTM (CLTM) candidate cell is when the LTM candidate cell configuration includes execution conditions, the UE can trigger an LTM cell switch procedure when such conditions are fulfilled. Therefore, in this case the embodiments described herein may be applied also to “CLTM”, “CLTM candidate cell”, “CLTM event”, “CLTM resource configuration” or “CLTM reporting configuration”.

[0061] In the context of the disclosure, the term “report-on-leave” is used to refer to the measurement report being transmitted when the LTM candidate cell beam fulfills the leaving condition(s) associated to the LTM event. In other words, “report-on-leave” is triggered when one or more LTM candidate cell beam(s) fulfill the leaving condition(s) associated to an LTM event.

[0062] FIGS. 5-8 illustrate possible MAC CE formats according to the aspects of the present disclosure.

[0063] FIG. 5 illustrates a bitmap in the beginning of an example MAC CE 500 to indicate which of the reported beams fulfill entering vs leaving conditions (16 bits per indication), total of 16-48 bits increased size of MAC CE depending on whether both entering and leaving conditions are reported in the same MAC CE. The “Exx” bit indicates the fulfilment of the LTM event entering condition(s) for the reported beam and the “Lxx” bit indicates the fulfilment of LTM event leaving condition(s) for the given reported beam.

[0064] FIG. 6 illustrates an example MAC CE 600 and illustrates an aspect in which one bit per beam is reported to indicate entering, leaving and fulfillment of execution condition (3 bits per beam, which is available in the above proposal, total of 0 bits increased MAC CE). The “F” bit indicates whether the given reported beam is the triggered beam, i.e., fulfilled the LTM event condition(s), “E” bit indicates that the LTM event entering condition(s) are fulfilled and the “L” bit indicates that the LTM event leaving condition(s) are fulfilled for the given reported beam.

[0065] FIG. 7 illustrates an example MAC CE 700 and illustrates an aspect in which one bit per beam reported to indicate whether a beam is a triggering beam and one bit that depending on if it is a triggering beam indicates entering or leaving, or in the case of the beam is not triggering is just a reserved bit. (2 bits per beam, which is available in the above proposal, total of 0 bits increased MAC CE).

[0066] FIG. 8 illustrates an example MAC CE 800 and illustrates an aspect in which 4 bits indicate the number of beams which fulfilled the leaving condition(s). These beams are included right before the beams of the serving cell. For instance, if L=2, this means that the 2 beams before the RSRP of the serving cell are beams which fulfilled the leaving condition.

[0067] FIG. 9 depicts steps in a method 900, performed by a User Equipment (UE) (e.g., 1112, 1200) operative in a wireless communication network, which is configured with at least one L1 / L2 Triggered Mobility (LTM) candidate configuration that includes Channel State Information (CSI) resources that are transmitted by an LTM candidate cell and can be measured by the UE. A configuration is received from a first network node (e.g., 1110, 1300) which includes at least one LTM CSI reporting configuration associated with one or more event triggering condition(s), and which instructs the UE to measure one or more CSI resources according to a configured LTM candidate configuration (block 902). When the conditions for one event are met (block 904), one or more LTM reports are sent to the first network node according to the associated LTM CSI reporting configuration (block 906).

[0068] FIG. 10 depicts steps in a method 1000, performed by a network node (e.g., 1110, 1300) operative in a wireless communication network, which is configured with at least one L1 / L2 Triggered Mobility (LTM) candidate configuration that includes Channel State Information (CSI) resources that are transmitted by an LTM candidate cell and can be measured by the UE. A configuration is transmitted to a UE (e.g., 1112, 1200) which includes at least one LTM CSI reporting configuration associated with one or more event triggering condition(s), and which instructs the UE to measure one or more CSI resources according to aconfigured LTM candidate configuration (block 1002). When the conditions for one event are met (block 1004), one or more LTM reports are received from the UE according to the associated LTM CSI reporting configuration (block 1006).

[0069] One or more embodiments (e.g., method 900, method 1000) can include one or more of the following features. In some embodiments, the LTM candidate cell resource identifier(s) fulfil(s) the entering, or the leaving condition(s) associated to the LTM event which triggered the LI -measurement report for an entire time-to-trigger, (TTT,) duration. In some embodiments, the LTM candidate cell resource identifier(s) fulfil(s) the entering, or the leaving condi tion(s) associated to the LTM event which triggered the LI -measurement report for the duration less than a time-to-trigger, (TTT,) duration. In some embodiments, a bitmap is used to indicate whether a reported beam is an event-triggered or a non-triggered beam and whether the reported beam fulfills the entering condition(s) or the leaving condition(s) for the given LTM event for the entire TTT duration or less than TTT duration. In some embodiments, a single-bit per LI -measurement report Media Access Control, (MAC,) Control Element, (,CE) is used to indicate whether a Multi-Radio, (MR,) MAC CE is transmitted due to the fulfilment of the entering condition(s) or the leaving condition(s) associated to the LTM event. In some embodiments, the indicated beam measurement for the SpCell is included at a specific location in the LI -measurement report MAC CE. In some embodiments, the indicated beam measurement for the SpCell is included at the end of the MR MAC CE. In some embodiments, two bits are used to indicate whether the reported beam is an event-triggered or a non-triggered beam and whether the given reported beam fulfills the entering condition(s) or the leaving condition(s) for the given LTM event. In some embodiments: 00 indicates that the reported beam is an event-triggered beam; 01 indicates that the reported beam is a non-triggered beam; 10 indicates that the reported beam fulfilled the leaving condition; and 11 is reserved for future uses. In some embodiments, a predetermined combination of the two bits is used to indicate whether the reported beam is an event-triggered beam, non-triggered beam, or a beam which fulfilled the leaving condition(s).

[0070] One or more embodiments (e.g., method 900, method 1000) can include one or more of the following features. In some embodiments, if the measurement report is sent because a beam fulfilled the leaving condition(s), the UE includes in the measurement report only beams which have fulfilled the leaving condition. In some embodiments, the number of beams fulfilling the leaving condition(s) is indicated explicitly in the measurement report and such beams are located at a specific location in the LI -measurement report MAC CE. Insome embodiments, the number of beams fulfilling the leaving condition(s) is indicated at the beginning of the MAC CE report. In some embodiments, the number of beams fulfilling the leaving condition(s) is indicated explicitly in the measurement report and such beams are located immediately before or after the beam of the serving cell. In some embodiments, if there are five beams fulfilling the leaving condition(s) and the indicated beam of the serving cell is located on the Octet N of the measurement report MAC CE, within this MAC CE there is an indication that the number of beams fulfilling the leaving condition is five and these five beams are located starting from Octet N-5. In some embodiments, if there are five beams fulfilling the leaving condition(s), then those beams are reported in the last five Octets of the LI -measurement report MAC CE and the LI -measurement for the indicated beam in the serving cell is reported at N-5 Octet.

[0071] One or more embodiments (e.g., method 900, method 1000) can include one or more of the following features. In some embodiments, if the measurement report is sent because a beam fulfilled the entering condition(s), the UE includes in the measurement report only beams which have fulfilled the entering condition. In some embodiments, the UE includes a bit to indicate if all beams in this measurement report are included because their entering conditions have been triggered. In some embodiments, the UE includes a bit to indicate if all beams in this measurement report are included because their leaving conditions have been triggered.

[0072] FIG. 11 shows an example of a communication system 1100 in accordance with some embodiments.

[0073] In the example, the communication system 1100 includes a telecommunication network 1102 that includes an access network 1104, such as a radio access network (RAN), and a core network 1106, which includes one or more core network nodes 1108. The access network 1104 includes one or more access network nodes, such as network nodes 1110a and 1110b (one or more of which may be generally referred to as network nodes 1110), or any other similar 3rdGeneration Partnership Project (3GPP) access nodes or non-3GPP access points. Moreover, as will be appreciated by those of skill in the art, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network 1102 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunicationnetwork 1102 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network 1102, including one or more network nodes 1110 and / or core network nodes 1108.

[0074] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface.Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an O-2 interface defined by the O-RAN Alliance or comparable technologies. The network nodes 1110 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 1112a, 1112b, 1112c, and 1112d (one or more of which may be generally referred to as UEs 1112) to the core network 1106 over one or more wireless connections.

[0075] Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 1100 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 1100 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0076] The UEs 1112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with thenetwork nodes 1110 and other communication devices. Similarly, the network nodes 1110 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 1112 and / or with other network nodes or equipment in the telecommunication network 1102 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network 1102.

[0077] In the depicted example, the core network 1106 connects the network nodes 1110 to one or more host computing systems, such as host 1116. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 1106 includes one more core network nodes (e.g., core network node 1108) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 1108.Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0078] The host 1116 may be under the ownership or control of a service provider other than an operator or provider of the access network 1104 and / or the telecommunication network 1102. The host 1116 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0079] As a whole, the communication system 1100 of FIG. 11 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard(e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.

[0080] In some examples, the telecommunication network 1102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 1102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 1102. For example, the telecommunications network 1102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC) / Massive loT services to yet further UEs.

[0081] In some examples, the UEs 1112 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 1104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 1104.Additionally, a UE may be configured for operating in single- or multi-RAT or multistandard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

[0082] In the example, the hub 1114 communicates with the access network 1104 to facilitate indirect communication between one or more UEs (e.g. , UE 1112c and / or 1112d) and network nodes (e.g. , network node 1110b). In some examples, the hub 1114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 1114 may be a broadband router enabling access to the core network 1106 for the UEs. As another example, the hub 1114 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 1110, or by executable code, script, process, or other instructions in the hub 1114. As another example, the hub 1114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, thehub 1114 may be a content source. For example, for a UE that is a VR device, display, loudspeaker, or other media delivery device, the hub 1114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 1114 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 1114 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0083] The hub 1114 may have a constant / persistent or intermittent connection to the network node 1110b. The hub 1114 may also allow for a different communication scheme and / or schedule between the hub 1114 and UEs (e.g. , UE 1112c and / or 1112d), and between the hub 1114 and the core network 1106. In other examples, the hub 1114 is connected to the core network 1106 and / or one or more UEs via a wired connection. Moreover, the hub 1114 may be configured to connect to an M2M service provider over the access network 1104 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 1110 while still connected via the hub 1114 via a wired or wireless connection. In some embodiments, the hub 1114 may be a dedicated hub -that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 1110b. In other embodiments, the hub 1114 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 1110b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0084] FIG. 12 shows a UE 1200 in accordance with some embodiments. The UE 1200 presents additional details of some embodiments of the UE 1112 of FIG. 1. As used herein, a UE refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage / playback device, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), an Augmented Reality (AR) or Virtual Reality (VR) device, wireless customer-premise equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things(NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0085] A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g. , a smart power meter).

[0086] The UE 1200 includes processing circuitry 1202 that is operatively coupled via a bus 1204 to an input / output interface 1206, a power source 1208, a memory 1210, a communication interface 1212, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in FIG. 12. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0087] The processing circuitry 1202 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 1210. The processing circuitry 1202 may be implemented as one or more hardware-implemented state machines e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 1202 may include multiple central processing units (CPUs).

[0088] In the example, the input / output interface 1206 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, orany combination thereof. An input device may allow a user to capture information into the UE 1200. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

[0089] In some embodiments, the power source 1208 is structured as a battery or battery pack. Other types of power sources, such as an external power source e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source 1208 may further include power circuitry for delivering power from the power source 1208 itself, and / or an external power source, to the various parts of the UE 1200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 1208. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 1208 to make the power suitable for the respective components of the UE 1200 to which power is supplied.

[0090] The memory 1210 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 1210 includes one or more application programs 1214, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 1216. The memory 1210 may store, for use by the UE 1200, any of a variety of various operating systems or combinations of operating systems.

[0091] The memory 1210 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-linememory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 1210 may allow the UE 1200 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 1210, which may be or comprise a device-readable storage medium.

[0092] The processing circuitry 1202 may be configured to communicate with an access network or other network using the communication interface 1212. The communication interface 1212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 1222. The communication interface 1212 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 1218 and / or a receiver 1220 appropriate to provide network communications e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 1218 and receiver 1220 may be coupled to one or more antennas e.g., antenna 1222) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0093] In the illustrated embodiment, communication functions of the communication interface 1212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / internet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0094] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 1212, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random e.g., to even out the load from reporting from several sensors), in response to a triggering event e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0095] As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0096] A UE, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE 1200 shown in FIG. 12.

[0097] As yet another specific example, in an loT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another UE and / or a network node. TheUE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0098] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0099] FIG. 13 shows a network node 1300 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).

[0100] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node) and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0101] Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), basetransceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0102] The network node 1300 includes a processing circuitry 1302, a memory 1304, a communication interface 1306, and a power source 1308. The network node 1300 may be composed of multiple physically separate components e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 1300 comprises multiple separate components e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 1300 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 1304 for different RATs) and some components may be reused (e.g., a same antenna 1310 may be shared by different RATs). The network node 1300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1300, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 1300.

[0103] The processing circuitry 1302 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other network node 1300 components, such as the memory 1304, to provide network node 1300 functionality.

[0104] In some embodiments, the processing circuitry 1302 includes a system on a chip (SOC). In some embodiments, the processing circuitry 1302 includes one or more of radio frequency (RF) transceiver circuitry 1312 and baseband processing circuitry 1314. In some embodiments, the radio frequency (RF) transceiver circuitry 1312 and the basebandprocessing circuitry 1314 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 1312 and baseband processing circuitry 1314 may be on the same chip or set of chips, boards, or units.

[0105] The memory 1304 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computerexecutable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 1302. The memory 1304 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 1302 and utilized by the network node 1300. The memory 1304 may be used to store any calculations made by the processing circuitry 1302 and / or any data received via the communication interface 1306. In some embodiments, the processing circuitry 1302 and memory 1304 is integrated.

[0106] The communication interface 1306 is used in wired or wireless communication of signaling and / or data between a network node, access network, and / or UE. As illustrated, the communication interface 1306 comprises port(s) / terminal(s) 1316 to send and receive data, for example to and from a network over a wired connection. The communication interface 1306 also includes radio front-end circuitry 1318 that may be coupled to, or in certain embodiments a part of, the antenna 1310. Radio front-end circuitry 1318 comprises filters 1320 and amplifiers 1322. The radio front-end circuitry 1318 may be connected to an antenna 1310 and processing circuitry 1302. The radio front-end circuitry may be configured to condition signals communicated between antenna 1310 and processing circuitry 1302. The radio front-end circuitry 1318 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 1318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1320 and / or amplifiers 1322. The radio signal may then be transmitted via the antenna 1310. Similarly, when receiving data, the antenna 1310 may collect radio signals which are then converted into digital data by the radio front-end circuitry1318. The digital data may be passed to the processing circuitry 1302. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0107] In certain alternative embodiments, the network node 1300 does not include separate radio front-end circuitry 1318, instead, the processing circuitry 1302 includes radio front-end circuitry and is connected to the antenna 1310. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1312 is part of the communication interface 1306. In still other embodiments, the communication interface 1306 includes one or more ports or terminals 1316, the radio front-end circuitry 1318, and the RF transceiver circuitry 1312, as part of a radio unit (not shown), and the communication interface 1306 communicates with the baseband processing circuitry 1314, which is part of a digital unit (not shown).

[0108] The antenna 1310 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 1310 may be coupled to the radio front-end circuitry 1318 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 1310 is separate from the network node 1300 and connectable to the network node 1300 through an interface or port.

[0109] The antenna 1310, communication interface 1306, and / or the processing circuitry 1302 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 1310, the communication interface 1306, and / or the processing circuitry 1302 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

[0110] The power source 1308 provides power to the various components of network node 1300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 1308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 1300 with power for performing the functionality described herein. For example, the network node 1300 may be connectable to an external power source e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby theexternal power source supplies power to power circuitry of the power source 1308. As a further example, the power source 1308 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0111] Embodiments of the network node 1300 may include additional components beyond those shown in FIG. 13 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 1300 may include user interface equipment to allow input of information into the network node 1300 and to allow output of information from the network node 1300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1300. In some embodiments providing a core network node, such as core network node 108 of FIG. 11, some components, such as the radio front-end circuitry 1318 and the RF transceiver circuitry 1312 may be omitted.

[0112] FIG. 14 is a block diagram illustrating a virtualization environment 1400 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 1400 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 1400 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface. Virtualization may facilitate distributed implementations of a network node, UE, core network node, or host.

[0113] Applications 1402 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in thevirtualization environment Q400 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0114] Hardware 1404 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 1406 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 1408a and 1408b (one or more of which may be generally referred to as VMs 1408), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 1406 may present a virtual operating platform that appears like networking hardware to the VMs 1408.

[0115] The VMs 1408 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 1406. Different embodiments of the instance of a virtual appliance 1402 may be implemented on one or more of VMs 1408, and the implementations may be made in different ways.Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

[0116] In the context of NFV, a VM 1408 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 1408, and that part of hardware 1404 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 1408 on top of the hardware 1404 and corresponds to the application 1402.

[0117] Hardware 1404 may be implemented in a standalone network node with generic or specific components. Hardware 1404 may implement some functions via virtualization. Alternatively, hardware 1404 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 1410, which, among others, oversees lifecycle management of applications 1402. In some embodiments, hardware 1404 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may becoupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 1412 which may alternatively be used for communication between hardware nodes and radio units.

[0118] Although the computing devices described herein (e.g., UEs, network nodes) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0119] Aspects of the present disclosure present numerous advantages over the prior art, and may achieve one or more of the following technical effects. A more flexible and detailed report format for the LI -measurement MAC CE report is defined. The network is better informed on different LI -measurement aspects and therefore can make better handover decisions. Also, the report format for the LI -measurement report MAC CE can be applied to all the given LTM events.

[0120] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.

Claims

CLAIMS1. A method, performed by a User Equipment, UE, (1112, 1200) operative in a wireless communication network, which is configured with at least one L1 / L2 Triggered Mobility, LTM, candidate configuration that includes Channel State Information, CSI, resources that are transmitted by an LTM candidate cell and can be measured by the UE, the method comprising:receiving a configuration from a first network node (1110, 1300) which includes at least one LTM CSI reporting configuration associated with one or more event triggering condition(s), and which instruct the UE to measure one or more CSI resources according to a configured LTM candidate configuration; and when the conditions for one event are met, sending one or more LTM reports to the first network node according to the associated LTM CSI reporting configuration.

2. The method of claim 1, wherein the LTM candidate cell resource identifier(s) fulfil(s) the entering, or the leaving condition(s) associated to the LTM event which triggered the Ll-measurement report for an entire time-to-trigger, TTT, duration.

3. The method of claim 1, wherein the LTM candidate cell resource identifier(s) fulfil(s) the entering, or the leaving condition(s) associated to the LTM event which triggered the Ll-measurement report for the duration less than a time-to-trigger, TTT, duration.

4. The method of any one of claims 1-3, wherein a bitmap is used to indicate whether a reported beam is an event-triggered or a non-triggered beam and whether the reported beam fulfills the entering condition(s) or the leaving condition(s) for the given LTM event for the entire TTT duration or less than TTT duration.

5. The method of any one of claims 1-4, wherein a single-bit per LI -measurement report Media Access Control, MAC, Control Element, CE, is used to indicate whether a MultiRadio, MR, MAC CE is transmitted due to the fulfilment of the entering condition(s) or the leaving condition(s) associated to the LTM event.

6. The method of any one of claims 1-5, wherein the indicated beam measurement for the SpCell is included at a specific location in the LI -measurement report MAC CE7. The method of claim 6 wherein the indicated beam measurement for the SpCell is included at the end of the MR MAC CE.

8. The method of any one of claims 1-5, wherein two bits are used to indicate whether the reported beam is an event-triggered or a non-triggered beam and whether the given reported beam fulfills the entering condition(s) or the leaving condition(s) for the given LTM event.

9. The method of claim 8 wherein:00 indicates that the reported beam is an event-triggered beam;01 indicates that the reported beam is a non-triggered beam;10 indicates that the reported beam fulfilled the leaving condition; and11 is reserved for future uses.

10. The method of claim 8 wherein a predetermined combination of the two bits is used to indicate whether the reported beam is an event-triggered beam, non-triggered beam, or a beam which fulfilled the leaving condition(s).

11. The method of any one of claims 1-5, wherein if the measurement report is sent because a beam fulfilled the leaving condition(s), the UE includes in the measurement report only beams which have fulfilled the leaving condition.

12. The method of any one of claims 1-5, wherein the number of beams fulfilling the leaving condition(s) is indicated explicitly in the measurement report and such beams are located at a specific location in the LI -measurement report MAC CE.

13. The method of claim 12 wherein the number of beams fulfilling the leaving condition(s) is indicated at the beginning of the MAC CE report.

14. The method of any one of claims 1-5, wherein the number of beams fulfilling the leaving condition(s) is indicated explicitly in the measurement report and such beams are located immediately before or after the beam of the serving cell.

15. The method of claim 8 wherein, if there are five beams fulfilling the leaving condition(s) and the indicated beam of the serving cell is located on the Octet N of the measurement report MAC CE, within this MAC CE there is an indication that the number of beams fulfilling the leaving condition is five and these five beams are located starting from Octet N-5.

16. The method of claim 8 wherein, if there are five beams fulfilling the leaving condition(s), then those beams are reported in the last five Octets of the LI -measurement report MAC CE and the LI -measurement for the indicated beam in the serving cell is reported at N-5 Octet.

17. The method of any one of claims 1-5, wherein if the measurement report is sent because a beam fulfilled the entering condition(s), the UE includes in the measurement report only beams which have fulfilled the entering condition.

18. The method of any one of claims 1-5, wherein the UE includes a bit to indicate if all beams in this measurement report are included because their entering conditions have been triggered.

19. The method of any one of claims 1-5, wherein the UE includes a bit to indicate if all beams in this measurement report are included because their leaving conditions have been triggered.

20. A method, performed by a network node (1110, 1300) operative in a wireless communication network in which a User Equipment, UE, (1112, 1200) is configured with at least one L1 / L2 Triggered Mobility, LTM, candidate configuration that includes Channel State Information, CSI, resources that are transmitted by an LTM candidate cell and can be measured by the UE, the method comprising:transmitting a configuration from to the UE which includes at least one LTM CSI reporting configuration associated with one or more event triggering condition(s), and which instruct the UE to measure one or more CSI resources according to a configured LTM candidate configuration; andwhen the conditions for one event are met, receiving from the UE one or more LTMreports according to the associated LTM CSI reporting configuration.

21. The method of claim 20, wherein the LTM candidate cell resource identifier(s) fulfil(s) the entering, or the leaving condition(s) associated to the LTM event which triggered the Ll-measurement report for an entire time-to-trigger, TTT, duration.

22. The method of claim 20, wherein the LTM candidate cell resource identifier(s) fulfil(s) the entering, or the leaving condition(s) associated to the LTM event which triggered the Ll-measurement report for the duration less than a time-to-trigger, TTT, duration.

23. The method of any one of claims 20-22, wherein a bitmap is used to indicate whether a reported beam is an event-triggered or a non-triggered beam and whether the reported beam fulfills the entering condition(s) or the leaving condition(s) for the given LTM event for the entire TTT duration or less than TTT duration.

24. The method of any one of claims 20-23, wherein a single-bit per LI -measurement report Media Access Control, MAC, Control Element, CE, is used to indicate whether a Multi-Radio, MR, MAC CE is transmitted due to the fulfilment of the entering condition(s) or the leaving condition(s) associated to the LTM event.

25. The method of any one of claims 20-24, wherein the indicated beam measurement for the SpCell is included at a specific location in the LI -measurement report MAC CE26. The method of claim 25 wherein the indicated beam measurement for the SpCell is included at the end of the MR MAC CE.

27. The method of any one of claims 20-24, wherein two bits are used to indicate whether the reported beam is an event-triggered or a non-triggered beam and whether the given reported beam fulfills the entering condition(s) or the leaving condition(s) for the given LTM event.

28. The method of claim 27 wherein:00 indicates that the reported beam is an event-triggered beam;3101 indicates that the reported beam is a non-triggered beam;10 indicates that the reported beam fulfilled the leaving condition; and11 is reserved for future uses.

29. The method of claim 27 wherein a predetermined combination of the two bits is used to indicate whether the reported beam is an event-triggered beam, non-triggered beam, or a beam which fulfilled the leaving condition(s).

30. The method of any one of claims 20-24, wherein if the measurement report is sent because a beam fulfilled the leaving condition(s), the UE includes in the measurement report only beams which have fulfilled the leaving condition.

31. The method of any one of claims 20-24, wherein the number of beams fulfilling the leaving condition(s) is indicated explicitly in the measurement report and such beams are located at a specific location in the LI -measurement report MAC CE.

32. The method of claim 31 wherein the number of beams fulfilling the leaving condition(s) is indicated at the beginning of the MAC CE report.

33. The method of any one of claims 20-24, wherein the number of beams fulfilling the leaving condition(s) is indicated explicitly in the measurement report and such beams are located immediately before or after the beam of the serving cell.

34. The method of claim 27 wherein, if there are five beams fulfilling the leaving condition(s) and the indicated beam of the serving cell is located on the Octet N of the measurement report MAC CE, within this MAC CE there is an indication that the number of beams fulfilling the leaving condition is five and these five beams are located starting from Octet N-5.

35. The method of claim 27 wherein, if there are five beams fulfilling the leaving condition(s), then those beams are reported in the last five Octets of the LI -measurement report MAC CE and the LI -measurement for the indicated beam in the serving cell is reported at N-5 Octet.

36. The method of any one of claims 20-24, wherein if the measurement report is sent because a beam fulfilled the entering condition(s), the UE includes in the measurement report only beams which have fulfilled the entering condition.

37. The method of any one of claims 20-24, wherein the UE includes a bit to indicate if all beams in this measurement report are included because their entering conditions have been triggered.

38. The method of any one of claims 20-24, wherein the UE includes a bit to indicate if all beams in this measurement report are included because their leaving conditions have been triggered.

39. A user equipment (1112, 1200) for performing an L1 / L2 Triggered Mobility (LTM) cell switch procedure, comprising:processing circuitry configured to perform any of the steps of any one of claims 1-19;andpower supply circuitry configured to supply power to the processing circuitry.

40. A network node (1110, 1300) for transmitting an L1 / L2 Triggered Mobility (LTM) configuration to a user equipment, UE, (1112, 1200) and receiving from the UE an LTM report, the network node comprising:processing circuitry configured to perform any of the steps of any one of claims 20-38;andpower supply circuitry configured to supply power to the processing circuitry.

41. A user equipment, UE, (1112, 1200) for performing an L1 / L2 Triggered Mobility (LTM) cell switch procedure, the UE comprising:an antenna configured to send and receive wireless signals;radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry;the processing circuitry being configured to perform any of the steps of any one of claims 1-19;an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry;an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; anda battery connected to the processing circuitry and configured to supply power to the UE.

Images