KR101988477B1 - Method of registration of devices for M2M network using M2M gateway and M2M gateway for it - Google Patents

Abstract

The present invention relates to a method for registering a device to a network through a gateway based on machine to machine (M2M) communication, which includes: (a) an M2M network management server (hereinafter referred to as a management server) and a predetermined registration procedure; Receiving at least one device configuration information, which is not registered in the M2M network, from the management server; (b) if the gateway recognizes connection of any new M2M device, determining whether to register an M2M network based on one or more M2M device configuration information received from the management server; And (c) determining whether to register the new M2M device with the M2M network according to the determination result.

Description

Method of registration of devices for M2M network using M2M network and M2M gateway for it}

The present invention relates to a method and a gateway device for registering a plurality of M2M devices on an M2M network, and more particularly, to a method and a gateway device for registering a plurality of M2M devices on an M2M network through an M2M gateway. .

The development of modern information and communication technology is changing to networking centering not only computers but also smart phones and portable multimedia devices. Such small devices with computing and communication networking functions used in computers, smart phones, etc. are used not only for information devices but also for various objects around humans to enable a communication network between things to obtain and share information around each other.

Representative of such techniques is machine to machine (M2M) communication. M2M is a technology for networking of machines and devices that are prevalent in everyday life. M2M communication connects and enables a series of devices from the computer body to everyday products (eg, home appliances, buildings, or vehicles).

M2M communication is a concept of configuring a network using a small communication device in an M2M device and sharing the collected information.It started from the USN (Ubiquitous Sensor Network) mainly targeting a local area without human intervention, but gradually As the scope and purpose vary, various wired / wireless networks can be used for M2M communication. The M2M communication is used for various convergence services such as situation recognition, location information, remote control, etc. using cellular-based high-speed communication technology such as 3GPP and LTE along with low-cost, low-power short-range wireless communication such as Zigbee, Bluetooth, and WiFi. It is possible.

M2M networks are based on the implementation of the European Telecommunication Standards Institute (ETSI) standard. According to the ETSI standard, M2M devices are directly connected to the network area by 'direct connection method' in which M2M devices directly connect to M2M networks, and M2M devices bypass the M2M network by using a gateway as a network proxy. It can be divided into 'indirect connection method' connecting to.

1 is a diagram illustrating an example of a structure of a communication system using a general M2M network.

Referring to FIG. 1, the M2M communication system 100 stores data transmitted from the device area 101 and the M2M devices 111 and 112 including the M2M devices 111 and 112 and / or the M2M gateway 113. It may be divided into a network area 102 composed of a transport network 114 for transmitting through a communication network and an M2M application 115 associated with the transport network.

In this case, the network area 102 manages the network management unit 116 that performs network configuration management, fault management, subscriber management and performance management, and M2M network, and performs configuration, failure, and subscriber management of the M2M network. The M2M management unit 117 may be further included.

The M2M device area 101 is composed of a direct communication M2M device 111, an indirect communication M2M device 112, and an M2M gateway 113.

The direct communication type M2M device 111 includes an M2M function unit 111a and an M2M application unit 111b to perform one or more application applications through a communication function and directly connect to an M2M network.

On the other hand, the indirect communication type M2M device 112 corresponds to a device using the M2M local area network, and is intended to distinguish it from the direct communication type M2M device 111. Examples include remote equipment such as equipment used for healthcare and payment terminals for offline payment (card, smart card payment) or mobile payment (payment using a smartphone, etc.). The indirect communication type M2M device 112 is indirectly connected to the M2M transport network 114 via the M2M gateway 113 and to the M2M gateway 113 through an M2M local area network distinct from the M2M network.

In detail, the indirect communication type M2M device 112 does not directly access the M2M network and does not include a separate M2M function unit or an M2M application unit, and thus may access the network through a separate gateway or router. That is, the M2M gateway 113 serves as a network proxy for indirectly connecting the indirect communication type M2M device 112 to the transmission network 114.

The M2M gateway 113 connects the indirect communication type M2M device 112 to the access network 114a via the M2M local area network. To this end, the M2M gateway 113 includes an M2M function 113a and an M2M application 113b, and connects an indirect communication type M2M device 112 connected through an M2M local area network to an access network 114a. Perform entry, routing, and communication functions. In addition, the M2M gateway 113 may collect device operation data, environment data, sensing data, and the like from the indirect communication type M2M device 112 and transmit them to a remote operation server.

As such, the direct communication type M2M device 111 and the M2M gateway 113 provide functions such as data collection and reporting, remote control function, group communication or one-to-one communication function, and transaction processing in order to provide M2M service.

The M2M regional network is a network that connects the indirect communication type M2M device 112 and the M2M gateway 113. The M2M local area network has unique network settings, communication processing, management, maintenance, and maintenance for smooth sensing and driving functions of the device. As a network comprising a network, data processing is performed within a local network.

Area networks include personal area networks (PANs) such as IEEE 802.15, ZigBee, Bluetooth, and RFID, automotive communications, industrial networks, building automation communications, and communications technologies used for home automation.

Transport network 114 includes an access network 114a, a core network 114b, and an M2M service capability 114c associated with M2M network access of the M2M device.

The access network 114a is a network configured for accessing various devices to a communication network in M2M communication, and includes a wired access network and / or a wireless access network.

Recently, M2M communication using wireless communication is mainly performed.Wireless access networks include Wideband Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMAX), Wireless Fidelity (WiFi), and Long Term Revolution (LTE). Can be used.

The core network 114b is a high-speed backbone network of a large communication network capable of large-capacity, long-distance voice and data services, and includes a public switched telephone network (PSTN), an integrated information network (ISDN), an IMT-2000, a wide area network (WAN), and an on-premises information network ( LAN), general cable broadcasting (CATV). It mainly uses the Internet backbone network, which connects the Internet, controls services and networks, and provides interconnection and roaming capabilities with other networks.

The access network 114a and the core network 114b serve as a delivery network for data communication between the M2M transport network 114 and the M2M application 115 and the M2M devices 111 and 112, and control information and M2M data. Send it.

The M2M service capability 114c identifies and stores information for providing application functions, performs communication selection, remote object management, security, transaction management, interworking, and the like, and configures an M2M core with the core network 114b. do.

The M2M application 115 performs an operation related to the execution of an application application related to various services that may be provided to the M2M device, and is connected to the transmission network 114 to connect the wired / wireless between the administrator or user terminal and the M2M devices 111 and 112. Make a connection using a network.

As such, when the 'direct connection method' is used in the M2M communication system illustrated in FIG. 1 as in the direct communication type M2M device 111, the M2M device 111 is configured to authenticate, authorize, manage, and provision the network area. Will perform the same function.

On the other hand, when using the 'indirect connection method' such as the indirect communication type M2M device 112, the M2M device 112 is connected to the transmission network 114 through the gateway 113, the gateway 113 is an M2M device ( 112, authentication, authorization, management provisioning to the network is performed.

Unlike a direct connection method in which a device directly connects to an M2M network, an indirect connection method in which a device is indirectly registered through a gateway is performed through a plurality of steps.

FIG. 2 is a flowchart illustrating a process in which a device performs communication with a network in a general M2M network. Specifically, FIG. 2 illustrates a process in which an indirect communication type M2M device registers with an M2M network.

Referring to FIG. 2, the M2M device registers an application with a gateway service capability module (GSCL) in a gateway through a device service capability module (DSCL) in a device (S201).

Upon registration, the gateway's GSCL performs local communication with the M2M device over the M2M local network, and locally with the Network Service Capabilities Layer (NSCL) of the network and the M2M network. (S202).

Separately, the M2M network undergoes bootstrap and a predetermined network registration process (S203), and bootstrap and service connection process for a service provided to M2M devices (S204).

The NSCL of the network configures a GSCL context with respect to the GSCL of the gateway connected through local communication, and registers the DSCL or GSCL in the NSCL (S205).

In the process shown in FIG. 2, steps S201 and S202 correspond to a connection process (first connection) between the device and the gateway, and steps S203 to S205 correspond to a connection process (second connection) between the gateway and the network.

As each connection process is completed, the M2M device may be registered on the M2M network through the gateway, and specifically, the M2M device may be connected to the NSCL to perform mutual data communication (S206).

According to the process described above with reference to FIG. 2, a new M2M device may register through a network bootstrap in order to connect to an access network through an M2M gateway. In the network registration process, the gateway may allocate an IP address, authenticate, Privilege charging process. In addition, in order to connect the M2M device to the NSCL through the gateway, the gateway performs mutual authentication with the NSCL during the service connection through the service bootstrap. In addition, in order to exchange device configuration information of the M2M device with the NSCL, the M2M gateway performs a service capability module (SCL) registration procedure of the NSCL.

Accordingly, when a plurality of indirect communication type M2M devices register with the M2M network to perform data communication with the NSCL, the gateway performs the process illustrated in FIG. 2 for each M2M device.

3 is a diagram illustrating a process in which a plurality of M2M devices are registered in an M2M network through a gateway.

Referring to FIG. 3, when n M2M devices 301 register an application with the M2M gateway 302, and the gateway 302 registers n devices 301 with the M2M network, that is, the NSCL 303. The gateway 302 performs n network registrations, n service connection processes, and n SCL registration processes with the NSCL 303.

In N network registration process, N IP address allocation, authentication, authorization, and billing procedures are performed, N service connection processes, N mutual authentication procedures, and N SCL registration processes, N device configuration information exchange procedures. It is done.

As such, when a plurality of M2M devices are registered in the M2M network through the gateway, network communication resources are wasted in the data communication process between the M2M device and the NSCL, and data loss occurs during the device configuration information exchange during the SCL registration process. Potential problems may arise in the provision of M2M services.

Therefore, various methods for minimizing the process of registering a plurality of devices on a network have been studied.

For example, in the case of the "authentication system of a home device and its authentication method (application number 10-2003-002091)" in the prior art, in an environment in which one device is authenticated in one home network domain, it moves to another home network domain. Therefore, in order to solve the problems such as the management problems in the device authentication process and the increase in the management cost in the certification authority, a method of simplifying the device registration process by sharing information between the home gateway where the device is registered and other home gateways is proposed. Suggesting.

SUMMARY OF THE INVENTION The present invention has been made to solve the above-described problems, and when the M2M network registration of a plurality of M2M gateways, the gateway performs registration and authentication for each device and ultimately processes the same as those registered in the network. I would suggest.

The technical problems to be achieved in the present invention are not limited to the technical problems mentioned above, and other technical problems not mentioned above will be clearly understood by those skilled in the art from the following description. Could be.

According to an aspect of the present invention, a method of registering a device in a network through a gateway based on machine to machine (M2M) communication according to an embodiment of the present invention includes: (a) an M2M network management server (hereinafter, ' Receiving one or more device configuration information not registered in the M2M network from the management server by the gateway which has completed a predetermined registration procedure); (b) if the gateway recognizes connection of any new M2M device, determining whether to register an M2M network based on one or more M2M device configuration information received from the management server; And (c) determining whether to register the new M2M device with the M2M network according to the determination result.

The at least one M2M device configuration information according to an embodiment of the present invention may include at least one of at least one M2M device identification information, device configuration information, user identification information and network identification information corresponding to the M2M device.

The step (a) according to an embodiment of the present invention may further include provisioning, by the gateway, the one or more pieces of M2M device configuration information received from the management server.

Step (b) according to an embodiment of the present invention includes the steps of: collecting predetermined device information from the new M2M device; Analyzing, by the gateway, the device information based on the one or more M2M device configuration information received from the management server; And according to the analysis result, the gateway may allocate predetermined network identification information to the new M2M device and register with the M2M network.

In this case, the gateway according to an embodiment of the present invention, if the device information and the at least one M2M device configuration information match, according to the analysis result, the new M2M device to identify the network corresponding to the new M2M device You can assign information. Alternatively, when the device information and the one or more M2M device configuration information do not match, the network identification information limited to the new M2M device or network registration blocking of the new M2M device may be performed. .

According to an embodiment of the present invention, step (c) may include: determining whether the gateway uses a predetermined M2M service provided by the gateway of the new M2M device registered in the M2M network; And registering the application of the new M2M device with the gateway according to the determination result. In addition, according to the determination result, when the service of using the new M2M device is inconsistent with a predetermined M2M service provided by the gateway, application registration of the new M2M device may be blocked.

According to an embodiment of the present invention, the new M2M device may include an M2M device to which predetermined user identification information is given as a self-purchasing device of a user.

In this case, the step (b) according to an embodiment of the present invention, the gateway includes the step of confirming the M2M network unregistered state of the new M2M device connected to the gateway at the request of the user, the (c The step) may include the step of the gateway notifying the new M2M device of the M2M network unregistered status. In addition, the device registration method according to an embodiment of the present invention, the gateway according to an embodiment of the present invention receiving a registration request message including the user identification information from the new M2M device; And determining whether to register the new M2M device application by comparing the user identification information with the one or more pieces of M2M device configuration information received from the management server.

Gateway to register the M2M device to the network based on M2M (Machine to Machine) communication in accordance with another embodiment of the present invention for solving the above problems, referred to as M2M network management server (hereinafter referred to as "management server" And a wireless communication unit for performing wireless communication with one or more M2M devices; A data storage unit for storing one or more device configuration information not registered in the M2M network received from the management server through the wireless communication unit; And a controller configured to determine whether to register the M2M network of the new M2M device based on the data storage unit when performing a predetermined registration procedure with the management server and connecting a new M2M device.

The control unit according to an embodiment of the present invention, based on the data storage unit comparing and analyzing the information transmitted from the new M2M device connected to the gateway to determine whether or not M2M network registration target; And a registration / authentication unit performing M2M network registration / blocking and a predetermined authentication procedure of the new M2M device according to a result of the comparison analysis unit.

When the new M2M device is registered as an M2M network, the controller may notify the management server of configuration information regarding the M2M device through the wireless communication unit.

The controller may determine whether to use a predetermined M2M service provided by the gateway of the new M2M device registered to the M2M network, and according to the determination result, the application of the new M2M device. Can be registered.

The above embodiments are only some of the preferred embodiments of the present invention, and various embodiments reflecting the technical features of the present invention are based on the detailed description of the present invention described below by those skilled in the art. Can be derived and understood.

According to an embodiment of the present invention, by registering and authenticating a plurality of M2M devices on an M2M network through an M2M gateway, it simplifies the process of registering and authenticating a plurality of M2M devices, and wastes network resources and data loss during registration and authentication. Can solve the service obstacles.

BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings, included as part of the detailed description in order to provide a thorough understanding of the present invention, provide examples of the present invention and together with the description, describe the technical idea of the present invention.
1 is a diagram illustrating an example of a structure of a communication system using a general M2M network.
2 is a flowchart illustrating a process of a device performing communication with a network in a general M2M network.
3 is a diagram illustrating a process in which a plurality of M2M devices are registered in an M2M network through a gateway.
4 is a diagram illustrating an example of a system structure for registering a plurality of M2M devices based on an M2M gateway according to an embodiment of the present invention to an M2M network.
5 is a flowchart illustrating an example of a device registration process in a network registration system of an M2M device using a gateway according to an embodiment of the present invention.
6 is a flowchart illustrating another example of a device registration process in a network registration system of an M2M device using a gateway according to an embodiment of the present invention.
7 is a flowchart illustrating another example of a device registration process in a network registration system for an M2M device using a gateway according to an embodiment of the present invention.

As the invention allows for various changes and numerous embodiments, particular embodiments will be illustrated in the drawings and described in detail in the written description. In the following description of the present invention, if it is determined that the detailed description of the related known technology may obscure the gist of the present invention, the detailed description thereof will be omitted.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings. The detailed description, which will be given below with reference to the accompanying drawings, is intended to explain exemplary embodiments of the present invention and is not intended to represent the only embodiments in which the present invention may be practiced. The following detailed description includes specific details in order to provide a thorough understanding of the present invention. However, one of ordinary skill in the art appreciates that the present invention may be practiced without these specific details.

The present invention relates to a method and system for registering multiple M2M devices on an M2M network. Specifically, in order to solve a service failure caused by waste of network resources and data loss in the process of registering and authenticating a plurality of M2M devices, a plurality of M2M on the M2M network based on the device and network information received from the network management server. It is to propose a method and system for registering a device.

4 is a diagram illustrating an example of a system structure for registering a plurality of M2M devices based on an M2M gateway according to an embodiment of the present invention to an M2M network.

Referring to FIG. 4, a system 400 according to an embodiment of the present invention includes a management server 410 in an M2M network area, an M2M device 420 and an M2M gateway 430 in a user area. Here, the M2M device 420 corresponds to an unregistered device on the M2M network, and network registration is requested to use M2M communication.

The management server 410 sends device configuration information to the M2M gateway 430 with respect to the M2M device 420 to be newly registered, and the M2M gateway 430 sends the M2M device 420 registered to the M2M gateway 430. The device is registered with the M2M network system based on the device configuration information received from the management server 410.

To this end, the M2M gateway 430 is a wireless communication unit 431 for performing wireless communication with the M2M device 420 and the management server 410, data for storing device configuration information transmitted from the management server 410, etc. The storage unit 432 includes a control unit 433 which performs overall control operations for the gateway and determines whether to register the device on the network based on the device configuration information received from the M2M device 410.

The wireless communication unit 431 allows the gateway 430 to perform wireless data communication with the M2M device 420 or the management server 410 through a local area network or an M2M network.

The data storage unit 432 stores and updates one or more pieces of M2M device configuration information or user identification information received from the management server 410 through the wireless communication unit 431, and the control unit 433 may later store the M2M device. Provide the data necessary to perform the registration and authentication procedures. The M2M device configuration information may include new device information, network identification information, and user identification information.

The controller 433 generally controls operations and functions of the M2M gateway 430. Specifically, the controller 433 connects to the M2M network terminal of the gateway 430 and configures the M2M device transmitted from the management server 410 after the connection. Provision of information, application registration of the M2M device 420 to access, network registration, etc. are performed.

To this end, the control unit 433 compares the configuration information transmitted from the M2M device 420 with information previously received from the management server 410 to determine whether or not it is a legitimate object and network registration and authentication. The registration / authentication unit 433b may further include a procedure.

When the M2M device 420 is connected to the gateway 430, the comparison analyzer 433a checks information on the M2M device 420 connected in the network registration process, and stores the information and the data in the data storage 432. Compare and analyze device information.

When the registration / authentication unit 433b matches the information of the M2M device 420 and the device information transmitted from the management server 410 according to the analysis result of the comparison analysis unit 433a, the registration / authentication unit 433b may be assigned to the corresponding M2M device 420. Assign network identification information (IP address, etc.). On the other hand, if the information does not match, it is possible to block network registration of the M2M device or assign limited network identification information such as a private IP address. In addition, the registration / authentication unit 433b may perform an authentication procedure and a user authentication procedure with respect to the M2M device 420.

The controller 430 may bind the access information to the system by notifying the management server 410 of configuration information about the device 420 after performing the registration and authentication procedure for the M2M device 420.

As such, when using the M2M gateway according to an embodiment of the present invention, the network management server 410 does not need to perform a registration and authentication procedure for directly registering the M2M device 420. It can be confirmed that 421 is registered. Also, with network registration

The gateway 422 not only registers the device application with the GSCL but also directly performs network registration based on predetermined device configuration information, thereby allocating network identification information to the registered M2M device 421 so that the device communicates data through the M2M network. To do this.

Device registration for the M2M network through the gateway according to the embodiment of the present invention described with reference to FIG. 4 will be described with reference to FIGS. 5 to 7 below.

5 is a flowchart illustrating an example of a device registration process in a network registration system of an M2M device using a gateway according to an embodiment of the present invention.

Referring to FIG. 5, a gateway according to an embodiment of the present invention registers a gateway with a network management server. Specifically, a GSCL registered with a gateway application (GA) registers the GSCL with an NSCL registered with a network application. Register (S501).

After the connection between the GA and the GSCL and the connection between the GSCL and the NSCL is completed, the communication between the GSCL and the NSCL takes place, and the GSCL and the NSCL can exchange device configuration information with each other.

For example, the management server may store and manage information about one or more M2M devices that are currently unregistered, in use, or available in a predetermined database, and the information about the M2M devices may correspond to device configuration information and a user corresponding to a device that is in use. It may include at least one of identification information.

The management server derives configuration information about one or more M2M devices included in the management category of each gateway based on the information of the registered gateway based on the database and transmits the configuration information to the gateway (S503). The configuration information about the M2M device may include at least one of device identification information, device configuration information, user identification information, and network identification information (eg, public IP address, private IP address, etc.).

Steps S501 to S503 indicate an SCL registration process.

Through the SCL registration process, the management server transmits M2M device configuration information to the gateway, and the gateway provisions the received M2M device configuration information (S504).

Subsequently, when a case where a new M2M device in an unregistered state enters on the M2M network system occurs, the new M2M device registers DSCL with GSCL of the M2M gateway (S505). For example, when a user purchases a new M2M device to drive a predetermined function using the M2M network, a new M2M device which is not registered in the M2M network system enters and the device registers the SCL with the gateway discovered by the user input signal. Can be done.

As DSCL of the new M2M device registers with the GSCL of the gateway, the gateway checks the connected M2M device information and compares it with the M2M device configuration information provisioned in the previous step (S504) (S506).

As a result of the comparison, when the M2M device configuration information transmitted from the management server and the connected new M2M device information match, the gateway derives network identification information corresponding to the device identification information based on the device configuration information and assigns it to the new M2M device. Network registration may be performed at step S507. As described above, the network identification information may correspond to a network ID such as a public IP address or a private IP address.

On the other hand, if the M2M device information connected as a result of the comparison does not match the new M2M device configuration information, it is possible to block the registration of the M2M device or to allocate private network identification information such as a private IP address (S508).

As such, when network registration of the new M2M device at the gateway is completed, the gateway may notify the management server of the registered new M2M device configuration information and bind the connection information (S509).

For example, as the gateway registers a new M2M device, the gateway may notify the management server of device configuration information in real time, or may notify the management server of one or more device configuration information at regular intervals or aperiodically.

Notification of new M2M device configuration information corresponds to SCL registration update.

After registering the M2M device, a gateway registration process of an application in the device is performed.

Next, the gateway determines whether to allow the use of a predetermined M2M service provided by the gateway of the M2M device, and if the M2M device configuration information matches the M2M device information and service state information previously stored in the gateway and is using the corresponding M2M service. The application is registered in the GSCL of the gateway (S510 and S511).

After the registration of the device application is completed, the gateway may notify the management server of the device configuration information to update the SCL registration of the changed matters (S512).

As described above, according to an embodiment of the device registration process illustrated in FIG. 5, the gateway according to an embodiment of the present invention provisions device configuration information and user authentication information in advance for network registration, thereby connecting a new M2M device. The communication procedure between the gateway and the management server can be minimized.

On the other hand, the user tries to connect to the M2M network using an M2M device that is not pre-registered in the M2M system, or to use the second M2M service when the user has a first M2M device using the first M2M service. Alternatively, a situation may arise where a user attempts to connect and use an M2M device that is being used by connecting to a first gateway to a second gateway to which another user's device is connected.

That is, according to the embodiment of the present invention, since the gateway performs device registration on behalf of the network management server, it is necessary to manage not only the management target device of the gateway but also the connection of devices that are out of the management target. For example, when a new M2M device whose gateway has not received information from the network end is connected, the gateway may manage the M2M device as an unregistered state even if the M2M device is a device registered at the network end through another gateway. .

As described above, a method in which a user uses a service other than the currently registered service or accesses an M2M device in a service non-use state to the network will be described with reference to FIG. 6.

FIG. 6 is a flowchart illustrating another example of a device registration process in a network registration system for an M2M device using a gateway according to an embodiment of the present invention. Specifically, a user is not using a predetermined M2M service registered in an M2M device. The device network registration method in the case will be described.

Referring to FIG. 6, a series of SCL registration processes S601 to S603 for registering an M2M device to an M2M network through a gateway is the same as the SCL registration processes S501 to S503 described above with reference to FIG. 5.

When the SCL registration process is completed, the gateway provisions M2M device configuration information received from the management server (S604).

Thereafter, a case where an unregistered M2M device enters the M2M network system occurs. For example, when a user wants to connect and use an M2M device in use by connecting to a first gateway, the second gateway may be connected to the management server. Since the received M2M device configuration information does not include information on the M2M device, the M2M device may be managed as an unregistered device.

The gateway compares and checks the M2M device information based on the M2M device configuration information provisioned in the previous step (S604) with respect to the M2M device that registered the DSCL in the GSCL of the M2M gateway (S605 and S606).

As a result of the comparison, if the gateway is found to be included in the device configuration information provisioned by the M2M device to be accessed, the gateway performs network registration by assigning network identification information (S607). However, even if the M2M device is included in the device information transmitted from the management server, the M2M device may not be included in the management target of the gateway. Therefore, in this case, whether to register the application is determined according to whether the service is used.

Similarly, when it is determined that the M2M device is not included in the device configuration information, the gateway may assign limited network identification information such as blocking network registration or allocating a private IP address (S608).

In addition, when network registration of the new M2M device at the gateway is completed, the gateway may notify the management server of the registered new M2M device configuration information and bind the access information (S609).

Next, the gateway determines whether the M2M device uses the M2M service. According to the above-described embodiment, when the network-registered M2M device does not use the M2M service provided by the gateway (that is, provisioned M2M device configuration information) When the M2M service information used by the corresponding M2M device is not included), the gateway may block application registration of the M2M device (S610 and S611).

In this way, the user can block other users' devices from accessing their gateways, and the gateway can act as a proxy for judging whether the other user's device is authorized to reduce unnecessary communication times between the gateway and the network.

Furthermore, the device registration method through the gateway according to an embodiment of the present invention can be applied to a case where a user additionally purchases an M2M device using the same M2M service in a situation where a user uses a predetermined M2M service through a registered M2M device. have.

7 is a flowchart illustrating another example of a device registration process in a network registration system of an M2M device using a gateway according to an embodiment of the present invention. Specifically, the M2M device automatically registers an M2M device into a network through self-opening. I would suggest a way.

Referring to FIG. 7, a series of SCL registration processes S701 to S703 for registering an M2M device to an M2M network through a gateway is the same as the SCL registration processes S501 to S503 described above with reference to FIG. 5.

However, the GSCL of the gateway is registered with the NSCL of the network management server and the configuration information is exchanged (S701), as well as the device information list including the configuration information of the plurality of M2M devices, as well as a plurality of user information corresponding to each M2M device. A list of user information including a may also be interchanged.

When the SCL registration process is completed, the gateway provisions the M2M device information list and the user information list received from the management server (S704).

Thereafter, the user accesses the gateway in a state in which a smart card capable of displaying user identification information such as a universal IC card (UICC) is mounted on a new M2M device purchased by the user, or a phone number registration is performed (S705).

Here, it is assumed that the new M2M device is to additionally register the registered M2M device as the same M2M device as the M2M device in which the user has registered with the management server and used a predetermined M2M service, hereinafter referred to as 'additional M2M device'. do.

The gateway determines that the additional M2M device connected to the gateway is an unregistered device on the network according to a user request signal based on the provisioned M2M device information list, and notifies the additional M2M device that it is not registered (S706).

The additional M2M device transmits a registration request message for requesting device registration to the gateway together with user identification information and device configuration information set in the device in the previous step (S705).

The gateway determines whether or not it matches the user identification information transmitted from the additional M2M device based on the user information list received from the management server in the previous step (S701).

When the user information received from the management server and the user information of the additional M2M device match according to the determination result, the gateway performs application registration of the additional M2M device (S709). Accordingly, the additional M2M device may be connected to the network management server through the gateway to use certain M2M services.

The gateway may notify the management server of the device configuration information as the device application registration is completed (S710). In this case, the gateway may notify in real time according to device application registration, or collect and notify one or more device configuration information registered at predetermined intervals.

On the other hand, if the user information does not match, the gateway may grant limited network identification information such as blocking network registration or assigning a private IP address if it is determined that the M2M device to be accessed is not included in the provisioned device configuration information. There is (S711).

According to the embodiment illustrated in FIG. 7, the M2M gateway may automatically connect and open the M2M device to the gateway through an automatic registration procedure of the M2M device purchased by the M2M gateway, and use the M2M service more conveniently. .

The above description is merely illustrative of the technical idea of the present invention, and those skilled in the art to which the present invention pertains may make various modifications and changes without departing from the essential characteristics of the present invention. Therefore, the embodiments described in the present invention are not intended to limit the technical idea of the present invention but to explain, and the technical idea of the present invention is not limited by these embodiments. The protection scope of the present invention should be interpreted by the following claims, and all technical ideas within the scope equivalent thereto should be construed as being included in the scope of the present invention.

Claims (15)

In a method of registering a device to a network through a gateway based on machine to machine (M2M) communication,
(a) at least one device that has completed a predetermined registration procedure for an M2M network management server (hereinafter referred to as a management server), which is included in the management category of the gateway from the management server but is not currently registered in the M network; Receiving configuration information;
(b) if the gateway recognizes connection of any new M2M device, determining whether the new M2M device is a registration target of the M2M network based on the device configuration information received from the management server; And
(c) determining whether to register the new M2M device with the M2M network according to the determination result.
The prescribed registration procedure
The gateway uses a Gateway Service Capability Layer (GSCL) in which a gateway application (GA) is registered, and a Network Service Capability Layer (NSCL) of a management server in which a network application is registered. Registering with the M2M device through the gateway to the M2M network. The method of claim 1,
The at least one M2M device configuration information,
And at least one of one or more M2M device identification information, device configuration information, user identification information corresponding to the M2M device, and network identification information. The method of claim 1,
In step (a),
And provisioning, by the gateway, the one or more pieces of M2M device configuration information received from the management server, M2M device registration with an M2M network through a gateway. The method of claim 1,
In step (b),
Extracting, by the gateway, device information of the new M2M device from the new M2M device; And
And comparing, by the gateway, device configuration information of the M2M devices received from the management server with device information of the new M2M device, and determining whether to register the M2M network with an M2M network. To register M2M devices. The method of claim 4, wherein
In step (c),
As a result of the determination, when the device information and the at least one M2M device configuration information match, the gateway allocates network identification information corresponding to the new M2M device to the new M2M device and transfers the new M2M device to the M2M network. How to register M2M device to the M2M network through the gateway. The method of claim 4, wherein
In step (c),
As a result of the determination, when the device information and the device configuration information do not coincide, M2M through a gateway, which allocates limited network identification information to the new M2M device or blocks registration of the new M2M device in the M2M network. How to register M2M device to network. The method of claim 1,
Step (c) is,
When the new M2M device is registered with the M2M network, determining whether the new M2M device uses a predetermined M2M service provided by the gateway; And
As a result of the determination, if the use service of the new M2M device matches the predetermined M2M service provided by the gateway, the application of the new M2M device is registered with the gateway, and the use service of the new M2M device is provided by the gateway. Blocking application registration of the new M2M device if it is inconsistent with a predetermined M2M service, M2M device registration method through a gateway to the M2M network. delete The method of claim 1,
The new M2M device includes a M2M device that is given a predetermined user identification information to the user's self-purchase device, M2M device registration method through the gateway to the M2M network. The method of claim 9,
In step (b),
Checking, by the gateway, an M2M network unregistered state of the new M2M device connected to the gateway at the request of the user,
Step (c) is,
Sending, by the gateway, an M2M network unregistered state to the new M2M device. The method of claim 10,
The gateway receiving a registration request message including the user identification information from the new M2M device; And
And determining whether to register the new M2M device application by comparing the user identification information with the one or more pieces of M2M device configuration information received from the management server. . A gateway for registering an M2M device to a network based on machine to machine (M2M) communication,
A wireless communication unit for performing wireless communication with an M2M network management server (hereinafter referred to as a management server) and one or more M2M devices;
A data storage unit receiving one or more device configuration information included in the management category of the gateway from the management server but not currently registered in the M2M network, and storing the received device configuration information through the wireless communication unit;
And a control unit that performs a predetermined registration procedure with the management server and determines whether to register the M2M network of the new M2M device based on the data storage unit when any new M2M device is connected.
The prescribed registration procedure
The gateway uses a Gateway Service Capability Layer (GSCL) in which a gateway application (GA) is registered, and a Network Service Capability Layer (NSCL) of a management server in which a network application is registered. The gateway that registers the M2M device based on the M2M communication with the network. The method of claim 12,
The control unit,
A comparison and analysis unit that compares and analyzes information transmitted from the new M2M device accessing the gateway based on the data storage unit to determine whether to be an M2M network registration target; And
And a registration / authentication unit configured to register / block M2M network of the new M2M device and perform a predetermined authentication procedure according to a result of performing the comparison and analysis unit. The method of claim 12,
The control unit,
And registering the new M2M device as an M2M network to notify the management server of configuration information about the M2M device through the wireless communication unit. The method of claim 12,
The control unit,
Determining whether to use a predetermined M2M service provided by the gateway of the new M2M device registered in the M2M network, and registering an application of the new M2M device according to the determination result; Gateway that registers with the network.

Images