Patent Application
20240373359
The present disclosure pertains to the field of wireless communications. The present disclosure relates to methods for handling low energy conditions of an energy harvesting wireless device, a related network node and a related wireless device.
Future services will likely require cellular connectivity everywhere, anytime and in everything. This means that the number of devices that have to be wirelessly connected, which are also referred to as internet of Things (IoT) devices, is going to explode. A vast majority of these devices are battery powered and their batteries need to be recharged or replaced.
Changing/recharging batteries manually is not feasible, e.g., a trillion-IoT device in the world with 10-year battery life-time means that in total ˜274 billion batteries needs changing every day. In an IoT context, 10-years battery life means a 10-years battery operation without charging which cannot even be fulfilled in many applications.
Recycling batteries is another factor that needs to be taken into account, for instance in 2018 191 000 tones of portable batteries were sold in the EU but only near half the amount, i.e., 88 000 tones of used portable batteries were collected as waste to be recycled.
This means that new approaches need to be used to sustain the world's battery requirement since these materials are very limited. Energy harvesting is a potential candidate that can help avoid an exploding request for batteries in the world and keep the limited natural materials un-harvested.
For certain application of IoT devices, for example devices that are placed in difficult to reach and/or remote locations, it may be difficult to charge the device frequently and/or manually. This kind of IoT-device may typically be reporting sensor outputs infrequently. It may be equipped with a limited battery capacity. Hence, it may be charged in full capacity using energy harvesting.
Harvesting resources, however, might not be available all the time especially if they are harvested from ambient or natural resources. The harvesting capabilities also depend on whether a device is stationary in an indoor or outdoor environment or is a mobile device as the intensity of energy harvesting can vary based on its location and its activity. Consequently, the device might not be able to communicate with the network or other devices during a certain period when the instantaneous harvesting energy is not available, not enough and/or the stored energy level drops below a certain level. This condition may typically lead to excessive unnecessary signaling which may increase the overhead and usage of unnecessary energy resources when the device has harvested enough energy and restarts communication.
Accordingly, there is a need for devices and methods for handling low energy conditions of an energy harvesting wireless device, which may mitigate, alleviate, or address the existing shortcomings and may provide a solution that reduces energy consumption and latency for communications with an energy harvesting device.
A method is disclosed, performed by a network node, for handling low energy conditions of an energy harvesting wireless device, WD. The network node has stored a UE context of the WD received during a registration procedure with the WD. The method comprises receiving, from the WD, a message indicating that the WD has insufficient power level for performing regular radio operation for upcoming message exchange and indicating that the UE context of the WD is to be preserved for a time period during which the power level is insufficient.
Further, a network node is provided, the device comprising memory circuitry, processor circuitry, and a wireless interface, wherein the network node is configured to perform any of the methods disclosed herein for the network node.
It is an advantage of the present disclosure that the network node may be informed by the WD that the WD may have insufficient energy level for performing an upcoming message exchange and that the WD intends to resume communication with the network node upon harvesting a sufficient level of energy. Thereby, the network is aware that the WD, although it may not respond to signaling from the network node, has not left the network. The network node may thus indicate and/or convey to the network, such as to the core network, to preserve the UE context of the WD until the WD has a sufficient energy level and resumes communication with the network node. Since the UE context of the WD can be preserved, the WD is not required to perform a time consuming and energy draining registration procedure with the network to resume communications. A further advantage of the present disclosure is thus a reduced latency in the communication and/or a reduced energy consumption of the WD. Reduced energy consumption further reduces the time the WD is unavailable for communication.
A method is disclosed, performed by an energy harvesting wireless device (WD) for handling low energy conditions of the WD. The WD has a UE context generated during a registration procedure with the network node stored in the network. The method comprising determining whether an energy level of the WD is sufficient for performing regular radio operation for an upcoming message exchange. The method comprises, upon determining that the energy level is insufficient for performing regular radio operation for the upcoming message exchange, transmitting S203, to the network node, a message indicating that the WD has insufficient power level for performing regular radio operation for upcoming message exchange. The method comprises indicating that the UE context of the WD is to be preserved for a time period during which the power level is insufficient.
Further, a wireless device is provided, the device comprising memory circuitry, processor circuitry, and a wireless interface, wherein the wireless device is configured to perform any of the methods disclosed herein for the wireless device.
It is an advantage of the present disclosure that the WD may inform the network that the WD may have insufficient energy level for performing an upcoming message exchange and that the WD intends to resume communication with the network node upon harvesting a sufficient level of energy. Thereby, the network may be made aware that the WD, although it may not respond to signaling from the network node, has not left the network. The network node may indicate to the network, such as to the core network, to preserve the UE context of the WD until the WD has a sufficient energy level and resumes communication with the network node. Since the UE context of the WD can be preserved, the WD is not required to perform a time consuming and energy draining registration procedure with the network to resume communications. A further advantage of the present disclosure is thus a reduced latency in the communication and/or a reduced energy consumption of the WD. Reduced energy consumption further reduces the time the WD is unavailable for communication.
The above and other features and advantages of the present disclosure will become readily apparent to those skilled in the art by the following detailed description of examples thereof with reference to the attached drawings, in which:
Various examples and details are described hereinafter, with reference to the figures when relevant. It should be noted that the figures may or may not be drawn to scale and that elements of similar structures or functions are represented by like reference numerals throughout the figures. It should also be noted that the figures are only intended to facilitate the description of the examples. They are not intended as an exhaustive description of the disclosure or as a limitation on the scope of the disclosure. In addition, an illustrated example needs not have all the aspects or advantages shown. An aspect or an advantage described in conjunction with a particular example is not necessarily limited to that example and can be practiced in any other examples even if not so illustrated, or if not so explicitly described.
A connected mode may be referred to an operation mode wherein a data transmission can be communicated e.g., between the wireless device and a network node or between the wireless device and another wireless device. A connected mode may be referred to an operation state wherein a radio transmitter and/or a radio receiver is activated for such communication. A connected mode may be referred to an operation state wherein the wireless device is synchronized time-wise and/or frequency-wise e.g., by a determined timing advance parameter for the communication. Furthermore, it may be referred to as an operation state wherein transfer of unicast data to/from the wireless device can be performed. In certain communication systems, a connected mode may be referred to a radio resource control (RRC) state. In various examples, an active state may be a RRC connected state and/or an RRC active state. However, a connected mode may be an active period within another RRC state.
The dormant mode is a mode where the UE has no active connection with the network node. A dormant mode may be seen as an inactive mode of the wireless device. A dormant mode may be seen as a mode where the wireless device is unsynchronized with a timing of a network. In one or many examples the wireless device may in a dormant mode not have a valid timing advance information with respect to the network. A dormant mode may be seen as a mode where the wireless device may not be able to receive dedicated signaling. A dormant mode may be seen as a mode where closed loop power control is inactivated or suspended. Dormant mode may comprise RRC idle mode, RRC suspend and/or RRC inactive mode. For example, the wireless device may be in dormant mode when the connection with the network node has been released and/or suspended.
The figures are schematic and simplified for clarity, and they merely show details which aid understanding the disclosure, while other details have been left out. Throughout, the same reference numerals are used for identical or corresponding parts.
As discussed in detail herein, the present disclosure relates to a wireless communication system 1 comprising a cellular system, for example, a 3GPP wireless communication system. The wireless communication system 1 comprises a WD 300 and/or a network node 400. The WD 300 may be an energy harvesting wireless device configured use energy harvesting sources to harvest the energy required by the WD 300 for communicating with the network node 400 or a second WD 300A.
A network node disclosed herein refers to a radio access network (RAN) node operating in the radio access network or a CN node operating in the core network. The RAN node may be one or more of a base station, an evolved Node B, eNB, gNB in NR. In one or more examples, the RAN node is a functional unit which may be distributed in several physical units.
A core network, CN, node disclosed herein refers to a network node operating in the core network, such as in the Evolved Packet Core Network, EPC, and/or a 5G Core Network, 5 GC. Examples of CN nodes in EPC include a Mobility Management Entity, MME. Examples of CN nodes in 5 GC include Access and Mobility Management Function (AMF) and Service Management Function (SMF). In one or more examples, the CN node is a functional unit which may be distributed in several physical units.
The CN node 600 may be configured to communicate with the RAN node 400 via a link, such as a wired link, 12.
The wireless communication system 1 described herein may comprise one or more wireless devices 300, 300A, and/or one or more network nodes 400, such as one or more of: a base station, an eNB, a gNB and/or an access point, and one or more CN nodes 600.
A wireless device may refer to a mobile device, a user equipment (UE) and/or other devices having wireless capability, such as e.g., sensors wirelessly transmitting the measured data.
The wireless device 300, 300A may be configured to communicate with the network node 400 via a wireless link (or radio access link) 10, 10A.
Energy harvesting resources for harvesting energy by the WD might not be available all the time, especially if the energy harvesting resources are ambient or natural resources.
Additionally, the amount of energy that can be stored in a WD may be limited and the WD may thus run out of the back-up stored energy if the WD is not able to harvest energy. Consequently, the WD might not be able to communicate with the network or other devices during a certain period when the instantaneous harvesting energy is not enough and/or the stored energy level drops below a certain level. During this period the WD may currently get unregistered from the network, such as from the core network. When the WD gets unregistered from the network the network may discard the UE context for the WD. UE context may be seen as a set of information associated with a UE, such as the WD, that may be advantageous and/or necessary for communication with the core network, such as to maintain one or more services, such as to support one or more radio bearers, such as for Quality-of-service classes. For example, the UE context may comprise information indicative of a capability of the UE, and/or information indicative of the UE state and/or security information, and/or subscription identifiers and/or mobility information, such as defined in 3GPP TS 36.410 v. 16.0.0. and TS 23.502 v. 16.9.0 The UE context may be used to enable faster resuming to active state from e.g., idle state, e.g., from a state with lower energy level as disclosed herein. The UE context may comprise an EPS Radio Access Bearer (E-RAB) context, security context, roaming and access restrictions, UE S1 signaling connection ID(s). The UE context may be a set of information agreed upon between the WD and the network node during a registration procedure of the WD with the network. To resume communication the WD thus has to repeat all the registration signaling when the device has (harvested) sufficient energy for communication. When the WD is registered to the network it may also have to periodically update the registration, for example with a Periodic Registration Update to the Core Network, to notify the network that the WD is still reachable, such as by the network node. The WD may also perform Mobility Registration Updates when it has moved to another tracking area of the network, in order for the network to be able to page the WD. This signaling is power-consuming, which may lead to the energy level dropping significantly due to the registration signaling, sometimes to the extent that the energy level after performing the registration signaling is insufficient for upcoming message exchange. The tracking area update period is given from the Network, as defined in 3rd Generation Partnership Program (3GPP) TS 23.501 v. 17.1.1. If the WD does not send a tracking area update the Network may unregister the WD since it is not reachable and the location of the WD is unknown. For example, in case the WD is not able to respond to paging from the network or is not able to communicate with the network according to legacy RRC Connected mode or RRC Idle mode procedures, the network while have no understanding of the WD's where abouts, and hence believe and decide that the WD has left the network and will de-register the WD, such as the UE context of the WD, from the network.
The present disclosure provides a solution that alleviates or addresses the existing shortcomings, such as the shortcomings mentioned in relation to the method shown in
According to the present disclosure, the WD using energy harvesting can, when an event related to the energy level is triggered, indicate a communication condition, a traffic condition and/or remaining stored energy of the WD to the network or to other WDs. Thereby, the network and/or the other WDs can be made aware of the reason for not receiving a response from the WD and may does refrain from unregistering the WD. This allows the WD to stay connected with the network, without being dropped-out or getting unregistered, which reduces the signaling required by the WD for resuming communication once a sufficient energy level has been harvested.
The communication condition and/or traffic condition may be indicative of a current operation that may drain the stored energy of the WD. The communication condition and/or the traffic condition may be used by the network node to receive information about the operating conditions of the WD. Furthermore, the network node can also inform the WD on traffic conditions of an expected upcoming, such as subsequent message exchange. The network node may in one or more example methods transmit the traffic conditions via a paging message or via wake-up signaling).
In one or more example methods, the communication condition and/or traffic condition can be defined as the number of uplink and downlink transmissions and/or receptions (such as Physical Uplink Shared Channel (PUSCH), Physical Downlink Shared Channel (PDSCH), Physical Uplink Control Channel (PUCCH), and/or Physical Downlink Control Channel (PDCCH) transmission and/or receptions), or the number of messages within a certain duration of time.
In one or more example methods, the communication and/or traffic conditions (e.g., in RRC connected, in RRC-Inactive and in RRC Idle mode) can be predefined conditions, such as:
The event related to the energy harvesting may be one or more of:
The transmission of the indication of the communication condition and/or remaining stored energy can be done through one or more of the following.
When the WD is in RRC Connected mode, the indication may be transmitted as a new bits or new information element (IE) via e.g., UE assistance information or together with other UL transmissions.
When the WD is in RRC Idle or RRC inactive mode, the indication may be transmitted as a new information bit or new IE using Small Data Transmission (SDT) or legacy random-access procedure. This avoids the WD entering connected mode, and hence saving energy of the WD, if just for a communication status or energy level update.
In one or more example methods, upon the network node receiving the low energy level indication from the WD in connected mode, the network terminates and releases the WD to either Idle mode or Inactive mode within a certain time period.
In one or more example methods, upon the network node receiving the low energy level indication from the WD in connected mode, the network reduces the data rate for upcoming message exchange and remains in connected mode, based on the severity of the energy level and the energy harvesting situation. For example, if the energy level and the energy harvesting situation is sufficient for communicating with the reduced data rate.
The network node transmits a message 1102 indicative of expected properties, such as an expected traffic volume and/or expected energy level, of an upcoming message exchange to the WD. The message may be a paging message or a wake-up signal comprising the expected properties as additional information.
The WD predicts 1104, based on its potential harvesting capability, that its energy level is not sufficient for the message exchange indicated by the network node.
The WD transmits a message 1106 to the network node indicating that the WD has insufficient power level for performing regular radio operation for the upcoming message exchange. The indication may be transmitted according to a pre-configured and/or pre-specified code-word, indicative of the WDs insufficient energy level and a certain time period for which the energy level will be insufficient. The indication may be transmitted using SDT or early channel access messages, such as via a RACH procedure. The WD being unable to perform regular radio operation means that no communication can be performed, such as due to insufficient energy level. Regular radio operation herein means in accordance with (3GPP) TS spec or agreement, for example responding to paging, updates etc. Hence, not regular radio operation means that one or more activities (receive and/or transmit) that the WD would normally do if it would have enough power is skipped.
Upon receiving the message indicating that the WD has insufficient power level, the network, such as the network node, may update an energy status 1108 of the WD. The network node may keep the WD and its corresponding information, such as the UE context of the WD, for operation in IDLE mode. In other words, the network preserves the UE context of the WD in the core network until the WD has harvested a sufficient energy level for communicating with the network node, such as for the upcoming message exchange.
The procedure above may optionally be followed by a message from the WD to the network node indicating that the WD has sufficient energy for resuming communication.
Instead, the WD reaches a predetermined energy level and predicts 1204, based on its potential harvesting capability, that its energy level is not sufficient for an upcoming message exchange.
The WD transmits an un-solicitated message 1206 to the network node indicating that the WD has insufficient power level for performing regular radio operation for the upcoming message exchange. The indication may be transmitted according to a pre-configured and/or pre-specified code-word, e.g., Code A, Code B or Code C as described earlier, indicative of the WDs insufficient energy level and a certain time period for which the energy level will be insufficient. The indication may be transmitted via PUR or SDT or early channel access messages, such as via a RACH procedure. By transmitting the indication via PUR or SDT, the energy required for transmitting the indication may be reduced since the WD may be able to transmit the indication without performing a connection setup with the network.
Upon receiving the message indicating that the WD has insufficient power level, the network, such as the network node, may update information of the energy status 1208 of the WD. The network node may keep the WD and its corresponding information, such as the UE context of the WD, for operation in IDLE mode. In other words, the network preserves the UE context of the WD in the core network until the WD has harvested a sufficient energy level for communicating with the network node, such as for the upcoming message exchange.
The procedure above may optionally be followed by a message from the WD to the network node indicating that the WD has sufficient energy for resuming communication.
The method 100 comprises receiving S103, from the WD, a message indicating that the WD has insufficient power level for performing regular radio operation for upcoming message exchange and indicating that the UE context of the WD is to be preserved for a time period during which the power level is insufficient. Regular radio operation herein means that the WD is camping on a cell, performing cell measurements, doing cell reselection if needed, and/or monitors a paging channel for paging messages, as defined in 3GPP TS 38.304 v. 16.5.0, for the case of Idle mode operation. Not performing regular operation may herein mean that the WD is unable to perform one or more of these operations due to insufficient energy level. A message exchange herein means a transmission and/or a reception of a message, such as control signaling, data communication, and/or reading system information. In one or more example methods, the WD is operating in IDLE mode. The UE context being preserved may be seen as the network, such as the CN node 600, not discarding the UE context of the WD.
In one or more example methods, the message indicating an insufficient power level for performing radio operation is indicative of expected properties of the upcoming message exchange. In one or more example methods, the upcoming message exchange may be an Uplink (UL) data transmission, such as when the WD is in Radio Resource Control (RRC) connected mode and has data to transmit, the WD may indicate the expected properties of the upcoming message exchange to the network node. In one or more example methods, the expected properties may be one or more of an expected traffic volume and/or expected energy level, of an upcoming message exchange to the WD. In one or more example methods, the upcoming message exchange may be a scheduled preconfigured uplink transmission or early data transmission, such as carrying scheduled sensor data report at a scheduled time and/or predefined message size.
In one or more example methods, the method 100 comprises transmitting S101, to the WD, a message indicative of expected properties of the upcoming message exchange. In one or more example methods, the expected properties may be one or more of an expected traffic volume and/or expected energy level, of an upcoming message exchange to the WD. In one or more example methods, the message exchange may be initiated by the network node. This may for example be the case when the WD is in RRC IDLE mode or in RRC Inactive mode as defined in 3GPP TS 38.304 v. 16.5.0. In one or more example methods, the message indicative of expected properties of the upcoming message exchange is one or more of a paging signal and a wake-up signal.
In one or more example methods, the properties of the upcoming message exchange comprise one or more of an expected traffic volume, an expected traffic condition and an expected energy level. The traffic volume herein means a specific measured volume of data of the message exchanged, such as of a file transfer, or volume of data stored in a data buffer, such as an UL and/or DL buffer. Traffic condition herein means a traffic type, such as whether it is a continuous transmission or a specific traffic pattern and/or the associated typical data size, such as a traffic pattern being related to the application of the WD.
In one or more example methods, the message indicating the insufficient power level is a non-acknowledgement, NACK, message transmitted in response to the message indicative of expected properties of the upcoming message exchange. The NACK message may comprise additional information, such as the energy level of the WD, the WD's potential capability of harvesting energy and/or the time required to harvest a sufficient energy level.
In one or more example methods, the message indicating the insufficient power level comprises a code indicative of a predetermined energy condition of the WD. In one or more example methods, the indication can be done via a plurality of different specified codes, where each code can contain a certain information. In one or more examples, the indication can be done via a code A, a code B, or a code C. Transmission of these codes may indicate:
Based on the received code the network node may determine the time period during which the WD may be absent while harvesting energy. In one or more example methods, the network node may, based on the determined time period, determine the time the network is to preserve the UE context of the WD. In one or more example methods, the network node may, based on the determined time period, determine when the network node may resume communication with the WD.
In one or more example methods, the message indicating the insufficient power level is received via Preconfigured Uplink Resources, PUR, Small Data Transmission, SDT, and/or a channel access message, such as a Random Access Channel (RACH) message. In one or more example methods, the SDT may use a RACH procedure to convey the message indicating the insufficient power level. In one or more example methods, such as when the WD is in IDLE mode, the message indicating the insufficient power level may be an un-solicitated transmission by the WD via PUR or SDT.
In one or more example methods, the message indicating the insufficient energy level may indicate that the energy level is not sufficient for any upcoming communication for a certain time. In one or more example methods, the message indicating the insufficient energy level may be indicative of the WDs potential capability of harvesting energy. For example, the message may indicate that the WD may harvest x mW of energy in y min or may indicate that a sufficient energy level may be harvested in a certain time period.
In one or more example methods, the properties of the upcoming message exchange are represented in a bitmap format. In one or more example methods, the properties of the upcoming message exchange are represented in a bitmap format indicative of traffic conditions of the WD.
In one or more example methods, the method 100 comprises preserving S105 the UE context for the WD while refraining from communicating with the WD during the time period. Preserving the UE context herein means storing all parameters agreed during the registration process between the WD and the network node. In other words, the network keeps information about the WD so that communication can resume without the WD having to perform a new registration process with the network. Refraining from communicating with the WD means that the network. node will not attempt any communication with the WD, such as exchanging messages with the WD. In other words, there will be no signaling between the network node and the WD when the network node refrains from communicating with the WD. Upon receiving the message indicating that the energy level is insufficient, the network node may know that the WD is unavailable due to insufficient energy level for communication. The network node may thus preserve the UE context of the WD, and thus keep the WD connected, until the WD has harvested a sufficient energy level for resuming communications.
In one or more example methods, the method 100 comprises returning S107 to regular radio operation upon expiry of the time period, such as the time period for which the WD has indicated that it has insufficient energy level, or upon receiving a message from the WD indicating that the energy level is sufficient for performing radio operation. Regular radio operation herein refers to the legacy radio operation as indicated in
The method 200 comprises determining S202 whether an energy level of the WD is sufficient for performing regular radio operation for an upcoming message exchange.
The method 200 comprises, upon determining that the energy level is insufficient for performing regular radio operation for the upcoming message exchange, transmitting S203, to the network node, a message indicating that the WD has insufficient power level for performing regular radio operation for upcoming message exchange and indicating that the UE context the WD is to be preserved for a time period during which the power level is insufficient. This action S203 corresponds to the action S103 performed by the network node as discussed in relation to
In one or more example methods, the message indicating an insufficient power level for performing radio operation is indicative of expected properties of the upcoming message exchange. In one or more example methods, the upcoming message exchange may be an Uplink (UL) data transmission, such as when the WD is in Radio Resource Control (RRC) connected mode and has data to transmit, the WD may indicate the expected properties of the upcoming message exchange to the network node.
In one or more example methods, the method 200 comprises receiving S201, from the network node, a message indicative of expected properties of the upcoming message exchange. This may for example be the case when the WD is in RRC IDLE mode or in RRC Inactive mode as defined in 3GPP TS 38.304 v. 16.5.0. In one or more example methods, the message indicative of expected properties of the upcoming message exchange is one or more of a paging signal and a wake-up signal. This action S201 corresponds to the action S101 performed by the network node as discussed in relation to
In one or more example methods, the properties of the upcoming message exchange comprise one or more of an expected traffic volume, an expected traffic condition and an expected energy level. The traffic volume herein means a specific measured volume of data of the message exchanged, such as of a file transfer, or volume of data stored in a data buffer, such as an UL and/or DL buffer. Traffic condition herein means a traffic type, such as whether it is a continuous transmission or a specific traffic pattern, such as a traffic patter being related to the application of the WD.
In one or more example methods, the message indicating the insufficient power level is a non-acknowledgement, NACK, message transmitted in response to the message indicative of expected properties of the upcoming message exchange.
In one or more example methods, the message indicating the insufficient power level comprises a code indicative of a predetermined energy condition of the WD. In one or more example methods, the indication can be done via a plurality of different specified codes, where each code can contain a certain information. In one or more examples, the indication can be done via a code A, a code B, or a code C. Transmission of these codes may indicate:
Code C: harvesting and recharging energy storage device is on-going, pause the ongoing communication and resume communication after a certain time period.
In one or more example methods, the message indicating the insufficient power level is transmitted via Preconfigured Uplink Resources, PUR, Small Data Transmission, SDT, or a channel access message.
In one or more example methods, the properties of the upcoming message exchange are represented in a bitmap format.
In one or more example methods, transmitting S203 is performed upon triggering of an event. In one or more example methods, the event is the energy level of the WD being below an energy threshold. In one or more example methods, the event is the energy level of the WD being insufficient for a predicted energy level of the upcoming message exchange. In one or more example methods, the event is an instantaneous energy provided by energy harvesting is insufficient for operating a communication circuitry of the WD. In one or more example methods, the event is receiving a message initiating communication with the WD.
In one or more example methods, the method 200 comprises returning S205 to regular radio operation upon expiry of the time period or upon the energy level is sufficient for performing radio operation. This action S205 corresponds to the action S107 performed by the network node as discussed in relation to
In one or more example methods, the WD is operating in IDLE mode.
The network node 800 is configured to receive (such as via the interface 403), from the WD, a message indicating that the WD has insufficient power level for performing regular radio operation for upcoming message exchange and indicating that the UE context of the WD is to be preserved for a time period during which the power level is insufficient.
The interface 403 may be configured for wireless communications via a wireless communication system, such as a 3GPP system, such as a 3GPP system supporting one or more of: New Radio, NR, Narrow-band IoT, NB-IoT, Long Term Evolution, LTE, and Long Term Evolution-enhanced Machine Type Communication, LTE-M, supporting various frequency range, such as millimeter-wave communications, operating in licensed band and/or unlicensed band.
Processor circuitry 402 is optionally configured to perform any of the operations disclosed in
Furthermore, the operations of the network node 800 may be considered a method that the network node 800 is configured to carry out. Also, while the described functions and operations may be implemented in software, such functionality may also be carried out via dedicated hardware or firmware, or some combination of hardware, firmware and/or software.
Memory circuitry 401 may be one or more of a buffer, a flash memory, a hard drive, a removable media, a volatile memory, a non-volatile memory, a random access memory (RAM), or other suitable device. In a typical arrangement, memory circuitry 401 may include a non-volatile memory for long term data storage and a volatile memory that functions as system memory for processor circuitry 402. Memory circuitry 401 may exchange data with processor circuitry 402 over a data bus. Control lines and an address bus between memory circuitry 401 and processor circuitry 402 also may be present (not shown in
Memory circuitry 401 may be configured to store information (such as information related to energy conditions of the energy harvesting device, properties of an upcoming message exchange, and/or a UE context of the WD) in a part of the memory.
The wireless device 300 is configured to determine (such as using the processor circuitry 302), whether an energy level of the WD is sufficient for performing regular radio operation for an upcoming message exchange.
The wireless device 300 is configured to transmit (such as via the wireless interface 303), upon determining that the energy level is insufficient for performing regular radio operation for the upcoming message exchange, to the network node, a message indicating that the WD has insufficient power level for performing regular radio operation for upcoming message exchange and indicating that the UE context the WD is to be preserved for a time period during which the power level is insufficient.
The wireless interface 303 is configured for wireless communications via a wireless communication system, such as a 3GPP system, such as a 3GPP system supporting one or more of: New Radio, NR, Narrow-band IoT, NB-IoT, Long Term Evolution, LTE, and
Long Term Evolution-enhanced Machine Type Communication, LTE-M, supporting various frequency range, such as millimeter-wave communications, operating in licensed band and/or unlicensed band.
The energy harvesting circuit 304 may be configured to harvest energy from an energy source. The energy source may be an ambient energy (such as light energy, wind energy and/or vibration energy), or a dedicated energy source (such as wireless power transfer). Ambient energy harvesting relies on energy resources that are readily available in the environment and that can be sensed by wireless devices capable of harvesting energy where dedicated energy harvesting are characterized by on-purpose energy transmissions from dedicated energy sources to the energy wireless devices capable of harvesting energy.
The wireless device 300 is optionally configured to perform any of the operations disclosed in
Furthermore, the operations of the wireless device 300 may be considered a method that the wireless device 300 is configured to carry out. Also, while the described functions and operations may be implemented in software, such functionality may also be carried out via dedicated hardware or firmware, or some combination of hardware, firmware and/or software.
Memory circuitry 301 may be one or more of a buffer, a flash memory, a hard drive, a removable media, a volatile memory, a non-volatile memory, a random access memory (RAM), or other suitable device. In a typical arrangement, memory circuitry 301 may include a non-volatile memory for long term data storage and a volatile memory that functions as system memory for processor circuitry 302. Memory circuitry 301 may exchange data with processor circuitry 302 over a data bus. Control lines and an address bus between memory circuitry 301 and processor circuitry 302 also may be present (not shown in
Memory circuitry 301 may be configured to store information (such as information related to energy conditions of the energy harvesting device, properties of an upcoming message exchange, and/or a UE context of the WD) in a part of the memory.
Examples of methods and products (network node and wireless device) according to the disclosure are set out in the following items:
The use of the terms “first”, “second”, “third” and “fourth”, “primary”, “secondary”, “tertiary” etc. does not imply any particular order, but are included to identify individual elements. Moreover, the use of the terms “first”, “second”, “third” and “fourth”, “primary”, “secondary”, “tertiary” etc. does not denote any order or importance, but rather the terms “first”, “second”, “third” and “fourth”, “primary”, “secondary”, “tertiary” etc. are used to distinguish one element from another. Note that the words “first”, “second”, “third” and “fourth”, “primary”, “secondary”, “tertiary” etc. are used here and elsewhere for labelling purposes only and are not intended to denote any specific spatial or temporal ordering. Furthermore, the labelling of a first element does not imply the presence of a second element and vice versa.
It may be appreciated that
Other operations that are not described herein can be incorporated in the example operations. For example, one or more additional operations can be performed before, after, simultaneously, or between any of the described operations.
Certain features discussed above as separate implementations can also be implemented in combination as a single implementation. Conversely, features described as a single implementation can also be implemented in multiple implementations separately or in any suitable sub-combination. Moreover, although features may be described above as acting in certain combinations, one or more features from a claimed combination can, in some cases, be excised from the combination, and the combination may be claimed as any sub-combination or variation of any sub-combination
It is to be noted that the word “comprising” does not necessarily exclude the presence of other elements or steps than those listed.
It is to be noted that the words “a” or “an” preceding an element do not exclude the presence of a plurality of such elements.
It should further be noted that any reference signs do not limit the scope of the claims, that the examples may be implemented at least in part by means of both hardware and software, and that several “means”, “units” or “devices” may be represented by the same item of hardware.
The various example methods, devices, nodes and systems described herein are described in the general context of method steps or processes, which may be implemented in one aspect by a computer program product, embodied in a computer-readable medium, including computer-executable instructions, such as program code, executed by computers in networked environments. A computer-readable medium may include removable and non-removable storage devices including, but not limited to, Read Only Memory (ROM), Random Access Memory (RAM), compact discs (CDs), digital versatile discs (DVD), etc. Generally, program circuitries may include routines, programs, objects, components, data structures, etc. that perform specified tasks or implement specific abstract data types. Computer-executable instructions, associated data structures, and program circuitries represent examples of program code for executing steps of the methods disclosed herein. The particular sequence of such executable instructions or associated data structures represents examples of corresponding acts for implementing the functions described in such steps or processes.
Although features have been shown and described, it will be understood that they are not intended to limit the claimed disclosure, and it will be made obvious to those skilled in the art that various changes and modifications may be made without departing from the scope of the claimed disclosure. The specification and drawings are, accordingly, to be regarded in an illustrative rather than restrictive sense. The claimed disclosure is intended to cover all alternatives, modifications, and equivalents.
| Number | Date | Country | Kind |
|---|---|---|---|
| 2151086-2 | Aug 2021 | SE | national |
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/EP2022/073764 | 8/26/2022 | WO |
