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

Abstract

Disclosed is a LoRa join server device connected to a plurality of LoRa network server devices constituting a LoRa terminal device and a LoRa network. The Lora join server device comprises: a communication unit transmitting and receiving data with a LoRa network server device; a data storage unit storing a profile including information on a LoRa network server device involved in a service for a LoRa terminal device among a plurality of LoRa network server devices; and a control unit. When the control unit is determined that two or more LoRa network server devices among the plurality of LoRa network server devices are involved in the service for the LoRa terminal device based on the profile, the communication unit is controlled to request the deletion of information on the at least one LoRa terminal device of the two or more LoRa network server devices.

Description

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

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

The Internet of Things (IoT) refers to intelligent technologies and services that connect various things through a network such as the Internet so that people and things, information between things and things can communicate with each other. The IoT is a more advanced technology than conventional wired / wireless communication, and can be used in various fields such as unmanned meter, unmanned vending machine, intelligent transportation service, and real-time monitoring medical service. According to the results of IoT device-related research and analysis, the number of IoT-connected devices is expected to increase to about 30 billion by 2025, and accordingly, research on IoT utilization is actively being conducted.

Conventionally, Wi-Fi, Bluetooth, etc. have been used as a communication method for the construction of the IoT system. However, these methods are disadvantageous in that they can communicate only at a relatively short distance and are not suitable for IoT systems that need to cover a wide range. The communication method for the Internet of Things needs to be designed so that it can cover a wide range as described above, but has low power consumption for the Internet of Things devices where there are many cases where charging restrictions and continuous power supply are required. Accordingly, a demand for so-called low power wide-area (LPWA) has emerged. LPWA is a general term for IoT network technology specialized in small data transmission, where low-speed transmission of 1 kbps or less is acceptable and has characteristics of wide area coverage and low power consumption.

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

Meanwhile, the LoRa network may consist of a LoRa terminal device, a LoRa base station device, and a LoRa network server device.

In this LoRa network, a LoRa network server device that is responsible for LoRa service is allocated to each LoRa terminal device, and when a LoRa network server device assigned to any LoRa terminal device fails, another LoRa network server device without a failure is assigned to any LoRa terminal device. When the failure is recovered, the original LoRa network server device is re-assigned to any LoRa terminal device.

As described above, in case a failure occurs, the LoRa network server device in charge of the LoRa service for a random LoRa terminal device is redundantly operated. If the LoRa network is operated for a long time, failures and recovery may occur several times, and LoRa Recently, information about LoRa terminal devices that have not been allocated is accumulated in the network server device, and the unnecessary information accumulated in this way erodes the resources of the LoRa network server device, thereby adversely affecting the LoRa service.

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

According to an embodiment, a LoRa join server device capable of managing resources of a LoRa network server device is provided.

Also, a method for processing information for resource management of a LoRa network server device in a LoRa join server device is provided.

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 having ordinary knowledge to which the present invention belongs from the following description.

According to a first aspect, a LoRa join server device connected to a LoRa terminal device and a plurality of LoRa network server devices constituting a LoRa network includes a communication unit for transmitting and receiving data to and from the LoRa network server device, and among the plurality of LoRa network server devices. A data storage unit for storing a profile including information on a LoRa network server device involved in a service for the LoRa terminal device, and a control unit, wherein the control unit is configured to provide the service with the plurality of LoRa networks based on the profile. When it is determined that two or more LoRa network server devices are involved, the control unit controls the communication unit to request deletion of information on the LoRa terminal device from at least one of the two or more LoRa network server devices.

According to a second aspect, an information processing method performed by a LoRa join server device connected to a LoRa terminal device and a plurality of LoRa network server devices constituting a LoRa network is a service for the LoRa terminal device among the plurality of LoRa network server devices. Storing a profile including information on the LoRa network server device involved in the data storage unit, and determining that two or more LoRa network server devices among the plurality of LoRa network server devices are involved in the service based on the profile And requesting deletion of information on the LoRa terminal device from at least one of the two or more LoRa network server devices.

According to an embodiment of the present invention, when two or more LoRa network server devices are involved in a service for one LoRa terminal device, a LoRa corresponding to at least one of two or more LoRa network server devices involved in a service for the corresponding LoRa terminal device It is possible to request deletion of information on the terminal device. When the LoRa network server device deletes unnecessary information according to the request to delete the information, since the resources of the LoRa network server device eroded by unnecessary information can be utilized for the LoRa service, the quality of the LoRa service is improved.

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 join server device included in a LoRa network system according to an embodiment of the present invention.
3 is a flowchart of an information processing method performed by a LoRa join server device included in a LoRa network system according to an embodiment of the present invention.
4 is a signal flow diagram illustrating an example of a join operation according to failure and recovery in a LoRa network system according to an embodiment of the present invention.
5 is a signal flow diagram illustrating another example of a join operation according to failure and recovery in a LoRa network system according to an embodiment of the present invention.
6 is a signal flow diagram of an information deletion operation performed by a LoRa network server device in a LoRa network system according to an embodiment of the present invention.
7 is a signal flow diagram illustrating an example of a profile update operation performed by a LoRa join server device in a system according to an embodiment of the present invention.
8 is a signal flow diagram illustrating another example of a profile update operation performed by a LoRa join server device in a system according to an embodiment of the present invention.

Advantages and features of the present invention, and methods for achieving them will be clarified with reference to 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 various different forms, and only the embodiments allow the disclosure of the present invention to be complete, and common knowledge in the art to which the present invention pertains It is provided to completely inform the person having the scope of the invention, and the present invention is only defined by the scope of the claims.

In describing embodiments of the present invention, when it is determined that a detailed description of known functions or configurations may unnecessarily obscure the subject matter of the present invention, the detailed description 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 a user's or operator's intention or practice. Therefore, the definition should be made based on the contents throughout this specification.

1 is a configuration diagram of a LoRa network system according to an embodiment of the present invention, and FIG. 2 is a configuration diagram of a LoRa join server device included in a LoRa network system according to an embodiment of the present invention.

As shown in this, the LoRa network system joins LoRa terminal devices 11 and 12, LoRa base station devices 21, 22, 23 and 24, LoRa network server devices 31 and 32, application server device 40 and LoRa. It includes a server device (100). However, since the connection relationship between the components of the LoRa network system of FIG. 1 and each component is only an embodiment of the present invention, the technical spirit 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 mobile communication terminal devices in which LoRa applications for automatic metering, LoRa applications for traffic information collection, and the like are installed.

The LoRa base station devices 21, 22, 23, and 24 are uplink packets transmitted from the LoRa terminal devices 11, 12 to the LoRa network server devices 31, 32 and LoRa terminals in the LoRa network server devices 31, 32. The downlink packets transmitted to the devices 11 and 12 are relayed. The LoRa base station devices 21, 22, 23 and 24 may be connected to the LoRa network server devices 31 and 32 through wireless backhaul networks and / or wired backhaul networks.

The LoRa network server devices 31 and 32 are in charge of the base station device selection and call processing for the LoRa service for the LoRa terminal devices 11 and 12. The LoRa network server device (31, 32) is in charge of the service for the LoRa terminal device (11, 12) assigned to manage the service. 1, a first LoRa network server device 31 is allocated to a service for a first LoRa terminal device 11, and a second LoRa network server device 32 is provided for a service for a second LoRa terminal device 12. The assigned example is shown. In addition, the LoRa network server devices 31 and 32 can manage services for other LoRa terminal devices in addition to the pre-assigned LoRa terminal devices when a failure of another LoRa network server device is detected or an allocation command such as a jurisdiction redundancy command occurs. . For example, when a failure occurs in the first LoRa network server device 31, the second LoRa network server device 32 may service the first LoRa terminal device 11.

The application server device 40 may be included in the LoRa network system as described above, receiving data from the LoRa network server devices 31 and 32, encrypting / decrypting data packets, and for the LoRa terminal devices 11 and 12. It can perform functions such as provision of specific application service and management / control related to the application service.

The LoRa join server device 100 performs registration and authentication management (eg, key management) for the LoRa terminal devices 11 and 12, and LoRa for any LoRa terminal device among the plurality of LoRa terminal devices 11 and 12 It informs which LoRa network server device among the plurality of LoRa network server devices 31 and 32 to perform call processing for service.

The LoRa join server device 100 includes a communication unit 110, a data storage unit 120 and a communication unit 130, as shown in FIG. However, since the components of the LoRa join server apparatus 100 of FIG. 2 and the functions of each component are only one embodiment of the present invention, the technical spirit of the present invention is not limitedly interpreted by FIG. 2.

The communication unit 110 of the LoRa join server device 100 transmits and receives signals to and from the LoRa network server devices 31 and 32 under the control of the control unit 130.

The data storage unit 120 of the LoRa join server device 100 includes a profile including information on the LoRa network server device involved in the service for the LoRa terminal devices 11 and 12 among the LoRa network server devices 31 and 32. And stores various data based on the result of information processing by the control unit 130. 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, and DVDs. Hardware devices specially configured to store and execute program instructions, such as optical media, magneto-optical media such as floptical disks, and flash memory. Can be.

The control unit 130 of the LoRa join server device 100 may provide at least two of the LoRa network server devices 31 and 32 to services for any LoRa terminal device 11 or 12 based on the profile stored in the data storage unit 120. When it is determined that the LoRa network server device is involved, the communication unit 110 controls the at least one of the two or more LoRa network server devices to request deletion of information about the arbitrary LoRa terminal device 11 or 12. For example, the control unit 130 generates a session key required for communication between the application server device 40 and the LoRa terminal devices 11 and 12 connected to the LoRa network, and then stores the session key in the data storage unit 120, and random LoRa A message requesting the deletion of information on the terminal device 11 or 12 may be transmitted to the LoRa network server device 31 or 32 through the communication unit 110. In addition, the control unit 130 is connected to the application server device 40 connected to the LoRa network and the generated resource (Resource) when the information is received through the communication unit 110 from the LoRa network server device (31, 32) to the resource Information about the profile may be included and stored in the data storage unit 120. For example, the control unit 130 may be implemented by including a microprocessor.

3 is a flowchart of an information processing method performed by the LoRa join server device 100 included in the LoRa network system according to an embodiment of the present invention.

As shown in FIG. 3, an information processing method according to an embodiment includes storing a profile including information on a LoRa network server device involved in a service for a LoRa terminal device among a plurality of LoRa network server devices in a data storage unit. Includes. For example, the service for the first LoRa terminal device may be handled by a previously assigned first LoRa network server device, and when a failure of the first LoRa network server device is detected or an allocation command occurs, the second LoRa network server device A service for the first LoRa terminal device may be provided, and a profile including information on the first LoRa network server device and the second LoRa network server device responsible for the service for the first LoRa terminal device may be stored in the data storage unit. Can be.

And, the information processing method according to an embodiment of the plurality of LoRa network server device of the plurality of LoRa network server devices in the service for the LoRa terminal device based on the profile stored in the data storage unit, it is determined that two or more LoRa Further comprising the step of requesting to delete information about the LoRa terminal device to at least one of the network server device (S220 to S240). For example, when the power of the LoRa terminal device is turned off and on according to a failure and recovery of the LoRa network server device, the join operation may be performed again, and at this time, two of the plurality of LoRa network server devices are provided to the service for the LoRa terminal device. When it is determined that the above-mentioned LoRa network server device is involved, a session key required for communication with another server device connected to the LoRa network can be generated and stored in a data storage unit, and a message requesting deletion of information about an arbitrary LoRa terminal device is generated. It can be sent to any LoRa network server device.

The information processing method performed by the LoRa join server device 100 included in the LoRa network system according to an embodiment of the present invention will be further described below with reference to FIGS. 4 to 8.

4 is a signal flow diagram illustrating an example of a join operation according to failure and recovery in a LoRa network system according to an embodiment of the present invention. This join operation is a case in which the service for the second LoRa terminal device 12 is restored after a failure occurs in the second LoRa network server device 32 in a state where it is assigned to the jurisdiction of the second LoRa network server device 32, This is an example in which the second LoRa terminal device 12 requests a join from the second LoRa network server device 32 after the failure recovery.

When a failure occurs in the second LoRa network server apparatus 32, the operator allocates a service for the second LoRa terminal apparatus 12 to the jurisdiction of the first LoRa network server apparatus 31 until the failure is recovered. It can be input to the device 100. Alternatively, the first LoRa network server device 31, the second LoRa network server device 32, and the LoRa join server device 100 may periodically transmit and receive status messages to each other, and based on the status message, the LoRa join server The device 100 may detect that a failure has occurred in the second LoRa network server device 32.

In the state in which the second LoRa network server device 32 has failed, the first LoRa network server device 31 through the second LoRa base station device 21, 22, 23, 24 in the vicinity of the second LoRa terminal device 12 Sends a join request message to request join (S301).

Subsequently, the first LoRa network server device 31 queries the LoRa join server device 100 for jurisdiction (S303) because the service for the second LoRa terminal device 12 does not know which LoRa network server device has jurisdiction. After that, perform the procedure for receiving a response. Here, the LoRa join server device 100 notifies the first LoRa network server device 31 through a jurisdiction that a service for the second LoRa terminal device 12 is allocated (S305).

Then, the first LoRa network server device 31 requests the join of the second LoRa terminal device 12 to the LoRa join server device 100 (S307), and the LoRa join server device 100 is the second LoRa terminal device. (12) generates and stores the session key required to communicate with the application server device 40 and responds to the join of the second LoRa terminal device 12 (S309), and the first LoRa network server device 31 Sends a join accept message to the second LoRa terminal device 12 to accept the join requested in step S301 (S311).

Various information related to the service for the second LoRa terminal device 12 is stored in the first LoRa network server device 31 through the steps S301 to S311, and the data storage unit of the LoRa join server device 100 In 120), information about the first LoRa network server device 31 involved in the service for the second LoRa terminal device 12 is stored.

Thereafter, the failure of the second LoRa network server device 32 is recovered, and when the power of the second LoRa terminal device 12 is turned off by the user and then turned on again, the join operation is performed again.

Upon re-execution of the join operation, the second LoRa terminal device 12 transmits a join request message to the second LoRa network server device 32 through the nearby LoRa base station devices 21, 22, 23, and 24. Request join (S313).

Subsequently, the second LoRa network server apparatus 32 queries the LoRa join server apparatus 100 for jurisdiction (S315) because the service for the second LoRa terminal apparatus 12 does not know which LoRa network server apparatus has jurisdiction. After that, perform the procedure for receiving a response. Here, the LoRa join server device 100 notifies the second LoRa network server device 32 through a jurisdiction that a service for the second LoRa terminal device 12 is allocated (S317).

Then, the second LoRa network server device 32 requests the join of the second LoRa terminal device 12 to the LoRa join server device 100 (S319), and the LoRa join server device 100 is the second LoRa terminal device. (12) generates and stores the session key required to communicate with the application server device 40, responds to the join of the second LoRa terminal device 12 (S321), and the second LoRa network server device 32 Sends a join accept message to the second LoRa terminal device 12 to accept the join requested in step S313 (S323).

Meanwhile, as described above, various information related to the service for the second LoRa terminal device 12 is stored in the first LoRa network server device 31 through steps S301 to S311, and the second LoRa network server device ( After the failure of 32) is restored, since the second LoRa network server device 32 controls the service for the second LoRa terminal device 12, the second LoRa network terminal device from the standpoint of the first LoRa network server device 31 The information on the service in (12) corresponds to unnecessary information. This unnecessary information can adversely affect the LoRa service because it consumes the resources of the first LoRa network server device 31.

Therefore, after the LoRa join server device 100 responds to the join of the second LoRa terminal device 12, a profile including information on the LoRa network server device involved in the service for the second LoRa terminal device 12 It is checked whether two or more LoRa network server devices are involved in the service for the second LoRa terminal device 12, and two or more LoRa network server devices among the services for the second LoRa terminal device 12 are involved. If it is determined that the message is transmitted to at least one of the two or more LoRa network server device requesting the deletion of information about the second LoRa terminal device 120. For example, the LoRa join server device 100 is second to the first LoRa network server device 31 in charge of the service for the second LoRa terminal device 12 during the failure of the second LoRa network server device 32. Request to delete the stored information related to the LoRa terminal device 12 (S325).

Then, the first LoRa network server device 31 deletes various types of information related to the service for the second LoRa terminal device 12 accumulated through steps S301 to S311, and then requests for information deletion in step S325. Responds to the LoRa join server device 100 (S327).

5 is a signal flow diagram illustrating another example of a join operation according to failure and recovery in a LoRa network system according to an embodiment of the present invention. This join operation is a case in which the service for the second LoRa terminal device 12 is restored after a failure occurs in the second LoRa network server device 32 in a state where it is assigned to the jurisdiction of the second LoRa network server device 32, This is an example in which the second LoRa terminal device 12 requests a join from the first LoRa network server device 31 after the failure recovery.

When a failure occurs in the second LoRa network server apparatus 32, the operator allocates a service for the second LoRa terminal apparatus 12 to the jurisdiction of the first LoRa network server apparatus 31 until the failure is recovered. It can be input to the device 100. Alternatively, the first LoRa network server device 31, the second LoRa network server device 32, and the LoRa join server device 100 may periodically transmit and receive status messages to each other, and based on the status message, the LoRa join server The device 100 may detect that a failure has occurred in the second LoRa network server device 32.

In the state in which the second LoRa network server device 32 has failed, the first LoRa network server device 31 through the second LoRa base station device 21, 22, 23, 24 in the vicinity of the second LoRa terminal device 12 Sends a join request message to request join (S401).

Subsequently, the first LoRa network server device 31 queries the LoRa join server device 100 for jurisdiction (S403) because the service to the second LoRa terminal device 12 does not know which LoRa network server device has jurisdiction. After that, perform the procedure for receiving a response. Here, the LoRa join server device 100 notifies the first LoRa network server device 31 through a jurisdiction that a service for the second LoRa terminal device 12 is allocated (S405).

Then, the first LoRa network server device 31 requests the join of the second LoRa terminal device 12 to the LoRa join server device 100 (S407), and the LoRa join server device 100 is the second LoRa terminal device. (12) generates and stores the session key required to communicate with the application server device 40 and responds to the join of the second LoRa terminal device 12 (S409), and the first LoRa network server device 31 Sends a join accept message to the second LoRa terminal device 12 to accept the join requested in step S301 (S411).

Through these steps S401 to S411, various information related to a service for the second LoRa terminal device 12 is stored in the first LoRa network server device 31, and a data storage unit of the LoRa join server device 100 ( In 120), information about the first LoRa network server device 31 involved in the service for the second LoRa terminal device 12 is stored.

Thereafter, the failure of the second LoRa network server device 32 is recovered, and when the power of the second LoRa terminal device 12 is turned off by the user and then turned on again, the join operation is performed again.

Upon re-execution of the join operation, the second LoRa terminal device 12 transmits a join request message to the first LoRa network server device 31 through the nearby LoRa base station devices 21, 22, 23, and 24. Request to join (S413).

Subsequently, the first LoRa network server device 31 queries the LoRa join server device 100 for jurisdiction (S415) because the service for the second LoRa terminal device 12 does not know which LoRa network server device has jurisdiction. After that, perform the procedure for receiving a response. Here, the LoRa join server device 100 transmits a response to the first LoRa network server device 31 through the jurisdiction that the service for the second LoRa terminal device 12 is assigned to the second LoRa network server device 32. Inform (S417).

Then, the first LoRa network server device 31 requests a join of the second LoRa terminal device 12 to the second LoRa network server device 32 (S419), and the second LoRa network server device 32 comprises 2 Transfers the join request for the LoRa terminal device 12 to the LoRa join server device 100 (S421), and the LoRa join server device 100 includes the second LoRa terminal device 12 and the application server device 40. In addition to generating and storing the session key required for communication, the second LoRa terminal device 12 responds to the join (S423), and the second LoRa network server device 32 connects to the second LoRa terminal device 12. The join response is transmitted to the first LoRa network server device 31, and the first LoRa network server device 31 transmits a join acceptance message to the second LoRa terminal device 12 to accept the join requested in step S413. (S427).

Meanwhile, as described above, various information related to the service for the second LoRa terminal device 12 is stored in the first LoRa network server device 31 through steps S401 to S427, and the second LoRa network server device ( After the failure of 32) is restored, since the second LoRa network server device 32 controls the service for the second LoRa terminal device 12, the second LoRa network terminal device from the standpoint of the first LoRa network server device 31 The information on the service in (12) corresponds to unnecessary information. This unnecessary information can adversely affect the LoRa service because it consumes the resources of the first LoRa network server device 31.

Therefore, after the LoRa join server device 100 responds to the join of the second LoRa terminal device 12, a profile including information on the LoRa network server device involved in the service for the second LoRa terminal device 12 It is checked whether two or more LoRa network server devices are involved in the service for the second LoRa terminal device 12, and two or more LoRa network server devices among the services for the second LoRa terminal device 12 are involved. If it is determined that the message is transmitted to at least one of the two or more LoRa network server device requesting the deletion of information about the second LoRa terminal device 120. For example, the LoRa join server device 100 is second to the first LoRa network server device 31 in charge of the service for the second LoRa terminal device 12 during the failure of the second LoRa network server device 32. Request to delete the stored information related to the LoRa terminal device 12 (S429).

Then, the first LoRa network server device 31 deletes various types of information related to the service for the second LoRa terminal device 12 accumulated through steps S401 to S427, and then requests for information deletion in step S429. Responds to the LoRa join server device 100 (S431).

6 is a signal flow diagram of an information deletion operation performed by a LoRa network server device in a LoRa network system according to an embodiment of the present invention.

4 or 5, the first LoRa network server device 31 may participate in the service for the second LoRa terminal device 12 during the failure of the second LoRa network server device 32, and 2 After the failure of the LoRa network server device 32 is recovered, the first LoRa network server device 31 enters the second LoRa network server device 32 because it manages the service for the second LoRa terminal device 12 In the information on the service of the second LoRa terminal device 12 corresponds to unnecessary information. This unnecessary information can adversely affect the LoRa service because it consumes the resources of the first LoRa network server device 31.

Therefore, the first LoRa network server device 31 may request the LoRa join server device 100 to confirm the profile of the second LoRa terminal device 12. For example, when the packet transmission / reception of the second LoRa terminal device 12 does not occur for a predetermined threshold time, the first LoRa network server device 31 may transmit the second LoRa terminal server device 100 to the LoRa join server device 100 ( You can request confirmation of the profile for 12).

Then, the LoRa join server device 100 checks the profile for the second LoRa terminal device 12 in response to the information verification request from the first LoRa network server device 31, and based on the identified profile, at the current time By providing information on the LoRa network server device that is in charge of the service for the second LoRa terminal device 12, it is possible to respond to the information verification request in step S501. As a result, the first LoRa network server device 31 is accumulated while participating in the service for the second LoRa terminal device 12 during the failure of the second LoRa network server device 32 as shown in FIG. 4 or FIG. 5. Various information related to a service for the LoRa terminal device 12 may be deleted (S503).

7 is a signal flow diagram illustrating an example of a profile update operation performed by a LoRa join server device in a system according to an embodiment of the present invention, wherein the second LoRa terminal device 12 is a second LoRa network server device 32 This is an example of requesting a join.

4 or 5, the first LoRa network server device 31 may participate in the service for the second LoRa terminal device 12 during a failure of the second LoRa network server device 32. However, when a resource such as an application server device 40 and a security key is generated before a failure of the second LoRa network server device 32 occurs, a second LoRa terminal device during a failure of the second LoRa network server device 32 occurs The first LoRa network server device 31 involved in the service for (12) is a second LoRa terminal because it cannot grasp the resources generated between the second LoRa network server device 32 and the LoRa join server device 100 When providing a service for the device 12, a corresponding resource cannot be provided to the LoRa join server device 100, so that the service for the second LoRa terminal device 12 may not be normally performed.

The second LoRa terminal device 12 requests a join by transmitting a join request message to the second LoRa network server device 32 through the nearby LoRa base station devices 21, 22, 23, and 24 (S601).

Subsequently, the second LoRa network server apparatus 32 queries the LoRa join server apparatus 100 for jurisdiction (S603) because the service for the second LoRa terminal apparatus 12 does not know which LoRa network server apparatus has jurisdiction. After that, perform the procedure for receiving a response. Here, the LoRa join server device 100 notifies the second LoRa network server device 32 through a jurisdiction that the service for the second LoRa terminal device 12 is in an assigned state (S605).

Then, the second LoRa network server apparatus 32 requests the join of the second LoRa terminal apparatus 12 to the LoRa join server apparatus 100 (S607), and the LoRa join server apparatus 100 is the second LoRa terminal apparatus. (12) generates and stores the session key required to communicate with the application server device 40, and responds to the join request of the second LoRa terminal device 12 (S609).

Here, the second LoRa network server device 32 and the LoRa join server device 100 generate resources such as a security key required for the second LoRa terminal device 12 to communicate with the application server device 40 ( S611). Then, the second LoRa network server device 32 requests the LoRa join server device 100 to update the profile for the second LoRa terminal device 12 (S613). Then, the LoRa join server device 100 updates the profile for the second LoRa terminal device 12 including resources such as the security key generated in step S611 according to the request of the second LoRa network server device 32. Afterward, it responds to the profile update request in step S613 (S615).

Then, the second LoRa network server device 32 transmits a join acceptance message to the second LoRa terminal device 12 according to the profile update response of the LoRa join server device 100, thereby joining the join request in step S601. Accept (S617).

Subsequently, as illustrated in FIG. 4 or FIG. 5 described above, the first LoRa network server device 31 may participate in the service for the second LoRa terminal device 12 during the failure of the second LoRa network server device 32. . However, when a resource such as an application server device 40 and a security key is generated before a failure of the second LoRa network server device 32 occurs, a second LoRa terminal device during a failure of the second LoRa network server device 32 occurs The first LoRa network server device 31 involved in the service for (12) is a second LoRa terminal because it cannot grasp the resources generated between the second LoRa network server device 32 and the LoRa join server device 100 When providing a service for the device 12, the corresponding resource cannot be provided to the LoRa join server device 100. However, since the profile for the second LoRa terminal device 12 is updated by the LoRa join server device 100 through steps S613 and S615, the service for the second LoRa terminal device 12 is normally provided.

8 is a signal flow diagram showing an example of a profile update operation performed by a LoRa join server device in a system according to an embodiment of the present invention, wherein the second LoRa terminal device 12 is the first LoRa network server device 31 This is an example of requesting a join.

4 or 5, the first LoRa network server device 31 may participate in the service for the second LoRa terminal device 12 during a failure of the second LoRa network server device 32. However, when a resource such as an application server device 40 and a security key is generated before a failure of the second LoRa network server device 32 occurs, a second LoRa terminal device during a failure of the second LoRa network server device 32 occurs The first LoRa network server device 31 involved in the service for (12) is a second LoRa terminal because it cannot grasp the resources generated between the second LoRa network server device 32 and the LoRa join server device 100 When providing a service for the device 12, a corresponding resource cannot be provided to the LoRa join server device 100, so that the service for the second LoRa terminal device 12 may not be normally performed.

The second LoRa terminal device 12 requests a join by transmitting a join request message to the first LoRa network server device 31 through the nearby LoRa base station devices 21, 22, 23, and 24 (S701).

Subsequently, the first LoRa network server device 31 queries the LoRa join server device 100 for jurisdiction (S703) because the service for the second LoRa terminal device 12 does not know which LoRa network server device has jurisdiction. After that, perform the procedure for receiving a response. Here, the LoRa join server device 100 notifies the first LoRa network server device 31 through a jurisdiction that the service for the second LoRa terminal device 12 is assigned to the second LoRa network server device 32. (S705).

Then, the first LoRa network server device 31 requests the second LoRa network server device 32 to join the second LoRa terminal device 12 (S707), and the second LoRa network server device 32 is LoRa. The join server device 100 transmits a join to the second LoRa terminal device 12 (S709), and the LoRa join server device 100 communicates with the second LoRa terminal device 12 to the application server device 40 In addition to generating and storing the session key required to do the response to the join request of the second LoRa terminal device 12 (S711).

Here, the second LoRa network server device 32 and the LoRa join server device 100 generate resources such as a security key required for the second LoRa terminal device 12 to communicate with the application server device 40 ( S713). Then, the second LoRa network server device 32 requests the LoRa join server device 100 to update the profile for the second LoRa terminal device 12 (S715). Then, the LoRa join server device 100 updates the profile for the second LoRa terminal device 12 including resources such as the security key generated in step S713 according to the request of the second LoRa network server device 32. Afterwards, it responds to the profile update request in step S715 (S717).

Then, the second LoRa network server device 32 transmits a join acceptance message to the first LoRa network server device 31 according to the profile update response of the LoRa join server device 100 (S719), and the first LoRa network server The device 31 transmits the join acceptance message to the second LoRa terminal device 12, thereby accepting the join for the join request in step S701 (S721).

Subsequently, as illustrated in FIG. 4 or FIG. 5 described above, the first LoRa network server device 31 may participate in the service for the second LoRa terminal device 12 during the failure of the second LoRa network server device 32. . However, when a resource such as an application server device 40 and a security key is generated before a failure of the second LoRa network server device 32 occurs, a second LoRa terminal device during a failure of the second LoRa network server device 32 occurs The first LoRa network server device 31 involved in the service for (12) is a second LoRa terminal because it cannot grasp the resources generated between the second LoRa network server device 32 and the LoRa join server device 100 When providing a service for the device 12, the corresponding resource cannot be provided to the LoRa join server device 100. However, the service for the second LoRa terminal device 12 is normally provided because the LoRa join server device 100 updates the profile for the second LoRa terminal device 12 through steps S715 and S717.

As described so far, according to an embodiment of the present invention, when two or more LoRa network server devices are involved in a service for one LoRa terminal device, two or more LoRa network server devices involved in a service for the corresponding LoRa terminal device It is possible to request deletion of information on the corresponding LoRa terminal device. When the LoRa network server device deletes unnecessary information according to the request to delete the information, the quality of the LoRa service is improved because the resources of the LoRa network server device that has been eroded by unnecessary information can be utilized for the LoRa service.

The combination of each block in the block diagram and each step of the flowchart attached to the present invention may be performed by computer program instructions. Since these computer program instructions may be mounted on an encoding processor of a general purpose computer, special purpose computer, or other programmable data processing equipment, the instructions performed through the encoding processor of a computer or other programmable data processing equipment may include each block in the block diagram or In each step of the flowchart, means are created to perform the functions described. These computer program instructions can also be stored on a computer-readable or computer-readable recording medium that can be oriented to a computer or other programmable data processing equipment to implement a function in a particular way, so that it is computer- or computer-readable. It is also possible for the instructions stored in the recording medium to produce an article of manufacture containing instructions means for performing the functions described in each block or flowchart step of the block diagram. Computer program instructions can also be mounted on a computer or other programmable data processing equipment, so a series of operational steps are performed on a computer or other programmable data processing equipment to create a process that is executed by the computer to generate a computer or other programmable data. It is also possible for instructions to perform processing equipment to provide steps for performing the functions described in each block of the block diagram and in each step of the flowchart.

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

The above description is merely illustrative of the technical idea of the present invention, and those skilled in the art to which the present invention pertains may make various modifications and variations without departing from the essential quality of the present invention. Therefore, the embodiments disclosed in the present invention are not intended to limit the technical spirit of the present invention, but to explain, and the scope of the technical spirit 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 interpreted as being included in the scope of the present invention.

According to an embodiment of the present invention, by deleting information on unnecessary LoRa terminal devices stored in the LoRa network server device, since the resources of the LoRa network server device that has been eroded by unnecessary information can be used for the LoRa service, the LoRa service The quality is improved.

The present invention can be applied to various IoT network technology fields as well as LoRa network systems.

11, 12: LoRa terminal device 21, 22, 23, 24: LoRa base station device
31, 32: LoRa network server device 40: application server device
100: LoRa join server device 110: Communication unit
120: data storage unit 130: control unit

Claims (5)

A LoRa (Long Range) terminal device and a LoRa join server device connected to a plurality of LoRa network server devices constituting a LoRa network,
Communication unit for transmitting and receiving data with the LoRa network server device,
A data storage unit for storing a profile including information on a LoRa network server device involved in a service for the LoRa terminal device among the plurality of LoRa network server devices;
It includes a control unit,
The control unit,
When it is determined that two or more LoRa network server devices among the plurality of LoRa network server devices are involved in the service based on the profile, the communication unit may cause at least one of the two or more LoRa network server devices for the LoRa terminal device. Control to request deletion of information
LoRa join server device. According to claim 1,
The service for the LoRa terminal device is in charge of a first allocated LoRa network server device among the plurality of LoRa network server devices, and when a failure of the first LoRa network server device is detected or an allocation command occurs, a plurality of LoRa network servers Among the devices, a second LoRa network server device is in charge of the service for the first LoRa terminal device,
The control unit stores information on the first LoRa network server device and the second LoRa network server device in charge of the service for the first LoRa terminal device by including the profile.
LoRa join server device. According to claim 2,
The control unit generates a session key necessary for communication between the LoRa terminal device and another server device connected to the LoRa network, and then transmits a message requesting the deletion of the information to the second LoRa network server device through the communication unit. doing
LoRa join server device. According to claim 1,
The control unit stores information on the resource, including information on the resource, when information about a resource generated by another server device connected to the LoRa network is received from the LoRa network server device through the communication unit.
LoRa join server device. A method of processing information performed by a LoRa join server device connected to a LoRa (Long Range) terminal device and a plurality of LoRa network server devices constituting a LoRa network,
Storing a profile including information on a LoRa network server device involved in service for the LoRa terminal device among the plurality of LoRa network server devices in a data storage unit;
When it is determined based on the profile that two or more LoRa network server devices among the plurality of LoRa network server devices are involved in the service, deletion of information on the LoRa terminal device is performed on at least one of the two or more LoRa network server devices. Which includes the steps of requesting
Information processing method of LoRa join server device.

Images