Carrier management in wireless communication networks
By employing a signaling mechanism that continues to monitor and report the MPE event status after carrier switching, the connection loss problem caused by MPE events on 5G NR FR2 carriers is resolved, enabling a more efficient recovery process and optimizing resource utilization.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- NOKIA TECHNOLOGIES OY
- Filing Date
- 2021-05-13
- Publication Date
- 2026-04-21
AI Technical Summary
After a Maximum Allowable Exposure (MPE) event occurs on a 5G NR FR2 carrier, the uplink transmission power of the UE decreases, resulting in connection loss. Traditional methods for attempting recovery are resource-intensive and inefficient, and the network cannot promptly obtain the termination status of the MPE event.
A new signaling mechanism is introduced to monitor and report the status of MPE events via a second carrier. After the UE switches to other carriers, it continues to monitor and report the termination or recovery of MPE events to the RAN node, providing MPE information to optimize the recovery process.
This reduces resource waste and improves the efficiency of the MPE event recovery process, enabling the network to more effectively restore the UE to 5G NR FR2 carrier operation when the MPE event terminates.
Smart Images

Figure CN115702588B_ABST
Abstract
Description
Technical Field
[0001] Examples disclosed herein relate to carrier management in wireless communication networks. Some examples involve the re-establishment of carriers that have experienced a Maximum Permissible Exposure (MPE) event. Background Technology
[0002] In fifth-generation (5G) New Radio (NR), a User Equipment (UE) can communicate with a Radio Access Network (RAN) node via one or more radio links operating on one or more carriers in the millimeter-wave (mmW) portion of the electromagnetic spectrum, specifically utilizing frequencies between 24 GHz and 52 GHz, referred to as Frequency Range 2 (FR2). Such high-frequency use is subject to MPE (Mean Power Regulation) limits imposed 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 potentially exceed MPE limits without such restrictions.
[0003] To ensure that UE uplink (UL) signals transmitted over a 5G NR FR2 carrier comply with MPE limits, the UE can limit its uplink transmission power. However, this may cause the UE's UL transmission power to drop below a level insufficient to maintain a sufficient connection link over the 5G NR FR2 carrier. Therefore, when a UE is operating over a 5G NR FR2 carrier, once an MPE event is detected (such as detecting a part of the user's body near the UE antenna and in the propagation path from the UE antenna to the RAN node, thus requiring uplink transmission power limitation to ensure MPE compliance), the RAN node can switch the UE from operating on the 5G NR FR2 carrier to operating on a different carrier, such as a Long Term Evolution (LTE) carrier or a 5G Frequency Range 1 (FR1) carrier, which uses sub-6GHz frequencies (i.e., the range of 400MHz to 6GHz) where MPE limits are not applicable.
[0004] In some cases, it may be necessary to seek to restore the UE to operation on a 5G NR FR2 carrier.
[0005] Some examples of this disclosure seek to provide an improved process for resuming UE operation on a previously used carrier that has experienced an MPE event. Some examples of this disclosure seek to avoid / reduce attempts to restore the UE to operation on a previously used carrier while the MPE event is still active on that carrier. Some examples seek to reduce signaling overhead and wasted resources, and to accelerate the re-establishment process, when attempting to re-establish UE operation on a previously used carrier.
[0006] The listing or discussion of any previously published documents or background information in this specification is not necessarily an admission that such documents or background information are part of the prior art or common general knowledge. One or more aspects / examples of this disclosure may or may not solve one or more background problems. Summary of the Invention
[0007] The scope of protection for the various embodiments of this invention is defined by the independent claims. Any examples / exemplifications and features described in this specification that are not within the scope of the independent claims should be interpreted as examples that help to understand the various embodiments of this invention.
[0008] According to at least some examples of this disclosure, a user equipment (UE) is provided, the UE comprising:
[0009] A component for receiving a first signal on a second carrier after a maximum permissible exposure MPE event occurs during operation on the first carrier, causing the UE to cease operation on the first carrier. The first signal is used to configure the UE to determine the state of an MPE event associated with the previously used first carrier.
[0010] A component for determining the current state of an MPE event associated with a previously used first carrier in response to the reception of a first signal; and
[0011] Components for transmitting a second signal on a second carrier in response to the reception of a first signal, wherein the second signal includes an indication of the current state of an MPE event associated with the previously used first carrier.
[0012] Based on at least some examples of this disclosure, a method is provided that includes:
[0013] After a maximum permissible exposure MPE event occurs during the operation of the user equipment (UE) on the first carrier, causing the UE to cease operation on the first carrier, a first signal is received on the second carrier. The first signal is used to configure the UE to determine the state of the MPE event associated with the previously used first carrier.
[0014] In response to the reception of the first signal, determine the current state of the MPE event associated with the previously used first carrier; and
[0015] In response to the reception of the first signal, a second signal is transmitted on the second carrier, wherein the second signal includes an indication of the current state of an MPE event associated with the previously used first carrier.
[0016] According to at least some examples of this disclosure, computer program instructions are provided for inducing a user equipment (UE) to perform the following operations:
[0017] After a maximum permissible exposure MPE event occurs during operation on the first carrier, causing the UE to cease operation on the first carrier, a first signal is received on the second carrier. The first signal is used to configure the UE to determine the status of the MPE event associated with the previously used first carrier.
[0018] In response to the reception of the first signal, determine the current state of the MPE event associated with the previously used first carrier; and
[0019] In response to the reception of the first signal, a second signal is transmitted on the second carrier, wherein the second signal includes an indication of the current state of an MPE event associated with the previously used first carrier.
[0020] According to at least some examples of this disclosure, a user equipment (UE) is provided, the UE comprising:
[0021] At least one processor; and
[0022] At least one memory including computer program instructions;
[0023] At least one memory and computer program instruction are configured, together with at least one processor, to cause the UE to execute at least the following:
[0024] Program instructions used to cause the following operations:
[0025] After a maximum permissible exposure MPE event occurs during operation on the first carrier, causing the UE to cease operation on the first carrier, a first signal is received on the second carrier. The first signal is used to configure the UE to determine the status of the MPE event associated with the previously used first carrier.
[0026] In response to the reception of the first signal, determine the current state of the MPE event associated with the previously used first carrier; and
[0027] In response to the reception of the first signal, a second signal is transmitted on the second carrier, wherein the second signal includes an indication of the current state of an MPE event associated with the previously used first carrier.
[0028] According to at least some examples of this disclosure, a non-transitory computer-readable medium encoded with instructions that, when executed by at least one processor, cause at least the following operations to be performed:
[0029] After a maximum permissible exposure MPE event occurs during the operation of the user equipment (UE) on the first carrier, causing the UE to cease operation on the first carrier, a first signal is received on the second carrier. The first signal is used to configure the UE to determine the state of the MPE event associated with the previously used first carrier.
[0030] In response to the reception of the first signal, determine the current state of the MPE event associated with the previously used first carrier; and
[0031] In response to the reception of the first signal, a second signal is transmitted on the second carrier, wherein the second signal includes an indication of the current state of an MPE event associated with the previously used first carrier.
[0032] According to at least some examples of this disclosure, a radio access network (RAN) node is provided, the RAN node comprising:
[0033] A component for transmitting a first signal on a second carrier after a maximum permissible exposure MPE event occurs during operation of a user equipment (UE) on a first carrier, causing the UE to cease operation on the first carrier. The first signal is used to configure the UE to determine the state of an MPE event associated with the previously used first carrier.
[0034] A component for receiving a second signal on a second carrier in response to the transmission of a first signal, wherein the second signal includes an indication of the current state of an MPE event associated with the previously used first carrier.
[0035] Based on at least some examples of this disclosure, a method is provided that includes:
[0036] After a maximum permissible exposure MPE event occurs during the operation of the user equipment (UE) on the first carrier, causing the UE to cease operation on the first carrier, a first signal is transmitted on the second carrier. The first signal is used to configure the UE to determine the state of the MPE event associated with the previously used first carrier.
[0037] A second signal is received on a second carrier in response to the transmission of a first signal, wherein the second signal includes an indication of the current state of an MPE event associated with the previously used first carrier.
[0038] According to at least some examples of this disclosure, computer program instructions are provided for causing a radio access network (RAN) node to perform the following operations:
[0039] After a maximum permissible exposure MPE event occurs during the operation of the user equipment (UE) on the first carrier, causing the UE to cease operation on the first carrier, a first signal is transmitted on the second carrier. The first signal is used to configure the UE to determine the state of the MPE event associated with the previously used first carrier.
[0040] A second signal is received on a second carrier in response to the transmission of a first signal, wherein the second signal includes an indication of the current state of an MPE event associated with the previously used first carrier.
[0041] According to at least some examples of this disclosure, a radio access network (RAN) node is provided, the RAN node comprising:
[0042] At least one processor; and
[0043] At least one memory including computer program instructions;
[0044] At least one memory and computer program instruction is configured, together with at least one processor, to cause the RAN node to execute at least the following:
[0045] After a maximum permissible exposure MPE event occurs during the operation of the user equipment (UE) on the first carrier, causing the UE to cease operation on the first carrier, a first signal is transmitted on the second carrier. The first signal is used to configure the UE to determine the state of the MPE event associated with the previously used first carrier.
[0046] A second signal is received on a second carrier in response to the transmission of a first signal, wherein the second signal includes an indication of the current state of an MPE event associated with the previously used first carrier.
[0047] According to at least some examples of this disclosure, a non-transitory computer-readable medium encoded with instructions that, when executed by at least one processor, cause at least the following operations to be performed:
[0048] After a maximum permissible exposure MPE event occurs during the operation of the user equipment (UE) on the first carrier, causing the UE to cease operation on the first carrier, a first signal is transmitted on the second carrier. The first signal is used to configure the UE to determine the state of the MPE event associated with the previously used first carrier.
[0049] A second signal is received on a second carrier in response to the transmission of a first signal, wherein the second signal includes an indication of the current state of an MPE event associated with the previously used first carrier.
[0050] According to at least some examples of this disclosure, a user equipment (UE) is provided, the UE comprising:
[0051] A component used to detect the occurrence of the maximum permissible exposure MPE event during operation on the first carrier.
[0052] Components used to determine connection loss on the first carrier;
[0053] A component for transmitting one or more signals for requesting a connection on a second carrier in response to the detection of an MPE event and the determination of a connection loss on a first carrier, wherein the one or more signals include an indication of the occurrence of an MPE event associated with the previously used first carrier.
[0054] Based on at least some examples of this disclosure, a method is provided that includes:
[0055] Detect the occurrence of the maximum permissible exposure MPE event during operation on the first carrier;
[0056] The connection on the first carrier wave was determined to be lost.
[0057] In response to the detection of an MPE event and the determination of a connection loss on a first carrier, one or more signals are transmitted to request a connection on a second carrier, wherein one or more signals include an indication of the occurrence of an MPE event associated with the previously used first carrier.
[0058] Based on various, but not necessarily all, examples of this disclosure, a computer program instruction is provided for causing the above-described methods to be executed.
[0059] According to at least some examples of this disclosure, a radio access network (RAN) node is provided, the RAN node comprising:
[0060] A component for receiving a signal from a user equipment (UE) requesting a connection on a second carrier after a maximum permissible exposure (MPE) event occurs during operation of the user equipment (UE) on a first carrier, causing the UE to cease operation on the first carrier, wherein the signal includes an indication of the occurrence of an MPE event associated with the previously used first carrier.
[0061] Based on at least some examples of this disclosure, a method is provided that includes:
[0062] After a Maximum Allowable Exposure (MPE) event occurs during operation of the User Equipment (UE) on the first carrier, causing the UE to cease operation on the first carrier, the UE receives a signal from the UE requesting a connection on the second carrier, wherein the signal includes an indication of the occurrence of an MPE event associated with the previously used first carrier.
[0063] Based on various, but not necessarily all, examples of this disclosure, a computer program instruction is provided for causing the above-described methods to be executed. Attached Figure Description
[0064] To better understand the various examples that contribute to the detailed description of this disclosure and certain examples of this disclosure, reference will now be made to the accompanying drawings by way of example only, in which:
[0065] Figure 1 An example of a wireless communication network suitable for use with the examples of this disclosure is illustrated schematically;
[0066] Figure 2Examples of UL beams with and without user obstruction are illustrated schematically;
[0067] Figure 3 An example of the maximum permissible effective isotropic radiated power (EIRP) based on the user distance to the UE and its impact on the UE range is shown;
[0068] Figure 4 An example of switching a UE from operating on a 5G NR FR2 carrier to operating on an LTE carrier is illustrated.
[0069] Figure 5 An example of a method according to this disclosure is illustrated schematically;
[0070] Figure 6 An example of another method according to this disclosure is illustrated schematically;
[0071] Figure 7 An example of signaling between a RAN node and a UE according to this disclosure is illustrated schematically;
[0072] Figure 8 An example of a reconnection process according to this disclosure is illustrated schematically;
[0073] Figure 9 Another example of a reconnection process according to this disclosure is illustrated schematically;
[0074] Figure 10 An example of a Media Access Control (MAC) control element (CE) suitable for use with the examples of this disclosure is illustrated schematically;
[0075] Figure 11 An example of a device according to this disclosure is illustrated schematically; and
[0076] Figure 12 An example of a computer program according to this disclosure is illustrated schematically.
[0077] These figures are not necessarily to scale. For clarity and brevity, certain features and views in the figures may be shown schematically or enlarged to aid in interpretation. For example, the dimensions of some elements in a figure may be exaggerated relative to others. Similar reference numerals are used in the accompanying figures to indicate similar features. For clarity, not all reference figures need to be shown in all accompanying figures.
[0078] List of abbreviations
[0079] 3GPP: Third Generation Partnership Project
[0080] 5G: Fifth Generation
[0081] CA: Carrier Aggregation
[0082] DC-CA: Dual-Connectivity Carrier Aggregation
[0083] EIRP: Effective Isotropic Radiated Power
[0084] EN-DC: E-UTRA—New Dual-Connect Radio
[0085] E-UTRA: Evolved UMTS Radio Access
[0086] FR1: Frequency range 1 (400MHz-6GHz)
[0087] FR2: Frequency range 2 (24GHz-52GHz)
[0088] gNB: gNodeB
[0089] ICNIRP: International Commission on Non-Ionizing Radiation Protection
[0090] IE: Information Elements
[0091] LTE: Long Term Evolution
[0092] MAC CE: Media Access Control Element
[0093] mmW: Millimeter wave
[0094] MN: Master Node
[0095] MR-DC: Multiple Radio Access Technology - Dual Connectivity
[0096] MPE: Maximum Permissible Exposure
[0097] NG: Next Generation
[0098] NR: New Radio / Next Radio
[0099] NR-DC: NR-NR dual connectivity
[0100] PBO: Power off
[0101] P-MPR: Power Management Maximum Power Reduction
[0102] RAN: Radio Access Network Node
[0103] RAT: Radio Access Technology
[0104] RLF: Radio link failure
[0105] RRC: Radio Resource Control
[0106] RSRP: Reference Signal Received Power
[0107] RSRQ: Reference Signal Reception Quality
[0108] SAR: Specific Absorption Rate
[0109] SCG: Auxiliary Community Group
[0110] S-RLF: Auxiliary RLF
[0111] SRB: Signaling Radio Bearer
[0112] SN: Secondary node
[0113] SS: Synchronization signal
[0114] UE: User Equipment
[0115] UL: Uplink
[0116] UMTS: Universal Mobile Telecommunications System
[0117] URLLC: Ultra-Reliable Low-Latency Communication Detailed Implementation
[0118] Figure 1 An example of network 100 is illustrated schematically. Network 100 includes multiple network nodes, including terminal node 110 (also known as user equipment), access node 120 (also known as RAN node, transmission receiving point, base station) and core network 130.
[0119] Terminal node 110 and access node 120 communicate with each other. Core network 130 communicates with access node 120. In some, but not all, examples, one or more core nodes of core network 130 may communicate with each other. In some, but not all, examples, one or more access nodes 120 may communicate with each other.
[0120] Network 100 may be a cellular network comprising multiple cells 122, each cell 122 being served by access node 120. The interface between terminal node 110 and access node 120 is radio interface 124. Access node 120 is a cellular radio transceiver. Terminal node 110 is a cellular radio transceiver.
[0121] In the specific example shown, network 100 is a next-generation (or new radio, NR) network. New radio is 3GPP's term for 5G technology. Terminal node 110 is user equipment (UE).
[0122] In this example, access node 120 can be a gNodeB (gNB), a Universal Terrestrial Radio Access Network (UTRAN) NodeB (NB), or an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) NodeB (eNB). Depending on the specific deployment scenario, access node 120 can be an ng-eNB or an en-gNB device. Access nodes 120 interconnect with each other via X2 or Xn interfaces 126. Access node 130 is also connected to the core network 130 via NG or S1 interfaces 128. Cellular network 100 can be configured to operate in licensed or unlicensed frequency bands.
[0123] Access node 120 can be deployed in NR standalone operation / scenario. Access node 120 can be deployed in non-standalone operation / scenario. Access node 120 can be deployed in carrier aggregation operation / scenario. Access node 120 can be deployed in dual-connectivity operation / scenario, i.e., multiple radio access technology - dual connectivity (MR-DC), especially for example:
[0124] Evolved Universal Terrestrial Radio Access - New Radio Dual Connectivity (EUTRA-NR-DC, also known as EN-DC),
[0125] New Radio-Evolved Universal Terrestrial Radio Access Dual Connectivity (NR-EUTRA-DC, also known as NE-DC),
[0126] Next-Generation Radio Access Network Evolution Universal Terrestrial Radio Access - New Radio Dual Connectivity (NG-RAN E-UTRA-NR Dual Connectivity, also known as NGEN-DC),
[0127] Or in the new radio dual connection (also known as NR-DC).
[0128] In such a non-standalone / dual-connectivity deployment, access nodes 120 can interconnect with each other via X2 or Xn interfaces and connect to the evolved packet core (EPC) via the S1 interface or to the 5G core (5GC) via the NG interface.
[0129] Access node 120 is a network element in the network responsible for radio transmission and reception to or from terminal node 110 in one or more cells 122. Such an access node may also be referred to as a Transmitter-Receiver Point (TRP) or a base station. Access node 120 is the network terminus of a radio link. Access nodes can be implemented as a single network device or distributed across two or more RAN nodes using different functional split architectures and different interfaces, such as Central Unit (CU), Distributed Unit (DU), and Remote Radio Header (RRH).
[0130] Terminal node 110 is a user-side device that terminates the radio link. It is a device that allows access to network services. Terminal node 110 can be a mobile terminal. Terminal node 110 can be a user equipment or a mobile station. The term "user equipment" can refer to a mobile device that includes a smart card (such as a subscriber identity module (SIM)) for authentication / encryption. In other examples, the term "user equipment" refers to a mobile device that includes a circuitry (such as a software SIM) embedded as part of the user equipment for authentication / encryption.
[0131] In the following description, access node 120 will be referred to as RAN node 120, and terminal node 110 will be referred to as UE 110.
[0132] Each of RAN node 120 and UE 110 may include one or more antennas, antenna patches, or antenna panels, each antenna, antenna patch, or antenna panel including an array of antenna elements. A controller controls the phase shift and amplitude of a radio frequency electrical signal applied to the antenna elements to generate a beamforming directional electromagnetic wave transmission signal with a controlled direction / beam steering direction and beam pattern (radiation pattern), thereby forming a transmission beam (e.g., a RAN node transmission beam for downlink transmission; and a UE transmission beam for uplink transmission). The transmission beam involves spatially directional transmission with power focused on a targeting direction or beam steering / pointing angle (such an angle corresponds to the direction of the main lobe of the transmitted radiation pattern).
[0133] The controller can process the phase shift and amplitude of the radio frequency electrical signal received from the antenna element (such radio frequency electrical signal corresponds to the electrical signal converted from the received electromagnetic wave signal) to achieve a preferred beamforming direction for reception, thereby forming a receive beam (e.g., a UE receive beam for downlink reception and a RAN node receive beam for uplink reception). The receive beam relates to spatially oriented reception, where the receive sensitivity is maximum at the aiming direction or pointing angle.
[0134] To form directional links for radio communications, beamforming can be used to compensate for high path loss due to poor radio frequency (RF) propagation, which can affect mmW / high-frequency transmissions that can be used with the 5G NR network during operation on 5G NR FR2 carriers, i.e., in the 24-52 GHz frequency range (compared to the sub-6 GHz range of 5G NR Frequency Range 1 (FR1)). In addition to beamforming, high-gain antennas are used to maintain the link budget required to maintain the connection link between the UE and the RAN node.
[0135] Signal transmission from the UE to RAN node 120 is an uplink (UL) transmission via an uplink (UL) beam. The UL beam can be considered as a beam pair, namely, the transmit beam (from the UE) and the receive beam (from the RAN node). Such a directional transmitter-side beam and a corresponding aligned directional receiver-side beam together provide the UL beam pair for UL transmission / reception and connectivity over a given carrier (such as a 5G FR2 carrier) (i.e., the optimal radio communication link / channel within the constraints of power, bandwidth, and signal quality over a given carrier). It should be understood that the transmit and receive beams are not necessarily physically aligned / directly line-of-sight aligned, especially in environments with abundant scattering.
[0136] In 5G NR networks, UL beams / beam pairs can be considered to be related to beamforming directional links from the UE to the RAN node. Such directional links have directional transmit beams (UE UL Tx beams) for UL transmission and corresponding directional receive beams (RAN node UL Rx beams) for UL transmission. These transmit and receive beams for UL transmission thus define UL beam pairs, also known simply as UL beams.
[0137] Figure 2 A portion of a wireless communication network is schematically shown, comprising a RAN node and two power class 3 (PC3) UEs operating over a 5G NR FR2 carrier (i.e., operating in the mmW portion of the electromagnetic spectrum).
[0138] Millimeter wave (mmW) spectrum offers the possibility of using a large portion of the continuous bandwidth to address high-throughput applications. 5G NR spectrum can be significantly higher than the spectrum used by LTE / 4G (ranging from 400MHz to 6GHz). In mmWave 5G NR, FR2 includes frequencies between 24GHz and 52GHz; and there is currently discussion about extending NR operation to the 52-114GHz range (frequency range 3).
[0139] However, operating high-gain antennas at such high frequencies raises concerns about user health. Therefore, there is a standard for the mmW range that specifies and regulates the maximum transmission power of the UE. Since frequencies below 100 GHz are non-ionizing, health concerns are limited to the thermal heating of body tissues while absorbing electromagnetic mmW energy. mmW frequencies produce a penetration depth of less than 1 mm, so potential thermal damage is limited to the surface of the skin and eyes. At 42 GHz, most of the energy is absorbed within the first 0.4 mm of human skin.
[0140] Governments have developed exposure guidelines to prevent health problems caused by thermal effects. At frequencies below 6 GHz (e.g., LTE), specific absorptivity (SAR) has been used to determine exposure thresholds. SAR measures the energy absorbed by the human body when exposed to an electromagnetic field. In the United States, the FCC sets a SAR limit of 1.6 W / kg, which is the average value over 1 g of tissue. In Europe, the average value is 2 W / kg over 10 g of tissue. The 1 g average provides finer resolution for studies of energy absorption in the human body.
[0141] In the mmWave region, where penetration depth is less than 1 mm, even 1 gram of tissue represents a considerable volume. Because it is difficult to define 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, not a volumetric energy distribution. MPE (Mean Physical Expansion) is a regulation concerning PD for the mmWave region. The Federal Communications Commission (FCC), the International Commission on Non-Ionizing Radiation Protection (ICNIRP), and several other regulatory agencies impose MPE constraints on transmitters at various carrier frequencies, particularly those such as mmWave transmissions. MPE constraints are typically defined based on short-term time-averaged radiated power, medium-term time-averaged radiated power, local spatial averaged radiated power, and / or intermediate spatial averaged radiated power. The implementation of MPE constraints can prevent hazardous operating conditions, ensure optimal user health, and / or reduce electromagnetic pollution or noise / interference from mmWave transmissions.
[0142] The FCC and ICNIRP set the MPE threshold for the general public at 10 W / m². 2 (1mW / cm 2 The energy absorbed by the human body increases as the distance to the UE decreases. Therefore, to comply with MPE constraints, the UE may have to reduce its output power if the user is close to the antenna. The UE can determine and comply with MPE constraints autonomously or locally. For example, the UE can detect the distance from the UE's antenna or antenna array to a part of the user's body (e.g., hand, face, ankle, etc.), determine the MPE constraint based on the detected distance, and transmit using MPE-compliant limited UL power based on the detected distance.
[0143] Figure 2 Examples of UE UL beams with the user not blocked (Case 1) and UE UL beams with the user blocked are shown.
[0144] In scenario 1, there is an unobstructed line-of-sight (LOS) propagation path for the UE UL beam from the UE to the RAN node. In scenario 2, a part of the human body obstructs the path of the UE UL beam from the UE to the RAN node.
[0145] In Case 1, the peak effective isotropic radiated power (EIRP) of the PC3 UE is +34 dBm, while in Case 2, the UE must reduce its output power to comply with MPE regulations because the user is exposed to the radiated beam and is very close to the radiated beam.
[0146] Figure 3 The diagram shows the relationship between the maximum permissible effective isotropic radiated power (EIRP) and the distance to the UE, as well as the relationship between the maximum permissible effective isotropic radiated power (EIRP) and the transmission range of the UE.
[0147] Figure 3 The graph on the left shows the relationship between the maximum permissible EIRP (i.e., the maximum permissible EIRP that complies with MPE limits) and the distance between the UE and the user. In this example, for the PC3 UE, the maximum permissible peak EIRP decreases by more than 20 dBm when the user approaches the touch antenna (1 cm away). Figure 3 The graph on the right shows the relationship between the maximum allowed EIRP and the UE's LOS range. It can be seen that reducing the maximum allowed EIRP significantly affects the UE's range, thereby degrading the signal quality received at the RAN node.
[0148] When an MPE event occurs at a UE connected / linked to the RAN node on a 5G NR FR2 carrier (such as in Case 2), the MPE limitation (i.e., a reduction in the UE's UL transmit power) can be very severe, leading to a radio link failure (RLF). A significant reduction in output power (e.g., a reduction of at least 20 dB in the output power of a PC3 UE) can result in a loss of connection to the RAN node and an RLF, where the required power reduction (i.e., the maximum power reduction in power management (P-MPR)) is too large to maintain the current link. The UE may be able to indicate the presence of an MPE event (potentially including a P-MPR value) to the network before the RLF event occurs so that the network can take appropriate corrective actions (e.g., handover, DC / CA reconfiguration).
[0149] At this point, the network only knows that the UE is operating in 5G NR FR2 and that communication is impossible due to the limited maximum allowed UL power caused by MPE events / MPE restrictions. In the case of non-standalone 5G operation, where control plane communication and mobility management require an LTE anchor, the network can switch the UE to LTE operation (i.e., e-UTRA), that is, switch the 5G NR FR2 carrier to an LTE carrier. This can happen, for example, when the UE notifies the network of a 5G NR FR2 link failure via a signaling procedure such as a secondary cell group (SCG) failure indication. Alternatively, when the primary link also fails, the UE can autonomously switch to an LTE carrier via an RRC re-establishment procedure. In the case of re-establishment, in the examples of this disclosure, the UE can also indicate that the 5G NR FR2 link failed due to MPE when transmitting signaling to the network notifying the reason for re-establishment.
[0150] For FR1 operation at frequencies below 6 GHz, the SAR specification differs from the MPE specification (the MPE specification applies to frequencies above 6 GHz). Furthermore, the FR1 antenna can be located on the UE at locations other than the FR2 antenna array. Therefore, while a user's body parts (e.g., hands) may be in the transmission path from the FR2 antenna array, no body parts may be in the transmission path from the FR1 antenna. For these reasons, transitioning from a 5G NR FR2 carrier to an LTE carrier may result in the UE not experiencing any UL power limitations.
[0151] Figure 4 An example is illustrated where a UE 110 with 5G NR FR2 capability switches from operating on 5G NRFR2 carrier 201 to operating on LTE carrier 202 due to MPE event 204 to avoid RLF.
[0152] Initially, at time t1, UE 110 operates fully or partially on the 5G NR FR2 carrier 201 with MPE protection / restriction (e.g., utilizing carrier aggregation (CA) and / or dual connectivity (DC)) and is connected to the serving gNB 120; that is, the UE is in the RRC_Connected state. The user's hand 203 is not on the propagation path of the serving beam (from antenna panel P1) serving the RAN node, therefore no MPE event occurs. When the UE operates on 5G NR FR2, the UE is monitoring for MPE events.
[0153] At time t2, while the UE is still operating on 5G NR FR2 carrier 201 and is still in the RRC_Connected state with the serving gNB, the user covers antenna panel P1.
[0154] The UE includes 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 various ways, including 60GHz radar. Based on the proximity sensors, the UE can autonomously back off its transmission power to comply with MPE requirements. Therefore, the proximity detector can detect and trigger an MPE event 204. The UE reports the presence of the MPE event on the 5G NR FR2 carrier 201. The resulting UL transmission power limitation is so severe that the UE is redirected to LTE, i.e., the 5G NR FR2 carrier is switched (e.g., via handover, RLF, or CA / DC reconfiguration) to an LTE carrier where MPE protection / limitation is not applicable.
[0155] At time t3, antenna panel P1 no longer operates on the 5G NR FR2 carrier. However, the UE is now connected on LTE carrier 202.
[0156] Typically, operators have more available spectrum on 5G NR FR2 than on LTE below 6GHz. Therefore, from the operator's perspective, they want to get UEs with 5G NR FR2 capabilities back to FR2 operation as soon as possible.
[0157] However, a problem faced by traditional UEs with 5G NR FR2 capabilities is that MPE event monitoring and reporting will not continue after the UE is reconfigured to operate over LTE (because 5G and LTE operations are very different).
[0158] Since the UE is currently operating on LTE, the network does not know when the UE will no longer experience MPE events or when the UE is ready to resume 5G NR FR2 operation. When connected via LTE, the network does not know the current state of MPE events on FR2, and therefore cannot optimally initiate a transition back to FR2.
[0159] Therefore, in order to redirect the UE back to 5G NR FR2 operation, traditionally, the network will periodically request the UE to extend its operation back to FR2, as long as the MPE event is still active and ongoing (e.g., Figure 4 If this happens at time t3, it will be unsuccessful. From a network operations perspective, such an uncoordinated process is inefficient because frequent attempts to restore unsuccessful FR2 links waste resources.
[0160] At time t4, antenna panel P1 is still not operating on the 5G NR FR2 carrier. Instead, the UE is still connected to the gNB on LTE carrier 202. However, the user's hand has left panel P1, causing the MPE events associated with the 5G NR FR2 carrier to stop / terminate, meaning that if the UE re-establishes operation on the 5G NR FR2 carrier, there will no longer be MPE restrictions limiting the UE's UL power transmission. However, since for legacy UEs, once a UE that has switched to an LTE carrier is no longer operating on the 5G NR FR2 carrier, there is no MPE monitoring and no MPE events are reported to the network, the network does not know when the UE is ready to resume 5G NR FR2 operation.
[0161] Some examples of this disclosure seek to address the problem of recovery to 5G NR FR2 (which has been reconfigured or converted to LTE due to the MPE event) when an MPE event ceases. Some examples of this disclosure seek to address optimized recovery of 5G NR FR2 (which has been reconfigured or converted to 5G NR FR1 due to the MPE event) when an MPE event ceases. Some examples of this disclosure seek to provide an improved process for resuming UE operation on a previously used carrier that has already experienced an MPE event.
[0162] To optimize resource utilization recovery (e.g., 5G NR FR2 carrier operation or virtually any high-frequency carrier operation experiencing MPE restrictions, constraints, and regulatory requirements), the network needs MPE information, such as information related to whether the UE is no longer experiencing severe FR2 MPE events (i.e., whether the UE no longer detects human body parts near the UE, or whether the required power back-off is still severe).
[0163] This disclosure provides an example of a novel signaling mechanism in the 3GPP specification that enables a UE, configurable by the network / RAN node via a second carrier, to continue monitoring MPE events and their status / conditions on the first carrier, and to autonomously / on-demand report MPE termination / recovery events to the RAN node on the second carrier. In this way, a UE capable of operating on a 5G NR FR2 carrier, even if it has stopped using the 5G NR FR2 carrier due to MPE events on the 5G NR FR2 carrier and has switched to another carrier (e.g., an LTE carrier or a 5G FR1 carrier), can still report MPE events associated with the 5G NR FR2 carrier, such as indicating the termination / stopping or recovery of MPE events to the network, which can then move the UE back to the 5G NR FR2 carrier.
[0164] As will be further discussed below, in the examples of this disclosure, even if the UE is no longer currently operating on a 5G NR FR2 carrier but on an LTE or 5G FR1 carrier, the MPE event is still monitored by the UE on 5G NR FR2 and reported to the network. The UE indicates to the network that the MPE event has terminated (even though the situation where it should have used FR2 has ended). Such a report of the status / condition of the MPE event (i.e., an indication of the current status of the MPE, i.e., an indication of whether the MPE is still active or stopped) can be:
[0165] Event-triggered (e.g., the UE determines that UL power is allowed to exceed a certain threshold, which can be configured by the network).
[0166] Periodic (i.e., sent periodically after the initial report of an MPE event),
[0167] According to the timer (i.e., the UE only reports to the network if the MPE event ends within the configured or predetermined duration),
[0168] Or any combination of the above (e.g., event-triggered periodic reporting with timers).
[0169] Such indication of the status / condition of an MPE event can be achieved through a toggling bit (i.e., "MPE no longer needed") in the transmitted signal / MPE report. The signal / MPE report may also include additional information related to the MPE event, such as the required power back-off, the duration since the UE detected the termination of the MPE event, or other information related to the occurrence and duration of the impact of the MPE termination.
[0170] Therefore, the examples of this disclosure can help provide MPE information to the network (e.g., RAN node gNB or eNB). This allows the network to attempt FR2 usage only when the MPE event has ended or recovered / is no longer so severe, enabling the UE to provide the required link budget, i.e., power backoff (PBO), to connect to the network over the 5G NR FR2 carrier. The implementation of the examples of this disclosure requires no new hardware and relies solely on the output of a proximity sensor already embedded in the UE, i.e., nearby user detection. This implementation relies on the UE continuing to monitor the 5G NR FR2 MPE event state after the UE has triggered an MPE event and been switched to a new carrier, even though the UE is not operating on 5G NR FR2. Based on the user antenna spacing distance determined by sensors such as proximity sensors and measurements of reference signals transmitted over the 5G NR2 carrier (e.g., synchronization signal block (SSB), channel state information reference signal (CSI-RS)), the power backoff required by the UE on all or specific arrays can be determined. MPE monitoring on the UE is not resource-intensive or battery-intensive. In fact, the UE is likely to perform MPE monitoring in a similar manner to listening for SS bursts for periodic link monitoring and initial access.
[0171] Figure 5 An example of a method 500 according to the present disclosure is illustrated schematically. The method 500 can be implemented by a device such as UE 110.
[0172] The method includes: in block 501, after an MPE event occurs during operation on a first carrier causing the UE to cease operation on the first carrier, receiving a first signal on a second carrier for configuring the UE to determine the state (or condition) of an MPE event associated with the previously used first carrier;
[0173] In some examples, the UE stops operating on the first carrier, at least in part, based on an MPE event during operation on the first carrier. In some examples, the UE may detect the occurrence of an MPE event during operation on the first carrier and, in response, stop operating on the first carrier. In some examples, due to an MPE event, the UE may switch from operating on the first carrier to operating on a second carrier, thus ceasing operation on the first carrier. This switch can be a reconfiguration, reconnection, or handover, i.e., causing the device to cease operation on the first carrier. The switch can be an ordered / managed switch, where the initial detection of the presence of an MPE event is signaled to the network, in response to which the network initiates a reconfiguration or handover process, thereby switching the device from the first carrier to the second carrier. In some examples, the switch can be a non-network-initiated switch, for example, where an RLF occurs due to an MPE event and the resulting MPE limitation requiring a significant reduction in the UE's UL transmission power, and the device subsequently initiates a reconnection process.
[0174] The first carrier can be, for example, a 5G NR FR2 carrier utilizing frequencies greater than 24 GHz and / or between 24 GHz and 52 GHz. The first carrier can also be a carrier in some other high-frequency range subject to MPE restrictions, i.e., greater than 6 GHz, particularly 52-114 GHz in the potential future frequency range 3 (FR3). The first carrier can be a carrier for a single connection link, a carrier for an MR-DC connection, a carrier for a CA connection, or even a carrier for a CA within an MR-DC.
[0175] The second carrier can be a different carrier from the first carrier. The second carrier can be, for example, an LTE carrier utilizing frequencies between 400MHz and 6GHz. The second carrier can be a 5G NRFR1 carrier operating at frequencies below 6GHz (where MPE restrictions do not apply). In some examples, such as when a CA is operating in an NR-DC connection or 5G NR FR2, the second carrier can be another 5G NR FR2, although that carrier is not affected by (or another) MPE event. In some examples, the second carrier can be a carrier in a different high-frequency range (i.e., >6GHz), although that carrier is not affected by (or another) MPE event. The second carrier can be a carrier of a single connection link, a carrier of an MR-DC connection, a carrier of a CA connection, or even a carrier of a CA in an MR-DC.
[0176] Initially, the UE could operate on at least the first carrier, meaning the UE could connect entirely or partially to one or more RAN nodes on the first carrier (e.g., via MR-DC connection, CA connection, or even CA in MR-DC). However, after an MPE event, the UE no longer operates on the first carrier but instead operates on at least the second carrier; that is, the UE could connect entirely or partially to one or more RAN nodes on the second carrier. Initially, prior to the MPE event on the first carrier, the UE could operate on both the first carrier and at least the second carrier (e.g., via MR-DC connection, especially such as EN-DC), but after the MPE event, the UE no longer operates on the first carrier but instead operates on at least the second carrier (i.e., the UE stops operating on the first carrier and continues operating on the second carrier).
[0177] MPE events may involve one or more of the following: detection of a user's body portion in the propagation path of UL transmissions of a device operating on the first carrier; detection of the proximity / distance of the user's body portion to the device (i.e., a distance less than a threshold); determination of the UL transmission power backoff required to comply with MPE limits / tolerances; determination of the maximum permissible UL transmission power to comply with MPE limits; and / or comparison of the maximum permissible UL transmission power with the minimum UL transmission power used to maintain the radio link / connection on the first carrier (this may be determined, in particular, in part based on monitoring a reference signal from the RAN node on the first carrier).
[0178] The status / condition of the MPE event associated with the previously used first carrier can be the status of the MPE event, such as its current status, such as whether the MPE event on the first carrier is still active (condition = ON) or whether it has been terminated / resumed (condition = OFF).
[0179] In block 502, the state / condition of the MPE event associated with the previously used first carrier is determined in response to the reception of the first signal.
[0180] Therefore, receiving the first signal configures the UE to continue monitoring MPE events, such as continuing to detect the presence of the user's body parts and their proximity to the UE / antenna panel, and to determine whether MPE restrictions are needed to ensure MPE compliance, such as reducing UL transmission power.
[0181] In block 503, in response to the reception of the first signal, a second signal is transmitted over the second carrier, wherein the second signal includes an indication of the current status / condition of an MPE event associated with the previously used first carrier.
[0182] Therefore, examples of this disclosure can provide signaling to configure the UE to continue monitoring MPE events even if the UE has stopped using the first carrier (e.g., the UE may have switched from operating on a 5G NR FR2 carrier to operating on a second carrier). Furthermore, such monitoring can be used to determine the current state / condition of the MPE event, e.g., whether the MPE event has terminated and was signaled to the RAN node on the second carrier. Advantageously, this can provide the RAN node with the necessary information to decide whether to resume UE operation on the 5G NR FR2 carrier. Thus, examples of this disclosure can achieve optimal 5G NR FR2 resource utilization and optimal link recovery / carrier re-establishment, i.e., optimal spectrum and resource allocation.
[0183] In some examples, the first signal of an RRC message may configure the UE to monitor the state of MPE events associated with the previously used first carrier. In response to the reception of the first signal, the current state of the MPE events associated with the previously used first carrier is monitored, both while the UE is still operating on the second carrier and no longer operating on the first carrier. The UE may include components for continuing to monitor the first carrier even after switching to the second carrier. Such components may in particular include one or more antennas / antenna panels of the UE configured to receive signals (such as reference signals) at the frequency of the first carrier (such as 5G NR FR2) and to measure its signal characteristics (such as measuring the power and quality of the received signal, e.g., Reference Signal Received Power (RSRP) and (RSRQ)). Based on such signal measurements, and measurements of the proximity of the user to the UE / antenna / antenna panel via sensors such as proximity detectors, the transmit power backoff (i.e., P-MPR) required to meet MPE limits can be determined. Therefore, when the UE no longer uses the first carrier (e.g., has switched from the first carrier to the second carrier), such MPE-related information associated with the MPE events associated with the previously used first carrier can be determined.
[0184] In some examples, the first signal is a request for MPE information, while the second signal is an MPE information report related to an MPE event. The second signal can be transmitted via RRC or MAC signaling (as will be discussed further below).
[0185] The first signal can configure the UE's reporting, such as its content and when it should be transmitted. The second signal may include indications of one or more of the following:
[0186] Is the MPE event active / still active?
[0187] Has the MPE event stopped / terminated / resumed / no longer existed?
[0188] The power reduction value, i.e., the P-MPR required to meet the MPE limit;
[0189] UL transmission power, i.e., the maximum permissible UL transmission power in compliance with MPE limits;
[0190] The expected probability of a MPE event recurring can be determined based on machine learning of typical usage / past MPE events;
[0191] One or more signal level parameter values, i.e., measurements used to determine reference signals such as RSRP and RSRQ; and
[0192] The amount of time elapsed after the MPE event;
[0193] The amount of time elapsed after the transition from operation on the first carrier to the second carrier.
[0194] The above items can be determined / measured for all or specific arrays / receive beams of a UE used for 5G NR FR2 reception.
[0195] In some examples, the second signal is transmitted in the following manner:
[0196] Periodically;
[0197] At least partially based on timers,
[0198] In response to the fulfillment of a condition, such as when it is determined that no part of the user's body is present in the propagation path of the first carrier, and / or
[0199] In response to additional signals / new requests for MPE information.
[0200] The first signal can configure the basis for transmitting the second signal, that is, the factors that trigger the transmission of the second signal (e.g., transmitting the second signal in response to determining that a measured / determined signal characteristic value of a received reference signal meets a criterion about a threshold signal characteristic value set by the RAN node in its first signal).
[0201] In some examples, determining the current state / conditions of an MPE event includes:
[0202] Components used to detect the proximity of a user's body part to the UE antenna; and / or
[0203] A component used to measure one or more characteristics (SSB, CSI-RS) of one or more reference signals received on a first carrier.
[0204] In some examples, the UE detects the initial occurrence of an MPE event during UE operation on the first carrier (e.g., such detection can occur while the UE is operating on the first carrier and before the UE switches to operation on the second carrier). The UE can determine that the connection on the first carrier is lost, such as due to a radio link failure. In response to the detection of the MPE event and the determination of the lost connection on the first carrier, the UE can transmit one or more signals to request a connection on the second carrier. Such signals can be RRC signaling, such as RRC messages, such as RRC connection request messages or RRC connection re-establishment request messages. In the case of re-establishment, the UE can also indicate that the connection loss on the first carrier was due to MPE when transmitting signaling to the network notifying them of the reason for re-establishment.
[0205] Figure 6 An example of method 600 according to the present disclosure is illustrated schematically. Method 600 can be implemented by means such as RAN node 120.
[0206] In block 601, after an MPE event occurs during UE operation on the first carrier, causing the UE to cease operation on the first carrier, the RAN node transmits a first signal on the second carrier. The first signal is used to configure the UE to determine the state / condition of the MPE event associated with the previously used first carrier.
[0207] In some examples, the UE stops operating on the first carrier at least in part based on an MPE event during operation on the first carrier. In some examples, the UE can switch from operating on the first carrier to operating on the second carrier, so that the UE no longer operates on the first carrier. This switch can be a reconfiguration, reconnection, or handover, i.e., causing the device to no longer operate on the first carrier.
[0208] In block 602, in response to the transmission of the first signal, the RAN node receives a second signal on the second carrier, wherein the second signal includes an indication of the current status / condition of an MPE event associated with the previously used first carrier.
[0209] In some examples, the RAN node can determine whether to re-establish UE operation on the first carrier, at least in part based on the received second signal. Such a determination may also take into account one or more radio conditions of the first carrier, such as its current traffic load. In response to this determination, the RAN node can decide to re-establish UE operation on the first carrier and implement appropriate procedures in this regard, such as transitioning the UE back to operation on the 5G NR FR2 carrier.
[0210] In some examples, prior to the transmission of the first signal, the RAN node receives from the UE a signal requesting a connection on the second carrier, wherein this signal includes an indication of the occurrence of an MPE event associated with the previously used first carrier. Such a signal can thus indicate to the RAN node that the UE was previously connected on the first carrier but lost the connection due to the MPE event. Once the connection on the second carrier is established, such a signal can trigger the RAN node to transmit a first signal requesting the status / conditions of the MPE event associated with the previously used first carrier.
[0211] Figure 7 An example of signaling 700 between UE 110 and RAN node 120 according to this disclosure is illustrated schematically.
[0212] Initially, the UE connects to the RAN node (i.e., in RCCCONNECTED state) on the first carrier (e.g., a 5G NR FR2 carrier). Following the detection of an MPE event at 701 (e.g., a user body portion in the path of the UE's 5G NR FR2 UL transmission beam), at 702, the UE signals the RAN node to notify of the MPE event report. In response to the MPE report, at 703, the RAN node signals the UE to reconfigure it for operation on the second carrier.
[0213] At 704, when the UE connects to the RAN node (i.e., in RCC CONNECTED state) on the second carrier (e.g., an LTE carrier or a 5G FR1 carrier), the RAN node transmits a first signal received by the UE. In response to the reception of the first signal, the UE continues to monitor MPE events on the first carrier. At 705, the UE determines that the MPE event has terminated. This could be due to, for example, determining that a part of the user's body has moved so that it is no longer in the path of the 5G NR FR2 UL transmission beam. Alternatively, this could be due to determining that the minimum UL transmission power required to maintain the 5G NR FR2 connection has decreased below the maximum permissible UL transmission power that still complies with MPE limits; for example, the UE may have changed location / moved closer to the RAN node, or radio conditions may be favorable for the 5G NR FR2 connection.
[0214] In response to the determination at 706 that the MPE event has been terminated, this triggers the UE to transmit a second signal including an indication of the termination of the MPE event.
[0215] At 707, in response to the reception of a second signal indicating that the MPE event has been terminated, the RAN node can again trigger the process of reconfiguring the UE to operate on the first carrier 5G NR FR2 carrier.
[0216] The various examples discussed above are primarily described in relation to a UE transitioning its connection from the RAN node from 5G NR FR2 to LTE and then back to 5G NR FR2. However, it should be understood that the examples in this disclosure are applicable to other configurations, particularly such as dual connectivity (DC) and carrier aggregation (CA).
[0217] In DC, the UE can simultaneously transmit and receive data on multiple component carriers from two cell groups via the primary RAN node (MN) and the secondary RAN node (SN), where each cell group contains at least one carrier (i.e., such that MN and / or SN can have multiple carriers). The first and second carriers can be component carriers of either the primary RAN node or the secondary RAN node.
[0218] In CA, the UE can simultaneously transmit and receive data from a single RAN node on multiple component carriers. The first carrier and the second carrier can be component carriers among the multiple component carriers of the RAN node in CA.
[0219] In DC-CA, the UE can simultaneously transmit and receive data from the primary RAN node and / or the secondary RAN node on multiple component carriers. The first carrier and the second carrier can be component carriers among the multiple component carriers of the primary and / or secondary RAN nodes in DC-CA.
[0220] Figure 8 An example of a reconnection process according to this disclosure is illustrated schematically. The figure shows a flowchart of the process for the UE and the RAN node.
[0221] As shown in box 801, the RAN node's receipt of an MPE report (e.g., signal 702 discussed above) indicating the presence of an MPE event affecting 5G NR FR2 triggers the network (operating under non-standalone 5G with LTE anchor) to switch the UE from 5G NR FR2 to LTE. Based on the MPE report, it can be determined that the required P-MPR on 5G NR FR2 is too high, so the network decides that switching the UE to LTE is the safest option (i.e., to comply with MPE limits and avoid RLF). As shown in box 802, the UE has switched to LTE and connected to LTE. As shown in box 803, the network knows that the previous 5G NR FR2 connection was terminated due to the MPE event because of the MPE report received.
[0222] As shown in box 804, the network requests an MPE event termination report (similar to the transmission of signal 704 and the "first signal" discussed in the examples above). The MPE termination report can be configured by the network, such as its content and when it should be transmitted to the RAN node. In some examples, this report is sent autonomously by the UE.
[0223] In response to the receipt of this request, the UE continues to monitor 5G NR FR2 related aspects / events, especially the current status of 5G NR FR2 MPE events, even if the UE is not currently performing 5G NR FR2 configuration or communication. The UE transmits MPE reports to the RAN node via active LTE carriers.
[0224] As shown in box 805, based on the received MPE report, the RAN node determines whether the MPE event has terminated or has become less severe / sufficiently weakened so that the required MPE limit for UE transmission power is not too high, thus falling below the acceptable minimum UE UL transmission power for a 5G NR FR2 connection over a 5G NR FR2 carrier. If so, the flowchart proceeds to box 806; otherwise, the process returns to box 804 and waits for further MPE reports.
[0225] As shown in box 806 (which may be optional), the RAN node determines whether other radio conditions (e.g., current traffic load over the 5G NR FR2 cell) are favorable / suitable for reconnecting to 5G NR FR2. If so, the flowchart can proceed to box 807; otherwise, the process can loop back to box 804 and await further MPE reports. It should be understood that the order of boxes 805 and 806 is interchangeable.
[0226] As shown in box 807, after the successful determination in boxes 805 and 806, the RAN attempts to reconnect the UE to 5G NRFR2.
[0227] Figure 8 This indicates a managed / orderly transition from 5G NR FR2 to LTE, which occurs because the RAN node has received the initial MPE report at box 801 and is able to take remedial measures to avoid RLF and reconfigure the UE for LTE operation over the LTE carrier.
[0228] Figure 9 Another example of a reconnection process according to this disclosure is illustrated schematically. Figure 9 This indicates a situation where the network management transition from 5G NR FR2 to LTE cannot be performed and RLF (Restricted Link Fault) cannot be avoided. For example:
[0229] The UE may be unable to transmit its MPE report to the RAN node.
[0230] The MPE report may have been transmitted, but the RAN node never received it, and the UE does not have enough UL transmission budget to repeat the transmission of the MPE report before the RLF timer expires, or
[0231] The RAN node was unable to take timely remedial measures to reconfigure the UE for LTE operation over LTE carriers before the RLF timer expired.
[0232] Therefore, as shown in box 902, the UE needs to request a connection to the network, i.e., via an RRC message. However, since the UE can connect to a different RAN node than its previous connection, the new RAN node is unaware of the MPE event on the previous 5G NR FR2 connection to the previously connected RAN network node. Therefore, in the example of this disclosure, the connection request RRC message includes an indication of the occurrence of a 5G NR FR2 MPE event, possibly with an identifier of the affected 5G NR FR2 carrier. Thus, as shown in box 804, the network (e.g., the new RAN node with a different connection than the previously connected RAN node) knows that the previous 5G NR FR2 connection was terminated due to the MPE event.
[0233] Figure 9 The remaining boxes shown (805-807) and Figure 8 The frames described are the same.
[0234] Using the method proposed in this disclosure, once the network knows both inputs, the network will only attempt MPE event carrier (e.g., 5G NR FR2) link reconfiguration:
[0235] 1) The UE is able to reuse the MPE event carrier (e.g., 5G NR FR2) (i.e., the MPE event ends and / or UL power is sufficient).
[0236] 2) The MPE event carrier (e.g., FR2) system and radio conditions are appropriate (e.g., the UE detects that the radio conditions meet the requirements set by the network configuration or determined autonomously by the UE).
[0237] MPE event carrier (e.g., 5G NR FR2) link recovery is optimized after the MPE event, which means:
[0238] 1) Once the MPE event stops, UEs operating on LTE should return to the MPE event carrier (e.g., 5G NR FR2).
[0239] 2) When the MPE event is still valid, the network should not waste resources by frequently requesting to switch to the MPE event carrier (e.g., 5GNR FR2).
[0240] Other use cases exemplified in this disclosure will now be described.
[0241] Consider the following use case:
[0242] 1) MPE events during MR-DC connection, where
[0243] a.SN uses only the FR2 carrier (i.e., FR1-FR2 DC).
[0244] b.SN uses both FR1 and FR2 carriers (i.e., FR1-FR2 CA in SN).
[0245] 2) MPE events during NR-DC connection, where
[0246] a. MN uses FR1, SN uses FR2 (i.e., FR1-FR2 DC).
[0247] b. Both MN and SN use FR2 (i.e., FR1-FR2 CA in SN).
[0248] c. MN uses FR2, SN uses FR1 (i.e., FR2-FR2 DC).
[0249] In both of these scenarios, the network has several potential responses to the UE:
[0250] I. Release SN and return to MN operation.
[0251] II. Switch to another cell / RAT when MPE is detected.
[0252] III. During MPE, allow the UE to trigger RLF or S-RLF (causing RRC re-establishment or indicating secondary cell group (SCG) failure to the MN).
[0253] Although the exact signaling varies depending on the combination used, what they have in common is that when triggered to report the termination of an MPE event, the UE no longer utilizes the carrier where the MPE event occurred. The following basic logic applies to all of these cases:
[0254] -UE detects and reports MPE on the carrier.
[0255] - The network resolves MPE issues (network behavior, applicable only to certain different initiation conditions) by releasing or changing some or all serving cells. This may cause the UE to operate under LTE or NR, but use a non-FR2 frequency or disable the FR2 frequency (i.e., measured but not used) or pause it (neither measured nor used), and therefore be unable to utilize the carrier where the MPE event occurred. The network determines whether the MPE event termination / resumption signaling should be allowed.
[0256] - The UE detects the termination of a previously triggered MPE event and reports it to the network using (multiple) currently utilized carriers (including information related to the MPE event).
[0257] Two aspects of the examples in this disclosure are:
[0258] 1) MPE event termination / recovery signaling mechanism, and
[0259] 2) MPE event termination / recovery signaling content.
[0260] For 1), the signaling can be RRC or MAC CE:
[0261] For RRC, signaling can be initiated by the UE (e.g., ULInformationTransferMRDC, UEAssistanceInformation) or polled by the network (e.g., UEInformationRequest and UEInformationResponse).
[0262] For MAC CE, this information can be fully triggered by the UE (e.g., a new UL MAC CE), or it can also include a request and response (e.g., a new DL MAC CE following a new UL MAC CE as a response to stop further reporting).
[0263] For 2), at least the following information can be considered:
[0264] The currently used P-MPR
[0265] Currently available FR2 UL transmission power
[0266] Time since MPE event termination / resumption event detection
[0267] The expected probability of the MPE event recurring (based on, for example, UE machine learning algorithms).
[0268] The signal level of the FR2 carrier detected by the UE or configured by the network (when the UE is measuring the FR2 carrier).
[0269] Any combination of the above
[0270] The various examples disclosed herein provide a mechanism for notifying the network of the status / condition of an MPE event, and the ability to resume operation on 5G NR FR2 (e.g., after a severe MPE event causes a radio link failure on 5G NR FR2, or after a transition to LTE by autonomous or network configuration). The following are example methods for notifying the network of the MPE event status before attempting to use a 5G NR FR2 carrier again:
[0271] When no user blocking is detected, the UE autonomously triggers a report of MPE event termination.
[0272] Network configuration is derived from periodic MPE event updates from the UE (e.g., frame-based reports).
[0273] When the network wants to configure 5G NR FR2 (e.g., when configuring EN-DC using a 5G NR FR2 carrier), the network polls the UE, and the UE sends a polling response (e.g., via RRC or MAC signaling, as described below).
[0274] The network uses, for example, a UL power threshold to configure MPE event termination reporting, which instructs the UE to report an event when its available UL power (i.e., in consideration of MPE events, in compliance with MPE limits) exceeds the threshold.
[0275] An example of signaling used in this disclosure will now be described.
[0276] Signaling used to indicate MPE event termination / recovery can be via RRC or MAC signaling. For RRC / MAC signaling indicating MAC CE, various alternatives exist as listed below 1) and 2):
[0277] 1) Use RRC signaling with OtherConfig and UEAssistanceInformation (network configured, UE triggered). The network can use such RRC signaling to instruct the UE to send auxiliary information for MPE event termination / recovery using existing UEAssistanceInformation messages when an MPE event occurs.
[0278] An example is shown below (note that the highlighted parts indicate the new configuration / new IE):
[0279] -OtherConfig
[0280] IE OtherConfig contains configurations related to other configurations.
[0281] OtherConfig information element
[0282]
[0283]
[0284] -UEAssistanceInformation
[0285] The UEAssistanceInformation message is used to indicate UE assistance information to the eNB.
[0286] Signal radio bearer: SRB1
[0287] RLC-SAP: AM
[0288] Logical Channel: DCCH
[0289] Direction: UE to E-UTRAN
[0290] UEAssistanceInformation message
[0291]
[0292]
[0293] 2) Use RRC signaling for UEInformationRequest / UEInformationResponse (polling from the network). The network can also actively poll the UE to report information via the existing RRC request-response mechanism shown below (note that the highlighted part indicates the new configuration / new IE):
[0294] -UEInformationRequest
[0295] UEInformationRequest is a command used by E-UTRAN to retrieve information from the UE.
[0296] Signal radio bearer: SRB1
[0297] RLC-SAP: AM
[0298] Logical Channel: DCCH
[0299] Direction: E-UTRAN to UE
[0300] UEInformationRequest message
[0301]
[0302]
[0303] -UEInformationResponse
[0304] The UE uses the UEInformationResponse message to transmit information requested by E-UTRAN.
[0305] Signal radio bearer: SRB1 or SRB2 (when including recorded measurement information)
[0306] RLC-SAP: AM
[0307] Logical Channel: DCCH
[0308] Direction: UE to E-UTRAN
[0309] UEInformationResponse message
[0310]
[0311]
[0312]
[0313] 3) MAC CE indicating MPE event: In this case, the MAC CE will contain this information.
[0314] Figure 10 An example of a MAC CE suitable for use with the examples of this disclosure is illustrated schematically. Figure 10 The MAC CE is shown, which has:
[0315] The M bit (i.e., 1 indicates that the MPE event is ON, and 0 indicates that it is OFF)
[0316] The current duration of the MPE event,
[0317] P-MPR, and
[0318] RSRP / RSRQ measured from FR2 carrier / cell.
[0319] It should be understood that other methods can be used to transmit MPE information, namely, requesting MPE information and reporting MPE information, which can provide detailed examples of the above signaling.
[0320] Various, but not all, examples of this disclosure may take the form of methods, apparatus, or computer programs. Therefore, various, but not all, examples may be implemented in hardware, software, or a combination of hardware and software.
[0321] Various examples, but not all examples, of this disclosure are described using flowchart illustrations and schematic block diagrams. It should be understood that each block (of the flowcharts 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 processors, processing circuitry systems, or controllers(s) such that they execute on the processor, processing circuitry system, or controller to create components for causing the implementation of the functions specified in the one or more blocks, i.e., such that the method can be implemented by a computer. The computer program instructions can be executed by the processor(s) such that they cause the processor(s) to perform a series of operational steps / actions to produce a computer-implemented process, such that the instructions executing on the processor(s) provide steps for implementing the functions specified in the one or more blocks.
[0322] Therefore, a box supports: a combination of components for performing a specified function; a combination of actions for performing a specified function; and computer program instructions / algorithms for performing a specified function. It will also be understood that each box and box combination can be implemented by a system based on dedicated hardware or a combination of dedicated hardware and computer program instructions that performs a specific function or action.
[0323] Various, but not necessarily all, examples of this disclosure provide a method and corresponding means including various modules, components, or circuit systems that provide functionality for performing / applying the method. These modules, components, or circuit systems can be implemented as hardware or as software or firmware to be executed by a computer processor. In the case of firmware or software, examples of this disclosure can be provided as a computer program product including a computer-readable storage structure thereon embodying computer program instructions (i.e., software or firmware) for execution by a computer processor.
[0324] Figure 11 An example of controller 800 is shown. Controller 800 may be located within a device such as UE 110 or RAN node 120, which also includes a radio transceiver 809. The device may be implemented by a computing device, particularly those described above. In some, but not necessarily all, examples, the device may be embodied as a chip, chipset, or module, i.e., for any of the above. Implementation of controller 800 may be as a controller circuit system. Controller 800 may be implemented solely in hardware, have certain aspects implemented in software including firmware, or may be a combination of hardware and software (including firmware).
[0325] like Figure 11 As shown, the controller 800 can be implemented using instructions that implement hardware functions, for example, by using executable instructions of a computer program 806 in a general-purpose or special-purpose processor 802, which can be stored on a computer-readable storage medium (disk, memory, etc.) for execution by such processor 802.
[0326] Processor 802 is configured to read from and write to memory 804. Processor 802 may also include an output interface and an input interface, via which processor 802 outputs data and / or commands, and via which data and / or commands are input to processor 802.
[0327] Memory 804 stores a computer program 806 including computer program instructions (computer program code) that control the operation of devices 110 and 120 when loaded into processor 802. The computer program instructions of computer program 806 enable the devices to perform the operations described above. Figures 5-9 The logic and routines of the methods, processes, procedures, and signaling are shown in the diagram. Processor 802 is able to load and execute computer program 806 by reading memory 804.
[0328] Although memory 804 is shown as a single component / circuit system, it can be implemented as one or more separate component / circuit systems, some or all of which may be integrated / removable and / or provide permanent / semi-permanent / dynamic / cache storage.
[0329] Although processor 802 is shown as a single component / circuit system, it can be implemented as one or more separate component / circuit systems, some or all of which may be integrated or removable. Processor 802 may be a single-core or multi-core processor.
[0330] Although examples of devices have been described above based on various components, it should be understood that these components may be embodied as corresponding controllers or circuit systems, such as one or more processing elements or processors of the device, or controlled by corresponding controllers or circuit systems. In this regard, each of the above-described components may be one or more of any device, component, or circuit system embodied in hardware, software, or a combination of hardware and software, configured to perform the corresponding function of the aforementioned corresponding component.
[0331] In the example where the device is located within UE 110, the device therefore includes:
[0332] At least one processor 802; and
[0333] At least one memory 804 including computer program code,
[0334] At least one memory 804 and computer program code are configured, together with at least one processor 802, to cause the device to perform at least the following:
[0335] After the user equipment (UE) changes from operating on at least the first carrier to operating on the second carrier due to the occurrence of a maximum permissible exposure MPE event during operation on the first carrier, causing the UE to no longer operate on the first carrier, a first signal is received on the second carrier. The first signal is used to configure the UE to determine the state of the MPE event associated with the previously used first carrier.
[0336] In response to the reception of the first signal, determine the current state of the MPE event associated with the previously used first carrier; and
[0337] In response to the reception of the first signal, a second signal is transmitted on the second carrier, wherein the second signal includes an indication of the current state of an MPE event associated with the previously used first carrier.
[0338] In the example where the device is located within RAN node 120, the device therefore includes:
[0339] At least one processor 802; and
[0340] At least one memory 804 including computer program code,
[0341] At least one memory 804 and computer program code are configured, together with at least one processor 802, to cause the device to perform at least the following:
[0342] After the UE changes from operating on at least the first carrier to operating on the second carrier due to the occurrence of a maximum permissible exposure MPE event during operation on the first carrier, causing the UE to no longer operate on the first carrier, a first signal is transmitted on the second carrier. The first signal is used to configure the UE to determine the state of the MPE event associated with the previously used first carrier.
[0343] A second signal is received on a second carrier in response to the transmission of a first signal, wherein the second signal includes an indication of the current state of an MPE event associated with the previously used first carrier.
[0344] Based on some examples of this disclosure, a system including the aforementioned UE and RAN node is provided.
[0345] like Figure 12 As shown, computer program 806 can reach devices 110 and 120 via any suitable transmission mechanism 810. Transmission mechanism 810 can 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 recording medium (such as an optical disc read-only memory (CD-ROM) or a digital versatile disc (DVD) or solid-state storage), or an article of manufacture that includes or tangibly embodies computer program 806. The transmission mechanism can be a signal configured to reliably transmit computer program 806. Devices 110 and 120 can propagate or transmit computer program 806 as a computer data signal.
[0346] In some examples of this disclosure, a computer program instruction is provided for causing UE 110 to perform at least the following operations or for performing at least the following operations:
[0347] After the user equipment (UE) changes from operating on at least the first carrier to operating on the second carrier due to the occurrence of a maximum permissible exposure MPE event during operation on the first carrier, causing the UE to no longer operate on the first carrier, a first signal is received on the second carrier. The first signal is used to configure the UE to determine the state of the MPE event associated with the previously used first carrier.
[0348] In response to the reception of the first signal, determine the current state of the MPE event associated with the previously used first carrier; and
[0349] In response to the reception of the first signal, a second signal is transmitted on the second carrier, wherein the second signal includes an indication of the current state of an MPE event associated with the previously used first carrier.
[0350] In some examples of this disclosure, computer program instructions are provided for causing RAN node 120 to perform at least the following operations or for performing at least the following operations:
[0351] After the UE changes from operating on at least the first carrier to operating on the second carrier due to the occurrence of a maximum permissible exposure MPE event during operation on the first carrier, causing the UE to no longer operate on the first carrier, a first signal is transmitted on the second carrier. The first signal is used to configure the UE to determine the state of the MPE event associated with the previously used first carrier.
[0352] A second signal is received on a second carrier in response to the transmission of a first signal, wherein the second signal includes an indication of the current state of an MPE event associated with the previously used first carrier.
[0353] References to “computer-readable storage medium,” “computer program product,” “tangible computer program,” or “controller,” “computer,” “processor,” etc., should be understood to include not only computers with different architectures (such as single / multiprocessor architectures and sequential (von Neumann) / parallel architectures), but also special-purpose circuits, such as field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), signal processing devices, and other processing circuitry systems. References to computer programs, instructions, code, etc., should be understood to encompass software such as programmable processors or firmware, including the programmable content of hardware devices, whether processor instructions or configuration settings for fixed-function devices, gate arrays, or programmable logic devices.
[0354] As used in this application, the term "circuit system" may refer to one or more or all of the following:
[0355] (a) Pure hardware circuit system implementation (such as implementations only in analog and / or digital circuit systems), and
[0356] (b) A combination of hardware circuitry and software, such as (if applicable):
[0357] (i) A combination of (multiple) analog and / or digital hardware circuits and software / firmware, and
[0358] (ii) Any part of a hardware processor(s) having software (including multiple digital signal processors(s)), software, and memory, which work together to cause device 100 (such as a mobile phone or server) to perform various functions, and
[0359] (c) (Multiple) hardware circuits and / or (multiple) processors, such as (multiple) microprocessors or a portion thereof, which require software (e.g., firmware) to operate, but may be absent when operation is not required.
[0360] The definition of "circuit system" applies to all uses of the term in this application, including in any claim. As another example, as used in this application, the term "circuit system" also covers only implementations of hardware circuitry or processors and their accompanying software and / or firmware. For instance, if applicable to a particular claim element, the term "circuit system" also covers baseband integrated circuits for mobile devices or similar integrated circuits in servers, cellular network devices, or other computing or networking devices.
[0361] Figures 4 to 9 The stages shown may represent steps in a method and / or code segments in computer program 806. The description of a specific order of boxes does not necessarily indicate that a required or preferred order exists, and the order and arrangement of boxes can be changed. Furthermore, some boxes may be omitted.
[0362] When a structural feature is described, the structural feature may be replaced by a component that performs one or more functions of the structural feature, whether the function or these functions are explicitly described or implicitly described.
[0363] As can be understood from the above, in some examples, a system is provided that includes at least one UE110 and at least one RAN node120.
[0364] In some, but not all, examples, particularly in use cases such as enhanced mobile broadband (eMBB), the UE can be embodied in a handheld portable electronic device, such as a mobile phone, wearable computing device, or personal digital assistant, which may additionally provide one or more audio / text / video communication functions (e.g., telecommunication, video communication, and / or text transmission (SMS / MMS / email) functions), interactive / non-interactive viewing functions (e.g., web browsing, navigation, TV / program viewing functions), music recording / playback functions (e.g., Motion Picture Experts Group I Audio Layer 3 (MP3) or other formats and / or (FM / AM) radio broadcast recording / playback), data download / transmission functions, image capture functions (e.g., using (e.g., built-in) digital camera), and gaming functions.
[0365] UE can also refer to Internet of Things (IoT) devices, large-scale industrial networks, smart city infrastructure, wearable devices, connected medical devices, autonomous devices, etc. These types of UE devices can operate for extended periods without human intervention (e.g., performing maintenance, replacing or recharging device batteries, etc.), may have reduced processing power and / or memory storage, may have reduced battery storage capacity due to a smaller form factor, can be integrated into machinery (e.g., heavy machinery, factory machinery, sealing equipment, etc.), and can be installed / located in hazardous or hard-to-reach environments, etc.
[0366] The device can be housed in a module. As used herein, "module" refers to a unit or device that does not include certain parts / components to be added by the final manufacturer or user.
[0367] In some, but not all, examples, UE 110 and RAN node 120 are configured to transmit data with or without local storage of data in memory 804 at UE 110 or RAN node, and with or without local processing of the data by a circuit system or processor at UE 110 or RAN node 120. Data may be stored remotely at one or more devices in processed or unprocessed formats. Data may be stored in the cloud. Data may be processed remotely at one or more devices. Data may be partially processed locally and partially processed remotely at one or more devices. Data may be wirelessly transmitted to remote devices via short-range radio communication such as Wi-Fi or Bluetooth, or via long-range cellular radio links. The device may include a communication interface, such as a radio transceiver for data communication.
[0368] UE 110 and RAN node 120 can be part of an Internet of Things (IoT) network that forms part of a larger distributed network.
[0369] Data processing (whether local or remote) can be used for health monitoring, data aggregation, patient monitoring, vital sign monitoring, or other purposes.
[0370] As used herein, the term "determine" (and its grammatical variations) can include, in particular, claculating, computing, processing, deriving, investigating, searching (e.g., looking up in a table, database, or other data structure), confirming, etc. Furthermore, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data in memory), obtaining, etc. Additionally, "determine" can include resolving, selecting, picking, establishing, etc.
[0371] In this specification, unless otherwise expressly stated, references to “a”, “an”, “the” [feature, element, component, means, etc.] shall be interpreted as “at least one” [feature, element, component, means, etc.].
[0372] The term "comprise" as used in this document is inclusive rather than exclusive. That is, any reference to X that includes Y means that X may include only one Y or may include multiple Ys. If the intention is to use "comprise" with an exclusive meaning, it will be clearly stated in the context by referring to "comprising only one" or using "consisting".
[0373] Various examples are referenced in this specification. Descriptions of features or functions associated with examples indicate that such features or functions exist in that example. The use of the terms “example,” “for example,” “may,” or “may” in the text indicates (whether explicitly stated or not) that such features or functions exist at least in the described example, whether or not they are described as examples, and that they may, but not necessarily, exist in some or all other examples. Therefore, “example,” “for example,” “may,” or “may” refers to a specific instance of a class of examples. An instance’s properties may be properties of only that instance, properties of the class, or properties of subclasses of the class that include some, but not all, instances of that class. Therefore, it is implicitly disclosed that features described with reference to one example and not another may be used as part of a working composition in that other example where possible, but are not necessarily required to be used in that other example.
[0374] In this specification, various examples are referenced, and adjectives or adjective phrases are used to describe the characteristics of the examples. Such descriptions of characteristics associated with examples indicate that the characteristic exists exactly as described in some examples and substantially as described in others.
[0375] The description of a function should also be considered as disclosing any means suitable for performing that function. Where a structural feature is described, the structural feature may be replaced by a component for performing one or more functions of the structural feature, whether or not the function or these functions are explicitly described or implicitly described.
[0376] Although examples have been described with reference to various examples in the preceding paragraphs, it should be understood that modifications may be made to the given examples without departing from the scope of the claims.
[0377] The presence of a feature (or combination of features) in a claim is a reference to that feature or combination of features itself, as well as a reference to a feature (equivalent feature) that achieves substantially the same technical effect. Equivalent features include, for example, features that are variations and achieve substantially the same result in substantially the same manner. Equivalent features include, for example, features that perform substantially the same function in substantially the same manner to achieve substantially the same result.
[0378] The features described above can be used in combinations other than those explicitly described above.
[0379] Although features have been described with reference to certain characteristics, these features may be performed by other features, whether or not they are described. Similarly, although features have been described with reference to certain examples, these features may also exist in other examples, whether or not they are described. Therefore, a feature described with respect to one example / aspect of this disclosure may include any or all features described with respect to another example / aspect of this disclosure, and vice versa, provided they are not inconsistent with each other. Although specific terms are used herein, they are used only in a general and descriptive sense and not for limiting purposes.
[0380] The terms “a” or “the” as used in this document are inclusive, not exclusive. That is, any reference to X that includes a (a) or the (the) Y indicates that X may include only one Y or may include multiple Ys, unless the context clearly indicates otherwise. If “a” or “the” is intended to have an exclusive meaning, it will be clearly stated in the context. In some cases, “at least one” or “one or more” may be used to emphasize the inclusive meaning, but the omission of these terms should not be construed as inferring any exclusive meaning.
[0381] In the above description, the described apparatus may alternatively or additionally include apparatus that, in some other examples, includes a distributed apparatus system, such as a client / server apparatus system. In examples where the provided apparatus forms (or the 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 that collectively implement the embodiments of this disclosure. In some, but not necessarily all, examples, the apparatus is reconfigured by an entity other than its original manufacturer to implement the embodiments of this disclosure by being provided with additional software (e.g., software downloaded by a user), which, when executed, causes the apparatus to implement the embodiments of this disclosure (such implementation is either entirely implemented by the apparatus or as part of the apparatus system described above).
[0382] The foregoing description illustrates some examples of this disclosure; however, those skilled in the art will recognize possible alternative structures and methodological features that provide equivalent functionality to the specific examples of the structures and features described above, and for the sake of brevity and clarity, these structures and features have been omitted from the foregoing description. Nevertheless, the foregoing description should be understood to implicitly include references to such alternative structures and methodological features that provide equivalent functionality, unless such alternative structures or methodological features are expressly excluded in the foregoing description of the examples of this disclosure.
[0383] The examples and appended claims of this disclosure can be appropriately combined in any manner that is readily apparent to those skilled in the art.
[0384] Each claim is incorporated herein as additional disclosure, and the claims are embodiments of the invention(s). Furthermore, although the claims herein are provided to include specific dependencies, it is contemplated that any claim may depend on any other claim, and any such alternative embodiments and their equivalents are also within the scope of this disclosure to the extent that any features of the various claims may be combined, integrated, and / or omitted, and / or the dependencies of the claims may be altered.
[0385] Although the foregoing specification has been made to draw attention to features considered important, it should be understood that the applicant may seek protection by means of any patentable feature or combination of features mentioned above and / or shown in the drawings, whether or not it is emphasized.
Claims
1. A user equipment (UE), comprising: At least one processor; as well as At least one memory including computer program code; The at least one memory and the computer program code are configured to, together with the at least one processor, cause the UE to execute: The initial occurrence of the maximum permissible exposure MPE event is detected during operation on the first carrier. Based on the MPE event, a connection loss is determined on the first carrier; In response to the detection of the MPE event and the determination of the connection loss on the first carrier, one or more signals are transmitted to request a connection on the second carrier, wherein the one or more signals include an indication of the occurrence of the MPE event associated with the previously used first carrier; After the MPE event occurs during operation on the first carrier, causing the UE to cease operation on the first carrier, a first signal is received on the second carrier, the first signal being used to configure the UE to determine the state of the MPE event associated with the previously used first carrier; The current state of the MPE event associated with the previously used first carrier is determined in response to the reception of the first signal by the following: Detect the proximity of the user's body parts to the antenna of the UE; as well as Measure one or more characteristics of one or more reference signals received on the first carrier; as well as In response to the reception of the first signal, a second signal is transmitted on the second carrier, wherein the second signal is transmitted via the Media Access Control (MAC) control unit CE and includes the following: an indication of the current state of the MPE event associated with the previously used first carrier; an indication that the MPE event is still valid on the first carrier; and an estimated uplink UL transmission power backoff value for MPE compliance on the first carrier. The estimated UL transmission power value to be used on the first carrier; the expected probability that the MPE event will recur on the first carrier; one or more signal level parameter values measured on the first carrier; and the amount of time elapsed after the transition from operation on the first carrier to the second carrier.
2. The UE of claim 1, wherein the first carrier uses a frequency above 24 GHz and is monitored for MPE compliance.
3. The UE of claim 2, wherein the second carrier uses a frequency below 6 GHz and is not monitored for MPE compliance.
4. The UE of claim 3, wherein the UE is further caused to perform: in response to the first signal, when the UE is operating on the second carrier and no longer operating on the first carrier, monitoring the current state of the MPE event associated with the previously used first carrier.
5. The UE of claim 4, wherein the first signal includes a request for MPE information associated with the first carrier, and the second signal includes a report of MPEG information associated with the first carrier.
6. The UE of claim 5, wherein the second signal is transmitted in response to the reception of a new request.
7. The UE of claim 5, wherein the second signal is transmitted when it is determined that there is no longer a user body part in the propagation path of the first carrier.
8. A system for communication, comprising: User Equipment (UE); At least one processor; and At least one memory including instructions, which, when executed by the at least one processor, cause the UE to perform: The initial occurrence of the maximum permissible exposure MPE event is detected during operation on the first carrier. Based on the MPE event, a connection loss is determined on the first carrier; In response to the detection of the MPE event and the determination of the connection loss on the first carrier, one or more signals are transmitted to request a connection on the second carrier, wherein the one or more signals include an indication of the occurrence of the MPE event associated with the previously used first carrier; After the MPE event occurs during operation on the first carrier, causing the UE to cease operation on the first carrier, a first signal is received on the second carrier, the first signal being used to configure the UE to determine the state of the MPE event associated with the previously used first carrier; The current state of the MPE event associated with the previously used first carrier is determined in response to the reception of the first signal by the following: Detect the proximity of the user's body parts to the antenna of the UE; as well as Measure one or more characteristics of one or more reference signals received on the first carrier; as well as In response to the reception of the first signal, a second signal is transmitted on the second carrier, wherein the second signal is transmitted via the Media Access Control (MAC) control unit CE and includes the following: an indication of the current state of the MPE event associated with the previously used first carrier; an indication that the MPE event is still valid on the first carrier; and an estimated uplink UL transmission power backoff value for MPE compliance on the first carrier. The estimated UL transmission power value to be used on the first carrier; the expected probability that the MPE event will recur on the first carrier; one or more signal level parameter values measured on the first carrier; and the amount of time elapsed after the transition from operation on the first carrier to the second carrier.
9. The system of claim 8, wherein the first carrier uses a frequency above 24 GHz and is monitored for MPE compliance.
10. The system of claim 9, wherein the second carrier uses a frequency below 6 GHz and is not monitored for MPE compliance.
11. The system of claim 10, wherein the UE is further caused to perform: in response to the first signal, when the UE is operating on the second carrier and no longer operating on the first carrier, monitoring the current state of the MPE event associated with the previously used first carrier.
12. The system of claim 11, wherein the first signal includes a request for MPE information associated with the first carrier, and the second signal includes a report of MPEG information associated with the first carrier.
13. The system of claim 12, wherein the second signal is transmitted in response to the receipt of a new request.
14. The system of claim 12, wherein the second signal is transmitted when it is determined that no user body part exists in the propagation path of the first carrier.
15. A method for communication, comprising: The initial occurrence of the maximum permissible exposure MPE event is detected during operation on the first carrier. Based on the MPE event, a connection loss is determined on the first carrier; In response to the detection of the MPE event and the determination of the connection loss on the first carrier, one or more signals are transmitted to request a connection on the second carrier, wherein the one or more signals include an indication of the occurrence of the MPE event associated with the previously used first carrier; After the MPE event occurs during the operation of the user equipment (UE) on the first carrier, causing the UE to cease operation on the first carrier, a first signal is received on the second carrier, the first signal being used to configure the UE to determine the state of the MPE event associated with the previously used first carrier; The current state of the MPE event associated with the previously used first carrier is determined in response to the reception of the first signal by the following: Detect the proximity of the user's body parts to the antenna of the UE; as well as Measure one or more characteristics of one or more reference signals received on the first carrier; as well as In response to the reception of the first signal, a second signal is transmitted on the second carrier, wherein the second signal is transmitted via the Media Access Control (MAC) control unit CE and includes the following: an indication of the current state of the MPE event associated with the previously used first carrier; an indication that the MPE event is still valid on the first carrier; and an estimated uplink UL transmission power backoff value for MPE compliance on the first carrier. The estimated UL transmission power value to be used on the first carrier; the expected probability that the MPE event will recur on the first carrier; one or more signal level parameter values measured on the first carrier; and the amount of time elapsed after the transition from operation on the first carrier to the second carrier.
16. The method of claim 15, wherein the first carrier uses a frequency above 24 GHz and is monitored for MPE compliance.
17. The method of claim 16, wherein the second carrier uses a frequency below 6 GHz and is not monitored for MPE compliance.
18. The method of claim 17, further comprising: In response to the first signal, when the UE is operating on the second carrier and no longer operating on the first carrier, the current state of the MPE event associated with the previously used first carrier is monitored.
19. The method of claim 18, wherein the first signal includes a request for MPE information associated with the first carrier, and the second signal includes a report of MPEG information associated with the first carrier.
20. The method of claim 18, wherein the second signal is transmitted when it is determined that no user body part exists in the propagation path of the first carrier.