KR101885592B1 - Networlk device, management device, and system having the device and the server, control method thereof - Google Patents

Abstract

The present invention proposes a method for re-opening an IoT terminal suitable for a pseudo-opening environment, and discloses a technique for improving the performance of the Internet (IoT) service.

Description

TECHNICAL FIELD [0001] The present invention relates to a network device, a management device, a system including the same, and a method of operating the device.

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to Internet (IoT) technology, and more particularly, to a technique for realizing a re-activation scheme of an IoT terminal suitable for a pseudo-activation environment.

Internet of Things (IoT) technology, which connects information of living things through wired / wireless networks in various fields such as healthcare, remote meter reading, smart home, smart car and smart farm, is attracting attention.

The following is a brief description of the IoT network structure for providing the Internet (IoT) service based on the Internet (IoT) technology.

The IoT network includes a remote terminal IoT terminal, a client terminal having an object Internet application (hereinafter referred to as " IoT application ") for checking the data of the remote IoT terminal and controlling the IoT terminal, an IoT terminal and a client terminal And a gateway (eg, a base station) that performs signal transmission and reception between the network device (or the IoT app server), the IoT terminal, and the network device that connect the network to each other via a wired or wireless network.

In addition, the IoT network may further include a Customer Care & Billing System (CCBS) apparatus for subscriber management using the Internet Internet (IoT) service. The CCBS apparatus manages all the subscriber information registered / changed in the course of using the Internet (IoT) service. In particular, the CCBS apparatus transmits all information related to service opening, termination, re-opening and pausing to the subscriber's IoT terminal .

That is, when the service opening / re-opening of the IoT terminal of a specific subscriber is requested, the CCBS device transmits subscriber information necessary for opening / re-opening to the network device. On the other hand, when the service termination / pause is requested for the IoT terminal of the specific subscriber, the CCBS apparatus requests the network apparatus to delete the subscriber information for the specific subscriber.

Meanwhile, in the IoT network, an OTA (Over The Activation) procedure is performed to open the IoT terminal. To open the OTA, a Device Extend Unique Identifier, an Application Extend Unique Identifier, (ApplicationKey, hereinafter referred to as AppKey) must be shared (set) between each device in the IoT network.

Particularly, in order to open the OTA, each device in the IoT network must share (set) a key key, i.e., an application key (AppKey). In order to prevent a key from leaking, a pseudo application key Pseudo AppKey) method.

Here, the Pseudo AppKey method refers to a method in which the IoT terminal and the CCBS device in the IoT network preliminarily share (set) a pseudo application key (Pseudo AppKey) on the basis of a pseudo application key (Pseudo AppKey) When the open call processing is requested, the network device allocates a real application key (Real AppKey) to the IoT terminal and causes the standard OTA opening to be performed based on the allocated real application key (Real AppKey) Procedure.

When a join request for opening the OTA is received from the IoT terminal, the network device checks a message integrity check (MIC) of a join request according to a pseudo application key (Pseudo AppKey) And determines whether the real application key is allocated based on the result of the procedure.

At this time, in order to perform the integrity check (MIC) procedure, the same application key must be shared (set) in advance between the IoT terminal and the network device. In order to perform the initial opening procedure in the pseudo activation environment as described above An integrity check (MIC) procedure will be performed based on the pseudo application key (Pseudo AppKey).

That is, when the integrity check (MIC) procedure for the pseudo application key (Pseudo AppKey) is successfully completed and the first activation procedure is successfully completed, a real application key (Real AppKey) is assigned to the IoT terminal where the first activation procedure is completed And stored.

However, if the IoT terminal that has completed the initial opening attempts to re-enter after re-entering the service after releasing the service, the execution of the integrity check (MIC) procedure by the Real AppKey stored at the time of initial opening fails So that the re-opening operation will fail.

Accordingly, the present invention provides a new IoT terminal to allow a re-start procedure to be successfully performed without failure even when a service is used through the initial opening in a pseudo opening environment and then re-opened after the service is used. I would like to propose the opening method.

The present invention has been made in view of the above circumstances, and it is an object of the present invention to provide a method of re-opening an IoT terminal suitable for a pseudo-opening environment, To a technique for improving performance.

According to a first aspect of the present invention, there is provided a network device comprising: a revocation managing unit for transmitting a real application key allocated to a specific terminal to a management apparatus when a specific terminal is revoked; And when a specific message related to the service provision of the specific terminal is received from the management apparatus, whether or not at least one of the real application key and the pseudo application key is included in the specific message is determined And determining whether to restart the service of the specific terminal based on the determination result.

The specific message may include a first field for displaying a first value corresponding to the pseudo application key and a second field for displaying a second value corresponding to the real application key.

The determining unit determines that the first service is opened when the first value is included in the first field and the second value is not included in the second field.

Wherein the determining unit determines that the service restart of the specific terminal is included if the first value is included in the first field and the second value is included in the second field.

According to a second aspect of the present invention, there is provided a management apparatus comprising: a revocation managing unit for receiving a real application key allocated to a specific terminal from a network device when a specific terminal is revoked; A registration manager for generating a re-registration request message including a real application key and a pseudo application key for a service re-activation request of the specific terminal; And a transmitting / receiving unit for transmitting the re-registration request message to the network device.

The revocation management unit may store the pseudo application key assigned to the specific terminal and the real application key when they are received from the network device.

According to a third aspect of the present invention, there is provided an IoT network system comprising: an IoT network system for, when a service re-activation request of a specific terminal is requested, a real application key A management device for generating a registration request message; And a re-registration requesting unit for, upon receiving the re-registration request message from the management apparatus, determining whether or not at least one of the real application key and the pseudo application key is included in the re- And a network device for determining whether to restart the service of the terminal.

Wherein the management apparatus transmits a revocation request message including the pseudo application key to the network device to request service termination of the specific terminal, and transmits the revocation request message to the network device, And a response message including the response message to the network device.

The network device performs service re-activation of the specific terminal only when the real application key and the pseudo application key are both included in the re-registration request message.

Accordingly, according to the network device and the management apparatus of the present invention, the system including them, and the operation method of the devices, by proposing a re-opening method of the IoT terminal suited to the pseudo opening environment, The effect of improving the performance can be obtained.

FIG. 1 is an exemplary diagram illustrating a structure of an Internet (IoT) network to which the present invention is applied.
FIG. 2 is an exemplary view showing a state where the existing re-opening operation fails.
3 is a block diagram illustrating a configuration of a network device according to an embodiment of the present invention.
FIG. 4 is a flowchart illustrating an operation method of a first opening procedure according to an embodiment of the present invention.
5 is a block diagram illustrating the configuration of a management apparatus according to an embodiment of the present invention.
6 is a flowchart illustrating an operation method of a management apparatus according to an embodiment of the present invention.
7 is a flowchart illustrating an operation method of a cancellation and re-activation process according to an embodiment of the present invention.
8 is a flowchart illustrating an operation method of a network device according to an embodiment of the present invention.

Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings.

FIG. 1 shows a network structure of Internet of Things (IOT) to which the present invention is applied.

1, the Internet (IoT) network structure to which the present invention is applied includes an IoT terminal (e.g., terminals 1, 2, ..., N) 100 at a remote location, A network device 200 (IoT app server) for connecting the IoT terminal and the customer terminal (IoT app) through a wired / wireless network, an IoT terminal, And a gateway (for example, base stations 1, 2, ...) for transmitting and receiving signals between network devices 200.

In addition, the IoT network includes a management apparatus 300 for managing subscribers using the Internet (IoT) service, and a network interworking server 400 for connecting a wired / wireless network between the network apparatus 200 and the management apparatus 300 .

The management device 300 may be a CCBS (Customer Care & Billing System) device and manages all the subscriber information registered / changed in the process of using the Internet service (IoT) Service management, service opening, termination, re-opening, and pausing.

That is, when service opening / re-opening of the IoT terminal of a specific subscriber is requested, the management apparatus 300 transmits subscriber information necessary for opening / re-opening to the network device 200 through the network interworking server 400, . Meanwhile, when the service termination / pause is requested to the IoT terminal of the specific subscriber, the management apparatus 300 notifies the network device 200 via the network interworking server 400 that subscriber information for a specific subscriber should be deleted You will be asked.

In such an IoT network, an OTA (Over The Activation) procedure is performed to open the IoT terminal 100. For this purpose, a Device Extend Unique Identifier (DevEUI), an Application Extend Unique Identifier (AppEUI), an application key (AppKey), and the like must be previously shared (set) between each device in the IoT network.

Particularly, in order to open the OTA, each device in the IoT network must share (set) a key key, i.e., an application key (AppKey). In order to prevent a key from leaking, a pseudo application key Pseudo AppKey) method.

The Pseudo AppKey method is a method in which after the IoT terminal 100 and the management apparatus 300 in the IoT network share a pseudo application key Pseudo AppKey in advance, Pseudo AppKey) is requested, the network device 200 allocates a Real Application Key (Real AppKey) to the IoT terminal 100 and allocates the allocated Real AppKey ), The standard OTA opening is performed.

When receiving a join request for opening the OTA from the IoT terminal 100, the network device 200 checks the integrity of the join request message (Join Request) according to the pseudo application key (Pseudo AppKey) (Real AppKey) is determined based on the result of performing an integrity check (MIC) procedure.

In order to perform the integrity check (MIC) procedure, the same application key must be shared (set) between the IOT terminal 100 and the network device 200 in advance. In such a pseudo activation environment An integrity check (MIC) procedure will be performed based on the pseudo application key (Pseudo AppKey) when performing the initial opening procedure.

That is, when the integrity check (MIC) procedure for the pseudo application key (Pseudo AppKey) is successfully performed and the initial activation procedure is successfully completed, the IoT terminal 100, which has completed the initial activation procedure, Are allocated and stored.

However, if the IoT terminal 100 that has completed the initial opening attempts to reopen after reopening the service after the service is terminated, the real application key (Real AppKey) The execution fails and the re-opening fails.

Referring to FIG. 2, a situation in which re-activation of the IoT terminal fails when an existing re-activation scheme is performed in a pseudo-activation environment will be briefly described below.

In FIG. 2, when the terminal 1 is in a pseudo opening environment and the terminal 1 requests the re-opening after using the service through the initial opening, the corresponding procedure according to the situation (① opening, ② termination, ) Are performed successively.

The management device transmits a registration request message including terminal basic information to the network device through the network interworking server so that the first opening of the terminal 1 can be performed (S10, S11).

Here, the registration request message includes terminal basic information related to the terminal 1 such as a terminal identifier (DevEUI), an application identifier (AppEUI), a pseudo application key (Pseudo AppKey)

Then, the network device stores the terminal basic information of the terminal 1 included in the registration request message to complete the registration, generates a response message for the registration request message to inform that the registration is completed, (S12-S14).

After the terminal 1 is shipped and turned on for the first time, the network device transmits a join request to the network device for opening the OTA. When the network device performs the integrity check (MIC) procedure of the join request And determines whether a real application key (Real AppKey) is allocated based on the result (S15-S18).

The join request includes a terminal identifier (DevEUI), an application identifier (AppEUI), and a pseudo application key (Pseudo AppKey), which are basic terminal information stored in the terminal 1 in the manufacturing process of the terminal 1.

That is, at the time of initial opening of the terminal 1, the network device transmits a pseudo application key (Pseudo AppKey) previously shared (set) through the above-mentioned registration process and a pseudo application key Pseudo AppKey) are identical to each other and performs an integrity check (MIC) procedure.

As a result of performing the integrity check (MIC) procedure, if the two application keys are not identical, the network device determines that the first opening procedure has failed and drops a join request.

On the other hand, if the two application keys are the same, it is determined that the execution of the first activation procedure is successful, and a real application key is assigned to the terminal 1. The network device transmits the allocated real application key (Real AppKey) The subscriber information including the terminal basic information of the terminal 1 is generated and stored.

When the terminal 1 is requested to be terminated while the terminal 1 is being used for the first time and the service is being used, the management apparatus transmits a revocation request message including the aforementioned terminal basic information to the network And delivers it to the network device through the server (S19-S21).

Then, the network device detects and deletes the subscriber information matched with the terminal basic information of the terminal 1 included in the revocation request message, and generates a response message to the revocation request message to inform that the subscriber information of the terminal 1 has been deleted And then transmits it to the management apparatus through the network interworking server (S22-S26).

When the revocation procedure is performed as described above, the subscriber information of the terminal 1 can be deleted from the network device, but the real application key (Real AppKey) allocated to the terminal 1 at the time of initial opening from the network device is still stored.

When re-activation of the terminal 1 is requested in a state where the real application key is stored in the terminal 1 as described above, the network device performs the re-activation of the terminal 1 as in the first- Registration request message including the terminal basic information received from the risk management apparatus, completes the registration, generates a response message for the re-registration request message, and transmits the re-registration request message to the management apparatus through the network interworking server (S27- S32).

After the terminal 1 turns on the power, the network device transmits a join request to the network device for opening the OTA, and the network device performs an integrity check (MIC) procedure of a join request (Join Request) (S33 , S34).

At this time, a join request transmitted from the terminal 1 for re-opening includes a real application key (Real AppKey), a terminal identifier (DevEUI) and an application identifier (AppEUI) allocated at the time of initial opening.

The network device further includes a pseudo application key (Pseudo AppKey) shared (set) in the above-mentioned re-registration process and a real application key (Real AppKey) detected from a join request It is determined whether they are the same or not and an integrity check (MIC) procedure is performed.

That is, in the re-activation procedure, since the two application keys do not coincide with each other, the integrity check (MIC) procedure fails and the re-activation fails (S35).

In this way, if the re-activation of the terminal 1 fails, the terminal 1 is transmitted again to the manufacturer so that the real application key (Real AppKey) allocated at the time of initial opening is changed to the pseudo application key (Pseudo AppKey) The re-start procedure can be performed.

However, considering that there are many IoT terminals in the IoT network, and there is a characteristic that the place where the IoT terminal is installed is mainly installed in a position (e.g., sewer) where the worker can not easily approach, the re- It is practically impossible to perform the procedure of changing the pseudo application key (Pseudo AppKey) after disassembling the IoT terminals from the installation location and then transmitting the same to the manufacturer. Therefore, There is a need for solutions.

Accordingly, the present invention proposes a method for re-opening the IoT terminal suitable for a pseudo-opening environment.

More specifically, in the present invention, a new IoT terminal (not shown) is provided to allow a re-start procedure to be successfully performed without failure even when the service is re-opened after using the service through the initial opening in the pseudo- And a network device and a management apparatus for realizing the re-opening of the network.

Hereinafter, a network device for providing Internet service (IoT) according to an embodiment of the present invention will be described in detail with reference to FIG.

The network device 200 according to the present invention includes a revocation management unit 210 that transmits a real application key allocated to a specific terminal to a management apparatus 300 when a specific terminal is revoked, (Real AppKey) and a pseudo application key (Pseudo AppKey) is included in a specific message when a specific message related to service provision of a specific terminal is received from the terminal And a determination unit 220 for determining whether to restart the service of the specific terminal.

The network device 200 includes a transceiver 230 for transmitting and receiving all messages related to providing Internet service (IoT) service (for example, a message related to opening / reopening / canceling / pausing) And a storage unit 240 for storing messages and information (e.g., various application keys, subscriber information) identified based thereon.

The termination management unit 210 performs a termination process when a service termination request of a specific terminal is requested.

More specifically, the specific terminal may be any one of the terminals 1, 2, 3,... N shown in FIG. 1, but it is possible to use a service through the first opening in the pseudo opening environment, It can be defined as the requesting terminal.

For example, if the terminal 1 requests the termination while using the service through the initial opening, the terminal 1 may be a specific terminal. Hereinafter, for convenience of explanation, the terminal 1 will be referred to as a specific terminal, and the initial opening procedure of the terminal 1 will be described first with reference to FIG. 4 before explaining the termination procedure for the terminal 1.

4, the management apparatus 300 of the present invention transmits a registration request message including terminal basic information to the network device 200 (FIG. 4) via the network interworking server 400 so that the terminal 1 can be opened for the first time (S100, S101).

Here, the registration request message includes terminal basic information 1 related to the terminal 1 such as a terminal identifier (DevEUI), an application identifier (AppEUI), a pseudo application key (Pseudo AppKey) In the case of the terminal basic information 1 related to the terminal 1, it is preferable that the terminal basic information 1 is stored in the memory of the terminal 1 in the manufacturing process of the terminal 1.

Then, the network device 200 stores the terminal basic information 1 of the terminal 1 included in the registration request message, and completes the registration. After that, the network device 200 generates a response message to the registration request message to notify that the registration of the terminal 1 is completed, and then transmits the response message to the management device 300 through the network interworking server 400 (S103, S104 ).

The terminal identifier 1 (DevEUI), the application identifier (AppEUI), and the pseudo application key (Pseudo AppKey) are transmitted to the management device 1 through the terminal device 1 for the OTA (Over The Activation) (Set) to the network device 300 and the network device 200, respectively.

The network device 200 then transmits a join request to the network device 200 for opening the OTA after the terminal 1 is shipped and turned on for the first time, (Real AppKey) based on the result of the MIC procedure (S105-S106).

Here, the join request includes a terminal identifier (DevEUI), an application identifier (AppEUI), and a pseudo application key (Pseudo AppKey) which are terminal basic information 1 stored in the terminal 1 in the manufacturing process of the terminal 1.

More specifically, the network device 200 detects a pseudo application key (Pseudo AppKey) from a join request (Join Request). Thereafter, the network device 200 determines whether the detected pseudo application key (Pseudo AppKey) is the same as the pseudo application key (Pseudo AppKey) that is shared (set).

That is, if the two application keys are not the same, the network device 200 determines that the integrity check (MIC) procedure has failed, and therefore, the network device 200 determines that the initial activation procedure is failed and drops the join request.

On the other hand, if the two application keys are the same, the network device 200 determines that the integrity check (MIC) procedure is successful, so that the network device 200 determines that the initial activation procedure is successful and assigns a real application key to the terminal 1 S107).

Accordingly, when the initial opening is completed, the terminal 1 stores the real application key (Real AppKey) instead of the pseudo application key (Pseudo AppKey) included in the terminal basic information 1 to generate the terminal basic information 2. That is, in the terminal basic information 2, a terminal identifier (DevEUI), an application identifier (AppEUI), and a real application key (Real AppKey) are stored.

After that, the network device 200 generates and stores subscriber information including a real application key (Real AppKey) allocated to the terminal 1 and pre-registered terminal basic information 1 (S108).

The subscriber information of the terminal 1 stored in the network device 200 includes a terminal identifier (DevEUI), an application identifier (AppEUI), a pseudo application key (Pseudo AppKey), a real application key Real AppKey) will be saved.

When the management device 300 requests the revocation of the terminal 1 using the service through the first opening, the network device 200 transmits the real application key allocated to the terminal 1 to the management device 300, As shown in FIG.

3, the revocation management unit 210 of the network device 200 receives a revocation request message for requesting the revocation of the service of the terminal 1 from the management apparatus 300. Based on the revocation request message The subscriber information of the terminal 1 is detected.

Herein, the revocation request message includes terminal basic information 1 related to the terminal 1 such as a terminal identifier (DevEUI), an application identifier (AppEUI), a pseudo application key (Pseudo AppKey)

The revocation management unit 210 detects subscriber information matching the terminal basic information 1 included in the revocation request message from the storage unit 240 and generates a response message for the revocation request message based on the detected subscriber information do. Subsequently, the revocation managing unit 210 deletes the detected subscriber information from the storage unit 240. [

Here, the response message includes a terminal identifier (DevEUI), an application identifier (AppEUI), a pseudo application key (Pseudo AppKey), a real application key (Real AppKey), and a revocation result code.

Thereafter, the revocation managing unit 210 notifies that the subscriber information of the terminal 1 has been deleted, and transmits a response message to the management apparatus 300 in response to the revocation request message for the re-activation procedure of the terminal 1, which will be described later.

The determination unit 220 determines whether or not the service of the terminal 1 is restarted.

More specifically, when a specific message related to the service provision of the terminal 1 is received from the management apparatus 300, the determination unit 220 determines whether the specific message includes a real application key (Real AppKey) and a pseudo application key It is determined whether or not the terminal 1 is to be restarted based on a result of determining whether at least one is included.

At this time, the specific message includes a first field for displaying a first value corresponding to a pseudo application key (Pseudo AppKey) and a second field for displaying a second value corresponding to a real application key (Real AppKey) .

When the specific message is received from the management apparatus 300, the determination unit 220 determines whether to restart the service of the terminal 1 based on the result of checking both the value of the first field and the value of the second field .

That is, the determination unit 220 includes a first value corresponding to the pseudo application key (Pseudo AppKey) in the first field, and a second value corresponding to the real application key (Real AppKey) is included in the second field It is determined that the specific message received from the management apparatus 300 is a registration request message requesting registration of the terminal 1 for the first time opening of the terminal 1.

As a result, when the registration request message is received from the management apparatus 300, the determination unit 220 can confirm that the first opening procedure for the terminal 1 should be performed when a join message (join request) is received from the terminal 1 in the future .

Meanwhile, the determining unit 220 includes a first value corresponding to a pseudo application key (Pseudo AppKey) in a first field and a second value corresponding to a real application key (Real AppKey) Registration request message requesting re-registration of the terminal 1 in order to request re-activation of the terminal 1, the specific message received from the management apparatus 300. [

When the re-registration request message is received from the management apparatus 300, the determination unit 220 requests the re-activation of the terminal 1 that has been using the service for the first time since the service is revoked. Therefore, (Join Request) is received, it can be confirmed that the re-activation procedure for the terminal 1 should be performed.

Hereinafter, a management apparatus for providing the Internet (IoT) service according to an embodiment of the present invention will be described in detail with reference to FIG. 5 and FIG. In FIG. 5, a specific terminal will be described as terminal 1 as in FIG.

The management apparatus 300 according to the present invention includes a revocation management unit 310 that receives a real application key (Real AppKey) allocated to the terminal 1 from the network device 200 at the time of termination of the service of the terminal 1, A registration management unit 320 for generating a re-registration request message including a real application key (Real AppKey) and a pseudo application key (Pseudo AppKey), and a re-registration request message to the network device 200 And a transmission / reception unit 330.

In addition, the management apparatus 300 may include all messages (e.g., messages related to opening / reopening / canceling / pausing) related to provision of the Internet service (IoT) and information , Subscriber information), and the like.

Upon termination of the service of the terminal 1, the revocation management unit 310 receives a response message for the revocation request message from the network device 200. [

More specifically, the revocation management unit 310 generates a revocation request message to request the service termination of the terminal 1, and transmits the revocation request message to the network device 200 (S200).

Herein, the revocation request message includes terminal basic information 1 related to the terminal 1 such as a terminal identifier (DevEUI), an application identifier (AppEUI), a pseudo application key (Pseudo AppKey)

3, the network device 200 transmits the subscriber information of the terminal 1 matching the terminal basic information 1 included in the revocation request message to the network device 200, After generating a response message for the revocation request message based on the subscriber information, the management server 300 transmits the response message to the management apparatus 300 and deletes the subscriber information.

The revocation management unit 310 receives a response message for the revocation request message from the network device 200 (S210).

At this time, the response message includes a terminal identifier (DevEUI), an application identifier (AppEUI), a pseudo application key (Pseudo AppKey), a real application key (Real AppKey), and a revocation result code.

Thereafter, the revocation management unit 310 detects the terminal basic information 1 previously registered based on the response message, and generates subscriber information of the terminal 1 by matching the real application key (Real AppKey) with the previously registered terminal basic information 1 And stores it (S220, S230).

When the revocation procedure is performed, the subscriber information including the real application key allocated to the subscriber station 1 is deleted from the network device 200, The same subscriber information as the deleted subscriber information is generated and stored.

The registration management unit 320 generates a re-registration request message for the service re-activation request of the terminal 1.

More specifically, the registration management unit 320 generates a re-registration request message based on the subscriber information of the terminal 1 generated according to the result of performing the service termination of the terminal 1 so that the service re-activation of the terminal 1 can be performed S240).

Here, the subscriber information includes a terminal identifier (DevEUI), an application identifier (AppEUI), a pseudo application key (Pseudo AppKey), and a real application key (Real AppKey).

The registration management unit 320 detects a real application key and a pseudo application key from the subscriber information of the terminal 1 and generates a re-registration request message including the detected real application key and the pseudo application key (S240) .

Hereinafter, with reference to FIG. 7, a description will be made of a procedure for performing termination and re-opening of a specific terminal using a service through the initial opening in the pseudo-opening environment of the present invention. In Fig. 7, the terminal 1 will be described as a specific terminal.

7, the management apparatus 300 of the present invention generates a revocation request message to request the service termination of the terminal 1 and transmits the revocation request message to the network device 200 through the network interworking apparatus 400 (S300-S302).

Here, the revocation request message includes terminal basic information 1 related to the terminal 1 such as a terminal identifier (DevEUI) of the terminal 1, an application identifier (AppEUI), a pseudo application key assigned to the terminal 1,

Then, the network device 200 detects subscriber information matching the terminal basic information 1 included in the revocation request message, and generates a response message for the revocation request message based on the detected subscriber information (S303, S304) . Subsequently, the network device 200 deletes the detected subscriber information from the storage unit 240 (S305).

Here, the subscriber information includes a terminal identifier (DevEUI), an application identifier (AppEUI), a pseudo application key (Pseudo AppKey), and a real application key (Real AppKey).

As a result, in the present invention, if subscriber information is stored in the network device 200 after the cancellation process, call processing for the subscriber terminal 1 will be performed. Therefore, subscriber information of the subscriber terminal 1 requesting cancellation, in particular Real AppKey, The call processing of the terminated terminal 1 is prevented in advance.

Thereafter, the network device 200 transmits a response message to the revocation request message to the management device 300 through the network interworking server 400 (S306-S308).

When the response message to the revocation request message is received from the network device 200, the management apparatus 300 detects the terminal basic information 1 previously registered related to the terminal 1 based on the response message, In step S309, the subscriber information of the terminal 1 is generated by matching the real application key (Real AppKey) with the basic information 1 and stored.

Here, the subscriber information includes a terminal identifier (DevEUI), an application identifier (AppEUI), a pseudo application key (Pseudo AppKey), and a real application key (Real AppKey).

When the termination procedure of the terminal 1 is completed according to the above description, the subscriber information including the real application key allocated to the terminal 1 is not deleted from the network device 200, The same subscriber information as the deleted subscriber information is generated and stored.

In step S310, the management apparatus 300 generates a re-registration request message based on the subscriber information of the terminal 1 generated according to the result of performing the service termination of the terminal 1 so that the re-activation of the terminal 1 can be performed. Then, the management apparatus 300 transmits a re-registration request message to the network device 200 through the network interworking server 400 (S311).

Then, the network device 200 detects the subscriber information of the terminal 1 from the re-registration request message, and stores the subscriber information of the terminal 1 to complete the re-registration of the terminal 1 (S312). Then, the network device 200 generates a response message to the re-registration request message and transmits the response message to the management apparatus 300 through the network interworking server 400 (S313-S315).

When the UE 1 turns on the power and then transmits a join request to the network device 200 for opening the OTA, the network device 200 performs an integrity check (MIC) procedure of a Join Request (S316-S319).

At this time, the real application key (Real AppKey), the terminal identifier (DevEUI), and the application identifier (AppEUI) are included in the join request transmitted from the terminal 1 for re-opening.

Accordingly, the network device 200 detects a real application key (Real AppKey) from a join message (Join Request). Thereafter, the network device 200 determines whether the detected real application key (Real AppKey) is the same as the real application key (Real AppKey) shared (re-set) upon re-registration of the terminal 1.

That is, if the two application keys are not the same, the network device 200 determines that the re-start procedure is unsuccessful and drops the join request because the integrity check (MIC) procedure is unsuccessful.

On the other hand, if the two application keys are the same, the network device 200 determines that the re-activation procedure is successful because the integrity check (MIC) procedure is successful and completes the re-activation procedure.

Hereinafter, a method of operating a network device according to an embodiment of the present invention will be described in detail with reference to FIG.

Prior to a specific description, for convenience of explanation, the terminal 1 of FIG. 1 will be referred to as a specific terminal and the operation after the service termination of the terminal 1 that has used the service through the initial opening in the pseudo opening environment is completed I will explain how.

8, when a specific message related to the service provision of the terminal 1 is received from the management apparatus 300 after the termination of the service of the terminal 1 is completed, the network device 200 of the present invention transmits a specific field Based on the result of confirming the value of " 0 "

At this time, the specific message includes a first field for displaying a first value corresponding to a pseudo application key (Pseudo AppKey) and a second field for displaying a second value corresponding to a real application key (Real AppKey) .

More specifically, when a specific message is received from the management apparatus 300, the network device 200 confirms the specific field of the specific message, that is, the value of the first field and the value of the second field (S400, S410).

Thereafter, the network device 200 determines whether there is a value for displaying the application key in each field (S420).

As a result of the determination in step S420, if there is a value for displaying the corresponding application key in each of the fields, the network device 200 includes the first value corresponding to the pseudo application key (Pseudo AppKey) in the first field , And the second field contains a second value corresponding to the real application key (Real AppKey).

That is, the fact that a specific message includes a first value corresponding to a pseudo application key (Pseudo AppKey) and a second value corresponding to a real application key (Real AppKey) The network device 200 transmits a specific message received from the management apparatus 300 to the terminal 1 for re-activation of the terminal 1 because the terminal 1 using the service is requested to re- Registration request message requesting registration (S430).

When the join request is received from the terminal 1 in the future, the network device 200 performs re-activation of the terminal 1 according to the re-start procedure of FIG. 7 described above (S440).

On the other hand, if it is determined in step S420 that there is no value for displaying the application key in all the fields, the network device 200 determines that the first value corresponding to the pseudo application key (Pseudo AppKey) , But it is determined that the second field does not contain the second value corresponding to the real application key (Real AppKey).

That is, the fact that only the first value corresponding to the pseudo application key (Pseudo AppKey) is contained in the specific message means that the terminal 1 has not yet performed the initial opening, and therefore the network device 200 receives It is determined that the specific message is a registration request message for requesting registration of the terminal 1 for the first opening of the terminal 1 (S450).

When the join request is received from the terminal 1 in the future, the network device 200 performs the initial opening to the terminal 1 according to the initial opening procedure of FIG. 4 described above (S460).

As described above, according to the network device and the management apparatus of the present invention, and the system including them and the operation method of the devices, the terminal 1 is transmitted to the manufacturer again to perform the re-activation to the terminal 1, The real application key (Real AppKey) assigned to the terminal 1 at the first opening of the terminal 1 is changed to the pseudo application key (Pseudo AppKey) after the assigned real application key is changed to the pseudo application key AppKey), the terminal 1 can be freely canceled and re-opened based on this.

Thus, according to the present invention, the effect of improving the performance of the Internet (IoT) service can be obtained by suggesting the re-opening method of the IoT terminal suitable for the pseudo-opening environment.

A network device and a management device according to an embodiment of the present invention, a system including the same, and a method of operating the devices can be implemented in the form of a program command that can be executed through various computer means, have. The computer-readable medium may include program instructions, data files, data structures, and the like, alone or in combination. The program instructions recorded on the medium may be those specially designed and constructed for the present invention or may be known to those skilled in the art of computer software. Examples of computer-readable media include magnetic media such as hard disks, floppy disks and magnetic tape; optical media such as CD-ROMs and DVDs; magnetic media such as floppy disks; Magneto-optical media, and hardware devices specifically configured to store and execute program instructions such as ROM, RAM, flash memory, and the like. Examples of program instructions include machine language code such as those produced by a compiler, as well as high-level language code that can be executed by a computer using an interpreter or the like. The hardware devices described above may be configured to operate as one or more software modules to perform the operations of the present invention, and vice versa.

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, but, on the contrary, It will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the appended claims.

According to the network apparatus and management apparatus of the present invention, the system including them, and the operation method of the apparatuses, the present invention proposes a method of re-opening the IoT terminal suitable for a pseudo-access environment, It is not only the use of the related technology but also the possibility of commercialization or operation of the applied device, but it is an industrially applicable invention since it is practically possible to carry out clearly.

100: terminal device
200: Network device
210: Revocation management unit 220: Decision unit
230: Transmitting / receiving unit 240:
300: management device
310: revocation management unit 320: registration management unit
330: Transmitting / receiving unit 340:

Claims (9)

A revocation management unit for transmitting a real application key allocated to the specific terminal to a management apparatus when a specific terminal is revoked; And
Based on a result of determining whether or not at least one of the real application key and the pseudo application key is included in the specific message when the specific message related to the service provision of the specific terminal is received from the management apparatus, Determining whether the specific message is for re-opening the service of the specific terminal or for opening the first service of the specific terminal,
Lt; RTI ID = 0.0 > 1, < / RTI > The method according to claim 1,
The specific message may include:
A first field for displaying a first value corresponding to the pseudo application key, and a second field for displaying a second value corresponding to the real application key. 3. The method of claim 2,
Wherein,
Wherein the determination unit determines that the first service is to be opened if the first field includes the first value and the second field does not include the second value. 3. The method of claim 2,
Wherein,
Wherein the determining unit determines that the specific terminal is to restart the service if the first value is included in the first field and the second value is included in the second field. A revocation management unit for receiving a real application key allocated to the specific terminal from a network device when a specific terminal is revoked;
A registration manager for generating a specific message including at least one of the real application key and a pseudo application key to request the first terminal to start the service or the service restart of the specific terminal; And
A transmission / reception unit for transmitting the specific message to the network device,
Wherein the management device comprises: 6. The method of claim 5,
The revocation management unit,
And when the real application key is received from the network device, matches the real application key with the pseudo application key assigned to the specific terminal. A management apparatus for receiving a real application key assigned to the specific terminal when a service of the specific terminal is terminated; And
A specific message is transmitted to the specific terminal based on a result of determining whether at least one of the real application key and the pseudo application key is included in the specific message, A network device for determining whether to re-start a service or to start an initial service of the particular terminal
The IoT network system comprising: 8. The method of claim 7,
The management apparatus includes:
And transmits a revocation request message including the pseudo application key to the network device in order to request service termination of the specific terminal. In response to the revocation request message, a response message including the real application key and the pseudo application key From the network device. 8. The method of claim 7,
The network device comprising:
Wherein the specific message is determined to be for re-opening the service of the specific terminal only when the specific message includes both the real application key and the pseudo application key.

Images