KR101991968B1 - A method and apparatus of configuration management for M2M area networks - Google Patents

Abstract

The present disclosure relates to a method and apparatus for configuration management of an M2M area network.
A method for managing a configuration of an M2M area network according to an exemplary embodiment of the present invention includes a step of detecting a state of a network by an M2M gateway or an M2M device, Receiving a message indicating an operation process for controlling the network event from the management apparatus, and performing an operation process according to the indicated message, wherein the M2M gateway Or the M2M device generates and manages a management object for the M2M area network, the operation process including an operation channel change process for changing an operation channel operated in the network, a network reconfiguration for changing a network parameter for the network process, It characterized in that at least one of the network channel scanning process for scanning a sleep schedule change process, and the available channel of the network for a change of the sleep schedule to all nodes in the network group.

Description

Field of the Invention [0001] The present invention relates to a method and apparatus for managing an M2M area network,

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a M2M (Machine to Machine Communication) technology, and relates to a method and an apparatus for managing a configuration of an M2M area network. The present invention relates to a configuration management method of an M2M area network capable of controlling a network configuration according to an operational state of a wireless M2M area network.

"Machine to machine communication" or MTC, "Machine type communication" or "Smart device communication" or "Machine oriented communication" refers to all kinds of communication in which a person does not intervene in the communication process Refers to a communication method.

On the other hand, each node constituting the wireless M2M area network usually uses a battery, so its output power is low. Therefore, the wireless M2M area network is deployed and operated in a multi-hop structure composed of multiple nodes to support service coverage for a remote area.

Due to the nature of the wireless channel environment, the M2M area network easily receives frequency interference by other wireless communication devices, and the transmission quality of the wireless channel tends to deteriorate easily due to changes in the surrounding environment. In addition, depending on the application, the position of some nodes in the M2M area network may be changed by a person or by moving objects mounted on the node, or may be newly added to the M2M area network, so that the network configuration is variable Pray.

This characteristic situation greatly reduces the operational efficiency of the wireless M2M area network if the operations manager does not respond immediately. Especially for wireless M2M area networks built in harsh environments where it is difficult to get operational managers to enter. Therefore, the configuration management by the remote management system for the wireless M2M area network is required for the operational efficiency.

According to an aspect of the present invention, there is provided a method for managing a configuration of a wireless M2M area network capable of collecting management information through an event detecting an abnormal operation state of a wireless M2M area network, Method and apparatus.

A method for managing a configuration of an M2M area network according to an exemplary embodiment of the present invention includes a step of detecting a state of a network by an M2M gateway or an M2M device, Receiving a message indicating an operation process for controlling the network event from the management apparatus, and performing an operation process according to the indicated message, wherein the M2M gateway Or the M2M device generates and manages a management object for the M2M area network, the operation process including an operation channel change process for changing an operation channel operated in the network, a network reconfiguration for changing a network parameter for the network process, A sleep schedule changing process for changing a sleep schedule for all the nodes of the network, and a network channel scanning process for scanning an available channel of the network.

A method for managing configuration of an M2M area network according to another embodiment of the present invention includes the steps of receiving event information generated from state information of a network from an M2M gateway or an M2M device, To the M2M gateway or the M2M device, and receiving from the M2M gateway or the M2M device status information generated as a result of the process or performing the operation process of the M2M gateway or the M2M device , The operational process includes an operation channel change process for changing an operating channel operated on the network, a network reconfiguration process for changing a network parameter for the network, a change of a sleep schedule for all nodes of the network And a network channel scanning process for scanning an available channel of the network.

A device according to an embodiment of the present invention includes a sink node for detecting a status of a network, a remote entity management (REM) function unit for generating the detected status information as network event information, And a GC (Generic Communication) function unit for receiving a message for instructing an operation process of controlling the network event from the management apparatus, wherein the REM function unit performs an operation process according to the indicated message , The operation process includes an operation channel change process for changing an operating channel operated on the network, a network reconfiguration process for changing a network parameter for the network, a sleep for changing a sleep schedule for all nodes of the network A schedule change process, It characterized in that any of the network channel scanning process for scanning the available channels of the greater one.

A management apparatus according to an embodiment of the present invention includes a receiver for receiving event information generated from state information of a network from an M2M gateway or an M2M device, a controller for generating a message indicating an operation process for controlling the network event, The M2M gateway or the M2M device transmits the status information generated as a result of performing the operation process or the result of the operation process to the M2M gateway or the M2M device, Device, the operational process comprising: an operational channel change process for changing an operating channel operated on the network; a network reconfiguration process for changing network parameters for the network; Sleep schedule change for the change in sleep schedule processes, and is characterized in that at least one of the network channel scanning process for scanning the available channels in the network.

According to the present invention, the abnormal state of the M2M area network can be detected through the event information management unit, the M2M application and the M2M device management system can be notified as the network event information, and the corresponding network event can be controlled through the execution of the operation process , It is possible to quickly adapt the configuration of the M2M area network to the event situation, thereby improving the operational efficiency of the network and improving the service life and service quality of the entire network.

1 is a diagram showing an M2M network structure.
2 is a diagram illustrating a structure of a management object for an M2M area network created and managed in an M2M GW or M2M device according to an exemplary embodiment of the present invention.
3 is a diagram illustrating a structure of an etsiAreaNwkInfo resource for an M2M area network generated and managed in an M2M NSCL according to an exemplary embodiment of the present invention.
4 is a block diagram of an M2M GW or M2M device for network event detection and process execution in accordance with an embodiment of the present invention.
5 is a diagram illustrating a configuration management procedure of an M2M area network according to an exemplary embodiment of the present invention.
6 is a diagram illustrating an AreaNwkReconfig process according to an embodiment of the present invention.
7 is a detailed view illustrating a node reconnection process according to an embodiment of the present invention.
FIG. 8 is a diagram illustrating a SleedSchedChange process according to an embodiment of the present invention.
9 is a diagram illustrating an OperChanChange process according to an embodiment of the present invention.
10 is a diagram illustrating a NwkChanScan process according to an embodiment of the present invention.
11 is a flowchart illustrating an M2M area network reconfiguration procedure according to an embodiment of the present invention.
12 is a diagram illustrating a network reconnection procedure of a MAN node for managing M2M area network configuration according to an embodiment of the present invention.
13 is a flowchart illustrating an operation channel change procedure for M2M area network configuration management according to an exemplary embodiment of the present invention.
FIG. 14 is a diagram illustrating a network channel scanning procedure according to an embodiment of the present invention.
15 is a diagram illustrating a sleep schedule change procedure for M2M area network configuration management according to an embodiment of the present invention.
16 is a diagram illustrating a procedure for connecting a new MAN node for managing the configuration of an M2M area network according to an embodiment of the present invention.
FIG. 17 is a diagram illustrating a structure of an < areaNwkInstance > resource according to an embodiment of the present invention.
FIG. 18 is a diagram showing an attribute of an <areaNwkEvent> resource and a structure of a sub resource according to an embodiment of the present invention.
FIG. 19 is a diagram showing an attribute of an <areaNwkAction> resource and a structure of a sub resource according to an embodiment of the present invention.
FIG. 20 is a diagram showing a resource attribute and sub-resource structure of <nwkActionStatus> and <areaNwkChanScan> according to an embodiment of the present invention.
FIG. 21 is a diagram showing attributes of <operChanChange>, <areaNwkReconfig>, and <sleepSchedChange> resources according to an embodiment of the present invention.
FIG. 22 is a diagram illustrating a configuration of a MANMO according to an embodiment of the present invention.
23 is a diagram illustrating a configuration of a management apparatus for managing an M2M area network according to an embodiment of the present invention.

Hereinafter, some embodiments of the present invention will be described in detail with reference to exemplary drawings. It should be noted that, in adding reference numerals to the constituent elements of the drawings, the same constituent elements are denoted by the same reference symbols as possible even if they are shown in different drawings. In the following description of the present invention, a detailed description of known functions and configurations incorporated herein will be omitted when it may make the subject matter of the present invention rather unclear.

In describing the components of the present invention, terms such as first, second, A, B, (a), and (b) may be used. These terms are intended to distinguish the constituent elements from other constituent elements, and the terms do not limit the nature, order or order of the constituent elements. When a component is described as being "connected", "coupled", or "connected" to another component, the component may be directly connected or connected to the other component, Quot; may be "connected," "coupled," or "connected. &Quot;

Embodiments of the present invention will be described with reference to object communication. Object communication is variously called M2M (Machine to Machine communication), MTC (Machine Type Communication), IoT (Internet of Things), Smart Device Communication (SDC), or Machine Oriented Communication . Object communication refers to various communication in which communication is performed without a person intervening in the communication process. Object communication can be used in various fields including Smart Meter, e-Health, Connected Consumer, City Automation, and Automotive Application.

In this specification, M2M will be mainly described. However, this description is not limited to M2M, but is applicable to all systems and structures providing inter-device communication, i.e., object communication, and communication occurring in these systems.

In addition, such object communication can be applied to various fields including Smart Meter, e-Health, Connected Consumer, City Automation, and Automotive Application .

The Service Capabilities Layer (SCL) is largely divided into Network Service Capabilities Layer (NSCL), Gateway Service Capabilities Layer (GSCL), and Device Service Capabilities Layer (DSCL). Hereinafter, N, G, and D refer to network domains, gateways, and devices, respectively, unless otherwise noted, which may be displayed in combination with the SCL. Applications, on the other hand, can be coupled to network domains, gateways, and devices, respectively, which can be denoted as NA, GA, DA.

1 is a diagram showing an M2M network structure. The M2M area network is connected to the M2M platform (M2M platform) through the M2M GW (Gateway) or the M2M device, and the M2M platform is connected to the M2M application / M2M device management system. The M2M GW or M2M device may connect a plurality of wireless M2M area networks 101, 102. A wireless M2M node is a component of a wireless M2M area network.

As described above, the M2M area network tends to easily receive frequency interference by wireless communication devices for other purposes due to the characteristics of the wireless channel environment, and to easily degrade the transmission quality of the wireless channel due to changes in the surrounding environment. In addition, depending on the application, the position of some nodes in the M2M area network may be changed by a person or by moving objects mounted on the node, or may be newly added to the M2M area network, so that the network configuration is variable Pray.

This characteristic situation greatly reduces the operational efficiency of the wireless M2M area network if the operations manager does not respond immediately. Especially for wireless M2M area networks built in harsh environments where it is difficult to get operational managers to enter. Therefore, the configuration management by the remote management system for the wireless M2M area network is required for the operational efficiency.

In general, the configuration management of the wireless M2M area network by the remote management system provides the own information of the network and the configuration state of the network as the management information.

For the ETSI M2M system, the configuration information of each M2M area network is provided together with the number of M2M area networks attached to the M2M gateway or M2M device for management of the M2M area network. The configuration information of the M2M area network includes the type of the M2M area network, the number of devices included in the corresponding network, the sleep schedule of the network, the network address format, and some network parameters such as the corresponding M2M area network type information. The management system uses this information that the M2M gateway or M2M device has for the management of the M2M area network. Since the information is defined as the information defined in the process of designing and building the M2M area network, the information can be managed effectively in a normal situation in which the network is operated in the same configuration as the initial network.

   However, the wireless M2M area network is in an abnormal operating state due to its characteristics. One of the unusual events is the occurrence of local frequency interference. In the vicinity of an M2M gateway or an M2M device, even if the operating channel is good, there may be a frequency interference around the end node of the M2M area network that is n hops away from the M2M device, such that the operating channel seriously affects service quality.

In another event situation, the network is no longer able to accommodate a new node due to saturation of the designed node capacity. That is, as the allotable network addresses are exhausted, the network address can not be allocated to the node which is to join the network any more.

Another event situation may be that a new node with a sleep schedule different from the sleep schedule of the network participates in the network or a sleep schedule for all or some of the nodes that make up the network due to a change in the data collection period for the application service Is required.

In addition, the event may also occur due to the fact that the new node participates in the network due to the mobility of the node or any node changes its position in the network.

In the above situation, the conventional configuration management method can not detect the abnormal operation state of the wireless M2M area network and can not cope with the event situation because it performs the passive configuration management that simply monitors the configuration state of the M2M area network. There is a problem that it can not be normalized.

Accordingly, a configuration management method for a wireless M2M area network capable of detecting an abnormal operation state of a wireless M2M area network, such as frequency interference, node connection rejection, new node connection, and the like, occurring in a wireless M2M area network, need.

According to an embodiment of the present invention, in order to solve the above problems and to detect an abnormal operation state of the wireless M2M area network and appropriately control the event situation, the M2M GW or the M2M device transmits the M2M area After detecting the abnormal state of the network by receiving the event notified by the node of the network, the event information is transmitted to the M2M network application (NA) via the M2M platform, that is, the M2M network service capability (NSCL) ) Or an M2M device management system, and is adapted to respond to a network event situation through execution of an operation process operation triggered by the M2M network application or the M2M device management system and to receive the execution result in the form of a notification, To obtain management information related to The configuration management method for wireless M2M area network according to claim is provided.

The M2M GW or M2M device receives event information about an abnormal operation status generated in a wireless M2M area network, and transmits a corresponding event, i.e., a new node participation to a wireless M2M area network, a new node addition to a node list of the network, (Management object node) for managing these events, and then transmits these event information to the M2M platform, that is, the M2M network service function (NSCL). &Lt; / RTI &gt; The received event information is stored in the corresponding management information providing means (i.e., management resource) in the M2M network service function, and is notified to the M2M network application or the M2M device management system.

Upon receiving the event information, the M2M network application or the M2M device management system transmits a network parameter value corresponding to the event status to the M2M GW or the M2M device via the M2M NSCL, And triggers corresponding process operations to be performed on the M2M GW or M2M device. The triggered process runs on the M2M GW or M2M device. When the process is completed, the M2M GW or the M2M device transmits the network status information acquired through the execution result or execution as management information to the M2M network application or the M2M device management system via the M2M NSCL.

The execution operation includes an operation channel change process for changing an operating channel operated on the network, a network reconfiguration process for changing a network parameter for the network, a sleep schedule change for changing a sleep schedule for all nodes of the network Processes, and network channel scanning processes for scanning available channels of the network, and the like.

Accordingly, the configuration management of the wireless M2M area network according to an exemplary embodiment of the present invention detects event data in the wireless M2M area network and executes a corresponding operation for an event situation, and detects network events based on the notified event A network event notification step of transmitting the information to the management system, a parameter change setting step of transmitting a relevant parameter value necessary for a corresponding operation to the event situation, a process of remotely triggering execution of a process, A triggering step, a process execution and state information collecting step of executing the process and acquiring state information as a result thereof or collecting network state information generated through execution, a step of collecting the state information and the result obtained and collected in the step, Of the execution result And a collection information delivery step.

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

2 and 3 illustrate a management object structure and a management resource structure for the M2M area network configuration management according to an exemplary embodiment of the present invention.

FIG. 2 is a diagram illustrating a structure of a MANMO (Area Network Management Object) for an M2M area network created and managed in an M2M GW or an M2M device according to an exemplary embodiment of the present invention. In the management object of FIG. 2, elliptical and rectangular shapes represent managed object nodes, and "< x > *" shown in the figure represents that a name is given when the corresponding managed object node is created.

The purpose of each managed object node is as follows. M2MAreaNwkInfo is a root node representing an M2M area network management object. M2MAreaNwkInfo / NumOfAreaNwks represents the total number of M2M area networks attached to the same M2M GW or M2M device. M2MAreaNwkInfo / AreaNwks is the parent node for all information related to all M2M area networks connected to the M2M GW or M2M device. M2MAreaNwkInfo / AreaNwks / <x> is the parent node for information about a specific M2M area network connected to the same M2M GW or M2M device.

M2MAreaNwkInfo / AreaNwks / < x > / AreaNwkType indicates the type of M2M area network. M2MAreaNwkInfo / AreaNwks / <x> / AddressType indicates the address type of the M2M area network. M2MAreaNwkInfo / AreaNwks / < x > / AreaNwkEvent is a placeholder containing an event generated in the M2M area network. M2MAreaNwkInfo / AreaNwks / <x> / AreaNwkEvent / DevAttached is one of the events of the M2M area network and indicates the participation of the new node and can display the address of the corresponding node. M2MAreaNwkInfo / AreaNwks / <x> / AreaNwkEvent / NwkJoinRejected is one of the events of the M2M area network, which indicates that the connection of the new node has been rejected due to the exhaustion of the previously acquired network address and the impossibility of address allocation. M2MAreaNwkInfo / AreaNwks / <x> / AreaNwkEvent / ListOfDevices represents a list of pointers to all the nodes in the M2M area network. All values in this list are separated by commas. Each value represents a reference to a particular node of the M2M area network, i.e., a M2M Area Network Device Management Object (MANDMO) for a particular M2M area network device.

M2MAreaNwkInfo / AreaNwks / < x > / AreaNwkInfo is a place frame containing parameters unique to the same M2M area network, and M2MAreaNwkInfo / AreaNwks / < x > / AreaNwkInfo / < M2MAreaNwkInfo / AreaNwks / <x> / AreaNwkInfo / <x> / ParameterName and M2MAreaNwkInfo / AreaNwks / <x> / AreaNwkInfo / <x> / ParameterValue indicate parameter names and parameter values, respectively.

M2MAreaNwkInfo / AreaNwks / <x> / Operations is a placeholder for the process that is executed to control the configuration of the M2M area network. M2MAreaNwkInfo / AreaNwks / < x > / Operations / AreaNwkChanScan has no value and is used to trigger a process to perform a scan operation on all available channels of the M2M area network. The M2MAreaNwkInfo / AreaNwks / < x > / Operations / AreaNwkChanScan / ResultsData contains a list of the set of channel scan values collected in the execution of the scan operation of all channels available in the M2M area network. All values in this list are separated by semicolons. Each value represents a channel measurement and separated by a colon. The left side of the colon indicates the energy detection (ED) value and the right side of the colon indicates the LQI (Link Quality Indicator) value.

M2MAreaNwkInfo / AreaNwks / < x > / Operations / OperChanChange has no value and is used to trigger the process of executing the change setting operation of the operating channel of the M2M area network. M2MAreaNwkInfo / AreaNwks / < x > / Operations / AreaNwkChanScan / ChannelNumber represents a channel number to be changed and operated for the M2M area network.

M2MAreaNwkInfo / AreaNwks / < x > / Operations / AreaNwkReconfig does not have any value and is used to trigger the process of executing the change setting operation of the network parameters for the M2M area network. M2MAreaNwkInfo / AreaNwks / < x > / Operations / AreaNwkReconfig / areaNwkParam represents a network parameter to be changed for the M2M area network.

M2MAreaNwkInfo / AreaNwks / < x > / Operations / SleepSchedChange does not have any value and is used to trigger the process of executing the change of sleep schedule for the M2M area network. M2MAreaNwkInfo / AreaNwks / < x > / Operations / SleepSchedChange / SleepSchedParam indicates a sleep schedule parameter to be changed for the M2M area network.

M2MAreaNwkInfo / AreaNwks / < x > / OperationStatus is a parent node for all information indicating the execution state of the operation. M2MAreaNwkInfo / AreaNwks / < x > / OperationStatus / Operation represents a link to an operation in which the state of the execution operation is expressed as "OperationStatus &quot;. M2MAreaNwkInfo / AreaNwks / < x > / OperationStatus / Progress indicates the progress state of the execution operation as a percentage. M2MAreaNwkInfo / AreaNwks / < x > / OperationStatus / FinalStatus indicates the final state of the execution operation.

3 is a diagram illustrating a structure of an etsiAreaNwkInfo resource for an M2M area network generated and managed in an M2M NSCL according to an exemplary embodiment of the present invention. The etsiAreaNwkInfo resource corresponds to the MANMO of FIG. 2 and has such a structure. The etsiAreaNwkInfo resource is located under the <sclBase> / <scl> / attachedDevices / mgmtObjs resource in NSCL. In this management resource, the rectangle represents the rounded rectangle of the resource, the attribute represents the number, the number represents the number, "*" means 0 or more, and n means finite number.

The lower resource and attribute of the etsiAreaNwkInfo resource correspond to corresponding nodes of the management object MANMO, respectively. Therefore, the meaning of each resource is the same as the managed object node of the same name in the managed object MANMO.

The non-identical information among these correspond to the following. < areaNwkInstance > corresponds to the managed object node M2MAreaNwkInfo / AreaNwks / < x > as a resource for specific M2M area network information. The <param> resource is for M2M area network specific parameters and corresponds to M2MAreaNwkInfo / AreaNwks / <x> / AreaNwkInfo / <x> / ParameterName and ParameterValue. In the <param> resource, a channelNumber indicating an operation channel number, an areaNwkParam indicating an M2M area network parameter, and a sleepSchedParam indicating a sleep schedule information of the network are added, respectively. The areaNwkActions resource also represents a collection of executable resources and corresponds to the managed object node M2MAreaNwkInfo / AreaNwks / <x> / Operations. The lower resources of the areaNwkActions resource are all executable resources. The nwkActionStatus resource is for all the information indicating the execution state of the operation and corresponds to the managed object node M2MAreaNwkInfo / AreaNwks / <x> / OperationStatus.

In addition, "attribute" includes an accessRightID indicating an identifier for access to a resource having this attribute, a creationTime indicating a generation time of the resource having this attribute, and a lastModifiedTime attribute indicating a last modification time of the resource having this attribute. The subscriptions resource represents a collection of recipients who should be notified of the status of changes to the parent resource of this resource.

4 is a block diagram of an M2M GW or M2M device for network event detection and process execution in accordance with an embodiment of the present invention. The M2M GW or M2M device 400 includes a gateway application / device application (GA / DA) 410, a GSCL / DSCL 420, and sink nodes 481 and 482. The GA / DA 410 has specific service logic as an application residing in the M2M GW or M2M device. The sink nodes 481 and 482 are the source nodes forming the M2M area network and provide a connection with the M2M area network node, and a plurality of sink nodes 481 and 482 may exist as needed. The GSCL / DSCL 420 includes a GREM / DREM (Gateway Remote Entity Management / Device Remote Entity Management) function block 430 for providing a management function for the M2M GW or the M2M device itself, A GIP / DIP (GIP / DIP) function block 440 for providing communication with an M2M area network node, a GGC / DGC (network service capability) module 440 for providing a communication function for transmitting / Gateway Generic Communication function block 450, and a service function 460. The service function 460 includes other functional blocks to be supported by the GSCL / DSCL 420, such as application support function, security function, connectivity and address management function. Herein, the M2M area network node means a legacy d device having no DSCL or a D 'device having only DA.

The GREM / DREM function block 430 includes a REM message processor 432 for generating / analyzing management messages to be transmitted / received to / from the NSCL such as management object (MO) data, ETSI <mgmtObj> resource management, A MAN management scheduler 436 for the management logic of the MAN (M2M Area Network) itself and the MAN node, a MAN management scheduler 436 for processing logic for management operations of the MAN node, Process execution function that executes a process (Duty cycle change, M2M reconfiguration, operation channel change, MAN channel scan) and notifies the result to the MAN management scheduler, and transmits to the sink node or analyzes the MAN event received from the sink node A MAN event processor 438 comprising a MAN event detection function, and a storage / update / inquiry unit for the MO tree and node values, It has a function block, such as MO ring manager (439) for M2M area network event detection and execution process will support.

The M2M area network event detection and process execution according to an embodiment of the present invention is performed in the local event processor 470. [ When a network event is notified from the sink node, the local event handler 470 delivers relevant information to the MO manager 439 and delivers the event type to the GW management scheduler 434. [ The GW management scheduler 434 forwards the request to the REM message processor 432 for transmission of an associated message according to the schedule for the received event. At this time, the event related status information transmitted from the MO manager 439 is also transmitted. Execution of the process for configuration management is performed when a message triggering the execution of the specific process received in the REM message processor 432 is identified by the MAN management scheduler 436 as specifying the associated managed object node in the particular process Lt; / RTI &gt; The execution of the process is performed through a series of processes in which an execution related message is transmitted to the network node through the sink node and status information received from the sink node is provided to the MO manager 439 and stored in the managed object node. When the MAN management scheduler 436 is notified from the MAN event processor 438 of the fact that the process execution is completed, the MAN management scheduler 436 starts the next step of the configuration management.

4 is summarized as follows.

The sink nodes 481 and 482 detect the state of the network, and the REM (Remote Entity Management) function, that is, the GREM / DREM 430 function block, generates the detected state information as network event information. The GGC / DGC 450, which is a part of the GC (Generic Communication) function, transmits the event information to the management apparatus for managing the M2M area network and receives a message for instructing the operation process for controlling the network event from the management apparatus. At this time, the REM function unit performs an operation process according to the indicated message, and the operation process includes an operation channel change process for changing an operation channel operated in the network, a network reconfiguration for changing a network parameter for the network A sleep schedule change process for changing a sleep schedule for all nodes of the network, and a network channel scan process for scanning an available channel of the network. The detailed operation of these operation processes is shown in Figs.

The event information may be information on node connection, information on rejection of node connection, information indicating that one or more nodes constituting the network need to be changed, or information on the node list update status.

The GC function unit may receive a parameter value necessary for a corresponding operation for the event situation from the network management apparatus (for example, NSCL) after transmitting the event information.

The REM function unit may generate state information including a result of generating or performing state information in the process of performing the operation process, and the GC function unit may transmit the generated state information to the network management apparatus.

The REM function unit applies the minimum sleep schedule to the M2M gateway or the M2M device to perform the network reconfiguration process, and the sink node detects the state of the network, and the state of the network is stabilized If it is confirmed, the REM function unit may restore the sleep schedule to a value before application of the minimum sleep schedule. This is an embodiment that uses the minimum sleep schedule to shorten the reconnection time of the node and the normalization time of the M2M area network. In this case, a small sleep schedule parameter is initially applied and then the original sleep schedule parameter is applied.

5 is a diagram illustrating a configuration management procedure of an M2M area network according to an exemplary embodiment of the present invention.

The network event notification step S572 is a step of detecting a network event based on the event data notified via the sink node 512 of the M2M area network and transmitting the information to the management system 530, And forwarding the event information to the NSCL and the M2M Device Management System (MDMS) 530. The network event detection step analyzes the event notified via the sink node to identify the type of the event. The M2M GW or M2M device considers that the notification has been generated by the network connection of the new node if the event received from the sink node has assigned a network address to the new node or a new node has occurred by joining the network. Event detection is the process of identifying a received event. The M2M GW or M2M device stores the detected event information in the DevAttached node of the managed object tree. If the event received from the sink node is identified as exhausting the network address, the event information is stored in the NwkJoinRejected node of the managed object tree.

The event information transmission step is a process of transmitting the stored event information to the M2M network application or the M2M device management system 530 via the M2M NSCL 520. [ Following the detection step, the M2M GW or the M2M device transmits the management resources of the NSCL corresponding to the DevAttach node and the NwkJoinRejected node, that is, the DevAttach resource and the NwkJoinRejected resource, respectively. This transfer process is the same as the process of updating the value of the resource with the node value. The resource value is then passed back to the M2M network application or M2M device management system. A change notification subscription to the areaNwkEvent resource is made in advance according to the ETSI M2M standard for delivery of the resource value.

The parameter change setting step S574 is a step of delivering the corresponding parameter value necessary for the corresponding operation of the event situation, that is, the execution of the related process. First, the M2M network application or M2M device management system 530 sets the parameter value for the process to be executed in the corresponding resource attribute of the M2M NSCL. The network parameters to be changed are set to the areaNwkParam attribute, the channel number to be changed to the channelNumber attribute, and the sleep schedule parameter to be changed to the sleepSchedParam property, respectively. The setting of these parameter values is the same as updating the corresponding attribute values.

When the parameter value is transferred by updating the parameter value, the M2M NSCL 520 transfers the value to the M2M GW or the M2M device 512 or 514 as it is. This transfer process also updates the values of the corresponding managed object nodes of the M2M GW or M2M device, namely, areaNwkParam, channelNumber, and sleepSchedParam.

The process execution triggering step S576 is a step of remotely triggering the execution of the related process which is a corresponding operation to the event situation determined by the network operation policy or the network management mechanism or the network operator. The M2M network application or M2M device management system 530 updates the corresponding resource of the M2M NSCL that represents the process to be executed. The update is to trigger the transmission of an execution message directed to the M2M GW or M2M device. When the M2M GW or M2M device receives an execution message, it triggers the execution of the corresponding process indicated by the associated managed object node.

In this step, when a new node participates in the network, the M2M network application or the M2M device management system transmits a management information providing means for the new node, that is, a message requesting creation of the managed object and the management resource to the M2M GW or the M2M device .

The process execution and status information collection step (S580) includes executing a process for the related operation and acquiring status information as a result thereof or collecting network status information generated through execution, And an information collecting step of collecting the network status information generated as a result of acquiring status information or executing. The process execution step is the step of executing the corresponding process triggered by the M2M network application or M2M device management system 530. [

The process for this step includes: an operation channel change process for changing an operating channel operated on the network; a network reconfiguration process for changing network parameters for the network; a change of a sleep schedule for all nodes of the network; A sleep schedule change process, and a network channel scan process for scanning available channels of the network.

The information collection step is a step of obtaining execution result information indicating completion of execution and success or failure, or obtaining information matching the execution purpose as state information obtained through a process operation. In the case of the network channel scanning process, the collected information means a received signal value (reception strength, link quality level) of the available channels measured by each node and is stored in the managed object node ResultsData.

In this step, when a new node participates in the network, a management object for a new node is created in the M2M GW or M2M device and a management resource for the new node is created in the M2M NSCL, respectively, And storing the management information in the management object for the new node in the M2M GW or M2M device and then transmitting the management information stored in the management object to the M2M NSCL so as to store the management information in the management resource.

The execution result notification and collection information transmission step (S590) is a step of transmitting the result or status information acquired or collected in the previous step to the M2M network application or the M2M device management system. The result of the process execution is transmitted from the M2M GW or the M2M device to the M2M NSCL as the status information of the channel scan data or the execution completion status, and is notified to the M2M network application or the M2M device management system again.

In this step, when a new node participates in the network, when the M2M network application or the M2M device management system is notified of the ListOfDevices information, which is a list of the network access nodes already updated from the M2M GW or the M2M device, And acquiring management information of the new node through inquiry.

5 will be described with reference to the apparatus. The M2M gateway or device includes a GSCL / DSCL and optionally includes a sink node and manages and manages managed objects (MANMO or MANDMO) for the M2M area network illustrated in FIG. The management device includes NA / MDMS and optionally NSCL, and generates and manages an etsiAreaNwkInfo resource for the M2M area network shown in FIG.

The operation process of M2M gateway or M2M device will be described as follows.

The M2M gateway detects the state of the network, generates the detected state information as network event information, and transmits the event information to the management device managing the M2M area network (S572). The M2M gateway or the M2M device receives a message indicating an operation process for controlling the network event from the management device (S574, S576). In this process, the M2M gateway or the M2M device may receive a parameter value necessary for the corresponding operation for the event status from the network management apparatus (S574).

 The M2M gateway or the M2M device performs an operation process according to the indicated message (S580). And result information generated or performed in the process of performing the operation process may be generated. The state information includes all of the information that is collected, produced or produced in the course of performing the operation process. The M2M gateway or M2M device can transmit such status information to the network management device.

Wherein the network reconfiguration process comprises the steps of applying a minimum sleep schedule to the M2M gateway or the M2M device and detecting a state of the network and if the state of the network is confirmed to be in a stable state, And restoring the value to the pre-application value. This is an embodiment that uses the minimum sleep schedule to shorten the reconnection time of the node and the normalization time of the M2M area network. In this case, a small sleep schedule parameter is initially applied and then the original sleep schedule parameter is applied.

The operation process of the management apparatus managing the M2M area network will be described as follows. The management apparatus receives the event information generated from the state information of the network from the M2M gateway or the M2M device (S572). Then, the management device transmits a message indicating an operation process for controlling the network event to the M2M gateway or the M2M device (S574, S576). In this process, the network management apparatus can transmit a parameter value necessary for the corresponding operation to the event situation to the M2M gateway or the M2M device (S574).

Then, the M2M gateway or the M2M device performs the operation process according to the indicated message (S580). The management device transmits the status information, which is a result created or performed in the process of performing the operation process, (S590). The state information includes all of the information that is collected, produced or produced in the course of performing the operation process.

Wherein the network reconfiguration process comprises: sending a message instructing the M2M gateway or the M2M device to apply a minimum sleep schedule; receiving event information from the M2M gateway or the M2M device, And transmitting a message instructing to restore the sleep schedule of the M2M gateway or the M2M device to a value before applying the minimum sleep schedule. This is an embodiment that uses the minimum sleep schedule to shorten the reconnection time of the node and the normalization time of the M2M area network. In this case, a small sleep schedule parameter is initially applied and then the original sleep schedule parameter is applied.

As the embodiment of the event information, the event information may include information on node connection, information on refusal of node connection, information indicating that one or more nodes constituting the network need to be changed, .

Wherein the operational process includes an operation channel change process for changing an operating channel operated on the network, a network reconfiguration process for changing network parameters for the network, a sleep schedule for changing a sleep schedule for all nodes of the network, A change process, and a network channel scan process for scanning the available channels of the network, all of which are illustrated in Figures 6-16.

6 to 8 illustrate an operation process for M2M area network configuration management according to an embodiment of the present invention.

The processes of FIGS. 6 through 8 are executed in the GREM / DREM of the M2M GW or M2M device. 6 is a diagram illustrating an AreaNwkReconfig process according to an embodiment of the present invention.

The AreaNwkReconfig process is the process of executing the network reconfiguration process running on the M2M area network. When it is an execution trigger, the MAN event handler of the M2M GREM requests the sink node to disconnect the connected nodes (S602). If the response is received from the sink node (S604, S606), the MAN event handler delivers the network parameter (Nwk Param) to be changed in the M2M area network to the sink node (S608). Then, the sleep schedule parameter SleepSchedParam having the minimum value of the sleep period is transmitted (S610). This is to provide a sleeping schedule that is much shorter than the original sleep schedule, thereby providing an operating condition that allows all disconnected nodes to reconnect to the M2M area network as quickly as possible. Therefore, the minimum sleep schedule can shorten the reconnection time of the node and the normalization time of the M2M area network.

When the connection event of the network node is received from the sink node (S612), the MAN event handler executes a node reconnection process (S614). Since the connection of the network node is independent for each node, this process is repeated until all the network nodes before the present process are connected (S616). When all the nodes are connected, the MAN event handler delivers the sleep schedule parameters before execution of the present process to the sink node (S618). The network parameters are then stored in the managed object node for it.

Modification of the network parameters and sleep schedule parameters results in a sink node generating a beacon message with the parameter and broadcasting it to the M2M area network. When a response to this is received, this process ends.

7 is a detailed view illustrating a node reconnection process according to an embodiment of the present invention.

The DevReattach process executed as part of the AreaNwkReconfig process of FIG. 6 is a process of collecting and updating information of a corresponding node upon reconnection of a network node. When the connection event of the network node is received, device information is requested to the node and collected (S702). The device information includes node address, node type, node application, node power information, neighbor node information, link quality, and available channel status. Since each node can provide the information managed by the device object, information corresponding to the managed object nodes managed by the managed object MANDMO can be collected. The MAN event handler updates each managed object node (MO) of the MANDMO through the MO manager using the collected information (S706). Then, the node list (ListOfDevices) is updated by adding the management object reference of the access node (AttachDevice) (S708). The MAN event handler then collects the MANDMO data of the access node (S710) and converts it into a resource representation. Then, the management object MANDMO data is transferred by updating a management resource provided for the access node in the M2M platform, that is, the NSCL (S712). If it is confirmed that the management object data is normally transferred (S714), the node list is transmitted to the NSCL (S716). The transmission of this information is also done by updating the attribute. The process then ends.

FIG. 8 is a diagram illustrating a SleedSchedChange process according to an embodiment of the present invention. This is the process of applying the change of sleep schedule to all nodes of the network.

The MAN event handler transmits a sleep schedule parameter (SleepScheduleParam) to the sink node and requests the parameter change (S802). If a response is received (S802, S804), the value of the sleep schedule parameter of the managed object for each node is updated to the currently changed value (S808, S810, S812). The process then ends.

9 is a diagram illustrating an OperChanChange process according to an embodiment of the present invention. This is the process of applying the change of the operating channel operated in the M2M area network.

When the execution trigger is generated, the MAN event handler requests the sink node to release the connection to all nodes connected thereto (S902). If the response is received from the sink node (S904), the MAN event handler delivers the channel number (ChanNum) to be changed in the M2M area network to the sink node. Then, the sleep schedule parameter having the minimum value of the sleep period is transmitted (S906). Its purpose is the same as that in the AreaNwkReconfig process.

If a response is received (S908, S910), the operation channel information on the management object for the M2M area network is updated to the changed value through this process (S912), and then the management resource < areaNwkInstance &Lt; / RTI &gt; is updated (S914). This update corresponds to the process in which the operating channel information is transferred from the GSCL / DSCL to the NSCL.

When the node connection event is received (S916), the node reconnection process is executed (S918). This process is the same as that in the AreaNwkReconfig process. Since the connection of the network node is independent for each node, this process is repeated until all of the network nodes before execution of this process are connected (S920).

When all the nodes are connected, the MAN event handler delivers the sleep schedule parameters before execution of the present process to the sink node (S922). The change of the network parameters and the sleep schedule parameters corresponds to the sink node generating a beacon message having the parameter and sending it to the M2M area network. Thereafter, when a response to this is received (S924, S926), the process ends.

10 is a diagram illustrating a NwkChanScan process according to an embodiment of the present invention. This is the process of performing quality state measurement for all available channels in the network.

When the execution of this process is triggered, the MAN event handler requests an available channel scan to the sink node (S1002). This request is broadcast by the sink node to all nodes in the M2M domain network. The quality information of the available channels measured by each node is transmitted to the sink node as a measurement result, which is notified to the MAN event handler again by the sink node (S1004, S1006). The measurement result has a list of ED and LQI values for each channel number. The MAN event processor updates the channel status value of the corresponding node in the management object for the M2M area network based on the measurement result (S1008). Next, the corresponding attribute of the management resource for the access node in the NSCL is updated based on the measurement result converted into the resource expression (S1010). This process is repeated every time a measurement result is notified (S1012). The process is terminated when a measurement result is received from all the nodes in the node list. At this time, the value of the ResultsData node is updated, and the ResultsData is collected and converted (S1014, S1016).

Detailed procedures for managing the M2M area network configuration according to an exemplary embodiment of the present invention are shown in FIGS.

11 is a flowchart illustrating an M2M area network reconfiguration procedure according to an embodiment of the present invention. If the M2M application or M2M device management system (NA / MDMS) 1130 determines the reconfiguration of the M2M domain network according to the operational policy, the decision logic, or the operator's needs, And requests update (S1152). After receiving the request, the NSCL 1120 transmits the parameter data to the GSCL / DSCL 1114 to request the update of the network parameters (S1154). The GSCL / DSCL 1114 updates the managed object node areaNwkParam for the network parameter with the received parameter data and transmits a response message to the request (S1156). Upon receiving the response message, the NSCL 1120 updates the network parameter property areaNwkParam and notifies the network parameter in step S1158 that the network parameter has been successfully updated (S1158).

The NA / MDMS 1130 then requests an update of the areaNwkReconfig resource to trigger execution of the reconfiguration process (S1160). Then, the NSCL 1120 transmits a message requesting execution of the managed object node areaNwkReconfig to the GSCL / DSCL 1114 (S1162), and delivers the successful update response to the NA / MDMS 1130 (S1164). When the response is received, the NA / MDMS 1130 requests creation of a new <subscription> resource under the nwkActionStatus resource (S1166) and receives a response to the creation result (S1168). The resource subscribes to the change notification so that the result of execution of the process can be notified.

When the execution message of S1162 is received, the GSCL / DSCL 1114 executes the AreaNwkReconfig process. The process is executed according to the flow of S1170 to S1192. Upon completion of the above execution, the GSCL / DSCL 1114 transmits the execution result to the NSCL 1120 through a status information general alert message to notify the execution result (S1194). The NSCL 1120 updates the operationStatus attribute using the execution result and notifies the NA / MDMS 1130 of the updated contents (S1196).

12 is a diagram illustrating a network reconnection procedure of a MAN node for managing M2M area network configuration according to an embodiment of the present invention.

As part of the AreaNwkReconfig process, the reconnection procedure of the MAN node of FIG. 12 is performed. The MAN nodes 1210 and 1211 make a Network Join request and connect to the M2M area network by receiving a Network Join response as a result (S1242 to S1250). The Network Join response contains the network address assigned to the node. The M2M domain network treats the node as connected to the network by sending a Network Join response. And transmits an update device command including the network address assigned to the access node to the sink node 1212 (S1252). If the node transmitting the Network Join response is a node not less than two hops from the sink node 1212, the update device command is transmitted to the sink node 1212 via the intermediate node.

When the update device command is received from the MAN node or a response message to the network join request is transmitted to the MAN node, the sink node 1212 notifies the GSCL / DSCL 1214 of the node connection event including the network address of the access node (S1254). When the event is received, the GSCL / DSCL 1214 requests and collects its node information for the node at the address (S1256 to S1266). When all the node information is collected, the GSCL / DSCL 1214 stores the collected node information in the existing management object MANDMO for the access node. That is, the management object node values are updated. GSCL / DSCL adds the managed object reference of the access node to the node list by updating the node list.

The GSCL / DSCL 1214 transforms the managed object MANDMO data into a resource representation to transfer the access node information to the NSCL 1220, and then updates the <attachedDevice> resource of the NSCL corresponding to the managed object MANDMO of the access node (S1268, S1270). The GSCL / DSCL 1214 updates the ListOfDevices attribute of the NSCL 1220 to forward the next updated node list to the NSCL 1220 (S1272, S1274). At this time, the ListOfDevices data is changed and stored as a list of NSCL (1220) < attachedDevice > resource references. Due to the update of the attribute, the ListOfDevices data is notified to the NA / MDMS 1230 which is a subscriber subscribed to the change notification of the areaNwkEvent resource (S1276, S1278). The NA / MDMS 1230 receiving the notification receives the information of the access node by inquiring about the <attachedDevice> resource of the reference added to the node list (S1280, S1282).

13 is a flowchart illustrating an operation channel change procedure for M2M area network configuration management according to an exemplary embodiment of the present invention.

If an operational policy change decision of the M2M domain network is determined by the operating policy or the decision logic and the operator's needs, the M2M application or M2M device management system (NA / MDMS) 1330 is operated And requests updating of the channel number (S1342). The NSCL 1320 receives the request, and then transmits the parameter data to the GSCL / DSCL 1314 to request the update of the channel number parameter (S1344). The GSCL / DSCL 1314 updates the managed object node channelNumber for the channel number parameter with the received parameter data and transmits a response message to the NSCL 1320 (S1346). Upon receiving the response message, the NSCL 1320 updates the channel number parameter attribute channelNumber and notifies the NA / MDMS 1330 of the successful update of the channel number parameter (S1348).

The NA / MDMS 1330 then requests an update of the operChannelChange resource to trigger execution of the operational channel change process (S1350). Then, the NSCL 1320 transmits a message requesting execution of the managed object node operChannelChange to the GSCL / DSCL 1314 (S1352), and immediately transmits a successful update response to the NA / MDMS 1330 (S1353). Upon receiving the response, the NA / MDMS 1330 requests creation of a new <subscription> resource under the nwkActionStatus resource and receives a response to the result of the creation. The generated < subscription > resource indicates a subscriber who subscribed to receive immediate notification of the execution result of the process.

When the execution message of S1352 is received, the GSCL / DSCL 1314 executes an operChannelChange process. The process is executed according to the flow of S1354 to S1380. When the execution is completed, the GSCL / DSCL 1314 transmits the execution result to the NSCL 1320 through a status information general alert message to notify the execution result (S1382). The NSCL 1320 updates the operationStatus attribute using the execution result and notifies the NA / MDMS 1330 of the updated contents (S1390). The operational channel change procedure is terminated in response to the NA / MDMS 1330 for that notification (S1392).

FIG. 14 is a diagram illustrating a network channel scanning procedure according to an embodiment of the present invention. The network channel scanning procedure is a procedure of collecting radio quality data of all channels available in the current wireless M2M area network prior to the operation channel changing procedure. This procedure is used as one of methods for determining whether to perform the operation channel change procedure and corresponds to the network event notification step which is one step of the M2M area network configuration management.

The NA / MDMS 1430 requests the NSCL 1420 to update the areaNwkChanScan resource to trigger the execution of the network channel scan process (S1442). Then, the NSCL 1420 delivers a message requesting the execution of the managed object node areaNwkChanScan to the GSCL / DSCL 1414 (S1444) and immediately delivers the successful update response to the NA / MDMS 1430 (S1445). When the response is received, the NA / MDMS 1430 requests creation of a new <subscription> resource under the areaNwkChanScan resource and receives a response to the creation result. The generated < subscription > resource indicates a subscriber who subscribed to receive immediate notification of the execution result of the process.

When the execution message of S1444 is received, the GSCL / DSCL 1414 executes the NwkChanScan process. The process is executed according to the flow of S1446 to S1466. When the execution is completed, the GSCL / DSCL 1414 transmits the execution result to the NSCL 1420 through a status information common alert message to notify the execution result (S1468). The NSCL 1420 updates the ResultsData attribute using the execution result and notifies the NA / MDMS 1430 of the updated contents (S1470, S1472). If a change notification subscription through the creation of a new <subscription> resource is made in advance for the nwkActionStatus resource, the NA / MDMS 1430 receives notification of the operational status and queries the ResultsData attribute and receives the measurement data, The channel scan procedure is terminated.

15 is a diagram illustrating a sleep schedule change procedure for M2M area network configuration management according to an embodiment of the present invention.

When the sleep schedule change of the M2M area network is determined according to the operation policy, the judgment logic, or the operator's need, the M2M application or M2M device management system (NA / MDMS) And requests updating of the schedule (S1542). After receiving the request, the NSCL 1520 transmits the parameter data to the GSCL / DSCL 1514 and requests the update of the sleep schedule parameter (S1544). The GSCL / DSCL 1514 updates the managed object node sleepSchedParam for the sleep schedule parameter with the received parameter data and transmits a response message to the NSCL 1520 (S1546). Upon receiving the response message, the NSCL 1520 updates the sleep schedule parameter attribute sleepSchedParam and notifies the NA / MDMS 1530 of the successful update of the sleep schedule parameter (S1548).

The NA / MDMS 1530 then requests the update of the sleepSchedChange resource to trigger the execution of the sleep schedule change process (S1550). Then, the NSCL 1520 delivers a message requesting execution of the managed object node sleepSchedChange to the GSCL / DSCL 1514 (S 1552), and delivers a successful update response to the NA / MDMS 1530 (S 1554). Upon receiving the response, the NA / MDMS 1530 requests creation of a new <subscription> resource under the nwkActionStatus resource and receives a response to the creation result (S1556, S1558). The generated < subscription > resource indicates a subscriber who subscribed to receive immediate notification of the execution result of the process.

When the execution message is received, the GSCL / DSCL 1514 executes the sleepSchedChange process. The process proceeds as in S1560 to S1572. When the execution is completed, the GSCL / DSCL 1514 transmits the execution result to the NSCL 1520 through a status information common alert message to notify the execution result (S1574). The NSCL 1520 updates the operationStatus attribute using the execution result and notifies the NA / MDMS 1530 of the updated contents (S1578, S1580). The sleep schedule change procedure is terminated in response to the NA / MDMS 1530 for that notification.

16 is a diagram illustrating a procedure for connecting a new MAN node for managing the configuration of an M2M area network according to an embodiment of the present invention.

When the update device command is received from the MAN nodes 1610 and 1611 in step S1652 or when a response message to the network join requests S1644 and S1648 is sent from the MAN nodes 1610 and 1611 in steps S1646 and S1650, 1612 notifies the GSCL / DSCL 1614 of a node connection event including the network address of the access node (S1654). When the event is received, the GSCL / DSCL 1614 updates the DevAttached attribute of the NSCL 1620 to update the managed object node DevAttached, change its data to a resource representation, and deliver it to the NSCL 1620. This update process is performed by an update request and an update response (S1656, S1658). Upon receiving the request, the NSCL 1620 updates the DevAttached attribute and then transmits an update response to the GSCL / DSCL 1614 (S1658). And then notifies the NSCL 1620 of the DevAttached attribute value as the update result.

Next, the NA / MDMS 1630 requests creation of a managed object for the access node. The GSCL / DSCL 1614 generates the managed object MANDMO (S1666) and notifies the NSCL 1620 of the result as a generation response (S1670) for the generated request transmitted via the NSCL 1620. NSCL 1620 creates a management resource < attachedDevice > for the access node based on this response. The creation location is the child of the <sclBase> / <scl> / attachedDevices resource, and the management data is stored in the <attachedDevice> / mgmtObjs / areaNwkDeviceInfo resource.

The GSCL / DSCL 1614 that has transmitted the creation response indicating that the creation of the managed object MANDMO is completed requests and collects its node information with respect to the access node of the network address. When all the node information is collected, the GSCL / DSCL 1614 stores the collected node information in the existing management object MANDMO for the access node. That is, the management object node values are updated. GSCL / DSCL (1614) adds the managed object reference of the access node to the node list by updating the node list.

The GSCL / DSCL 1614 transforms the managed object MANDMO data into a resource representation to transfer the access node information to the NSCL 1620, and then converts the managed object MANDMO data into a resource representation and transmits the <attachedDevice> element of the NSCL 1620 corresponding to the managed object MANDMO of the access node. And updates the resource (S1680, S1682). The GSCL / DSCL 1614 updates the ListOfDevices attribute of the NSCL to deliver the next updated node list to the NSCL (S1684, S1686). At this point, the ListOfDevices data is changed to a list of NSCL's <attachedDevice> resource references and saved. Due to the update of the attribute, the ListOfDevices data is notified to the subscriber subscribed to the change notification of the areaNwkEvent resource, i.e., the NA / MDMS 1630. The NA / MDMS 1630 receiving the notification receives the information of the access node by inquiring about the <attachedDevice> resource of the reference added to the node list (S1692, S1694).

As described above, according to the present invention, it is possible to detect an abnormal state of the wireless M2M area network through the event information management unit, notify the M2M application and the M2M device management system as network event information, and execute the operation process of controlling the corresponding network event Configuration management is possible to quickly adapt the wireless M2M area network.

The procedures shown in Figs. 5 to 16 are summarized as follows.

A method for managing configuration of a wireless M2M area network according to an exemplary embodiment of the present invention includes detecting an abnormal status of an M2M area network and providing it as network event information for an M2M area network connected to an M2M GW or an M2M device, Lt; / RTI &gt; Here, the event information is provided for node connection and node connection rejection, node list update status. In addition, the event information may be provided through the event information management means.

I) an operation channel change process for changing an operation channel operated in the M2M area network, ii) a network reconfiguration process for changing application of network parameters for the network, iii) A sleep schedule change process for changing the sleep schedule for the nodes, iv) a network channel scan process for scanning the available channels of the network, and so on.

As shown in FIG. 5, the configuration management by providing an event of a network and implementing an operation process for implementing the present invention includes a network event notification that detects a network event based on the received data and notifies the management system of the network event A parameter change setting step for transferring the related parameter value necessary for the corresponding operation to the event situation, a process execution trigger step for remotely triggering execution of the process, which is a corresponding operation for the event situation, A process execution and status information collection step of acquiring status information or collecting network status information generated through execution, an execution result notification and collection information delivery step of delivering the result and status information acquired or collected in the step to the management system .

FIG. 17 is a diagram illustrating a structure of an < areaNwkInstance > resource according to an embodiment of the present invention.

The structure of each subresource is shown in Table 1.

 Subregion of <areaNwkInstance> resource SubResource Mandatory / Optional Multiplicity Description areaNwkEvent M One A sub-resource that contains List of Devices and event detected areaNwkTypeInfo M One areaNwkAction M One A sub-resource that contains the actions to be executed. nwkActionStatus M One Indicates the status of the Action subscriptions M One

FIG. 18 is a diagram showing an attribute of an <areaNwkEvent> resource and a structure of a sub resource according to an embodiment of the present invention.

<areaNwkEvent> Table 2 shows the properties of the resource and the structure of the sub-resource.

 <areaNwkEvent> Resource properties and sub-resources AttributeName Mandatory /
Optional Type Description accessRightID M RW creationTime M RO lastModifiedTime M RO devAttached M RW nwkJoinRejected M RW . SubResource Mandatory /
Optional Multiplicity Description listOfDevices M One M2M functional architecture. subscriptions M One

FIG. 19 is a diagram showing an attribute of an <areaNwkAction> resource and a structure of a sub resource according to an embodiment of the present invention.

Table 3 shows the configuration of each sub-resource and attribute.

 <areaNwkAction> Resource properties and sub-resources AttributeName Mandatory /
Optional Type Description accessRightID M RW creationTime M RO lastModifiedTime M RO SubResource Mandatory /
Optional Multiplicity Description areaNwkChanScan
M One This action triggers attached devices to perform the scanning process operChanChange
M One This action triggers attached devices to change the current operational channel to the designated channel areaNwkReconfig
M One This action triggers attached devices to change the current network parameter to the designated network parameter set sleepSchedChange
M One This action triggers attached devices to change the sleep schedule (sleep interval, sleep duration) subscriptions M One

FIG. 20 is a diagram showing a resource attribute and sub-resource structure of <nwkActionStatus> and <areaNwkChanScan> according to an embodiment of the present invention.

2000 is a diagram showing an attribute of a < nwkActionStatus > resource and a structure of a sub resource according to an embodiment of the present invention.

Table 4 shows the configuration of each sub-resource and attribute.

<nwkActionStatus> Properties and sub-resources of the resource AttributeName Mandatory /
Optional Type Description accessRightID M RW See clause 9.2.2. creationTime M RO See clause 9.2.2. lastModifiedTime M RO See clause 9.2.2. operationStatus M RW Indicates the status of the Action SubResource Mandatory /
Optional Multiplicity Description Subscriptions M One See clause 9.2.3.22.

&Lt; AreaNwkChanScan > resource attribute and a sub-resource structure according to an embodiment of the present invention.

The configuration of each sub-resource and attribute is as shown in Table 5.

<areaNwkChanScan> Properties and sub-resources of the resource AttributeName Mandatory /
Optional Type Description accessRightID M RW creationTime M RO lastModifiedTime M RO resultsData M RW Contains data which result from the Action SubResource Mandatory /
Optional Multiplicity Description subscriptions M One

FIG. 21 is a diagram showing attributes of <operChanChange>, <areaNwkReconfig>, and <sleepSchedChange> resources according to an embodiment of the present invention.

2100 shows the properties of the <operChanChange> resource. The structure of the attribute is shown in Table 6.

<operChanChange> Properties of the resource AttributeName Mandatory / Optional Type Description accessRightID M RW creationTime M RO lastModifiedTime M RO ChanNumber M RW Channel number to be changed through the Action

2110 is a diagram showing the properties of the <areaNwkReconfig> resource according to an embodiment of the present invention.

Table 7 shows the structure of each attribute.

 Properties of the <areaNwkReconfig> resource AttributeName Mandatory / Optional Type Description accessRightID M RW creationTime M RO lastModifiedTime M RO areaNwkParam M RW Network param to be changed through the Action

Reference numeral 2120 denotes a property of a <sleepSchedChange> resource according to an embodiment of the present invention.

Table 8 shows the configuration of each attribute.

<sleepSchedChange> Properties of the resource AttributeName Mandatory / Optional Type Description accessRightID M RW creationTime M RO lastModifiedTime M RO sleepSchedParam M RW Sleep schedule param to be changed through the Action

FIG. 22 is a diagram illustrating a configuration of a MANMO according to an embodiment of the present invention. Details of the detailed node for application of the present invention in the configuration of FIG. 22 are as follows.

 M2MAreaNwkInfo / AreaNwks / AreaNwkEvent Status Tree Occurrence Format Min . Access Types Required One node Get

This node is an ancestor node for all event information related to the configuration occurring in the M2M area network belonging to the M2M gateway or the D device.

 M2MAreaNwkInfo / AreaNwks / AreaNwkEvent / DevAttached Status Tree Occurrence Format Min . Access Types Required One Int Get

This node represents the allocated address and connection time of the legacy device or D 'device connected to this M2M area network. Values are separated by commas.

M2MAreaNwkInfo / AreaNwks / AreaNwkEvent / NwkJoinRejected Status Tree Occurrence Format Min . Access Types Required One Chr Get

This node indicates that the connection request of legacy device or D 'device to this M2M area network is rejected.

M2MAreaNwkInfo / AreaNwks / AreaNwkEvent / ListOfDevices Status Tree Occurrence Format Min . Access Types Required One Chr Get

This node contains a list of pointers to all devices in this M2M area network. All values in this list are separated by commas. Each value represents a reference to a specific device.

M2MAreaNwkInfo / AreaNwks / <x> / Operations Status Tree Occurrence Format Min . Access Types Required One node Get

This node is the root node for the execution operation that is allowed to operate on this MO.

 M2MAreaNwkInfo / AreaNwks / <x> / Operations / AreaNwkChanScan Status Tree Occurrence Format Min . Access Types Required One null Get, Exec

This node is used to trigger the action of the AreaNwkChanScan process to scan all available channels for this M2M area network

M2MAreaNwkInfo / AreaNwks / <x> / Operations / AreaNwkChanScan / ResultsData Status Tree Occurrence Format Min . Access Types Required One Int Get

This node contains a list of channel scan value sets. All values in this list are separated by semicolons. Each value represents a channel measurement and is separated by a colon. The left side of the colon indicates the received energy (ED) value and the right side of the colon indicates the LQI value.

M2MAreaNwkInfo / AreaNwks / <x> / Operations / OperChanChange Status Tree Occurrence Format Min . Access Types Required One null Get, Exec

This node is used to trigger the run operation of the OperChanChange process for operating channel change to this M2M area network

M2MAreaNwkInfo / AreaNwks / <x> / Operations / OperChanChange / ChannelNumber Status Tree Occurrence Format Min . Access Types Required One int Get, Replace

This node represents the channel number to be changed through execution of the OperChanChange process.

M2MAreaNwkInfo / AreaNwks / <x> / Operations / AreaNwkReconfig Status Tree Occurrence Format Min . Access Types Required One null Get, Exec

This node is used to trigger the execution of the AreaNwkReconfig process to change the network configuration for this M2M area network

M2MAreaNwkInfo / AreaNwks / <x> / Operations / AreaNwkReconfig / NwkConfigParam Status Tree Occurrence Format Min . Access Types Required One int Get, Replace

This node represents a list of network parameters that should be changed through execution of the AreaNwkReconfig process. All values in this list are separated by commas.

M2MAreaNwkInfo / AreaNwks / <x> / Operations / SleepSchedChange Status Tree Occurrence Format Min . Access Types Required One null Get, Exec

This node is used to trigger the execution of the SleepSchedChange process, which changes the sleep schedule for all devices in this M2M area network.

M2MAreaNwkInfo / AreaNwks / <x> / Operations / SleepSchedChange / SleepSchedParam Status Tree Occurrence Format Min . Access Types Required One int Get, Replace

This node represents a list of sleep schedule parameters that should be changed through execution of the SleepSchedChange process. All values in this list are separated by commas.

 M2MAreaNwkInfo / AreaNwks / <x> / OperationStatus Status Tree Occurrence Format Min . Access Types Required One node Get

This node is an ancestor node for all information about the state of the process execution operation

 M2MAreaNwkInfo / AreaNwks / <x> / OperationStatus / Operation Status Tree Occurrence Format Min . Access Types Required One chr Get

This node represents a link to an execution operation whose status is represented by "OperationStatus &quot;.

 M2MAreaNwkInfo / AreaNwks / <x> / OperationStatus / Progress Status Tree Occurrence Format Min . Access Types Required One int Get

This node indicates the progress status of the execution operation in%. The range is from 0 to 100.

 M2MAreaNwkInfo / AreaNwks / <x> / OperationStatus / FinalStatus Status Tree Occurrence Format Min . Access Types Required One chr Get

This node represents the final state of the execution operation. The predefined value is "SUCCESS" or "FAILURE".

23 is a diagram illustrating a configuration of a management apparatus for managing an M2M area network according to an embodiment of the present invention.

The management apparatus 2300 includes a receiving unit 2310, a control unit 2320, and a transmitting unit 2330. Management device 2300 manages one or more M2M GW or M2M devices 2341, 2342.

The receiving unit 2310 receives the event information generated from the state information of the network from the M2M gateway or the M2M device. The control unit 2320 generates a message indicating an operation process for controlling the network event. The transmitter 2330 transmits the generated message to the M2M gateway or the M2M device. The transmitting unit 2330 can transmit a parameter value necessary for a corresponding operation to the event situation to the M2M gateway or the M2M device.

Then, the M2M gateway or the M2M device performs an operation process according to the indicated message, and the receiving unit 2310 receives status information, which is a result created or performed in the process of performing the operation process, from the M2M gateway or the M2M device . The state information includes all of the information that is collected, produced or produced in the course of performing the operation process.

As the embodiment of the event information, the event information may include information on node connection, information on refusal of node connection, information indicating that one or more nodes constituting the network need to be changed, .

Wherein the operational process includes an operation channel change process for changing an operating channel operated on the network, a network reconfiguration process for changing network parameters for the network, a sleep schedule for changing a sleep schedule for all nodes of the network, A change process, and a network channel scan process for scanning the available channels of the network, all of which are illustrated in Figures 6-17.

For example, the control unit may generate a message instructing the M2M gateway or the M2M device coupled to the M2M area network to apply the minimum sleep schedule to indicate the network reconfiguration process, Upon receiving the event information from the M2M device, the controller determines whether the state of the network is stable, and the controller generates a message for restoring the sleep schedule of the M2M gateway or the M2M device to a value before application of the minimum sleep schedule can do. This is an embodiment that uses the minimum sleep schedule to shorten the reconnection time of the node and the normalization time of the M2M area network. In this case, a small sleep schedule parameter is initially applied and then the original sleep schedule parameter is applied.

As described above, when the embodiment of the present invention is implemented, the abnormal state of the M2M area network can be detected through the event information management unit, the M2M application and the M2M device management system can be notified as the network event information, The network event can be controlled so that the configuration of the M2M area network can be appropriately adapted to the event situation so that the operation efficiency of the network can be improved and the service life of the entire network and the quality of application service can be improved.

The foregoing description is merely illustrative of the technical idea of the present invention, and various changes and modifications may be made by those skilled in the art without departing from the essential characteristics of the present invention. Therefore, the embodiments disclosed in the present invention are intended to illustrate rather than limit the scope of the present invention, and the scope of the technical idea of the present invention is not limited by these embodiments. The scope of protection of the present invention should be construed according to the following claims, and all technical ideas within the scope of equivalents should be construed as falling within the scope of the present invention.

Claims (18)

The M2M gateway or the M2M device detecting the state of the network;
Generating the detected state information as event information of the network and transmitting the event information to a management apparatus managing the M2M area network;
The M2M gateway or the M2M device receiving a parameter value necessary for a corresponding operation for an event of the network from the management device;
Receiving a message including a trigger signal for an operation process set to correspond to an event of the network from the management apparatus; And
And controlling an abnormal state corresponding to an event of the network by performing an operation process according to the received message,
The M2M gateway or the M2M device generates and manages a management object for the M2M area network,
Wherein the operational process includes an operation channel change process for changing an operating channel operated on the network, a network reconfiguration process for changing network parameters for the network, a sleep schedule for changing a sleep schedule for all nodes of the network, A change process, and a network channel scan process for scanning an available channel of the network.
The method according to claim 1,
Wherein the network reconfiguration process comprises: applying the minimum sleep schedule to the M2M gateway or the M2M device; And
Detecting a state of the network and restoring the sleep schedule to a value before application of the minimum sleep schedule.
The method according to claim 1,
Wherein the event information includes at least one of a node connection information, a node connection rejection information, information indicating that one or more nodes constituting the network need to be changed, A method for managing the configuration of an area network.
delete The method according to claim 1,
After performing the operation process
And transmitting the status information generated as a result of performing the operation process to the management apparatus.
Receiving event information generated from state information of a network from an M2M gateway or an M2M device;
Transmitting a parameter value necessary for a corresponding operation to an event of the network to the M2M gateway or the M2M device;
Sending a message to the M2M gateway or the M2M device, the message including a trigger signal for an operation process set to correspond to an event of the network; And
The M2M gateway or the M2M device performing the operation process to control an abnormal state corresponding to an event of the network or receiving the generated status information from the M2M gateway or the M2M device, ,
Wherein the operational process includes an operation channel change process for changing an operating channel operated on the network, a network reconfiguration process for changing network parameters for the network, a sleep schedule for changing a sleep schedule for all nodes of the network, A change process, and a network channel scan process for scanning an available channel of the network.
The method according to claim 6,
Wherein the network reconfiguration process comprises: sending a message to the M2M gateway or the M2M device instructing to apply a minimal sleep schedule; And
Receiving an event information from the M2M gateway or the M2M device and transmitting a message instructing to restore the sleep schedule of the M2M gateway or the M2M device to a value before application of the minimum sleep schedule, How to manage the configuration of the network.
The method according to claim 6,
Wherein the event information includes at least one of a node connection information, a node connection rejection information, information indicating that one or more nodes constituting the network need to be changed, A method for managing the configuration of an area network.
delete A sink node for detecting a state of the network;
A REM (Remote Entity Management) function for generating the detected state information as event information of the network; And
And a GC (Generic Communication) function unit for transmitting the event information to a management apparatus that manages an M2M area network and receiving a message including a trigger signal for an operation process set to correspond to an event of the network from the management apparatus,
The REM function unit performs an operation process according to the received message to control an abnormal state corresponding to an event of the network,
Wherein the operational process includes an operation channel change process for changing an operating channel operated on the network, a network reconfiguration process for changing network parameters for the network, a sleep schedule for changing a sleep schedule for all nodes of the network, A change process, and a network channel scan process for scanning an available channel of the network,
Wherein the GC function unit receives a parameter value necessary for a corresponding operation for an event of the network from the management apparatus after transmitting the event information.
11. The method of claim 10,
The device is an M2M gateway or an M2M device,
The REM function part applies the minimum sleep schedule to the M2M gateway or the M2M device to perform the network reconfiguration process,
Wherein when the sink node detects the state of the network, the REM function unit restores the sleep schedule to a value before application of the minimum sleep schedule.
11. The method of claim 10,
Wherein the event information includes at least one of information on node connection, information on rejection of node connection, information indicating that one or more nodes constituting the network need to be changed, .
delete 11. The method of claim 10,
Wherein the REM function unit generates status information in the process of performing the operation process or generates status information including a result of performing the status information,
And the GC function unit transmits the generated state information to the management apparatus.
A receiving unit for receiving event information generated from state information of the network from the M2M gateway or the M2M device;
A control unit for generating a message including a trigger signal for an operation process set to correspond to an event of the network; And
And a transmitter for transmitting the message to the M2M gateway or the M2M device,
Wherein the receiving unit receives status information from the M2M gateway or the M2M device as a result of performing the process or controlling the abnormal status corresponding to the event of the network by the M2M gateway or the M2M device,
Wherein the operational process includes an operation channel change process for changing an operating channel operated on the network, a network reconfiguration process for changing network parameters for the network, a sleep schedule for changing a sleep schedule for all nodes of the network, A change process, and a network channel scan process for scanning an available channel of the network,
Wherein the transmitting unit transmits a parameter value necessary for a corresponding operation to the event of the network to the M2M gateway or the M2M device.
16. The method of claim 15,
Wherein the controller generates a message instructing the M2M gateway or the M2M device coupled to the network to apply a minimum sleep schedule to indicate the network reconfiguration process;
When the receiver receives the event information from the M2M gateway or the M2M device, the controller generates a message for restoring the sleep schedule of the M2M gateway or the M2M device to a value before application of the minimum sleep schedule Management device.
16. The method of claim 15,
Wherein the event information includes at least one of information on node connection, information on refusal of node connection, information indicating that one or more nodes constituting the network need to be changed, Device.
delete

Images