Method and apparatus for communicating with an endpoint device

Abstract

An endpoint (EP) device can communicate with multiple gateways via wireless signals, such as wireless broadcast signals. The EP device is controlled under the direction of a control server, such as an application server, to communicate via a single gateway. The control server associates the EP device with a single target gateway and / or uses EP transmission power control training iterations to reduce the EP transmission power level until the EP device can only successfully transmit its wireless signals to the single gateway.

Description

Technical Field

[0001] The present invention relates to wireless communication systems, and more particularly, to methods and apparatus for reducing interference and / or increasing throughput in wireless communication systems (e.g., wireless communication systems using wireless broadcast signaling from endpoint devices and / or wireless communication systems supporting alternative wireless communication paths for endpoint devices). Background Technology

[0002] Internet of Things (IoT) and Low Power Wide Area (LPWA) devices lack device-to-gateway (GW) / edge node association, instead associating with a network server (NS). This is an obstacle to enabling technologies like 6lowpan on top of LPWA. The lack of device-to-gateway (GW) association also limits the ability to localize devices at low cost.

[0003] In various existing architectures, IoT and LPWA devices are not paired with gateways. Devices can, and sometimes do, communicate simultaneously with multiple gateways, for example, via broadcast signals intended to be received, recovered, and forwarded by any GW capable of recovering the broadcast signal. Therefore, application data from the same device is often sent to, for example, an application server via multiple wireless links and multiple paths in the network, which is redundant, inefficient, and often unnecessary. This redundant communication wastes air link and backhaul network resources, and when transmitted at power levels higher than necessary, it can interfere with transmissions from other devices.

[0004] Based on the above, new methods and apparatus are needed to support communication with devices such as application servers in a more efficient manner, especially with the transmission power used by each endpoint device. Summary of the Invention

[0005] Various features relate to methods and apparatus for power control of endpoint devices that communicate with an application server using wireless signals transmitted to one or more gateways connected to a control server. In many embodiments, the control server is an application server that supports one or more applications (e.g., meter reading, billing, or other applications), but also controls the transmission power levels of endpoint devices that transmit data to the server for use by applications supported by the server. Therefore, it should be recognized that in many cases, the server operates as both an application server and a control server. In embodiments where the application and control servers are a single entity, it can be referred to as either an application server or a control server because it serves both functions. While the control server supports power control operations, the additional application functionality is optional and not required to be supported in all embodiments.

[0006] The method and apparatus of this invention are well-suited for use in a variety of systems, including those that use low-power wide area networks (LPWANs) to transmit information. LPWANs can support remote signaling.

[0007] In various embodiments, the endpoint (EP) device, such as an IoT device, which may be, for example, a voltmeter, parking meter, sensor, or any wide range of devices, controls power by using training data transmission and power control signaling from a control server (e.g., an application server responsible for collecting and / or using data from IoT devices in some embodiments), and according to the invention, also controls the power of at least some IoT devices.

[0008] In various embodiments, IoT devices transmit wireless signals, such as broadcast signals. A gateway in the system receives the wireless signal, recovers the data from the signal, and transmits it to an application server. In some embodiments, the wireless gateway is connected to the application server via a wired or wireless network. In some embodiments, the application also acts as a control server, which can and sometimes does control the transmission power used by one or more EP devices. Because the wireless signal is broadcast by the EP device, if multiple gateways exist in the transmission coverage area of ​​the EP device, the signal can be received by multiple gateways.

[0009] The coverage area of ​​signals transmitted by EP devices depends on the transmission power used to transmit them. When gateways receive data (e.g., messages) from EP devices, they are transmitted through the network used to couple the gateways to the application server. Since the same data may be received by multiple gateways, the same data received by different gateways can, and sometimes can, be transmitted to the application server within the communication network. In some cases, a network server in the communication network aggregates data, such as messages from different gateways, and transmits the data (e.g., messages) along with information identifying the gateway that received the data being forwarded to the application and / or control server. In this case, due to aggregation, the application and / or control server can receive a single copy of the data received by multiple gateways but containing information about which gateways received the radio signals that transmitted the data from the EP device to the corresponding EP device.

[0010] According to various features in some embodiments, the server, acting as a control server, signals the EP device to operate in the training mode. The training mode operation of the EP device involves power control transmission, for example, wirelessly broadcasting a set of training data. The initial training data is transmitted at maximum power and, in at least some embodiments, using the maximum transmission data rate supported by the EP device being trained. The gateway device receiving the training data transmission recovers the data and forwards it to the control server along with information identifying the gateway receiving the transmission being forwarded. Because the initial transmission of training data is at maximum transmission power, it is likely to be received by multiple gateways. Therefore, multiple gateways can and often will receive the initial training data message and forward it to the control server.

[0011] Optionally, network devices in the communication path between the receiving gateway and the control (e.g., application) server may, and sometimes do, aggregate messages, for example, forwarding training data and gateway identifiers, such that a single message transmits training data and gateway identifiers received by multiple gateways. In other embodiments, the control server receives separate messages from different gateways that have successfully received training data transmitted from the endpoint devices.

[0012] In various embodiments where an EP device is associated with a specific gateway, a control device operates relative to the EP device in a so-called associated operation mode, wherein the EP device is associated with a specific gateway used in the communication path between the EP device and an application server, which can also be a control server as described above. In associated mode, the EP device may, for example, be associated with a gateway specified by the EP device in an association request, or with a gateway selected by the control server. In associated mode, as part of transmission power control training, the EP transmission power is reduced in a series of operations to a level that allows the EP device to communicate with the gateway it is associated with, but does not require the use of full transmission power if the gateway associated with the EP device can be reached, and still uses less than full transmission power to support the maximum data transmission rate.

[0013] In non-associative mode, EP devices can and are sometimes controlled to communicate with the application server using a single gateway, where the gateway can and is sometimes a gateway capable of supporting the maximum transmission power level at a lower EP transmission power level than other gateways in the system. In many such embodiments, the gateway used will be the one with the optimal wireless communication path to the EP device.

[0014] In both non-associative and associated modes, the gateway used to communicate with the application server can and is sometimes referred to as the target gateway. Power control training considers the target gateway when reducing transmission power to levels that will be used for actual data transmission, such as the transmission of instrument readings, sensor readings, and / or parking meter information related to parked cars.

[0015] According to some embodiments, an exemplary communication method includes: receiving training data wirelessly transmitted by a first endpoint device and received by one or more gateways coupled to the control server at a control server; determining whether the training data has been successfully received by at least one gateway other than a target gateway; when it is determined that the training data has been successfully received by at least one gateway other than the target gateway, sending a command to the first endpoint device to reduce the transmission power level; and when it is determined that the training data has not been successfully received by at least one gateway other than the target gateway, sending a command to the first endpoint device indicating that training has ended.

[0016] The method and apparatus according to the invention are well-suited for long-range low-power wireless IoT communication technologies, such as Sigfox and LoRaWAN. Furthermore, the method and apparatus according to the invention are also suitable for use in other access technologies, such as narrowband IoT (NB-IoT), LTE-M, and future C-LPWAN.

[0017] While various features discussed in the aspects have been used in some embodiments, it should be recognized that not all features are necessary or required for all embodiments, and reference to a feature in the aspects should in no way be construed as implying that the feature is necessary or critical for all embodiments. Many additional features and embodiments are discussed in the following detailed description. Many additional benefits will be discussed in the following detailed description. Attached Figure Description

[0018] Figure 1 This is a diagram of an exemplary communication system including multiple Internet of Things (IoT) devices that transmit IoT wireless broadcast uplink signals that can be received by multiple IoT gateways.

[0019] Figure 2 This is a diagram of an exemplary communication system comprising multiple endpoint (EP) Internet of Things (IoT) devices according to an exemplary embodiment, these IoT devices transmitting IoT wireless broadcast uplink signals, the exemplary system supporting transmit power control (TPC) of the EP IoT devices and / or association of the EP IoT devices with a selected gateway to reduce interference and / or increase throughput.

[0020] Figure 3A This is a first part of a signaling diagram according to an exemplary embodiment, used to illustrate an exemplary association between an EP IoT device and a selected gateway, and an exemplary transmission power control (TPC) for the EP IoT device in the associated operating mode.

[0021] Figure 3B This is the second part of a signaling diagram according to an exemplary embodiment, used to illustrate an exemplary association between an EP IoT device and a selected gateway, and an exemplary transmission power control (TPC) for the EP IoT device in the associated operating mode.

[0022] Figure 3C This is the third part of the signaling diagram according to an exemplary embodiment, used to illustrate an exemplary association between an EP IoT device and a selected gateway, and an exemplary transmission power control (TPC) for the EP IoT device in the associated operating mode.

[0023] Figure 3DThis is the fourth part of the signaling diagram according to an exemplary embodiment, used to illustrate an exemplary association between an EP IoT device and a selected gateway, and an exemplary transmission power control (TPC) for the EP IoT device in the associated operating mode.

[0024] Figure 3E This is the fifth part of the signaling diagram according to an exemplary embodiment, used to illustrate an exemplary association between an EP IoT device and a selected gateway, and an exemplary transmission power control (TPC) for the EP IoT device in the associated operating mode.

[0025] Figure 3 includes Figure 3A , Figure 3B , Figure 3C , Figure 3D and Figure 3E The combination of .

[0026] Figure 4A This is a first part of a signaling diagram according to an exemplary embodiment, used to illustrate exemplary transmission power control (TPC) for an EP IoT device in a non-associative operating mode.

[0027] Figure 4B This is the second part of a signaling diagram according to an exemplary embodiment, used to illustrate exemplary transmission power control (TPC) for an EP IoT device in a non-associative operating mode.

[0028] Figure 4 includes Figure 4A and Figure 4B The combination of .

[0029] Figure 5 This diagram illustrates an exemplary endpoint (EP) Internet of Things (IoT) device that initially communicates successfully via two communication paths, each including a different gateway, according to an exemplary embodiment. Then, after transmission power control (TPC) training that causes a reduction in EP IoT transmission power, it successfully communicates only via one communication path corresponding to a single gateway.

[0030] Figure 6A This is the first part of a flowchart of an exemplary method for operating a control server (e.g., an application server) according to an exemplary embodiment.

[0031] Figure 6B This is the second part of a flowchart of an exemplary method for operating a control server (e.g., an application server) according to an exemplary embodiment.

[0032] Figure 6C This is the third part of a flowchart of an exemplary method for operating a control server (e.g., an application server) according to an exemplary embodiment.

[0033] Figure 6DThis is the fourth part of a flowchart of an exemplary method for operating a control server (e.g., an application server) according to an exemplary embodiment.

[0034] Figure 6 includes Figure 6A , Figure 6B , Figure 6C and Figure 6D The combination of .

[0035] Figure 7 This is a diagram of an exemplary control server (e.g., an application server) according to an exemplary embodiment.

[0036] Figure 8 This is a diagram of an exemplary endpoint (EP) device (e.g., an EP IoT device) according to an exemplary embodiment.

[0037] Figure 9 This is a diagram of an exemplary network server according to an exemplary embodiment.

[0038] Figure 10 This is a diagram of an exemplary gateway (e.g., an IoT gateway) according to an exemplary embodiment.

[0039] Figure 11A This is a first part of a diagram of an exemplary component of a part according to an exemplary embodiment, which may be included in an exemplary control server (e.g., an application server).

[0040] Figure 11B This is the second part of a diagram of an exemplary component of a part according to an exemplary embodiment, which may be included in an exemplary control server (e.g., an application server).

[0041] Figure 11C This is a third part of a diagram of an exemplary component of a part according to an exemplary embodiment, which may be included in an exemplary control server (e.g., an application server).

[0042] Figure 11D This is the fourth part of a diagram of an exemplary component of a part according to an exemplary embodiment, which may be included in an exemplary control server (e.g., an application server).

[0043] Figure 11 include Figure 11A , Figure 11B , Figure 11C and Figure 11D The combination of . Detailed Implementation

[0044] Figure 1This is a diagram of an exemplary communication system 100, including an Internet of Things (IoT) gateway (IoT GW 1 102, IoT GW M 104), a core network server 106, an Component Management System / IoT Fixed Wireless Access Client Site Equipment (EMS / IoTFWA CPE) database 108, a service provider domain agent node 110, the Internet 112, a control network 114, and multiple IoT devices (IoT device 1 120, e.g., a temperature sensor device; IoT device 2 122, e.g., a fire sensor device; IoT device 3 124, e.g., a security sensor device; IoT device 4 126, e.g., a water meter sensor device; IoT device 5 128, e.g., a power grid sensor device; IoT device 6 130, e.g., a vehicle sensor device; IoT device 7, e.g., an electricity meter sensor device; ...; IoT device N 134, e.g., a gas meter sensor device). IoT GW1 102 and IoT GW M 104 are coupled to the core network server 106 via one or more backhaul network links 158. Core network server 106 is coupled to service provider domain agent node 110 via link 160. Core network server 106 is coupled to EMS / IoT FWA CPE database 108 via link 162. Service provider domain agent node 110 is coupled to EMS / IoT FWA CPE database 108 via link 163. Service provider domain agent node 110 and EMS / IoT FWA CPE database are coupled to the Internet 112 via communication links 166 and 164, respectively. Control network 114 is coupled to the Internet 112 via communication link 168. Control network 114 includes network server 116 and application server 118 coupled together via communication link 170.

[0045] Each of the IoT devices (120, 122, 124, 126, 126, 130, 132, ... 134) transmits a broadcast uplink IoT wireless signal at, for example, the maximum transmission power level. Depending on channel conditions, the broadcast IoT signal can be received by one or more IoT GW devices. The uplink signal broadcast by the IoT device can and sometimes can be detected by all IoT GWs (102, 104), and the information conveyed in the received signal is forwarded by each of the GWs (102, 104), for example, to application server 118. This results in redundant data being transmitted to the application server.

[0046] exist Figure 1 In Figure 100, IoT device 1 120 has a wireless IoT communication link with IoT GW 1 102, as indicated by dashed arrow 136. Figure 1In Figure 100, IoT device 2 122 has a wireless IoT communication link with IoT GW 1 102, as indicated by dashed arrow 138, and a wireless IoT communication link with IoT GW M 104, as indicated by dashed arrow 140. Figure 1 In Figure 100, IoT device 3 124 has a wireless IoT communication link with IoT GW 1 102, as indicated by dashed arrow 143, and a wireless IoT communication link with IoT GW M 104, as indicated by dashed arrow 144. Figure 1 In Figure 100, IoT device 4 126 has a wireless IoT communication link with IoT GW 1 102, as indicated by dashed arrow 146. Figure 1 In Figure 100, IoT device 5128 has a wireless IoT communication link with IoT GW 1 102, as indicated by dashed arrow 148. Figure 1 In Figure 100, IoT device 6 130 has a wireless IoT communication link with IoT GW M 104, as indicated by dashed arrow 150. Figure 1 In Figure 100, IoT device 7 132 has a wireless IoT communication link with IoT GW 1 102, as indicated by dashed arrow 152, and a wireless IoT communication link with IoT GW M 104, as indicated by dashed arrow 154. Figure 1 In Figure 100, IoT device N 134 has a wireless IoT communication link with IoT GW M 104, as indicated by dashed arrow 156.

[0047] Figure 2 This is a diagram of an exemplary communication system 200 supporting IoT communication (e.g., remote IoT communication) implemented according to an exemplary embodiment. The exemplary communication system 200 supports Transmission Power Control (TPC) for endpoint (EP) IoT devices, for example, on a single device basis, under the guidance of a control server (e.g., application server 219 of control network 263). The exemplary communication system 200 supports the association, e.g., pairing, of EP IoT devices with a single selected IoT GW, and the establishment of an end-to-end (E2E) communication path between the EP IoT device and the control server (e.g., application server 218), the E2E communication path including an IoT wireless link between the EP IoT device and the selected IoT GW. In various embodiments, the transmission power level of the EP IoT device is determined, e.g., via TPC training iterations, and set to a determined level such that broadcast application data transmissions (e.g., sensor reports) from the EP IoT device are successfully transmitted to an IoT gateway.

[0048] An exemplary communication system 200 includes an Internet of Things (IoT) gateway (IoT GW 1 202, IoT GW M 204), a core network server 206, an Component Management System / IoT Fixed Wireless Access Client Site Equipment (EMS / IoT FWA CPE) database 208, a service provider domain agent node 210, the Internet 212, a control network 214, and multiple endpoint (EP) IoT devices (IoT device 1 220, e.g., a temperature sensor device; IoT device 2 222, e.g., a fire sensor device; IoT device 3 224, e.g., a security sensor device; IoT device 4 226, e.g., a water meter sensor device; IoT device 5 228, e.g., a power grid sensor device; IoT device 6 230, e.g., a vehicle sensor device; IoT device 7 232, e.g., an electricity meter sensor device; ...; IoT device N 234, e.g., a gas meter sensor device). IoT GW 1 202 and IoT GW M 204 are coupled to the core network server 206 via one or more backhaul network links 258. Core network server 206 is coupled to service provider domain agent node 210 via link 260. Core network server 206 is coupled to EMS / IoT FWA CPE database 208 via link 262. Service provider domain agent node 210 is coupled to EMS / IoT FWA CPE database 208 via link 263. Service provider domain agent node 210 and EMS / IoT FWA CPE database 208 are coupled to the Internet 212 via communication links 266 and 264, respectively. Control network 214 is coupled to the Internet 212 via communication link 268. Control network 214 includes network server 216 and application server 218 coupled together via communication link 270. Network server 216 includes transmission power control component 280 and associated component 284. Application server 216 includes transmission power control component 282 and associated component 286.

[0049] Each of the EP IoT devices (220, 222, 224, 226, 226, 228, 230, 232, ... 234) transmits a broadcast uplink IoT wireless signal. According to the features of various embodiments, Figure 2 The EP IoT device shown has undergone Transport Power Control (TPC) training and / or association operations under the guidance of a control server (e.g., application server 218). Figure 2In the example, TPC results in each of the EP IoT devices (220, 222, 224, 226, 226, 228, 230, 232, ... 234) having a wireless IoT communication link with a single IoT gateway device. Due to the TPC operation, at least some of the EP IoT devices (220, 222, 224, 226, 226, 228, 230, 232, ... 234) have been controlled to operate at a transmission power level below the maximum permissible transmission power level, thereby eliminating some redundant connections with the IoT GW in the system, reducing interference in the wireless spectrum used for communication, and reducing backhaul signaling between the IoT GW and the application server.

[0050] EP IoT device 1 120 has a wireless IoT communication link with IoT GW 1 102, as indicated by dashed arrow 236. EP IoT device 2 222 has a wireless IoT communication link with IoT GW M 104, as indicated by dashed arrow 240. EP IoT device 3 224 has a wireless IoT communication link with IoT GW M 104, as indicated by dashed arrow 244. EP IoT device 4 226 has a wireless IoT communication link with IoT GW 1 102, as indicated by dashed arrow 246. EP IoT device 5 228 has a wireless IoT communication link with IoT GW 1 202, as indicated by dashed arrow 248. EP IoT device 6 230 has a wireless IoT communication link with IoT GW M 204, as indicated by dashed arrow 250. EP IoT device 7 232 has a wireless IoT communication link with IoT GW M 204, as indicated by dashed arrow 254. EP IoT device N234 has a wireless IoT communication link with IoT GW M 204, as indicated by dashed arrow 256.

[0051] Figure 3, including Figure 3A , Figure 3B , Figure 3D and Figure 3E The combination of these components is an exemplary signaling diagram 300 according to an exemplary embodiment, including portion A 301, portion B 303, portion C 305, portion D 307, and portion E 309. Exemplary signaling diagram 300 includes exemplary endpoint IoT device 302, GW 1 202, GW 2 204, network server (NS) 216, and application server (AS) 218. For example, exemplary EP IoT device 302 is... Figure 2Any IoT device (220, 222, 224, 226, 228, 230, 232, ..., 234) in System 200. Exemplary signaling diagram 300 illustrates: An exemplary endpoint (EP) IoT device associates with a single selected gateway device in response to an association request. The exemplary EP IoT device, under the guidance of a control server, performs a Transmission Power Control (TPC) training operation to determine the transmission power level for application data transmission in association mode. This determined power is below the maximum permissible TX power. The transmission of EP IoT application data at the determined TX power level is also illustrated. The EP IoT application data is received by a single IoT GW, which is the selected GW associated (paired) with the EP IoT device.

[0052] In step 304, EP IoT device 302 generates and transmits a wireless IoT broadcast signal 306 to convey a join request. In step 308, GW 1 202 receives signal 306. In step 310, GW 1 202 generates and sends message 312, thereby transmitting the join request to network server (NS) 216. In step 312, network server 216 receives message 312 and responds to the join request from GW 1 202. In step 314, GW 2 204 receives signal 306. In step 316, GW 2 204 generates and sends message 318, thereby transmitting the join request to network server 216. In step 320, network server 216 receives message 318 and responds to the join request from GW 2 204. In step 322, network server generates and sends message 324, thereby transmitting the join request to application server (AS) 218. In step 326, in response to the received join request, AS 218 generates and sends message 330, thereby transmitting the join acceptance to NS 216. In step 332, NS 216 receives message 330, and in step 334, NS 216 generates and sends message 336, thereby transmitting the join acceptance to GW 2204. In step 340, GW 2204 generates and sends wireless IoT signal 342, thereby transmitting the join acceptance to EP IoT device 302. In step 344, EP IoT device 302 receives signal 342 and resumes join acceptance.

[0053] In step 346, EP IoT device 302 generates and sends a wireless IoT broadcast signal 348, which transmits an association request. In step 350, GW 1 202 receives signal 348. In step 352, GW 1 202 generates and sends message 354, thereby transmitting the association request and GW 1 metadata (MD) 358, including RF information, to network server (NS) 216. In step 358, network server 216 receives message 354 and resumes the transmission of the association request and GW 1 metadata from GW 1 202. In step 360, GW 2 204 receives signal 348. In step 362, GW 2 204 generates and sends message 363, thereby transmitting the association request and GW 2 metadata 364, including RF information, to network server (NS) 216. In step 366, network server 216 receives message 363 and resumes the transmission of the association request and GW 2 metadata from GW 2 204.

[0054] In step 368, network server 216 aggregates the data received from the two GWs corresponding to EP IoT device 302, generates a message 370 containing transmission association request information, GW 1 metadata 356, and GW 2 metadata 364, and sends message 370 to application server 218. In step 374, application server 218 receives message 370 and resumes the transmission. In step 374, application server decides to use GW 2 204 for end-to-end (E2E) communication routing, for example, based on the RF characteristics from GW 1 metadata 356 and GW 2 metadata 364, such as receiving a stronger signal at GW 2 204. Therefore, application server 218 has associated EP IoT device 302 with GW 2 204.

[0055] In step 374, application server 218 generates and sends message 377 to network server 216. Message 377 includes an acknowledgment 382 corresponding to the association request, an instruction 380 to network server 216 requesting that EP IoT device 302 always operate in Class C, and application server metadata 378. In some embodiments, AS metadata 378 includes an identifier corresponding to the selected GW (which is GW2 204) and / or an identifier corresponding to the E2E communication path being established and including the selected GW (which is GW 2). In step 383, network server 216 receives message 377 and resumes transmission. In step 384, network server 216 generates and sends association acknowledgment message 384 to GW2 204. Association acknowledgment message 384 includes an acknowledgment 382 of the association request, a request 380' to EP IoT device 302 to set the Class C device to always be on, and application server metadata 378. In step 386, GW2 204 receives association acknowledgment message 384 and resumes transmission. In step 388, GW 2204 generates and sends a wireless IoT signal 390, which transmits an acknowledgment 382 of the association request, a request 380' for Class C always-on to EP 302, and application server metadata 378. In step 392, EP IoT device 302 receives signal 390 and resumes transmitting information.

[0056] In step 394, EP IoT device 302 switches to Class C operation. In step 396, EP IoT device 302 generates and transmits a broadcast IoT signal 398, which conveys a routing request. As indicated by box 400, the routing request conveys a command acknowledging the received request for Class C. In step 404, GW 1 202 receives signal 398 and resumes transmitting the information. In step 404, GW 1 202 generates and sends a routing request message 406 to network server 216, and in step 408, the network server receives routing request message 406. In step 410, GW 2 204 receives signal 398 and resumes transmitting the information. In step 412, GW 2 204 generates and sends a routing request message 414 to network server 216, and in step 414, network server 216 receives routing request message 412. In step 416, the network server processes the information from received messages 408 and 414, generates a routing request message 418, and sends the routing request message 418 to the application server 218. The routing request message 418 conveys an ACK for a Class C request. In step 420, the application server 218 receives the routing request message 418, and in response, generates and sends a routing acknowledgment message 424 to the network server in step 422. In some embodiments, the routing acknowledgment message 424 includes an instruction for the network server 216 to command the EP IoT device 302 to begin Transmit Power Control (TPC) training. In step 426, the network server 216 receives the routing acknowledgment message 424, and in step 428, the network server generates and sends a routing acknowledgment message 436 to the GW 2 204. In some embodiments, the routing acknowledgment message 436 includes a command to begin TPC training. In step 431, GW 2 204 receives route confirmation message 430, and in step 432, GW 2 204 generates and sends IoT signal 434 including route confirmation message, for example, including confirmation of route request for signal 398 and including command to start TPC training.

[0057] In step 438, the EP IoT device 302 begins a Transmit Power Control (TPC) training operation. In step 440, the EP IoT device 302 generates and transmits an IoT wireless signal 442 including training routing data frame 1. The IoT wireless signal 442 including training routing data frame 1 is transmitted at the highest data rate and the highest transmission power level, for example, as broadcast, as indicated by box 444. In step 446, GW 1 202 successfully receives the IoT signal 442 and resumes the transmission of training routing data frame 1. In step 448, GW 1 202 generates and sends a message 450 to the network server 216. The message 450 includes training routing data frame 1 and GW1 metadata 452, such as GW1ID information, received RF information, such as received signal strength information, received SNR information, etc. In step 454, the network server 216 receives message 450 and resumes the transmission of information including training routing data frame 1 and GW1 metadata 452. In step 458, GW 2 204 successfully receives IoT signal 442 and recovers the transmitted training routing data frame 1. In step 456, GW 2 204 generates and sends message 460 to network server 216. Message 460 includes training routing data frame 1 and GW 2 metadata 461, such as GW 2ID information, received RF information (e.g., received signal strength information, received SNR information, etc.). In step 464, network server 216 receives message 460 and recovers the transmitted information including training routing data frame 1 and GW 2 metadata 461. In step 464, network server 216 aggregates the information from received messages 450 and 460, generates an aggregated training routing data frame 1 message 466, which includes training routing data frame 1, GW 1 metadata 452, and GW 2 metadata 461, and sends message 466 to application server 218. In step 468, AS 218 receives message 466 and recovers the transmitted information. In step 470, AS 218 determines, based on the information in received message 466, that both GW 1 202 and GW 2 204 have successfully received training routing data frame 1. It then decides to reduce the transmission power level of EP IoT device 302, generates message 472, and sends message 472 to NS 216. Message 472 includes an acknowledgment 474 confirming receipt of training routing data frame 1, and an instruction 476 to NS 216 that EP 302 should reduce its transmission (TX) power by one level (e.g., 1.5 dBm). In step 448, NS 216 receives message 472 and resumes transmission. In step 480, NS 216 generates message 481 and sends it to GW 2 204.Message 481 includes an acknowledgment 482 confirming receipt of training routing data frame 1, and a command 484 to EP 302 to reduce the transmission (TX) power by one level (e.g., 1.5 dBm). In step 485, GW 2 204 receives message 481 and resumes transmission. In step 486, GW 2 204 generates an IoT wireless signal 488 and transmits it to EP IoT device 302, sending an ACK 482 and the command 484 to reduce the TX power by one level. In step 490, EP IoT device 302 receives signal 488, resumes transmission, and reduces its TX power by one level.

[0058] In step 492, the EP IoT device 302 generates and transmits an IoT wireless signal 494 including training routing data frame 2. As indicated by box 496, the IoT wireless signal 442, including training routing data frame 2, is transmitted at the highest data rate and a first reduced transmission power level, e.g., broadcast. In step 498, GW 1 202 successfully receives the IoT signal 494 and recovers the transmitted training routing data frame 2. In step 500, GW 1 202 generates and sends a message 502 to the network server 216. Message 502 includes training routing data frame 2 and GW 1 metadata 504, such as GW 1ID information, received RF information (e.g., received signal strength information, received SNR information, etc.). In step 506, the network server 216 receives message 512 and recovers the transmitted information including the training routing data frame 2 and GW 1 metadata 504. In step 508, GW 2204 successfully receives the IoT signal 494 and recovers the transmitted training routing data frame 2. In step 510, GW2 204 generates and sends message 512 to network server 216. Message 512 includes training routing data frame 2 and GW2 metadata 514, such as GW2ID information, received RF information (e.g., received signal strength information, received SNR information, etc.). In step 516, network server 216 receives message 512 and recovers the transmitted information including the training routing data frame 2 and GW2 metadata 514. In step 518, network server 216 aggregates the information from received messages 502 and 512, generates an aggregated training routing data frame 2 message 520 including training routing data frame 2, GW1 metadata 504, and GW2 metadata 514, and sends message 520 to application server 218. In step 522, AS218 receives message 520 and recovers the transmitted information. In step 524, AS 218 determines, based on the information from the received message 520, that both GW 1 202 and GW 2 204 have successfully received the training routing data frame 2. It then decides to reduce the transmission power level of the EP IoT device 302, generates message 526, and sends message 526 to NS 216. Message 526 includes an acknowledgment 528 confirming the receipt of the training routing data frame 2, and an instruction 530 to NS 216 instructing EP 302 to reduce its transmission (TX) power by one level (e.g., 1.5 dBm). In step 532, NS 216 receives message 526 and resumes transmission. In step 534, NS 216 generates message 535 and sends it to GW 2 204. Message 535 includes an acknowledgment 536 confirming the receipt of the training routing data frame 2, and an instruction 538 to EP 302 instructing it to reduce its transmission (TX) power by one level (e.g., 1.5 dBm).In step 540, GW 2 204 receives message 535 and resumes transmitting the information. In step 542, GW 2 204 generates an IoT wireless signal 544 and transmits it to the EP IoT device 302. This signal transmits an ACK 536 and a command 538 to reduce the TX power by one level. In step 546, the EP IoT device 302 receives signal 544, resumes transmitting the information, and reduces its TX power by one level.

[0059] For example, in response to AS 218 determining that GW 1 202 and GW 2 204 have both successfully received training routing data and can and sometimes will execute frames, additional iterations of the training routing data frames are sent and then the EP IoT device 302 is commanded to reduce power.

[0060] In step 448, EP IoT device 302 generates and transmits an IoT wireless signal 550 including training routing data frame N. The IoT wireless signal 550, including training routing data frame N, is transmitted at the highest data rate and with a reduced transmission power level for the (N-1)th time, e.g., broadcast, as indicated by box 552. GW 1 202 fails to receive the IoT signal 554, as indicated by X554. In step 556, GW 2 204 successfully receives the IoT signal 550 and recovers the transmitted training routing data frame N. In step 558, GW 2 204 generates and sends a message 560 to network server 216 including training routing data frame N and GW 2 metadata 562, such as GW 2ID information, received RF information, such as received signal strength information, received SNR information, etc. In step 564, network server 216 receives message 560 and recovers the information including the transmitted training routing data frame N and GW 2 metadata 562. In step 558, the network server generates a Training Routing Data Frame N message 568, which includes the Training Routing Data Frame N and GW2 metadata 562, and sends message 568 to the application server 218. In step 570, AS 218 receives message 568 and resumes the transmission of information. In step 572, AS 218 determines, based on the information in the received message 568, that the power reduction has been eliminated in EP 302 communication via GW 1 202, that EP 302 communication via GW 2 204 to NS216 / AS 218 is still operating and satisfactory, and that TPC training for EP IoT device 302 has been completed. In step 574, AS 218 generates an ACK message 574 and sends it to NS 216, the message conveying that the Training Routing Data Frame N has been successfully received, TPC training is complete, the TX power should remain at the current set level, and that it can continue to send sensor measurement reports using the current TX power level. In step 576, NS 216 receives an ACK message 575. In response, in step 578, NS 216 generates ACK message 580 (e.g., a forwarded version of ACK 575 conveying the information of ACK message 575) and sends it to GW 2 204. In step 582, GW 2 204 receives ACK message 580 and recovers the information conveyed in message 580. In step 584, GW 2 204 generates and transmits IoT wireless signal 486 to EP IoT device 302, which conveys the information of ACK message 580. In step 588, EP IoT device 302 receives signal 586 and recovers the transmitted information.

[0061] In step 590, EP IoT device 302 determines that TPC training is complete and the current TX power level should be used. In step 590, EP IoT device 302 is operated to, for example, perform sensor measurements and generate a sensor measurement report including sensor application dataset 1. In step 594, EP IoT device 302 generates a wireless IoT signal 598 that transmits device (e.g., sensor) application dataset 1. As indicated by box 598, signal 598 is transmitted at the highest data rate and the (N-1)th reduced power level. GW 1 202 does not receive wireless IoT signal 596, as indicated by X 600. However, in step 602, wireless signal 596 is successfully received by GW 2 204 and device (e.g., sensor) application dataset 1 is successfully recovered. In step 604, GW 2 204 generates message 606 and sends it to NS 216, thereby conveying device (e.g., sensor) application dataset 1. In step 608, NS 216 receives message 606 and recovers the transmitted information. In step 609, NS 216 generates and sends message 610 to application server 218, which includes device (e.g., sensor) application dataset 1. In step 612, application server 218 receives message 612, recovers the transmitted information, and forwards the recovered device (e.g., sensor) application dataset 1 to its corresponding appropriate application (e.g., temperature monitoring application, security application, instrumentation application, etc.). In step 614, AS 218 generates ACK 616 in response to the received signal 596 and sends it to NS 216. In step 618, NS 216 receives ACK message 616 and, in response, generates and sends ACK message 622 (e.g., a forwarded copy of message 616) to GW 2204 in step 620. In step 624, GW 2204 receives ACK message 622 and, in response, generates and sends wireless IoT signal 628 to EP IoT device 302 in step 626, which transmits the ACK for message 622. In step 630, the EP IoT device 302 receives signal 628 and resumes transmitting the ACK.

[0062] The EP IoT device 302 repeatedly performs the process of measuring, generating measurement reports, and sending the measurement reports to AS 218. Due to the TX power level setting, these processes are only transmitted via GW 2204.

[0063] In step 632, the EP IoT device 302 is operated to, for example, perform sensor measurements and generate a sensor measurement report including a sensor application dataset M. In step 634, the EP IoT device 302 generates a wireless IoT signal 636 that transmits the device (e.g., sensor) application dataset M. Signal 636 is transmitted at the highest data rate and the (N-1)th reduced power level, as indicated by block 638. GW 1 202 does not receive the wireless IoT signal 636, as indicated by X 639. However, in step 640, the wireless signal 636 is successfully received by GW 2 204 and the device (e.g., sensor) application dataset M is successfully recovered. In step 642, GW 2 204 generates message 644 and sends it to NS 216 to convey the device (e.g., sensor) application dataset M. In step 646, NS 216 receives message 644 and recovers the transmitted information. In step 648, NS 216 generates message 650 and sends it to application server 218. This message includes a device (e.g., sensor) application dataset M. In step 652, application server 218 receives message 650, recovers the transmitted information, and forwards the recovered device (e.g., sensor) application dataset M to its corresponding appropriate application (e.g., temperature monitoring application, security application, instrumentation application, etc.). In step 654, AS 218 generates ACK 656 in response to the received application dataset signal 636 and sends it to NS 216. In step 658, NS 216 receives ACK message 656 and, in response, generates and sends ACK message 662, such as a forwarded copy of message 656, to GW2 204 in step 660. In step 664, GW2 204 receives ACK message 662 and, in response, generates and sends a wireless IoT signal 668 to EP IoT device 302 in step 666, which transmits the ACK for message 662. In step 670, EP IoT device 302 receives signal 668 and resumes transmitting the ACK.

[0064] Figure 3D and Figure 3E Two alternative scenarios are presented, in which the EP IoT device leaves its associated operating mode. Therefore, operation can then proceed from... Figure 3C The end of the journey Figure 3D The beginning, or from Figure 3C The end of the journey Figure 3E The beginning of.

[0065] In step 670, EP IoT device 302 decides to terminate the associated link and association with a single GW (which is GW 2204). In step 672, EP IoT device 302 generates and transmits a wireless IoT signal 674 including an association termination request message (command) directed to application server 218. Signal 674 is transmitted at the highest data rate and the (N-1)th reduced power level, as indicated by block 676. In some other embodiments, the IoT signal transmitting the association termination request is transmitted at the maximum power level. GW 1 202 does not receive signal 674, as indicated by X 678. However, at step 680, signal 674 is received by GW 2 204 and the association termination request (command) is successfully resumed. In step 682, GW 2 204 generates association termination request message 684 and sends it to NS 216. In step 686, NS 216 receives message 684, and in response, in step 688, generates an association exit request message 690 and sends it to AS 218. In step 692, AS 218 receives the association exit request message 690. In step 694, AS 218 generates and sends an association exit ACK message 696 and sends message 696 to NS 216. In step 698, AS 218 suspends the association link with EP 302; for example, EP IoT device 302 is no longer associated with a single GW 2 204. Therefore, AS 218 can now expect to receive information from EP 302 via any of the multiple alternative GWs (GW 1 202 or GW 2 204). In step 700, NS 216 receives message 696, and in response, generates an associated exit ACK message 704 and sends it to GW 2 204. In step 706, GW 2 204 receives the associated exit ACK message 704, and in response, in step 708, generates an IoT wireless signal 708 and sends it to the EP IoT device 302, which transmits the associated exit ACK. In step 710, the EP IoT device 302 receives signal 302, recovers the transmitted information, and recognizes that the associated exit request has been granted. In step 712, the EP IoT device suspends the associated link with the NS / AS and enters a fallback mode for non-associated connectivity. In various embodiments, as part of step 712, the EP IoT device 302 increases its TX power level to maximum power.

[0066] In step 714, AS 218 decides to terminate the link associated with EP IoT 302 and the association between EP IoT device 302 and a single GW (which is GW 2 204). In step 714, AS 218 generates message 718 and sends it to NS 216 to notify NS to send an association termination request (command) to EP IoT device 320. In step 720, NS 216 receives message 718, and in response, generates an association termination request (command) message 724 in step 722 and sends it to GW 2 204, which is received by GW 2 204 in step 726. In step 726, GW 2 204 generates an IoT wireless signal 730 and transmits it to EP IoT device 302, which carries the association termination request (command). In step 732, EP IoT device 302 receives signal 732, and in response, generates and transmits an IoT wireless signal 736 including an association termination ACK in step 734. As indicated by box 737, signal 736 is transmitted at the highest data rate and the (N-1)th reduced power level. In some other embodiments, the signal transmitting the associated exit ACK is transmitted at a higher power level.

[0067] GW 1 202 did not receive signal 736, as indicated by X 738. However, in step 740, signal 736 was received by GW2 204 and the associated exit request ACK was successfully recovered.

[0068] In step 741, EP IoT device 302 suspends the associated link with NS / AS and enters a fallback mode for non-associated connectivity. In various embodiments, as part of step 741, EP IoT device 302 increases its TX power level to maximum power.

[0069] In step 742, GW 2 204 generates an associated ACK message 744 and sends it to NS 216. In step 748, NS 216 receives message 744, and in response, in step 750, generates an associated exit ACK message 752 and sends it to AS 218. In step 751, NS 216 suspends the link associated with EP 302.

[0070] In step 754, AS 218 receives an association exit ACK message 752. In step 755, AS 218 suspends the link associated with EP IoT device 302; for example, EP IoT device 302 is no longer associated with a single GW 2 204. Therefore, AS 218 can now expect to receive information from EP IoT device 302 via any of the multiple alternative GWs (GW 1 202 or GW 2 204).

[0071] Figure 4, including Figure 4A and Figure 4B The combination of these components is an exemplary signaling diagram 800 according to an exemplary embodiment, including portion A 801 and portion B 803. Exemplary signaling diagram 800 includes exemplary endpoint IoT device 302, GW 1 202, GW 2 204, network server (NS) 216, and application server (AS) 218. For example, exemplary EP IoT device 302 is... Figure 2 Any one of the IoT devices (220, 222, 224, 226, 228, 230, 232, ..., 234) in the system 200. Exemplary signaling diagram 800 illustrates: An exemplary EP IoT device, under the guidance of a control server, performs a Transmit Power Control (TPC) training operation to determine the transmission power level for application data transmission in non-associative mode. The determined power is lower than the maximum permissible TX power, and the EP IoT application data is transmitted at the determined TX power level. The EP IoT application data is received by a single IoT GW.

[0072] In step 804, EP IoT device 302 generates and transmits a wireless IoT broadcast signal 806, which conveys a join request. In step 808, GW 1 202 receives signal 806. In step 810, GW 1 202 generates message 812 and transmits it to network server (NS) 216, which also conveys a join request. In step 814, network server 216 receives message 812 and responds to the join request from GW 1 202. In step 818, GW 2 204 receives signal 806. In step 817, GW 2 204 generates message 818 and transmits it to network server 216. In step 820, network server 216 receives message 818 and responds to the join request from GW 2 204. In step 822, network server 216 generates message 824 and sends it to application server (AS) 218, which also conveys a join request. In step 816, AS 218 receives join request message 824. In step 826, in response to the received join request, AS 218 generates and sends message 830 to NS 216, which conveys join acceptance. In step 832, NS 216 receives message 830, and in step 834, NS 216 generates message 836 and sends it to GW 2 204, which conveys join acceptance. In step 840, GW 2 204 generates and sends wireless IoT signal 842 to EP IoT device 302, which conveys join acceptance. In step 844, EP IoT device 302 receives signal 842 and resumes join acceptance.

[0073] In step 846, the EP IoT device 302 initiates a Transmit Power Control (TPC) training operation. In some embodiments, the EP IoT device initiates the TPC training operation in response to a received join acceptance. In some embodiments, the EP IoT device initiates the TPC training operation in response to a command sent from a control server (e.g., AS 218), such as a command to begin TPC training for a non-associated mode. In some such embodiments, the command instructs the EP IoT device 302 to set the data rate to the maximum data rate and initially set the TX power level to the maximum power level.

[0074] In step 848, EP IoT device 302 generates and transmits IoT wireless signal 850 including training routing data frame 1. IoT wireless signal 850 including training routing data frame 1 is transmitted at the highest data rate and highest transmission power level, for example, as broadcast, as indicated by box 852. In step 854, GW 1 202 successfully receives IoT signal 850 and recovers the transmitted training routing data frame 1. In step 856, GW 1 202 generates and sends message 868 to network server 216. Message 868 includes training routing data frame 1 and GW1 metadata 860, such as GW1ID information, received RF information, such as received signal strength information, received SNR information, etc. In step 862, network server 216 receives message 858 and recovers the transmitted information including training routing data frame 1 and GW1 metadata 860. In step 866, GW 2 204 successfully receives IoT signal 850 and recovers the transmitted training routing data frame 1. In step 866, GW 2204 generates and sends message 868 to network server 216. Message 868 includes training routing data frame 1 and GW 2 metadata 870, such as GW 2ID information and received RF information, such as received signal strength information and received SNR information. In step 871, network server 216 receives message 868 and recovers the transmitted information including training routing data frame 1 and GW 2 metadata 870. In step 872, network server 216 aggregates the information from received messages 858 and 868, generates an aggregated training routing data frame 1 message 874, which includes training routing data frame 1, GW 1 metadata 860, and GW 2 metadata 870, and sends message 874 to application server 218. In step 876, AS 218 receives message 874 and recovers the transmitted information. In step 878, AS 218 determines, based on the information in received message 874, that both GW 1 202 and GW 2 204 have successfully received training routing data frame 1, decides to reduce the transmission power level of EP IoT device 302, generates message 880, and sends message 880 to NS 216. Message 880 includes acknowledgment 882, confirming receipt of training routing data frame 1, and instruction 884 to NS 216 to reduce the transmission (TX) power of EP 302 by one level (e.g., 1.5 dBm). In step 886, NS 216 receives message 880 and resumes transmission. In step 888, NS 216 generates message 890 and sends it to GW 2 204. Message 890 includes acknowledgment 892, confirming receipt of training routing data frame 1, and instruction 894 to EP 302 to reduce the transmission (TX) power by one level (e.g., 1.5 dBm).In step 896, GW 2 204 receives message 490 and resumes transmitting the information. In step 898, GW 2 204 generates an IoT wireless signal 900 that transmits ACK 892 and a command 894 to reduce the TX power by one level, and transmits it to the EP IoT device 302. In step 902, the EP IoT device 302 receives signal 900, resumes transmitting the information, and reduces its TX power by one level.

[0075] In step 904, the EP IoT device 302 generates and transmits an IoT wireless signal 906 including training routing data frame 2. As indicated by block 908, the IoT wireless signal 906, including training routing data frame 2, is transmitted, for example, via broadcast, at the highest data rate and a first reduced transmission power level. In step 910, GW 1 202 successfully receives the IoT signal 906 and recovers the transmitted training routing data frame 2. In step 911, GW 1 202 generates and sends a message 912 to network server 216. This message 912 includes training routing data frame 2 and GW 1 metadata 914, such as GW 1ID information, received RF information (e.g., received signal strength information, received SNR information, etc.). In step 915, network server 216 receives message 912 and recovers the transmitted information including the training routing data frame 2 and GW 1 metadata 914. In step 916, GW 2 204 successfully receives the IoT signal 906 and recovers the transmitted training routing data frame 2. In step 918, GW 2204 generates and sends message 920 to network server 216. Message 920 includes training routing data frame 2 and GW 2 metadata 922, such as GW 2ID information and received RF information, such as received signal strength information and received SNR information. In step 924, network server 216 receives message 920 and recovers the transmitted information including the training routing data frame 2 and GW 2 metadata 922. In step 926, network server 216 aggregates the information from received messages 912 and 920, generates an aggregated training routing data frame 2 message 928 including training routing data frame 2, GW 1 metadata 914, and GW 2 metadata 922, and sends message 928 to application server 218. In step 930, AS 218 receives message 928 and recovers the transmitted information. In step 932, AS 218 determines, based on the information in received message 928, that both GW 1 202 and GW 2 204 have successfully received training routing data frame 2, decides to reduce the transmission power level of EP IoT device 302, generates message 934, and sends message 934 to NS 216. Message 934 includes an acknowledgment 936 confirming receipt of training routing data frame 2, and an instruction 938 to NS 216 to reduce the transmission (TX) power of EP 302 by one level (e.g., 1.5 dBm). In step 940, NS 216 receives message 934 and recovers the transmitted information. In step 942, NS 216 generates message 944 and sends it to GW2 204. Message 944 includes an acknowledgment 946 confirming receipt of training routing data frame 2, and an instruction 948 to EP 302 to reduce the transmission (TX) power by one level (e.g., 1.5 dBm).In step 950, GW 2204 receives message 944 and resumes transmitting the information. In step 952, GW 2204 generates an IoT wireless signal 954 and transmits it to the EP IoT device 302. This signal transmits ACK 956 and a command 958 to reduce the TX power by one level. In step 960, the EP IoT device 302 receives signal 954, resumes transmitting the information, and reduces its TX power by one level.

[0076] For example, in response to AS 218 determining that GW 1 202 and GW 2 204 have both successfully received training routing data, which can sometimes be executed, additional iterations of the training routing data frame are sent and then the EP IoT device 302 is commanded to reduce power.

[0077] In step 962, EP IoT device 302 generates and transmits an IoT wireless signal 964 including training routing data frame N. The IoT wireless signal 964, including training routing data frame N, is transmitted at the highest data rate and a reduced transmission power level (N-1), e.g., broadcast, as indicated by box 966. GW 1 202 fails to receive the IoT signal 964, as indicated by X968. In step 970, GW 2 204 successfully receives the IoT signal 964 and recovers the transmitted training routing data frame N. In step 972, GW 2 204 generates and sends a message 974 to network server 216, which includes training routing data frame N and GW 2 metadata 976, such as GW 2ID information, received RF information (e.g., received signal strength information, received SNR information, etc.). In step 978, network server 216 receives message 974 and recovers the transmitted information including training routing data frame N and GW 2 metadata 976. In step 980, the network server generates a Training Routing Data Frame N message 982, which includes the Training Routing Data Frame N and GW 2 metadata 976, and sends message 982 to the application server 218. In step 984, AS 218 receives message 982 and resumes the transmission of information. In step 986, AS 218 determines, based on the information in the received message 982, that the power reduction has eliminated EP 302 communication via GW 1 202, that EP 302 communication via GW 2 204 to NS 216 / AS 218 is still operational and satisfactory, and that TPC training for EP IoT device 302 has been completed, for example, since effective communication is now maintained only via one gateway. In step 988, AS 218 generates an ACK message 990 and sends it to NS 216, which conveys that the Training Routing Data Frame N was successfully received, TPC training is complete, the TX power should remain at the current set level, and that it can continue to send sensor measurement reports using the current TX power level. In step 992, NS 216 receives ACK message 990. In response, in step 994, NS 216 generates ACK message 996 and sends it to GW 2 204, for example, a forwarded version of ACK 990 conveying the information of ACK message 990. In step 998, GW 2 204 receives ACK message 996 and recovers the information transmitted in message 996. In step 1000, GW 2 204 generates IoT wireless signal 1002 and transmits it to EP IoT device 302, which conveys the information of ACK message 996. In step 1004, EP IoT device 302 receives signal 1002 and recovers the transmitted information.

[0078] In step 1006, EP IoT device 302 determines that TPC training is complete and the current TX power level should be used. In step 1008, EP IoT device 302 is operated to, for example, perform sensor measurements and generate a sensor measurement report including sensor application dataset 1. In step 1010, EP IoT device 302 generates a wireless IoT signal 1012 that transmits device (e.g., sensor) application dataset 1. As indicated by box 1014, signal 1012 is transmitted at the highest data rate and the (N-1)th reduced power level. GW 1 202 does not receive wireless IoT signal 1012, as indicated by X 1016. However, in step 1018, wireless signal 1012 is successfully received by GW 2 204 and device (e.g., sensor) application dataset 1 is successfully recovered. In step 1020, GW 2 204 generates message 1022 and sends it to NS 216, conveying device (e.g., sensor) application dataset 1. In step 1024, NS 216 receives message 1022 and recovers the transmitted information. In step 1026, NS 216 generates message 1028 and sends message 1028 to application server 218, which includes device (e.g., sensor) application dataset 1. In step 1030, application server 218 receives message 1028, recovers the transmitted information, and forwards the recovered device (e.g., sensor) application dataset 1 to its corresponding appropriate application (e.g., temperature monitoring application, security application, instrumentation application, etc.). In step 1032, AS 218 generates ACK 1034 in response to the received application dataset of signal 1012 and sends it to NS 216. In step 1036, NS 216 receives ACK message 1034 and, in response, generates and sends ACK message 1040 (e.g., a forwarded copy of message 1034) to GW 2 204 in step 1038. In step 1042, GW 2 204 receives ACK message 1040, and in response, generates wireless IoT signal 1046 in step 1044 and transmits it to EP IoT device 302, which transmits ACK message 1040. In step 1048, EP IoT device 302 receives signal 1046 and recovers the transmitted ACK.

[0079] The EP IoT device 302 repeatedly performs the process of measuring, generating measurement reports, and sending the measurement reports to AS 218. Due to the TX power level setting, these processes are only transmitted via GW 2204.

[0080] In step 1050, the EP IoT device 302 is operated to, for example, perform sensor measurements and generate a sensor measurement report including a sensor application dataset M. In step 1052, the EP IoT device 302 generates a wireless IoT signal 1054 that transmits the device (e.g., sensor) application dataset M. Signal 1054 is transmitted at the highest data rate and the (N-1)th reduced power level, as indicated by block 1056. GW 1 202 does not receive the wireless IoT signal 1054, as indicated by X 1058. However, in step 1060, the wireless signal 1054 is successfully received by GW 2 204 and the device (e.g., sensor) application dataset M is successfully recovered. In step 1062, GW 2 204 generates message 1064 and sends it to NS 216 to convey the device (e.g., sensor) application dataset M. In step 1066, NS 216 receives message 1064 and recovers the transmitted information. In step 1068, NS 216 generates message 1070 and sends message 1070 to application server 218. This message includes a device (e.g., sensor) application dataset M. In step 1072, application server 218 receives message 1070, recovers the transmitted information, and forwards the recovered device (e.g., sensor) application dataset M to its corresponding appropriate application (e.g., temperature monitoring application, security application, instrumentation application, etc.). In step 1074, AS 218 generates ACK 1076 in response to the received application dataset signal 1054 and sends it to NS 216. In step 1078, NS 216 receives ACK message 1076 and, in response, generates and sends ACK message 1082, such as a forwarded copy of message 1076, to GW 2 204 in step 1080. In step 1084, GW 2 204 receives ACK message 1082, and in response, generates wireless IoT signal 1087 in step 1086 and sends it to EP IoT device 302, which transmits ACK message 662. In step 1088, EP IoT device 302 receives signal 1087 and resumes transmitting the ACK.

[0081] Figure 5Figure 1100 illustrates an exemplary endpoint (EP) Internet of Things (IoT) device 302, which initially communicates successfully via two communication paths, each including a different gateway, and then, after transmission power control (TPC) training that causes reduced transmission power for the EP IoT, successfully transmits only via one communication path corresponding to a single gateway. The EP IoT device 302 includes a wireless transmitter TXW 1108 and a wireless receiver RXW 1110. GW 1 202 includes a wireless transmitter TXW 1113, a wireless receiver RXW 1115, a network receiver RXN1 1119, and a network transmitter TXN1 1117. GW 2204 includes a wireless transmitter TXW 1112, a wireless receiver RXW 1114, a network receiver RXN1 1118, and a network transmitter TXN1 1116. Network server (NS) 216 includes a first network transmitter TXN1 1120, a first network receiver RXN1 11122, a second network transmitter RXN2 1124, and a second network transmitter TXN2 1126. In some embodiments, the first and second network transmitters of NS 216 are identical components. In some embodiments, the first and second network receivers of NS 216 are identical components. Application server (AS) 218 ​​includes a network transmitter TXN2 1128 and a network receiver RXN2 1130.

[0082] Drawing portion 1102 illustrates the initial communication of the exemplary EP IoT device 302 with the application server, for example, sending information to AS 218 via a first communication path including GW 1 202 (EP TXW->GW1RXW->GW 1TXN1->GW 1TXN1->NS RXN1->NSRXN2->AS RXN2) and a second communication path including GW 2 204 (EP TXW->GW 2RXW->GW 2TXN1->GW2TXN1->NS RXN1->NS RXN2->AS RXN2). The first communication path is illustrated by arrows 1150a, 1151a, 1152a, 1153c, and 1154c. In drawing portion 1102, the second communication path is shown by arrows 1150b, 1151b, 1152b, 1153c, and 1154c. At this time, EP 302 has a very strong link, for example, due to a high transmission power level. EP302 is being seen by multiple GWs (202, 204). In this example, the connection between EP302 and GW2 204 is stronger. EP device 302 is "interfering" with a GW (GW1 202) that doesn't need to serve it. At this point, GW1 202 can better serve another EP device in the communication system. If EP302 needs to reduce its TX power, then network capacity can be increased.

[0083] The larger arrow 1104 indicates a TPC iteration driven by the application server (AS) controlling EP 302, for example, reducing the TX power during each iteration until only one GW is able to successfully receive IoT wireless signals transmitted from EP IoT device 302 at the highest data rate. In this example, GW 1 202 exit results in a single end-to-end (E2E) path being used for communication between EP IoT device 302 and AS 218, the single E2E communication path including GW 2 204.

[0084] The AS 218-driven iteration includes the following. Commands are issued by AS 218: i) setting device 302 to the highest data rate (SF8BW500); ii) in each iteration, commanding the GW TX power to decrease by 1.5 dBm; iii) in each iteration, AS 218 instructs NS 216 to issue an ADR command to device 302 to decrease the TX power by 1.5 dBm. The exit criterion for the cycle is that the device is seen by only one GW (i.e., GW 2 302), and in some embodiments, the device is actually associated with GW 2 302.

[0085] Drawing portion 1106 illustrates an exemplary EP IoT device 302 communicating with an application server, for example, sending information to AS 218 via a remaining communication path including GW2 204 (EP TXW->GW 2RXW->GW 2TXN1->GW 2TXN1->NS RXN1->NS RXN2->ASRXN2). The remaining communication path is shown by arrows 1150b, 1151b, 1152b, 1153c, and 1154c in drawing portion 1106. This is the time when EP 302 is transmitting at the correct level for network reception (e.g., only via GW 2204). Other GWs in the system (e.g., GW 1 202, not associated with EP 302) are available and can freely handle more devices. Therefore, network capacity is expanded.

[0086] It should be recognized that by reducing the transmission power of EP IoT devices to eliminate redundant wireless IoT links, not only is there the benefit of reducing overall interference in the wireless communication spectrum and potentially increasing throughput, but additional benefits are also obtained, such as reduced battery power consumption of EP IoT device 302, reduced processing load of GW 1 202, network server 1153 and AS 218, and reduced backhaul signaling traffic transmitted between the gateway and the network server.

[0087] Figure 6, including Figure 6A , Figure 6B , Figure 6C and Figure 6D The combination of these is a flowchart 1200 of an exemplary method for operating a control server (e.g., an application server) according to an exemplary embodiment, for example, in a communication system including a control server, a network server, multiple endpoint (EP) Internet of Things (IoT) devices, and multiple IoT gateways (GW).

[0088] The operation begins at step 1201, where the control server is powered on and initialized. The operation proceeds from step 1201 to steps 1202 and 1210. In step 1202, the control server (e.g., an application server (AS)) monitors for association requests from endpoint (EP) IoT devices. Step 1202 may, and sometimes does, include step 1204, where the control server receives an association request from an EP IoT device that requests association with a gateway and the establishment of an end-to-end (E2E) communication path between the EP IoT device and the control server. This E2E communication path includes a selected gateway, such as a selected IoT gateway, and a wireless link between the EP IoT device and the selected GW. In some embodiments, each iteration of step 1204 includes one of steps 1206 and 1208. In step 1206, the control server receives an association request that includes information identifying a requested gateway to be used in the E2E communication path. In step 1208, the control server receives an association request that does not include information identifying the requested gateway to be used in the E2E communication path, and wherein the control server is expected to select the gateway to be used in the E2E communication path.

[0089] Returning to step 1201, in the continuously executing step 1210, for one or more gateways that can be used by IoT devices, the control server receives RF information (e.g., SNR information, received signal strength information, etc.) corresponding to the EP IoT device. The operation proceeds from steps 1204 and 1210 to step 1212.

[0090] In step 1212, the control server selects a gateway to associate with the EP IoT device and for use in the E2E communication path. In some embodiments, each iteration of step 1212 includes one of steps 1214 and 1216. In step 1214, the control server selects the gateway requested by the EP IoT device for use in the E2E communication path. In step 1216, the control server selects the gateway to be used in the E2E communication path, for example, based on RF information. For example, regarding the signal transmitted from the EP IoT device, the control server selects the gateway with the strongest received signal strength, for example, based on the received signal at the GW, data measurements at the GW, and metadata from the gateway, said data from the GW being forwarded to the control server, for example, via a network server, which aggregates information from multiple gateways.

[0091] The operation proceeds from step 1212 to step 1218. In step 1218, the control server generates an association response message. Step 1218 includes steps 1220, 1222, and in some embodiments, step 1224. In step 1220, the control server includes an acknowledgment in the association response message indicating that the association request is permitted. In step 1222, the control server includes information identifying the E2E communication path (e.g., an E2E path identifier) ​​in the association response message. In step 1224, the control server includes information identifying the gateway selected by the control server for the E2E communication path (e.g., a gateway (GW) identifier) ​​in the association response message. The operation proceeds from step 1218 to step 1226.

[0092] In step 1226, the control server sends the generated association response message to the EP IoT device. Step 1226 includes steps 1228 and 1230, and in some embodiments includes step 1232. In step 1228, the control server sends an acknowledgment indicating that the association request is permitted and that the EP IoT device has been associated with a specific GW, which is the selected GW. In step 1230, the control server sends information identifying the E2E communication path (e.g., an E2E path identifier). In step 1232, the control server sends information identifying the gateway selected by the control server for the E2E communication path (e.g., a GW identifier), the selected gateway being associated with the EP IoT device. Operation proceeds from step 1226 to step 1236 via connection node A1234.

[0093] In step 1236, the control server performs operations to perform Transmission Power Control (TPC) on the EP IoT device for associated mode operation. Step 1236 includes steps 1238, 1240, 1242, 1244, 1246, 1248, 1250, 1252, 1254, 1256, and 1258. In step 1238, the control server sends a command to the EP IoT device to set the EP IoT device to the maximum transmission power level and maximum data rate. The operation proceeds from step 1238 to step 1240. In step 1240, the control server sends a command to the EP IoT device to transmit training data frames. The operation proceeds from step 1240 to step 1242. In step 1242, the control server monitors and / or receives data (e.g., aggregated data) corresponding to one or more gateways that receive training data frames via it. The operation proceeds from step 1242 to step 1244.

[0094] In step 1244, the control server determines whether the training data has been successfully received by the selected gateway. If the training data has been successfully received by the selected gateway, the operation proceeds from step 1244 to step 1250. However, if the training data has not been received by the selected gateway, the operation proceeds from step 1244 to step 1246.

[0095] In step 1250, the control server determines whether the training data has been successfully received by any additional gateways other than the selected gateway. If the training data has been successfully received by one or more additional gateways other than the selected gateway, the operation proceeds from step 1250 to step 1254; otherwise, the operation proceeds from step 1250 to step 1258. In step 1254, the control server sends a command to the EP IoT device to reduce the transmission power level at the EP IoT device, for example, by 1.5 dB. The operation proceeds from step 1254 to step 1240, where the control server sends a command to the EP IoT device to transmit another frame of training data.

[0096] Returning to step 1258, in step 1258, the control server sends a command to the EP IoT device to notify the EP IoT device that TPC training has ended and that the current transmission power level is the power level used for associated pattern data transmission.

[0097] Returning to step 1246, if the evaluation was for the initial training frame, the operation proceeds to step 1248, where the control server determines that the selected gateway already associated (paired) with the EP IoT device is currently unacceptable, and a different gateway needs to be selected and transmission power control training needs to be restarted. However, if the evaluation in step 1244 was not for the initial training frame, the operation proceeds to step 1252, where the control server sends a command to the EP IoT device to increase the transmission power level at the EP IoT device to the power level used for the last successful training reception relative to the selected gateway. The operation proceeds to step 1256. In step 1256, the control server sends a command to the EP IoT device to notify it that TPC training has ended and that the current transmission power level is the power level used for associated pattern data transmission.

[0098] The operation proceeds from step 1236 to step 1260, where the control server receives forwarded EP IoT device application data.

[0099] In some embodiments, forwarded EP IoT application data may and sometimes does include aggregated forwarded EP IoT application data, for example, forwarded from a selected GW and another gateway, for example, based on changes in the location of the EP IoT device since TPC training, changes in channel conditions since TPC training, or TPC training failing to restrict wireless communication to only selected gateways (e.g., because the EP IoT device is equidistant between the two GWs).

[0100] The operation proceeds from step 1260 to step 1262. In step 1262, the control server filters out any received EP IoT application data that has not been transmitted via an E2P communication path including a selected gateway associated with (or paired with) the EP IoT. In some embodiments, the filtering is based on the inclusion of a path identifier. In some embodiments, the filtering is based on the GW identifier corresponding to a selected GW associated with the EP IoT device. In some embodiments, the filtering is performed by a web server preceding the control server, which receives and aggregates information from the GW.

[0101] Repeat steps 1260 and 1262, for example, as an additional data report, such as a sensor report sent by the EP IoT device.

[0102] The operation proceeds from step 1262 to step 1266 via connection node B 1264. In step 1266, the operation control server determines whether the EP IoT device should exit the associated mode. Step 1266 includes steps 1268, 1270, and 1272.

[0103] In step 1268, the control server checks and determines whether it has received the associated exit request from the EP IoT device. If it is determined that the EP IoT device has not received the associated exit request, the operation proceeds from the output of step 1268 to the input of step 1268, and performs another check at a later time, for example, after a predetermined time interval. However, if it is determined that the EP IoT device has received the associated exit request from the EP IoT device, the operation proceeds from step 1268 to step 1272, where the control server determines that the associated pattern regarding the EP IoT device should end.

[0104] In step 1270, the control server determines whether continuing to use the selected GW for the E2E path is undesirable, for example, because the reception quality has degraded since the EP IoT device has moved since the association was determined and the TPC was executed. If it is determined that continuing to use the selected GW is acceptable, the operation proceeds from the output of step 1270 to the input of step 1270, and another check is performed at a later time, for example, after a predetermined time interval. However, if it is determined that continuing to use the selected GW is undesirable, the operation proceeds from step 1270 to step 1272, in which the control server determines that the mode regarding the association of the EP IoT device should be terminated. The operation proceeds from step 1272 to step 1274.

[0105] In step 1274, the control server sends a message to the EP IoT device to terminate the associated mode and transition the EP IoT device to a non-associated mode. Each iteration of step 1274 includes one of steps 1276 or 1278. In step 1276, the control server sends an acknowledgment in response to the received association termination request. In step 1274, the control server sends an association termination request to the EP IoT device. The operation proceeds from step 1274 to step 1282 via connection node C1280.

[0106] In step 1282, the control server performs an operation to perform Transmission Power Control (TPC) on the EP IoT device for non-associative mode operation. Step 1282 includes steps 1284, 1286, 1288, 1290, 1292, 1294, 1296, 1298, 1300, 1302, and 1304. In step 1284, the control server sends a command to the EP IoT device to set the EP IoT device to the maximum transmission power level and maximum data rate. The operation proceeds from step 1284 to step 1286. In step 1286, the control server sends a command to the EP IoT device to transmit training data frames. The operation proceeds from step 1286 to step 1288. In step 1288, the control server monitors and / or receives data (e.g., aggregated data) corresponding to one or more gateways that receive training data frames via it. The operation proceeds from step 1288 to step 1290.

[0107] In step 1290, the control server determines whether the training data has been successfully received by at least one gateway. If the training data has been successfully received by at least one gateway, the operation proceeds from step 1290 to step 1294. However, if the training data has not been received by at least one gateway, the operation proceeds from step 1290 to step 1292.

[0108] In step 1294, the control server determines whether the training data has been successfully received by more than one gateway. If the training data has been successfully received by more than one gateway, the operation proceeds from step 1294 to step 1300; otherwise, the operation proceeds from step 1294 to step 1304. In step 1300, the control server sends a command to the EP IoT device to reduce the transmission power level at the EP IoT device, for example, by 1.5 dB. The operation proceeds from step 1300 to step 1286, where the control server sends a command to the EP IoT device to transmit another frame of training data.

[0109] Returning to step 1304, in step 1304, the control server sends a command to the EP IoT device to notify the EP IoT device that TPC training has ended and that the current transmission power level is the power level used for non-associative mode data transmission.

[0110] Returning to step 1292, if the evaluation was for the initial training frame, the operation proceeds to step 1296, where the control server determines that the EP IoT device is currently inaccessible and TPC training will be restarted at a later time (e.g., after a predetermined delay interval). However, if the evaluation in step 1290 was not for the initial training frame, the operation proceeds to step 1298, where the control server sends a command to the EP IoT device to increase the transmission power level at the EP IoT device to the power level used for the last successful training data reception. The operation proceeds to step 1302. In step 1302, the control server sends a command to the EP IoT device to notify it that TPC training has ended and that the current transmission power level is the power level used for non-associative mode data transmission.

[0111] The operation proceeds from step 1282 to step 1306, where the control server receives forwarded EP IoT device application data. In some embodiments, the forwarded EP IoT application data may, and sometimes does, include aggregated forwarded EP IoT application data, for example, forwarded from multiple GWs, based on changes in the location of the EP IoT device since TPC training, changes in channel conditions since TPC training, or the inability of TPC training to restrict wireless communication to only selected gateways (e.g., because the EP IoT devices are equidistant between two GWs).

[0112] Step 1306 is repeated, for example, as an additional data report, such as a sensor report sent by the EP IoT device. The operation proceeds from step 1306 to step 1202 via connection node D 1308, where the control server monitors another association request from the EP IoT device.

[0113] The flowchart 1200 in Figure 6 has been described from the perspective of controlling a single EP IoT device. It should be understood that the control server is operated to control multiple EP IoT devices in the communication system. Therefore, the steps of flowchart 1200 can and sometimes are executed by the control server for each of the multiple different EP IoT devices in the communication system. Thus, each EP IoT device in the system can and sometimes is associated with (paired with) one of the GWs in the system. Furthermore, each EP IoT device in the system can and sometimes is individually controlled by the control server using Transmission Power Control (TPC).

[0114] Figure 7 This is a diagram of an exemplary control server 1400 (e.g., an application server) according to an exemplary embodiment. The exemplary control server 1400 is, for example, an exemplary control server 218 (e.g., [missing information]) described with respect to the flowchart of FIG6. Figure 2 Application servers (e.g., 3, 4, and 5), and / or control servers (e.g., application servers). An exemplary control server 1400 includes a processor 1402 (e.g., CPU), a network interface 1404 (e.g., wired or optical interface), an I / O interface 1406, components of hardware components 1408 (e.g., circuit components), and memory 1410 coupled together via a bus 1412. These various components can exchange data and information via the bus 1412. The network interface 1404 includes a receiver 1424 and a transmitter 1426. In some embodiments, the receiver 1424 and transmitter 1426 are included as part of a transceiver 1428. The network interface 1404 couples the control server (e.g., application server) to a network server (e.g., network server 216).

[0115] The control server 1400 also includes multiple input / output devices (speaker 1414, switch 1416, mouse 1418, keyboard / keyboard 1420 and display 1422) which are coupled to I / O interface 1406, thereby allowing various I / O devices to communicate with other components coupled to bus 1412.

[0116] The memory 1410 includes a component 1430 (e.g., a component 1430 of a software component) and data / information 1432. Component 1430 of the component includes an association app 1434 for performing operations and controls related to associating the EP device with a specific GW and communication path; a transmission power control (TPC) app 1436 for performing operations and controls related to the TPC controlling the EP device and / or GW device; and multiple device (e.g., sensor) applications, for example, corresponding to different functions and / or services (device (e.g., sensor) app 11434 (e.g., temperature app), device (e.g., sensor) app 2 1436 (e.g., security app), device (e.g., sensor) app 3 1438 (e.g., gas meter app), device (e.g., sensor) app 4 1440 (e.g., electricity meter app), device (e.g., sensor) app 5 1442 (e.g., water meter app), device (e.g., sensor) app 6 1444 (e.g., fire detection and / or notification app), device (e.g., sensor) app 7... 1434 (e.g., vehicle apps, such as vehicle tracking apps or vehicle status reporting apps), ..., device (e.g., sensor) apps N). Data information 1432 includes information corresponding to multiple endpoint (EP) devices (EP device 1 (e.g., EP IoT device 1), data information 1450, ... EP device N data / information 1452). EP device 1 data / information 1450 includes association information, such as information associating EP device 1 with a specific selected or determined GW and the E2E communication path between EP device 1 and control server 1410, determined EP TX power level information 1456, such as the determined TX power level to be used by EP device 1 after TPC training operation under the control of control server 1400, and received device (e.g., sensor) application data 1458 (e.g., sensor reports received from EP devices).

[0117] Figure 8 This is a diagram of an exemplary endpoint (EP) device 1500 according to an exemplary embodiment, such as an EP IoT device, or an EP IoT sensor device. The exemplary EP device 1500 is, for example... Figure 2The EP devices (220, 222, 224, 226, 228, 230, 232, ..., 234), the EP device 302 of Figures 3, 4, and 5, and / or the EP device described with respect to the flowchart of Figure 6. An exemplary EP device 1500 includes a processor 1502 (e.g., CPU), a wireless interface 1504 (e.g., IoT wireless interface), a network interface 1506 (e.g., wired or optical interface), an I / O interface 1510, components of hardware components 1508 (e.g., circuit components), a memory 1512, and a SIM card 1509 in some embodiments, coupled together via a bus 1514. These various components can exchange data and information via the bus 1514. The wireless interface 1504 includes a wireless receiver 1522 coupled to one or more receiving antennas 1526, ..., 1528 and a wireless transmitter 1524 coupled to one or more transmitting antennas 1530, ..., 1532. In some embodiments, the same antennas are used for both transmission and reception. Network interface 1504 includes receiver 1518 and transmitter 1520. In some embodiments, receiver 1518 and transmitter 1520 are included as part of transceiver 1516.

[0118] Endpoint (EP) device 1500 also includes multiple input / output devices (speaker 1534, switch 1536, mouse 1538, keyboard / keyboard 1540, display 1532, camera 1544, microphone 1546, and one or more of the following: temperature sensor 1580, fire sensor 1582, vehicle sensor 1584, water meter sensor 1586, electricity meter sensor 1588, power line sensor 1590, gas meter sensor 1592, safety sensor 1594, ..., custom sensor 1596), which are coupled to I / O interface 1510, thereby allowing various I / O devices to communicate with other components coupled to bus 1514.

[0119] Memory 1510 includes component 1548 (e.g., component of software components) and data / information 1560. Component 1548 includes an association application 1562 for performing operations and associating the EP device with a single GW, and a communication path between the EP device and a control server (e.g., an application server, a transport power control (TPC) app 1564 for performing operations related to EP device TX power control (e.g., determining the TX power level to be used) under the guidance of the control server, and a device app 1566 (e.g., a sensor app corresponding to the functions and / or data types to be reported by the EP device to the control server (e.g., the application server)). Data / information 1560 includes association information 1568 (e.g., information identifying a specific GW already associated with the EP device and / or information identifying the E2E communication path between the EP device and the control server (e.g., the application server)) to be sent to the application server, mode information 1570 (e.g., information identifying whether the EP device is currently in an associated or non-associated mode), a determined TX power level 1572 to be used by the EP device, and device application data 1574 (e.g., sensor reports).

[0120] Figure 9 This is a diagram of an exemplary network server 1600 according to an exemplary embodiment. The exemplary network server 1600 is, for example... Figure 2 Network servers 216 (as described in Figures 3, 4, and 5) and / or the network server described with respect to the flowchart of Figure 6. An exemplary network server 1600 includes a processor 1602 (e.g., CPU), a first network interface 1604 (e.g., a wired or optical interface), a second network interface 1606, an I / O interface 1630, components of hardware components 1608 (e.g., components of circuitry), and memory 1610 coupled together via a bus 1617. These various components can exchange data and information via the bus 1617. The first network interface 1604 includes a receiver 1612 and a transmitter 1614. In some embodiments, the receiver 1612 and transmitter 1614 are included as part of a transceiver 1616. The first network interface 1604, for example, couples the network server to other network nodes and / or the Internet. The second network interface 1606 includes a receiver 1618 and a transmitter 1620. In some embodiments, the receiver 1618 and transmitter 1620 are included as part of a transceiver 1622. The second network interface 1606, for example, couples the network server to a control server (e.g., an application server, such as AS 218). In some embodiments, a single network interface performs the functions of both the first and second network interfaces 1604 and 1606.

[0121] The network server 1600 also includes multiple input / output devices (speaker 1628, switch 1632, mouse 1634, keyboard / keyboard 1636, and monitor 1638) which are coupled to I / O interface 1630, thereby allowing various I / O devices to communicate with other components coupled to bus 1617.

[0122] Memory 1610 includes components 1624 (e.g., components of software components) and data / information 1626. Component 1624 includes an associated app 1650 for performing operations and controls associated with connecting the EP device to a specific GW and communication path, and a Transport Power Control (TPC) application 1652 for performing operations and controls related to the TPC controlling the EP device and / or GW device. The operations performed by network device 1600 include aggregation related to messages received from one or more gateways and communication of data / information including aggregated information received from the gateways to a control server (e.g., an application server). Network device 1600 also receives messages from the control server (e.g., an application server) instructing the network server to send messages to the EP device and / or GW, such as commands including power control commands.

[0123] Figure 10 This is a schematic diagram of an exemplary gateway (GW) 1700 (e.g., an IoT gateway) according to an exemplary embodiment. The exemplary gateway 1700 is, for example... Figure 2One of the gateways (202, ..., 204) of 3, 4, and 5 and / or the GW described with respect to the flowchart of Figure 6. Exemplary gateway 1700 includes a processor 1702 (e.g., CPU), a wireless interface 1704, a network interface 1706 (e.g., a wired or optical interface), an I / O interface 1710, components of hardware components 1708 (e.g., components of circuitry), a memory 1710, and a SIM card 1709 in some embodiments, coupled together via bus 1714. Various components can exchange data and information via bus 1714. Wireless interface 1704 (e.g., an IoT wireless interface) includes a wireless receiver 1726 coupled to one or more receiving antennas 1730, ..., 1732, through which the gateway receives wireless signals, such as IoT broadcast signals from EP devices (e.g., EPIoT devices), and a wireless transmitter 1728 coupled to one or more transmitting antennas 1734, ..., 1736, through which the gateway transmits wireless signals (e.g., IoT downlink signals) to EP devices (e.g., EP IoT devices). In some embodiments, one or more identical antennas are used for both transmission and reception. Network interface 1706 includes receiver 1722 and transmitter 1724. In some embodiments, receiver 1722 and transmitter 1724 are included as part of transceiver 1720. Network interface 1706, for example, couples gateway 1700 to other network nodes and / or the Internet.

[0124] Gateway 1700 also includes multiple input / output devices (speaker 1738, switch 1740, mouse 1742, keyboard / keyboard 1744, and display 1746) which are coupled to I / O interface 1710, thereby allowing various I / O devices to communicate with other components coupled to bus 1714.

[0125] The memory 1712 includes components 1716 of components (e.g., components of software components) and data / information 1718.

[0126] Figure 11 ,include Figure 11A , Figure 11B , Figure 11C and Figure 11D The combination of these components, which are exemplary components of component 1800 according to an exemplary embodiment, includes a combination of part A 1801, part B 1803, part C 1805, and part D 1807, which may be included in an exemplary control server (e.g., an application server). Exemplary components of the component include, for example, those included in... Figure 7 Control server 1400 (e.g., application server), Figure 2In the exemplary control server 218 (e.g., application server) of 3, 4 and 5 and / or the control server (e.g., application server) described with reference to the flowchart of FIG6.

[0127] Components in component 1800 may, and in some embodiments, be implemented entirely in hardware within a processor (e.g., processor 1402), for example, as separate circuits. Components in component 1800 may, and in some embodiments, be implemented entirely in hardware within component 1408, for example, as separate circuits corresponding to different components. In other embodiments, some of these components are implemented, for example, as circuits within processor 1402, while others are implemented, for example, as circuits within component 1408, external to and coupled to processor 1402. As should be appreciated, the level of integration of components on the processor and / or with some components external to the processor may be one of the design choices. Alternatively, in addition to being implemented as circuits, all or some of the components may be implemented in software and stored in memory 1410 of control server 1400, these components controlling the operation of control server 1400 to implement the functions corresponding to the components when the components are executed by the processor (e.g., processor 1402). In some such embodiments, component 1800 of the component is included in memory 1410 as part of component 1430 of the software component. In other embodiments, the various components in component 1800 of the component are implemented as a combination of hardware and software; for example, another circuit outside the processor provides input to the processor, which then operates under software control to perform a portion of the functionality of the component.

[0128] When implemented in software, a component includes code that, when executed by a processor (e.g., processor 1402), configures the processor to perform a function corresponding to the component. In an embodiment where component 1800 is stored in memory 1410, memory 1410 is a computer program product including a computer-readable medium containing code, such as separate code for each component, for causing at least one computer (e.g., processor 1402) to perform the function corresponding to that component.

[0129] Components can be used that are entirely hardware-based or entirely software-based. However, it should be recognized that any combination of software and hardware (e.g., circuit-implemented components) can be used to achieve the function. As should be understood, Figure 11The components shown control and / or configure the control server 1400 or its elements (such as processor 1402) to perform the functions of the corresponding steps shown and / or described and / or illustrated in one or more methods in the flowcharts, signaling diagrams, or any of the accompanying drawings. Therefore, the components 1800 of the components include various parts that perform the functions of one or more corresponding described and / or illustrated steps of the exemplary methods.

[0130] Component 1800 of the component includes component 1802, which is configured to operate a control server to monitor association requests from endpoint (EP) Internet of Things (IoT) devices at the control server. Component 1802 includes component 1804, which is configured to operate the control server to receive association requests at the control server to associate with a gateway and establish an end-to-end (E2E) communication path between the endpoint IoT device and the control server. Component 1804 includes components 1806 and 1808, where component 1806 is configured to operate the control server to receive association requests that include information identifying a requested gateway to be used in the end-to-end communication path, and component 1808 is configured to operate the control server to receive association requests that do not include information identifying a requested gateway to be used in the end-to-end communication path, and wherein the control server is expected to select a gateway.

[0131] Component 1800 of the component also includes components 1810 and 1812. Component 1810 is configured to operate a control server to receive, at the control server, radio frequency (RF) information corresponding to an endpoint IoT device for use with one or more gateways that can be used by the endpoint IoT device, such as SNR information, received signal strength information, etc. Component 1812 is configured at the control server to select an EP IoT device associated with and used for an end-to-end communication path. Component 1812 includes components 1814 and 1816. Component 1814 is configured to select an EP IoT request gateway to be used for the end-to-end communication path, and component 1816 is configured to select a gateway to be used for the end-to-end communication path, for example, based on RF information.

[0132] Component 1800 of the component also includes component 1818 configured to generate an associated response message. Component 1818 includes components 1820, 1822, and 1824, component 1820 being configured to include an acknowledgment indicating that the association request is granted, component 1822 being configured to include information identifying the E2E path (e.g., an end-to-end (E2E) path identifier), and component 1824 being configured to include information identifying the gateway selected by the control server for the E2E communication path (e.g., a gateway identifier).

[0133] Component 1800 of the component also includes component 1826, which is configured as an operation control server to send a generated association response message to the EP IoT device. Component 1826 includes components 1828, 1830, and 1832. Component 1828 is configured as an operation control server to send an acknowledgment indicating that the association request is permitted, component 1830 is configured as an operation control server to send information identifying the end-to-end communication path (e.g., an E2E path identifier), and component 1832 is configured as an operation control server to send information identifying the gateway selected by the control server for the E2E communication path (e.g., a GW identifier).

[0134] Component 1800 of the component also includes component 1836, which is configured as an operation control server to perform transmit power control (TPC) on the EP IoT device for the associated mode. Component 1836 includes components 1838, 1840, 1842, 1844, 1846, 1848, and 1852. Component 1838 is configured as an operation control server to send commands to the EP IoT device to set the EP IoT device to the maximum transmit power level and maximum data rate. Component 1840 is configured as an operation control server to send commands to the EP IoT device to set the EP IoT device to the maximum transmit power level and maximum data rate. The IoT device is configured to transmit training data frames. Component 1842 is configured to operate the control server to monitor and / or receive data (e.g., aggregated data) corresponding to one or more gateways that receive training data frames via it. Component 1844 is configured to determine whether the training data has been successfully received by the selected gateway and to control operation based on that determination. Component 1846 is configured to determine whether the successful reception of an initial training frame is being evaluated and to control operation based on that determination. Component 1848 is configured to determine that the selected gateway is currently unacceptable, for example, in response to determining that the reception of an initial training frame is being evaluated and the selected gateway has failed to successfully receive data. Component 1852 is configured, for example, in response to determining that the training data has not been successfully received by the selected gateway and that this is not an initial training frame, to operate the control server to increase the transmission power level at the EP IoT device to the power level used for the last successful training reception relative to the selected gateway. Component 1836 also includes components 1850 and 1854, wherein component 1850 is configured to determine whether training frames are received by any additional gateway other than the selected gateway and to control operation based on the determination, and component 1854 is configured to operate the control server to send a command to the EP IoT device to reduce the transmission power level at the EP IoT device (e.g., reduce it by 1.5 dB), for example in response to determining that one or more additional gateways other than the selected gateway have received training data.

[0135] Component 1836 also includes components 1856 and 1858, wherein component 1856 is configured to operate the control server to send a command to the EP IoT device to notify the EP IoT device that TPC training has ended and that the current TX power level is the power level for associated pattern data transmission, for example, after component 1852 sends a command to the EP IoT device, and component 1858 is configured to operate the control server to send a command to the EP IoT device to notify the EP IoT device that TPC training has ended and that the current power level is the power level for associated pattern data transmission, for example, in response to a determination that training data was successfully received by the selected gateway but not by the attached gateway.

[0136] Component 1800 of the component also includes components 1860 and 1862, wherein component 1860 is configured as an operations control server to receive forwarded EP IoT device application data, and component 1862 is configured as an operations control server to filter out any received EP IoT application data that is not transmitted via an E2E communication path including a selected gateway. Component 1800 of the component also includes component 1866, which is configured as an operations control server to determine whether an EP IoT device should exit associated mode. Component 1866 includes components 1868, 1870, and 1872. Component 1868 is configured to determine whether the control server has received an associated exit request from the EP IoT device and to perform a control operation based on that determination. Component 1870 is configured to determine whether the control server has determined that continued use of the selected gateway for the E2E path is undesirable and to perform a control operation based on that determination. Component 1872 is configured to determine that the associated mode of the EP IoT device should terminate, for example, in response to any of the following: i) receiving an associated exit request from the EP IoT device or ii) the control server determines that continued use of the selected gateway for the E2E path is undesirable, for example, based on changes (e.g., degradation) in RF report information (e.g., SNR and / or signal strength) corresponding to the EP IoT device and the selected gateway, based on changes in network load between GWs, and / or based on observed reductions in successful recovery information from the EP IoT. Component 1800 of the component also includes component 1874, which is configured to operate the control server to send a message to the EP IoT device to terminate the associated mode and transition the EP IoT device to a non-associated mode, for example, in response to determining that the association with the EP IoT device should be terminated. Component 1874 includes components 1876 and 1878, component 1876 being configured to operate the control server to send an acknowledgment in response to a received association termination request, and component 1878 being configured to operate the control server to send an association termination request to the EP IoT device, for example, in response to the control server determining that it no longer wishes to use the selected gateway and that the control server has determined that the association should be terminated.

[0137] Component 1800 of the component also includes component 1882, which is configured as an operation control server to perform transmit power control (TPC) on EP IoT devices for non-association mode. Component 1882 includes components 1884, 1886, 1888, 1890, 1892, 1896, and 1898. Component 1884 is configured as an operation control server to send a command to the EP IoT device to set the EP IoT device to a maximum transmission power level and a maximum data rate. Component 1886 is configured as an operation control server to send a command to set the EP IoT device to transmit training data frames. Component 1888 is configured as an operation control server to monitor and / or receive data (e.g., aggregated data) corresponding to one or more gateways that receive training data frames via it. Component 1890 is configured to determine whether the training data has been successfully received by at least one gateway and control operations based on this determination. Component 1892 is configured to determine whether the reception preparation evaluation of the initial training frame has been conducted and control operations based on this determination. Component 1896 is configured to determine that the EP IoT device is currently inaccessible, for example, in response to determining that the reception of the initial training frame has been evaluated and that the initial training frame data has not been successfully received by any gateway. Component 1898 is configured as an operation control server to set the EP IoT device to transmit training data frames. The transmission power level at the IoT device is increased to the power level used for the last successful training reception, for example, in response to determining that the training data was not successfully received by any gateway and that this was not the initial training frame.

[0138] Component 1882 also includes components 1894 and 1900, wherein component 1894 is configured to determine whether training frames are received by more than one gateway and control operation based on the determination, and component 1900 is configured to operate the control server to send a command to the EP IoT device to reduce the transmission power level at the EP IoT device (e.g., reduce it by 1.5 dB), for example in response to determining that training data has been successfully received by multiple gateways.

[0139] Component 1882 also includes components 1902 and 1904. Component 1902 is configured to operate the control server to send a command to the EP IoT device to notify the EP IoT device that TPC training has ended and that the current TX power level is the power level to be used for non-associative mode data transmission, for example, after component 1898 sends a command to the EP IoT device. Component 1904 is configured to operate the control server to send a command to the EP IoT device to notify the EP IoT device that TPC training has ended and that the current power level is the power level to be used for non-associative mode data transmission, for example, in response to determining that training data was successfully received by a single gateway but not by any additional gateways.

[0140] Component 1800 of the component also includes component 1906, which is configured as an operation control server to receive forwarded EP IoT device application data, for example, when in a non-associative mode.

[0141] The following further describes various aspects and / or features of some embodiments of the present invention.

[0142] In some embodiments of the associated mode, the endpoint-gateway (EP-GW) association (e.g., virtual association) is imposed on top of the media access control (MAC) layer (e.g., long-distance low-power wide-area network (LPWAN) (LoRaWAN) MAC layer or other protocol MAC layers.

[0143] In some embodiments, higher throughput across the network is achieved in non-associative mode, and endpoint (EP) devices are able to minimize end-to-end (E2E) latency and fragmentation using the maximum available payload size.

[0144] In some embodiments, a transmission power control loop is implemented, for example at the physical (PHY) and MAC layers, which ensures that a device (e.g., an EP device) communicates with a single GW. In some embodiments, implementing a transmission power control loop, for example at the physical (PHY) and MAC layers, increases the possibility, for example, significantly increases the possibility that a device (e.g., an EP device) can communicate with a single GW.

[0145] In some embodiments, the control server (e.g., application server (AS) or network server (NS)) or EP device requests a single route from the EP to the NS / AS via a unique GW request. In some embodiments, multiple EP operating modes are supported, such as associated and unassociated modes. In some embodiments, a security mode is incorporated to exit the GW-associated mode and fall back to the original architecture, such as a LoRaWAN architecture or other protocol architecture. In some embodiments, both associated and unassociated modes support Transmission Power Control (TPC) of the EP device under the control of the control server (e.g., application server).

[0146] In some embodiments, implementations include building blocks for Internet Protocol (IP) connectivity over another protocol (e.g., the LoRaWAN protocol or another protocol).

[0147] Various exemplary Transmit Power Control (TPC) loops implemented according to some embodiments of the present invention provide unique ways to guarantee or significantly increase the possibility of single-route communication from the NS / AS to the device / EP. This approach of using TPC to achieve or increase the possibility of single-route communication is advantageous because it can result in one or more, or all, of the following: i) increased ability to achieve higher data rates, such as up to 22 kbps instead of the 1.1-5 kbps normal operating mode in LoRaWAN; ii) provision of low-cost device location through cell association; iii) minimization of interference between different sensors and ensuring longer battery life for the device (EP device); and iv) guaranteeing or providing backward compatibility, for example, full backward compatibility with existing protocols (e.g., LoRaWAN or another protocol currently in use).

[0148] In some embodiments, under associated mode, exemplary embodiments of the invention allow a device (e.g., an EP device such as an IoT EP device) to be associated with a gateway (GW) in a network (e.g., LoRaWAN or other networks), for example, through virtual association. This approach allows for simpler, non-intrusive device location, simpler device management, and simpler operation and maintenance (O&M) operations, such as firmware updates for devices within the same cell.

[0149] In various embodiments, the associated patterns introduce new procedures, such as new LoRaWAN procedures, which can be implemented in MAC layer applications.

[0150] In some embodiments, in the non-associative mode, exemplary embodiments allow for increased payload size of the device (e.g., an EP device such as an EPIoT device) and utilization of the highest available data rate. In some embodiments, the non-associative mode facilitates similar functionality to that described above with respect to the associated mode, while guaranteeing or providing backward compatibility on the device, such as full backward compatibility.

[0151] In some embodiments, the Transmission Power Control (TPC) method according to the invention makes it possible to ensure that each EP device (e.g., a sensor device) is served by only 1GW to ensure a single path (through a single GW) from the NS / AS to the EP. In some embodiments, the Transmission Power Control (TPC) method according to the invention increases the possibility that an EP device (e.g., a sensor device) is served by only 1GW having a single path (through a single GW) from the NS / AS to the EP.

[0152] In various embodiments, the novel architecture and / or method according to exemplary embodiments includes one or more of the following features. Devices may, and sometimes are, paired with a single GW, such as through virtual pairing. Exemplary TPC methods facilitate locking devices to a single GW. In some embodiments, the TPC algorithm operates only at the application (APP) layer and therefore does not break lower protocols (e.g., LoRaWAN protocol or protocol dependencies of other implementations). In some embodiments, virtualized edge nodes are capable of generating and maintaining E2E unique routes. In some embodiments, virtualized edge nodes include a GW HW and encompass NS functionality.

[0153] The application-level implications of some embodiments will now be described. In some embodiments, the underlying protocol (e.g., LPWAN / LoRaWAN protocol or another protocol) is augmented by custom application-layer commands built on top of a standard MAC layer (e.g., LoRaWAN MAC layer or other protocol MAC layer) to request and initiate IP connectivity over a connection (e.g., LPWAN or LoRaWAN or other protocol connection).

[0154] Examples of MAC commands to add include:

[0155] i)AssociationReq: A command issued by the EP to initiate a unique E2E route between the device and the NS / AS;

[0156] ii)AssociationACK: A command issued by NS to acknowledge the request and send back the request to put the EP on in class C of the device that is always on;

[0157] iii) RouteReq: A command that confirms the EP's Class C capability and transmits at the highest DataRate and highest TX power, and that the EP switches to Class C.

[0158] iv) RouteAck: A command issued by NS to EP

[0159] v)TrainingRoute: N ACKed frames are generated by the EP and all are ACKed by the NS; these frames will be used to generate and guarantee a single route between the EP and the NS through a single GW.

[0160] vi) AssociationExitReq: A command generated by NS or EP to suspend the associated link; and

[0161] vii)AssociationExitACK: EP or NS confirmation will fall back to an unassociated connectivity mode, such as a LoRaWAN / LPWAN unassociated connectivity mode or another protocol unassociated connectivity mode.

[0162] Various MAC-level meanings will now be described. Various embodiments of the invention include unique features built upon standard existing MAC protocols (e.g., standard LPWAN existing MAC protocols). It can be an over-the-air firmware update (FUOTA) over LoRaWAN, SIGFox, NB-IoT, LTE CAt-M, etc. The application requests and ACKs discussed earlier can be expressed as functions of existing MAC commands, such as existing LoRaWAN MAC commands or existing MAC commands of other protocols, such as ADR Req, MACACK, LinkCheck, etc.

[0163] In some embodiments, each of the JoinReq and DATA transmissions will remain compliant with existing protocols (e.g., LPWAN / LoRaWAN). In some embodiments, starting with AssociationReq, those commands are custom commands that enable a unique EE2E connection between the EP and the GW. In some embodiments, each frame is broadcast and there is no GW association, according to existing protocols (e.g., LoRaWAN or other existing protocols). Various features of this invention help maintain a single route between each given EP and the GW. This facilitates the implementation of 6lowpan and other compression mechanisms on top of existing protocols (e.g., on top of LPWAN / LoRaWAN or another implemented protocol). In some embodiments, TrainingRoute is a collection of MAC frames that use Adaptive Bit Rate (ADR) to set the EP with respect to TX to ensure that each EP is received by at most a single GW.

[0164] The various aspects and / or characteristics related to TrainingRoute will now be described. In some embodiments, the TrainingRoute frame is a special AD RACK frame where the EP begins transmission at its maximum power and maximum data rate (e.g., 22kbps) (SF7BW500). Transmitting at the maximum rate ensures that the link budget is always guaranteed to be decreasing as the EP and NS iterate over the TX power, by fixing one of the variables (i.e., DataRate (DR)). Fixing the DR at the highest DR will ensure connectivity at 22kbps, which is suitable for most sensor applications and latency-tolerant applications. In each TrainingRoute frame, the EP and AS exchange data through one or more GWs, and the goal is to have the EP transmit at a sufficiently low TX power so that it can be received and acknowledged by a single GW. This is ensured by using standard ADR commands (e.g., LoRaWAN standard ADR commands or other protocol standard ADR commands) and reducing the TX power from the EP and GW by 1.5dB or another predetermined value on each iteration (uplink frames will tune the EP TX power and DL frames will tune the GW TX power).

[0165] Information about exemplary messages according to some embodiments will now be described. An application server (AS) appends metadata to the message. Exemplary metadata appended by the AS includes, for example, APP_id, device_id, hardware_serial, port, counter, and is_retry.

[0166] EP devices send payloads, for example, Base64 encoded.

[0167] Exemplary metadata attached by NS includes, for example, “call time” – the call duration in milliseconds, “time” – the time the server received the message, “frequency” – the frequency at which messages are sent, “modulation” – the modulation used (e.g., LORA or FSK), “data_rate” – the data rate used – if it is LORA modulation, “bit_rate” – the bit rate used if it is FSK modulation, and “coding_rate” – the encoding rate used.

[0168] Exemplary metadata information attached by the GW includes, for example, "gtw-id" - the gateway's EUI, "timestamp" - the timestamp when the gateway received the message, "time" - the time when the gateway received the message, "channel" - the channel on which the gateway received the message, "rssi" - the signal strength of the received message, "snr" - the signal-to-noise ratio of the received message, "rf_chain" - the radio frequency chain on which the gateway received the message, "latitude" - the latitude of the gateway reported in its status update, "longitude" - the longitude of the gateway, "device_latitude" - the latitude of the EP device, and "device-longitude" - the longitude of the EP device.

[0169] In some embodiments, each time the EP transmits data (payload or MAC command), the EP actually transmits encrypted bytes via modulation (e.g., LoRa modulation following the LoRaWAN standard, or another alternative modulation following the corresponding standard).

[0170] One or more gateways receive the data and convert the payload into, for example, base64 data, and append some RF characteristics, timestamps, their locations, etc. The one or more gateways send this converted payload and the appended metadata to a network server, for example, via a return route including the Internet.

[0171] A network server (NS) receives this data, for example, from one or more gateways and aggregates the traffic for each device (e.g., each EP device). The NS then sends the aggregated data to the AS.

[0172] AS receives data from each device and makes decisions based on the application data.

[0173] In some embodiments of the invention, standard messages are used, but the only difference is that, according to features of some embodiments of the invention, associations are created on top of existing protocols (e.g., LoRaWAN or other protocols). This novel mechanism is not included in existing standards. According to the invention, some embodiments include a unique E2E routing association. An association request message is sent by the EP device and received by two or more GWs, but is intended to establish an association with only one GW. The GW that successfully receives the association request message forwards a reply message along with GW metadata to the network server. The GW metadata includes RF information, such as GW ID information, Received Signal Strength Index (RSSI) information, and SNR information. The NS receives information from the GW that successfully received the association request, for example, aggregating the received information. In some embodiments, the NS decides to use a GW (e.g., GW2) based on RF characteristics and notifies the AS of this decision. In other embodiments, the NS sends the aggregated information to the AS, which decides which GW to use, for example, selecting GW2 based on better RF characteristics. An association ACK is generated and sent back to the EP. Subsequently, the EP's TPC is performed under the guidance of the application server. Training routing data frames are broadcast by the EP, for example, starting from the maximum TX power level at the maximum data rate. If the training routing frame is received by multiple GWs, the AS controls the EP to reduce the TX power, for example, by 1.5 dB, and sends another frame. Eventually, for example, after N frames, the transmitted frame is received by only a single GW (which is the associated GW), and training is terminated.

[0174] In some embodiments, in the non-associated mode, TPC training is still performed in a similar manner to the associated mode, but there is no formal association between the EP and a particular GW. TPC is performed iteratively in reduced increments until the EP communicates with only one GW.

[0175] Note that during the non-associative mode, the target gateway is the gateway that can receive data from the endpoint device at the maximum data rate using the lowest transmission power. In some embodiments, the determination of the target gateway and the minimum transmission power level are performed via a power control training phase, where the endpoint transmission power is successively reduced, for example, until successful communication with only one gateway is maintained. The determined target gateway is typically the gateway with the best wireless communication path to the endpoint device, and in most cases (if not all), the gateway closest to the endpoint device.

[0176] In embodiments where the endpoint device can operate in a so-called associated mode, the endpoint device or control server (e.g., application server) can specify a particular target gateway to use. A gateway can be specified because it is operated by the same service provider and / or for other reasons, such as having a good backhaul connection with the control server (e.g., application server) and / or a good wireless connection with the endpoint device. In associated mode, a power control training phase is used to determine the endpoint device's transmission power level, such as a minimum level or near a minimum level, where data is received by the target gateway at the maximum supported transmission data rate.

[0177] List of exemplary method embodiments numbered as follows:

[0178] Method Example 1. A communication method comprising: receiving at a control server training data (1242 or 1288) wirelessly transmitted by a first endpoint device (e.g., EP device 220) and received by one or more gateways (e.g., GW1 202 and / or GW2 (204)) coupled to the control server (218); determining ((1250) or (1294)) whether the training data was successfully received by at least one gateway other than a target gateway (e.g., if the target gateway is either a selected gateway in an associated mode or a gateway reachable by a minimum power transmission capable of supporting the maximum data transmission rate, if the target gateway is a single gateway capable of supporting the maximum data transmission rate at the minimum power level, if multiple gateways successfully received the training data at the maximum data rate, then if the identity of the target gateway is unknown, then the training data was successfully received by an additional gateway, therefore... (for which it has not yet been identified by a power-off operation); when it is determined ((1250) or (1294)) that the training data has been successfully received by at least one gateway other than the target gateway, send a command ((1254) or (1300)) to the first endpoint device to reduce the transmission power level (e.g., reduce by a predetermined amount, such as 1.5 dB or some other amount, such as 2 dB); and when it is determined ((1250) or (1294)) that the training data has not been successfully received by at least one gateway other than the target gateway, send a command ((1258) or (1304)) to the first endpoint device to indicate that the training (e.g., transmission power control (TPC) training) has ended.

[0179] Method Example 2. The method of Method Example 1 further includes performing the following steps before determining whether the training data ((1250) or (1294)) has been successfully received by at least one gateway other than the target gateway: the operation control server (218) sends a command ((1238) or (1284)) to the first endpoint device (e.g., EP device 220) to transmit the training data at the maximum transmission power level.

[0180] Method Example 3. The method of Method Example 2, wherein the command to the first endpoint also commands the endpoint to use the maximum data transmission rate.

[0181] Method Example 4. The method of Method Example 2 further includes performing the following steps before determining whether the training data ((1250) or (1294)) has been successfully received by at least one gateway other than the target gateway: determining (1244) that the training data has been successfully received by the selected gateway.

[0182] Method Example 5. The method of Method Example 1, wherein, given the current location of the first endpoint device, the target gateway is a single gateway in the communication system capable of receiving data at the maximum data rate using the lowest transmission power level that can successfully support the maximum data rate.

[0183] Method Example 6. The method of Method Example 1, wherein a plurality of gateways are capable of receiving data transmitted by a first endpoint device at a maximum transmission rate and a maximum transmission power level, and wherein the target gateway is a single gateway among the plurality of gateways capable of receiving data transmitted by the first endpoint device at a maximum transmission rate and a determined reduced transmission power level for subsequent application data transmission.

[0184] Method Example 7. The method of Method Example 6, wherein the subsequent application data transmission is a sensor measurement report.

[0185] Method Example 8. The method of Method Example 6, wherein the target gateway is a single remaining gateway after one or more iterations of transmission power control training, which eliminates other gateways among a plurality of gateways.

[0186] Method Example 9. The method of Method Example 1, wherein the target gateway is a gateway specified by the first endpoint device or the control server (application server) when the first endpoint device is to operate in the associated operating mode.

[0187] Method Example 10. The method of Method Example 1 further includes: selecting (1212) a gateway to be used for communication from the first endpoint device to the control server at the control server, said selected gateway being a target gateway.

[0188] Method Example 11. The method of Method Example 10 further includes: receiving (1204, 1206 or 1208) an association request from the first endpoint device at the control server before selecting (1212) a gateway to be used for communication from the first endpoint device to the control server (218).

[0189] Method Example 12. The method of Method Example 11, wherein the association request (see step 1206) indicates that the requested gateway is to be used for communication with the control server.

[0190] Method Example 13. The method of Method Example 1, wherein the method includes determining ((1250) or (1294)) that training data has been successfully received by at least one gateway other than the target gateway and sending ((1254)) or (1300)) a command to reduce the transmission power level to a first endpoint device, the method further includes: receiving at a control server training data wirelessly transmitted by the first endpoint device at a reduced power level and received by one or more gateways (e.g., GW1102 and / or GW2 (204)) coupled to the control server (218) (second iteration of step 1242 or step 1288); determining (through the second iteration of step 1244 or 1290) whether the training data transmitted by the first endpoint device at a reduced power level has been successfully received by the target gateway.

[0191] Method Example 14. The method of Method Example 13 further includes: in response to determining that training data transmitted by the first endpoint at a reduced power level was not successfully received by the target gateway (e.g., the negative determination in step 1244 or 1290 during the second iteration of the loop), sending a command ((1552) or 1298)) to the first endpoint device to increase the transmission power level.

[0192] Method Example 15. The method of Method Example 14, wherein the command to increase the transmission power level to the endpoint device further instructs the endpoint device to exit the power control training operation phase, or the method further includes: the control server sending an operation command to the endpoint device to exit the power control training phase.

[0193] Method Example 16. The method of Method Example 13 further includes: in response to determining that training data transmitted by the first endpoint device at a reduced power level has been successfully received by the target gateway, determining (step (1250) or (1294), for example, performed during the second iteration of the loop) whether the training data transmitted at a reduced power level has been successfully received by at least one gateway other than the target gateway.

[0194] Method Example 17. The method of Method Example 16 further includes: in response to determining that training data transmitted at a reduced power level has been successfully received by at least one gateway other than the target gateway, sending a command (1254 or 1300) to the endpoint device to reduce the transmission power level.

[0195] Method Example 18. The method of Method Example 16 further includes: in response to determining that training data transmitted at a reduced power level has not been successfully received by at least one gateway other than the target gateway, sending (1258 or 1304) a command to the endpoint device indicating that the current transmission power level will be used for data transmission.

[0196] Method Example 19. The method of Method Example 18, wherein the command indicating to the endpoint device that the current transmission power level will be used for data transmission also indicates that the transmission power control training operation mode has ended.

[0197] Method Example 20. The method of Method Example 1, wherein the first endpoint device is an Internet of Things (IoT) endpoint device.

[0198] Method Example 21. The method of Method Example 20, wherein the one or more gateways are IoT gateways.

[0199] List of exemplary device embodiments:

[0200] Device Embodiment 1. A control server (218 or 1400) comprising: a processor (1402) configured to: operate the control server to receive training data (1242 or 1288) wirelessly transmitted by a first endpoint device (e.g., EP device 220) and received by one or more gateways (e.g., GW1 202 and / or GW2 (204)) coupled to the control server (218); determine ((1250) or (1294)) whether the training data was successfully received by at least one gateway other than a target gateway (e.g., if the target gateway is either a selected gateway in an associated mode or a gateway reachable by a minimum power transmission capable of supporting the maximum data transmission rate, and if the target gateway is a single gateway capable of supporting the maximum data transmission rate at the minimum power level, and if multiple gateways successfully received the training data at the maximum data rate, then if the identity of the target gateway is unknown, then the training data was successfully received by an additional gateway, therefore... (for which it has not yet been identified by a power-off operation); when it is determined ((1250) or (1294)) that the training data has been successfully received by at least one gateway other than the target gateway, send a command ((1254) or (1300)) to the first endpoint device to reduce the transmission power level (e.g., reduce by a predetermined amount, such as 1.5 dB or some other amount, such as 2 dB); and when it is determined ((1250) or (1294)) that the training data has not been successfully received by at least one gateway other than the target gateway, send a command ((1258) or (1304)) to the first endpoint device to indicate that the training (e.g., transmission power control (TPC) training) has ended.

[0201] Device Embodiment 2. The control server of Device Embodiment 1, wherein the processor is further configured to: before determining whether the training data has been successfully received by at least one gateway other than the target gateway, the operation control server (218) sends a command ((1238) or (1284)) to the first endpoint device (e.g., EP device 220) to transmit the training data at the maximum transmission power level.

[0202] Device Embodiment 3. The control server of Device Embodiment 2, wherein the command to the first endpoint also commands the endpoint to use the maximum data transmission rate.

[0203] Device Embodiment 4. The control server of Device Embodiment 2, wherein the processor determines (1244) that the training data has been successfully received by the selected gateway before determining ((1250) or (1294)) whether the training data has been successfully received by at least one gateway other than the target gateway.

[0204] Device Embodiment 5. The control server of Device Embodiment 1, wherein, given the current location of the first endpoint device, the target gateway is a single gateway in the communication system capable of receiving data at the maximum data rate using the lowest transmission power level that can successfully support the maximum data rate.

[0205] Device Embodiment 6. The control server of Device Embodiment 1, wherein a plurality of gateways are capable of receiving data transmitted by a first endpoint device at a maximum transmission rate and a maximum transmission power level, and wherein the target gateway is a single gateway among the plurality of gateways capable of receiving data transmitted by the first endpoint device at a maximum transmission rate and a determined reduced transmission power level for subsequent application data transmission.

[0206] Device Embodiment 7. The control server of Device Embodiment 6, wherein the subsequent application data transmission is a sensor measurement report.

[0207] Device Embodiment 8. The control server of Device Embodiment 6, wherein the target gateway is a single remaining gateway after one or more iterations of transmission power control training, which eliminates other gateways among multiple gateways.

[0208] Device Embodiment 9. The control server of Device Embodiment 1, wherein the target gateway is the gateway specified by the first endpoint device or the control server (application server) when the first endpoint device wants to operate in the associated operating mode.

[0209] Device Embodiment 10. The control server of Device Embodiment 1, wherein the processor is further configured to: select (1212) a gateway to be used for communication from the first endpoint device to the control server at the control server, the selected gateway being a target gateway.

[0210] Device Embodiment 11. The control server of Device Embodiment 10, wherein the processor is further configured to receive (1204, 1206 or 1208) an association request from the first endpoint device at the control server before selecting (1212) a gateway to be used for communication from the first endpoint device to the control server (218).

[0211] Device Embodiment 12. The control server of Device Embodiment 11, wherein the association request (see step 1206) indicates that the requested gateway is to be used for communication with the control server.

[0212] Device Embodiment 13. The control server of Device Embodiment 1, wherein the processor determines ((1250) or (1294)) that training data has been successfully received by at least one gateway other than the target gateway and sends ((1254)) or (1300)) a command to reduce the transmission power level to the first endpoint device, and wherein the processor is further configured to: operate the control server to receive at the control server training data wirelessly transmitted by the first endpoint device at a reduced power level and received by one or more gateways (e.g., GW1102 and / or GW2 (204)) coupled to the control server (second iteration of step 1242 or step 1288); determine (through the second iteration of step 1244 or 1290) whether the training data transmitted by the first endpoint device at a reduced power level has been successfully received by the target gateway.

[0213] Device Embodiment 14. The control server of Device Embodiment 13, wherein the processor is further configured to: in response to determining that training data transmitted by the first endpoint at a reduced power level was not successfully received by the target gateway (e.g., a negative determination in step 1244 or 1290 during the second iteration of the loop), operate the control server to send a command to the first endpoint device ((1552) or 1298)) to increase the transmission power level.

[0214] Device Embodiment 15. The control server of Device Embodiment 14, wherein the command to increase the transmission power level to the endpoint device further instructs the endpoint device to exit the power control training operation phase, or the method further includes the control server sending an operation command to the endpoint device to exit the power control training phase.

[0215] Device Embodiment 16. The control server of Device Embodiment 13, wherein the processor is further configured to: in response to determining that training data transmitted by the first endpoint device at a reduced power level has been successfully received by the target gateway, determine (step (1250) or (1294), for example, performed during the second iteration of the loop) whether the training data transmitted at a reduced power level has been successfully received by at least one gateway other than the target gateway.

[0216] Device Embodiment 17. The control server of Device Embodiment 16, wherein the processor is further configured to: in response to determining that training data transmitted at a reduced power level has been successfully received by at least one gateway other than the target gateway, the operation control server sends a command (1254 or 1300) to the endpoint device to reduce the transmission power level.

[0217] Device Embodiment 18. The control server of Device Embodiment 16, wherein the processor is further configured to, in response to determining that training data transmitted at a reduced power level has not been successfully received by at least one gateway other than the target gateway, send (1258 or 1304) a command to the endpoint device indicating that the current transmission power level will be used for data transmission.

[0218] Device Embodiment 19. The control server of Device Embodiment 18, wherein the command indicating to the endpoint device the current transmission power level to be used for data transmission also indicates that the transmission power control training operation mode has ended.

[0219] Device Example 20. The control server of Device Example 1, wherein the first endpoint device is an Internet of Things (IoT) endpoint device.

[0220] Device Embodiment 21. The control server of Device Embodiment 20, wherein one or more gateways are IoT gateways.

[0221] List of exemplary non-transitory computer-readable medium embodiments:

[0222] Example 1 of a non-transitory computer-readable medium: A non-transitory computer-readable medium (1410) includes computer-executable instructions that, when executed by a processor (1402) of a control server (1400), cause the control server (1400) to perform the following steps: receiving training data (1242 or 1288) wirelessly transmitted by a first endpoint device (e.g., EP device 220) and received by one or more gateways (e.g., GW1 202 and / or GW2 (204)) coupled to the control server (218); determining ((1250) or (1294)) whether the training data was successfully received by at least one gateway other than the target gateway (e.g., if the target gateway is either the selected gateway in an associated mode or a gateway reachable by the minimum power transmission that can support the maximum data transmission rate, and if the target gateway is a single gateway that can support the maximum data transmission rate at the minimum power level, and if multiple gateways successfully received the training data at the maximum data rate, then if the identity of the target gateway is unknown, then the training data was successfully received by the attached gateway, because... (for which it has not yet been identified by a power-off operation); when it is determined ((1250) or (1294)) that the training data has been successfully received by at least one gateway other than the target gateway, send a command ((1254) or (1300)) to the first endpoint device to reduce the transmission power level (e.g., reduce by a predetermined amount, such as 1.5 dB or some other amount, such as 2 dB); and when it is determined ((1250) or (1294)) that the training data has not been successfully received by at least one gateway other than the target gateway, send a command ((1258) or (1304)) to the first endpoint device to indicate that the training (e.g., transmission power control (TPC) training) has ended.

[0223] Various embodiments are directed to devices, such as control servers (e.g., application servers (AS), network servers), gateways (e.g., IoT gateways), endpoint (EP) devices (e.g., EP IoT devices, such as EP IoT sensors or application devices), user equipment (e.g., user equipment (UE) devices), base stations (e.g., cellular base stations such as eNB, gNB, or ng-eNB (macro cell base stations and small cell base stations)), non-cellular network access points (e.g., WiFi APs, network nodes, mobility management entities (MME), home subscriber servers (HSS), wireless local area network controllers (WLC)), gateways (e.g., S-GW, P-GW, S-GW / P-GW), AMF devices, servers, customer site equipment, cable systems, non-cellular networks, cellular networks, service management systems, network nodes, gateways, cable front-ends / hubs, network monitoring nodes / servers, cluster controllers, cloud nodes, production nodes, cloud service servers, and / or network equipment devices. Various embodiments also relate to methods, such as controlling and / or operating methods that include: a control server (e.g., an application server (AS), a network server), a gateway (e.g., an IoT gateway), an endpoint (EP) device (e.g., an EP IoT device, such as an EP IoT sensor) or application device user equipment (e.g., user equipment (UE) equipment), a base station (e.g., a cellular base station such as an eNB, gNB, or ng-eNB (macrocell base station and small cell base station)), a non-cellular network access point (e.g., a WiFi AP), a network node, a mobility management entity (MME), a home subscriber server (HSS), a wireless local area network controller (WLC), a gateway (e.g., an S-GW, P-GW, S-GW / P-GW), a user equipment, a base station, a gateway, a server, a wired network, a cloud network, a node, a server, a cloud service server, customer site equipment equipment, a controller, a network monitoring node / server, and / or cable or network equipment equipment. Various embodiments also relate to methods, such as methods that control and / or operate a communication system including an EP device (e.g., an IoT EP device), a gateway, a network server, and a control server (e.g., an application server). Various embodiments also relate to methods, such as operating a control server to associate an EP device with a specific gateway, establishing an E2E communication path between the EP device and the control server, controlling the TX power level at the EP device and the gateway, and managing loading and interference. Various embodiments also relate to machines, such as computer-readable media, such as ROM, RAM, CD, hard disk, etc., which include machine-readable instructions for controlling the machine to implement one or more steps of the method. The computer-readable medium is, for example, a non-transitory computer-readable medium.

[0224] Non-associative mode can be implemented and in various embodiments without requiring the end-user device to include any additional functionality, such as hardware functionality or capabilities beyond those typically included in standard EP devices. This is because in non-associative mode, control (e.g., intelligence for implementing the mode) is placed in and implemented on a network server (NS or controller), allowing the EP device to obtain the benefits that non-associative mode may offer without requiring changes to the EP device.

[0225] It should be understood that the specific order or hierarchy of steps in the disclosed processes and methods is an example of exemplary methods. Based on design preferences, it is understood that the specific order or hierarchy of steps in the processes and methods can be rearranged while remaining within the scope of this disclosure. The appended method claims present the elements of each step in an exemplary order and are not intended to limit one to the presented specific order or hierarchy. In some embodiments, one or more processors are used to perform one or more steps of each of the methods.

[0226] In various embodiments, each step or element of the method is implemented using one or more processors. In some embodiments, each element is a step implemented using a hardware circuit system.

[0227] In various embodiments, the nodes and / or elements described herein are implemented using one or more components to perform steps corresponding to one or more methods, such as message receiving, message generation, signal generation, signal processing, sending, comparison, determination, and / or transmission steps. Therefore, in some embodiments, various features are implemented using components, or in some embodiments using logic (such as, for example, logic circuits). Such components can be implemented using software, hardware, or a combination of software and hardware. Many of the above-described methods or method steps can be implemented using machine-executable instructions (such as software), which are included in a machine-readable medium (such as a memory device, e.g., RAM, floppy disk, etc.) to control a machine (e.g., a general-purpose computer with or without additional hardware) to implement, for example, all or part of the above-described methods in one or more nodes. Thus, among other things, various embodiments are directed to machine-readable media, such as non-transitory computer-readable media, including machine-executable instructions for causing a machine (e.g., a processor and associated hardware) to perform one or more of the steps of the above-described methods. Some embodiments target devices such as control servers (e.g., application servers (AS), network servers), gateways (e.g., IoT gateways), endpoint (EP) devices (e.g., EP IoT devices, such as EP IoT sensors or application devices), user equipment (e.g., user equipment (UE) devices), base stations (e.g., NB-IoT-enabled cellular base stations (macro cell base stations or small cell base stations) such as eNB, gNB, or ng-eNB), NB-IoT-enabled non-cellular network access points (e.g., NB-IoT-enabled WiFi APs), network nodes, mobility management entity (MME) nodes, home subscriber servers (HSS), wireless local area network controllers (WLC), and gateways (e.g., S-GW, P-GW, S-GW / P-GW, etc.), said devices including processors configured to implement one, more, or all of the steps of one or more methods of the present invention.

[0228] In some embodiments, one or more devices (e.g., control servers (such as application servers (AS), network servers), gateways (e.g., IoT gateways), endpoint (EP) devices (such as EP IoT devices, such as EP IoT sensors or application devices), user equipment (such as user equipment (UE) devices), base stations (e.g., NB-IoT-enabled cellular base stations (macro cell base stations or small cell base stations) such as eNB, gNB, or ng-eNB), and NB-IoT-enabled non-cellular network access points (e.g., NB-IoT-enabled WiFi) are included. One or more processors (e.g., CPUs) of an AP, network node, Mobility Management Entity (MME) node, Home Subscriber Server (HSS), Wireless LAN Controller (WLC), gateway (e.g., S-GW, P-GW, S-GW / P-GW, etc.) are configured to perform steps described as being performed by a communication node (e.g., a controller). The processor configuration can be achieved by using one or more components (e.g., software components) to control the processor configuration and / or by including hardware (e.g., hardware components) within the processor to perform the described steps and / or control the processor configuration. Thus, some, but not all, embodiments are directed to devices such as communication nodes (e.g., control servers such as application servers (AS), network servers), gateways (e.g., IoT gateways), endpoint (EP) devices (e.g., EP IoT devices, such as EP IoT sensors or application devices)), user equipment (e.g., user equipment (UE) devices), base stations (e.g., NB-IoT-enabled cellular base stations (macrocell base stations or small cell base stations) such as eNB, gNB, or ng-eNB), and NB-IoT-enabled non-cellular network access points (e.g., NB-IoT-enabled WiFi). AP), network node, mobility management entity (MME) node, home subscriber server (HSS), wireless local area network controller (WLC), gateway (e.g., S-GW, P-GW, S-GW / P-GW, etc.), including components corresponding to each of one or more of the steps of the various methods described in which the device including the processor performs them.In some, but not all, embodiments, devices (e.g., control servers (such as application servers (AS), network servers), gateways (such as IoT gateways), endpoint (EP) devices (such as EP IoT devices, e.g., EP IoT sensors or application devices), user equipment (such as user equipment (UE) devices), base stations (e.g., NB-IoT-enabled cellular base stations (macrocell base stations or small cell base stations) such as eNB, gNB, or ng-eNB), NB-IoT-enabled non-cellular network access points (e.g., NB-IoT-enabled WiFi APs), network nodes, mobility management entity (MME) nodes, home subscriber servers (HSS), wireless local area network controllers (WLC), gateways (e.g., S-GW, P-GW, S-GW / P-GW, etc.)) include controllers corresponding to each step of the various methods performed by the devices, including processors. These components can be implemented using software and / or hardware.

[0229] Some embodiments relate to computer program products that include computer-readable media, such as non-transitory computer-readable media, including code for enabling a computer or multiple computers to perform various functions, steps, actions, and / or operations (e.g., one or more of the steps described above).

[0230] Depending on the embodiment, the computer program product may and sometimes does include different code for each step to be performed. Therefore, the computer program product may and sometimes does include code for each individual step of a method, such as a method for controlling a controller or node. The code may be in the form of machine (e.g., computer) executable instructions stored on a computer-readable medium (e.g., a non-transitory computer-readable medium, such as RAM (Random Access Memory), ROM (Read-Only Memory), or other types of storage devices). In addition to the computer program product, some embodiments are also directed to a processor configured to implement one or more of the various functions, steps, actions, and / or operations of one or more of the methods described above. Thus, some embodiments are directed to a processor (e.g., a CPU) configured to implement some or all of the steps of the methods described herein. The processor can be used in, for example, communication devices (e.g., control servers (such as application servers (AS), network servers), gateways (such as IoT gateways), endpoint (EP) devices (such as EP IoT devices, e.g., EP IoT sensors or application devices 3)), user equipment (such as user equipment (UE) devices), base stations (e.g., NB-IoT-enabled cellular base stations (macro cell base stations or small cell base stations) such as eNB, gNB, or ng-eNB), NB-IoT-enabled non-cellular network access points (e.g., NB-IoT-enabled WiFi APs), network nodes, mobility management entity (MME) nodes, home subscriber servers (HSS), wireless local area network controllers (WLC), gateways (e.g., S-GW, P-GW, S-GW / P-GW), or other devices described in this application. In some embodiments, the component is implemented as a hardware device; in such embodiments, the component is a hardware component. In other embodiments, the component can be implemented as software, e.g., a processor or a set of computer-executable instructions. Depending on the embodiment, a component may be all hardware components, all software components, a combination of hardware and / or software, or in some embodiments, some components may be hardware components while others may be software components.

[0231] In view of the foregoing description, many additional variations of the methods and apparatus of the various embodiments described above will be apparent to those skilled in the art. Such variations should be considered within the scope of the invention. In view of the foregoing description and the following claims, many additional embodiments within the scope of the invention will be apparent to those skilled in the art. Such variations are considered within the scope of the invention.

Claims

1. A communication method, the method comprising: Training data is received at the control server from the first endpoint device via wireless transmission and from one or more gateways coupled to the control server. Determine whether the training data has been successfully received by at least one gateway other than the target gateway; When it is determined that the training data has been successfully received by at least one gateway other than the target gateway, a command to reduce the transmission power level is sent to the first endpoint device. as well as When it is determined that the training data has not been successfully received by at least one gateway other than the target gateway, a command indicating that the training has ended is sent to the first endpoint device.

2. The method of claim 1, further comprising, before determining whether the training data has been successfully received by at least one gateway other than the target gateway, performing the following steps: The operation control server sends a command to the first endpoint device to transmit training data at the maximum transmission power level.

3. The method of claim 2, wherein the command to the first endpoint device further commands the first endpoint device to use a maximum data transmission rate.

4. The method of claim 1, wherein, Given the current location of the first endpoint device, the target gateway is a single gateway in the communication system that can receive data at the maximum data rate using the lowest transmission power level that can successfully support the maximum data rate.

5. The method of claim 1, wherein the target gateway is a gateway specified by the first endpoint device or the control server when the first endpoint device is to operate in the associated operating mode.

6. The method of claim 1, wherein the method includes determining that training data has been successfully received by at least one gateway other than the target gateway and sending a command to the first endpoint device to reduce the transmission power level, the method further comprising: Training data is received at the control server from the first endpoint device via wireless transmission at a reduced power level and from one or more gateways coupled to the control server. as well as Determine whether the training data transmitted by the first endpoint device at a reduced power level was successfully received by the target gateway.

7. The method of claim 6, further comprising: In response to the determination that the training data transmitted by the first endpoint device at a reduced power level was not successfully received by the target gateway, a command to increase the transmission power level is sent to the first endpoint device.

8. The method of claim 6, further comprising: In response to determining that the training data transmitted by the first endpoint device at a reduced power level was successfully received by the target gateway, it is determined whether the training data transmitted at a reduced power level was successfully received by at least one gateway other than the target gateway.

9. The method of claim 6, further comprising: In response to the determination that the training data transmitted at a reduced power level was successfully received by at least one gateway other than the target gateway, Send a command to the first endpoint device to reduce the transmission power level.

10. The method of claim 6, further comprising, in response to determining that training data transmitted at a reduced power level has not been successfully received by at least one gateway other than the target gateway, sending a command to the first endpoint device indicating that the current transmission power level will be used for data transmission.

11. The method of claim 10, wherein the command indicating to the first endpoint device that the current transmission power level will be used for data transmission also indicates that the transmission power control training operation mode has ended.

12. The method of claim 1, wherein the first endpoint device is an Internet of Things (IoT) endpoint device, and wherein the one or more gateways are IoT gateways.

13. A control server, comprising: The processor is configured as follows: The operation control server is configured to receive training data wirelessly transmitted by the first endpoint device and received by one or more gateways coupled to the control server at the control server. Determine whether the training data has been successfully received by at least one gateway other than the target gateway; When it is determined that the training data has been successfully received by at least one gateway other than the target gateway, the operation control server sends a command to the first endpoint device to reduce the transmission power level. as well as When it is determined that the training data has not been successfully received by at least one gateway other than the target gateway, the operation control server sends a command to the first endpoint device indicating that the training has ended.

14. The control server of claim 13, wherein the processor determines that the training data has been successfully received by at least one gateway other than the target gateway, and operates the control server to send a command to the first endpoint device to reduce the transmission power level, and wherein the processor is further configured to: The operation control server is configured to receive training data wirelessly transmitted at a reduced power level by a first endpoint device and received by one or more gateways coupled to the control server; and Determine whether the training data transmitted by the first endpoint device at a reduced power level was successfully received by the target gateway.

15. The control server of claim 14, wherein the processor is further configured to: In response to the determination that the training data transmitted by the first endpoint device at a reduced power level was not successfully received by the target gateway, the operation control server sends a command to the first endpoint device to increase the transmission power level.

16. The control server of claim 14, wherein the processor is further configured to: In response to determining that the training data transmitted by the first endpoint device at a reduced power level was successfully received by the target gateway, it is determined whether the training data transmitted at a reduced power level was successfully received by at least one gateway other than the target gateway.

17. The control server of claim 16, wherein the processor is further configured to: In response to the determination that the training data transmitted at a reduced power level was successfully received by at least one gateway other than the target gateway, The operation control server sends a command to the first endpoint device to reduce the transmission power level.

18. The control server of claim 16, wherein the processor is further configured to, in response to determining that training data transmitted at a reduced power level has not been successfully received by at least one gateway other than the target gateway, send a command to the first endpoint device indicating that the current transmission power level will be used for data transmission.

19. The control server of claim 18, wherein the command indicating to the first endpoint device that the current transmission power level will be used for data transmission also indicates that the transmission power control training operation mode has ended.

20. A non-transitory computer-readable medium comprising computer-executable instructions that, when executed by a processor of a control server, cause the control server to perform the following steps: Training data is received at the control server from the first endpoint device via wireless transmission and from one or more gateways coupled to the control server. Determine whether the training data has been successfully received by at least one gateway other than the target gateway; When it is determined that the training data has been successfully received by at least one gateway other than the target gateway, a command to reduce the transmission power level is sent to the first endpoint device. as well as When it is determined that the training data has not been successfully received by at least one gateway other than the target gateway, a command indicating that the training has ended is sent to the first endpoint device.

Images