Method and systems for optimizing downlink traffic in low power wide area networks
The server system optimizes downlink message delivery in LPWANs by scheduling based on priority and probability, addressing bandwidth and interference issues to ensure timely and reliable transmission of critical control messages.
Patent Information
- Application Number
- PCT/FI2024/050240
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-19
- Filing Date
- 2024-05-17
- Publication Date
- 2024-11-28
AI Technical Summary
Low Power Wide Area Networks (LPWANs) face limitations in downlink message delivery due to limited resources, bandwidth constraints, and interference between downlink and uplink communications, particularly in simplex or half-duplex systems, which can lead to delayed or missed critical control messages.
A server system that retrieves and schedules downlink transmission requests based on priority values and forecasted uplink message priority, optimizing transmission opportunities by considering the probability of message receipt and available gateways, to ensure timely and prioritized delivery of downlink messages.
This approach enhances the reliability and efficiency of downlink message transmission in LPWANs, ensuring critical messages are delivered promptly, such as those controlling smart meters during power shortages, while minimizing interference and maximizing bandwidth utilization.
Smart Images

Figure FI2024050240_28112024_PF_FP_ABST
Abstract
Description
METHOD AND SYSTEMS FOR OPTIMIZING DOWNLINK TRAFFIC IN LOW POWER WIDE AREA NETWORKSBACKGROUND
[0001] Low power wide area networks (LPWAN) employ end devices, gateways, and servers in order to collect data. This collection of data is provided via uplink messages from the end devices that are sent to the gateways that then pass this information on to the server or servers. In this fashion, LPWANs can monitor utility consumption, track assets, and provide for contact tracing among other solutions.
[0002] In certain solutions, LPWANs also employ downlink messaging or simply downlinks where data is transmitted from the server, through the gateway to an end device. Such messages may be used to control end devices, for example, when the end device is a smart meter, downlink may be used to tell the meter to disconnect in the case of demand side management or non-payment.
[0003] Within LPWANs, including LoRaWAN networks where end devices are paired with a network and not exclusively tied to a single gateway, end devices will broadcast uplink messages that are received by any number of gateways for forwarding to a server that will then de-duplicate any multiply received uplink message. In a similar fashion, downlink messages may be transmitted via a variety of channels within an LPWAN.
[0004] However, delivery of downlink messages is often limited. Either by resources available to coordinate the downlink, such as gateways, which may require repeated broadcast in order to deliver the messages, or through limited bandwidth. Such as when LPWANs operate in simplex or half-duplex communication. Additionally, there may be a variety of end devices on the LPWAN to which an operator would like to transmit a downlink message.SUMMARY OF THE INVENTION
[0005] The invention is defined by the features of the independent claims. Some specific embodiments are defined in the dependent claims.
[0006] According to a first aspect of the present invention, there is provided a server for a low power wide area network, LPWAN, the server comprising at least one processing core and at least one memory including computer program code, the at least one memory and the computer program code being configured to, with the at least one processing core, cause the server at least to: retrieve a list of downlink transmission requests for the LPWAN; derive a list of downlink transmission opportunities comprising at least the following parameters for each downlink transmission request of the list of downlink transmission requests: a unique downlink transmission request identifier, a downlink path, a transmission start time, a transmission end time and a priority value; retrieve an uplink messages priority value forecast for the LPWAN; generate a potentially displaced amount of uplink priority value for each downlink transmission opportunity of the list of downlink transmission opportunities based on the uplink messages priority value forecast for the LPWAN, and determine a transmission schedule for the downlink transmission requests by comparing the unique downlink transmission request identifier, the downlink path, the transmission start time, the transmission end time, the priority value and the potentially displaced amount of uplink priority value forecast of each downlink transmission opportunity.
[0007] According to a second aspect of the present invention, there is provided a method for scheduling downlink transmissions in an LPWAN, the method comprising the steps of: retrieving a list of downlink transmission requests for the LPWAN; deriving a list of downlink transmission opportunities comprising at least the following parameters for each downlink transmission request of the list of downlink transmission requests: a unique downlink transmission request identifier, a downlink path, a transmission start time, a transmission end time and a priority value; retrieving an uplink messages priority value forecast for the LPWAN; generating a potentially displaced amount of uplink priority value for each downlink transmission opportunity of the list of downlink transmission opportunities based on the uplink messages priority value forecast for the LPWAN, and determining a transmission schedule for the downlink transmission requests by comparingthe unique downlink transmission request identifier, the downlink path, the transmission start time, the transmission end time, the priority value and the potentially displaced amount of uplink priority value forecast of each downlink transmission opportunity.
[0008] According to a third aspect of the present invention, there is provided a non- transitory computer readable medium having stored thereon a set of computer readable instructions that, when executed by at least one processor, cause an apparatus to at least perform a method in accordance with the first aspect and / or the second aspect.BRIEF DESCRIPTION OF THE DRAWINGS
[0009] FIGURES 1A, IB and 1C illustrate device, gateway and server communications in accordance with at least some embodiments of the present invention;
[0010] FIGURE 2 illustrates an example apparatus capable of supporting at least some embodiments of the present invention, andEMBODIMENTS
[0011] LPWANs, such as LoRaWANs, implementing embodiments of the present invention, comprise a number of end devices which transmit and receive information in the form of messages to and from gateways. The gateways themselves being in communication with servers. Such LPWANs may comprise a massive number of end devices which transmit and receive to and from a large number of gateways which then implement a backhaul network to connect to a server or servers. All of these transmissions impose limits on communications of the LPWAN. For example, only one downlink message may be transmitted over a given bandwidth at a time. While the downlink message may be transmitted by a number of gateways, simultaneous transmission of different messages over the same frequency would be impractical if not impossible.
[0012] Similarly, there may be only a limited number of gateways which could feasibly be in contact with a set of end devices and as such only a limited number of possible downlink message transmitters. At the same time, the gateways themselves may be computationally limited or lean. Therefore, LPWANs implementing embodiments ofthe present invention provide for prioritization and optimization of downlink message transmission such that the limited downlink paths are best utilized.
[0013] Messages themselves may have different priorities or priority values. For example, downlink messages may comprise updated configuration files for various devices of the LPWAN. Without prioritization, updated configuration files for smart meters which will allow for greater control during an impending power shortage could be delayed in order to reconfigure a group of distributed weather stations in order to report temperature in Celsius. While both updates are deemed necessary, only the smart metering update will have an immediate impact and thus need prioritization. Or even more stark, downlink messages which control smart metering to cycle certain loads off during a power shortage may not be received and thus a brownout may become a blackout.
[0014] Embodiments of the present invention address an issue within certain LPWANs, such as LoRaWANs wherein both downlink and uplink communications channels have a limited capacity. Similarly, the problem of communications interfering with each other may be addressed. For example the interference mentioned above wherein two downlink messages cannot be transmitted over the same frequency at the same time, thus limiting regional downlink transmission capacity. Other interference may be experienced in LPWANs implementing half-duplex communication protocols which only allow for downlink or uplink communication at any given time. In such half-duplex systems, the downlink and uplink communications could be said to interfere with each other.
[0015] Embodiments of the present invention provide for a server for a low power wide area network, LPWAN, the server comprising at least one processing core and at least one memory including computer program code, the at least one memory and the computer program code being configured to, with the at least one processing core, cause the server at least to: retrieve a list of downlink transmission requests for the LPWAN; derive a list of downlink transmission opportunities comprising at least the following parameters for each downlink transmission request of the list of downlink transmission requests: a unique downlink transmission request identifier, a downlink path, a transmission start time, a transmission end time and a priority value; retrieve an uplink messages priority value forecast for the LPWAN; generate a potentially displaced amount of uplink priority value for each downlink transmission opportunity of the list of downlink transmissionopportunities based on the uplink messages priority value forecast for the LPWAN, and determine a transmission schedule for the downlink transmission requests by comparing the unique downlink transmission request identifier, the downlink path, the transmission start time, the transmission end time, the priority value and the potentially displaced amount of uplink priority value forecast of each downlink transmission opportunity. Within some embodiments the forecast comprises priority values over a given start and end time. In certain embodiments the downlink message requests comprise the message to be transmitted. When the message to be transmitted is included, the message may be used to determine transmission start and end times.
[0016] Transmission schedules according to certain embodiments comprise instructions configured to cause transmission of at least one of the downlink opportunities of the list of downlink opportunities, the instructions comprising a downlink path, a transmission start time and a transmission end time. Some transmission schedules include a transmission start time for each scheduled downlink message. Certain transmission schedules are determined by considering which of a plurality of gateways of the LPWAN will need to be placed in transmit mode to transmit the downlink messages.
[0017] Certain embodiments of the present invention employ a consideration for the probability of message receipt. For example, the determination of the transmission schedule may consider the probability of message reception. Such probability of transmission may be used as a multiplier to any priority value associated with a message to arrive at a probable priority which is then used to determine the transmission schedule. For example, if two messages having a priority value of 10 and 20 respectively are both requesting the same transmission slot and the first message has a probability of delivery of 0.9 and the second 0.1, the resulting probable priority values would be 9 and 2 respectively. Certain embodiments would prioritize transmission of the first message as its probably priority value is higher. At least some embodiments employ a propagation model of the LPWAN in order to determine probability of message reception. In some embodiments the transmission schedule includes instructions on which gateways of the LPWAN should transmit the scheduled downlink messages.
[0018] FIGURES 1A - 1C are included here to illustrated both the architecture of LPWANs according to certain embodiments and probability as employed here. FIGURE 1A shows interactions of a device, or end device, and a gateway of a LPWAN. WithinFIGURE 1A, both uplink (solid line) and downlink (dotted line) probability of success (p) are equal, resulting in a symmetrical link budget or channel.
[0019] FIGURE IB shows interactions between a device, multiple gateways and a server. As compared to FIGURE 1A, FIGURE IB shows an asymmetric channel. While the server can receive an uplink forwarded through any of the gateways, downlinks are only forwarded through one gateway and thus have a lower probability of receipt.
[0020] FIGURE 1C shows the same system of FIGURE IB, only now the downlink message is being forwarded through two different gateways in accordance with embodiments of the present invention. Now, while the channel may still be asymmetric, downlink reception probability is improved.
[0021] According to some embodiments, the downlink path comprises at least one gateway identified as necessary to transmit the downlink message.
[0022] In some embodiments the uplink messages priority value forecast is generated in at least the following steps: obtaining uplink messages forecast for the LPWAN, assigning a priority value to uplink messages of the obtained uplink messages forecast for the LPWAN, and summing the priority values of the uplink messages forecasted over time. In certain embodiments, the uplink priority value forecast includes indication of gateways of the LPWAN which could receive the uplink messages. For example, the uplink priority value forecast may comprise forecasts for individual gateways of the LPWAN.
[0023] In certain embodiments instructions are transmitted to gateways of the LPWAN, the instructions being configured to cause the gateways to transmit downlinks based on the determined transmission schedule.
[0024] In some embodiments the potentially displaced amount of uplink priority value is determined based on an amount of uplink traffic which would not be received if the downlink message request were transmitted. That is, the amount of uplink traffic which is projected or forecast as not being received. Such projections or forecasts may be calculated based on the time in which gateways of the LPWAN would be unable to receive messages, for example because the gateways are in transmit mode within a half-duplex scheme. At least some transmission schedules are determined by maximizing the total transmitted priority value. This may include uplink and downlink priority value. In someembodiments a downlink message is added to the transmission schedule if the priority value of the downlink message is greater than the potentially displaced amount of uplink priority value. The transmission schedule may be determined by comparing the downlink message requests in descending order of priority value.
[0025] Priority value may be determined in a variety of fashions. For example, as discussed above, priority value may be associated with an impact to infrastructure. Where transmissions are critical, or outage related, they may be given a high priority value versus transmissions related to user experience improvements which may be given a low priority value. Priority value may also be determined by users of the LPWAN in a bidding process. For example, an operator of tracking devices on the LPWAN may want to change a frequency of location updates by sending a downlink transmission to all of their devices. This transmission is not time sensitive as the change in frequency will have limited impact beyond saving a small amount of overall network charges. Such an operator may set their bid for a downlink opportunity to be up to the savings the change in frequency would provide as any greater fee for transmission would not result in savings. In contrast, an operator of smart meters may need to limit their energy usage due to a fixed supply contract wherein any overage will result in steep fines. This operator would rightly set a higher bid for their downlink transmissions halting energy usage at the smart meters as any cost to transmit less than the fine would result in savings. In at least some cases information is transmitted regarding downlink messages requests which were not included in the transmission schedule.
[0026] FIGURE 2 illustrates an example apparatus capable of supporting at least some embodiments of the present invention. Illustrated is device 300, which may comprise, for example: any of the participants in a LPWAN systems discussed herein, such as: an end device, gateway or server. Comprised in device 300 is processor 310, which may comprise, for example, a single- or multi-core processor wherein a single-core processor comprises one processing core and a multi-core processor comprises more than one processing core. Processor 310 may comprise a Qualcomm Snapdragon 800 processor, for example. Processor 310 may comprise more than one processor. A processing core may comprise, for example, a Cortex- A8 processing core manufactured by Intel Corporation or a Brisbane processing core produced by Advanced Micro Devices Corporation. Processor 310 may comprise at least one application-specific integrated circuit, ASIC. Processor 310 may comprise at least one field-programmable gate array, FPGA. The aforementionedprocessor types are non-limiting examples, alternatively an Intel i7 processor, or another suitable type of processor, may be employed.
[0027] Device 300 may comprise memory 320. Memory 320 may comprise randomaccess memory and / or permanent memory. Memory 320 may comprise at least one RAM chip. Memory 320 may comprise magnetic, optical and / or holographic memory. Memory 320 may be at least in part accessible to processor 310. Memory 320 may be means for storing information. Memory 320 may comprise computer instructions that processor 310 is configured to execute. When computer instructions configured to cause processor 310 to perform certain actions are stored in memory 320, and device 300 overall is configured to run under the direction of processor 310 using computer instructions from memory 320, processor 310 and / or its at least one processing core may be considered to be configured to perform said certain actions.
[0028] Device 300 may comprise a transmitter 330. Device 300 may comprise a receiver 340. Transmitter 330 and receiver 340 may be configured to transmit and receive, respectively, information in accordance with systems, for example, transmitter 330 may transmit information to a monitor for display to a user, and / or receiver 340 may receive input information concerning a location and / or orientation of a further device.
[0029] Device 300 may comprise a near-field communication, NFC, transceiver 350. NFC transceiver 350 may support at least one NFC technology, such as NFC, Bluetooth, Wibree or similar technologies.
[0030] Device 300 may comprise user interface, UI, 360. UI 360 may comprise at least one of a display, a keyboard and a touchscreen. A user may be able to operate device 300 via UI 360, for example to start or terminate execution of programs.
[0031] Processor 310 may be furnished with a transmitter arranged to output information from processor 310, via electric leads internal to device 300, to other devices comprised in device 300. Such a transmitter may comprise a serial bus transmitter arranged to, for example, output information via at least one electric lead to memory 320 for storage therein. Alternatively, to a serial bus, the transmitter may comprise a parallel bus transmitter. Likewise, processor 310 may comprise a receiver arranged to receive information in processor 310, via electrical leads internal to device 300, from other devices comprised in device 300. Such a receiver may comprise a serial bus receiver arranged to;for example, receive information via at least one electric lead from receiver 340 for processing in processor 310. Alternatively, to a serial bus, the receiver may comprise a parallel bus receiver.
[0032] Device 300 may comprise further devices not illustrated in FIGURE 2. For example, where device 300 comprises a computer device, it may comprise at least one clock or auxiliary power unit, APU to provide battery power in case of mains power failure.
[0033] Processor 310, memory 320, transmitter 330, receiver 340, NFC transceiver 350 and / or UI 360 may be interconnected by electric leads internal to device 300 in a multitude of different ways. For example, each of the aforementioned devices may be separately connected to a master bus internal to device 300, to allow the devices to exchange information. However, as the skilled person will appreciate, this is only one example and depending on the embodiment, various ways of interconnecting at least two of the aforementioned devices may be selected without departing from the scope of the present invention.
[0034] It is to be understood that the embodiments of the invention disclosed are not limited to the particular structures, process steps, or materials disclosed herein, but are extended to equivalents thereof as would be recognized by those ordinarily skilled in the relevant arts. It should also be understood that terminology employed herein is used for the purpose of describing particular embodiments only and is not intended to be limiting.
[0035] Reference throughout this specification to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, appearances of the phrases “in one embodiment” or “in an embodiment” in various places throughout this specification are not necessarily all referring to the same embodiment.
[0036] As used herein, a plurality of items, structural elements, compositional elements, and / or materials may be presented in a common list for convenience. However, these lists should be construed as though each member of the list is individually identified as a separate and unique member. Thus, no individual member of such list should be construed as a de facto equivalent of any other member of the same list solely based ontheir presentation in a common group without indications to the contrary. In addition, various embodiments and example of the present invention may be referred to herein along with alternatives for the various components thereof. It is understood that such embodiments, examples, and alternatives are not to be construed as de facto equivalents of one another, but are to be considered as separate and autonomous representations of the present invention.
[0037] Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided, such as examples of lengths, widths, shapes, etc., to provide a thorough understanding of embodiments of the invention. One skilled in the relevant art will recognize, however, that the invention can be practiced without one or more of the specific details, or with other methods, components, materials, etc. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the invention.
[0038] While the forgoing examples are illustrative of the principles of the present invention in one or more particular applications, it will be apparent to those of ordinary skill in the art that numerous modifications in form, usage and details of implementation can be made without the exercise of inventive faculty, and without departing from the principles and concepts of the invention. Accordingly, it is not intended that the invention be limited, except as by the claims set forth below.
[0039] The verbs “to comprise” and “to include” are used in this document as open limitations that neither exclude nor require the existence of also un-recited features. The features recited in depending claims are mutually freely combinable unless otherwise explicitly stated. Furthermore, it is to be understood that the use of "a" or "an", i.e. a singular form, throughout this document does not exclude a plurality.
Claims
CLAIMS:
1. A server for a low power wide area network, LPWAN, the server comprising at least one processing core and at least one memory including computer program code, the at least one memory and the computer program code being configured to, with the at least one processing core, cause the server at least to:- retrieve a list of downlink transmission requests for the LPWAN;- derive a list of downlink transmission opportunities comprising at least the following parameters for each downlink transmission request of the list of downlink transmission requests: a unique downlink transmission request identifier, a downlink path, a transmission start time, a transmission end time and a priority value;- retrieve an uplink messages priority value forecast for the LPWAN;- generate a potentially displaced amount of uplink priority value for each downlink transmission opportunity of the list of downlink transmission opportunities based on the uplink messages priority value forecast for the LPWAN, and- determine a transmission schedule for the downlink transmission requests by comparing the unique downlink transmission request identifier, the downlink path, the transmission start time, the transmission end time, the priority value and the potentially displaced amount of uplink priority value forecast of each downlink transmission opportunity.
2. The server of claim 1, wherein the transmission schedule comprises instructions configured to cause transmission of at least one of the downlink opportunities of the list of downlink opportunities, the instructions comprising a downlink path, a transmission start time and a transmission end time.
3. The server of claim 1 or 2, wherein the downlink path comprises at least one gateway identified as necessary to transmit the downlink message.
4. The server of any one of the preceding claims, wherein the uplink messages priority value forecast is generated in at least the following steps:- obtaining uplink messages forecast for the LPWAN,- assigning a priority value to uplink messages of the obtained uplink messages forecast for the LPWAN, and- summing the priority values of the uplink messages forecasted over time.
5. The server of any one of the preceding claims, wherein the server is further configured to transmit instructions to gateways of the LPWAN, the instructions being configured to cause the gateways to transmit downlinks based on the determined transmission schedule.
6. The server of any one of claims 2 - 5, wherein the forecast comprises priority values over a given start and end time.
7. The server of any preceding claim, wherein the downlink message requests comprise the message to be transmitted.
8. The server of claim 7, wherein the transmission start time and transmission end time is determined based at least in part on the size of the downlink message.
9. The server of any one of claims 2 - 8, wherein the potentially displaced amount of uplink priority value is determined based on an amount of uplink traffic which would not be received if the downlink message request were transmitted.
10. The server of any one of the preceding claims, wherein the transmission schedule is determined by maximizing the total transmitted priority value.
11. The server of any one of the preceding claims, wherein a downlink message is added to the transmission schedule if the priority value of the downlink message is greater than the potentially displaced amount of uplink priority value.
12. The server of any one of the preceding claims, wherein the transmission schedule is determined by comparing the downlink message requests in descending order of priority value.
13. The server of any one of the preceding claims, wherein the server is further configured to transmit information regarding downlink messages requests which were not included in the transmission schedule.
14. The server of any one of the preceding claims wherein determination of the transmission schedule further considers the probability of message reception.
15. The server of claim 14, wherein the probability of message reception is determined based on a propagation model of the LPWAN.
16. The server of any one of the preceding claims, wherein the transmission schedule includes instructions on which gateways of the LPWAN should transmit the scheduled downlink messages.
17. The server of any one of the preceding claims, wherein the transmission schedule is determined by considering which of a plurality of gateways of the LPWAN will need to be placed in transmit mode to transmit the downlink messages.
18. The server of any one of the preceding claims, wherein the uplink priority value forecast comprises forecasts for individual gateways of the LPWAN.
19. The server of any one of the preceding claims, wherein the LPWAN is a LoRaWAN.
20. A method for scheduling downlink transmissions in an LPWAN, the method comprising the steps of:- retrieving a list of downlink transmission requests for the LPWAN;- deriving a list of downlink transmission opportunities comprising at least the following parameters for each downlink transmission request of the list of downlink transmission requests: a unique downlink transmission request identifier, a downlink path, a transmission start time, a transmission end time and a priority value;- retrieving an uplink messages priority value forecast for the LPWAN;- generating a potentially displaced amount of uplink priority value for each downlink transmission opportunity of the list of downlink transmission opportunities based on the uplink messages priority value forecast for the LPWAN, and- determining a transmission schedule for the downlink transmission requests by comparing the unique downlink transmission request identifier, the downlink path, the transmission start time, the transmission end time, the priority value and the potentially displaced amount of uplink priority value forecast of each downlink transmission opportunity.
21. The method of claim 20, wherein the transmission schedule comprises instructions configured to cause transmission of at least one of the downlink opportunities of the list of downlink opportunities, the instructions comprising a downlink path, a transmission start time and a transmission end time.
22. The method of any one of claim 20 or claim 21, wherein the downlink path comprises at least one gateway identified as necessary to transmit the downlink message.
23. The method of any one of claims 20 - 23, wherein the uplink messages priority value forecast is generated in at least the following steps:- obtaining uplink messages forecast for the LPWAN,- assigning a priority value to uplink messages of the obtained uplink messages forecast for the LPWAN, and- summing the priority values of the uplink messages forecasted over time.
24. The method of any one of claims 20 - 23, wherein the method further comprises the steps of transmitting instructions to gateways of the LPWAN, the instructions being configured to cause the gateways to transmit downlinks based on the determined transmission schedule.
25. The method of any one of claims 20 - 24, wherein the forecast comprises priority values over a given start and end time.
26. The method of any one of claims 20 - 25, wherein the downlink message requests comprise the message to be transmitted.
27. The method of claim 26, wherein the transmission start time and transmission end time is determined based at least in part on the size of the downlink message.
28. The method of any one of claims 20 - 27, wherein the potentially displaced amount of uplink priority value is determined based on an amount of uplink traffic which would not be received if the downlink message request were transmitted.
29. The method of any one of claims 20 - 28, wherein the transmission schedule is determined by maximizing the total transmitted priority value.
30. The method of any one of claims 20 - 29, wherein a downlink message is added to the transmission schedule if the priority value of the downlink message is greater than the potentially displaced amount of uplink priority value.
31. The method of any one of claims 20 - 30, wherein the transmission schedule is determined by comparing the downlink message requests in descending order of priority value.
32. The method of any one of claims 20 - 31, wherein the server is further configured to transmit information regarding downlink messages requests which were not included in the transmission schedule.
33. The method of any one of claims 20 - 32, wherein determination of the transmission schedule further considers the probability of message reception.
34. The method of claim 33, wherein the probability of message reception is determined based on a propagation model of the LPWAN.
35. The method of any one of claims 20 - 34, wherein the transmission schedule includes instructions on which gateways of the LPWAN should transmit the scheduled downlink messages.
36. The method of any one of claims 20 - 35, wherein the transmission schedule is determined by considering which of a plurality of gateways of the LPWAN will need to be placed in transmit mode to transmit the downlink messages.
37. The method of any one of claims 20 - 36, wherein the uplink priority value forecast comprises forecasts for individual gateways of the LPWAN.
38. The method of any one of claims 20 - 37, wherein the LPWAN is a LoRaWAN.
39. A non-transitory computer readable medium having stored thereon a set of computer readable instructions that, when executed by at least one processor, cause an apparatus to at least perform a method in accordance with at least one of claims 20 - 38.
40. A computer program configured to cause a method in accordance with at least one of claims 20 - 38 be performed.
Citation Information
Patent Citations
Wearable electronic device and system for tracking location and identifying changes in salient indicators of patient health
US20190209022A1
Method for transmitting power headroom report, user equipment, processing device, storage medium, and computer program
US20230092884A1
