KR102162855B1 - Long range join server and information processing method therefor - Google Patents

Abstract

The disclosed LoRa join server device and a LoRa network server device constituting a LoRa network with a plurality of LoRa terminal devices include a communication unit that transmits and receives data to and from a LoRa terminal device and a LoRa join server device, and a first requesting join among a plurality of LoRa terminal devices. A data storage unit that stores a profile including information on the allocation status of LoRa services to a LoRa terminal device, and a control unit, wherein the control unit receives downlink data to be transmitted to the first LoRa terminal device by the communication unit. If the downlink data is counted, the downlink data is counted for the first time after checking whether the LoRa service is temporarily allocated to the first LoRa terminal device based on the profile, the downlink count received from the communication unit from the LoRa join server device After increasing the value by a preset value, the communication unit is controlled to include in the downlink data and transmit it to the first LoRa terminal device.

Description

LoRa join server device and its information processing method {LONG RANGE JOIN SERVER AND INFORMATION PROCESSING METHOD THEREFOR}

The present invention relates to a LoRa (Long Range) terminal device, a LoRa join server device, a LoRa network server device constituting a LoRa network, and an information processing method performed by the LoRa network server device.

The Internet of Things (IoT) refers to intelligent technologies and services that connect various objects through networks such as the Internet so that information between people and objects and objects and objects can communicate with each other. The IoT is a more advanced technology compared to existing wired/wireless communication, and can be used in various fields such as unmanned meters, unmanned vending machines, intelligent transportation services, and real-time monitoring medical services. According to the research results and analysis of IoT devices, the number of IoT access devices is expected to increase to about 30 billion by 2025, and accordingly, research on IoT application is being actively conducted.

Conventionally, Wi-Fi, Bluetooth, and the like have been used as a communication method for constructing such an IoT system. However, such methods have a disadvantage that communication is possible only in a relatively short distance, and thus, is not suitable for an IoT system that needs to cover a wide range. The communication method for the IoT needs to be designed to cover a wide range as described above, but also to reduce power consumption for IoT devices in which charging restrictions and continuous power supply are often required. Accordingly, a demand for so-called Low Power Wide-Area (LPWA) has emerged. LPWA is a collective term for IoT network technology specialized for small data transmission, which allows low-speed transmission of 1 kbps or less, has wide area coverage and low power consumption.

The LoRa (Long Range) network is one of these LPWA networks. In general, the IoT system does not require high-speed real-time data transmission and reception. Power consumption is reduced by adopting a downlink asymmetric transmission method. The LoRa network is an IoT-only network that can accommodate low-performance devices with small batteries for the implementation of the Internet of Small Things, and can provide coverage with a speed of 293bps to 5.4kbps and a sensitivity of -143dbm. In addition, due to the limitations of data transmission and reception as described above, the LoRa network terminal device cannot receive the data transmitted from the LoRa network base station device only after a certain period of time has elapsed after transmitting the transmission data to the LoRa network base station device. have.

The LoRa network can be composed of a LoRa terminal device, a LoRa base station device, and a LoRa network server device.

In such a LoRa network, a LoRa network server device that will be in charge of LoRa service is assigned to each LoRa terminal device, and if a failure occurs in the first LoRa network server device assigned to a random LoRa terminal device, the second LoRa network server device without a failure is a random LoRa device. It is allocated to the terminal device, and when the failure is recovered, the original first LoRa network server device is allocated to the random LoRa terminal device again.

In this way, in case a failure occurs, the LoRa network server device, which is in charge of LoRa service to any LoRa terminal device, is operated by dualizing the main allocation state and the temporary allocation state, and the LoRa network server device is responsible for call processing and LoRa. It is responsible for the transfer processing of downlink data to be transmitted to the terminal equipment and uplink data transmitted from the LoRa terminal equipment.

Meanwhile, in a LoRa network, uplink data is counted by a LoRa terminal device, downlink data is counted by a LoRa network server device, and the counted uplink/downlink count values are transmitted by including in the header of the data. Here, the LoRa terminal device and the LoRa network server device normally process only when the count values included in the uplink/downlink data are sequential.

The 2nd LoRa network server device is downlinked in a situation where the LoRa service for the LoRa terminal device is temporarily allocated to the 2nd LoRa network server device due to a failure in the first LoRa network server device, which is mainly assigned the LoRa service for the LoRa terminal device. In the case of downlink transmission processing of downlink data including the coefficient value for the data to the LoRa terminal device, the LoRa terminal device is transmitted from the second LoRa network server device than the downlink count value received from the first LoRa network server device. The downlink coefficient value may be smaller. In this way, when the downlink count values are not sequential, the LoRa terminal device determines that it is an abnormal situation even though it is a normal situation and does not transmit an Ack message. Then, there is a problem in that the transmission side of the downlink message performs retransmission of the downlink message as a response (Ack) message is not received.

In addition, in a situation in which the failure of the first LoRa network server device is recovered and the LoRa service for the LoRa terminal device is mainly allocated to the first LoRa network server device, the LoRa terminal device transmits uplink data including a count value for the uplink data. It can be transmitted to the first LoRa network server device. However, when the count value for the uplink data exceeds the preset maximum value, it is counted again from "1", so the count value of the uplink data processed before the failure occurred by the first LoRa network server device is currently A situation that is larger than the coefficient value included in the uplink data of may occur. As described above, when the uplink count values are not sequential, the first LoRa network server device determines that the uplink data is an abnormal condition even though it is a normal condition, and thus discards the corresponding uplink data without transmitting processing.

Korean Patent Application Publication No. 10-2018-0025613 (published on Mar. 9, 2018)

According to an embodiment, there is provided a LoRa network server apparatus and a method for processing the information so that retransmission of a downlink message does not occur due to non-sequential generation of downlink coefficient values.

In addition, there is provided a LoRa network server apparatus and a method for processing the information so that the uplink data discard processing does not occur due to out-of-order generation of uplink coefficient values.

The problem to be solved of the present invention is not limited to those mentioned above, and another problem to be solved that is not mentioned will be clearly understood by those of ordinary skill in the art from the following description.

According to a first aspect, a LoRa join server device and a LoRa network server device constituting a LoRa network with a plurality of LoRa terminal devices include a communication unit for transmitting and receiving data with the LoRa terminal device and the LoRa join server device, and the plurality of LoRa terminal devices. Includes a data storage unit for storing a profile including information on the allocation status of LoRa services to the first LoRa terminal device requesting join among the terminal devices, and a control unit, wherein the control unit transmits to the first LoRa terminal device When downlink data to be performed is received, the downlink data is counted, and if the downlink data is counted for the first time after checking whether the LoRa service is temporarily allocated to the first LoRa terminal device based on the profile, the LoRa The communication unit controls the communication unit so that the downlink coefficient value received through the communication unit from the join server device is increased by a preset value and then included in the downlink data and transmitted to the first LoRa terminal device.

According to a second aspect, a LoRa join server device and a LoRa network server device constituting a LoRa network with a plurality of LoRa terminal devices include a communication unit that transmits and receives data with the LoRa terminal device and the LoRa join server device, and the plurality of LoRa A data storage unit for storing a profile including information on the allocation status of LoRa services to the first LoRa terminal device that requested join among the terminal devices, and a control unit, wherein the control unit is transmitted from the first LoRa terminal device. The uplink data is received by the communication unit, and after confirming whether to temporarily allocate a LoRa service to the first LoRa terminal device based on the profile, an uplink coefficient value and a preset value included in the uplink data Based on the comparison result, the communication unit controls the communication unit to request the LoRa join server device to update the profile for the first LoRa terminal device.

According to a third aspect, the information processing method performed by a LoRa join server device and a LoRa network server device constituting a LoRa network with a plurality of LoRa terminal devices is provided to a first LoRa terminal device that requested a join among the plurality of LoRa terminal devices. Storing a profile including information on the allocation state of a LoRa service for a data storage unit, and receiving downlink data to be transmitted to the first LoRa terminal device, and the first LoRa terminal based on the profile After checking whether the LoRa service is temporarily allocated to the device, and if the downlink data is the first, requesting the LoRa join server device to receive a downlink count value, and the received downlink count value as much as a preset value. And transmitting the data to the first LoRa terminal device, including the data in the downlink data.

According to a fourth aspect, the information processing method performed by a LoRa join server device and a LoRa network server device constituting a LoRa network with a plurality of LoRa terminal devices is provided to a first LoRa terminal device that requested a join among the plurality of LoRa terminal devices. Storing a profile including information on an allocation state of a LoRa service for a data storage unit, and receiving uplink data transmitted from the first LoRa terminal device, and the first LoRa terminal device based on the profile After confirming whether to temporarily allocate a LoRa service for, comparing an uplink coefficient value included in the uplink data with a preset value, and a result of comparing the uplink coefficient value with the preset value, And requesting the LoRa join server device to update a profile for the first LoRa terminal device.

According to an embodiment of the present invention, when there is a possibility that retransmission of a downlink message may occur due to out-of-order generation of downlink count values, the LoRa network server apparatus changes and transmits the downlink count values. Avoid retransmission of downlink messages due to sequential generation.

In addition, when there is a concern that uplink data discard processing may occur due to the out-of-order generation of uplink count values, the LoRa network server device requests an update of information related to the LoRa join server device, thereby preventing the out-of-order generation of uplink count values. This prevents the discarding of uplink data from occurring.

1 is a block diagram of a LoRa network system according to an embodiment of the present invention.
2 is a block diagram of a LoRa network server device included in a LoRa network system according to an embodiment of the present invention.
3 is a flowchart illustrating an example of a method for processing information on downlink data performed by a LoRa network server device included in a LoRa network system according to an embodiment of the present invention.
4 is a flowchart illustrating an example of a method for processing information on uplink data performed by a LoRa network server device included in a LoRa network system according to an embodiment of the present invention.
5 is a signal flow diagram illustrating an example of transmitting downlink data according to failure and recovery in a LoRa network system according to an embodiment of the present invention.
6 is a signal flow diagram illustrating an example of transmitting uplink data according to a failure and recovery in a LoRa network system according to an embodiment of the present invention.

Advantages and features of the present invention, and a method of achieving them will become apparent with reference to the embodiments described below in detail together with the accompanying drawings. However, the present invention is not limited to the embodiments disclosed below, but may be implemented in a variety of different forms, and only these embodiments make the disclosure of the present invention complete, and are common knowledge in the art It is provided to completely inform the scope of the invention to those who have, and the invention is only defined by the scope of the claims.

In describing the embodiments of the present invention, if it is determined that a detailed description of a known function or configuration may unnecessarily obscure the subject matter of the present invention, a detailed description thereof will be omitted. In addition, terms to be described later are terms defined in consideration of functions in an embodiment of the present invention, which may vary according to the intention or custom of users or operators. Therefore, the definition should be made based on the contents throughout this specification.

1 is a block diagram of a LoRa network system according to an embodiment of the present invention.

As shown, the LoRa network system includes LoRa terminal devices (11, 12), LoRa base station devices (21, 22, 23, 24), LoRa network server devices (101, 102), LoRa join server devices (30), and applications. It includes a server device (40). However, since the components of the LoRa network system of FIG. 1 and the connection relationship between the components are only an embodiment of the present invention, the technical idea of the present invention is not limitedly interpreted by FIG. 1. For example, the number of each component of the LoRa network system is only an example.

The LoRa terminal devices 11 and 12 may be various IoT devices such as automatic meters and traffic information collection devices. For example, the LoRa terminal devices 11 and 12 may include a mobile communication terminal device installed with a LoRa application for automatic metering and a LoRa application for collecting traffic information.

The LoRa base station devices 21, 22, 23, 24 are the uplink data transmitted from the LoRa terminal devices 11, 12 to the LoRa network server devices 101, 102, and the LoRa terminals in the LoRa network server devices 101, 102. It relays downlink data transmitted to the devices 11 and 12. The LoRa base station apparatuses 21, 22, 23, and 24 may be connected to the LoRa network server apparatuses 101 and 102 through a wireless backhaul network and/or a wired backhaul network.

The LoRa network server devices 101 and 102 are in charge of selecting a base station device for LoRa service and processing a call to the LoRa terminal devices 11 and 12. These LoRa network server apparatuses 101 and 102 are in charge of services for the LoRa terminal apparatuses 11 and 12 that are mainly allocated or temporarily allocated to manage the service. In FIG. 1, the first LoRa network server device 101 is mainly allocated to the service for the first LoRa terminal device 11, and the second LoRa network server device 102 is for the service to the second LoRa terminal device 12. Is shown as an example of which is mainly assigned. In addition, the LoRa network server devices 101 and 102 have temporary jurisdiction over services for other LoRa terminal devices in addition to the main LoRa terminal devices when a failure of other LoRa network server devices is detected or a temporary allocation command such as a jurisdiction redundancy command is issued I can. For example, when a failure occurs in the first LoRa network server device 101, a LoRa service for the first LoRa terminal device 11 may be temporarily allocated to the second LoRa network server device 102, and the second LoRa network When a failure occurs in the server device 102, a LoRa service for the second LoRa terminal device 12 may be temporarily allocated to the first LoRa network server device 101. In the following description, in order to facilitate understanding of the description, LoRa services for the first LoRa terminal device 11 are mainly allocated to the first LoRa network server device 101 and temporarily allocated to the second LoRa network server device 102. In addition, the LoRa service for the second LoRa terminal device 12 is mainly allocated to the second LoRa network server device 102 and temporarily allocated to the first LoRa network server device 101. .

Then, the LoRa network server devices 101 and 102 transmit and receive downlink data and uplink data with the LoRa terminal devices 11 and 12 and the application server device 40. These LoRa network server devices 101 and 102 will be described again with reference to FIG. 2.

The LoRa join server device 30 performs registration and authentication management (eg, key management) for the LoRa terminal devices 11 and 12, and provides a LoRa for any LoRa terminal device among a plurality of LoRa terminal devices 11 and 12. It indicates which LoRa network server device among the plurality of LoRa network server devices 101 and 102 should perform call processing for service. This LoRa join server device 30 includes uplink data counted by the first LoRa terminal device 11 from the second LoRa network server device 102 to which the LoRa service for the first LoRa terminal device 11 is temporarily allocated. When a profile update request message containing information indicating that the count value of has reached the maximum value is received, the LoRa service for the first LoRa terminal device 11 is transferred to the first LoRa network server device 101 to which the first LoRa is assigned. Initialization of the count value for the uplink data being managed can be requested. In addition, the LoRa join server device 30 is an uplink counted by the second LoRa terminal device 12 from the first LoRa network server device 101 to which the LoRa service for the second LoRa terminal device 12 is temporarily allocated. When a profile update request message including information that the count value of the data has reached the maximum value is received, the LoRa service for the second LoRa terminal device 12 is assigned to the second LoRa network server device 102, which is mainly allocated. It is possible to request initialization of coefficient values for uplink data previously being managed. For example, temporary allocation of call processing for LoRa service is performed in the case of a failure in any one of the first LoRa network server device 101 and the second LoRa network server device 102, to a LoRa network server device that does not have a failure. Can be temporarily allocated.

The application server device 40 receives data from the LoRa network server devices 101 and 102, encrypts/decrypts data packets, provides specific application services to the LoRa terminal devices 11 and 12, and manages related application services. /Can perform functions such as control. Such an application server device 40 may transmit downlink data to the LoRa terminal devices 11 and 12 through the LoRa network server devices 101 and 102, and the LoRa terminal device through the LoRa network server devices 101 and 102. Uplink data can be received from (11, 12).

2 is a block diagram of a LoRa network server device 101 included in a LoRa network system according to an embodiment of the present invention.

As shown in FIG. 2, the LoRa network server apparatus 101 includes a communication unit 110, a data storage unit 120, and a control unit 130. Likewise, the LoRa network server device 102 also includes a communication unit 110, a data storage unit 120, and a control unit 130. For example, the control unit 130 may be implemented including a microprocessor. Since the components of the LoRa network server device 101 of FIG. 2 and the functions of each component are only an embodiment of the present invention, the technical idea of the present invention is not limitedly interpreted by FIG. 2.

The communication unit 110 of the LoRa network server device 101 transmits and receives various signals to and from the LoRa terminal devices 11 and 12 and the LoRa join server device 30 under the control of the controller 130. The communication unit 110 transmits the uplink data received from the LoRa terminal devices 11 and 12 to the application server device 40 or downlink data received from the application server device 40 under the control of the controller 130. Is transmitted to the LoRa terminal devices 11 and 12.

The data storage unit 120 of the LoRa network server device 101 stores a profile including information on the allocation status of the LoRa service to the LoRa terminal device requesting the join among the plurality of LoRa terminal devices 11 and 12, Various types of data based on the result of information processing by the control unit 130 are stored. The data storage unit 120 may be specifically implemented as a computer-readable recording medium, and examples of the computer-readable recording medium include magnetic media such as hard disks, floppy disks, and magnetic tapes, CD-ROMs, DVDs, and Hardware devices specially configured to store and execute program instructions such as optical media, magneto-optical media such as floptical disks, and flash memory. I can.

When the downlink data to be transmitted to the second LoRa terminal device 12 is received by the communication unit 110, the controller 130 of the LoRa network server device 101 counts the downlink data, and the data storage unit 120 If the downlink data is first counted after it is confirmed as the temporary allocation status of the LoRa service to the second LoRa terminal device 12 based on the profile stored in the device, it is received from the LoRa join server device 30 through the communication unit 110 The communication unit 110 is controlled to transmit the downlink coefficient value to the second LoRa terminal device 12 including the downlink data after increasing the downlink coefficient value by a preset value.

In addition, the controller 130 may control the communication unit 110 to transmit the count value of the downlink data to the LoRa join server device 30 every preset period.

In addition, the control unit 130 receives the uplink data transmitted from the second LoRa terminal device 12 by the communication unit 110, and based on the profile stored in the data storage unit 120, the second LoRa terminal device 12 ), based on the result of comparing the uplink count value included in the uplink data with a preset value, the second LoRa terminal device 12 is sent to the LoRa join server device 30. Controls the communication unit 110 to request an update of the profile for ).

In addition, the controller 130 transmits from the second LoRa terminal device 12 when it is confirmed that the LoRa service is mainly allocated to the second LoRa terminal device 12 based on the profile stored in the data storage unit 120. If the uplink count value included in the uplink data that has been transferred is less than the uplink count value included in the previously forwarded uplink data, the uplink data is discarded, but a specific message from the LoRa join server device 30 When (eg, a request for initializing a previous uplink count value) is received, the corresponding uplink data may be transferred and processed.

3 is a flowchart illustrating an example of a method for processing information on downlink data performed by a LoRa network server device included in a LoRa network system according to an embodiment of the present invention.

As shown in FIG. 3, in an information processing method according to an example, storing a profile including information on the allocation status of a LoRa service to a first LoRa terminal device requesting a join among a plurality of LoRa terminal devices in a data storage unit (S301) is included.

In addition, in the information processing method according to an example, downlink data to be transmitted to the first LoRa terminal device is received (S303), and temporary allocation of LoRa service to the first LoRa terminal device based on the profile stored in the data storage unit If the downlink data is the first (S307) after the status is confirmed (S305), a request to the LoRa join server device (S309) to receive a downlink coefficient value (S311).

In addition, the information processing method according to an example further includes a step (S313) of increasing the downlink coefficient value received in step S311 by a preset value and then including it in the downlink data to the first LoRa terminal device (S313).

5 is a signal flow diagram illustrating an example of transmitting downlink data according to failure and recovery in a LoRa network system according to an embodiment of the present invention. Steps S301 to S313 shown in FIG. 3 are performed by the first LoRa network server device 101 while steps S511 to S514 of FIG. 5 are being performed.

Hereinafter, a process in which downlink data is transmitted according to failure and recovery in a LoRa network system will be described with reference to FIGS. 1, 2 and 5. 5, the LoRa service for the second LoRa terminal device 12 is mainly allocated to the second LoRa network server device 102 from steps S501 to S510, and a failure occurs in the second LoRa network server device 102. In S511 to S517, the LoRa service for the second LoRa terminal device 12 is temporarily allocated to the first LoRa network server device 101.

The LoRa service for the second LoRa terminal device 12 is mainly allocated to the second LoRa network server device 102 by the join procedure, and the second LoRa network server device 102 is the second LoRa terminal device ( A profile including information on the main allocation of the LoRa service for 12) is stored in the data storage unit 120 (S501 and S502).

When the application server 40 transmits downlink data to be transmitted to the second LoRa terminal device 12, the second LoRa network server device 102 counts downlink data. For example, the control unit 130 of the second LoRa network server device 102 may count the count value of the downlink data as “50” (S503).

Subsequently, the second LoRa network server device 102 confirms that the LoRa service for the second LoRa terminal device 12 is mainly allocated based on the profile stored in the data storage unit 120, and the LoRa join server device ( 30) request a profile (e.g., key value, etc.) for the second LoRa terminal device 12 (S504) and receive a response (S505), and the downlink data received in step S503 is sent to the second LoRa terminal device 12 The transfer process is performed (S506).

The second LoRa terminal device 12 receiving the downlink data transmits a response (Ack) message to the second LoRa network server device 102 (S507), and the second LoRa network server device 102 responds (Ack). ) The message is transmitted to the application server device 40 (S508).

Thereafter, the second LoRa network server device 102 includes the downlink count value of the second LoRa terminal device 12 in the LoRa join server device 30 because the count value for the downlink data has been updated in step S503. A request for updating a profile is requested (S509), and a response to the profile update request is received from the LoRa join server device 30 (S510).

These steps S509 and S510 are performed so that the LoRa join server device 30 can manage the downlink count value for the second LoRa terminal device 12, and can be performed whenever the downlink count value changes. , LoRa join may be performed every preset period in consideration of the load of the server device 30. For example, each time the downlink coefficient value for the second LoRa terminal device 12 increases by "50", steps S509 and S510 may be performed.

On the other hand, when a failure occurs in the second LoRa network server device 102, a LoRa service for the second LoRa terminal device 12 is temporarily allocated to the first LoRa network server device 101. This temporary allocation may be based on a jurisdiction redundancy command provided by the operator, or the first LoRa network server device 101 and the second LoRa network server device 102 according to status information that can be exchanged between the first LoRa network server device 101 and the second LoRa network server device 102. The network server device 101 may detect the occurrence of a failure in the second LoRa network server device 102 and temporarily allocate a LoRa service to the second LoRa terminal device 12 by itself.

Thereafter, the application server 40, which shared a state in which the LoRa service for the second LoRa terminal device 12 is temporarily allocated to the first LoRa network server device 101, is transmitted to the second LoRa terminal device 12. Link data may be transmitted to the first LoRa network server device 101.

Then, the first LoRa network server device 101 counts downlink data for the second LoRa terminal device 12. At this time, when the first LoRa network server device 101 is temporarily allocated the LoRa service for the second LoRa terminal device 12 and then counts downlink data as the first, the second LoRa server device 30 is sent to the LoRa join server device 30. A profile including a downlink coefficient value for the terminal device 12 is requested (S512), and a profile including a downlink coefficient value is received through a response of the LoRa join server device 30 (S513).

In addition, the first LoRa network server device 101 increases the downlink count value for the second LoRa terminal device 12 received in step S513 by a preset value, and then includes it in the downlink data. Pass it to (12). For example, the first LoRa network server device 101 may receive "150" stored in the LoRa join server device 30 according to a preset period as a downlink count value for the second LoRa terminal device 12. In the downlink data transmitted to the second LoRa terminal device 12 after adding "50" to the received downlink coefficient value for the second LoRa terminal device 12, the downlink coefficient value is "200". "Can be included (S514).

Then, in the second LoRa terminal device 12, since the downlink coefficient value included in the downlink data in step S514 is larger than the downlink coefficient value included in the previously received downlink data, the downlink coefficient values are sequentially. It determines as an increasing normal situation (S515), transmits a response (Ack) message to the first LoRa network server device 101 (S516), and the first LoRa network server device 101 applies a response (Ack) message to the application. It is transmitted to the server device 40 (S517). In this way, the application server device 40 receiving the response (Ack) message performs retransmission for the same downlink data as it is confirmed that the downlink data transmitted in step S511 has been normally transferred to the second LoRa terminal device 12. I never do that.

4 is a flowchart illustrating an example of a method for processing information on uplink data performed by a LoRa network server device included in a LoRa network system according to an embodiment of the present invention.

As shown in FIG. 4, in an information processing method according to an example, storing a profile including information on the allocation status of a LoRa service to a first LoRa terminal device requesting a join among a plurality of LoRa terminal devices in a data storage unit (S401) is included.

In addition, in the information processing method according to an example, the uplink data transmitted from the first LoRa terminal device is received (S403), and the temporary allocation state of the LoRa service to the first LoRa terminal device based on the profile stored in the data storage unit. If it is confirmed as (S405), the step (S409) of comparing a preset value by checking (S407) an uplink coefficient value included in the uplink data.

In addition, the information processing method according to an example is the step of requesting the LoRa join server device to update the profile for the first LoRa terminal device based on the result of comparing the uplink coefficient value checked in step S407 with a preset value ( S411) is further included.

6 is a signal flow diagram illustrating an example of transmitting uplink data according to a failure and recovery in a LoRa network system according to an embodiment of the present invention. Steps S401 to S411 shown in FIG. 4 are performed by the first LoRa network server device 101 while steps S603 to S610 of FIG. 6 are being performed.

Hereinafter, a process in which uplink data is transmitted according to a failure and recovery in a LoRa network system will be described with reference to FIGS. 1, 2 and 6.

6, a LoRa service for the second LoRa terminal device 12 is mainly allocated to the second LoRa network server device 102, and a failure occurs in the second network server device 102 until steps S601 and S602, and then step S603. From S610 to S610, the LoRa service for the second LoRa terminal device 12 is temporarily allocated to the first LoRa network server device 101, and after the failure of the second LoRa network server device 102 is recovered, the second from S611 to S619 This is the case where the LoRa service for the LoRa terminal device 12 is mainly allocated to the second LoRa network server device 102.

The LoRa service for the second LoRa terminal device 12 is mainly allocated to the second LoRa network server device 102 by the join procedure, and the second LoRa network server device 102 is the second LoRa terminal device ( A profile including information on the main allocation of the LoRa service for 12) is stored in the data storage unit 120 (S601 and S602).

However, when a failure occurs in the second LoRa network server device 102, a LoRa service for the second LoRa terminal device 12 is temporarily allocated to the first LoRa network server device 101. This temporary allocation may be based on a jurisdiction redundancy command provided by the operator, or the first LoRa network server device 101 and the second LoRa network server device 102 according to status information that can be exchanged between the first LoRa network server device 101 and the second LoRa network server device 102. The network server device 101 may detect the occurrence of a failure in the second LoRa network server device 102 and temporarily allocate a LoRa service to the second LoRa terminal device 12 by itself. Then, the first LoRa network server device 101 stores a profile including information on a temporary allocation state of a LoRa service to the second LoRa terminal device 12 in the data storage unit 120.

Thereafter, the second LoRa terminal device 12, which shared a state in which the LoRa service for the second LoRa terminal device 12 is temporarily allocated to the first LoRa network server device 101, is transmitted to the application server device 40. Uplink data can be transmitted to the first LoRa network server device 101. At this time, the second LoRa terminal device 12 counts the uplink data and transmits the counted uplink count value in the header of the uplink data. For example, the second LoRa terminal device 12 may count "65535" as an uplink count value, include it in uplink data and transmit it to the first LoRa network server device 101 (S603). .

Then, the first LoRa network server device 101 confirms that the LoRa service for the second LoRa terminal device 12 is temporarily allocated based on the profile stored in the data storage unit 120, and the LoRa join server device ( 30) request a profile (e.g., key value, etc.) for the second LoRa terminal device 12 (S604) and receive a response (S605), and transfer the uplink data received in step S603 to the application server device 40 Process (S606).

The application server device 40 receiving the uplink data transmits a response (Ack) message to the first LoRa network server device 101 (S607), and the first LoRa network server device 101 transmits a response (Ack) message. Is transferred to the second LoRa terminal device 12 (S608).

Meanwhile, the first LoRa network server device 101 checks the uplink count value included in the uplink data received from the second LoRa terminal device 12 in step S603, compares a preset value, Based on the result of comparing the count value and the preset value, the LoRa join server device 30 is requested to update the profile of the second LoRa terminal device 12. According to the LoRa network communication standard, the uplink count value is a 16-bit field, and when the uplink count value exceeds "65535", it is counted again from "1". For example, a value of "65535" may be preset in the first LoRa network server device 101, and the first LoRa network server device 101 may receive the received from the second LoRa terminal device 12 in step S603. When the uplink count value included in the uplink data reaches a preset value, the LoRa join server device 30 may request an update of the profile for the second LoRa terminal device 12.

Thereafter, after the failure of the second LoRa network server device 102 is recovered, the LoRa service for the second LoRa terminal device 12 is mainly allocated to the second LoRa network server device 102. This return to the main allocation state may be by a jurisdiction return command provided by the operator, or the state information that can be exchanged between the first LoRa network server device 101 and the second LoRa network server device 102 Accordingly, the first LoRa network server device 101 may detect failure recovery of the second LoRa network server device 102 and release the temporary allocation state of the LoRa service to the second LoRa terminal device 12 by itself. Then, the second LoRa network server device 101 stores a profile including information on the main allocation state of the LoRa service to the second LoRa terminal device 12 in the data storage unit 120.

On the other hand, the LoRa service for the second LoRa terminal device 12 is transmitted to the application server device 40 by the second LoRa terminal device 12, which shares a state mainly allocated to the second LoRa network server device 102. Uplink data may be transmitted to the second LoRa network server device 102. At this time, the second LoRa terminal device 12 counts the uplink data and transmits the counted uplink count value in the header of the uplink data. For example, the second LoRa terminal device 12 may count "8" as an uplink count value, and may include this in uplink data and transmit it to the second LoRa network server device 102 (S611). .

Then, the second LoRa network server device 102 confirms that the LoRa service for the second LoRa terminal device 12 is mainly allocated based on the profile stored in the data storage unit 120, and the LoRa join server device ( 30) requests a profile (eg, a key value) for the second LoRa terminal device 12 (S612) and receives a response. At this time, the LoRa join server device 30 has received a profile update request message including information that the count value of the uplink data counted by the second LoRa terminal device 12 has reached the maximum value in step S609. For this reason, a request is made to the second LoRa network server device 102 to initialize the count value for the uplink data previously being managed (S613).

Accordingly, in the second LoRa network server device 102, the uplink count value included in the uplink data received from the second LoRa terminal device 12 in step S611 is converted to the previously managed uplink data initialized in step S613. Since it is larger than the coefficient value for, it is determined as a normal situation in which the uplink coefficient value increases sequentially (S614), and the uplink data received in step S611 is transferred to the application server device 40 (S615).

The application server device 40 receiving the uplink data transmits a response (Ack) message to the second LoRa network server device 102 (S616), and the second LoRa network server device 102 sends a response (Ack) message. Is transferred to the second LoRa terminal device 12 (S617).

Thereafter, the second LoRa network server device 102 has updated the count value for the uplink data in steps S613 and S615, and thus the uplink count of the second LoRa terminal device 12 is added to the LoRa join server device 30. A profile update including a value is requested (S618), and a response to the profile update request is received from the LoRa join server 30 (S619).

As described so far, according to an embodiment of the present invention, when there is a risk of retransmission of a downlink message due to out-of-order generation of downlink count values, the LoRa network server apparatus changes and transmits the downlink count values, It prevents retransmission of downlink messages due to out-of-order generation of downlink count values.

In addition, when there is a concern that uplink data discard processing may occur due to the out-of-order generation of uplink count values, the LoRa network server device requests an update of information related to the LoRa join server device, thereby preventing the out-of-order generation of uplink count values. This prevents the discarding of uplink data from occurring.

Combinations of each block in the block diagram attached to the present invention and each step in the flowchart may be performed by computer program instructions. Since these computer program instructions can be mounted on the encoding processor of a general-purpose computer, special purpose computer or other programmable data processing equipment, the instructions executed by the encoding processor of the computer or other programmable data processing equipment are each block of the block diagram or Each step of the flow chart will create a means to perform the functions described. These computer program instructions can also be stored on a computer-usable or computer-readable recording medium that can be directed to a computer or other programmable data processing equipment to implement a function in a specific manner, so that the computer-readable or computer-readable medium. It is also possible to produce an article of manufacture in which the instructions stored on the recording medium contain instruction means for performing the functions described in each block of the block diagram or each step of the flowchart. Computer program instructions can also be mounted on a computer or other programmable data processing equipment, so that a series of operating steps are performed on a computer or other programmable data processing equipment to create a computer-executable process to create a computer or other programmable data processing equipment. It is also possible for the instructions to perform the processing equipment to provide steps for performing the functions described in each block of the block diagram and each step of the flowchart.

In addition, each block or each step may represent a module, segment, or part of code comprising one or more executable instructions for executing the specified logical function(s). In addition, it should be noted that in some alternative embodiments, functions mentioned in blocks or steps may occur out of order. For example, two blocks or steps shown in succession may in fact be performed substantially simultaneously, or the blocks or steps may sometimes be performed in the reverse order depending on the corresponding function.

The above description is merely illustrative of the technical idea of the present invention, and those of ordinary skill in the art to which the present invention pertains will be able to make various modifications and variations without departing from the essential quality of the present invention. Accordingly, the embodiments disclosed in the present invention are not intended to limit the technical idea of the present invention, but to explain the technical idea, and the scope of the technical idea of the present invention is not limited by these embodiments. The scope of protection of the present invention should be interpreted by the following claims, and all technical ideas within the scope equivalent thereto should be construed as being included in the scope of the present invention.

According to an embodiment of the present invention, retransmission of downlink messages due to out-of-order generation of downlink count values is prevented, and uplink data discard processing due to out-of-order generation of uplink count values does not occur. do.

The present invention can be applied not only to a LoRa network system but also to various IoT network technology fields.

11, 12: LoRa terminal equipment 21, 22, 23, 24: LoRa base station equipment
30: LoRa join server device 40: Application server device
101, 102: LoRa network server device 110: communication unit
120: data storage unit 130: control unit

Claims (6)

As a LoRa (Long Range) join server device and a LoRa network server device that composes a LoRa network with a plurality of LoRa terminal devices,
A communication unit for transmitting and receiving data with the LoRa terminal device and the LoRa join server device,
A data storage unit for storing a profile including information on an allocation state of a LoRa service to a first LoRa terminal device requesting a join among the plurality of LoRa terminal devices;
Including a control unit,
The control unit receives downlink data to be transmitted to the first LoRa terminal device using the communication unit,
Count the received downlink data,
Based on the profile, it is checked whether or not a LoRa service is temporarily allocated to the first LoRa terminal device according to a failure of a LoRa network server device previously allocated to the first LoRa terminal device,
It is checked whether the downlink data is first counted based on the confirmation of the temporary allocation of the LoRa service to the first LoRa terminal device,
Requesting the LoRa join server device through the communication unit on the basis of confirming that the downlink data is first counted, and receiving a downlink count value,
Controls the communication unit to increase the received downlink coefficient value from the LoRa join server device by a preset value and then include it in the downlink data and transmit it to the first LoRa terminal device.
LoRa network server device. The method of claim 1,
The control unit controls the communication unit to transmit the count value of the downlink data to the LoRa join server device every preset period.
LoRa network server device. As a LoRa (Long Range) join server device and a LoRa network server device that composes a LoRa network with a plurality of LoRa terminal devices,
A communication unit for transmitting and receiving data with the LoRa terminal device and the LoRa join server device,
A data storage unit for storing a profile including information on an allocation state of a LoRa service to a first LoRa terminal device requesting a join among the plurality of LoRa terminal devices;
Including a control unit,
The control unit receives the uplink data transmitted from the first LoRa terminal device using the communication unit, and based on the profile, according to the occurrence of a failure of the LoRa network server device pre-allocated to the first LoRa terminal device. Checks whether or not a LoRa service is temporarily allocated to the first LoRa terminal device, and based on the confirmation of the temporary allocation of the LoRa service to the first LoRa terminal device, an uplink coefficient value included in the uplink data Comparing a preset value with and controlling the communication unit to request an update of a profile for the first LoRa terminal device to the LoRa join server device based on the result of the comparison.
LoRa network server device. The method of claim 3,
When it is determined that the LoRa service is mainly allocated to the first LoRa terminal device based on the profile, the control unit includes an uplink coefficient value included in the uplink data in the previously transmitted uplink data If it is smaller than the uplink count value, the corresponding uplink data is discarded, but when a specific message is received from the LoRa join server device, the corresponding uplink data is transmitted and processed.
LoRa network server device. As an information processing method performed by a LoRa (Long Range) join server device and a LoRa network server device constituting a LoRa network with a plurality of LoRa terminal devices,
Storing a profile including information on an allocation state of a LoRa service to a first LoRa terminal device requesting a join among the plurality of LoRa terminal devices in a data storage unit, and
Receiving downlink data to be transmitted to the first LoRa terminal device,
Checking whether to temporarily allocate a LoRa service to the first LoRa terminal device based on the profile according to a failure of a LoRa network server device previously allocated to the first LoRa terminal device,
Confirming whether the downlink data is the first based on confirmation of the temporary allocation of the LoRa service to the first LoRa terminal device;
Requesting the LoRa join server device to receive a downlink coefficient value based on the fact that the downlink data is confirmed to be the first;
Increasing the received downlink coefficient value by a preset value, including in the downlink data, and transmitting it to the first LoRa terminal device
Information processing method of the LoRa network server device comprising a. As an information processing method performed by a LoRa (Long Range) join server device and a LoRa network server device constituting a LoRa network with a plurality of LoRa terminal devices,
Storing a profile including information on an allocation state of a LoRa service to a first LoRa terminal device requesting a join among the plurality of LoRa terminal devices in a data storage unit, and
Receiving uplink data transmitted from the first LoRa terminal device;
Based on the profile, checking whether a LoRa service is temporarily allocated to the first LoRa terminal device according to a failure of a LoRa network server device previously allocated to the first LoRa terminal device,
Comparing an uplink coefficient value included in the uplink data with a preset value based on confirmation of the temporary allocation of the LoRa service to the first LoRa terminal device;
Requesting the LoRa join server device to update a profile for the first LoRa terminal device based on a result of comparing the uplink coefficient value and the preset value
Information processing method of the LoRa network server device comprising a.

Images