WO2019093581A1 - Device and method for providing terminal management and message filtering in lora network - Google Patents

Abstract

A device and a method for managing terminal authentication processing of a LoRa terminal in a LoRa network, filtering a message of the LoRa terminal, and transmitting only the filtered message to a LoRa server are provided. The device comprises: a terminal receiving unit for receiving an uplink message from a LoRa terminal; a terminal managing unit for comparing a device address of the received message with a pre-stored device address to check if the device addresses match and successfully authenticating the LoRa terminal with the matching device address; a filtering unit for filtering the message of the LoRa terminal that has been successfully authenticated and discarding a message that has not been filtered; a server transmitting unit for transmitting the filtered message to a LoRa server; a server receiving unit for receiving a corresponding response message from the LoRa server; and a terminal transmitting unit for transmitting the received response message to the LoRa terminal on a downlink.

Description

Apparatus and method for providing terminal management and message filtering in a roaming network

This application claims priority based on Korean Patent Application No. 2017-0149022, filed on November 9, 2017, the entire contents of which are incorporated herein by reference.

The present invention relates to a LAN network management technology, and relates to an apparatus and method for authenticating and managing whether a Laura terminal connected to a Laura network is registered as a network, filtering a message of a terminal authenticated Laura terminal and transmitting only a valid message to a server will be.

LoRa (Long Range) is a Low Power Wide Area (LPWA) technology that allows objects to communicate with each other. Laura can communicate over 10 km with minimum power consumption.

Laura terminal, Laura gateway (gateway) and Laura network - server (hereafter referred to as server) can define Laura network. In the Laura technology defined so far, the Laura gateway can not manage the Laura terminal because it defines only the message transfer function between Laura server and Laura terminal. Anyone who is based on the Industrial Scientific Medical (ISM) band can use Laura as a Laura terminal. Therefore, the operator of the Laura network not only provides services to the customers subscribed to the service, but also receives data of other users' laura networks, which hinders the provision of exclusive services only for the operator and the customer.

In addition, a laurel network is being operated as a structure in which messages are transmitted from the Laura gateway to the Laura server for all messages coming in through the ISM band. Therefore, the Laura server receives data of all Laura terminals irrespective of whether or not the service is subscribed, so that it is inevitable to use the backhaul between Laura gateway and Laura server inefficiently. In particular, when a wireless backhaul is used, there is a problem that a service provider or a customer has to pay an excessive data cost that is not related to a terminal that wants to provide an actual service.

<Prior Art Literature>

<Patent Literature>

Patent Document 1: Korean Patent No. 10-1731996 (Apr. 25, 2017)

It is an object of the present invention to provide an apparatus and method for managing authentication information of a Laura terminal requesting access to a Laura network and filtering only messages of an authenticated Laura terminal and transmitting the messages to Laura server .

The apparatus determines the download history and the uplink count of the Laura terminal for the terminal whose authentication information has not been confirmed, receives the authentication information from the Laura server according to the determination result, and manages the authentication information by the authentication terminal. If there is no download history and the number of uplinks Another purpose is to destroy the message of the exceeding Laura terminal.

An apparatus for providing management and message filtering of a Laura terminal in a lawn network, the apparatus comprising: a terminal receiver for receiving an uplink message from a Laura terminal; Comparing the device address of the received message with the pre-stored device address, and managing the matching Laura terminal as an authentication success; A filtering unit for filtering the message of the Laura terminal that has been successfully authenticated and discarding the message that has not been filtered; A server transmitting unit for transmitting the filtered message to the Laura server; A server receiving unit for receiving a corresponding response message from the Laura server; And a terminal transmitter for downlinking the received response message to the Laura terminal.

If the message received by the terminal receiver is a message requesting connection to the LAN, the server transmitter transmits the connection request message to the Laura server, and the server receiver receives the connection request from the Laura server, The terminal management unit receives the registration response message including the device address that identifies the valid terminal connected to the network, and the terminal management unit extracts and stores the device address from the received registration response message.

The Laura server extracts the subscriber information of the Laura terminal from the message of the connection request, and when the extracted subscriber information is the subscribed subscriber information, it determines that subscriber authentication is successful and generates the device address, And transmits the registration response message including the device address field based on the format.

The Laura server receives the connection request message through at least one device communicating with the Laura terminal, and transmits the registration response message to each device that has transmitted the message.

The Laura server transmits the registration response message to the other device when receiving the message of the Laura terminal from a device that is different from the device that transmitted the last received message of the Laura terminal.

Wherein the apparatus further comprises a response history management unit for managing a history of downlink transmission of the response message from the Laura server to the Laura terminal and an uplink counting unit for counting uplink times of uplink messages of the Laura terminal, The filtering unit processes the message of the Laura terminal that failed authentication if the downlink hysteresis does not exist and the number of uplinks is less than the reference number.

The uplink counting unit periodically initializes the number of uplinks exceeding the reference number.

The server transmitting unit transmits the authentication failure message to the Laura server, the server receiving unit receives the registration response message or the downlink response message from the Laura server, and the terminal management unit extracts the device address from the received message .

According to another aspect, there is provided a method for providing management and message filtering of a Laura terminal in a Laura network, the method comprising: receiving an uplink message from a Laura terminal; Comparing the device address of the received message with a pre-stored device address, and managing the matching Laura terminal as a successful authentication; Filtering the message of the Laura terminal that has been successfully authenticated, and discarding the message that has not been filtered; Transmitting the filtered message to the Laura server; Receiving a response message from the Laura server; And a terminal transmitting step of downlinking the received response message to the Laura terminal.

According to an aspect of the present invention, the Laura GW device stores the terminal authentication information of the Laura terminal, processes the message based on the stored authentication information so that only messages that have successfully been terminal authenticated by the Laura terminal are filtered, The load on the Laura server can be reduced by selectively transmitting the data to the Laura server.

According to another aspect of the present invention, a downlink history is determined for a Laura terminal that fails terminal authentication of a device address, and the number of uplink times is determined to repeatedly guarantee an opportunity for re-authentication during a reference number of times, It is possible to maximize the authentication opportunity of the laura network connection.

BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings, which are incorporated in and constitute a part of the specification, illustrate preferred embodiments of the invention and, together with the description of the invention below, And should not be construed as interpretation.

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

2 is a schematic internal configuration diagram of the Laura GW apparatus of Fig.

3 is an exemplary diagram of a registration response message received by the Laura GW device of FIG. 1 from the GW server for terminal management.

4 is a flowchart illustrating a terminal management and message filtering using a connection request message according to an exemplary embodiment of the present invention.

FIG. 5 is a flowchart illustrating a terminal management and message filtering using a message in which the Laura GW apparatus shown in FIG. 4 fails in terminal authentication.

Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. Prior to this, terms and words used in the present specification and claims should not be construed as limited to ordinary or dictionary terms, and the inventor should appropriately interpret the concepts of the terms appropriately It should be interpreted in accordance with the meaning and concept consistent with the technical idea of the present invention based on the principle that it can be defined. Therefore, the embodiments described in the present specification and the configurations shown in the drawings are only the most preferred embodiments of the present invention and do not represent all the technical ideas of the present invention. Therefore, It is to be understood that equivalents and modifications are possible.

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

The launder system 100 according to an embodiment of the present invention includes a Laura terminal 110, a Laura GW apparatus 130, and a Laura server 150.

The Laura terminal 110 is a terminal for data communication based on the Laura network.

The Laura GW device 130 manages the network connection of the Laura terminal 110 in the course of intermediating the laura network based data communication between the Laura terminal 110 and the Laura server 150, And transmits the message to the Laura server 150 by filtering the message of the Laura terminal 100. [ Therefore, the Laura server 150 receives the message of the Laura terminal 100 filtered through the Laura GW device 130 instead of receiving all the messages uplinked by the Laura terminal 100, The efficiency of the hole is improved. The success of the filtering is the case where the Laura terminal 110 is registered with the Laura server 150 as a service subscriber.

The Laura server 150 receives the message of the Laura terminal 110 via the Laura GW device 130 and responds to the Laura GW device 130 with the processing result of the message. If the message of the Laura terminal 110 requests a connection to the Laura network, the Laura server 150 determines whether the Laura terminal 110 joins the service. Subscriber authentication is successful if it is a valid service subscriber. The Laura server 150 generates the device address as information for identifying that the Laura terminal 110 that has succeeded in the subscriber authentication is effectively connected to the Laura network.

Here, the Laura server 150 responds to the Laura GW device 130 with a registration response message (e.g., Proprietary) indicating that the Laura terminal 110 includes the device address and is effectively registered in the Laura network. Laura GW device 130 stores the device address of the responded message in the DB for authentication processing.

In addition, the Laura server 150 transmits a connection response message (e.g. Join-Accept) including the device address and allowing the Laura terminal 110 to access the network through the Laura GW device 130 to the Laura terminal 110 Reply.

After the Laura terminal 110 receives the connection response message, the Laura terminal 110 transmits the uplink message to the Laura GW device 130 using the received device address. For reference, the uplink message is a message defined in LoRaWAN. The uplink message of the " Confirmed " type is requested to be transmitted to the Laura terminal 110 after the response message is processed by the Laura server 150. [ The " Unconfirmed " uplink message is processed by the Laura server 150 and the response message is not transmitted to the Laura terminal 110. [

The Laura GW device 130 compares the device address of the Laura terminal 110 of the received message with the device address stored in the DB, determines that the terminal authentication is successful as the device addresses match, . Then, the Laura server 150 selectively receives only the filtered messages through the Laura GW device 130, thereby reducing the processing load.

2 is a schematic internal configuration diagram of the Laura GW apparatus 130 of FIG.

The apparatus of the present invention may be implemented as a computing apparatus corresponding to the Laura GW apparatus 130. [ The computing device may include a memory, a memory controller, one or more processors (CPUs), a peripheral interface, an input / output (I / O) subsystem, a display device, an input device, and a communications circuit. The memory may include high speed random access memory and may also include one or more magnetic disk storage devices, non-volatile memory such as flash memory devices, or other non-volatile semiconductor memory devices. Access to the memory by other components such as the processor and the peripheral interface may be controlled by the memory controller. The memory can store various information and program instructions, and the program is executed by the processor.

The peripheral interface connects the input / output peripheral of the computing device to the processor and memory. The one or more processors execute various software programs and / or a set of instructions stored in memory to perform various functions and process data for the computing device. The I / O subsystem provides an interface between I / O peripheral devices such as display devices, input devices, and peripheral interfaces. The display device can use liquid crystal display (LCD) technology or light emitting polymer display (LPD) technology.

A processor is a processor configured to perform an operation associated with a computing device and to perform instructions, for example, using instructions retrieved from memory to control the reception and manipulation of input and output data between components of the computing device. The communication circuit performs communication via an external port or communication by an RF signal. The communication circuit converts the electrical signal to an RF signal and vice versa, and is capable of communicating with the communication network, other mobile gateway devices, and the communication device through the RF signal.

The Laura GW apparatus 130 according to an embodiment of the present invention includes a terminal receiver 231, a terminal management unit 232, a response history management unit 233, an uplink counting unit 234, a filtering unit 235, 236, a server receiving unit 237, and a terminal transmitting unit 238. [ Assuming that the Laura GW device 130 is a computing device composed of a memory and a processor, each of the components 231 to 218 is implemented in the form of a program, which can be loaded into a memory and executed through the processor.

The terminal receiver 231 receives a message transmitted from the Laura terminal 110 through the Laura network.

The terminal management unit 232 manages terminal authentication processing of the Laura terminal 110 by storing the device address of the registration response message received through the server receiving unit 237 in the DB.

Here, in the management, the terminal management unit 232 inquires the matching device address from the DB using the device address (DevAddr) of the received message as a key, and when the matching device address is inquired, Is determined to be successful. The device address is information generated by the Laura server 150 to authenticate that the Laura server 150 is a subscriber authenticated by the Laura terminal 110 and is a valid terminal of the Laura network. Of course, if the inquiry of the device address fails, the Laura terminal 110 fails authentication.

The filtering unit 235 performs a filtering process on the message in which the terminal authentication is successful and makes the message to be transmitted to the Laura server 150.

If the terminal authentication fails, the filtering unit 235 receives the downlink message from the response history management unit 233 to the Laura terminal 110 in order to request subscriber authentication from the Laura server 150 Look for history. That is, the response history management unit 233 manages the history of the downlink transmission of the response message processed by the Laura server 150 to the Laura terminal 110. If the response history is not retrieved, the message is considered to be discarded because there is no history of service in the laurel network.

In addition, the filtering unit 235 inquires the number of times the uplink message received from the uplink counting unit 234 is received. That is, the uplink counting unit 234 counts the number of uplink messages received from the Laura terminal 110. [

If there is no response history and the number of counts of the inquired uplink is less than or equal to the reference number, the filtering unit 235 filters the message of the Laura terminal 110 and provides an opportunity to be serviced by the Laura server 150 . If there is no response history and the number of counting of the uplink exceeds the reference number, the LaRule terminal 110 regards the subscription information in the Laura network as not being available and the service history to be absent, Discards the message. Of course, by discarding the message, the processing load of the Laura server 150 is reduced.

The server transmitting unit 236 transmits the uplink message of the filtered Laurie terminal 110 to the Laura server 150 to request message processing.

The server receiving unit 237 receives the result of the requested message processing from the Laura server 150.

Here, the server transmitting unit 236 encodes the uplink message (encoded based on the LoRaWAN standard) received from the Laura terminal 110 into the GWMP standard format and transmits it to the Laura server 150 (e.g., tunneling) . The Laura server 150 receives the encoding message from the server transmission unit 236, decodes the encoded message, and processes the message. The Laura server 150 processes the message of the Laura terminal 110 and generates a GWMP compliant response message. The receiver of the response message is the Laura GW device 130 or the Laura terminal 110. For example, when the recipient of the response message is the Laura GW device 130, the Laura server 150 encodes the response message according to the GWMP standard and transmits the response message to the Laura GW device 130. When the receiver of the response message is the Laura terminal 110, the response message encoded based on the LoRaWAN standard is generated, the message is encoded again according to the GWMP standard, and the encoded message is transmitted to the Laura terminal 110 through the Laura GW 130 .

When the server receiving unit 237 receives the GWMP-based response message from the Laura server 150, it checks the post-decoding response message and performs a corresponding process. If the server receiving unit 237 receives the LoRaWAN compliant response message, it transmits a response message to the Laura terminal 110 to process the message.

When the server receiving unit 247 receives the registration response message from the Laura server 150 to be the receiver of the Laura GW unit 130, the Laura GW unit 130 transmits the device address of the received message DB information. If the server receiving unit 237 receives the downlink response message to be the receiver of the Laura terminal 110, the device address of the Laura terminal 110 is extracted from the received message and stored in the DB, Let's do it. Thereafter, the received message is transmitted to Laura terminal 110.

The terminal transmitter 238 wirelessly transmits the GWMP-based decoded downlink response message (encoded based on the LoRaWAN standard) to the Laura terminal 110 at an appropriate time. For reference, since the LoRa standard defines transmission and reception of data at a designated time, a proper time point at which the Laura terminal 110 can receive data is determined.

The Laura server 150 preferably processes the corresponding message according to the contents of the message requested by the Laura terminal 110 and responds to the Laura GW device 130 with the response message of the processing result.

When the Laura terminal 110 initially accesses the Laura network for data communication based on the Laura network, the Laura server 150 receives the connection request message " Join-Request " of the Laura terminal 110, As a result, it replies registration response message " Proprietary " and connection response message " Join-Accept " respectively. The Laura server 150 extracts the subscriber information (e.g., DevEui: Device End user identity) of the Laura terminal from the received message, and when the extracted subscriber information is service subscription subscriber information, the subscriber authentication processing is regarded as successful . As the subscriber authentication is successful, the Laura server 150 generates the device address (e.g., DevAddr) generated by registering the network connection of the Laura terminal 110, and transmits a registration response message including the generated device address do. The Laura server 150 permits network connection of the Laura terminal 110 to which the service subscriber information is confirmed for the initial connection request of the Laura terminal 110 to generate the device address as the network registration information. That is, the device address is generated only when the Laura network connection is permitted. The Laura server 150 transmits a registration response message including information of the device address in the data format described later with reference to FIG.

Here, the case where the Laura server 150 transmits the registration response message for connection authentication of the Laura terminal 110 is as follows. First, when receiving the connection request message of " Join-Request ", the Laura server 150 responds to the registration response message to all Laura GW devices 130 that have transmitted the message. For reference, the Laura terminal 110 communicates messages through at least one Laura GW device 130 capable of communicating. Next, when receiving the "Unconfirmed" uplink message as the nth message, if the Laura GW device 130 of the (n-1) th message and the nth message are different, A response message is transmitted. That is, when the Laura server 150 receives the message of the Laura terminal 110 from the second Laura GW apparatus 130 different from the first Laura GW apparatus 130 that received the last message of the Laura terminal 110 And transmits a registration response message to the second Laura GW apparatus 130 so that the Laura terminal 110 can be managed as a service-authenticated terminal.

FIG. 3 is an exemplary view of a registration response message received by the Laura GW device 130 of FIG. 1 from the Laura server 150 for terminal management.

The PULL_RESP message transmitted from the Laura server 150 to the Laura GW device 130 for connection authentication of the Laura terminal 110 is added with a registration response message form defined in the present invention based on the Laura WAN standard. The registration response message includes the value of the device address DevAddr 330 of the Laura terminal 110 authenticated by the Laura server 150. The Laura GW device 130 then transmits the value of the DevAddr 330 to the DB The mobile terminal 100 can process the terminal authentication for determining the validity of the connection by comparing the DevAddr of the Laura terminal 110 included in the uplink message with the DevAddr 330 stored in the DB. That is, when the Laura GW device 130 confirms that the device address of the Laura terminal 110 that transmitted the uplink message matches the DevAddr 330 stored in the DB, the Laura terminal 110 succeeds in terminal authentication And filters the received message and classifies the received message as a message to be transmitted to the Laura server 150.

While the basic standard of the MAC header is maintained, the value of '111' (0x7) of MType 301 is defined as the identification value of the registration message. The DevAddr 303 is an address of 4 bytes (32 bits) of the Laura terminal 110 registered after the subscriber is confirmed in the Laura server 150. The Laura GW device 130 may store the received device address to authenticate that the Laura terminal 110 is connected to the Laura network and use it to manage the connection of the Laura terminal 110. [

In summary, the terminal management unit 232 determines the value of the registration message received at the server receiving unit 237. [ If the MType 301 is '111', the ACK of the FCtl 305 is '1' and the Count of the Fcnt 307 is '0', the terminal management unit 232 stores the value of the DevAddr 303 in the DB . The DevAddr 303 stored in the DB is then compared with the device address of the uplink message as the device address.

4 is a flowchart illustrating a terminal management and message filtering process by the Laura GW device 130 according to an embodiment of the present invention using a connection request message.

Message communication according to the LoRaWAN standard is involved in the data section between the Laura terminal 110 and the Laura server 150 via the Laura GW device 130. [ Here, in the data section of the Laura GW device 130 and the Laura server 150, data communication based on LoRaWAN standard-based data is performed using GWMP. Then, a LoRaWAN-based encoded message transmitted and received by the Laura terminal 110 is encoded on the GWMP basis between the Laura GW device 130 and the Laura server 150. [

When the Laura terminal 110 initially accesses the Laura network, it transmits a connection request message of " Join-Request " and the Laura GW device 130 receives the message (S401). The Laura GW device 130 pushes the received message to the Laura server 150 if the received message is a connection request message (S403).

When the Push message of the connection request is received, the Laura server 150 compares the subscriber information (DevEUI) of the received message with the stored subscription information, and if the Pusher message is matched, the subscriber authentication of the Laura terminal 110 is successful It is determined that the network connection is valid (S411). When the connection validity of the subscriber is judged, the Laura server 150 registers the Laura terminal 110 information in Laura network information and generates a registration response message including the device address (DevAddr). When the connection is not valid, no additional processing is performed.

The Laura GW apparatus 130 receives a registration response message from the Laura server 150 indicating that the connection of the Laura terminal 110 is valid (S421). The Laura GW device 130 confirms the device address using the field information of FIG. 3 in the MAC header and the frame header of the received registration response message (S423), and stores the confirmed device address (S425).

In addition, the Laurel GW device 130 receives a connection response message (Join-Accept) including the device address from the Laura server 150 in response to the connection request message (Join-Request) of the Laura terminal 110 S427). The Laura GW device 130 terminates the processing of the connection request message by transmitting the received connection response message to the Laura terminal 110 as a downlink response message of connection permission (S429). The Laura terminal 110 transmits the uplink message including the stored device address to the Laura GW device 130 after storing the device address of the received message while the connection of the Laura network is maintained.

Since the connection response message (Join-Accept) is encrypted based on the unique key value and the LoRaWAN between the Laura server 150 and the Laura terminal 110, the Laura GW device 130 includes the connection response message The device address assigned to the Laura terminal 110 can not be extracted. However, in the present invention, in order to process the terminal authentication, the Laura GW device 130 may receive the registration response message from the Laura server 150 and store the device address in step S425.

On the other hand, when the Laura GW device 130 receives the uplink message from the Laura terminal 110, it can process the terminal authentication of the Laura terminal 110 using the device address stored in step S425. At this time, the Laura GW device 130 may or may not store the device address of the Laura terminal 110.

The Laura GW device 130 assumes that it receives an uplink message from any Laura terminal 110 that does not store the device address (S451). The Laura GW device 130 compares the device address of the Laura terminal 110 and the device address stored in the storage step S425 and fails to inquire the device address and thus fails the terminal authentication of the Laura terminal 110 S453). If the uplink message is received from the Laura terminal 110, which is not accompanied with processing of the connection request message in step S401, the Laura terminal 110 fails to terminal authentication. The Laura terminal 110 which has failed in terminal authentication requires additional terminal management and filtering processing through the processing described later with reference to FIG.

On the contrary, it is assumed that the Laura GW device 130 receives the uplink message from the Laura terminal 110 storing the device address (S471). The Laura GW device 130 compares the device address of the Laura terminal 110 and the device address stored in the storage step S425. If the device address matches, the Laura terminal 110 processes the terminal authentication success, The message is processed as a successful filtering (S473). The Laura GW device 130 transmits the filtered message to the Laura server 150 to request message processing (S475). The message is processed by the Laura server 150. If it is a "Confirm" type message, the Laurel GW device 130 receives the downlink response message from the Laura server 150 and transmits the received message to Laura terminal 110.

5 is a flowchart illustrating a terminal management and message filtering using a message in which the Laura GW device 130 in FIG. 4 fails in terminal authentication.

In the terminal authentication failure step S453 of FIG. 4, the Laura GW device 130 inquires the DevAddr 303 matching the device address of the Laura terminal 110, and may fail for the following reason.

The condition that the Laura terminal 110 is brought into the second Laura GW apparatus 130 different from the first Laura GW apparatus 130 while the Laura terminal 110 is moving and the condition that the Laura terminal 110 does not require OTA registration according to the & The Laura terminal 110 fails to authenticate the terminal. At this time, the Laura GW device 130 should be able to confirm the device address of the Laura terminal 110 that failed the terminal authentication from the Laura server 150 and manage it as the authentication terminal. This is because the second Laura GW apparatus 130 must be able to continuously provide the service to the newly entered Laura terminal 110 after the connection is already authenticated through the Laura GW apparatus 130. In addition, in the case of the Laura terminal 110 which does not require registration, management is required as an authentication terminal since the service must proceed without a separate message process of Join-Request. That is, in the case of the Laura terminal 110 in which the terminal authentication fails due to the above reason, the following processing is required for additional terminal management and message filtering.

The Laura GW apparatus 130 determines whether there is a downlink history to Laura terminal 110 (S511). For the Laura terminal 110 having no history of the downlink, the Laura GW apparatus 130 determines the number of uplinks (S513). If the number of uplinks is less than the reference number, the Laura GW unit 130 pushes the message to the Laura server 150 in order to determine an initial connection and guarantee an opportunity to be confirmed as a service subscriber in the Laura server 150 (S515) .

The Laura GW unit 130 fails to confirm as a service subscriber because the Laura terminal 110 having no history of downlink and exceeding the reference number has failed to execute the step S515 under the condition that the step S515 is executed, ) Discards the message (S517). Here, the Laura GW apparatus 130 initializes the number of uplinks for which the reference number is exceeded after a certain period of time, through refresh, and guarantees an opportunity to check again considering the service change due to the registration update of the Laura terminal.

When the Laura server 150 receives the push message, it determines whether the device address of the Laura terminal 110 is valid or a terminal subscribed to the service, and performs authentication processing (S521). If the authentication process fails, the message corresponding to the network connection of the unvalidated Laura terminal 110 is discarded and the message is not answered (S523). In the case of the non-response, the downlink history of the Laura terminal 110 in the Laura GW unit 130 does not occur but increases only the number of uplinks.

When the validity of the Laura terminal 110 is authenticated, the Laura server 150 responds to the Laura GW device 130 with a response message corresponding to the uplink message. In accordance with the uplink message, the Laura server 150 responds to the proprietary registration response message in which the Laura GW device 130 becomes the recipient, or transmits the proprietary registration response message in which the Laura terminal 110 receives the downlink Reply response message.

If the registration response message is answered, the Laurel GW device 130 receives a proprietary registration response message indicating that the connection is valid from the Laura server 150 (S531). The Laura GW device 130 receiving the message from the Laura server 150 ends the processing of the uplink message of the Laura terminal 110 by storing the device address determined to be valid in the DB (S533).

Meanwhile, when the downlink response message is answered, the Laura server 150 transmits a "confirmed-ack" message to the Laura terminal 110 via the Laura GW device 130 as a response message defined in the LoRaWan. At this time, the Laurel GW device 130 receives a downlink message including the device address, not the registration response message, from the Laura server 150 (S531). Here, the Laura GW device 130 extracts the device address (DevAddr) of the Laura terminal 110 included in the downlink message and stores the device address (DevAddr) in the DB for terminal authentication processing (S533). The Laura GW device 130 transmits the downlink response message including the device address to the Laura terminal 110 (S535).

While the present invention has been particularly shown and described with reference to exemplary embodiments thereof, it is to be understood that the invention is not limited to the disclosed exemplary embodiments. It goes without saying that various modifications and variations are possible within the scope of equivalence of the scope.

Claims (16)

1. An apparatus for providing management and message filtering of a Laura terminal in a lawn network,

   A terminal receiver for receiving an uplink message from a Laura terminal;

   Comparing the device address of the received message with the pre-stored device address, and managing the matching Laura terminal as an authentication success;

   A filtering unit for filtering the message of the Laura terminal that has been successfully authenticated and discarding the message that has not been filtered;

   A server transmitting unit for transmitting the filtered message to the Laura server;

   A server receiving unit for receiving a corresponding response message from the Laura server; And

   A terminal transmitter for downlink transmission of the received response message to the Laura terminal

   &Lt; / RTI &gt;
2. The method according to claim 1,

   If the message received at the terminal receiver is a message requesting access to the LAN,

   The server transmitting unit transmits a message of the connection request to the Laura server,

   The server receiving unit receives from the Laura server a registration response message including a device address that identifies that the Laura terminal is a subscriber authenticated and connected to the network,

   Wherein the terminal management unit extracts and stores the device address from the received registration response message.
3. 3. The method of claim 2,

   The Laura server comprises:

   Extracts the subscriber information of the Laura terminal from the message of the connection request, and when the extracted subscriber information is subscribed subscriber information, it determines that subscriber authentication is successful and generates the device address, And transmits the registration response message including the device address field.
4. 3. The method of claim 2,

   The Laura server comprises:

   Receives the connection request message through at least one device communicating with the Laura terminal, and transmits the registration response message to each device that has transmitted the message.
5. 3. The method of claim 2,

   The Laura server comprises:

   And transmits the registration response message to the other device when receiving the message of the Laura terminal from a device other than the device that transmitted the last received message of the Laura terminal.
6. The method according to claim 1,

   A response history management unit for managing a history of downlink transmission of the response message from the Laura server to the Laura terminal,

   Further comprising an uplink counting unit for counting uplink times of uplink messages of the Laura terminal,

   Wherein the filtering unit performs a filtering process on the message of the failed Laura terminal if the downlink hysteresis does not exist and the number of uplinks is less than or equal to the reference number.
7. The method according to claim 6,

   Wherein the uplink-

   And periodically initializes the number of uplink times exceeding the reference number.
8. The method according to claim 6,

   The server transmitting unit transmits the authentication failure message to the Laura server,

   Wherein the server receiving unit receives the registration response message or the downlink response message from the Laura server,

   Wherein the terminal management unit extracts and stores the device address from the received message.
9. A method for providing management and message filtering of a Laura terminal in a roaming network,

   Receiving a uplink message from a Laura terminal;

   Comparing the device address of the received message with a pre-stored device address, and managing the matching Laura terminal as a successful authentication;

   Filtering the message of the Laura terminal that has been successfully authenticated, and discarding the message that has not been filtered;

   Transmitting the filtered message to the Laura server;

   Receiving a response message from the Laura server; And

   And transmitting the received response message to the Laura terminal on the downlink.
10. 10. The method of claim 9,

    If the message received in the terminal receiving step is a message requesting access to the LAN,

    In the transmitting step, a message of the connection request is transmitted to the Laura server,

    Receiving a registration response message including a device address that identifies the valid terminal of the Laura terminal as a subscriber authenticated and connected to the network from the Laura server,

    Wherein the device address is extracted and stored from the registration response message in the managing step.
11. 11. The method of claim 10,

    In the receiving step,

    The Laura server extracts the subscriber information of the Laura terminal from the message of the connection request, and when the extracted subscriber information is the subscribed subscriber information, it determines that subscriber authentication is successful and generates the device address, And sending the registration response message including the device address field based on the format.
12. 11. The method of claim 10,

    The Laura server comprises:

    Receiving a message of the connection request through at least one device communicating with the Laura terminal, and transmitting the response message to each device that has transmitted the message.
13. 11. The method of claim 10,

    The Laura server comprises:

    When receiving the message of the Laura terminal from a device that is different from the device that transmitted the last received message of the Laura terminal, transmits the registration response message to the other device.
14. 10. The method of claim 9,

    Wherein the processing comprises:

    Managing a history of downlink transmission of the response message from the Laura server to the Laura terminal; and

    Further comprising counting an uplink number of uplink messages of the Laura terminal,

    And filtering the message of the failed Laura terminal if the downlink history is absent and the number of uplinks is less than or equal to the reference number.
15. 15. The method of claim 14,

    Wherein the counting step comprises:

    And periodically initializing the number of uplink times exceeding the reference number.
16. 14. The method of claim 13,

    Wherein the authentication failure message is transmitted to the Laura server in the transmitting step,

    Receiving a registration response message or a downlink response message from the Laura server in the receiving step,

    Wherein the device address is extracted and stored from the received response message in the managing step.

Images