Patent Description:
In 5th Generation (<NUM>) New Radio (NR), a UE can communicate with a Radio Access Network (RAN) node via one or more radio links operating over one or more carriers in the millimetre-wave (mmW) part of the electromagnetic spectrum, namely utilising frequencies between <NUM> and <NUM> - known as Frequency Range <NUM> (FR2). The use of such high frequencies is subject to MPE limits stipulated by regulatory bodies such as the Federal Communications Commission (FCC). User Equipment (UE) is capable of transmitting electromagnetic radiation at frequencies and power levels that could, if not restricted, exceed MPE limits.

In order to ensure compliance with MPE limits for UE uplink (UL) signals transmitted over a <NUM> NR FR2 carrier, the UE may restrict its uplink transmission power. However, this can cause a reduction of the UL transmission power of the UE to a level that is insufficient to maintain an adequate connection link over the <NUM> NR FR2 carrier. Due to this, when a UE is operating over a <NUM> NR FR2 carrier, upon detection of an MPE event (such as a detection of a user's body part proximal to the UE's antenna and in a propagation pathway from the UE's antenna to a RAN node thereby necessitating a restriction of the uplink transmission power to ensure compliance with MPE limits), the RAN node may transition the UE from operating over the <NUM> NR FR2 carrier to operating over a different carrier e.g. a Long Term Evolution (LTE) carrier or a <NUM> Frequency Range <NUM> (FR1) carrier that uses sub <NUM> frequencies (i.e. ranging from <NUM> to <NUM>) for which MPE limits do not apply.

In some circumstances, it may be desirable to seek to restore the UE to operating over the <NUM> NR FR2 carrier.

Certain examples of the disclosure seek to provide an improved process for restoring UE operation over a previously used carrier that had been subject to an MPE event. Certain examples of the disclosure seek to avoid/reduce attempts to restore a UE to operation over the previously used carrier whilst the MPE event is still active for the carrier. Certain examples seek to reduce signalling overhead and wasted resources in attempting to re-establish UE operation over the previously used carrier, as well as hasten the re-establishment process.

<CIT> discloses methods, systems, and devices for wireless communications that use asynchronous carrier aggregation, including between high frequency band and lower frequency band transmissions. A user equipment (UE) may be configured to monitor transmissions in a first frequency band and a second frequency band. The UE may measure a timing difference between transmissions in the first frequency band and one or more of the transmissions in the second frequency band, and transmit an indication of the timing difference to a base station. The base station may use the timing difference to determine whether the UE is to use asynchronous carrier aggregation. If the base station determines that the UE is to use asynchronous carrier aggregation, the base station may configure the UE to observe at least a minimum amount of delay when conducting uplink signaling via one of the frequency bands.

The listing or discussion of any prior-published document or any background in this specification should not necessarily be taken as an acknowledgement that the document or background is part of the state of the art or is common general knowledge. One or more aspects/examples of the present disclosure may or may not address one or more of the background issues.

According to at least some examples of the disclosure there is provided a User Equipment, UE, comprising:.

According to at least some examples of the disclosure there is provided a method comprising:.

According to at least some examples of the disclosure, not covered by the subject-matter of the claims and present for illustration purposes only, there is provided computer program instructions for causing a User Equipment, UE, to perform:.

According to at least some examples of the disclosure, not covered by the subject-matter of the claims and present for illustration purposes only, there is provided a non-transitory computer readable medium encoded with instructions that, when performed by at least one processor, causes at least the following to be performed:.

According to at least some examples of the disclosure there is provided a Radio Access Network, RAN, node comprising:.

According to at least some examples of the disclosure, not covered by the subject-matter of the claims and present for illustration purposes only, there is provided computer program instructions for causing a Radio Access Network, RAN, node to perform:.

According to various, but not necessarily all, examples of the disclosure, not covered by the subject-matter of the claims and present for illustration purposes only, there is provided computer program instructions for causing the above method to be performed.

According to at least some examples of the disclosure there is provided a Radio Access Network, RAN, node comprising:
means for receiving, following a maximum permissible exposure, MPE, event occurring during operation of a User Equipment, UE, over a first carrier such that the UE is no longer operating over the first carrier, a signal from the UE for requesting connection over a second carrier, wherein the signal comprises an indication of an occurrence of the MPE event associated with the previously used first carrier.

According to at least some examples of the disclosure there is provided a method comprising:
receiving, following a maximum permissible exposure, MPE, event occurring during operation of a User Equipment, UE, over a first carrier such that the UE is no longer operating over the first carrier, a signal from the UE for requesting connection over a second carrier, wherein the signal comprises an indication of an occurrence of the MPE event associated with the previously used first carrier.

For a better understanding of various embodiments/examples of the present disclosure, reference will now be made by way of example only to the accompanying drawings in which:.

Certain features and views of the figures may be shown schematically or exaggerated in scale in the interest of clarity and conciseness. For example, the dimensions of some elements in the figures can be exaggerated relative to other elements to aid explication. Similar reference numerals are used in the figures to designate similar features. For clarity, all reference numerals are not necessarily displayed in all figures.

<FIG> schematically illustrates an example of a network <NUM> comprising a plurality of network nodes including terminal nodes <NUM> (also referred to as User Equipment), access nodes <NUM> (also referred to as RAN nodes, transmission reception points, base stations), and core network <NUM>.

The terminal nodes <NUM> and access nodes <NUM> communicate with each other. The core network <NUM> communicates with the access nodes <NUM>. One or more core nodes of the core network <NUM> may, in some but not necessarily all examples, communicate with each other. The one or more access nodes <NUM> may, in some but not necessarily all examples, communicate with each other.

The network <NUM> may be a cellular network comprising a plurality of cells <NUM> each served by an access node <NUM>. The interfaces between the terminal nodes <NUM> and the access nodes <NUM> are radio interfaces <NUM>. The access nodes <NUM> are cellular radio transceivers. The terminal nodes <NUM> are cellular radio transceivers.

In the particular example illustrated, the network <NUM> is a Next Generation (or New Radio, NR) network. New Radio is the 3GPP name for <NUM> technology. The terminal nodes <NUM> are user equipment (UE).

In the present example, the access nodes <NUM> can be gNodeBs (gNBs), or Universal Terrestrial Radio Access network (UTRAN) NodeB (NBs), or Evolved Universal Terrestrial Radio Access network (E-UTRAN) NodeB (eNBs). Depending on the exact deployment scenario, the access nodes <NUM> could be, ng-eNB, or en-gNB equipment The access nodes <NUM> are interconnected with each other by means of X2 or Xn interfaces <NUM>. The access nodes <NUM> are also connected by means of NG or S1 interfaces <NUM> to the core network <NUM>. The cellular network <NUM> could be configured to operate in licensed or unlicensed frequency bands.

The access nodes <NUM> can be deployed in a NR standalone operation/scenario. The access nodes <NUM> can be deployed in a non-standalone operation/scenario. The access nodes can be deployed in a Carrier Aggregation operation/scenario. The access nodes <NUM> can be deployed in a dual connectivity operation/scenario, i.e. Multi Radio Access Technology - Dual Connection (MR-DC), not least for example such as:.

In such non-standalone/dual connectivity deployments, the access nodes <NUM> may be interconnected to each other by means of X2 or Xn interfaces, and connected to an Evolved Packet Core (EPC) by means of an S1 interface or to a <NUM> Core (5GC) by means of a NG interface.

The access nodes <NUM> are network elements in the network responsible for radio transmission and reception in one or more cells <NUM> to or from the terminal nodes <NUM>. Such access nodes may also be referred to as a transmission reception points (TRP's) or base stations. The access nodes <NUM> are the network termination of a radio link. An access node can be implemented as a single network equipment, or distributed over two or more RAN nodes, such as a central unit (CU), a distributed unit (DU), a remote radio head-end (RRH), using different functional-split architectures and different interfaces.

The terminal nodes <NUM> are devices that terminate the user side of the radio link. They are devices allowing access to network services. The terminal nodes <NUM> may be mobile terminals. The terminal nodes <NUM> may be user equipment or mobile stations. The term 'User Equipment' may be used to designate mobile equipment comprising a smart card for authentication/encryption etc such as a subscriber identity module (SIM). In other examples, the term 'user equipment' is used to designate mobile equipment comprising circuitry embedded as part of the user equipment for authentication/ encryption such as software SIM.

In the following description, an access node <NUM> will be referred to as a RAN node <NUM>, and a terminal node <NUM> will be referred to as a UE <NUM>.

Each of the RAN node <NUM> and UE's <NUM> may comprise one or more antennas, antenna patches or antenna panels, each comprising an array of antenna elements. A controller controls phase shifts and amplitudes of the radio frequency electrical signals applied to the antenna elements to generate a beamformed directional electromagnetic wave transmitted signal having a controlled direction/beam steering direction and a beam pattern (radiation pattern), thereby forming a transmission beam (e.g. a RAN node transmission beam for use with downlink transmission; and a UE transmission beam for use with uplink transmission). The transmission beam relates to a spatially directed transmission with power focussed in an aiming direction or beam steering/pointing angle, such an angle corresponding to a direction of a main lobe of the transmitted radiation pattern.

The controller may process the phase shifts and amplitudes of radio frequency electrical signals received from the antenna elements (such radio frequency electrical signals corresponding to transduced electrical signals from received electromagnetic wave signals) to achieve a preferred beamforming direction for reception, thereby forming a reception beam (e.g. a UE reception beam for use with downlink reception, and a RAN node reception beam for use with uplink reception). The reception beam relates to spatially directed reception wherein reception sensitivity is maximal at an aiming direction or pointing angle.

Beamforming, to form directional links for radio communication, may be used to compensate for high path-losses due to poor radio frequency (RF) propagation, which may affect the mmW/high frequency transmissions that can be used with <NUM> NR networks during operation over a <NUM> NR FR2 carrier - namely at frequencies in the region of <NUM> - <NUM> (as compared to <NUM> NR `s Frequency Range <NUM> (FR1)'s sub <NUM> range). In addition to beam forming, high gain antennas are used to maintain the link budget required to maintain a connectivity link between the UE and RAN node.

Transmission of signals from a UE to the RAN node <NUM> is uplink (UL) transmission via an uplink (UL) beam. A UL beam may be considered to comprise a beam pair, namely a transmission beam (from the UE) and reception beam (of the RAN node). Such a directional transmitter-side beam and a corresponding aligned directional receiver side beam jointly provide a UL beam pair for UL transmission/reception and connectivity over a given carrier, such as a <NUM> FR2 carrier (i.e. an optimal radio communication link/channel within the constraints of power, bandwidth and signal quality over a given carrier). It is to be appreciated that the transmission and reception beams are not necessarily physically aligned towards each other/in direct line of sight, not least for example in situations where there is a rich-scattering environment.

In a <NUM> NR network, an UL beam/beam pair may be considered to relate to a beamformed directional link from a UE to a RAN node, such a directional link having a directional transmission beam for UL transmission (UE UL Tx beam), and a corresponding directional reception beam for the UL transmission (RAN node UL Rx beam), such a transmission beam and reception beam for UL transmission thereby defining a UL beam pair, also referred to simply as UL beam.

<FIG> schematically illustrates a portion of a wireless communication network comprising a RAN node and two Power Class <NUM> (PC3) UE's operating over a <NUM> NR FR2 carrier, i.e. operating in the mmW part of the electromagnetic spectrum.

The millimetre-wave (mmW) spectrum offers the possibility of using large portions of contiguous bandwidth to address high-throughput applications. The <NUM> NR frequency spectrum may extend well above the frequency spectrum utilised by LTE/<NUM>, which ranges from <NUM> to <NUM>. In mmWave <NUM> NR, FR2 comprises the frequencies between <NUM> and <NUM>; and extending the NR operation into the <NUM>-<NUM> range (Frequency Range <NUM>) is currently being discussed.

However, operating at such high frequencies with high gain antennas has raised concerns for the health of users. Therefore, there is a standard on mmW regime that specifies and regulates the maximum transmission power for UE. Since frequencies below <NUM> are non-ionizing, the concern for health is limited to thermal heating of body tissue while absorbing electromagnetic mmW energy. mmW frequencies yield penetration depths below <NUM>, therefore possible thermal damage is limited to the surface of the skin and the eyes. Most of the energy is absorbed within the first <NUM> of the human skin at <NUM>.

Governmental exposure guidelines are in place to prevent health issues due to thermal effects. Below <NUM> (e.g. LTE), Specific Absorption Rate (SAR) has been used to determine the exposure threshold. SAR measures the energy absorbed by the human body when exposed to electromagnetic fields. In the US, the FCC stipulate a SAR limitation of <NUM> W/kg averaged over <NUM> of tissue. Whereas, in Europe, it is <NUM> W/kg averaged over <NUM> of tissue. The <NUM> averaging provides a finer resolution for the study of energy absorption in the human body.

In the mmW regime, where the penetration depth is below <NUM>, even <NUM> of tissue is rather a large volume. Since it can be difficult to define a meaningful volume for SAR evaluation, it has been commonly accepted to use Power Density (PD) and not SAR to set the restrictions on exposure at mmW frequencies. It is thus a planar energy distribution as opposed to a volumetric one. The MPE is the regulation on PD for the mmWave regime. Federal Communications Commission (FCC) and International Commission on Non-Ionizing Radiation Protection (ICNIRP), as well as multiple other regulatory agencies impose MPE constraints on transmitters at various carrier frequencies (not least such as mmWave transmissions). MPE constraints are typically specified in terms of short-term temporal averaging of radiated power, medium-term temporal averaging of radiated power, local-spatial averaging of radiated power, and/or medium-spatial averaging of radiated power. The imposing of the MPE constraints can prevent hazardous operating conditions, ensure users' optimal health, and/or reduce electromagnetic pollution or noise/interference from mmWave transmissions.

The FCC and ICNIRP set the threshold for MPE at <NUM> W/m<NUM> (<NUM> mW/cm<NUM>) for the general public, between <NUM> or <NUM> respectively and <NUM>. The energy absorbed by the human body increases as a function of decreasing distance to the UE. Therefore, to comply with the MPE limit, the UE might have to reduce its output power if the user gets in close vicinity of the antenna. A UE may determine and conform to MPE constraints autonomously or locally at the UE. For example, the UE may detect a distance from an antenna or an antenna array of the UE to a user's body part (e.g., a hand, face, ankle, etc.), determine an MPE constraint based on the detected distance, and transmit using an MPE compliant restricted UL power based on the detected distance.

<FIG> illustrates an example of user un-obstructed UE UL beam (case <NUM>) and a user obstructed UE UL beam.

In case <NUM>, there is an unobstructed Line of Sight (LOS) propagation path of the UE UL beam from the UE to the RAN node. In case <NUM>, a part of a human body obstructs the path of the UE's UL beam from the UE to the RAN node.

In case <NUM>, the Effective Isotropic Radiated Power (EIRP) of the PC3 UE peaks at +<NUM> dBm, while in case <NUM>, the UE has to reduce its output power to comply with the MPE regulations, as the user is exposed to and in close proximity to the radiated beam.

<FIG> illustrates a graph of the maximum allowed Effective Isotropic Radiated Power (EIRP) vs. user distance to a UE, as well as a graph of the maximum allowed Effective Isotropic Radiated Power (EIRP) vs. the UE's transmission range.

The graph on the left of <FIG> illustrates the relationship between the maximum allowed EIRP (i.e. the maximum EIRP allowed to comply with MPE limits) and the separation between the UE and a user. In this example, for a PC3 UE, when the user is nearly touching the antenna (<NUM> away), there is a reduction in maximum allowed peak EIRP of more than <NUM> dBm. The graph on the right of <FIG> illustrates the relationship between the maximum allowed EIRP and the UE's LOS range. As is evident from this, reducing the maximum allowed EIRP dramatically impacts the range of the UE, thus deteriorating the signal quality received at the RAN node.

When an MPE event occurs (such as in case <NUM>) at a UE connected/linked to a RAN node over a <NUM> NR FR2 carrier, the MPE restriction, i.e. reduction in the UE's UL transmission power, might be so severe that it causes a Radio Link Failure (RLF). Significantly reducing the output power (e.g. by at least <NUM> dB for PC3 UE's) is likely to lead to losing the connection to the RAN node and lead to an RLF, wherein the required power reduction, namely the Power Management Maximum Power Reduction (P-MPR), is too great to maintain the current link. The UE may be able to indicate the existence of the MPE event to the network (possibly including P-MPR value) before the occurrence of the RLF event so as the network can take appropriate corrective actions (e.g., handover, DC/CA reconfiguration).

At this point, the network only knows that the UE was operating in <NUM> NR FR2 and that the maximum allowed UL power is too limited to pursue communication due to an MPE event/MPE limitations. In case of non-standalone <NUM> operation, where an LTE anchor is required for control plane communication and mobility management, the network may transition the UE to LTE operation (i.e. E-UTRA), i.e. transition the <NUM> NR FR2 carrier to an LTE carrier. For example, this may occur when the UE informs the network that the <NUM> NR FR2 link has failed via a signalling procedure such as Secondary Cell Group (SCG) failure indication. Alternatively, the UE may autonomously transition to an LTE carrier with an RRC Re-establishment procedure when the primary link also fails. In case re-establishment is utilized, in examples of the disclosure, the UE may also indicate that the <NUM> NR FR2 link failed due to MPE reasons when transmitting the signalling informing to the network of the re-establishment causes.

For FR1 sub-<NUM> frequency operation, a SAR regulation applies which is different to the MPE regulation (which applied for over <NUM> frequencies). Furthermore, the FR1 antenna may be located elsewhere on the UE than the FR2 antenna array. Hence whilst a user's body part (e.g. hand) may in the path of transmissions from the FR2 antenna array, there may be no body parts of the user in the path of transmissions from the FR1 antenna. For these reasons, transiting from a <NUM> NR FR2 carrier to an LTE carrier may result in the UE not experiencing any UL power restrictions.

<FIG> schematically illustrates an example of a <NUM> NR FR2 capable UE <NUM> transitioning from operating over a <NUM> NR FR2 carrier <NUM> to operation over an LTE carrier <NUM> due to an MPE event <NUM> in order to avoid an RLF.

Initially, at time t1, the UE <NUM> is operating wholly or partly (e.g., utilizing Carrier Aggregation (CA) and/or Dual Connectivity (DC)) over a <NUM> NR FR2 carrier <NUM> for which MPE protection/limits applies, and is connected to a serving gNB <NUM>, i.e. the UE is in an RRC_Connected state. The user's hand <NUM> is not on the propagation path of the serving beam (from antenna panel P1) serving the RAN node, hence there is no MPE event. Whilst the UE is operating over <NUM> NR FR2, the UE is monitoring for MPE events.

At time t2, whilst the UE is still operating over a <NUM> NR FR2 carrier <NUM> and still in an RRC_Connected state with the serving gNB, the user covers the antenna panel P1.

The UE comprises proximity sensors, and dedicated components built into the UE device to detect nearby objects including humans and body parts. These components can be implemented in many ways including <NUM> radars. Based on the proximity sensor, the UE can autonomously back off its transmission power to comply with MPE requirements. The proximity detectors may thereby detect and trigger an MPE event <NUM>. The UE reports the existence of the MPE event <NUM> over the <NUM> NR FR2 carrier <NUM>. The resultant restriction on UL transmission power is so severe that the UE is redirected to LTE, i.e. transition (e.g. via a handover, RLF, or CA/DC re-configuration) the <NUM> NR FR2 carrier to an LTE carrier for which MPE protection/limits do not apply.

At time t3, the antenna panel P1 is no longer operating over a <NUM> NR FR2 carrier. Instead, the UE is now connected over an LTE carrier <NUM>.

Typically, operators have more spectrum available on <NUM> NR FR2 than on LTE sub-<NUM>. Therefore, it is desirable from the operator point of view to get the <NUM> NR FR2 capable UE back to FR2 operation as soon as it is feasible.

However, an issue suffered by conventional <NUM> NR FR2 capable UE's is that MPE event monitoring and reporting does not continue after the UE has been reconfigured to operate over LTE (since <NUM> and LTE operations are very different).

With the UE now operating on LTE, the network does not know when the UE is no longer experiencing the MPE event and when the UE is ready to resume <NUM> NR FR2 operation. The network is not aware of the current status of the MPE event on FR2 while connected through LTE, thus cannot optimally initiate the transition back to FR2.

As such, in order to redirect the UE back to <NUM> NR FR2 operation, conventionally the network will periodically request the UE to extend its operation back to FR2, which will be unsuccessful for as long as the MPE event is still active and ongoing, such as in <FIG> at time t3. Such uncoordinated procedures are not efficient from a network operation perspective, as it wastes resources to frequently attempt an unsuccessful FR2 link recovery.

At time t4, the antenna panel P1 is still not operating over a <NUM> NR FR2 carrier. Instead, the UE is still connected to the gNB over an LTE carrier <NUM>. The user's hand has, however, moved away from panel P1 such that the MPE event associated with the <NUM> NR FR2 carrier has ceased/has been terminated such that there would no longer be an MPE restriction restricting the UE's UL power transmission were it to re-establish operation over a <NUM> NR FR2 carrier. However, since, for conventional UE's, there is no MPE monitoring nor reporting of MPE events to the network once the UE is no longer operating over a <NUM> NR FR2 carrier having been transitioned to an LTE carrier, the network is unaware of when the UE is ready to resume <NUM> NR FR2 operation.

Certain examples of the present disclosure seek to address such issues and optimize recovery to <NUM> NR FR2, having been reconfigured or transitioned to LTE due to an MPE event, when the MPE event ceases. Certain examples of the present disclosure seek to address optimize recovery to <NUM> NR FR2, having been reconfigured or transitioned to <NUM> NR FR1 due to an MPE event, when the MPE event ceases. Certain examples of the present disclosure seek to provide an improved process for restoring UE operation over a previously used carrier that had been subject to an MPE event.

In order to optimize resource utilization recovery (e.g. <NUM> NR FR2 carrier operation or indeed any high-frequency carrier operation subject to MPE limits, restraints and regulatory requirements), the network requires MPE information, such as relating to whether or not the UE is experiencing a severe FR2 MPE event anymore (i.e. whether or not the UE is detecting a human body part close to the UE any longer or the required power back-off is still severe).

Examples of the present disclosure provide a new signalling mechanism for the 3GPP specifications to enable the UE to be configured by the network/RAN node, through the second carrier, to keep on monitoring the MPE event over the first carrier and a status/condition of the same, and to autonomously/on-demand report an MPE termination/recovery event to the RAN node over the second carrier. In such a manner, although a UE capable of operating over a <NUM> NR FR2 carrier UE has stopped using the <NUM> NR FR2 carrier and has been transitioned to another carrier, e.g. an LTE carrier or an <NUM> FR1 carrier, due to the MPE event on the <NUM> NR FR2 carrier, the UE can still report an MPE event associated with the <NUM> NR FR2 carrier, e.g. indicate the termination/cessation or recovery of the MPE event to the network, whereupon the network can then move the UE back to a <NUM> NR FR2 carrier.

As will be discussed further below, in examples of the disclosure, the MPE event is monitored by the UE on <NUM> NR FR2 and reported to the network, even though the UE is currently no longer operating over the <NUM> NR FR2 carrier and is operating on LTE or <NUM> FR1 carrier. The UE indicates to the network that the MPE event has terminated (even if the situation where it would have used FR2 would have ended already). Such reporting of the status/condition of an MPE event, i.e. an indication as to the current status of the MPE as to whether it is still active or as ceased, may be:.

Such an indication of the status/condition of the MPE event may be effected by an MPE toggling bit (i.e. "MPE no longer required") in a transmitted signal/MPE report. The signal/MPE report could also additionally contain further information related to the MPE event e.g.: required power back-off, duration of time since the UE detected the MPE event termination, or other information related to the occurrence, duration of effects of the MPE termination.

Examples of the disclosure may thereby assist in the provision to the network (e.g. RAN node gNB or eNB) of MPE information. This may enable the network to only attempt FR2 usage when the MPE event has been terminated or has recovered/is no longer so severe, such that the UE is able to provide the required link budget, i.e. Power Back Off (PBO), to connect with the network over the <NUM> NR FR2 carrier. Implementation of examples of the disclosure do not require any new hardware and merely relies on the output of the proximity sensors already embedded in the UEs, i.e. nearby user detection. The implementation relies on continuing the UE monitoring of the <NUM> NR FR2 MPE event status, after the UE has triggered the MPE event and been transitioned to a new carrier, even though the UE is not operating on <NUM> NR FR2 any longer. Based on a user-antenna separation distance, determined by sensors such as proximity sensors and based on measurements of reference signals (e.g., Synchronization Signal Block (SSB), Channel State Information - Reference Signal (CSI-RS) transmitted over the <NUM> NR2 carrier, a required power back-off of the UE on all or specific arrays can be determined. MPE monitoring on the UE is not resource or battery intensive and, indeed, it is likely that the UE would do aspects of MPE monitoring as it listens to e.g. SS burst for periodic link monitoring and initial access.

<FIG> schematically illustrates an example of a method <NUM> according to the present disclosure that can be implemented by an apparatus such as a UE <NUM>.

The method comprises, at block <NUM>, following a MPE event occurring during operation over a first carrier such that the UE is no longer operating over the first carrier, a first signal is received, over a second carrier, for configuring the UE to determine a status (or a condition) of the MPE event associated with a previously used first carrier;.

In some examples, based at least in part on the MPE event during operation over the first carrier, the UE ceases to operate over the first carrier. In some examples, the UE may detect the occurrence of the MPE event during operation over a first carrier and, responsive to the same, the UE ceases to operate over the first carrier. In some examples, due to the MPE event, the UE may be transitioned from operating over the first carrier to operating over the second carrier such that the UE is no longer operating over the first carrier. The transition may be a re-configuration, a re-connection, or a hand over, i.e. such that apparatus no longer operating over the first carrier. The transition may be an orderly/managed transition wherein an initial detection of the existence of the MPE event is signalled to the network, responsive to which the network initiates a re-configuration or hand over procedure, thereby transitioning the apparatus from the first to the second carrier. In some examples, the transition may be a non-network-initiated transition, for example wherein, due to an MPE event and resultant MPE restriction requiring a severe reduction in the UE's UL transmission power, an RLF occurs following which the apparatus initiates a re-connection procedure.

The first carrier could be, for example a <NUM> NR FR2 carrier utilising frequencies greater than <NUM> and/or between <NUM> and <NUM>. The first carrier could be a carrier at some other high frequency range that is subject to MPE limits, i.e. > <NUM>, not least a <NUM>-<NUM> of a potential future Frequency Range <NUM> (FR3). The first carrier could be a carrier of: a single connectivity link, MR-DC connectivity, CA connectivity, or even CA in MR-DC.

The second carrier could be a carrier different to the first carrier. The second carrier could be, for example an LTE carrier utilizing frequencies between <NUM> and <NUM>. The second carrier could be a <NUM> NR FR1 carrier operating at sub <NUM> frequencies (for which MPE limits do not apply). In some examples, such as where NR-DC connectivity, or CA in <NUM> NR FR2 is in operation, the second carrier could be another <NUM> NR FR2, albeit one that is not affected by the (or another) MPE event. In some examples, the second carrier could be a carrier at some other high frequency range, i.e. > <NUM>, again albeit one that is not affected by the (or another) MPE event. The second carrier could be a carrier of: a single connectivity link, MR-DC connectivity, CA connectivity, or even CA in MR-DC.

Initially, the UE may be in operation over at least the first carrier, i.e. the UE may be connected to one or more RAN nodes wholly or partially (e.g. via MR-DC connectivity, CA connectivity, or even CA in MR-DC) over the first carrier. Whereas, after the MPE event, the UE is no longer operating over the first carrier and is operating over at least the second carrier, i.e. the UE may be connected to one or more RAN nodes wholly or partially over the second carrier. Initially, i.e. prior to the MPE event on the first carrier, the UE may be in operation over the first carrier and at least the second carrier (e.g. via MR-DC connectivity, not least such as EN-DC), whereas, after the MPE event the UE is no longer operating over the first carrier and is operating over at least the second carrier (i.e. UE ceases operation over the first carrier and continues operation over the second carrier).

The MPE event may relate to one or more of: detection of user body part in propagation pathway of UL transmissions from apparatus operative over first carrier; detection of proximity/distance of user body part to apparatus (i.e. distance less than threshold values), determination of UL transmission power back off required to comply with MPE limits/tolerances, determination of a maximum allowed UL transmission power that complies with MPE limits and/or comparing the same to a minimum UL transmission power for sustain a radio link/connection over the first carrier (which may be determined based, not least in part on monitoring reference signals from the RAN node over the first carrier).

The status/condition of the MPE event associated with the previously used first carrier may be a status of the MPE event, e.g. a current status of the same, such as whether the MPE event over the first carrier is still active (condition = ON) or if it has terminated/recovered (condition = OFF).

At block <NUM>, responsive to receipt of the first signal, a determination is made as to the status/condition of the MPE event associated with the previously used first carrier.

The receipt of the first signal thereby configures the UE to continue to monitor the MPE event, e.g. continue to detect the presence and proximity of a user's body part to the UE/antenna panel, and determining whether an MPE restriction is required to ensure MPE compliance, e.g. reducing a UL transmission power.

At block <NUM>, responsive to receipt of the first signal, a second signal is transmitted over the second carrier, wherein the second signal comprises an indication of the current status/condition of the MPE event associated with the previously used first carrier.

Examples of the disclosure may thereby provide signalling that configures the UE to continue to monitor the MPE event even through the UE has stopped using the first carrier (for example the UE may have been transitioned from operating over a <NUM> NR FR2 carrier to operating over a second carrier). Moreover, such monitoring can be used to determine a current status/condition of the MPE event, e.g. whether it has terminated, which is signalled to a RAN node over the second carrier. Advantageously, this may thereby provide the requisite information to the RAN node for enabling it to decide whether or not to resume operation of the UE over the <NUM> NR FR2 carrier. Examples of the disclosure may thereby enable optimum <NUM> NR FR2 resource utilization and optimum link recovery/carrier re-establishment, i.e. for optimum spectrum and resource allocation.

In some examples, the first signal, which may be an RRC message, configures the UE to monitor a status of the MPE event associated with the previously used first carrier. Responsive to receipt of the first signal, the current status of the MPE event associated with the previously used first carrier is monitored whilst the UE is still operating over the second carrier and is no longer operating over the first carrier. The UE may comprise means for continuing to monitor the first carrier in spite of having been transitioned to the second carrier. Such means may comprise, not least, one or more antennas/antenna panels of the UE that are configured for reception of signals (such as reference signals) at the frequency of the first carrier (such as <NUM> NR FR2), and measuring signal characteristics of the same (such as measuring the power and quality of the received signals, e.g. Reference Signal Received Power (RSRP) and (RSRQ)). Based on such signal measurements, as well as measurements of user proximity to the UE/antenna/antenna panels of the same via sensors such as proximity detectors, and required transmission power back off, i.e. P-MPR, can be determine for complying with MPE limits. Thus, such MPE related information related to the MPE event associated with the previously used first carrier can be determined whilst the UE is no longer using the first carrier, e.g. having been transitioned therefrom to the second carrier.

In some examples, the first signal is a request for MPE information and the second signal is a report of MPE information related to the MPE event. The second signal may be transmitted via RRC or MAC signalling (as will be discussed further below).

The first signal may configure the UE's report, e.g. its content and when it is to be transmitted. The second signal may comprise an indication of one or more of the following:.

Various of the above may be determined/measured for on all or specific array's/receiving beams of the UE for <NUM> NR FR2 reception.

In some examples, the second signal is transmitted:.

The first signal may configure on what basis the second signal is sent, i.e. what triggers the sending of the second signal (for example, transmitting the second in signal in response to determining that measured/determined signal characteristic value of a received reference signal satisfy a criterion with respect to a threshold signal characteristic value set by the RAN node in its first signal).

In some examples, determining the current status/condition of the MPE event comprises:.

In some examples, the UE detects an initial occurrence of the MPE event during UE operation over the first carrier (for example, such a detection may occur whilst the UE is operating over the first carrier and prior to a transition of the UE to operating over the second carrier). The UE may determine a loss of connection over the first carrier, e.g. a radio link failure. Responsive to the detection of the MPE event and the determination of the loss connection over the first carrier, the UE may transmit one or more signals for requesting connection over the second carrier. Such one or more signals could be RRC signalling, e.g. RRC messages such as an RRC CONNECTION REQUEST message or an RRC CONNECTION REESTABLISHMENT REQUEST message. In cases where re-establishment is utilized, the UE may also indicate, when transmitting signalling informing the network of the re-establishment causes, that the loss of connection over the first carrier was due to MPE reasons.

<FIG> schematically illustrates an example of a method <NUM> according to the present disclosure that can be implemented by an apparatus such as a RAN node <NUM>.

At block <NUM>, the RAN node, following an MPE event occurring during operation of a UE over a first carrier such that the UE is no longer operating over the first carrier, transmits a first signal, over a second carrier, for configuring the UE to determine a status/condition of the MPE event associated with the previously used first carrier.

In some examples, the UE ceases to operate over the first carrier based at least in part on the MPE event during operation over the first carrier. In some examples, the UE may be transitioned from operating over the first carrier to operating over the second carrier such that the UE is no longer operating over the first carrier. The transition may be a re-configuration, a re-connection, or a hand over, i.e. such that apparatus no longer operating over the first carrier.

At block <NUM>, responsive to transmission of the first signal, the RAN node receives a second signal over the second carrier, wherein the second signal comprises an indication of the current status/condition of the MPE event associated with the previously used first carrier.

In some examples, based at least in part on the received second signal, the RAN node can determine whether to re-establish operation of the UE over the first carrier. Such a determination may also take into account one or more radio conditions of the first carrier, such as its current traffic load. Responsive to the determination, the RAN node may decide to re-establish operation of the UE over the first carrier and effect the appropriate procedure in this regard, e.g. to transition the UE back to operation over the <NUM> NR FR2 carrier.

In some examples, prior to transmission of the first signal, the RAN node receives a signal from the UE for requesting connection over the second carrier, wherein the signal comprises an indication of the occurrence of an MPE event associated with the previously used first carrier. Such a signal may thereby indicate to the RAN node that the UE had previously been connected over a first carrier but, due to an MPE event, lost connection. Such a signal may thereby trigger the RAN node to transmit, once a connection over the second carrier has been established, the first signal for requesting a status/condition of the MPE event associated with the previously used first carrier.

<FIG> schematically illustrates an example of signalling <NUM> between a UE <NUM> and a RAN node <NUM> according to the present disclosure.

Initially, the UE is connected (i.e. is in RCC CONNECTED state) to the RAN node over a first carrier, e.g. <NUM> NR FR2 carrier. Following detection of an MPE event at <NUM> (e.g., a user's body part in the path of the UE's <NUM> NR FR2 UL transmission beam), at <NUM> the UE signals a report of the MPE event to the RAN node. Responsive to the MPE report, at <NUM> the RAN node signals the UE to reconfigure the UE to operate over the second carrier.

At <NUM>, whilst the UE is connected (i.e. is in RCC CONNECTED state) to the RAN node over the second carrier, e.g. LTE carrier or a <NUM> FR1 carrier, the RAN node transmits the first signal which is received by the UE. Responsive to receipt of the first signal, the UE continues to monitor the MPE event over the first carrier. At <NUM> the UE determines that the MPE event has terminated. This may be due, for example to a determination that the user's body part has moved such that it would no longer be in the path of a <NUM> NR FR2 UL transmission beam. Alternatively, it may be due to determining that the required minimum UL transmission power for maintaining a <NUM> NR FR2 connection has reduced to a level below the maximum allowed UL transmission power that still complies with MPE limits, for example, the UE may have changed position/moved closer to the RAN node or the radio conditions may otherwise be favourable for <NUM> NR FR2 connection.

Responsive to the determination that the MPE event has terminated, at <NUM>, this triggers the UE to transmit the second signal, comprising an indication of the termination of the MPE event.

At <NUM>, responsive to receipt of the second signal indicating the that the MPE event has terminated, the RAN node may trigger a procedure to reconfigure the UE to operate over the first carrier, <NUM> NR FR2 carrier, once more.

The various examples discussed above have primarily been described with respect the UE transitioning the connection from the RAN node from <NUM> NR FR2 to LTE, and then back to <NUM> NR FR2. However, it is to be appreciated that examples of the present disclosure are applicable to other configurations, not least such as Dual Connectivity (DC) and Carrier Aggregation (CA).

In DC, the UE can simultaneously transmit and receive data on multiple component carriers from two cell groups via a master RAN node, Master Node (MN), and a secondary RAN node, Secondary Node (SN), wherein each cell group contains at least one carrier (i.e. such that the MN and/or the SN may have multiple carriers). The first carrier and the second carrier may be component carriers for either of the master RAN node and the secondary RAN node.

In CA, the UE can simultaneously transmit and receive data on multiple component carriers from a single RAN node. The first carrier and the second carrier can be component carriers of the multiple component carriers of the RAN node in CA.

In DC-CA, the UE can simultaneously transmit and receive data on multiple component carriers from the master RAN node and/or the secondary RAN node. The first carrier and the second carrier can be component carriers of such multiple component carriers for the master and/or secondary RAN nodes in DC-CA.

<FIG> schematically illustrates an example of a reconnection process according to the present disclosure. The Figure shows a flowchart of the procedures of a UE and a RAN node.

As indicated at block <NUM>, the RAN node's receipt of an MPE report, indicating the existence of an MPE event affecting <NUM> NR FR2 (e.g. signal <NUM> discussed above) triggers the network (operating under non-standalone <NUM> with an LTE anchor) to transition the UE from <NUM> NR FR2 to LTE. Based on the MPE report, it may be determined that the P-MPR required on <NUM> NR FR2 is so high that the network decides it is safest (i.e. to comply with MPE limits and avoid RLF) to transition the UE to LTE. As indicated at block <NUM> the UE has been transitioned to and is connected to LTE. As indicated at block <NUM>, due to receipt of the MPE report, the network is made aware that a previous <NUM> NR FR2 connection stopped due to an MPE event.

As indicated at block <NUM>, the network requests an MPE event termination report (similar to the transmission of signal <NUM> and the 'first signal' discussed in the above examples). The MPE termination report may be configured by the network, such as with regards to its information content and when it is to be transmitted to the RAN node. In some examples the report is autonomously sent by the UE.

In response to receipt of the request, the UE continues to monitor <NUM> NR FR2 related aspects/events, including not least a current status of the <NUM> NR FR2 MPE event, even though the UE has no <NUM> NR FR2 configuration or communication ongoing. The UE transmits the MPE report to the RAN node via the active LTE carrier.

As indicated in block <NUM>, based on the received MPE report, the RAN node determines whether the MPE event has terminated, or has become less severe/sufficiently abated such that the required MPE restriction of UE transmission power is not too high so as to be below an acceptable minimum UE UL transmission power for <NUM> NR FR2 connection over a <NUM> NR FR2 carrier. If so, the flow chart proceeds to block <NUM>, else the process loops back to block <NUM> and awaits a subsequent further MPE report.

As indicated in block <NUM>, which may be optional, the RAN node determines whether other radio conditions (e.g. current traffic load over the <NUM> NR FR2 cell) are favourable/amenable to reconnecting to <NUM> NR FR2. If so, the flow chart may proceed to block <NUM>; else the process may loop back to block <NUM> and await a subsequent further MPE report. It is to be appreciated that the order of blocks <NUM> and <NUM> is interchangeable.

As indicated in block <NUM>, following successful determinations in blocks <NUM> and <NUM>, the RAN attempts to reconnect the UE to <NUM> NR FR2.

<FIG> represents the case where a managed/orderly transition from <NUM> NR FR2 to LTE is performed, due to the RAN node having received the initial MPE report at block <NUM> and being able to take remedial action to avoid RLF and reconfigure the UE for LTE operation over an LTE carrier.

<FIG> schematically illustrates a further example of a reconnection process according to the present disclosure. <FIG> represents the case where a network managed transition from <NUM> NR FR2 to LTE is unable to be performed and avoid RLF. For example:.

Consequently, as indicated in block <NUM>, the UE needs to request to connect to the network, i.e. via an RRC message. However, since the UE may connect to a different RAN node than it was previously connected with, the new RAN node is unaware of the MPE event over the previous <NUM> NR FR2 connection with the previously connected RAN node. Accordingly, in examples of the disclosure, the RRC message requesting connection include an indication of the occurrence of the <NUM> NR FR2 MPE event, possibly with an identification of the affected <NUM> NR FR2 carrier. Hence, as indicated at block <NUM>, the network, e.g. the newly connected RAN node different from the previously connected RAN node, is aware that the previous <NUM> NR FR2 connection stopped due to an MPE event.

The remainder of the blocks shown in <FIG> (<NUM> - <NUM>) are the same as those described above for <FIG>.

With the proposed approach set out in the present disclosure, the network will only attempt the MPE-event carrier (e.g. <NUM> NR FR2) link reconfiguration once it knows both inputs:.

MPE-event carrier (e.g. <NUM> NR FR2) link recovery is optimized after MPE events, meaning that:.

Further use cases of examples of the present disclosure will now be described.

For both cases, there are several potential responses from network to UE:.

While the exact signalling varies depending on the used combination, the commonality is that the UE is no longer utilizing the carrier for which the MPE event occurred when being triggered to report the MPE event termination. The following basic logic is the same for all of these cases:.

The two aspects of examples of the present disclosure are:.

For <NUM>), the signalling can be either RRC or MAC CE:.

For <NUM>), at least the following information can be considered:.

Various examples of the disclosure provide a mechanism to inform the network of a status/condition of the MPE event, and hence of the ability to resume operation over <NUM> NR FR2 (for example after an autonomous or network-configured transition to LTE following a radio link failure on <NUM> NR FR2 caused where the MPE event is severe). The following are example approaches for the network to be informed on MPE event status before attempting to again use the <NUM> NR FR2 carrier:.

Signalling for indicating an MPE event termination/recovery may be via RRC or MAC signalling. There are various alternatives, <NUM>) and <NUM>) set out below, for the RRC/MAC signalling to indicate the MAC CE:.

An example of this is shown below (N. the highlighted parts indicate the new configuration/new IE's):.

The IE OtherConfig contains configuration related to other configuration. <IMG>
<IMG>
<IMG>.

The UEAssistanceInformation message is used for the indication of UE assistance information to the eNB.

<NUM>) RRC signalling using UEInformationRequest/UEInformationResponse (polling from the network). The network may also actively poll the UE to report the information via existing RRC request-response mechanisms as shown below (N. the highlighted parts indicate the new configuration/new lE's):.

The UEInformationRequest is the command used by E-UTRAN to retrieve information from the UE.

The UEInformationResponse message is used by the UE to transfer the information requested by the E-UTRAN.

<NUM>) MAC CE indicating the MPE event: In this case, the MAC CE would contain the information.

<FIG> schematically illustrates an example of a MAC CE suitable for use with examples of the present disclosure. <FIG> shows a MAC CE with:.

It is to be appreciated that other ways to the above described detailed examples of signaling, may be provided for transmitting MPE information, i.e. for requesting MPE information and reporting MPE information.

Various, but not necessarily all, examples of the present disclosure can take the form of a method, an apparatus. Some examples of the present disclosure, not covered by the subject-matter of the claims and present for illustration purposes only, can take the form of a computer program. Accordingly, various, but not necessarily all, examples can be implemented in hardware, software or a combination of hardware and software.

Various, but not necessarily all, examples of the present disclosure are described using flowchart illustrations and schematic block diagrams. It will be understood that each block (of the flowchart illustrations and block diagrams), and combinations of blocks, can be implemented by computer program instructions of a computer program. These program instructions can be provided to one or more processor(s), processing circuitry or controller(s) such that the instructions which execute on the same create means for causing implementing the functions specified in the block or blocks, i.e. such that the method can be computer implemented. The computer program instructions can be executed by the processor(s) to cause a series of operational steps/actions to be performed by the processor(s) to produce a computer implemented process such that the instructions which execute on the processor(s) provide steps for implementing the functions specified in the block or blocks.

Accordingly, the blocks support: combinations of means for performing the specified functions; combinations of actions for performing the specified functions; and computer program instructions/algorithm for performing the specified functions. It will also be understood that each block, and combinations of blocks, can be implemented by special purpose hardware-based systems which perform the specified functions or actions, or combinations of special purpose hardware and computer program instructions.

Various, but not necessarily all, examples of the present disclosure provide both a method and corresponding apparatus comprising various modules, means or circuitry that provide the functionality for performing/applying the actions of the method. The modules, means or circuitry can be implemented as hardware, or can be implemented as software or firmware to be performed by a computer processor. In the case of firmware or software, examples of the present disclosure can be provided as a computer program product including a computer readable storage structure embodying computer program instructions (i.e. the software or firmware) thereon for performing by the computer processor.

<FIG> illustrates an example of a controller <NUM>. The controller <NUM> could be provided within an apparatus, such as a UE <NUM> or a RAN node <NUM> that further comprises a radio transceiver <NUM>. The apparatus can be embodied by a computing device, not least such as those mentioned above. In some but not necessarily all examples, the apparatus can be embodied as a chip, chip set or module, i.e. for use in any of the foregoing. Implementation of a controller <NUM> may be as controller circuitry. The controller <NUM> may be implemented in hardware alone, have certain aspects in software including firmware alone or can be a combination of hardware and software (including firmware).

The memory <NUM> stores a computer program <NUM> comprising computer program instructions (computer program code) that controls the operation of the apparatus <NUM>, <NUM> when loaded into the processor <NUM>. The computer program instructions, of the computer program <NUM>, provide the logic and routines that enables the apparatus to perform the methods, processes, procedures and signalling described above and illustrated in <FIG>. The processor <NUM> by reading the memory <NUM> is able to load and execute the computer program <NUM>.

Although examples of the apparatus have been described above in terms of comprising various components, it should be understood that the components can be embodied as or otherwise controlled by a corresponding controller or circuitry such as one or more processing elements or processors of the apparatus. In this regard, each of the components described above can be one or more of any device, means or circuitry embodied in hardware, software or a combination of hardware and software that is configured to perform the corresponding functions of the respective components as described above.

In examples where the apparatus is provided within a UE <NUM> the apparatus therefore comprises:.

In examples where the apparatus is provided within a RAN node <NUM> the apparatus therefore comprises:.

According to some examples of the present disclosure, there is provided a system comprising the aforementioned UE and RAN node.

As illustrated in <FIG>, the computer program <NUM> may arrive at the apparatus <NUM>, <NUM> via any suitable delivery mechanism <NUM>. The delivery mechanism <NUM> may be, for example, a machine readable medium, a computer-readable medium, a non-transitory computer-readable storage medium, a computer program product, a memory device, a record medium such as a Compact Disc Read-Only Memory (CD-ROM) or a Digital Versatile Disc (DVD) or a solid state memory, an article of manufacture that comprises or tangibly embodies the computer program <NUM>. The delivery mechanism may be a signal configured to reliably transfer the computer program <NUM>. The apparatus <NUM>, <NUM> may propagate or transmit the computer program <NUM> as a computer data signal.

In certain examples of the present disclosure, not covered by the subject-matter of the claims and present for illustration purposes only, there is provided computer program instructions for causing a UE <NUM> to perform at least the following or for performing at least the following:.

In certain examples of the present disclosure, not covered by the subject-matter of the claims and present for illustration purposes only, there is provided computer program instructions for causing a RAN node <NUM> to perform at least the following or for performing at least the following:.

The stages illustrated in <FIG> can represent steps in a method and/or sections of code in the computer program <NUM>. The illustration of a particular order to the blocks does not necessarily imply that there is a required or preferred order for the blocks and the order and arrangement of the block may be varied. Furthermore, it can be possible for some blocks to be omitted.

From the foregoing it will be appreciated that in some examples there is provided a system comprising: at least one UE <NUM> and at least one RAN node <NUM>.

In some but not necessarily all examples, not least such as Enhanced Mobile Broadband (eMBB) use cases, the UE may embodied on a hand held portable electronic device, such as a mobile telephone, wearable computing device or personal digital assistant, that can additionally provide one or more audio/text/video communication functions (e.g. tele-communication, video-communication, and/or text transmission (Short Message Service (SMS)/ Multimedia Message Service (MMS)/emailing) functions), interactive/non-interactive viewing functions (e.g. web-browsing, navigation, TV/program viewing functions), music recording/playing functions (e.g. Moving Picture Experts Group-<NUM> Audio Layer <NUM> (MP3) or other format and/or (frequency modulation/amplitude modulation) radio broadcast recording/playing), downloading/sending of data functions, image capture function (e.g. using a (e.g. in-built) digital camera), and gaming functions.

The UE may also refer to Internet of Things (IoT) devices, massive industrial networks, smart city infrastructure, wearable devices, networked medical devices, autonomous devices, etc. These types of UE devices may operate for extended periods of time without human intervention (e.g., perform maintenance, replace or recharge an on-device battery, etc.), may have reduced processing power and/or memory storage, may have reduced battery storage capability due to having small form factors, may be integrated into machinery (e.g., heavy machinery, factory machinery, sealed devices, etc.), may be installed/located in hazardous environment or difficult to access environments, etc..

The apparatus can be provided in a module. As used here 'module' refers to a unit or apparatus that excludes certain parts/components that would be added by an end manufacturer or a user.

In some but not necessarily all examples, the UE <NUM> and the RAN node <NUM> are configured to communicate data with or without local storage of the data in a memory <NUM> at the UE <NUM> or the RAN node <NUM> and with or without local processing of the data by circuitry or processors at the UE <NUM>, or the RAN node <NUM>. The data may be stored in processed or unprocessed format remotely at one or more devices. The data may be stored in the Cloud. The data may be processed remotely at one or more devices. The data may be partially processed locally and partially processed remotely at one or more devices. The data may be communicated to the remote devices wirelessly via short range radio communications such as Wi-Fi or Bluetooth, for example, or over long-range cellular radio links. The apparatus may comprise a communications interface such as, for example, a radio transceiver for communication of data.

The UE <NUM>, the RAN node <NUM> can be part of the Internet of Things forming part of a larger, distributed network.

The processing of the data, whether local or remote, can be for the purpose of health monitoring, data aggregation, patient monitoring, vital signs monitoring or other purposes.

As used herein, the term "determining" (and grammatical variants thereof) can include, not least: calculating, computing, processing, deriving, investigating, looking up (e.g., looking up in a table, a database or another data structure), ascertaining and the like. Also, "determining" can include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), obtaining and the like. Also, "determining" can include resolving, selecting, choosing, establishing, and the like.

In this description, references to "a/an/the" [feature, element, component, means. ] are to be interpreted as "at least one" [feature, element, component, means. ] unless explicitly stated otherwise.

The description of a function should additionally be considered to also disclose any means suitable for performing that function. Where a structural feature has been described, it can be replaced by means for performing one or more of the functions of the structural feature whether that function or those functions are explicitly or implicitly described.

Accordingly, features described in relation to one example/aspect of the disclosure can include any or all of the features described in relation to another example/aspect of the disclosure, and vice versa, to the extent that they are not mutually inconsistent. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.

The term 'a' or `the' is used in this document with an inclusive not an exclusive meaning. That is any reference to X comprising a/the Y indicates that X may comprise only one Y or may comprise more than one Y unless the context clearly indicates the contrary. If it is intended to use 'a' or `the' with an exclusive meaning then it will be made clear in the context. In some circumstances the use of 'at least one' or 'one or more' may be used to emphasis an inclusive meaning but the absence of these terms should not be taken to infer any exclusive meaning.

In the above description, the apparatus described can alternatively or in addition comprise an apparatus which in some other examples comprises a distributed system of apparatus, for example, a client/server apparatus system. In examples where an apparatus provided forms (or a method is implemented as) a distributed system, each apparatus forming a component and/or part of the system provides (or implements) one or more features which collectively implement an example of the present disclosure. In some but not necessarily all examples, an apparatus is re-configured by an entity other than its initial manufacturer to implement an example of the present disclosure by being provided with additional software, for example by a user downloading such software, which when executed causes the apparatus to implement an example of the present disclosure (such implementation being either entirely by the apparatus or as part of a system of apparatus as mentioned hereinabove).

Claim 1:
A User Equipment, UE, (<NUM>) comprising:
means (<NUM>) for receiving, following a maximum permissible exposure, MPE, event (<NUM>, <NUM>) occurring during operation over a first carrier (<NUM>) such that the UE is no longer operating over the first carrier, a first signal (<NUM>), over a second carrier (<NUM>), for configuring the UE to determine a status of the MPE event associated with a previously used first carrier;
means (<NUM>) for determining, responsive to receipt of the first signal, a current status of the MPE event associated with the previously used first carrier; and
means (<NUM>) for transmitting, responsive to receipt of the first signal, a second signal (<NUM>) over the second carrier, wherein the second signal comprises an indication of the current status of the MPE event associated with the previously used first carrier.