MPE assistance in telecommunication systems

Abstract

An apparatus, method, and computer program are described that include: detecting an occurrence of a maximum allowed exposure event; and reporting maximum allowed exposure assistance information in response to detecting the occurrence of the maximum allowed exposure event, wherein reporting the maximum allowed exposure assistance information includes: generating a scheduled report when a periodic scheduling override condition is invalid, wherein the scheduled report is sent when a first time period expires; and generating an unscheduled report when the periodic scheduling override condition is valid, wherein the unscheduled report is sent without waiting for the first time period to expire.

Description

Technical Field

[0001] This specification relates to mobile communication systems, and more particularly to using mobile communication systems in accordance with exposure guidelines. Background Art

[0002] Exposure guidelines for communications systems are known. Such exposure guidelines can be expressed in terms of the Specific Absorption Rate (SAR) or Maximum Permissible Exposure (MPE). Although progress has been made, there is still room for further development in this area. Summary of the Invention

[0003] In a first aspect, the present specification describes a device (e.g., a user device, or a device implemented at a user device) comprising: means for detecting an occurrence of a maximum allowed exposure event (e.g., when the user device is less than a minimum safe distance from the user); means for reporting maximum allowed exposure assistance information (e.g., to a network element) in response to detecting the occurrence of the maximum allowed exposure event, wherein the means for reporting the maximum allowed exposure assistance information is configured to: generate a scheduled report when a periodic scheduling coverage condition is invalid, wherein the scheduled report is sent when a first time period expires; and generate a non-scheduled report when the periodic scheduling coverage condition is valid, wherein the non-scheduled report is sent without waiting for the first time period to expire. A first timer may be provided for monitoring the first time period (e.g., the first time period may be a time period of the first timer).

[0004] Some example embodiments further include means for determining a severity of the detected maximum allowed exposure event. For example, some example embodiments further include means for setting a periodic scheduling override condition to be valid if the detected maximum allowed exposure event is determined to have high severity. The detected maximum allowed exposure event may be determined to have high severity if the duty cycle reduction required to resolve the exposure event is above a threshold or if the power backoff requirement is above a threshold.

[0005] Some example embodiments further include means for monitoring an ongoing maximum permitted exposure event (e.g., using a second timer). Some example embodiments further include means for reporting that the maximum permitted exposure event has ended if the maximum permitted exposure event ends before expiration of a second time period. The second time period may be the same as or different from the first time period described above.

[0006] Some example embodiments further include a first timer for monitoring the first time period. Thus, for example, the first time period may be the time period of the first timer. Some example embodiments further include a second timer for monitoring the second time period. The second time period may be the same as the first time period, but this is not required for all example embodiments. For example, the second time period may be shorter than the first time period. The first timer and the second timer may be implemented using the same timer device, or may be implemented using separate timer devices.

[0007] Some example embodiments further comprise means for indicating (eg, via communication with an associated network, base station, Node B, etc.) that the device (eg, associated user equipment) is capable of providing maximum allowed exposure assistance information.

[0008] Some example embodiments further include means for triggering power backoff in response to a maximum allowable exposure event. Alternatively or additionally, some example embodiments further include means for triggering duty cycle adjustment (or duty cycle limiting) in response to a maximum allowable exposure event. Power backoff and / or duty cycle limiting may be triggered to meet MPE management requirements.

[0009] Some example embodiments further comprise means for reconfiguring a user equipment protocol to enable communication of maximum allowable exposure assistance information between the user equipment and the network element.

[0010] The maximum allowed exposure assistance information may be provided as part of a modified L3-based UE-assisted signaling procedure. For example, the signaling procedure may include: establishing a connection; exchanging capabilities; and device reconfiguration.

[0011] In a second aspect, the present specification describes an apparatus (e.g., a network node, such as a base station and gNB, or an apparatus or system communicating with such a node), comprising: a device for detecting (e.g., at a network element or similar device or system) a maximum allowed exposure event report (e.g., received from a user equipment or from an apparatus or system communicating with one or more user equipment); a device for determining (e.g., based on whether the report is received with an expected period) whether the detected maximum allowed exposure report is a scheduled report or an unscheduled report; a device for determining whether one or more time periods of a maximum allowed exposure event protocol should be updated (e.g., by one or more timers) to reduce the number of unscheduled reports if the detected maximum allowed exposure event report is determined to be a unscheduled report; and a device for adjusting uplink resources (e.g., in response to an MPE event triggering duty cycle adjustment and / or power backoff) to meet the maximum allowed exposure power backoff requirement.

[0012] Some example embodiments further comprise means for storing maximum allowed exposure event statistics upon receiving a maximum allowed exposure event report.

[0013] Some example embodiments further comprise means for receiving an indication that the remote user equipment is capable of providing maximum allowed exposure-related assistance information.

[0014] Some example embodiments further include means for defining a first timer start time for a user equipment, wherein the scheduling report is sent by the user equipment to the device upon expiration of the first timer. The means for defining the first timer start time may define the first timer start time for each of a plurality of user equipments (e.g., different user equipments in the plurality of user equipments may have different first timer start times).

[0015] Some example embodiments further comprise means for reconfiguring a user equipment protocol to enable communication of maximum allowable exposure assistance information between the user equipment and the network element.

[0016] The maximum allowed exposure assistance information may be provided as part of a modified L3-based UE-assisted signaling procedure. For example, the signaling procedure may include: establishing a connection; exchanging capabilities; and device reconfiguration.

[0017] In a third aspect, the present specification describes a method comprising: detecting an occurrence of a maximum allowed exposure event; and reporting maximum allowed exposure auxiliary information in response to detecting the occurrence of the maximum allowed exposure event, wherein reporting the maximum allowed exposure auxiliary information comprises: generating a scheduling report when a periodic scheduling coverage condition is invalid, wherein the scheduling report is sent when a first time period expires; and generating a non-scheduling report when the periodic scheduling coverage condition is valid, wherein the non-scheduling report is sent without waiting for the first time period to expire.

[0018] The method may further include determining a severity of the detected maximum allowed exposure event, and setting the periodic scheduling override condition to active if the detected maximum allowed exposure event is determined to have a high severity.

[0019] The method may further include monitoring an ongoing maximum allowed exposure event and reporting that the maximum allowed exposure event has ended if the maximum allowed exposure event ends before expiration of the second time period.

[0020] In a fourth aspect, the present specification describes a method comprising: detecting a maximum allowed exposure event report; determining whether the detected maximum allowed exposure report is a scheduled report or a non-scheduled report; in a case where the detected maximum allowed exposure event report is determined to be a non-scheduled report, determining whether one or more time periods of the maximum allowed exposure event protocol should be updated to reduce the number of non-scheduled reports; and adjusting uplink resources to meet the maximum allowed exposure power backoff requirements.

[0021] The method may further include storing maximum allowed exposure event statistics upon receiving a maximum allowed exposure event report.

[0022] The method may further comprise defining a first timer start time for a user equipment, wherein the scheduling report is sent by the user equipment upon expiration of the first timer.Example embodiments may further comprise defining a first timer start time for each of a plurality of user equipments.

[0023] In a fifth aspect, this specification describes an apparatus configured to perform any method as described with reference to the third or fourth aspects.

[0024] In a sixth aspect, this specification describes computer-readable instructions that, when executed by a computing device, cause the computing device to perform any of the methods described with reference to the third or fourth aspects.

[0025] In a seventh aspect, the present specification describes a computer-readable medium comprising program instructions stored thereon for performing at least the following operations: detecting the occurrence of a maximum allowed exposure event; and reporting maximum allowed exposure auxiliary information in response to detecting the occurrence of the maximum allowed exposure event, wherein reporting the maximum allowed exposure auxiliary information comprises: generating a scheduling report when a periodic scheduling coverage condition is invalid, wherein the scheduling report is sent when a first time period expires; and generating a non-scheduled report when the periodic scheduling coverage condition is valid, wherein the non-scheduled report is sent without waiting for the first time period to expire.

[0026] In an eighth aspect, the present specification describes a computer-readable medium comprising program instructions stored thereon for performing at least the following operations: detecting a maximum allowed exposure event report; determining whether the detected maximum allowed exposure report is a scheduled report or a non-scheduled report; in a case where the detected maximum allowed exposure event report is determined to be a non-scheduled report, determining whether one or more time periods of the maximum allowed exposure event protocol should be updated to reduce the number of non-scheduled reports; and adjusting uplink resources to meet the maximum allowed exposure power backoff requirements.

[0027] In a ninth aspect, the present specification describes a computer program comprising instructions for causing an apparatus to at least perform the following operations: detect the occurrence of a maximum allowed exposure event; and report maximum allowed exposure auxiliary information in response to detecting the occurrence of the maximum allowed exposure event, wherein reporting the maximum allowed exposure auxiliary information comprises: generating a scheduling report when a periodic scheduling coverage condition is invalid, wherein the scheduling report is sent when a first time period expires; and generating a non-scheduled report when the periodic scheduling coverage condition is valid, wherein the non-scheduled report is sent without waiting for the first time period to expire.

[0028] In a tenth aspect, the present specification describes a computer program comprising instructions for causing a device to perform at least the following operations: detect a maximum allowed exposure event report; determine whether the detected maximum allowed exposure report is a scheduled report or a non-scheduled report; in a case where the detected maximum allowed exposure event report is determined to be a non-scheduled report, determine whether one or more time periods of the maximum allowed exposure event protocol should be updated to reduce the number of non-scheduled reports; and adjust uplink resources to meet the maximum allowed exposure power backoff requirements.

[0029] In an eleventh aspect, the present specification describes an apparatus comprising: at least one processor; at least one memory comprising computer program code that, when executed by the at least one processor, causes the apparatus to perform the following operations: detect the occurrence of a maximum allowed exposure event; and report maximum allowed exposure auxiliary information in response to detecting the occurrence of the maximum allowed exposure event, wherein reporting the maximum allowed exposure auxiliary information comprises: generating a scheduling report when a periodic scheduling coverage condition is invalid, wherein the scheduling report is sent when a first time period expires; and generating a non-scheduling report when the periodic scheduling coverage condition is valid, wherein the non-scheduling report is sent without waiting for the first time period to expire.

[0030] In a twelfth aspect, the present specification describes an apparatus comprising: at least one processor; and at least one memory comprising computer program code that, when executed by the at least one processor, causes the apparatus to perform the following operations: detect a maximum allowed exposure event report; determine whether the detected maximum allowed exposure report is a scheduled report or a non-scheduled report; determine whether one or more time periods of the maximum allowed exposure event protocol should be updated to reduce the number of non-scheduled reports when the detected maximum allowed exposure event report is determined to be a non-scheduled report; and adjust uplink resources to meet the maximum allowed exposure power backoff requirements.

[0031] In a thirteenth aspect, the present specification describes an apparatus comprising: a maximum allowed exposure event monitor for detecting the occurrence of a maximum allowed exposure event; and an output for reporting maximum allowed exposure auxiliary information (e.g., to a network node) in response to detecting the occurrence of the maximum allowed exposure event, wherein reporting the maximum allowed exposure auxiliary information comprises: generating a scheduling report when a periodic scheduling coverage condition is invalid, wherein the scheduling report is sent when a first time period expires; and generating a non-scheduling report when the periodic scheduling coverage condition is valid, wherein the non-scheduling report is sent without waiting for the first time period to expire.

[0032] In a fourteenth aspect, the present specification describes an apparatus comprising: a control module for detecting a maximum allowed exposure event report and determining whether the detected maximum allowed exposure report is a scheduled report or a non-scheduled report; a timer module for determining whether one or more time periods of a maximum allowed exposure event protocol should be updated to reduce instances of non-scheduled reports when the detected maximum allowed exposure event report is determined to be a non-scheduled report; and a resource module for adjusting uplink resources to meet maximum allowed exposure power backoff requirements. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] Example embodiments will now be described by way of non-limiting example with reference to the following schematic diagrams, in which:

[0034] Figure 1 is a block diagram of a system according to an example embodiment;

[0035] Figure 2 is a graph showing example exposure rates;

[0036] Figure 3 and 4 is a block diagram of a system according to an example embodiment;

[0037] Figure 5 is a graph illustrating an example power back-off feature;

[0038] Figure 6 is a message sequence according to an example embodiment;

[0039] Figure 7 is a flowchart illustrating an algorithm according to an example embodiment;

[0040] Figure 8 is a message sequence according to an example embodiment;

[0041] Figure 9 is a message sequence according to an example embodiment;

[0042] Figure 10 is a flowchart showing an algorithm according to an example embodiment;

[0043] Figure 11 is a flowchart showing an algorithm according to an example embodiment;

[0044] Figure 12 is a block diagram of components of a system according to an example embodiment; and

[0045] Figure 13A and 13B Tangible media, namely, a removable nonvolatile memory unit and a compact disc (CD), respectively, are shown storing computer readable codes that, when executed by a computer, perform operations according to example embodiments. DETAILED DESCRIPTION

[0046] The scope of protection sought by various exemplary embodiments of the present invention is defined by the independent claims. Exemplary embodiments and features described in the specification that do not fall within the scope of the independent claims (if any) are to be construed as examples useful for understanding various embodiments of the present invention.

[0047] Like reference numerals refer to like elements throughout the description and drawings.

[0048] Millimeter wave (mmW) spectrum offers the potential to use large portions of contiguous bandwidth to enable mobile communication systems to deliver high-throughput applications. The fifth-generation (5G) New Radio (NR) spectrum is much higher than the previous fourth-generation (4G) spectrum, ranging from 400 MHz to 6 GHz, also known as Frequency Range 1 (FR1). In mmWave 5G NR, Frequency Range 2 (FR2) includes frequencies between 24 GHz and 52 GHz; discussions are currently underway to extend NR operation to the 52-114 GHz range.

[0049] The use of high-gain antennas operating at such high frequencies has raised concerns about user health. The millimeter wave regime has a standard that specifies and regulates the maximum power of user equipment (UE). Because frequencies below 100 GHz are non-ionizing, health concerns are limited to thermal heating of body tissues when absorbing electromagnetic mmW energy. The penetration depth produced by millimeter wave frequencies is less than 1 mm, so potential thermal damage is limited to the surface of the skin and eyes; in fact, most of the energy is absorbed within the first 0.4 mm of human skin at 42 GHz.

[0050] Governments have established exposure guidelines to prevent health problems caused by thermal effects. Below 6 GHz, the specific absorption rate (SAR) is used to determine exposure thresholds. SAR measures the amount of energy absorbed by the human body when exposed to electromagnetic fields. The FCC's SAR limit in the United States is 1.6 W / kg averaged over 1 gram of tissue, while in Europe it is 2 W / kg averaged over 10 grams of tissue. The 1-gram average provides finer resolution for studying energy absorption in the human body.

[0051] Nevertheless, for mmWave systems with penetration depths below 1 mm, even 1-g tissue is actually a fairly large volume. Due to the difficulty in defining a meaningful volume for SAR assessment, it is generally accepted to use power density (PD) rather than SAR to set exposure limits at mmWave frequencies. Therefore, it is a planar energy distribution rather than a volume distribution. The maximum permissible exposure (MPE) is based on the regulation of PD in the mmWave region. The FCC and ICNIRP set the threshold for MPE at 10 W / m 2 (1mW / cm 2), and for the general public, between 6 or 10 GHz and 100 GHz, respectively. The energy absorbed by the human body increases as a function of distance from the UE. Therefore, to comply with MPE limits, the UE may reduce its output power if the user is close to the antenna.

[0052] Figure 1 1 is a block diagram of a system generally indicated by reference numeral 10 according to an example embodiment. In system 10, a first user 12 communicates with a network node (gNB) 16 using a first mobile communication device (UE) 13, and a second user 14 communicates with the network node 16 using a second mobile communication device (UE) 15.

[0053] like Figure 1 As shown in , communication between the first device 13 and the network node 16 occurs via an unobstructed line of sight (LOS) path, while the second user 14 stands at least partially in a beam path from the second device 15 to the network node 16 .

[0054] Therefore, the second user is exposed to the radiation beam between the second device 15 and the network node 16. When the user is close to the second device 15, the amount of energy absorbed by the user's body may be relatively large; therefore, the output power of the second device 15 may need to be reduced to comply with the MPE requirement.

[0055] Figure 2 20 is a graph illustrating a maximum allowable equivalent isotropically radiated power (EIRP) depending on the distance between a user device (e.g., an antenna of the user device) and the user. As clearly shown in example graph 20, the maximum allowable EIRP decreases as the distance between the user device and the user decreases.

[0056] Figure 3 3 is a block diagram of a system 30 according to an example embodiment. The system 30 includes a user 32 (similar to the users 12 and 14 described above) and a user device 34 (similar to the user devices 13 and 15 described above). In the system 30, the user 32 and the user device 34 are separated by a distance greater than a minimum safety distance d. min The distance d user-UE Separate.

[0057] Figure 4 is a block diagram of a system 40, generally indicated by reference numeral 40, according to an example embodiment. The system 40 includes the system 40 described above with reference to Figure 3 However, in the system 40, the user 32 and the user device 34 are separated by a distance less than the minimum safety distance d. min The distance d user-UE Separate.

[0058] When the distance between the user 32 and the user device 34 is less than the minimum safety distance dmin When the power is reduced, the user equipment is required to perform power backoff to comply with the MPE management requirements. This backoff is referred to as an MPE event in this article.

[0059] Figure 5 5 is a graph, generally indicated by the reference numeral 50, illustrating an example power backoff feature. The graph (on the y-axis) shows user equipment transmit power plotted over time. As shown in graph 50, user equipment transmit power decreases between times t0 and t1 (due to the MPE event). For example, user equipment transmit power can be reduced by reducing the duty cycle of uplink transmissions.

[0060] If the user equipment 32 is communicating with a network element (such as the network node 16 described above) when power backoff occurs, the network node may not be able to receive sufficient power from the uplink transmission from the user equipment in order to successfully decode the payload transmitted from the user equipment. This may be the case, for example, because when the user equipment is at a power level above d min By the time the MPE triggers, link adaptation (e.g., selection of MCS, TBS, and UL transmit power) may have already been performed. Depending on the duration of the MPE event, a radio link failure (RLF) may also be triggered, resulting in a disrupted user experience and requiring the user equipment to reconnect to the network (e.g., transition to the RRC connected state again).

[0061] Figure 6 6 is a message sequence generally indicated by reference numeral 60 according to an example embodiment. The message sequence shows messages between a user equipment 62 (such as the user equipment 13, 15, or 34 described above) and a network element 64 (such as the network node 16 described above) that enables the user equipment 62 to notify the network element 64 of the occurrence of an MPE event. The message sequence 60 includes a setup connection message 65, a capability exchange message 66, a device reconfiguration message 67, and MPE assistance information 68. As discussed further below, the MPE assistance information 68 may be used to report the occurrence of an MPE event.

[0062] As discussed further below, message sequence 60 may be implemented using the Radio Resource Control (RRC) protocol.

[0063] Message sequence 60 begins with a setup connection message 65, in which user equipment 62 establishes a connection with network element 64. For example, user equipment 62 may transition from a radio resource control (RRC) idle or inactive state to an RRC connected state.

[0064] The setup connection message 65 is followed by a capability exchange message 66 in which the user equipment 62 informs the network element 64 of its capabilities, typically in response to a request for such information from the network element. In the context of the example embodiments described herein, the user equipment 62 informs the network element 64 that it is capable of providing MPE-related UE assistance as part of the capability exchange message 66.

[0065] Using a device reconfiguration message 67 (RRC reconfiguration), the network element 64 configures the user equipment 62 to be able to report UE assistance related to MPE. This configuration may include details such as how often the user equipment 62 is allowed to perform this reporting (e.g., the range of allowed periodicities). For example, to minimize signaling overhead, a long periodicity may be preferred. Alternatively, a small periodicity may be preferred to enable the network to react quickly (e.g., to quickly adjust the power backoff at the user equipment). The reconfiguration message may be based on existing RRC reconfiguration protocols.

[0066] Finally, upon detecting the occurrence of an MPE event, user equipment 62 sends its MPE assistance information to the network as part of an MPE assistance information message 68. As discussed in detail below, the timing of the transmission of MPE event reports may depend on the severity of the MPE condition.

[0067] Figure 7 is a flow chart illustrating an algorithm generally indicated by reference numeral 70 according to an example embodiment.

[0068] The algorithm 70 begins at operation 72 where the occurrence of a maximum permissible exposure (MPE) event is detected. At operation 74, the severity of the detected MPE event is determined or otherwise detected.

[0069] At operation 76, a determination is made as to whether a coverage condition (e.g., a periodic scheduling coverage condition) is satisfied. For example, the coverage condition may be related to the severity of the detected MPE event. The severity may be related to the extent to which the transmission (uplink) duty cycle needs to be reduced to overcome the MPE event. Alternatively or additionally, the severity may be associated with the extent to which power backoff is required to overcome the MPE event.

[0070] If operation 76 determines that the coverage condition is not met (eg, if the severity of the MPE event is below a threshold level), algorithm 70 moves to a wait state 78. After the wait state expires, an MPE report is generated at operation 79 (hereinafter referred to as a scheduled MPE report).

[0071] If operation 76 determines that the coverage condition is satisfied, the algorithm 70 moves to operation 79 , thereby generating an MPE report without waiting for the expiration of the above-described wait state (hereinafter referred to as an unscheduled MPE report).

[0072] Thus, algorithm 70 can report the maximum allowable exposure assistance information in response to detecting the occurrence of the maximum allowable exposure event (e.g., to a network element such as network element 64). Furthermore, reporting the maximum allowable exposure assistance information includes generating a scheduled report if the coverage condition is not met (i.e., invalid), and generating an unscheduled report if the coverage condition is met (i.e., valid).

[0073] As discussed further below, scheduled reports may be sent upon expiration of the first time period, while unscheduled reports may be sent without waiting for expiration of the first time period.

[0074] Figure 8 8 is a message sequence according to an example embodiment, generally indicated by reference numeral 80. Message sequence 80 illustrates messages between the user equipment 62 and the network element 64 described above, which enable the user equipment 62 to notify the network element 64 of the occurrence of an MPE event. Message sequence 80 illustrates details of an example implementation of the MPE assistance information message 68 described above.

[0075] Message sequence 80 shows the detection of an MPE event 81 at user equipment 62 and the end of the detection of an MPE event 82 at user equipment 62. Message sequence 80 shows how this information is transmitted to network element 64 if the coverage conditions of operation 76 of algorithm 70 are not met (e.g., the MPE event is not considered severe).

[0076] As discussed further below, in the event that the MPE event is not considered severe, the MPE assistance information is sent upon expiration of a time period (eg, a timer).Thus, the MPE assistance information messages may be sent periodically.

[0077] Message sequence 80 includes a first potential MPE assistance information message 83a and a second potential MPE assistance information message 83b, both of which occur before the start of MPE event 81. Since no MPE event is detected at these times, MPE information is not required to be sent in potential messages 83a and 83b. Those potential message time slots can simply be omitted; alternatively, a blank message can be sent to indicate that no MPE event was detected.

[0078] After detecting the MPE event 81, an MPE assistance information message 84 is sent from the user equipment 62 to the network element 64. Since the MPE event 81 is not considered severe, the MPE assistance information message 84 is sent at the next available periodic potential MPE assistance information message.

[0079] In response to receiving the MPE assistance information 84, an MPE processing procedure 85 is initiated. The MPE processing procedure 85 may include means for triggering power backoff in response to a maximum allowed exposure event to meet MPE management requirements. As discussed further below, the power backoff procedure may include changing the uplink resources provided to the user equipment 62 for communicating with the network element 64 to meet the MPE requirements.

[0080] Once the end of the MPE event 82 is detected, an MPE assistance information message 86 is sent from the user equipment to the network element 64, for example, in the next periodic message time slot indicating the end of the MPE event.

[0081] Message sequence 80 includes additional potential MPE auxiliary information messages 87a and 87b, both of which occur after the MPE event has ended. After message 86, no further MPE events are detected, and therefore no MPE information needs to be sent in potential messages 87a and 87b. As described above, those potential message slots can simply be omitted; alternatively, a blank message can be sent indicating that no MPE event was detected.

[0082] Figure 9 90 is a message sequence according to an example embodiment. Message sequence 90 illustrates messages between the user equipment 62 and the network element 64 described above, which enable the user equipment 62 to notify the network element 64 of the occurrence of an MPE event. Thus, like message sequence 80, message sequence 90 illustrates details of an example implementation of the MPE assistance information message 68 described above.

[0083] Message sequence 90 shows the detection of an MPE event 91 at user equipment 62 and the end of the detection of an MPE event 92 at user equipment 62. Message sequence 90 illustrates how this information is communicated to network element 64 if the coverage conditions of operation 76 of algorithm 70 are met (e.g., the MPE event is deemed severe).

[0084] As discussed further below, in the event that the MPE event is deemed severe, the MPE assistance information is sent without waiting for the expiration of a time period (eg, a timer).

[0085] Message sequence 90 includes a first potential MPE assistance information message 93a and a second potential MPE assistance information message 93b, both of which occur before the start of MPE event 91. Since no MPE event is detected at these times, there is no need to send MPE messages in potential messages 93a and 93b. Those potential message time slots can simply be omitted; alternatively, a blank message can be sent to indicate that no MPE event was detected.

[0086] After detecting the MPE event 91, an MPE assistance information message 94 is sent from the user equipment 62 to the network element 64. Since the MPE event 91 is considered severe, the MPE assistance information message 94 is sent without waiting for the next available periodic potential MPE assistance information message.

[0087] In response to receipt of MPE assistance information 94, MPE processing 95 is initiated. MPE processing is similar to MPE processing 85 described above; for example, MPE processing 95 may include changing uplink resources provided to user equipment 62 to communicate with network element 64 to meet MPE requirements.

[0088] Once the end of the MPE event 92 is detected, an MPE assistance information message 96 is sent from the user equipment to the network element 64, for example, in the next periodic message time slot indicating the end of the MPE event.

[0089] Message sequence 90 includes further potential MPE auxiliary information messages 97a and 97b, both of which occur after the end of the MPE event. After message 96, no further MPE events are detected, and therefore no MPE information needs to be sent in potential messages 97a and 97b. As described above, those potential message slots can simply be omitted; alternatively, a blank message can be sent to indicate that no MPE event was detected.

[0090] Figure 10 1 is a flow chart illustrating an algorithm according to an example embodiment, generally indicated by reference numeral 100. Algorithm 100 begins at operation 101. Algorithm 100 may be implemented at user device 62 (or some similar user device). In some example embodiments, multiple instances of algorithm 100 may be implemented at each of multiple user devices.

[0091] At operation 102, a first timer T1 is started (eg, at the user equipment 62). The first timer T1 is associated with periodic reporting of MPE events.

[0092] At operation 103, the user device 62 begins monitoring for the start of an MPE event. This may be an internal user device process and may be implemented in many different ways. For example, a proximity sensor may be provided to determine the presence of a user near the user device, or a radar-based or similar detection method may be provided.

[0093] At operation 104, the user device 62 determines whether an MPE event has been detected (such as the start of MPE event 81 or 91 described above). If an MPE event is detected, the algorithm 100 moves to operation 105. If no MPE event is detected, the algorithm 100 returns to operation 102.

[0094] At operation 105, the user equipment 62 determines whether the periodic scheduling coverage condition is valid. As discussed elsewhere herein, the periodic scheduling coverage condition may be valid in the event that the MPE event is considered severe. If the periodic scheduling coverage condition is invalid, the algorithm 100 moves to operation 106. If the periodic scheduling coverage condition is valid, the algorithm 100 moves to operation 107.

[0095] Example implementations of operation 105 include considering a duty cycle threshold or a power backoff threshold. For example, if the required duty cycle reduction due to the MPE event is below a duty cycle threshold level (e.g., 20%) due to the MPE event, then the coverage condition may be met. Alternatively or additionally, if the required power backoff due to the MPE event is above a threshold level (e.g., a given dB level), then the coverage condition may be met.

[0096] Alternatively or additionally, operation 105 may contemplate a flag that may be set to override periodic reporting. For example, the user equipment 62 or the control module may be allowed to set a flag to override periodic reporting (e.g., if the UE waits until timer T1 expires when the desired duty cycle reduction is not achievable).

[0097] Thus, operation 105 may include determining a severity of the detected maximum allowed exposure event.Operation 105 may include setting a periodic scheduling override condition to active if the detected maximum allowed exposure event is determined to be of high severity.

[0098] At operation 106 , the user equipment 62 waits for timer T1 to expire and then sends an MPE event report. Thus, operation 106 results in periodic MPE reports being sent (as discussed above with reference to message sequence 80 ). The algorithm 100 then moves to operation 108 .

[0099] At operation 107 , the user equipment 62 triggers the transmission of the MPE event report without waiting for the timer T1 to expire (as discussed above with reference to the message sequence 90 ). The algorithm 100 then moves to operation 108 .

[0100] At operation 108, a second timer T2 is set. The first timer T1 and the second timer T2 may have the same or different durations. For example, the second timer duration may be shorter than the first timer duration. The timers may be two instances of the same timer or separate timers.

[0101] In operation 109, the user device 62 monitors the ongoing MPE event. Then, in operation 110, it is determined whether the MPE event has ended. For example, it can be determined whether the distance between the user device 62 and the user is greater than the minimum distance d minIn the event that the maximum permissible exposure event ends before the time period of the second timer expires, then operation 110 may determine that the MPE event has ended.

[0102] If it is determined in operation 110 that the MPE event has ended, the algorithm 100 moves to operation 111 ; otherwise, the algorithm 100 moves to operation 112 .

[0103] At operation 111, the end of the MPE event is reported (e.g., by user equipment 62 to network element 64). Operation 111 may be implemented, for example, by message 86 of message sequence 80 or message 96 of message sequence 90. Once the end of the MPE is reported, algorithm 100 returns to operation 102.

[0104] At operation 112 (where it is determined that an MPE event is ongoing), the user equipment 62 determines whether a periodic scheduling coverage condition is valid. As discussed with reference to operation 105, the periodic scheduling coverage condition may be valid if the MPE event is considered severe. If the periodic scheduling coverage condition is invalid, the algorithm 100 moves to operation 113. If the periodic scheduling coverage condition is valid, the algorithm 100 moves to operation 114.

[0105] Example implementations of operation 112 include considering a duty cycle threshold, a power backoff threshold, or a flag. The coverage conditions in operation 112 may be the same as the conditions in operation 105, but this is not required. For example, the coverage conditions in operation 112 may be stricter than the conditions in operation 105 or stricter than the actual conditions of the user equipment at the time, thereby determining whether the MPE event has become worse (e.g., the user equipment 62 has moved closer to the user).

[0106] At operation 113 , the user equipment 62 waits for the second timer T2 to expire and then sends an MPE event report. Thus, operation 113 results in a periodic MPE report being sent. The algorithm 100 then returns to operation 108 .

[0107] At operation 114 , the user equipment 62 triggers the transmission of the MPE event report without waiting for the second timer T2 to expire. The algorithm 100 then returns to operation 108 .

[0108] Figure 11 is a flow chart showing an algorithm according to an example embodiment, generally indicated by reference numeral 120. Algorithm 120 begins at operation 121. Algorithm 120 may be implemented at network element 64 (or some similar node).

[0109] At operation 122, the network element 64 monitors for receipt of a UE assistance report from a user equipment (such as the user equipment 62). At operation 123, upon detecting the UE assistance report, it is determined (e.g., at the network element 64) whether the received UE assistance report is an MPE event report (e.g., a message such as message 84 or 94 described above).

[0110] If a received MPE event report is detected at operation 123 , the algorithm 120 moves to operation 124 ; otherwise, the operation 120 returns to operation 122 .

[0111] At operation 124, the network element 64 determines whether the received report follows the currently expected periodicity (i.e., T1 in the case of MPE event detection, or T2 in the case of an ongoing MPE event). If not, the received MPE report is identified as an unscheduled report and the algorithm 120 moves to operation 125. Otherwise, the received MPE report is identified as a scheduled report and the algorithm 120 moves to operation 126.

[0112] At operation 125, information about the user equipment that triggered the unscheduled report is extracted (e.g., at network element 64) and used to create statistics. Such MPE event statistics may be generated and stored upon receipt of an MPE event report. In addition, one or more time periods (e.g., timers) of the MPE event protocol may be updated to reduce instances of unscheduled reports. For example, a machine learning algorithm may be used to update the timer (or time period).

[0113] For example, the values ​​associated with the first and / or second timers described above may be adjusted. It should be noted that the occurrence of MPE events may vary in certain cells (or even for individual users). For example, a particular user may frequently hold their user device close to their head in talk mode, while another user may consistently use a headset with their user device placed on a surface away from the user. In the latter case, fewer MPE events are expected, and therefore the T1 and T2 timers may be more relaxed.

[0114] At operation 126, information about the user equipment that triggered the scheduled report is extracted (eg, at network element 64) and used to create statistics. Such MPE event statistics may be generated and stored upon receipt of an MPE event report.

[0115] At operation 127 , uplink resources of the user equipment 62 are adjusted, for example, to meet MPE power backoff requirements. In an example embodiment, the uplink duty cycle may be modified at operation 127 .

[0116] The uplink resources may also be modified by defining a first timer start time for a particular user equipment, wherein upon expiration of the first timer, the scheduling report is sent by the user equipment to the apparatus. Furthermore, the first timer start time may be set to be different for different user equipments, such that the first timer (and therefore the scheduling report) is staggered.

[0117] For the sake of completeness, Figure 12 3 is an example schematic diagram of components for implementing one or more modules of the above-described algorithm, which is collectively referred to below as a processing system 300. The processing system 300 may have a processor 302, a memory 304 coupled to the processor and including a RAM 314 and a ROM 312, and optionally, a user input 310 and a display 318. The processing system 300 may include one or more network interfaces 308 for connecting to a network, such as a modem that may be wired or wireless.

[0118] Processor 302 is connected to each of the other components to control their operation.

[0119] The memory 304 may include non-volatile memory, a hard disk drive (HDD), or a solid-state drive (SSD). The ROM 312 of the memory 304 stores, among other things, an operating system 315 and may store software applications 316. The processor 302 uses the RAM 314 of the memory 304 for temporary storage of data. The operating system 315 may include code that, when executed by the processor, implements aspects of the algorithms and message sequences 60, 70, 80, 90, 100, and 120.

[0120] Processor 302 may take any suitable form. For example, it may be a microcontroller, multiple microcontrollers, a processor, or multiple processors. Processor 302 may include processor circuitry.

[0121] Processing system 300 may be a stand-alone computer, a server, a console, or a network thereof.

[0122] In some example embodiments, processing system 300 may also be associated with external software applications. These may be applications stored on a remote server device and may run partially or exclusively on the remote server device. These applications may be referred to as cloud-hosted applications. Processing system 300 may communicate with the remote server device in order to utilize the software applications stored there.

[0123] Figure 13A and Figure 13BTangible media are shown, namely a removable memory unit 365 and a compact disc (CD) 368, which store computer-readable code that, when executed by a computer, can perform the method according to the above-described exemplary embodiments. Removable memory unit 365 can be a memory card, such as a USB memory card, having an internal memory 366 storing computer-readable code. The computer system can access memory 366 via connector 367. CD 368 can be a CD-ROM, DVD, or the like. Other forms of tangible storage media can be used.

[0124] Some example embodiments of the present invention may be implemented in software, hardware, application logic, or a combination of software, hardware, and application logic. The software, application logic, and / or hardware may reside in memory or on any computer medium. In example embodiments, the application logic, software, or instruction set is maintained on any of various conventional computer-readable media. In the context of this document, "memory" or "computer-readable medium" can be any non-transitory medium or unit that can contain, store, communicate, propagate, or transport instructions for use with an instruction execution system, apparatus, or device, such as a computer.

[0125] Where relevant, references to "computer-readable storage medium," "computer program product," "tangibly embodied computer program," etc., or "processor," "processing circuitry," etc., should be understood to include not only processors having different architectures, such as single / multi-processor architectures and sequencer / parallel architectures, but also specialized circuits, such as field programmable gate arrays (FPGAs), application specific circuits (ASICs), signal processing devices, and other devices. References to computer programs, instructions, code, etc., should be understood to mean software for programmable processor firmware, such as the programmable content of a hardware device as instructions for a processor, or configuration settings for a fixed-function device, gate array, programmable configuration or logic device, etc.

[0126] As used in this application, the term "circuitry" refers to all of the following: (a) purely hardware circuit implementations (such as implementations in analog and / or digital circuits only) and (b) combinations of circuitry and software (and / or firmware), where the software is such as (as applicable to): (i) a combination of a processor or (ii) a processor / software (including a digital signal processor), software, and a portion of memory that work together to enable a device (e.g., a server) to perform various functions and (c) circuitry (such as a microprocessor or a portion of a microprocessor) that requires software or firmware to operate, even if that software or firmware is not actually present.

[0127] If desired, the different functions discussed herein may be performed in a different order and / or concurrently with each other. Furthermore, if desired, one or more of the above functions may be optional or may be combined. Similarly, it will also be understood that Figures 6 to 11 The flowcharts and message sequences shown are examples only and the various operations described therein may be omitted, reordered, and / or combined.

[0128] It should be understood that the exemplary embodiments described above are purely illustrative and do not limit the scope of the present invention. Other changes and modifications will be apparent to those skilled in the art after reading this specification.

[0129] Furthermore, the disclosure of the present application should be understood to include any novel feature or any novel combination of features disclosed herein, whether explicitly or implicitly, or any generalization thereof, and new claims may be formulated during the prosecution of the present application or any application derived therefrom to cover any such feature and / or combination of such features.

[0130] Although various aspects of the invention are set out in the independent claims, further aspects of the invention comprise other combinations of features from the described exemplary embodiments and / or dependent claims with features of the independent claims, and not just in the combinations explicitly set out in the claims.

[0131] It should also be noted herein that although various examples have been described above, these descriptions should not be viewed in a limiting sense. Rather, several variations and modifications are possible without departing from the scope of the present invention as defined in the appended claims.

[0132] The example embodiments described herein may be implemented as part of an existing RRC protocol, such as specification TS 38.311: Radio Resource Control Protocol Specification.

[0133] Below, we present the text that needs to be added to TS 38.331 to enable this functionality. We underline the newly added functionality.

[0134] Changes in "5.3.5 RRC Reset"

[0135] NOTE: In this section, we define the MPE functionality of the UE upon receiving the RRC reconfiguration message.

[0136] *****Part omitted********

[0137] 5.3.5.9 Other Settings

[0138] UE will:

[0139] 1>if (if) the received otherConfig includes delayBudgetReportingConfig:

[0140] 2>if delayBudgetReportingConfig is set to setup:

[0141] 3> Consider that it is configured to send delay budget reports according to 5.7.4;

[0142] 2>else(otherwise):

[0143] 3> Consider itself not configured to send delay budget reports and stop timer T342, if running.

[0144] 1>if the received otherConfig includes overheatingAssistanceConfig:

[0145] 2>if overheatingAssistanceConfig is set to setup:

[0146] 3> Consider itself configured to provide overheat assistance information in accordance with 5.7.4;

[0147] 2>else:

[0148] 3> Consider that it is not configured to provide overheat assistance information and stop timer T345, if running;

[0149] 1>if the received otherConfig includes mpeAssistanceConfig:

[0150] 2>ifmpeAssistanceConfig is set to setup:

[0151] 3> consider itself configured to provide MPE assistance information according to 5.7.4.3;

[0152] 2>else:

[0153] 3> Consider itself not configured to provide MPE assistance information and stop timer TXYZ, if running;

[0154] *****Part omitted********

[0155] Changes in "5.3.7 RRC Connection Reestablishment"

[0156] Note: Here we ensure that the UE refreshes the previous MPE assisted configuration upon RRC connection re-establishment.

[0157] *****Part omitted********

[0158] 5.3.7.2 Startup

[0159] The UE initiates this process when one of the following conditions is met:

[0160] 1> When a radio link failure of the MCG is detected, according to 5.3.10; or

[0161] 1> When reconfiguring an MCG with synchronization failure, according to subsection 5.3.5.8.3; or

[0162] 1> in case of mobility failure from NR, according to subsection 5.4.3.5; or

[0163] 1> upon an integrity check failure indication from lower layers regarding SRB1 or SRB2, except when an integrity check failure is detected on RRCReestablishment; or

[0164] 1> In case of RRC connection reconfiguration failure, follow the procedure in section 5.3.5.8.2.

[0165] When initiating this procedure, the UE shall:

[0166] 1> Stop timer T310, if running;

[0167] 1> Stop timer T304, if running;

[0168] 1>Start timer T311;

[0169] 1>Suspend all RBs except SRBo;

[0170] 1>Reset MAC;

[0171] 1> Release MCG SCell(s), if configured;

[0172] 1>Release spCellConfig;

[0173] 1> Release delayBudgetReportingConfig, if configured, and stop timer T342, if running;

[0174] 1> Release overheatingAssistanceConfig, if configured, and stop timer T345, if running;

[0175] 1> Release mpeAssistanceConfig, if configured, and stop timer Txyz, if running;

[0176] 1> Perform cell selection according to the cell selection procedure specified in TS 38.304

[20] , c 5.2.6

[0177] *****Part omitted********

[0178] Changes in "5.3.13 RRC Connection Recovery"

[0179] Note: Here we ensure that the UE refreshes the previous MPE assisted configuration when the RRC connection is restored.

[0180] *****Part omitted********

[0181] 5.3.13.2 Startup

[0182] *****Part omitted********

[0183] 1> Release the delayBudgetReportingConfig from the UE inactive AS case, if stored;

[0184] 1> Stop timer T342, if running;

[0185] 1> Release the overheatingAssistanceConfig from the UE inactive AS situation, if stored;

[0186] 1> Stop timer T345, if running;

[0187] 1> Release the mpeAssistanceConfig from the UE inactive AS situation, if stored;

[0188] 1> Stop timer Txyz, if running;

[0189] 1> Apply CCCH configuration as specified in 9.1.1.2;

[0190] 1> Apply timeAlignmentTimerCommon included in SIB1;

[0191] 1>Start timer T319;

[0192] 1>Set the variable pendingRnaUpdate to false;

[0193] 1> Start the transmission of RRCResumeRequest message or RRCResumeRequest1 according to 5.3.13.3.

[0194] *****Part omitted********

[0195] Changes in "5.7.4 UE Assistance Information"

[0196] NOTE: Here we describe the UE behavior when the UE should start sending UE assistance information.

[0197] The purpose of this process is to inform the network that the UE's delay budget report carries the required Uu air interface delay increment / decrement, connected mode DRX cycle length, overheat assistance information or MPE auxiliary information .

[0198] 5.7.4.2 Startup

[0199] A UE capable of providing delay budget reporting in RRC_CONNECTED may initiate this procedure in several cases, including when configured to provide delay budget reporting and when the delay budget preference changes.

[0200] If a UE capable of providing overheat assistance information in RRC_CONNECTED is configured to do so, the procedure is initiated upon detection of an internal overheat, or upon detection that it is no longer experiencing an overheat condition.

[0201] If a UE capable of providing MPE assistance information in RRC_CONNECTED is configured to do so, it may be detected To MPE event (ie UE is below the distance d from the user min ), or starts the process upon detecting that it is no longer experiencing MPE events.

[0202] When initiating this procedure, the UE shall:

[0203] 1> If configured to provide delay budget reporting:

[0204] 2> if the UE does not send a UEAssistanceInformation message with delayBudgetReport because it is configured to provide delay budget reporting; or

[0205] 2> If the current delay budget is different from the one indicated in the last UEAssistanceInformation message sent, and timer T342 is not running:

[0206] 3> Start sending UEAssistanceInformation message according to 5.7.4.3;

[0207] 1> If configured to provide overheating auxiliary information:

[0208] 2> If an overheat condition is detected and the T345 is not operating; or

[0209] 2> If the current overheat assistance information is different from the one indicated in the last UEAssistanceInformation message sent and timer T345 is not running:

[0210] 3> Start sending UEAssistanceInformation message according to 5.7.4.3;

[0211] 1> If configured to provide MPE auxiliary information:

[0212] 2> If the MPE condition has been detected and Txyz is not running; or

[0213] 2> If the current MPE assistance information is different from the last UEAssistanceInformation message sent And the timer Txyz is not running:

[0214] 3> Start sending UEAssistanceInformation message according to 5.7.4.3;

[0215] 5.7.4.3 Actions related to the transmission of UEAssistanceInformation message

[0216] *****Part omitted********

[0217] The UE shall set the content of the UEAssistanceInformation message for MPE event reporting as follows:

[0218] 1> If the UE experiences an MPE event:

[0219] 2> If the UE reports that it wants the UL duty cycle to be reduced

[0220] Include ueReducedDutyCycle in the MPEAssistance IE.

[0221] 2> If the UE reports the desired UL power backoff

[0222] Include uePowerBackoffRequired in the MPEAssistance IE.

[0223] 2>Start timer Txyz, and set the timer value to mpeIndicationProhibitTimer2;

[0224] 1>else (if the UE no longer experiences the MPE event)

[0225] 2> Do not include ueReducedDutyCycle and uePowerBackoffRequired;

[0226] 2>Start timer Txyz and set the timer value to mpeIndicationProhibitTimer1.

[0227] Changes in "6.2.2 Message Definition"

[0228] NOTE: Here we introduce the changes required in UE assistance information to support the MPE functionality.

[0229] *****Part omitted********

[0230] –UEAssistanceInformation

[0231] The UE assistance information is used to indicate UE assistance information to the network.

[0232]

[0233]

[0234]

[0235]

[0236]

[0237] *****Part omitted********

[0238] Changes in "6.3.3 UE Capability Information Elements"

[0239] NOTE: Here we introduce elements that allow the UE to inform the network that it can provide MPE related UE assistance.

[0240] *****Part omitted********

[0241] –UE-NR-Capability

[0242] The IE UE-NR-Capability is used to convey the NR UE radio access capability parameters, see TS 38.306

[26] .

[0243]

[0244]

[0245]

[0246]

[0247] *****Part omitted********

[0248] Changes in "6.3.4 Other Information Elements"

[0249] NOTE: In this section, we introduce the required RRC information element changes in order to define the inhibit timer associated with MPE reporting. The network uses this inhibit timer to control how often the UE is allowed to trigger MPE reporting.

[0250] *****Part omitted********

[0251] –OtherConfig

[0252] IE OtherConfig contains configurations related to other configurations.

[0253]

[0254]

[0255]

[0256] *****Part omitted********

[0257] Changes to "7.1.1 Timer (Information Rich)"

[0258] NOTE: Here we introduce a timer that allows controlling the frequency of MPE related UE assistance messages.

[0259] *****Part omitted********

[0260]

[0261] *****Part omitted********

Claims

1. A communication device, comprising: at least one processor; and at least one memory comprising computer program code, the at least one memory and the computer program code being configured to, with the at least one processor, cause the apparatus to perform: Detect the occurrence of maximum allowable exposure events; determining a severity of the detected maximum allowable exposure event; setting a periodic scheduling override condition to be valid if the detected maximum allowed exposure event is determined to be of high severity; as well as In response to detecting the occurrence of the maximum allowed exposure event, reporting maximum allowed exposure assistance information, wherein reporting the maximum allowed exposure assistance information comprises: generating a scheduling report when the periodic scheduling coverage condition is invalid, wherein the scheduling report is sent when a first time period expires; and An unscheduled report is generated if the periodic scheduling override condition is valid, wherein the unscheduled report is sent without waiting for the first time period to expire.

2. The device according to claim 1, wherein In the event that the duty cycle reduction required to resolve the exposure event is above a threshold, the detected maximum allowed exposure event is determined to have a high severity.

3. The apparatus of claim 1, wherein: The at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to further perform: monitoring for an ongoing maximum allowable exposure event.

4. The apparatus of claim 3, wherein: The at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to further perform: reporting that the maximum allowed exposure event has ended if the maximum allowed exposure event ends before expiration of a second time period.

5. The apparatus of claim 1, further comprising a first timer for monitoring the first time period.

6. The apparatus of claim 1, wherein: The at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to further perform: indicating that the apparatus is capable of providing maximum allowed exposure assistance information.

7. The apparatus of claim 1, wherein: The at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to further perform: triggering a power backoff in response to the maximum allowed exposure event.

8. The apparatus of claim 1, wherein: The at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to further perform: triggering a duty cycle adjustment in response to the maximum allowed exposure event.

9. Apparatus according to any one of the preceding claims, wherein The maximum allowed exposure assistance information is provided as part of a modified L3-based UE-assisted signaling procedure.

10. A device for communication, comprising: at least one processor; and at least one memory including computer program code, the at least one memory and the computer program code being configured to, with the at least one processor, cause the apparatus to perform: Detection of maximum allowable exposure event reports; determining whether the detected maximum allowable exposure event report is a scheduled report or an unscheduled report; determining whether one or more time periods of the maximum allowable exposure event protocol should be updated to reduce instances of unscheduled reporting if a detected maximum allowable exposure event report is determined to be an unscheduled report; and Adjust uplink resources to meet the maximum allowed exposed power back-off requirement.

11. The apparatus of claim 10, wherein: The at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to further perform: storing maximum allowed exposure event statistics upon receiving a maximum allowed exposure event report.

12. The apparatus of claim 10, wherein: The at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to further perform: receiving an indication that a remote user equipment is capable of providing maximum allowed exposure-related assistance information.

13. The apparatus of claim 10, wherein: The at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to further perform: defining a first timer start time for a user equipment, wherein the scheduling report is sent by the user equipment to the device upon expiration of the first timer.

14. The apparatus of claim 13, wherein: Defining a first timer start time defines a first timer start time for each of the plurality of user equipments.

15. The apparatus of claim 10, wherein: The at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to further perform: reconfiguring a user equipment protocol to enable transmission of maximum allowed exposure assistance information between the user equipment and a network element.

16. The apparatus according to any one of claims 10 to 15, wherein: The maximum allowed exposure assistance information is provided as part of a modified L3-based UE-assisted signaling procedure.

17. A method for communication, comprising: Detect the occurrence of maximum allowable exposure events; determining a severity of the detected maximum allowable exposure event; setting a periodic scheduling override condition to be valid if the detected maximum allowed exposure event is determined to be of high severity; as well as In response to detecting the occurrence of the maximum allowed exposure event, reporting maximum allowed exposure auxiliary information, Among them, reporting the maximum allowed exposure auxiliary information includes: generating a scheduling report when the periodic scheduling coverage condition is invalid, wherein the scheduling report is sent when the first time period expires; and generating a non-scheduling report when the periodic scheduling coverage condition is valid, wherein the non-scheduling report is sent without waiting for the first time period to expire.

18. The method of claim 17, further comprising monitoring an ongoing maximum allowed exposure event and reporting that the maximum allowed exposure event has ended if the maximum allowed exposure event ends before expiration of a second time period.

19. A method for communication, comprising: Detection of maximum allowable exposure event reports; determining whether the detected maximum allowable exposure event report is a scheduled report or an unscheduled report; In the event that the detected maximum allowable exposure event report is determined to be an unscheduled report, determining whether one or more time periods of the maximum allowable exposure event protocol should be updated to reduce instances of unscheduled reporting; and Adjust uplink resources to meet the maximum allowed exposed power back-off requirement.

20. The method of claim 19, further comprising storing maximum allowable exposure event statistics upon receiving a maximum allowable exposure event report.

21. The method according to claim 19 or 20, further comprising defining a first timer start time for a user equipment, wherein the scheduling report is sent by the user equipment if the first timer expires.

22. A computer-readable medium comprising program instructions for causing a device for communication to at least: Detect the occurrence of maximum allowable exposure events; determining a severity of the detected maximum allowable exposure event; setting a periodic scheduling override condition to be valid if the detected maximum allowed exposure event is determined to be of high severity; as well as In response to detecting the occurrence of the maximum allowed exposure event, reporting maximum allowed exposure auxiliary information, Wherein, the method for reporting the maximum allowed exposure auxiliary information includes: generating a scheduling report when the periodic scheduling coverage condition is invalid, wherein the scheduling report is sent when the first time period has passed; and generating a non-scheduling report when the periodic scheduling coverage condition is valid, wherein the non-scheduling report is sent without waiting for the first time period to pass.

23. A computer-readable medium comprising program instructions for causing a device for communication to at least: Detection of maximum allowable exposure event reports; determining whether the detected maximum allowable exposure event report is a scheduled report or an unscheduled report; determining whether a time period of a maximum allowed exposure event protocol should be updated if the detected maximum allowed exposure event report is determined to be an unscheduled report; and Adjust uplink resources to meet the maximum allowed exposed power back-off requirement.

24. A device for communication, comprising: a device for detecting the occurrence of a maximum permissible exposure event; means for determining a severity of said maximum allowable exposure event detected; means for setting a periodic scheduling override condition to be effective if the detected maximum allowed exposure event is determined to be of high severity; as well as means for reporting maximum allowed exposure assistance information in response to detecting an occurrence of the maximum allowed exposure event, wherein the means for reporting the maximum allowed exposure assistance information is configured to: generating a scheduling report when the periodic scheduling coverage condition is invalid, wherein the scheduling report is sent when a first time period expires; and An unscheduled report is generated if the periodic scheduling override condition is valid, wherein the unscheduled report is sent without waiting for the first time period to expire.

25. A device for communication, comprising: Devices for detecting and reporting maximum permissible exposure events; means for determining whether a detected maximum allowable exposure event report is a scheduled report or an unscheduled report; means for determining whether one or more time periods of the maximum allowed exposure event protocol should be updated to reduce instances of unscheduled reporting if a detected maximum allowed exposure event report is determined to be an unscheduled report; and Means for adjusting uplink resources to meet maximum allowed exposed power backoff requirements.

Images