KR102253174B1 - Method and apparatus for managing terminal in LoRa communication environment - Google Patents

Abstract

The present invention relates to a method and device for detecting and managing an abnormal terminal in a long range (LoRa) communication environment. According to an embodiment of the present invention, the method for detecting and managing an abnormal terminal in a LoRa communication environment in a terminal management server comprises the steps of: receiving data from a LoRa terminal; checking a terminal management policy of the LoRa terminal and checking a time for which uplink data is allowed; verifying whether a data reporting period of the LoRa terminal is a normal reporting period by comparing the data reception time with the checked allowable time; and if the verification is successful, forwarding the data to a customer communication device.

Description

Terminal management method and apparatus in LoRa communication environment TECHNICAL FIELD [Method and apparatus for managing terminal in LoRa communication environment]

The present invention relates to a method and apparatus for detecting and managing an abnormal terminal in a LoRa (Long Range) communication environment.

LoRa (Long Range) is a Low Power Wide Area (LPWA) technology that helps objects to communicate with each other. LoRa technology is applied to electronic devices that can be used for a long time without battery replacement or charging because communication is possible over 10 km with minimal power consumption.

The LoRa terminal, the LoRa gateway (LoRa base station), and the server can be defined as LoRa networks. A LoRa wireless section is formed between the LoRa terminal and the LoRa gateway, and a wired or wireless IP backhaul is formed between the LoRa gateway and the LoRa server. In the LoRa network service, the LoRa terminal receives the network service from the LoRa server through data relay of the LoRa gateway.

After completing the registration procedure with the server, the LoRa terminal transmits data to the server at predetermined periodic intervals.

In general, in order to transmit uplink data (that is, data transmitted in the gateway direction) from a LoRa terminal, a data usage fee for the LoRa terminal is previously concluded with a communication company. The usage plan may be agreed upon to generate uplink data from a LoRa terminal according to a specified time slot, or a usage plan may be negotiated to generate uplink data only at a designated location. For example, a LoRa terminal that transmits uplink data once an hour may be charged with a monthly rate of 2,000 won, and a LoRa terminal that transmits uplink data once a day may be charged with a monthly rate of 1,000 won. . In addition, a loRa terminal with mobility may be charged an additional charge of 500 won per month compared to a non-mobile terminal.

However, even if such a fee agreement is signed, it is impossible to check in real time whether the LoRa terminal is properly keeping it.

An object of the present invention is to provide a terminal management method and apparatus for checking in real time whether a terminal management policy based on a fee agreement is normally observed by a LoRa terminal.

Other objects and advantages of the present invention can be understood by the following description, and will be more clearly understood by examples of the present invention. In addition, it will be easily understood that the objects and advantages of the present invention can be realized by the means shown in the claims and combinations thereof.

According to a first aspect of the present invention for achieving the above object, a method of detecting and managing an abnormal terminal in a LoRa communication environment in a terminal management server includes: receiving data from a LoRa terminal; Checking a terminal management policy of the Laura terminal and checking a time when uplink data is allowed; Comparing the data reception time with the checked allowed time, and verifying whether the data reporting period of the LoRa terminal is a normal reporting period; And if the verification is successful, transferring the data to a customer communication device.

The method may further include, if the verification fails, suspending transmission of the data to the customer communication device, and transmitting a warning message to the customer communication device.

The verifying may include, if the mobility non-support information is recorded in the terminal management policy, confirming a gateway that relays the data; And additionally verifying whether the gateway that relayed the data is a communication allowed gateway and is included in the terminal management policy.

The method, if the verification fails, increases the number of violations of the terminal management policy, checks whether the increased number of violations exceeds a threshold number, and sets it as an abnormal terminal of the Laura terminal when the number of violations exceeds a threshold number. It may further include the step of canceling the registration.

The method may include, after the step of canceling the registration, when a registration request is received from the Laura terminal, rejecting the registration request as the Laura terminal is set as an abnormal terminal.

The above methods may be executed in the form of a computer program recorded on a computer-readable recording medium.

According to a second aspect of the present invention for achieving the above object, a terminal management apparatus for detecting and managing an abnormal terminal in a LoRa communication environment includes: a storage unit for storing a terminal management policy of a LoRa terminal; And when receiving data from the LoRa terminal, checks the gateway that relayed the data, verifies whether the verified gateway is included in the terminal management policy as a communication allowed gateway, and if the verification is successful, the data It includes a terminal verification unit for transmitting the to the customer communication device.

The terminal verification unit may perform the verification when it is recorded in the terminal management policy that the mobility of the Laura terminal is not supported.

The terminal verification unit checks a time when uplink data is allowed in the terminal management policy, compares the data reception time and the allowed time, and adds whether the data reporting period of the Laura terminal is a normal reporting period. Can be verified.

If the verification fails, the terminal verification unit may increase the number of violations of the terminal management policy, and cancel the registration of the Laura terminal when the increased number of violations exceeds a threshold number.

The present invention creates a terminal management policy based on a rate agreement, compares the reporting period of data received from the LoRa terminal or the report path of the data with the terminal management policy, and determines whether the LoRa terminal complies with the rules according to the rate agreement. It has the effect of monitoring in real time.

In addition, the present invention has the advantage of blocking uplink data generated in the LoRa terminal in advance by canceling the registration of the LoRa terminal when the LoRa terminal violates the terminal management policy.

In addition, when the LoRa terminal violates the terminal management policy, the load on the LoRa network is increased.The present invention rejects registration of the LoRa terminal violating the terminal management policy and blocks uplink data generated from the LoRa terminal, There is an advantage of preventing the phenomenon that the load of the LoRa network is increased in advance due to an abnormal LoRa terminal.

The following drawings attached to the present specification illustrate preferred embodiments of the present invention, and serve to further understand the technical idea of the present invention along with specific details for carrying out the present invention, so the present invention is described in such drawings. It is limited to the matters and should not be interpreted.
1 is a diagram illustrating a LoRa communication system according to an embodiment of the present invention.
2 is a diagram illustrating a terminal management server according to an embodiment of the present invention.
3 is a flowchart illustrating a method of verifying a data reporting period of a LoRa terminal in a terminal management server according to an embodiment of the present invention.
4 is a flowchart illustrating a method of verifying mobility of a LoRa terminal in a terminal management server according to an embodiment of the present invention.
5 is a flowchart illustrating a method of canceling registration of a LoRa terminal according to a terminal management policy violation in a terminal management server according to an embodiment of the present invention.

The above-described objects, features, and advantages will become more apparent through the following detailed description in connection with the accompanying drawings, whereby those of ordinary skill in the technical field to which the present invention pertains can easily implement the technical idea of the present invention. There will be. In addition, in describing the present invention, when it is determined that a detailed description of a known technology related to the present invention may unnecessarily obscure the subject matter of the present invention, a detailed description thereof will be omitted. Hereinafter, a preferred embodiment according to the present invention will be described in detail with reference to the accompanying drawings.

1 is a diagram illustrating a LoRa communication system according to an embodiment of the present invention.

As shown in Fig. 1, the LoRa communication system according to the embodiment of the present invention includes at least one LoRa terminal 100, a plurality of gateways 200-N, a terminal management server 300, an operator terminal 400, and a customer. And a communication device 500. Message communication according to the LoRaWAN standard is performed between the LoRa terminal 100 and the gateway 200-N. In addition, data communication based on GWMP (GateWay Message Protocol) is performed between the gateway 200-N and the terminal management server 300.

The LoRa terminal 100 performs wireless communication based on the LoRa network with the gateway 200-N. The Laura terminal 100 includes a user's mobile terminal, an Internet of Thing (IoT) communication device, and the like. The Laura terminal 100 counts a preset reporting period, and transmits the data extracted according to a preloaded algorithm to the gateway 200-N when the reporting period arrives. The data may be one or more of status data of the lora terminal 100, measurement data using a sensor, location data, and the like. The Laura terminal 100 first performs a registration (ie, join) procedure with the terminal management server 300 before transmitting data. The LoRa terminal 100 communicates with one or more gateways 200-N through an Industrial Scientific and Medical (ISM) band.

The gateway 200-N relays data between the LoRa terminal 100 and the terminal management server 300. The gateway 200 -N may wirelessly communicate with the Laura terminal 100 and may communicate with the terminal management server 300 by wire. The gateway 200 -N transmits the data received from the LoRa terminal 100 to the terminal management server 300.

The operator terminal 400 is a personal computer, laptop computer, mobile terminal, server, etc. owned by the operator, and provides a terminal management policy based on the rate agreement (i.e., rate plan) to which the LoRa terminal 100 has subscribed to the terminal management server 300. send. In other words, the operator confirms the fee agreement for the LoRa terminal 100 signed by the customer, and transmits the identification information of the LoRa terminal 100, the terminal management policy, and the identification information of the customer's communication device 500 to the terminal management server. By transmitting to 300, data related to the terminal management policy are stored in the terminal management server 300. The reporting period of the Laura terminal 100 may be recorded in the terminal management policy. In addition, whether or not mobility is supported may be recorded in the terminal management policy, and when mobility is not supported, identification information of one or more gateways allowed to communicate is recorded in the terminal management policy.

The customer communication device 500 is a communication device used by a customer who has received a report of data from the Laura terminal 100. The customer communication device 500 may be any one of a personal computer, a notebook computer, a mobile terminal, a server, and the like. When the Laura terminal 100 complies with the terminal management policy, the customer communication device 500 may receive data of the Laura terminal 100 from the terminal management server 300.

The terminal management server 300 is a device that manages the lora terminal 100, and authenticates whether the lora terminal 100 is registered, and selectively permits the registration of the lora terminal 100 according to the authentication. In addition, the terminal management server 300 receives the terminal management policy from the operator terminal 400, and continuously checks whether the LoRa terminal 100 is reporting uplink data by observing the rules recorded in the terminal management policy. Monitor.

2 is a diagram illustrating a terminal management server according to an embodiment of the present invention.

The terminal management server 300 according to an embodiment of the present invention includes a memory, a memory controller, one or more processors (CPU), peripheral interfaces, input/output (I/O) subsystems, a display device, an input device, and a communication circuit. I can.

The memory may include high-speed random access memory, and may also include one or more magnetic disk storage devices, nonvolatile memory such as flash memory devices, or other nonvolatile semiconductor memory devices. Access to memory by other components such as the processor and peripheral interfaces can be controlled by the memory controller. The memory can store various types of information and program instructions, and programs are executed by the processor.

The peripheral interface connects the input/output peripheral devices of the terminal management server 300 to the processor and memory. One or more processors execute various software programs and/or instruction sets stored in a memory to perform various functions for the terminal management server 300 and process data. The I/O subsystem provides an interface between input and output peripherals, such as display devices and input devices, and peripheral interfaces. The display device may use liquid crystal display (LCD) technology or light emitting polymer display (LPD) technology.

The processor is a processor configured to perform an operation related to the terminal management server 300 and execute instructions. For example, by using the instructions retrieved from the memory, receiving input and output data between components of the terminal management server 300 and You can control the operation. The communication circuit performs communication through an external port or communication by an RF signal. The communication circuit converts the electrical signal to an RF signal or vice versa, through which it can communicate with a communication network, other mobile gateway devices and communication devices.

Referring to FIG. 2, the terminal management server 300 according to an embodiment of the present invention includes a storage unit 310, a policy information acquisition unit 320, an authentication unit 330, and a terminal verification unit 340, and , These components may be implemented as software, stored in a memory, and executed by a processor, or may be implemented as a combination of software and hardware.

The storage unit 310 is a storage means such as a memory and a disk device, and stores authentication information and a terminal management policy of the roller terminal 100. As the authentication information of the lora terminal 100, identification information of the lora terminal 100, identification information of an application mounted on the lora terminal 100, and a nonce are stored.

The policy information acquisition unit 320 receives and stores a terminal management policy for the Laura terminal 100 from the operator terminal 400. That is, the policy information acquisition unit 320 is a terminal management policy based on the rate agreement (i.e., rate plan) to which the Laura terminal 100 has subscribed, the identification information of the Laura terminal 100, and the identification of the customer's communication device 500 Information is received from the operator terminal 400, and the received identification information of the Laura terminal 100, the identification information of the customer communication device 500, and a terminal management policy are mapped and stored in the storage unit 310. In the terminal management policy, one or more of a time zone in which data can be received (ie, a time zone in which uplink data can be transmitted from a LoRa terminal) and information on whether or not mobility is supported may be recorded. When information for which mobility is not supported is recorded in the terminal management policy, identification information of one or more gateways to which communication is permitted is recorded in the terminal management policy.

When receiving the registration request message from the Laura terminal 100, the authentication unit 330 compares the authentication information included in the registration request message with the authentication information of the Laura terminal 100 stored in the storage unit 310, and (100) is authenticated. Specifically, the authentication unit 330 checks the identification information of the lora terminal 100, the identification information of the application, and a random number from the authentication information received from the lora terminal 100, and the identification information of the lora terminal 100, the application By checking whether the identification information and the authentication information having a random number are stored in the storage unit 310, the Laura terminal 100 can be authenticated.

If the authentication of the lora terminal 100 fails, the authentication unit 330 does not permit registration of the lora terminal 100 and transmits a join reject message to the lora terminal 100. On the other hand, if the authentication of the lora terminal 100 is successful, the authentication unit 330 registers the lora terminal 100, generates a security key for the lora terminal 100, and transmits it to the lora terminal 100. . The security key is a symmetric key or an asymmetric key. When the security key is an asymmetric key, the authentication unit 330 may transmit the encryption key to the LoRa terminal 100.

The terminal verification unit 340 checks whether the reporting period of the data received from the Laura terminal 100 is a normal reporting period, based on the management policy of the Laura terminal 100 stored in the storage unit 310, and It is verified whether the data transmitted from 100) is data received through the permitted gateway 200-N (ie, data received through the permitted routing path).

The terminal verification unit 340 checks the identification information of the customer communication device 500 mapped with the identification information of the Laura terminal 100 when the Laura terminal 100 complies with the terminal management policy, and the customer having the identification information The data received from the Laura terminal 100 is transmitted to the communication device 500. On the other hand, if the terminal verification unit 340 transmits data in a state in which the Laura terminal 100 does not comply with the terminal management policy, the terminal verification unit 340 will not transmit the data received from the Laura terminal 100 to the customer communication device 500. And send a warning message to the customer communication device 500.

The terminal verification unit 340 counts the number of times that the Laura terminal 100 violates the management policy, and when the number of violations of the management policy exceeds a preset threshold number, the Laura terminal 100 is used as an abnormal terminal. By setting, the registration of the Laura terminal 100 is canceled. Thereafter, even if a re-registration request message is received from the Laura terminal 100, the authentication unit 330 rejects the registration of the Laura terminal 100 because the Laura terminal 100 is set as an abnormal terminal.

3 is a flowchart illustrating a method of verifying a data reporting period of a LoRa terminal in a terminal management server according to an embodiment of the present invention.

Referring to FIG. 3, the policy information acquisition unit 320 of the terminal management server 300 includes a terminal management policy including a time zone allowed when the roller terminal 100 transmits uplink data, and The identification information and the identification information of the customer communication device 500 are received from the operator terminal 400 and stored in the storage unit 310 (S301).

In the state where the terminal management policy is stored in this way, the authentication unit 330 of the terminal management server 300 receives a join request message from the Laura terminal 100 (S303). Then, the authentication unit 330 compares the authentication information included in the registration request message with the authentication information of the roller terminal 100 stored in the storage unit 310 to authenticate the roller terminal 100 (S305). Specifically, the authentication unit 330 checks the identification information of the lora terminal 100, the identification information of the application, and a random number from the authentication information received from the lora terminal 100, and the identification information of the lora terminal 100, the application By checking whether the identification information and the authentication information having a random number are stored in the storage unit 310, the Laura terminal 100 can be authenticated. If the authentication of the lora terminal 100 fails, the authentication unit 330 does not permit registration of the lora terminal 100 and transmits a join reject message to the lora terminal 100. On the other hand, the authentication unit 330, if the authentication of the lora terminal 100 is successful, registers the lora terminal 100, generates a security key for the lora terminal 100, and registers including this security key A join accept message is transmitted to the Laura terminal 100 (S307).

Then, the Laura terminal 100 stores the security key and starts counting whether or not the reporting period has arrived (S309). When the first reporting period arrives, the Laura terminal 100 generates data to be reported, and transmits the data to the terminal management server 300 via the surrounding gateway 200-N (S311). At this time, the Laura terminal 100 may encrypt the data using the security key and then transmit the data to the terminal management server 300.

Next, the terminal verification unit 340 checks the time zone allowed to transmit the uplink data in the terminal management policy stored in the storage unit 310, and the reporting period of the data received from the LoRa terminal 100 (i.e., data The time at which is received) is compared with the allowed time period to determine whether or not the data is reported in the normal period. The terminal verification unit 340 receives the data received from the LoRa terminal 100 as the data report period is included in the allowed time period (that is, it is a normal period data report). ) Is transmitted (S313, S315). In this case, the terminal verification unit 340 may decrypt the encrypted data using the security key and then transmit the decrypted data to the customer communication device 500.

In this case, when data is transmitted from the LoRa terminal at a normal period (ie, an allowed time period), the data is transmitted to the customer communication device 500 by the terminal management server 300.

On the other hand, when the next reporting cycle arrives, the Laura terminal 100 generates data to be reported, and transmits the data to the terminal management server 300 via the neighboring gateway 200-N (S317). . At this time, the Laura terminal 100 may encrypt the data using the security key and then transmit the data to the terminal management server 300.

Next, the terminal verification unit 340 checks the time period allowed for transmitting the uplink data again in the terminal management policy stored in the storage unit 310, and the reporting period of the data received from the loRa terminal 100 (ie , Data reception time) and the allowed time period are compared to determine whether the data is reported in the normal period. The terminal verification unit 340 increases the number of violations of the terminal management policy by '1' as the reporting period of the data is not included in the allowed time period (i.e., it is an abnormal period of data reporting), and A warning message warning that the terminal 100 has sent data at an unauthorized time is transmitted to the customer communication device 500 (S321). The terminal verification unit 340 may not transmit the data received from the Laura terminal 100 to the customer communication device 500 because the Laura terminal 100 violates the terminal management policy.

When data is transmitted from the LoRa terminal at such an abnormal period (i.e., the allowed time period), the data is not transmitted to the customer communication device 500 by the terminal management server 300 and a warning message is sent to the customer communication device instead. It can be transmitted to 500.

4 is a flowchart illustrating a method of verifying mobility of a LoRa terminal in a terminal management server according to an embodiment of the present invention.

In FIG. 4, it is described that the loRa terminal 100 is not supported with mobility.

Referring to FIG. 4, the policy information acquisition unit 320 of the terminal management server 300 includes a terminal management policy including information on mobility non-support for the LoRa terminal 100 and identification information of one or more gateways that are allowed to communicate, the The identification information of the LoRa terminal 100 and the identification information of the customer communication device 500 are received from the operator terminal 400 and stored in the storage unit 310 (S401). In FIG. 4, it is assumed that the identification information of the gateway 1 200-1 is stored in the terminal management policy as gateway identification information for which communication is permitted.

In the state where the terminal management policy is stored in this way, the authentication unit 330 of the terminal management server 300 receives a join request message from the Laura terminal 100 (S403). Then, the authentication unit 330 compares the authentication information included in the registration request message with the authentication information of the roller terminal 100 stored in the storage unit 310 to authenticate the roller terminal 100 (S405). If the authentication of the lora terminal 100 fails, the authentication unit 330 does not permit registration of the lora terminal 100 and transmits a join reject message to the lora terminal 100. On the other hand, the authentication unit 330, if the authentication of the lora terminal 100 is successful, registers the lora terminal 100, generates a security key for the lora terminal 100, and registers including this security key A join accept message is transmitted to the Laura terminal 100 (S407).

Next, the Laura terminal 100 stores the security key and starts counting whether or not the reporting period arrives. When the first reporting period arrives, the Laura terminal 100 generates data to be reported, and transmits the data to the terminal management server 300 via the neighboring gateway 1 200-1 (S409). At this time, the Laura terminal 100 may encrypt the data using the security key and then transmit the data to the terminal management server 300.

Next, the terminal verification unit 340 confirms that the mobility of the LoRa terminal 100 is not supported in the terminal management policy stored in the storage unit 310, and at least one gateway identification information (i.e., gateway 1) that is allowed to communicate. Identification information). And the terminal verification unit 340 confirms that the gateway that relayed the data of the LoRa terminal 100 is the gateway 1 (200-1), and confirms that the gateway 1 (200-1) is a gateway through which communication is allowed, Accordingly, it is determined that the data of the LoRa terminal 100 is reported through a normal routing path (S411). Subsequently, the terminal verification unit 340 transmits the data reported by the Laura terminal 100 to the customer communication device, as the gateway 1 (200-1), which relayed the data of the Laura terminal 100, is a gateway that is allowed to communicate. It passes to 500 (S413). In this case, the terminal verification unit 340 may decrypt the encrypted data using the security key and then transmit the decrypted data to the customer communication device 500.

When the data of the LoRa terminal is received through the allowed gateway 1 100, the data is transmitted to the customer communication device 500 by the terminal management server 300.

Meanwhile, when the next reporting period arrives after moving to another location (ie, after moving to the vicinity of Gateway 2), the LoRa terminal 100 generates data to be reported, and sends this data to the surrounding gateway 2 ( 200-2) and transmitted to the terminal management server 300 (S415). At this time, the Laura terminal 100 may encrypt the data using the security key and then transmit the data to the terminal management server 300.

Next, the terminal verification unit 340 of the terminal management server 300 confirms again that the mobility of the LoRa terminal 100 is not supported in the terminal management policy stored in the storage unit 310, and at least one communication is permitted. Reconfirm the gateway identification information (ie, gateway 1 identification information). In addition, the terminal verification unit 340 confirms that the gateway that relayed the data of the LoRa terminal 100 is the gateway 2 200-2, and confirms that the gateway 2 200-2 is a gateway for which communication is not permitted. Accordingly, it is determined that the data of the LoRa terminal 100 is reported through an abnormal routing path (S417).

Subsequently, the terminal verification unit 340 increases the number of violations of the terminal management policy by '1' as the gateway 2 200-2 relaying the data of the LoRa terminal 100 is a gateway that is not allowed to communicate, A warning message warning that the LoRa terminal 100 has transmitted data through an unauthorized gateway is transmitted to the customer communication device 500 (S419). The terminal verification unit 340 may not transmit the data received from the Laura terminal 100 to the customer communication device 500 because the Laura terminal 100 violates the terminal management policy.

When the loRa terminal 100, which is not supported by mobility, transmits data through an unauthorized gateway, the data is not transmitted to the customer communication device 500 by the terminal management server 300, and a warning message is sent to the customer instead. It is transmitted to the communication device 500.

On the other hand, when mobility support information is recorded in the terminal management policy, the terminal verification unit 340 of the terminal management server 200 communicates the data of the LoRa terminal 100 to the customer regardless of the change of the gateway 200-N. It can be delivered to the device 500.

5 is a flowchart illustrating a method of canceling registration of a LoRa terminal according to a terminal management policy violation in a terminal management server according to an embodiment of the present invention.

5, when the number of violations of the terminal management policy increases, the terminal verification unit 340 of the terminal management server 300 checks whether the number of violations of the increased terminal management policy exceeds a preset threshold number. do. If the number of violations of the terminal management policy does not exceed the threshold number, the terminal verification unit 340 maintains the registration of the Laura terminal 100 as it is.

On the other hand, if the number of violations of the terminal management policy exceeds the threshold number (S501), the terminal verification unit 340 sends a communication failure notification message to the customer communication device 500 notifying that communication with the LoRa terminal is disconnected. It transmits to the communication device 500 (S503).

Subsequently, the terminal verification unit 340 sets the lora terminal 100 as an abnormal terminal, transmits a join reject message to the lora terminal 100 (S505), and Cancel registration. When the registration of the lora terminal 100 is canceled in this way, the data reported from the lora terminal 100 is not transmitted to the customer communication device 500.

Thereafter, the Laura terminal 100 may transmit a join request rejecting registration to the terminal management server 300 again (S507). Then, the authentication unit 330 of the terminal management server 300 rejects the registration of the Laura terminal 100 as the Laura terminal 100 is set as an abnormal terminal, and sends a join request to the Laura terminal. It transmits to the terminal 100, and maintains the deregistration state of the Laura terminal 100 (S509).

As described above, according to an embodiment of the present invention, by creating a terminal management policy based on a fee agreement, comparing and analyzing the data received from the LoRa terminal with the terminal management policy, the LoRa terminal determines the rules according to the rate agreement. Compliance can be monitored in real time. In addition, according to the present invention, when the LoRa terminal violates the rules according to the tariff agreement, by canceling the registration of the LoRa terminal, uplink data generated in the LoRa terminal can be blocked in advance.

While this specification includes many features, such features should not be construed as limiting the scope or claims of the invention. In addition, features described in separate embodiments herein may be combined and implemented in a single embodiment. Conversely, various features described in a single embodiment in the present specification may be individually implemented in various embodiments, or may be properly combined and implemented.

Although the operations have been described in a specific order in the drawings, it should not be understood that such operations are performed in a specific order as shown, or as a series of consecutive sequences, or that all described operations are performed to obtain a desired result. . Multitasking and parallel processing can be advantageous in certain environments. In addition, it should be understood that classification of various system components in the above-described embodiments does not require such classification in all embodiments. The above-described program components and systems may generally be implemented as a package in a single software product or multiple software products.

The method of the present invention as described above may be implemented as a program and stored in a recording medium (CD-ROM, RAM, ROM, floppy disk, hard disk, magneto-optical disk, etc.) in a form that can be read by a computer. This process can be easily performed by a person of ordinary skill in the art to which the present invention pertains, and thus will not be described in detail.

The present invention described above, for those of ordinary skill in the art to which the present invention pertains, various substitutions, modifications and changes are possible within the scope of the technical spirit of the present invention. It is not limited by the drawings.

100: communication terminal
200: gateway
300: terminal management server
310: storage
320: Policy information acquisition unit
330: authentication department
340: terminal verification unit
400: operator terminal
500: customer communication device

Claims (12)

As a method of detecting and managing an abnormal terminal in a LoRa communication environment in a terminal management server,
Receiving data from a Laura terminal;
Checking a terminal management policy of the Laura terminal and checking a time when uplink data is allowed;
Comparing the data reception time with the checked allowed time, and verifying whether the data reporting period of the LoRa terminal is a normal reporting period; And
If the verification is successful, including the step of transferring the data to the customer communication device,
The verifying step,
If the mobility non-support information is recorded in the terminal management policy, checking a gateway that relays the data; And
And further verifying whether or not the gateway relaying the data is a communication allowed gateway and is included in the terminal management policy. The method of claim 1,
If the verification fails, the step of suspending the transmission of the data to the customer communication device, and transmitting a warning message to the customer communication device. delete As a method of detecting and managing an abnormal terminal in a LoRa communication environment in a terminal management server,
Receiving data from a Laura terminal;
Checking a terminal management policy of the Laura terminal and checking a time when uplink data is allowed;
Comparing the data reception time with the checked allowed time, and verifying whether the data reporting period of the LoRa terminal is a normal reporting period;
If the verification is successful, transferring the data to a customer communication device; And
If the verification fails, increase the number of violations of the terminal management policy, check whether the increased number of violations exceeds the threshold number, and set it as an abnormal terminal of the Laura terminal, and cancel the registration of the Laura terminal. Terminal management method comprising the step of. The method of claim 4,
After the step of canceling the registration,
If a registration request is received from the Laura terminal, the terminal management method further comprising the step of rejecting the registration request as the Laura terminal is set as an abnormal terminal. The method of claim 1,
Before the receiving step,
Terminal management method further comprising the step of receiving and storing the terminal management policy from the operator terminal. A computer program that executes the method according to any one of claims 1, 2, and 4 to 6 and is recorded on a computer-readable recording medium. In a terminal management device that detects and manages an abnormal terminal in a LoRa communication environment,
A storage unit for storing the terminal management policy of the Laura terminal; And
Upon receiving the data from the LoRa terminal, the gateway that relayed the data is checked, and after verifying whether the confirmed gateway is included in the terminal management policy as a communication allowed gateway, the data is transmitted when the verification is successful. Including a terminal verification unit transmitted to the customer communication device,
The terminal verification unit,
A terminal management device that performs the verification when the mobility of the LoRa terminal is not supported and is recorded in the terminal management policy. delete The method of claim 8,
The terminal verification unit,
If the verification fails, the terminal management device, which suspends the transmission of the data to the customer communication device, and transmits a warning message to the customer communication device. The method of claim 8,
The terminal verification unit,
Checking a time when uplink data is allowed in the terminal management policy, comparing the data reception time with the allowed time, and further verifying whether the data reporting period of the LoRa terminal is a normal reporting period. Terminal management device. The method of claim 11,
The terminal verification unit,
If the verification fails, the number of violations of the terminal management policy is increased, and when the increased number of violations exceeds a threshold number, the registration of the LoRa terminal is canceled.

Images